advertisement
Raritan EMX
User Guide
Release 2.2.0
Copyright © 2012 Raritan, Inc.
EMX-0D-v2.2.0-E
September 2012
255-80-6107-00
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.
FCC Information
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a commercial installation. This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential environment may cause harmful interference.
VCCI Information (Japan)
Raritan is not responsible for damage to this product resulting from accident, disaster, misuse, abuse, non-Raritan modification of the product, or other events outside of Raritan's reasonable control or not arising under normal operating conditions.
If a power cable is included with this product, it must be used exclusively for this product.
Contents
Chapter 1 Introduction 1
Overview ........................................................................................................................................ 2
What's New in EMX Help ...............................................................................................................iii
Product Models ............................................................................................................................. iv
EMX2-111 ........................................................................................................................... iv
EMX2-888 ........................................................................................................................... iv
Product Features ........................................................................................................................... v
Package Contents ......................................................................................................................... vi
Chapter 2 Installing and Configuring the EMX Device 7
Before You Begin ........................................................................................................................... 7
Mounting the EMX Device ............................................................................................................. 7
Mounting a Zero U EMX Device .......................................................................................... 8
Mounting a 1U EMX Device ................................................................................................ 9
Connecting the EMX to a Power Source ..................................................................................... 11
Configuring the EMX .................................................................................................................... 11
Connecting the EMX to a Computer .................................................................................. 12
Installing the USB-to-Serial Driver ..................................................................................... 12
Connecting the EMX to Your Network ............................................................................... 14
Initial Network Configuration .............................................................................................. 15
Combining Asset Sensors ........................................................................................................... 22
Connecting Asset Sensors to the EMX ........................................................................................ 24
Connecting an Asset Sensor to the EMX-111 ................................................................... 25
Connecting an Asset Sensor to the EMX-888 ................................................................... 27
Connecting AMS-M2-Z Asset Sensors (Optional) ....................................................................... 28
Connecting Blade Extension Strips ............................................................................................. 30
Connecting Environmental Sensors (Optional) ........................................................................... 33
About Contact Closure Sensors ........................................................................................ 35
Connecting Third-Party Detectors/Switches ...................................................................... 35
Contact Closure Sensor LEDs ........................................................................................... 39
Connecting Differential Air Pressure Sensors ............................................................................. 40
Connecting a Logitech Webcam (Optional) ................................................................................. 41
Connecting a Schroff LHX Heat Exchanger (Optional) ............................................................... 41
Chapter 3 Getting Started 43
Supported Web Browsers ............................................................................................................ 43
Connection Ports ......................................................................................................................... 43
LCD Display Panel ....................................................................................................................... 45
LCD Display ....................................................................................................................... 45
Control Buttons .................................................................................................................. 47
iii
Contents
Reset Button ................................................................................................................................ 50
Contact Closure Sensor Termination ........................................................................................... 51
Power Switch ............................................................................................................................... 51
Logging In .................................................................................................................................... 51
Logout .......................................................................................................................................... 52
Changing Your Password ............................................................................................................ 53
Introduction to the Web Interface ................................................................................................. 54
Menus ................................................................................................................................ 55
Setup Button ...................................................................................................................... 55
Status Bar .......................................................................................................................... 55
Add Page Icon ................................................................................................................... 56
Data Pane .......................................................................................................................... 57
Warning Icon ...................................................................................................................... 57
Readings Highlighted in Yellow or Red ............................................................................. 58
Browser-Defined Shortcut Menu ....................................................................................... 60
Viewing the Dashboard ................................................................................................................ 61
Chapter 4 User and Role Management 62
Overview ...................................................................................................................................... 62
Managing Users ........................................................................................................................... 62
Creating a User Profile ...................................................................................................... 62
Setting Up User Preferences (Units of Measure) .............................................................. 67
Setting Up Default User Preferences (Units of Measure).................................................. 67
Changing the User List View ............................................................................................. 68
Viewing Connected Users ................................................................................................. 68
Managing Roles ........................................................................................................................... 69
Setting Up Roles ................................................................................................................ 69
Creating a Role .................................................................................................................. 69
Modifying a Role ................................................................................................................ 70
Deleting a Role .................................................................................................................. 71
Chapter 5 EMX Device Management 72
Overview ...................................................................................................................................... 72
Naming the EMX Device .............................................................................................................. 72
Displaying the Device Information ............................................................................................... 73
Setting the Date and Time ........................................................................................................... 73
Specifying the Device Altitude ..................................................................................................... 74
Changing the Measurement Units ............................................................................................... 75
Determining How to Display Tree Items ...................................................................................... 76
How to Display Asset Sensors .......................................................................................... 76
How to Display LHX Heat Exchangers .............................................................................. 77
Modifying the Network Configuration ........................................................................................... 78
Modifying the Network Interface Settings .......................................................................... 78
Modifying the Network Settings ......................................................................................... 80
Modifying the Network Service Settings ...................................................................................... 84
Changing the HTTP(S) Settings ........................................................................................ 84
Configuring the SNMP Settings, Traps and Informs ......................................................... 85
Changing the SSH Settings ............................................................................................... 90
iv
Contents
Changing the Telnet Settings ............................................................................................ 91
Enabling Service Advertisement ........................................................................................ 92
Configuring the SMTP Settings ................................................................................................... 92
Setting Up an EMX Using Bulk Configuration ............................................................................. 94
Saving an EMX Configuration ........................................................................................... 95
Copying a EMX Configuration ........................................................................................... 96
Backup and Restore the EMX Device Settings ........................................................................... 96
Firmware Upgrade ....................................................................................................................... 97
Updating the Firmware ...................................................................................................... 97
Viewing Firmware Update History ..................................................................................... 98
Full Disaster Recovery ...................................................................................................... 99
Updating the Asset Sensor Firmware ................................................................................ 99
Network Diagnostics .................................................................................................................... 99
Pinging a Host ................................................................................................................. 100
Tracing the Network Route .............................................................................................. 100
Listing TCP Connections ................................................................................................. 100
Downloading Diagnostic Information ......................................................................................... 100
Rebooting the EMX .................................................................................................................... 102
Resetting to Factory Defaults .................................................................................................... 102
Chapter 6 Security 104
Access Security Control ............................................................................................................. 104
Forcing HTTPS Encryption .............................................................................................. 104
Configuring the Firewall ................................................................................................... 105
Setting Up User Login Controls ....................................................................................... 110
Setting Up Role-Based Access Control Rules ................................................................ 113
Setting Up an SSL Certificate .................................................................................................... 118
Certificate Signing Request ............................................................................................. 118
Creating a Self-Signed Certificate ................................................................................... 120
Installing Existing Key and Certificate Files ..................................................................... 122
Downloading Key and Certificate Files ............................................................................ 122
Setting Up LDAP Authentication ................................................................................................ 123
Gathering the LDAP Information ..................................................................................... 123
Adding the LDAP Server Settings ................................................................................... 124
Sorting the LDAP Access Order ...................................................................................... 127
Testing the LDAP Server Connection.............................................................................. 127
Editing the LDAP Server Settings.................................................................................... 127
Deleting the LDAP Server Settings ................................................................................. 128
Disabling the LDAP Authentication.................................................................................. 128
Enabling LDAP and Local Authentication Services ......................................................... 129
Enabling and Editing the Security Banner (Restrictive Service Agreement Banner) ................ 129
Chapter 7 Event Rules, Event Actions and Application Logs 131
Event Rules and Actions ............................................................................................................ 131
Components of an Event Rule ......................................................................................... 131
Creating an Event Rule ................................................................................................... 132
Sample Event Rules ........................................................................................................ 154
Modifying an Event Rule .................................................................................................. 156
v
Contents
Modifying an Action ......................................................................................................... 157
Deleting an Event Rule or Action..................................................................................... 158
A Note about Untriggered Rules ...................................................................................... 158
Event Logging ............................................................................................................................ 158
Viewing the Local Event Log ........................................................................................... 159
Clearing Event Entries ..................................................................................................... 159
Viewing the Communication Log ............................................................................................... 160
Chapter 8 Managing External Devices 161
Overview .................................................................................................................................... 161
EMX and PX2 PDU Cascading Connections ............................................................................ 162
Cascading EMX Devices ................................................................................................. 163
Cascading PX2 Devices with a EMX ............................................................................... 163
Server Accessibility .................................................................................................................... 164
Adding IT Devices for Ping Monitoring ............................................................................ 165
Editing Ping Monitoring Settings ...................................................................................... 167
Deleting Ping Monitoring Settings ................................................................................... 168
Checking Server Monitoring States ................................................................................. 168
Configuring the Serial Port ......................................................................................................... 169
Environmental Sensors .............................................................................................................. 169
Identifying Environmental Sensors .................................................................................. 170
Managing Environmental Sensors ................................................................................... 171
Configuring Environmental Sensors ................................................................................ 172
Setting Data Logging ....................................................................................................... 176
Viewing Sensor Data ....................................................................................................... 177
Unmanaging Environmental Sensors .............................................................................. 181
Threshold Information ...................................................................................................... 182
What is Deassertion Hysteresis?..................................................................................... 182
What is Assertion Timeout? ............................................................................................. 183
Webcams ................................................................................................................................... 184
Configuring Webcams ..................................................................................................... 185
Configuring Webcam Storage ......................................................................................... 186
Viewing Webcam Snapshots and Videos ........................................................................ 187
Taking, Viewing and Managing Webcam Snapshots ...................................................... 188
Sending Videos in an Email or Instant Message ............................................................. 190
GSM Modems ............................................................................................................................ 191
Schroff LHX Heat Exchangers ................................................................................................... 192
Enabling and Disabling Schroff LHX Heat Exchanger Support ....................................... 192
Naming a Heat Exchanger .............................................................................................. 193
Configuring LHX Temperature and Fan Thresholds ....................................................... 194
Monitoring the Heat Exchanger ....................................................................................... 194
Controlling the Heat Exchanger ....................................................................................... 197
PowerLogic PM710 .................................................................................................................... 198
Configuring the PM710 and Configuring Threshold Settings .......................................... 199
Resetting the PM710 Minimum and Maximum Values.................................................... 199
Clearing the PM710 Energy Accumulators ..................................................................... 200
vi
Contents
Chapter 9 Using SNMP 201
Overview .................................................................................................................................... 201
Enabling SNMP .......................................................................................................................... 202
Configuring SNMP Notifications ................................................................................................ 204
SNMPv2c Notifications .................................................................................................... 205
SNMPv3 Notifications ...................................................................................................... 206
Configuring Users for Encrypted SNMP v3 ............................................................................... 208
SNMP Gets and Sets ................................................................................................................. 209
The EMX MIB .................................................................................................................. 209
Chapter 10 Using the Command Line Interface 212
About the Interface ..................................................................................................................... 212
Logging in to CLI ........................................................................................................................ 213
With HyperTerminal ......................................................................................................... 213
With SSH or Telnet .......................................................................................................... 214
Different CLI Modes and Prompts ................................................................................... 215
Closing a Serial Connection ............................................................................................ 215
Restricted Service Agreement ................................................................................................... 216
Help Command .......................................................................................................................... 218
Showing Information .................................................................................................................. 218
Network Configuration ..................................................................................................... 219
Asset Sensor Settings ..................................................................................................... 221
Environmental Sensor Information .................................................................................. 222
Environmental Sensor Threshold Information ................................................................. 224
Show Serial ...................................................................................................................... 224
Serial ................................................................................................................................ 225
Security Settings .............................................................................................................. 225
Existing User Profiles ...................................................................................................... 226
Existing Roles .................................................................................................................. 227
Rack Unit Settings of an Asset Sensor............................................................................ 228
Blade Extension Strip Settings ........................................................................................ 229
Command History ............................................................................................................ 229
History Buffer Length ....................................................................................................... 230
Examples ......................................................................................................................... 230
Configuring the EMX Device and Network ................................................................................ 231
Entering the Configuration Mode ..................................................................................... 231
Device Configuration Commands .................................................................................... 232
Networking Configuration Commands ............................................................................. 234
Security Configuration Commands .................................................................................. 258
Environmental Sensor Configuration Commands ........................................................... 280
Environmental Sensor Threshold Configuration Commands .......................................... 284
User Configuration Commands ....................................................................................... 290
Setting Up User Preferences (Units of Measure) ............................................................ 304
Time Configuration Commands ....................................................................................... 304
Role Configuration Commands ....................................................................................... 307
Asset Management Commands ...................................................................................... 312
Serial Port Configuration Commands .............................................................................. 312
vii
Contents
Asset Sensor Management ............................................................................................. 313
Rack Unit Configuration ................................................................................................... 316
Setting the History Buffer Length..................................................................................... 320
Multi-Command Syntax ................................................................................................... 320
Quitting the Configuration Mode ...................................................................................... 321
Unblocking a User ...................................................................................................................... 321
Resetting the EMX ..................................................................................................................... 322
Restarting the Device ...................................................................................................... 322
Resetting to Factory Defaults .......................................................................................... 322
Network Troubleshooting ........................................................................................................... 323
Entering the Diagnostic Mode ......................................................................................... 323
Diagnostic Commands .................................................................................................... 323
Quitting the Diagnostic Mode .......................................................................................... 326
Querying Available Parameters for a Command ....................................................................... 326
Retrieving Previous Commands ................................................................................................ 327
Automatically Completing a Command...................................................................................... 327
Logging out of CLI ...................................................................................................................... 328
Resetting to Factory Defaults (CLI) ........................................................................................... 328
Appendix A Using Raritan Asset Management Sensors with the EMX 329
Asset Sensors and Tags ............................................................................................................ 329
Configuring the Asset Sensor .......................................................................................... 330
Changing a Specific LED's Color Settings ...................................................................... 332
Connecting AMS-M2-Z Asset Sensors (Optional) ........................................................... 333
Expanding a Blade Extension Strip ................................................................................. 335
Connecting Blade Extension Strips ................................................................................. 336
Appendix B Integrating EMX and Asset Management Sensors with dcTrack 340
Overview .................................................................................................................................... 341
EMX Asset Sensor Management ............................................................................................... 343
Setting Up Asset Sensors in EMX ................................................................................... 343
viii
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 ........................................................................................................ 352
Sensor RJ-12 Port Pinouts ........................................................................................................ 352
RS-485 Port Pinouts .................................................................................................................. 352
Appendix E LDAP Configuration Illustration 354
Step A. Determine User Accounts and Groups ......................................................................... 354
Step B. Configure User Groups on the AD Server .................................................................... 355
Step C. Configure LDAP Authentication on the EMX Device .................................................... 356
Step D. Configure User Groups on the EMX Device ................................................................. 358
Index 363
ix
Chapter 1 Introduction
In This Chapter
What's New in EMX Help ......................................................................... iii
1
2
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.
The following items are required for setting up an asset management system:
ï‚·
Raritan asset tags: You tag an IT device by sticking an electronic asset tag on it
ï‚·
Raritan asset management sensors (asset sensors): Each asset sensor transmits the tag and position information to the EMX device
ï‚·
An EMX device: You can remotely locate each tagged IT device through the EMX device.
With Raritan environmental sensors connected to the EMX device, you can remotely monitor environmental conditions such as temperature or humidity in the data center or server room.
With a Logitech
®
QuickCam
®
Pro 9000 webcam connected, a simple camera and video surveillance system is built, displaying the real-time snapshots or videos inside the server room or data center to enhance monitoring and security.
Events and actions that are triggered when an event occurs are supported by the EMX. Specifically, email messages, log events, syslog messages, webcam snapshots, SNMP traps and SMS messages can be triggered when the events you define occur. Custom messages can be configured for email messages, and images captured by the webcam can be sent to users via email.
In addition, the EMX device integrates with a Schroff ® LHX-20 or LHX-40 heat exchanger, which draws warm air into the air/water heat exchanger to cool the air. This integration provides a solution for remotely monitoring the heat exchanger. EMX can also be used in conjunction with Raritan's data center management application, dcTrack
™
.
This user guide describes the following models:
ï‚·
EMX2-111
ï‚·
EMX2-888
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.
ï‚·
Support for SNMPv2c and SNMPv3 traps and informs - see
Configuring the SNMP Settings, Traps and Informs
ï‚·
Restrictive Service Agreement (security banner) support - see
Enabling and Editing the Security Banner (Restrictive Service
Agreement Banner)
ï‚·
Support for AMS-M2-Z Asset Sensors - see
Connecting AMS-M2-Z
Asset Sensors (Optional)
ï‚·
Support for Logitech ® QuickCam Deluxe for Notebooks and Logitech
QuickCam Communicate MP webcams. See
Webcams
(on page
ï‚·
Setting up alternate webcam snapshot image storage locations. See
Configuring Webcam Storage
ï‚·
Support for the PowerLogic
®
PM710 power meter. See
PowerLogic
PM710
ï‚·
Support for device USB cascading. See
EMX and PX2 PDU
Cascading Connections
ï‚·
Configurable units of measure for individual and all users. See
Setting Up User Preferences (Units of Measure)
Setting Up Default User Preferences (Units of Measure)
(on page
ï‚·
Enhanced bulk configuration feature. See
Setting Up an EMX Using
Bulk Configuration
ï‚·
Enhanced back and restore feature. See
Backup and Restore the
EMX Device Settings
ï‚·
Support for SSL certificates that are part of a chain. See
Setting Up an SSL Certificate
ï‚·
Additional email and SMS placeholder information. See.
Email and
SMS Message Placeholders
ï‚·
Redesigned event and action dialog box for easier rule and action creation. See
Event Rules and Actions
ï‚·
Information on integrating EMX and asset management sensors with
Raritan's data center management application dcTrack ® . See
Integrating EMX and Asset Management Sensors with dcTrack
Please see the Release Notes for a more detailed explanation of the changes applied to this version of the EMX.
iii
iv
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.
EMX2-111
EMX2-111 is a Zero U model with the following ports and components:
ï‚·
1 Sensor port
ï‚·
1 Feature port
ï‚·
1 RS-485 port
ï‚·
2 USB ports (1 USB-A and 1 USB-B)
ï‚·
1 RS-232 port
ï‚·
1 Ethernet port
ï‚·
1 LCD display
ï‚·
Control buttons
EMX2-888
EMX2-888 is a 1U model with the following ports and components:
ï‚·
8 Sensor ports
ï‚·
8 Feature ports
ï‚·
8 RS-485 ports
ï‚·
3 USB ports (2 USB-A and 1 USB-B)
ï‚·
1 RS-232 port
ï‚·
1 Ethernet port
ï‚·
1 LCD display
ï‚·
Control buttons
ï‚·
Contact closure sensor termination
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
ï‚·
User-specified location attributes for environmental sensors
ï‚·
The ability to display temperatures in Celsius or Fahrenheit, height in meters or feet, and pressure in Pascal or psi according to user credentials
ï‚·
Support for a maximum of 130 environmental sensors for the EMX-
888 and 16 for the EMX-111
ï‚·
Support for cascading AMS devices and/or PX2 devices connected to the EMX
ï‚·
Support for SNMP v1, v2, and v3
ï‚·
The ability to send traps and informs using the SNMP protocol
ï‚·
The ability to configure and set values through SNMP
ï‚·
Support for SSH and Telnet services
ï‚·
For SSH, both password and public key authentications are supported
ï‚·
Service Advertisement support
ï‚·
The ability to save one EMX device's configuration settings and then deploy those settings to other identical EMX devices
ï‚·
Support for the tilt sensor implemented on the Raritan asset sensors
ï‚·
Wireless connection via a Raritan-provided wireless USB LAN adapter
ï‚·
The ability to visually monitor the data center environment through a connected Logitech ® webcam. See
Webcams
supported Logitech makes and models.
ï‚·
Support for webcam images sent via email to designated recipients
ï‚·
Support of Cinterion ® MC52iT and MC55iT GSM modems, which allow you to send customized SMS messages to designated recipients for specific events
ï‚·
Support for select models of the Schneider PM710 via Modbus
ï‚·
The ability to send emails, log details, and/or set SNMP traps for specific events
v
vi
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. If anything is missing or damaged, contact the local dealer or Raritan
Technical Support for help.
ï‚·
The EMX device
ï‚·
Power cord
ï‚·
Bracket pack and screws
ï‚·
Asset sensors (optional)
ï‚·
Asset tags (optional)
Chapter 2 Installing and Configuring the EMX
Device
In This Chapter
Mounting the EMX Device ......................................................................... 7
Connecting the EMX to a Power Source ................................................. 11
Combining Asset Sensors ....................................................................... 22
Connecting Asset Sensors to the EMX ................................................... 24
Connecting AMS-M2-Z Asset Sensors (Optional) ................................... 28
Connecting Blade Extension Strips ......................................................... 30
Connecting Environmental Sensors (Optional) ....................................... 33
Connecting Differential Air Pressure Sensors ......................................... 40
Connecting a Logitech Webcam (Optional) ............................................. 41
Connecting a Schroff LHX Heat Exchanger (Optional) ........................... 41
Before You Begin
Prepare the installation site. Make sure the installation area is clean and not exposed to extreme temperatures or humidity. Allow sufficient space around the EMX for cabling and asset sensor connections.
Mounting the EMX Device
Depending on the model you purchased, the way to mount an EMX device varies.
7
8
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. After both L-brackets are installed on the device, you can choose either of the following ways to mount the device in the rack.
 Using rack screws, fasten the device to the rack through two identical holes near the edge of each L-bracket.
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. Align the oval-shaped holes of the rackmount bracket with the threaded holes on one side of the EMX device. b. Secure the rackmount bracket with Raritan-provided screws.
Note: The appropriate oval-shaped hole locations of the rackmount bracket may vary according to the threaded holes on you model.
2. Repeat Step 1 for securing the other rackmount bracket to the other side of the EMX.
9
10
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. Mount the EMX device on the rack by securing the rackmount brackets' ears to the rack's front rails with your own screws, bolts, cage nuts, or the like.
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. Install the cable retention clip by inserting both ends into the tiny holes on two hexagon screws adjacent to the power socket.
2. Plug one end of the Raritan-provided power cord into the power socket, and press the cable retention clip toward the power cord until it holds the cord firmly.
3. Connect the other end of the power cord to an appropriate power source.
Configuring the EMX
To configure the EMX device:
1. Connect the EMX device to a computer via a serial or USB connection.
11
12
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.
If your computer does not have a serial port, use a regular USB cable to connect the EMX to the computer for initial configuration. The EMX device can emulate a USB-to-serial converter after the USB-to-serial driver is properly installed in the Windows ® operating system.
Note: Not all serial-to-USB converters work properly with the EMX device so this section does not introduce the use of such converters.
Now connect the EMX to a computer for initial configuration by following either of the following procedures.
To make a serial connection:
1. Connect one end of the null-modem cable to the RS-232 port labeled
CONSOLE / MODEM on the EMX.
2. Connect the other end of the null-modem cable to the serial port
(COM) on the computer.
To make a USB connection:
1. Connect one end of a regular USB cable to the USB-B port on the
EMX.
2. Connect the other end of the USB cable to the USB-A port on the computer.
Installing the USB-to-Serial Driver
The EMX can emulate a USB-to-serial converter over a USB connection.
A USB-to-serial driver named "Dominion Serial Console" is required for
Microsoft
®
Windows
®
operating systems. Download the dominion-
serial.zip driver file, which contains dominion-serial.inf and dominion-
serial-setup.exe files, from the
Raritan website http://www.raritan.com
under the
Firmware and Documentation http://www.
,
http://www.raritan.com/support/firmware-and-documentation/
section for the EMX.
To install the driver in Windows
®
Vista and 7:
1. Disconnect the EMX's USB cable from the computer.
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. If not, extract it from the
Windows installation CD disc, and copy it to the same directory where the USB-to-serial driver is stored.
 On a CD disc with SP3 included, it is extracted from
I386\SP3.CAB.
 On a CD disc with SP2 included, it is extracted from
I386\SP2.CAB.
 On a CD without an SP, it is extracted from I386\DRIVER.CAB.
3. Connect the EMX's USB cable to the computer.
4. The computer detects the new device and the "Found New Hardware
Wizard" dialog appears. If this dialog does not appear, choose
Control Panel > System > Hardware > Device Manager, right-click the Dominion Serial Console, and choose Update Driver.
5. Select "Install from a list or specific location," and specify the location where the driver is stored.
6. If you see the message requesting the file "usbser.sys," specify the location of the file.
7. The installation is complete.
In Linux:
No additional drivers are required, but you must provide the name of the tty device, which can be found in the output of the "dmesg" after connecting the EMX to the computer. Usually the tty device is
"/dev/ttyACM#" or "/dev/ttyUSB#," where # is an integer number.
For example, if you are using the kermit terminal program, and the tty device is "/dev/ttyACM0," perform the following commands:
> set line /dev/ttyACM0
> connect
13
14
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.11n wireless USB LAN adapter into the USB-A port on your EMX.
 Connect a USB docking station to the USB-A port on the EMX and plug the 802.11n wireless USB LAN adapter into the appropriate USB port on the docking station.
Supported Wireless LAN Configuration
If you select the wireless connection, ensure that both of your wireless
USB LAN adapter and wireless network configuration meet the following requirements.
 Network type: 802.11n
 Protocol: WPA2 (RSN)
 Key management: WPA-PSK
 Encryption: CCMP (AES)
Important: Currently only Raritan-provided wireless USB LAN adapters are supported. You may contact Raritan Technical
Support for this information.
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)
To configure the EMX device:
1. Go to the computer that you connected to the EMX and open a communications program such as HyperTerminal or PuTTY.
2. Select the appropriate COM port, and make sure the port settings are configured as follows:
 Bits per second = 115200 (115.2Kbps)
 Data bits = 8
 Stop bits = 1
 Parity = None
 Flow control = None
Tip: For a USB connection, you can find out which COM port is assigned to the EMX by choosing Control Panel > System >
Hardware > Device Manager, and locating the "Dominion Serial
Console" under the Ports group.
3. Press Enter.
4. The EMX prompts you to log in. Note that both of user name and password are case sensitive. a. At the Username prompt, type admin and press Enter. b. At the Password prompt, type raritan and press Enter.
5. You are prompted to change the password if this is the first time you log in to the EMX. Follow the onscreen instructions to type your new password.
6. The # prompt appears when you log in successfully.
7. Type config and press Enter.
8. To configure network settings, type appropriate commands, and press Enter. All commands are case sensitive. a. To set the networking mode, type this command: network mode <mode> where <mode> is either wired for wired connection (default) or
wireless for wireless connection.
15
16
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 <option>
LAN interface duplex mode where <option> is auto, 10Mbps, or
100Mbps. network interface
LANInterfaceDuplexMode
<mode> where <mode> is half, full or auto.
Tip: You can combine multiple commands to configure multiple parameters at a time. For example, network interface LANInterfaceSpeed <option>
LANInterfaceDuplexMode <mode>
c. For the wireless network mode, you must configure the Service
Set Identifier (SSID) parameter.
To set
SSID
Use this command
network wireless SSID <ssid> where <ssid> is the SSID string.
If necessary, configure more wireless parameters shown in the following table.
To set
BSSID
Use this command
network wireless BSSID
<bssid> where <bssid> is the AP MAC address.
Chapter 2: Installing and Configuring the EMX Device
To set
Authentication method
Use this command
network wireless authMethod
<method> where <method> is psk for Pre-Shared
Key or eap for Extensible
Authentication Protocol. network wireless PSK <psk>
PSK where <psk> is the PSK string.
EAP outer authentication network wireless eapOuterAuthentication
<outer_auth>
EAP inner authentication where <outer_auth> is PEAP. network wireless eapInnerAuthentication
<inner_auth> where <inner_auth> is MSCHAPv2.
EAP identity network wireless eapIdentity
<identity> where <identity> is your user name for
EAP authentication.
EAP password network wireless eapPassword
EAP CA certificate
When prompted to enter the password for EAP authentication, type the password. network wireless eapCACertificate
When prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program.
Note: The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing "END CERTIFICATE."
d. To determine which IP protocol is enabled and which IP address returned by the DNS server is used, configure the following parameters.
17
18
Chapter 2: Installing and Configuring the EMX Device
To set
IP protocol
Use this command
network ip proto <protocol>
IP address returned by the DNS server where <protocol> is v4Only for enabling IPv4, v6Only for enabling
IPv6 or both for enabling both IPv4 and
IPv6 protocols. network ip dnsResolverPreference
<resolver> where <resolver> 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.
To set
IP configuration method
Use this command
network ipv4 ipConfigurationMode <mode> where <mode> is either dhcp for auto configuration (default) or static for specifying a static IP address.
 For the IPv4 DHCP configuration, configure this parameter.
To set
Preferred host name
(optional)
Use this command
network ipv4 preferredHostName <name> where <name> is the preferred host name.
Tip: To override the DHCP-assigned IPv4 DNS servers with those you specify manually, type this command: network ipv4 overrideDNS <option> where <option> is enable or disable. See the table below for the
IPv4 commands for manually specifying DNS servers.
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 <ip address> where <ip address> is the IP address you want to assign.
Subnet mask network ipv4 subnetMask
<netmask>
Gateway where <netmask> is the subnet mask. network ipv4 gateway <ip address>
Primary DNS server where <ip address> is the IP address of the gateway. network ipv4 primaryDNSServer <ip address> where <ip address> is the IP address of the primary DNS server. network ipv4 secondaryDNSServer <ip address>
Secondary
DNS server
(optional) where <ip address> is the IP address of the secondary DNS server. f. If you enabled IPv6 in the earlier step, configure the IPv6 network parameters.
To set
IP configuration method
Use this command
network ipv6 ipConfigurationMode <mode> where <mode> is either automatic for auto configuration (default) or static for specifying a static IP address.
Tip: To override the DHCP-assigned IPv6 DNS servers with those you specify manually, type this command: network ipv6 overrideDNS <option>
19
20
Chapter 2: Installing and Configuring the EMX Device
where <option> is enable or disable. See the table below for the
IPv6 commands for manually specifying DNS servers.
 For the static IPv6 configuration, you should configure the following parameters. Note that the IP address must follow the IPv6 format.
To set
Static IPv6 address
Gateway
Primary DNS server
Use this command
network ipv6 ipAddress <ip address> where <ip address> is the IP address you want to assign. network ipv6 gateway <ip address> where <ip address> is the IP address of the gateway. network ipv6 primaryDNSServer <ip address>
Secondary
DNS server
(optional) where <ip address> is the IP address of the primary DNS server. network ipv6 secondaryDNSServer <ip address> where <ip address> is the IP address of the secondary DNS server.
9. To quit the configuration mode with or without saving the changes, type either command, and press Enter.
Command Description
apply
Save all configuration changes and quit the configuration mode. cancel
Abort all configuration changes and quit the configuration mode.
The # prompt appears, indicating that you have quit the configuration mode.
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 parameters. show network ip all show network wireless details
Show all IP configuration parameters.
Show all wireless parameters.
(Perform this command only when you enable the wireless mode.)
Tip: You can also type "show network wireless" to display a shortened version of wireless settings.
11. If all are correct, type exit to log out of the EMX. If any are incorrect, repeat Steps 7 to 10 to change any network settings.
The IP address configured may take seconds to take effect.
21
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.
The following diagram illustrates some asset sensors. Note that Raritan provides more types of asset sensors than the diagram.
22
Number Item
8U MASTER asset sensor with 8 tag ports
8U SLAVE asset sensor with 8 tag ports
5U "ending" SLAVE asset sensor with 5 tag ports
Note: Unlike regular slave asset sensors, which have one DIN connector respectively on either end, the ending slave asset sensor has one DIN connector on only one end. An ending asset sensor is installed at the end of the asset sensor assembly.
To assemble asset sensors:
1. Connect a MASTER asset sensor to an 8U SLAVE asset sensor.
 Plug the white male DIN connector of the slave asset sensor into the white female DIN connector of the master asset sensor.
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.
 The final asset sensor can be 8U or 5U, depending on the actual height of your rack.
 Using the "ending" asset sensor as the final asset sensor is strongly recommended.
4. Vertically attach the asset sensor assembly to the rack, next to the IT equipment, making each tag port horizontally align with a rack unit.
The asset sensors are automatically attracted to the rack because of magnetic stripes on the back.
Note: The asset sensor is implemented with a tilt sensor so it can be mounted upside down.
23
24
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.
Letter
A
B
C
Item
Barcode (ID number), which is available on either end of the asset tag
Tag connector
Adhesive area with the tape
Note: The barcode of each asset tag is unique and is displayed in the
EMX web interface so it can easily be identified.
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.
Diagram key
Asset management tags
Asset management strip
25
26
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. The EMX-111 supports a maximum of
10-meters of cable connecting each asset sensor assembly.
4. Connect the other end of the Cat5e/6 cable into the in-line Cat5e/6 connector on the X-cable.
5. Connect the ethernet end of the X-cable into the FEATURE port on the EMX-111 device.
6. Plug the sensor cable of the X-cable into the SENSOR port on the
EMX-111. This supplies power to the asset sensor assembly from the SENSOR port via the Cat5e/6 cable.
Note: If sensors need to be connected to the EMX via the SENSOR port, plug them into the SENSOR connector on the X-cable. If no sensors are connected, this connector can remain empty.
7. Configure the asset sensor. See
Configuring the Asset Sensor
(on
All LEDs on the asset sensor assembly may cycle through different colors during the power-on process if the asset sensor's firmware is being upgraded by the EMX device. After the power-on or firmware upgrade process completes, the LEDs show solid colors. Note that the
LED color of the tag ports with asset tags connected will be different from the LED color of the tag ports without asset tags connected.
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 X-
Cable like the EMX-111.
Diagram key
Asset management tags
Asset management strip
EMX-888
Category 5e/6 cable (Cat5e/6 cable)
27
28
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. If needed, repeat the above steps to connect additional asset sensors to the rest of FEATURE ports.
5. Configure the asset sensor. See
Configuring the Asset Sensor
(on
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 in the cabinet.
Item
A
B
Description
RJ-45 connectors
Tag ports
To connect the AMS-M2-Z asset sensors to the EMX:
1. Connect the AMS-M2-Z to the EMX via a Category 5e/6 cable. a. Connect one end of the cable to the RJ-45 port labeled "Input" on the AMS-M2-Z.
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
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.
See
AMS-M2-Z Daisy-Chain Limitations
cable length limitations. b. Connect one end of the Category 5e/6 cable to the RJ-45 connector labeled "Output" on the AMS-M2-Z being connected to 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
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. Repeat Step 2 to connect IT devices to the other AMS-M2-Z's in the chain via the asset tags.
29
30
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.
The diagram illustrates a tag connector cable and a blade extension strip with 16 tag ports.
Tag connector cable
Item
A
B
C
Description
Barcode (ID number) for the tag connector cable
Tag connector
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.
Blade extension strip
Item
D
E
F
Description
Mylar section with the adhesive tape
Tag ports
Cable socket(s) for connecting the tag connector cable
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. 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. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape.
31
32
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.
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.
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. That is,
ï‚·
For EMX2-111, which has only 1 SENSOR port, a maximum of 16 environmental sensors can be connected.
ï‚·
For EMX2-888, which has 8 SENSOR ports, a maximum of 128 environmental sensors can be connected. Since the EMX2-888 device is implemented with two channels of onboard contact closure termination, it supports a maximum of 130 environmental sensors.
Each SENSOR port can only support a maximum of two Raritan contact closure sensors, which has the shortest update interval among all
Raritan sensors. See
Information about Update Interval
(on page
Note that a Raritan environmental sensor usually contains more than one sensor. For example, a DPX-T2H2 counts as 4 sensors, and a DPX-
T3H1 counts as 4 sensors.
Warning: For proper operation, wait for 15~30 seconds between each connection operation or each disconnection operation of environmental sensors.
To directly connect one or multiple environmental sensors:
ï‚·
Plug the connector of the environmental sensor into the SENSOR port on your EMX device.
Note: Depending on the model you purchased, the total number of
SENSOR ports varies.
To connect environmental sensors via an optional PX sensor hub:
1. Connect a Raritan sensor hub to the EMX device. a. Plug one end of the Raritan-provided phone cable (4-wire, 6-pin,
RJ-12) into the IN port (Port 1) of the hub. b. Plug the other end into one of the SENSOR ports on the EMX device.
33
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.
Raritan sensor hubs CANNOT be cascaded so at most a sensor hub can be connected to each SENSOR port on the EMX device. This diagram illustrates a configuration with a sensor hub connected.
34
The EMX device
Raritan-provided phone cable
Raritan PX sensor hub
Raritan environmental sensors
3. If there are any Raritan air flow sensors attached, make sure that sensor faces the source of the wind (such as a fan) in the appropriate orientation as indicated by the arrow on that sensor.
4. Configure the environmental sensor. See
Configuring
Environmental Sensors
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. The types of discrete detectors/switches that can be plugged into DPX-CC2-TR include those for:
ï‚·
Door open/closed detection
ï‚·
Door lock detection
ï‚·
Floor water detection
ï‚·
Smoke detection
ï‚·
Vibration detection
Raritan does NOT produce most of the above detectors/switches except floor water sensors. When using third-party probes, you must test them with Raritan's DPX-CC2-TR to ensure they work properly.
Important: Integration and testing for third-party detectors/switches is the sole responsibility of the customer. Raritan cannot assume any liability as a result of improper termination or failure (incidental or consequential) of third-party detectors/switches that customers provide and install. Failure to follow installation and configuration instructions can result in false alarms or no alarms. Raritan makes no statement or claim that all third-party detectors/switches will work with DPX-CC2-TR.
Connecting Third-Party Detectors/Switches
There are two ways to connect third-party detectors/switches to the EMX device:
ï‚·
Connect the detectors/switches to DPX-CC2-TR, which will be connected to a SENSOR port on the EMX device
ï‚·
Connect the detectors/switches to the contact closure sensor termination on the EMX device if your EMX device is EMX2-888
35
36
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.
To connect third-party or Raritan's discrete detectors/switches:
1. Strip the insulation around 12mm from the end of each wire of discrete detectors/switches.
2. Press and hold down the tiny rectangular buttons above the termination points on the body of DPX-CC2-TR.
Note: Each button controls the spring of each corresponding termination point.
3. Fully insert each wire of both detectors/switches into each termination point.
 Plug both wires of a detector/switch into the two termination points to the left.
 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. If any detector/switch plugged into the contact closure sensor is
Raritan's floor water sensor, verify that the total cable length from the port of the Raritan PX to the water detector at the end of the water sensor does not exceed 30 meters/100 feet.
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.
2. Uncover the dip switch on the body of DPX-CC2-TR.
3. To set the Normal state for channel 1, locate the dip switch labeled
1.
4. Use a pointed tip such as a pen to move the slide switch to the end labeled N.O or N.C.
 The side labeled N.O (Normally Open): The open status of the connected detector/switch is considered normal. This is the default.
 The side labeled N.C (Normally Closed): The closed status of the connected detector/switch is considered normal.
For Raritan's water sensors, the Normal state should be Normally
Open, which indicates there is no water detected. Adjust the dip switch setting to Normally Open and verify that the LED of the channel where the Raritan's water sensor is connected remains OFF.
5. To set the Normal state for channel 2, repeat Step 4 for adjusting the other dip switch's setting.
6. Install back the dip switch cover.
37
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. You need to test the compatibility after properly installing them.
To connect third-party detectors/switches:
1. Strip the insulation around 12mm from the end of each wire of discrete detectors/switches.
2. Press and hold down the tiny rectangular buttons above the termination points.
Note: Each button controls the spring of each corresponding termination point.
38
3. Fully insert each wire of both detectors/switches into each termination point.
 Plug both wires of a detector/switch into the two termination points to the left.
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.
Contact Closure Sensor LEDs
Two LEDs are located near the contact closure termination points on the
EMX device or Raritan contact closure sensor module (DPX-CC2-TR).
Each LED shows the state of the corresponding channel.
The LED is lit when the associated detector/switch is in the "abnormal" state, which is the opposite of the Normal state.
The meaning of a lit LED varies depending on the Normal state settings.
ï‚·
When the Normal state is set to Normally Closed (N.C):
LED
Not lit
Lit
Sensor state
Closed
Open
ï‚·
When the Normal state is set to Normally Open (N.O):
LED
Not lit
Lit
Sensor state
Open
Closed
39
40
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. Plug one end of a Raritan-provided phone cable to the SENSOR port of the EMX device.
2. Plug the other end of this phone cable to the IN port of the differential air pressure sensor.
3. To connect additional Raritan differential air pressure sensors, do the following: a. Plug one end of a Raritan-provided phone cable to the OUT port of the previous differential air pressure sensor. b. Plug the other end of this phone cable to the IN port of the newly-added differential air pressure sensor. c. Repeat Steps a to b to cascade more differential air pressure sensors. Note that each SENSOR port supports a maximum of
16 environmental sensors.
The EMX device
The Raritan differential air pressure sensor
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. 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. After connecting a webcam, you can visually monitor environmental conditions near the EMX through the web interface from anywhere.
For more information on the QuickCam webcam, see the user documentation accompanying it.
To connect a webcam:
1. Connect the webcam to the USB-A port on the EMX device. The
EMX automatically detects the webcam.
2. Position the webcam properly.
Snapshots or videos captured by the webcam are immediately displayed in the EMX web interface. See
Webcams
information on the feature, and
Configuring Webcams
for information on configuring the webcam once it has been connected.
Note: You must have Change Webcam Configuration permission applied to your role in order to configure webcams, and the View Webcam
Images and Configuration permission to view images in EMX.
Connecting a Schroff LHX Heat Exchanger (Optional)
To remotely monitor and administer the Schroff
®
LHX-20 or LHX-40 heat exchangers through the EMX device, you must establish a connection between the heat exchanger and the EMX device.
For more information on the LHX heat exchanger, see the user documentation accompanying that product.
To connect an LHX heat exchanger:
1. Plug one end of a standard Category 5e/6 UTP cable into the RS-
485 port on the Schroff LHX heat exchanger.
2. Plug the other end of the cable into one of available RS-485 ports on your EMX device.
41
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.
42
Chapter 3 Getting Started
In This Chapter
Supported Web Browsers ........................................................................ 43
Contact Closure Sensor Termination ...................................................... 51
Changing Your Password ........................................................................ 53
Introduction to the Web Interface ............................................................ 54
Viewing the Dashboard ........................................................................... 61
Supported Web Browsers
The following web browsers can be used to access the EMX web interface:
ï‚·
Google ® Chrome ® 12+
ï‚·
Internet Explorer
®
8 and 9
ï‚·
Firefox
®
10+
ï‚·
Safari ® 5.1 (MacOS Lion)
ï‚·
Konqueror
The following smart phone browsers are supported:
ï‚·
Safari on iOS 5.01
ï‚·
Dolphin
®
3.2.1
Connection Ports
Depending on the model you purchased, the total number of ports available varies.
The table below explains the function of each port.
Port
USB-B
USB-A
Used for...
Establishing a USB connection between a computer and the EMX device.
This port can be used for disaster recovery of the EMX device. Contact
Raritan Technical Support for instructions.
Connecting a USB device.
This is a "host" port, which is powered, per USB 2.0 specifications.
43
44
Chapter 3: Getting Started
Port
FEATURE
CONSOLE/
MODEM
SENSOR
ETHERNET
RS-485
Used for...
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.
Establishing a serial connection between a computer and the EMX device:
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.
Connection to Raritan's environmental sensors.
A Raritan sensor hub may be required if you want to connect more environmental sensors.
Connecting the EMX device to your company's network:
Connect a standard Cat5e/6 UTP cable to this port and connect the other end to your network. This connection is necessary to administer or access the EMX device remotely using the web interface.
There are two small LEDs adjacent to the port:
 Green indicates a physical link and activity.
 Yellow indicates communications at 10/100 BaseT speeds.
For a USB-cascading configuration, the wired connection is a must for the
master EMX. See Cascading the EMX via USB for details.
Note: Connection to this port is not required if the EMX device is connected to a wireless network.
Connection to an electrical device with the RS-485 interface. Currently the
EMX only supports the Schroff
®
LHX-20 and LHX-40 heat exchangers.
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.
45
46
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.
 For a sensor whose ID number is equal to or over
100, it is displayed as "1 SENSOR XX" where XX are the last two numeric digits of the ID number.
ï‚·
The number of the FEATURE port where the selected asset sensor is connected.
Depending on your selection, the information displayed includes:
ï‚·
Sensor reading comprising numeric digits or sensor state comprising alphabetical characters.
ï‚·
Number of the SENSOR port where the selected sensor is physically connected.
ï‚·
X, Y or Z coordinates of the selected environmental sensor.
ï‚·
Serial number of the selected environmental sensor.
ï‚·
The selected rack unit number of the selected asset sensor.
Note: For the Raritan asset sensor, a rack unit refers to a tag port.
ï‚·
MAC address of the EMX
The text "ALARM" may appear to indicate either of the following scenarios:
ï‚·
For a numeric environmental sensor, such as a temperature sensor, it means the sensor reading reaches or crosses the upper or lower thresholds if these thresholds have been enabled.
ï‚·
For a discrete (on/off) environmental sensor, such as a contact closure sensor, it means the sensor enters the abnormal state.
ï‚·
For an asset sensor, it means NO asset tag is detected on the selected rack unit.
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.
ï‚·
Up and Down buttons for selecting a specific ID or port number
ï‚·
MODE button for switching between different types of target information, including environmental sensor information, asset management information, and MAC address
ï‚·
FUNC button for switching between different types of data for a selected environmental sensor
By default the display panel shows the first environmental sensor listed on the External Sensors page of the web interface until you select a different environmental sensor or a different target.
Environmental Sensor Information
The environmental sensor information is displayed as "SENSOR" in the
LCD display. Operate the LCD display to view information about the selected environmental sensor, including the sensor reading or state, the sensor's physical port number, X, Y, Z coordinates and its serial number.
To display the environmental sensor information:
1. Press the Up or Down button until the desired environmental sensor's ID number is displayed in the top of the LCD display. See
LCD Display
(on page 45). For example, "SENSOR 1" refers to the
#1 sensor listed on the External Sensors page of the web interface.
 Pressing the (UP) button moves up one selection.
 Pressing the (DOWN) button moves down one selection.
 "1 SENSOR 24" refers to the #124 sensor.
Note: Press and hold the Up or Down buttons for at least two (2) seconds to quickly move through several items at once.
47
48
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.
Note: Numeric sensors use numeric values to indicate the environmental or internal conditions while discrete (on/off) sensors use alphabetical characters only to indicate the state changes.
3. If your EMX device has more than one SENSOR ports, press the
FUNC button to display the physical port number of the environmental sensor. The port number is shown as "P:X," where X is the port number. For the onboard contact closure sensor, it is displayed as CC1 or CC2.
4. Press the FUNC button to display the X, Y and Z coordinates of the sensor respectively.
 X coordinate is shown as "x:XX," where XX are the first two numeric digits entered for the X coordinate in the web interface.
 Y coordinate is shown as "y:XX," where XX are the first two numeric digits entered for the Y coordinate in the web interface.
 Z coordinate is shown as "z:XX," where XX are the first two numeric digits entered for the Z coordinate in the web interface.
If one or both of the first two digits for a specific coordinate are alphabetical characters, one or two underscores are displayed in place of the alphabetical characters.
5. Press the FUNC button again to display the serial number of the sensor, which is shown as "s:XX," where XX are two digits of the serial number. The LCD will cycle through the serial number from the first two digits to the final two.
For example, if the serial number is AE17A00022, the LCD display shows the following information one after another: s:AE --> s:17 --> s:A0 --> s:00 --> s:22
If no button is pressed after tens of seconds, the LCD display returns to the sensor reading or 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. See
LCD Display
 Pressing the (UP) button moves up one selection.
 Pressing the (DOWN) button moves down one selection.
If no asset sensor is detected or physically connected to the selected
FEATURE port, the term "nA" appears.
Note: Press and hold the Up or Down buttons for at least two (2) seconds to quickly move through several items at once.
3. Press the FUNC button. When an blinking double-arrow symbol appears on the left side of the LCD display, press the Up or Down button to select the desired rack unit on the currently selected asset sensor. The rack unit number appears in the middle of the LCD display.
 If the term "ALARM" appears below the rack unit number, it means no asset tag is detected or physically connected to that rack unit.
 If the term "ALARM" does NOT appear, it means a connected asset tag is detected on the rack unit.
IP Address
The IP Address is also available in the EMX LCD display. Use the Mode button to switch between sensor, asset and device mode. When in device mode, a small "d" is displayed in the upper left corner. The address starts with the IPv4 address, indicated by "i4" in the upper right corner of the display. Use the Function button to switch to the MAC address, in which case an "M" is displayed in the upper right corner.
49
50
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. The MAC address is displayed as "M:XX", where XX are two digits of the MAC address. The LCD will cycle through the MAC address from the first two digits to the final two.
For example, if the MAC address is 00:0d:5d:03:5E:1A, the LCD display shows the following information one after another:
M:00 --> M:0d --> M:5d --> M:03 --> M:5E --> M:1A
Reset Button
The reset button is located inside a small hole which is labeled RESET.
The EMX device can be reset to its factory default values using this button when a serial connection is available. See
Resetting to Factory
Defaults
Without the serial connection, pressing this reset button restarts the EMX device's software.
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
ï‚·
Contact Closure Sensor LEDs
Power Switch
The power switch turns on or off the EMX device.
To power cycle the EMX, press the power switch to turn off the device,
wait at least 10 seconds and then press the power switch again to turn it on. Note that a minimum of 10-second power-off period is required, or the device may not boot up properly.
Logging In
To log in to the web interface, you must enter a user name and password. The first time you log in to the EMX, use the default user name (admin) and password (raritan). You are then prompted to change the password for security purposes.
Exception: If you already changed the password for the admin account during the
Initial Network Configuration
password instead to log in to the web interface, and the EMX will NOT prompt you to change the password.
After successfully logging in, you can create user profiles for your other users. These profiles define their login names and passwords. See
Creating a User Profile
If a security login agreement has been enabled, you must accept the agreement in order to complete the login. The security agreement appears in the same dialog as the login credential requirements. See
Enabling and Editing the Security Banner (Restrictive Service
Agreement Banner)
(on page 129) for more information.
The web interface allows a maximum of 16 users to log in simultaneously.
You must enable JavaScript in the web browser for proper operation.
To log in to the web interface:
1. Open a browser, such as Microsoft Internet Explorer or Mozilla
Firefox, and type this URL:
51
Chapter 3: Getting Started
http(s)://<ip address> where <ip address> 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.
52
Logout
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. If a security agreement is displayed on the Login page, accept it.
Note: If you do not accept the security agreement, you cannot log on to the EMX.
5. Click Login or press Enter. The EMX page opens.
Note: Depending on your hardware configuration, elements shown on the EMX page may appear slightly different from this image.
After finishing your tasks with the EMX, you should log out to prevent others from accessing the web interface.
To log out of the web interface:
1. Do one of these:
 Click "logout" on the top-right corner of the web interface.
 Close the web browser by clicking the Close button (
) on the top-right corner of the browser.
 Close the web browser by choosing File > Close, or File > Exit.
The command varies according to the version of the browser you use.
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
If you are the administrator (admin), the EMX web interface automatically prompts you to change the password if this is your first time to log in to the EMX. If you have the Administrator Privileges, you can change other users' passwords, as well. See
Modifying a User Profile
To change your password:
1. Choose User Management > Change Password. The Change User
Password dialog appears.
2. Type the current password in the Old Password field.
3. Type your new password in the Password and Confirm Password fields. The password can be 4 to 64 characters long. It is case sensitive.
4. Click OK to save the changes.
53
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.
54
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.
ï‚·
Help displays information regarding the firmware and all open source packages embedded on the EMX. In addition, you can access the user guide from this menu.
Setup Button
The Setup button is available for most tree items. It triggers a setup dialog where you can change settings for the selected tree item.
Status Bar
The status bar shows five pieces of information from left to right.
ï‚·
Device name:
This is the name assigned to the EMX device. The default is "EMX."
See
Naming the EMX Device
ï‚·
IP address:
The numbers enclosed in parentheses is the IP address assigned to the EMX device. See
Initial Network Configuration
Modifying the Network Settings
Tip: The presence of the device name and IP address in the status bar indicates the connection to the EMX device. If the connection is lost, it shows " " instead.
ï‚·
Login name:
This is the user name you used to log in to the web interface.
55
56
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, <local> is displayed instead of an IP address.
There are different types of access clients:
 Web GUI: Refers to the EMX web interface.
 CLI: Refers to the command line interface (CLI).
The information in parentheses following "CLI" indicates how this user was connected to the CLI.
- Serial: Represents the local connection (serial or USB).
- SSH: Represents the SSH connection.
- Telnet: Represents the Telnet connection.
ï‚·
System date and time:
Current date, year, and time are displayed to the right of the bar. If positioning the mouse pointer over the system date and time, the time zone information is also displayed.
Sometimes a flag icon ( ) may appear to the far right of the bar when a communication error between the EMX device and the graphical user interface (GUI) occurs. When the icon appears, you can click the icon to view the communications log. See Viewing the Communication Log.
Add Page Icon
The Add Page icon , located on the top of the data pane, lets you open data pages of multiple tree items without overriding any opened page.
To open new data pages:
1. Click the Add Page icon page appears.
. A new tab along with a blank data
2. Click a tree item whose data page you want to open. The data of the selected tree item is then displayed on the blank page.
3. To open more data pages, repeat Steps 1 to 2. All tabs representing opened pages are shown across the top of the page.
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 (
) on the corresponding tab.
Data Pane
The right pane shows the data page of the selected tree item. The data page includes the item's current status, settings and a Setup button (if available).
All tabs above the pane represent the opened data pages. The highlighted tab indicates the current selection.
You can change the width of the pane to make the area larger or smaller.
To adjust the pane's width:
1. Move the mouse pointer to the left border of the right pane.
2. When the mouse pointer turns into a two-way arrow, drag the border horizontally to widen or shrink the pane.
Warning Icon
If the value you entered in a specific field is invalid, a red warning icon appears to the right and the field in question is surrounded by a red frame as shown in this illustration.
When this occurs, position your mouse pointer over the warning icon to view the reason and modify the entered value accordingly.
57
58
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.
Note: Numeric sensors use numeric values to indicate the environmental or internal conditions while discrete (on/off) sensors use alphabetical characters only to indicate the state changes.
See the table for the meaning of each color:
Color
White
State
The background is white in one of the following scenarios:
ï‚·
For a numeric sensor, no thresholds have been enabled.
ï‚·
If any thresholds have been enabled for a numeric sensor, the sensor reading is between the lower and upper warning thresholds.
ï‚·
For a discrete (on/off) sensor, the sensor state is normal.
ï‚·
The sensor reading or state is unavailable.
Yellow The reading drops below the lower warning threshold or rises above the upper warning threshold.
Red The meaning of the red color varies depending on the sensor type:
ï‚·
For a numeric sensor, this color indicates the reading drops below the lower critical threshold or rises above the upper critical threshold.
ï‚·
For a discrete (on/off) sensor, this color indicates the sensor is in the "alarmed" state.
ï‚·
For a Schroff
®
LHX heat exchanger (if available), this color indicates that at least one sensor implemented on that heat exchanger fails. See
Schroff LHX Heat
Exchangers
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.
ï‚· above upper warning: The numeric sensor's reading reaches or exceeds the upper warning threshold.
ï‚· alarmed: The discrete sensor is NOT in the normal state.
For information on the thresholds, see
Configuring Environmental
Sensors
59
60
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.
For information on each shortcut menu command or item, see the online help or documentation accompanying your web browser.
Below is the illustration of the IE browser's shortcut menu. Available menu commands or items may slightly differ based on your web browser version.
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.
Note: If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds, or at least one LHX built-in sensor fails on the heat exchanger. See
Readings Highlighted in Yellow or
Red (EMX)
Readings Highlighted in Yellow or Red
After clicking any other icon in the hierarchical tree, the Dashboard page is overridden. To return to the Dashboard page, click the Dashboard icon.
When the Dashboard page is opened, you can do the following to uncover or hide specific data.
To collapse any section:
1. Locate the section you want to collapse.
2. Click the upward arrow prior to the section title. The data specific to the section is hidden.
To expand a collapsed section:
1. Locate the section you want to expand.
2. Click the downward arrow prior to the section title. The data specific to the section appears.
61
Chapter 4 User and Role Management
In This Chapter
Overview
The EMX is shipped with one built-in user profile: admin, which is used for initial login and configuration. This profile has full system permissions, and should be reserved for the system administrator. It cannot be deleted and its permissions are not user-configurable except for the
SNMP v3 permission.
All users must have a user profile, which specifies a login name and password, and contains additional (optional) information about the user.
Every user profile must have at least a role to determine the user's system permissions. See
Setting Up Roles
any settings, you must log in to the user account with appropriate permissions.
By default, multiple users can log in simultaneously using the same login name.
Managing Users
Creating a User Profile
Creating new users adds a new login to the EMX.
To create a user profile:
1. Choose User Management > Users. The Manage Users dialog appears.
2. Click New. The Create New User dialog appears.
3. Type the information about the user in the corresponding fields. Note that User Name, Password and Confirm Password fields are required.
Field
User Name
Type this...
The name the user enters to log in to the EMX.
 The name can be 4 to 32 characters long.
 It is case sensitive.
62
Chapter 4: User and Role Management
Field Type this...
 Spaces are NOT permitted
Full Name The user's first and last names.
Password,
Confirm Password
The password the user enters to log in. Type it first in the Password field and then again in the
Confirm Password field.
 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.
 The email can be up to 32 characters long.
 It is case sensitive.
4. Select the Enabled checkbox. This is required so the user can log in to the EMX device.
5. Select the "Force password change on next login" checkbox if you prefer a password change by the user when the user logs in for the first time after this checkbox is enabled.
6. Click the SNMPv3 tab to set the SNMPv3 access permission. The permission is disabled by default. a. To permit the SNMPv3 access by this user, select the "Enable
SNMPv3 access" checkbox. Otherwise, leave the checkbox disabled.
Note: The SNMPv3 protocol must be enabled for SNMPv3 access.
See
Configuring the SNMP Settings
b. Set up SNMPv3 parameters if enabling the SNMPv3 access permission.
Field
Security Level
Description
Click the drop-down arrow to select a preferred security level from the list:
 NoAuthNoPriv: No authentication and no privacy.
 AuthNoPriv: Authentication and no privacy.
 AuthPriv: Authentication and privacy. This
63
64
Chapter 4: User and Role Management
Field
Use Password as
Authentication
Pass Phrase
Authentication
Pass Phrase
Description
is the default.
This checkbox is configurable only if AuthNoPriv
or AuthPriv is selected.
When the checkbox is selected, the authentication pass phrase is identical to the user's password.
To specify a different authentication pass phrase, disable the checkbox.
Type the authentication pass phrase in this field if the "Use Password as Authentication Pass
Phrase" checkbox is disabled.
The pass phrase must consist of 8 to 32 ASCII printable characters.
Confirm
Authentication
Pass Phrase
Privacy Pass
Phrase
Re-type the same authentication pass phrase for confirmation.
Use Authentication
Pass Phrase as
Privacy Pass
Phrase
This checkbox is configurable only if AuthPriv is
selected.
When the checkbox is selected, the privacy pass phrase is identical to the authentication pass phrase. To specify a different privacy pass phrase, disable the checkbox.
Type the privacy pass phrase in this field if the
"Use Authentication Pass Phrase as Privacy Pass
Phrase" checkbox is disabled.
The pass phrase must consist of 8 to 32 ASCII printable characters.
Confirm Privacy
Pass Phrase
Authentication
Protocol
Privacy Protocol
Re-type the same privacy pass phrase for confirmation.
Click the drop-down arrow and select the desired authentication protocol from the list. Two protocols are available:
 MD5
 SHA-1 (default)
Click the drop-down arrow and select the desired privacy protocol from the list. Two protocols are available:
 DES (default)
 AES-128
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
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.
 The Operator role provides limited permissions for frequentlyused functions. See
Setting Up Roles
scope of permissions. This role is selected by default.
 If no roles meet your needs, you can:
 Modify the permissions of an existing role: To modify the permissions of any role, double-click the role or highlight it and then click Edit Role. See
Modifying a Role
(on page
 Create a new role by clicking the Manage Roles button: See
Creating a Role
Note: With multiple roles selected, a user has the union of all roles' permissions.
10. To change any measurement units displayed in the web interface and command line interface for this new user, click the Preferences tab, and do any of the following:
 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.
A Pascal is equal to one newton per square meter. Psi stands for pounds per square inch.
Note: The measurement unit change only applies to the web interface and command line interface. To change the EMX device display, see
Setting Up Default User Preferences (Units of
Measure)
Note: Users can change the measurement units at any time by setting up their own user preferences. See
Setting Up User
Preferences (Units of Measure)
11. Click OK to save the changes.
65
66
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. If the password field is left blank, the password is not changed.
5. To change the SNMPv3 access permissions, click the SNMPv3 tab and make necessary changes. For details, see Step 6 of
Creating a
User Profile
6. To change the permissions, click the Roles tab and do one of these:
 Select or deselect any role's checkbox.
 To modify the permissions of any role, double-click the role or highlight it and then click Edit Role. See
Modifying a Role
(on
7. To change the measurement unit for temperature, length or pressure, click the Preferences tab, and select a different option from the drop-down list.
Note: The measurement unit change only applies to the web interface and command line interface.
8. Click OK to save the changes.
Deleting a User Profile
Delete outdated or redundant user profiles when necessary.
To delete user profiles:
1. Choose User Management > Users. The Manage Users dialog appears.
2. Select the user you want to delete by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
3. Click Delete.
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. Choose User Management > User Preferences. The Setup User
Preferences dialog opens.
2. Update any of the following as needed:
 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.
Setting Up Default User Preferences (Units of Measure)
Default units of measure are applied to the EMX GUI across all users, including users accessing the device via LDAP. The preferences are also applied to the EMX device display.
These settings affect:
ï‚·
Preferences for newly created users
ï‚·
Units displayed on the LCD (EMX2-111 and EMX2-888 only)
ï‚·
Units reported in log messages, for example when sensor crosses a threshold
To set user preferences for just your EMX GUI and not across all users or on the device display, see
Setting Up User Preferences (Units of
Measure)
Note: Preferences can also be changed by administrators for specific users from the Preferences tab of the Manage Users dialog. See
Creating a User Profile
To setup up default user preferences:
1. Choose User Management > Default User Preferences.
2. Update any of the following as needed:
67
68
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.
Viewing Connected Users
You can see which users are connected to the EMX device and their status. If you have administrator privileges, you can terminate any user's connection to the EMX device.
To view connected users:
1. Choose Maintenance > Connected Users. The Connected Users dialog appears, showing a list of connected users with the following information:
Column
User Name
Description
The login name used by each connected user.
IP Address
Client Type
The IP address of each user's host.
For the login via a serial connection, <local> is displayed instead of an IP address.
The interface through which the user is being connected to the EMX.
 Web GUI: Refers to the EMX web interface.
 CLI: Refers to the command line interface (CLI).
The information in parentheses following "CLI" indicates how this user was connected to the CLI.
- Serial: Represents the local connection (serial or
USB).
- SSH: Represents the SSH connection.
- Telnet: Represents the Telnet connection.
The length of time for which a user remains idle. Idle Time
The unit "min" represents minutes.
2. To disconnect any user, click the corresponding Disconnect button. a. A dialog appears, prompting you to confirm the operation.
Managing Roles
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.
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.
The EMX is shipped with two built-in roles: Admin and Operator.
ï‚·
The Admin role provides full permissions. You can neither modify nor delete this role.
ï‚·
The Operator role provides limited permissions for frequently-used functions. You can modify or delete this role. By default, the Operator role contains these permissions:
 View Event Settings
 View Local Event Log
 Change Event Settings
 Change Own Password
 Change EMD Configuration
ï‚·
The Operator role is assigned to a newly created user profile by default. See
Creating a User Profile
Creating a Role
Create a new role when you need a new combination of permissions.
To create a role:
1. Choose User Management > Roles. The Manage Roles dialog appears.
Tip: You can also access the Manage Roles dialog by clicking the
Manage Roles button in the Edit User 'XXX' dialog.
2. Click New. The Create New Role dialog appears.
3. Type the role's name in the Role Name field.
4. Type a description for the role in the Description field.
5. Click the Privileges tab to assign one or multiple permissions.
69
70
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.
Now you can assign the new role to any users. See
Creating a User
Profile
Modifying a User Profile
Modifying a Role
You can change an existing role's settings except for the name.
To modify a role:
1. Choose User Management > Roles. The Manage Roles dialog appears.
Tip: You can also access the Manage Roles dialog by clicking the
Manage Roles button in the Edit User 'XXX' dialog.
2. Select the role you want to modify by clicking it.
3. Click Edit or double-click the role. The Edit Role 'XXX' dialog appears, where XXX is the role name.
Tip: You can also access the Edit Role 'XXX' dialog by clicking the
Edit Role button in the Edit User 'XXX' dialog.
4. Modify the text shown in the Description field if necessary.
5. To change the permissions, click the Privileges tab.
Note: You cannot change the Admin role's permissions.
6. To delete any permissions, do this: a. Select the permission you want to remove by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. b. Click Delete.
7. To add any permissions, do this: a. Click Add. The Add Privileges to Role 'XXX' dialog appears, where XXX is the role name. b. Select the permission you want from the Privileges list.
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. The "Edit arguments of privilege 'XXX'" dialog appears, where XXX is the privilege name.
Note: If the permission you selected does not contain any arguments, the Edit button is disabled.
c. Select the argument you want. You can make multiple selections. d. Click OK.
9. Click OK to save the changes.
Deleting a Role
You can delete any role other than the Admin role.
To delete a role:
1. Choose User Management > Roles. The Manage Roles dialog appears.
Tip: You can also access the Manage Roles dialog by clicking the
Manage Roles button in the Edit User 'XXX' dialog.
2. Select the role you want to delete by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
3. Click Delete.
4. A message appears, prompting you to confirm the operation. Click
Yes to confirm the deletion.
71
Chapter 5 EMX Device Management
In This Chapter
Naming the EMX Device ......................................................................... 72
Displaying the Device Information ........................................................... 73
Setting the Date and Time ....................................................................... 73
Specifying the Device Altitude ................................................................. 74
Changing the Measurement Units ........................................................... 75
Determining How to Display Tree Items .................................................. 76
Modifying the Network Configuration ...................................................... 78
Modifying the Network Service Settings .................................................. 84
Configuring the SMTP Settings ............................................................... 92
Setting Up an EMX Using Bulk Configuration ......................................... 94
Backup and Restore the EMX Device Settings ....................................... 96
Downloading Diagnostic Information ..................................................... 100
Resetting to Factory Defaults ................................................................ 102
Overview
Following is information on setting up and managing the EMX after the
EMX device is installed.
Optionally, if you have already installed and configured an EMX and are now configuring a different EMX, you can use the Bulk Configuration feature to make the configuration process easier. See
Setting Up an
EMX Using Bulk Configuration
Naming the EMX Device
The default name for an EMX device is EMX, which can be changed as needed.
To change the device name:
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
2. Click Setup on the Settings page. The EMX Setup dialog appears.
3. Type a new name in the Device Name field.
72
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.
Tab
Device Information
Asset Strips
Information shown
General device information, such as model name, serial number, firmware version, hardware revision, and so on.
Each asset sensor's ID, boot version, application version and protocol version.
3. Enlarge the dialog if necessary.
4. You can re-sort the list or change the columns displayed.
5. Click Close to quit the dialog.
Tip: The firmware version is also available by clicking the EMX folder in the EMX Explorer pane.
Setting the Date and Time
Set the internal clock on the EMX device manually, or link to a Network
Time Protocol (NTP) server and let it set the date and time for the EMX.
To set the date and time:
1. Choose Device Settings > Date/Time. The Configure Date/Time
Settings dialog appears.
2. In the Time Zone field, click the drop-down arrow, and select your time zone from the list.
3. If the daylight saving time applies to your time zone, verify the
Automatic Daylight Saving Time Adjustment checkbox is selected.
If the daylight saving time rules are not available for the selected time zone, the checkbox is not configurable.
4. Choose one of the methods to set the date and time:
73
74
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. You can enter the time by deleting existing numbers and typing new ones in the hour, minute and second fields, or clicking the arrows to adjust each number.
 To let an NTP server set the date and time, select the
"Synchronize with NTP Server" radio button. There are two ways to assign the NTP servers.
 To use the DHCP-assigned NTP servers, make sure the
"Always use the servers below and ignore DHCP-provided servers" checkbox is deselected. This method is usable only when either IPv4 or IPv6 DHCP is enabled.
 To use the NTP servers that are manually specified, select the "Always use the servers below and ignore DHCPprovided servers" checkbox, and specify the primary NTP server in the First Time Server field. A secondary NTP server is optional.
Note: If the EMX device's IP address is assigned through IPv4 or
IPv6 DHCP, the NTP servers can be automatically discovered. When this occurs, the data you entered in the fields of First and Second
Time Server will be overridden.
5. Click OK to save the changes.
Specifying the Device Altitude
You must specify the EMX device's altitude above sea level if a Raritan differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See
Altitude
Correction Factors
Altitude Correction Factors (EMX)
The default altitude measurement unit is meter. You can have the measurement unit vary between meter and foot according to user credentials. See
Changing the Measurement Units
To specify the altitude of the EMX device:
1. In left navigation panel, click the EMX folder. The Settings page opens.
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
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. Click OK to save the changes.
Changing the Measurement Units
By default, the following measurement units are applied to all data shown in the EMX web interface:
 Temperature: degrees in Celsius (
)
 Length or height: meters (m)
 Air pressure: pascal (pa)
The EMX web interface allows shows different measurement units based on user login name. That is, different users may see different measurement units displayed according to their preferences. The other alternatives for each measurement unit include:
 Temperature: degrees in Fahrenheit (
)
 Length or height: feet (ft)
 Air pressure: psi
Determine the desired measurement unit when creating user profiles.
See
Creating a User Profile
Setting Up User
Preferences
Setting Up User Preferences (Units of Measure)
Setting Up Default User Preferences
Up Default User Preferences (Units of Measure)
change the measurement unit setting, you must have the administrator privileges.
To set the preferred measurement units:
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. Click the Preferences tab.
75
76
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. To change the pressure unit, select the desired option in the
Pressure Unit field.
 Pascal: This option displays the pressure value in Pascals (Pa).
A Pascal is equal to one newton per square meter.
 psi: This option displays the pressure value in psi. Psi stands for pounds per square inch.
8. Click OK to save the changes.
Determining How to Display Tree Items
By default the EMX web interface displays connected devices in the tree only if there are devices physically connected to FEATURE and RS-485
(auxiliary) ports and displays nothing if no devices are connected.
The EMX web interface allows you to determine when and how to display icons for connected and disconnected devices in the tree.
How to Display Asset Sensors
There are two ways to display connected asset sensors in the tree of the web interface:
ï‚·
Asset sensors are displayed only when they are physically connected.
ï‚·
Asset sensors are always displayed no matter they are physically connected or not, but their icons change to indicate the connection status.
To determine how to display connected asset sensors:
1. Click the Feature Ports folder. The Feature Ports page opens in the right pane, listing all FEATURE ports.
2. Select the number of the port that you want to configure, and click
Setup. Or you can simply double-click that port number. The Feature
Port Setup dialog for the selected port appears.
3. In the Detection Mode field, select the way to display connected asset sensors.
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. If the connection of an asset sensor is detected on a specific Feature port, this icon is displayed on that port. If not detected, this icon appears instead. See
Determining How to Display
Tree Items
When the Pinned checkbox is selected, click the drop-down arrow to select the device type to be displayed. Select Asset Strip for asset sensors.
4. Click OK to save the changes.
In the tree, the icon, if present, is followed by the device name if available, device type and the port number.
How to Display LHX Heat Exchangers
There are two ways to display connected Schroff ® LHX heat exchangers in the tree of the web interface:
ï‚·
LHX heat exchangers are displayed only when they are physically connected.
ï‚·
LHX heat exchangers are always displayed no matter they are physically connected or not, but their icons change to indicate the connection status.
The EMX supports the LHX-20 and LHX-40 models.
Note: Schroff LHX Support must be enabled in order for the LHX to be displayed. See
Enabling and Disabling Schroff LHX Heat Exchanger
Support
To determine how to display connected LHX heat exchangers:
1. Click the Auxiliary Ports folder or the Feature Ports folder depending on which port you want to connect the sensor to.
2. Select the number of the port that you want to configure, and click
Setup. Or you can simply double-click that port number. The
Auxiliary Port Setup dialog for the selected port appears.
3. In the Detection Mode field, select the way to display connected LHX heat exchangers.
 Disabled: When applied, disables to port and nothing connected to the port is detected.
77
78
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
When the Pinned checkbox is selected, click the drop-down arrow to select the appropriate device type for this port: LHX 20 or LHX 40.
4. Click OK to save the changes.
In the tree, the icon, if present, is followed by the device name if available, device type and the port number or FEATURE port (if applicable).
Modifying the Network Configuration
The network settings you can change via the web interface include wired, wireless, IPv4 and/or IPv6 settings.
Modifying the Network Interface Settings
The EMX supports two types of network interfaces: wired and wireless.
You should configure the network interface settings according to the networking mode that applies. See
Connecting the EMX to Your
Network
Wired Network Settings
The LAN interface speed and duplex mode were set during the installation and configuration process. See
Initial Network
Configuration
By default, the LAN speed and duplex mode are set to "Auto"
(automatic), which works in nearly all scenarios. You can change them if there are special local requirements.
To modify the network interface settings:
1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. The Interface Settings tab should have been selected. If not, click the
Interface Settings tab.
3. In the Network Interface field, click the drop-down arrow, and select
Wired from the list.
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.
 Full: Data is transmitted in both directions simultaneously.
 Half: Data is transmitted in one direction (to or from the EMX device) at a time.
6. Click OK to save the changes.
Tip: You can check the LAN status in the Current State field, including the speed and duplex mode.
Wireless Network Settings
Wireless SSID, PSK and BSSID parameters were set during the installation and configuration process. See
Initial Network
Configuration
(on page 15). You can change them via the web
interface.
To modify the wireless interface settings:
1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. The Interface Settings tab should have been selected. If not, click the
Interface Settings tab.
3. In the Network Interface field, click the drop-down arrow, and select
Wireless from the list.
4. Check the Hardware State field to ensure that the EMX device has detected a wireless USB LAN adapter. If not, verify whether the USB
LAN adapter is firmly connected or whether it is supported. See
Connecting the EMX to Your Network
5. Type the name of the wireless access point (AP) in the SSID field.
6. If the BSSID is available, select the Force AP BSSID checkbox, and type the MAC address in the BSSID field.
Note: BSSID refers to the MAC address of an access point in the wireless network.
79
80
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
EAP - PEAP
A Pre-Shared Key is required for this option.
 In the Pre-Shared Key field, type the PSK string.
PEAP stands for Protected Extensible
Authentication Protocol.
The following authentication data is required:
 Inner Authentication: Only Microsoft's
Challenge Authentication Protocol Version 2
(MSCHAPv2) is supported, allowing authentication to databases that support
MSCHAPv2.
 Identity: Type your user name for EAP authentication.
 Password: Type your password for EAP authentication.
 CA Certificate: A third-party CA certificate must be provided for EAP authentication.
Click Browse to select a valid certificate file.
- To view the contents of the selected certificate file, click Show.
- If the selected certificate file is invalid, click
Remove. Then select a new file.
8. Click OK to save the changes.
Modifying the Network Settings
The EMX was configured for network connectivity during the installation and configuration process. See
Configuring the EMX
necessary, you can modify any network settings using the web interface.
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. The Network Configuration dialog appears.
2. Click the IP Protocol tab.
3. Select one checkbox according to the Internet protocol(s) you want to enable:
 IPv4 only: Enables IPv4 only on all interfaces. This is the default.
 IPv6 only: Enables IPv6 only on all interfaces.
 IPv4 and IPv6: Enables both IPv4 and IPv6 on all interfaces.
4. If you selected the "IPv4 and IPv6" checkbox in the previous step, you must determine which IP address is used when the DNS resolver returns both of IPv4 and IPv6 addresses.
 IPv4 Address: Use the IPv4 addresses returned by the DNS server.
 IPv6 Address: Use the IPv6 addresses returned by the DNS server.
5. Click OK to save the changes.
81
82
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
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.
Option Description
DHCP To auto-configure the EMX, select DHCP.
With DHCP selected, you can enter a preferred DHCP host name, which is optional. Type the host name in the
Preferred Hostname field.
The host name:
 Consists of alphanumeric characters and/or hyphens
 Cannot begin or end with a hyphen
 Cannot contain more than 63 characters
 Cannot contain punctuation marks, spaces, and other symbols
Note: If the Service
Select the "Specify DNS server manually" checkbox if necessary. Then type the address of the primary DNS server in the Primary DNS Server field. The secondary DNS server and DNS suffix are optional.
Static To manually assign an IP address, select Static, and enter the following information in the corresponding fields:
 IP address
 Netmask
 Gateway
 Primary DNS server
 Secondary DNS server (optional)
 DNS Suffix (optional)
4. Click OK to save the changes.
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
To modify the IPv6 settings:
1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. Click the IPv6 Settings tab.
3. In the IP Auto Configuration field, click the drop-down arrow, and select the desired option from the list.
Option Description
Automatic To auto-configure EMX, select Automatic.
With this option selected, you can enter a preferred host name, which is optional. Type the host name in the
Preferred Hostname field.
The host name:
 Consists of alphanumeric characters and/or hyphens
 Cannot begin or end with a hyphen
 Cannot contain more than 63 characters
 Cannot contain punctuation marks, spaces, and other symbols
Select the "Specify DNS server manually" checkbox if necessary. Then type the address of the primary DNS server in the Primary DNS Server field. The secondary
DNS server and DNS suffix are optional.
Static To manually assign an IP address, select Static, and enter the following information in the corresponding fields:
 IP address
 Gateway
 Primary DNS server
 Secondary DNS server (optional)
 DNS Suffix (optional)
4. Click OK to save the changes.
83
84
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.
Therefore, DNS server settings are important for LDAP authentication.
With appropriate DNS settings, the EMX can resolve the LDAP server's name to an IP address for establishing a connection. If the SSL
encryption is enabled, the DNS server settings become critical since only fully qualified domain name can be used for specifying the LDAP server.
For information on LDAP authentication, see
Setting Up LDAP
Authentication
Modifying the Network Service Settings
The EMX supports these network communication services: HTTPS,
HTTP, Telnet and SSH.
HTTPS and HTTP enable the access to the web interface, and Telnet and SSH enable the access to the
command line interface
Using the Command Line Interface
By default, SSH is enabled, Telnet is disabled, and all TCP ports for supported services are set to standard ports. You can change default settings if necessary.
Note: Telnet access is disabled by default because it communicates openly and is thus insecure.
In addition, the EMX also supports the SNMP protocol.
Changing the HTTP(S) Settings
HTTPS uses Secure Sockets Layer (SSL) technology to encrypt all traffic to and from the EMX device so it is a more secure protocol than HTTP.
By default, any access to the EMX device via HTTP is automatically redirected to HTTPS. See
Forcing HTTPS Encryption
To change the HTTP or HTTPS port settings:
1. Choose Device Settings > Network Services > HTTP. The HTTP
Settings dialog appears.
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. Additionally, you may need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule" is enabled and the trap destination has not been set yet. See
Event Rules and Actions
(on
You can enable or disable SNMP communication between an SNMP manager and the EMX device. By default, SNMP v1/v2c is enabled on the EMX so the EMX can communicate with an SNMP manager.
The EMX provides you with the ability to create SNMPv2c and SNMPv3
TRAP communications, or SNMPv2c and SNMPv3 INFORM communications.
SNMP TRAP communications capture and send information via SNMP, but no confirmation that the communication between the devices has succeeded is provided to the receiving device.
SNMP INFORM communications capture and send information via
SNMP, and an acknowledgment that the communication was received by the receiving device is provided. If the inform communication fails, it is resent. You can define the number of times and the intervals to resend the inform communication, or leave the defaults of five (5) resends in three (3) second intervals.
Note: SNMP INFORM communications may take up slightly more network resources than SNMP TRAP communications since there are additional communications between the devices, and due to additional network traffic created should the initial communication fail and another is sent.
Use SNMP TRAP rules if you do not need confirmation that the communication has succeeded, and if you need to conserve network resources. Use SNMP INFORM communications to ensure more reliable communications, and if network resources can be managed with the potential additional network traffic.
To configure the SNMP communication:
1. Choose Device Settings > Network Services > SNMP. The SNMP
Settings dialog appears.
2. Enter the destination information that applies to the trap types you are using.
85
86
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. Select the "enable" checkbox in the "SNMP v3" field to enable communication with an SNMP manager using SNMP v3 protocol.
Tip: You can permit or disallow a user to access the EMX via the
SNMP v3 protocol. See
Configuring Users for Encrypted SNMP v3
5. 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
6. Select the MIB to be downloaded. The SNMP MIB for your EMX is used by the SNMP manager.
Chapter 5: EMX Device Management
7. Click OK, or continue to the Notifications tab create SNMP TRAP or
INFORM communications.
87
Chapter 5: EMX Device Management
8. To create an SNMP TRAP or INFORM communication, open the
Notifications tab on the SNMP Settings dialog.
88
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. 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. In the Host fields, enter the IP address of the device(s) you want to access. This is the address to which notifications are sent by the
SNMP system agent. You can specify up to 3 SNMP destinations.
4. In the Port fields, enter the port number used to access the device(s).
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. For SNMP INFORM communications, leave the resend settings at their default or: a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. 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.
5. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings: a. Host name b. Port number c. User ID needed to access the host d. Select the host security level
89
90
Chapter 5: EMX Device Management
Security level
"noAuthNoPriv"
"authNoPriv"
"authPriv"
Description
Select this if no authorization or privacy protocols are needed.
ï‚·
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.
ï‚·
Select the authentication protocol - MD5 or
SHA
ï‚·
Enter the authentication passphrase and confirm the authentication passphrase
ï‚·
Select the Privacy Protocol - DES or AES
ï‚·
Enter the privacy passphrase and then confirm the privacy passphrase
ï‚·
Click OK
Changing the SSH Settings
You can enable or disable the SSH access to the command line interface, or change the default TCP port for the SSH service. In addition, you can decide to log in using either the password or the public key over the SSH connection.
To change the SSH service settings:
1. Choose Device Settings > Network Services > SSH. The SSH
Settings dialog appears.
2. To use a different port, type a new port number in the field. Valid range is 1 to 65535.
3. To enable the SSH application, select the Enable SSH checkbox. To disable it, deselect the checkbox.
4. To select a different authentication method, select one of the checkboxes.
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. See
Creating a User Profile
Changing the Telnet Settings
You can enable or disable the Telnet access to the command line interface, or change the default TCP port for the Telnet service.
To change the Telnet service settings:
1. Choose Device Settings > Network Services > Telnet. The Telnet
Settings dialog appears.
2. To use a different port, type a new port number in the field. Valid range is 1 to 65535.
3. To enable the Telnet application, select the Enable Telnet Access checkbox. To disable it, deselect the checkbox.
4. Click OK to save the changes.
91
92
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.
To enable Service Advertisement:
1. Click Device Settings > Network Services > Service Advertisement
2. Click "Yes" in the "Changing Service Advertisement" confirmation dialog box. The feature is enabled and the Service Advertisement checkbox is selected in the menu.
To disable Service Advertisement:
1. Click Device Settings > Network Services > Service Advertisement.
2. Click "No" in the "Changing Service Advertisement " confirmation dialog box. The feature is disabled and the Service Advertisement checkbox is deselected in the menu.
Configuring the SMTP Settings
The EMX can be configured to send alerts or event messages to a specific administrator by email. To do this, you have to configure the
SMTP settings and enter an IP address for your SMTP server and a sender's email address.
Note: See
Configuring Event Rules
" on page 131) for information on creating event rules to send email
notifications.
To set the SMTP server settings:
1. Choose Device Settings > SMTP Server. The SMTP Server Settings dialog appears.
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. The time is measured in minutes. The default is 2 minutes.
7. If your SMTP server requires password authentication, do this: a. Select the Server Requires Authentication checkbox. b. Type a user name in the User Name field. c. Type a password in the Password field.
8. Now that you have set the SMTP settings, you can test it to ensure it works properly. Do the following: a. Type the recipient's email address in the Recipient Email
Addresses field. Use a comma to separate multiple email addresses. b. Click Send Test Email.
9. Click OK to save the changes.
10. Check if the recipient(s) receives the email successfully.
93
94
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.
You must have the administrator privileges to save and copy the EMX configurations.
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.
This file does NOT contain device-specific information, including:
ï‚·
Device name
ï‚·
Network settings (IP address, gateway, netmask and so on)
ï‚·
Device logs
ï‚·
Environmental sensor names
ï‚·
Environmental sensor states and values
ï‚·
SSL Certificate
ï‚·
Asset management sensor names and rack unit names
ï‚·
SNMP name, location, and contact
ï‚·
Server monitor entries
Because the date and time settings are saved in the configuration file, users should exercise caution when distributing the configuration file to the EMX devices in a different time zone than the source device.
To save a configuration file:
1. Choose Maintenance > Bulk Configuration. The Bulk Configuration dialog appears.
2. Click Download Bulk Configuration.
3. When the web browser prompts you to open or save the configuration file, click Save. Choose a suitable location and save the configuration file to your PC.
The file is saved in the XML format, and its content is encrypted using the AES-128 encryption algorithm.
95
96
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.
ï‚·
The target EMX device must be running the same firmware version as the source EMX device.
To copy a EMX configuration:
1. Log in to the target device's web interface.
2. If the target device's firmware version does not match that of the source device, update the target's firmware. See
Firmware Upgrade
3. Choose Maintenance > Bulk Configuration. The Bulk Configuration dialog appears.
4. In the Copy Bulk Configuration section, click Browse and select the configuration file stored on your PC.
5. Click Upload & Restore Bulk Configuration to copy the file.
A message appears, prompting you to confirm the operation and enter the admin password.
6. Enter the admin password, then click Yes to confirm the operation.
7. Wait until the EMX device resets and the Login page re-appears, indicating that the configuration copy is complete.
Backup and Restore the EMX Device Settings
All EMX information is captured in the XML backup file except for the device logs and SSL certificate.
To download a backup EMX XML file:
1. Choose Maintenance > Backup/Restore. The Backup/Restore of
Device Settings dialog opens.
2. In the Save Device Settings section, click Download Device Settings.
Save the file to your computer.
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. Enter the admin password, then click Yes to confirm the operation.
5. Wait until the EMX device resets and the Login page re-appears, indicating that the restore is complete.
Firmware Upgrade
You may upgrade your EMX device to benefit from the latest enhancements, improvements and features.
The EMX firmware files are available on the Raritan website's
Firmware and Documentation section
(
http://www.raritan.com/support/firmware-and-documentation/
).
Updating the Firmware
You must be the system administrator or log in to the user profile with the
Firmware Update permission to update the EMX device's firmware.
If applicable to your model, download the latest firmware file from the
Raritan website, read the release notes, then start the upgrade. If you have any questions or concerns about the upgrade, contact Raritan
Technical Support BEFORE upgrading.
Warning: Do NOT perform the firmware upgrade over a wireless connection.
To update the firmware:
1. Choose Maintenance > Update Firmware. The Firmware Update dialog appears.
2. In the Firmware File field, click Browse to select an appropriate firmware file.
3. Click Upload. A progress bar appears to indicate the upload status.
4. When the upload is complete, version information of both the existing firmware and uploaded firmware is shown, providing you a last chance to terminate the update.
97
98
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.
 In the web interface, all logged-in users see the EMX time out message, and the "disconnected" state is shown in the status bar.
 The user management operation, if any, is forced to suspend.
7. When the update is complete, a message appears, indicating the update is successful.
8. The EMX device resets, and the Login page re-appears. You can now log in and resume your operation.
Note 1: The other logged-in users are also logged out when the firmware update is complete.
Note 2: If you are using the EMX with an SNMP manager, download the
EMX MIB again after the firmware update to ensure your SNMP manager has the correct MIB for the latest release you are using. See
Using SNMP in the EMX User Guide.
Viewing Firmware Update History
The firmware upgrade history, if available, is permanently stored on the
EMX device.
This history indicates when a firmware upgrade event occurred, the prior and new versions associated with the firmware upgrade event, and the upgrade result.
To view the firmware update history:
1. Choose Maintenance > View Firmware Update History. The
Firmware Update History dialog appears, with the following information displayed.
 Date and time of the firmware upgrade event
 Previous firmware version
 Update firmware version
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.
Full Disaster Recovery
If the firmware upgrade fails, causing the EMX device to stop working, you can recover it by using a special utility rather than returning the device to Raritan.
Contact Raritan Technical Support for the recovery utility, which works in
Windows XP/Vista/7 and Linux. In addition, an appropriate EMX firmware file is required in the recovery procedure.
Updating the Asset Sensor Firmware
After connecting the asset sensor to the EMX device, it automatically checks its own firmware version against the version of the asset sensor firmware stored in the EMX firmware. If two versions are different, the asset sensor automatically starts downloading the new firmware from the
EMX device to upgrade its own firmware.
During the firmware upgrade, the following events take place:
ï‚·
The asset sensor is completely lit up, with the blinking LEDs changing the color from red to green.
ï‚·
A firmware upgrade process is indicated in the EMX web interface.
ï‚·
An SNMP trap is sent to indicate the firmware upgrade event.
Network Diagnostics
The EMX provides the following tools in the web interface for diagnosing potential networking issues.
ï‚·
Ping
ï‚·
Trace Route
ï‚·
List TCP Connections
Tip: These network diagnostic tools are also available through CLI. See
Network Troubleshooting
99
100
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. This number determines how many packets are sent for pinging the host.
4. Click Run Ping to start pinging the host. A dialog appears, displaying the Ping results.
5. Click Close to quit the dialog.
Tracing the Network Route
Trace Route lets you find out the route over the network between two hosts or systems.
To trace the route for a host:
1. Choose Maintenance > Network Diagnostics > Trace Route. The
Trace Route to Host dialog appears.
2. Type the IP address or name of the host whose route you want to check in the Host Name field.
3. Click Run. A dialog appears, displaying the Trace Route results.
4. Click Close to quit the dialog.
Listing TCP Connections
You can use the "List TCP Connections" to display a list of TCP connections.
To trace the route for a host:
1. Choose Maintenance > Network Diagnostics > List TCP
Connections. The TCP connections dialog appears.
2. Click Close to quit the dialog.
Downloading Diagnostic Information
Important: This function is for use by Raritan Field Engineers or
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.
3. Navigate to the desired directory and click Save.
4. E-mail this file as instructed by Raritan Technical Support.
101
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.
102
2. Click Yes to reset the EMX.
3. A message appears with a countdown timer showing the remaining time of the operation. It takes about one minute to complete.
4. When the reset is complete, the Login page opens. Now you can log back in to the EMX device.
Note: If you are not redirected to the Login page after the reset is complete, click the underlined text "this link" in the message.
Resetting to Factory Defaults
For security reasons, the EMX device can be reset to factory defaults only at the local console.
Important: Exercise caution before resetting the EMX to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.
You can use either the reset button or the command line interface (CLI) to reset the EMX.
To reset to factory defaults using the reset button:
1. Connect a computer to the EMX device. See
Connecting the EMX to a Computer
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.
Note: HyperTerminal is available on Windows operating systems prior to
Windows Vista. For Windows Vista or later versions, you may use
PuTTY, which is a free program you can download from the Internet. See
PuTTY's documentation for details on configuration.
103
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
Access Security Control
The EMX provides tools to control access. You can require HTTPS encryption, enable the internal firewall and create firewall rules, and create login limitations.
Tip: You can also create and install the certificate or set up external authentication servers to control any access. See
Setting Up an SSL
Certificate
Setting Up LDAP Authentication
(on
Forcing HTTPS Encryption
HTTPS uses Secure Sockets Layer (SSL) technology to encrypt all traffic to and from the EMX device so it is a more secure protocol than HTTP.
You can force users to access the EMX web interface through the
HTTPS protocol only. By default, this protocol is enabled.
To force HTTPS access to the web interface:
1. Choose Device Settings > Security > Force HTTPS for Web Access.
2. A message appears, prompting you to confirm the operation. Click
Yes to enforce the HTTPS service.
3. Choose Device Settings > Security to verify the "Force HTTPS for
Web Access" checkbox is selected as shown in this diagram.
If the checkbox is not selected, repeat these steps.
After enabling the HTTPS protocol, all access attempts using HTTP are redirected to HTTPS automatically.
104
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
2. Set the default policy. See
Changing the Default Policy
(on page
3. Create firewall rules specifying which addresses to accept and which ones to discard. See
Creating Firewall Rules
Changes made to firewall rules take effect immediately. Any unauthorized IP activities cease instantly.
Note: The purpose of disabling the firewall by default is to prevent users from accidentally locking themselves out of the device.
Enabling the Firewall
The firewall rules, if any, take effect only after the firewall is enabled.
To enable the EMX firewall:
1. Choose Device Settings > Security > IP Access Control. The
Configure IP Access Control Settings dialog appears.
2. To enable the IPv4 firewall, click the IPv4 tab, and select the Enable
IPv4 Access Control checkbox.
3. To enable the IPv6 firewall, click the IPv6 tab, and select the Enable
IPv6 Access Control checkbox.
4. Click OK to save the changes.
Changing the Default Policy
After enabling the firewall, the default policy is to accept traffic from all IP addresses. This means only IP addresses discarded by a specific rule will NOT be permitted to access the EMX.
You can change the default policy to Drop or Reject, in which case traffic from all IP addresses is discarded except the IP addresses accepted by a specific rule.
To change the default policy:
1. Choose Device Settings > Security > IP Access Control. The
Configure IP Access Control Settings dialog appears.
2. To determine the default policy for IPv4 addresses:
105
106
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.
 Reject: Discards traffic from all IPv4 addresses, and an ICMP message is sent to the source host for failure notification.
3. To determine the default policy for IPv6 addresses: a. Click the IPv6 tab. b. Ensure the Enable IPv6 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 IPv6 addresses.
 Drop: Discards traffic from all IPv6 addresses, without sending any failure notification to the source host.
 Reject: Discards traffic from all IPv6 addresses, and an ICMP message is sent to the source host for failure notification.
4. Click OK to save the changes. The new default policy is applied.
Creating Firewall Rules
Firewall rules determine whether to accept or discard traffic intended for the EMX, based on the IP address of the host sending the traffic. When creating firewall rules, keep these principles in mind:
ï‚·
Rule order is important.
When traffic reaches the EMX device, the rules are executed in numerical order. Only the first rule that matches the IP address determines whether the traffic is accepted or discarded. Any subsequent rules matching the IP address are ignored by the EMX.
ï‚·
Subnet mask may be required.
When typing the IP address, you may or may not need to specify
BOTH the address and a subnet mask. The default subnet mask is
/32 (that is, 255.255.255.255). You must specify a subnet mask only when it is not the same as the default. For example, to specify a single address in a Class C network, use this format:
x.x.x.x/24 where /24 = a subnet mask of 255.255.255.0.
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. Ensure the Enable IPv4 Access Control checkbox is selected on the
IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Create specific rules. See the table for different operations.
Action
Add a rule to the end of the rules list
Procedure
 Click Append. The "Append 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).
 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.
 Click OK to save the changes.
The system automatically numbers the rule.
107
Chapter 6: Security
Action
Insert a rule between two existing rules
Procedure
 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).
 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.
 Click OK to save the changes.
The system inserts the rule and automatically renumbers the following rules.
5. When finished, the rules appear in the Configure IP Access Control
Settings dialog.
108
6. Click OK to save the changes. The rules are applied.
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. Ensure the Enable IPv4 Access Control checkbox is selected on the
IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Select the rule to be modified in the rules list.
5. Click Edit or double-click the rule. The Edit Rule dialog appears.
6. Make changes to the information shown.
7. Click OK to save the changes.
8. Click OK to quit the Configure IP Access Control Settings dialog, or the changes are lost.
Sorting Firewall Rules
The rule order determines which one of the rules matching the same IP address is performed.
To sort the firewall rules:
1. Choose Device Settings > Security > IP Access Control. The
Configure IP 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. Ensure the Enable IPv4 Access Control checkbox is selected on the
IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Select a specific rule by clicking it.
5. Click or to move the selected rule up or down until it reaches the desired location.
6. Click OK to save the changes.
109
110
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. Ensure the Enable IPv4 Access Control checkbox is selected on the
IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Select the rule that you want to delete. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
5. Click Delete.
6. A message appears, prompting you to confirm the operation. Click
Yes to remove the selected rule(s) from the rules list.
7. Click OK to save the changes.
Setting Up User Login Controls
You can set up login controls to make it more difficult for hackers to access the EMX and the devices connected to it. You can arrange to lock persons out after a specified number of failed logins, limit the number of persons who log in using the same user name at the same time, and force users to create strong passwords.
Enabling User Blocking
User blocking determines how many times a user can attempt to log in to the EMX and fail authentication before the user's login is blocked.
Note that this function applies only to local authentication instead of authentication through external AA servers.
Note: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command via a serial connection.
See
Unblocking a User
To enable user blocking:
1. Choose Device Settings > Security > Login Settings. The Login
Settings dialog appears.
2. Locate the User Blocking section.
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.
 Infinite: This option sets no time limit on blocking the login.
 X min: This type of option sets the time limit to X minutes, where
X is a number.
 X h: This type of option sets the time limit to X hours, where X is a number.
 1 d: This option sets the time limit to 1 day.
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.
6. Click OK to save the changes.
Enabling Login Limitations
Login limitations determine whether more than one person can use the same login name at the same time, and how long users are permitted to stay idle before being forced to log out.
To enable login limitations:
1. Choose Device Settings > Security > Login Settings. The Login
Settings dialog appears.
2. Locate the Login Limitations section.
3. To prevent more than one person from using the same login at the same time, select the "Prevent concurrent login with same username" checkbox.
4. To adjust how long users can remain idle before they are forcibly logged out by the EMX, select a time option in the Idle Timeout
Period field. The default is 10 minutes.
 X min: This type of option sets the time limit to X minutes, where
X is a number.
 X h: This type of option sets the time limit to X hours, where X is a number.
 1 d: This option sets the time limit to 1 day.
111
112
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.
Enabling Strong Passwords
Use of strong passwords makes it more difficult for intruders to crack user passwords and access the EMX device. By default, strong passwords should be at least eight characters long and contain upper- and lower-case letters, numbers, and special characters, such as @ or
&.
To force users to create strong passwords:
1. Choose Device Settings > Security > Password Policy. The
Password Policy dialog appears.
2. Select the Strong Passwords checkbox to activate the strong password feature. The following are the default settings:
Minimum length
Maximum length
At least one lowercase character
At least one uppercase character
= 8 characters
= 32 characters
= Required
= Required
At least one numeric character
At least one special character
= Required
= Required
Number of restricted passwords in history = 5
Note: The maximum password length accepted by the EMX is 32 characters.
3. Make necessary changes to the default settings.
4. Click OK to save the changes.
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. To determine how often users are requested to change their passwords, select a number of days in the Password Aging Interval field. Users are required to change their password every time that number of days has passed.
Tip: If the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "9 d" to set the password aging time to 9 days.
4. Click OK to save the changes.
Setting Up Role-Based Access Control Rules
Role-based access control rules are similar to firewall rules, except they are applied to members sharing a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.
To set up role-based access control rules:
1. Enable the feature. See
Enabling the Feature
2. Set the default policy. See
Changing the Default Policy
(on page
3. Create rules specifying which addresses to accept and which ones to discard when the addresses are associated with a specific role. See
Creating Role-Based Access Control Rules
Changes made do not affect users currently logged in until the next login.
Enabling the Feature
You must enable this access control feature before any relevant rule can take effect.
To enable role-based access control rules:
1. Choose Device Settings > Security > Role Based Access Control.
The Configure Role Based Access Control Settings dialog appears.
113
114
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. Choose Device Settings > Security > Role Based Access Control.
The Configure Role Based Access Control Settings dialog appears.
2. To determine the default policy for IPv4 addresses: a. Click the IPv4 tab if necessary. b. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected. c. Select the action you want from the Default Policy drop-down list.
 Allow: Accepts traffic from all IPv4 addresses regardless of the user's role.
 Deny: Drops traffic from all IPv4 addresses regardless of the user's role.
3. To determine the default policy for IPv6 addresses: a. Click the IPv6 tab. b. Ensure the Enable Role Based Access Control for IPv6 checkbox is selected. c. Select the action you want from the Default Policy drop-down list.
 Allow: Accepts traffic from all IPv6 addresses regardless of the user's role.
 Deny: Drops traffic from all IPv6 addresses regardless of the user's role.
4. Click OK to save the changes.
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. Click the IPv4 tab for creating firewall rules, or click the IPv6 tab for creating IPv6 firewall rules.
3. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Create specific rules:
Action
Add a rule to the end of the rules list
Do this...
 Click Append. The "Append new Rule" dialog appears.
 Type a starting IP address in the Starting IP Address field.
 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.
 Allow: Accepts traffic from the specified IP address range when the user is a member of the specified role
 Deny: Drops traffic from the specified IP address range when the user is a member of the specified role
 Click OK to save the changes.
Insert a rule between two existing rules
The system automatically numbers the rule.
 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 a starting IP address in the Starting IP Address field.
115
116
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.
 Allow: Accepts traffic from the specified IP address range when the user is a member of the specified role
 Deny: Drops traffic from the specified IP address range when the user is a member of the specified role
 Click OK to save the changes.
The system inserts the rule and automatically renumbers the following rules.
5. Click OK to save the changes.
Editing Role-Based Access Control Rules
You can modify existing rules when these rules do not meet your needs.
To modify a role-based access control rule:
1. Choose Device Settings > Security > Role Based Access Control.
The Configure Role Based 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. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Select the rule to be modified in the rules list.
5. Click Edit or double-click the rule. The Edit Rule dialog appears.
6. Make changes to the information shown.
7. Click OK to save the changes.
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. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Select a specific rule by clicking it.
5. Click or to move the selected rule up or down until it reaches the desired location.
6. Click OK to save the changes.
Deleting Role-Based Access Control Rules
When any access control rule becomes unnecessary or obsolete, remove it.
To delete a role-based access control rule:
1. Choose Device Settings > Security > Role Based Access Control.
The Configure Role Based 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. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Select the rule to be deleted in the rules list. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
5. Click Delete.
6. A message appears, prompting you to confirm the operation. Click
Yes to confirm the deletion.
7. Click OK to save the changes.
117
118
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.
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.
Note: See
Forcing HTTPS Encryption
(on page 104) for instructions on
forcing users to employ SSL when connecting to the EMX.
A CSR is not required in either of the following scenarios:
ï‚·
You decide to generate a self-signed certificate on the EMX device.
ï‚·
Appropriate, valid certificate and key files have been available.
Certificate Signing Request
When appropriate certificate and key files for the EMX are NOT available, one of the alternatives is to create a CSR and private key on the EMX device, and send the CSR to a CA for signing the certificate.
Creating a Certificate Signing Request
Follow this procedure to create the CSR for your EMX device.
To create a CSR:
1. Choose Device Settings > Security > SSL Certificate. The Manage
SSL Certificate dialog appears.
2. Click the New SSL Certificate tab.
3. Provide the information requested.
 In the Subject section:
Field Type this information
Country (ISO Code) The country where your company is located. Use the standard ISO country code. For a list of ISO codes, visit the
ISO website
(
http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm
).
State or Province
Locality
The full name of the state or province where your company is located.
The city where your company is located.
Chapter 6: Security
Field
Organization
Type this information
The registered name of your company.
Organizational Unit The name of your department.
Common Name
Email Address
The fully qualified domain name (FQDN) of your EMX device.
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. If you generate a CSR without values entered in the required fields, you cannot obtain third party certificates.
 In the Key Creation Parameters section:
Field
Key Length
Self Sign
Challenge
Do this
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.
For requesting a certificate signed by the CA, ensure this
checkbox is NOT selected.
Type a password. The password is used to protect the certificate or
CSR. This information is optional, and the value should be 4 to 64 characters long.
The password is case sensitive, so ensure you capitalize the letters correctly.
Confirm Challenge Type the same password again for confirmation.
4. Click Create New SSL Key to create both the CSR and private key.
This may take several minutes to complete.
5. To download the newly-created CSR to your computer, click
Download Certificate Signing Request. a. You are prompted to open or save the file. Click Save to save it on your computer. b. After the file is stored on your computer, submit it to a CA to obtain the digital certificate. c. If desired, click Delete Certificate Signing Request to remove the
CSR file permanently from the EMX device.
6. To store the newly-created private key on your computer, click
Download Key. You are prompted to open or save the file. Click
Save to save it on your computer.
7. Click Close to quit the dialog.
119
120
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.
Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab later.
5. Click Close to quit the dialog.
Creating a Self-Signed Certificate
When appropriate certificate and key files for the EMX device are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate.
To create and install a self-signed certificate:
1. Choose Device Settings > Security > SSL Certificate. The Manage
SSL Certificate dialog appears.
2. Click the New SSL Certificate tab.
3. Provide the information requested.
Field Type this information
Country (ISO Code) The country where your company is located. Use the standard ISO country code. For a list of ISO codes, visit the
ISO website
(
http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm
).
State or Province The full name of the state or province where your company is located.
Locality
Organization
The city where your company is located.
The registered name of your company.
Organizational Unit The name of your department.
Common Name
Email Address
The fully qualified domain name (FQDN) of your EMX device.
An email address where you or another administrative user can be reached.
Field
Key Length
Self Sign
Validity in days
Chapter 6: Security
Type this information
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.
Ensure this checkbox is selected, which indicates that you are
creating a self-signed certificate.
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.
Note: All fields in the Subject section are mandatory, except for the
Organization, Organizational Unit and Email Address fields.
A password is not required for a self-signed certificate so the
Challenge and Confirm Challenge fields disappear after the Self Sign checkbox is selected.
4. Click Create New SSL Key to create both the self-signed certificate and private key. This may take several minutes to complete.
5. You can also do any of the following:
 Click "Install Key and Certificate" to immediately install the selfsigned certificate and private key. When any confirmation and security messages appear, click Yes to continue.
Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab later.
 To download the self-signed certificate or private key, click
Download Certificate or Download Key. You are prompted to open or save the file. Click Save to save it on your computer.
 To remove the self-signed certificate and private key permanently from the EMX device, click "Delete Key and Certificate".
6. If you installed the self-signed certificate in Step 5, after the installation completes, the EMX device resets and the login page reopens.
121
122
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. Is this the right place for this note? Does this explain it well enough or is an example needed of what a SSL certificate chain is?
To install the existing key and certificate files:
1. Choose Device Settings > Security > SSL Certificate. The Manage
SSL Certificate dialog appears.
2. Click the New SSL Certificate tab.
3. Select the "Upload Key and Certificate" checkbox. The Key File and
Certificate File fields appear.
4. In the Key File field, click Browse to select the private key file.
5. In the Certificate File field, click Browse to select the certificate file.
6. Click Upload. The selected files are installed on the EMX device.
Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab later.
7. Click Close to quit the dialog.
Downloading Key and Certificate Files
You can download the key and certificate files currently installed on the
EMX device for backup or other operations. For example, you can install the files on a replacement EMX device, add the certificate to your browser and so on.
To download the certificate and key files from an EMX device:
1. Choose Device Settings > Security > SSL Certificate. The Manage
SSL Certificate dialog appears.
2. The Active SSL Certificate tab should open. If not, click it.
3. Click Download Key to download the private key file installed on the
EMX device. You are prompted to open or save the file. Click Save to save it on your computer.
4. Click Download Certificate to download the certificate file installed on the EMX device. You are prompted to open or save the file. Click
Save to save it on your computer.
5. Click Close to quit the dialog.
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. If you prefer to use an external LDAP server, you must:
ï‚·
Provide the EMX with information about the LDAP server.
ï‚·
Create user profiles for users who are authenticated externally because a user profile on the EMX device determines the role(s) applied to the user, and determines the permissions for the user accordingly.
When configured for LDAP authentication, all EMX users must have an account on the LDAP server. Local-authentication-only users will have no access to the EMX except for the admin, who always can access the
EMX.
Gathering the LDAP Information
It requires knowledge of your LDAP server and directory settings to configure the EMX for LDAP authentication. If you are not familiar with the settings, consult your LDAP administrator for help.
To configure LDAP authentication, you need to check:
ï‚·
The IP address or hostname of the LDAP server
ï‚·
Whether the Secure LDAP protocol (LDAP over SSL) is being used
 If Secure LDAP is in use, consult your LDAP administrator for the
CA certificate file.
ï‚·
The network port used by the LDAP server
ï‚·
The type of the LDAP server, usually one of the following options:
 OpenLDAP
 If using an OpenLDAP server, consult the LDAP administrator for the Bind Distinguished Name (DN) and password.
 Microsoft Active Directory
® (AD)
123
124
Chapter 6: Security
 If using a Microsoft Active Directory server, consult your AD administrator for the name of the Active Directory Domain.
ï‚·
Bind Distinguished Name (DN) and password (if anonymous bind is
NOT used)
ï‚·
The Base DN of the server (used for searching for users)
ï‚·
The login name attribute (or AuthorizationString)
ï‚·
The user entry object class
ï‚·
The user search subfilter (or BaseSearch)
Adding the LDAP Server Settings
To activate and use external LDAP/LDAPS server authentication, enable
LDAP authentication and enter the information you have gathered for any LDAP/LDAPS server.
Note: An LDAPS server refers to an SSL-secured LDAP server.
To add the LDAP/LDAPS server settings:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Select the LDAP radio button to activate remote LDAP/LDAPS server authentication.
3. Click New to add an LDAP/LDAPS server for authentication. The
"Create new LDAP Server Configuration" dialog appears.
4. IP Address / Hostname - Type the IP address or hostname of your
LDAP/LDAPS authentication server.
Important: Without the SSL encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the SSL encryption is enabled.
5. Type of external LDAP/LDAPS server. Choose from among the options available:
 OpenLDAP
 Microsoft Active Directory. Active Directory is an implementation of LDAP/LDAPS directory services by Microsoft for use in
Windows environments.
6. LDAP over SSL - Select this checkbox if you would like to use SSL.
Secure Sockets Layer (SSL) is a cryptographic protocol that allows the EMX to communicate securely with the LDAP/LDAPS server.
7. Port - The default Port is 389. Either use the standard LDAP TCP port or specify another port.
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. A certificate file is required after enabling this option.
10. Server Certificate - Consult your authentication server administrator to get the CA certificate file for the LDAP/LDAPS server. Use the
Browse button to navigate to the certificate file. This file is required when the "Use only trusted LDAP Server Certificates" checkbox is selected.
Tip: You can first upload the CA certificate file for a future use before selecting the "Use only trusted LDAP Server Certificates" checkbox, and then select the checkbox when you need to utilize the certificate file.
11. Anonymous Bind - For "OpenLDAP," use this checkbox to enable or disable anonymous bind.
 To use anonymous bind, select this checkbox.
 When a Bind DN and password are required to bind to the external LDAP/LDAPS server, deselect this checkbox.
12. Use Bind Credentials - For "Microsoft Active Directory," use this checkbox to enable or disable anonymous bind.
 To use anonymous bind, deselect this checkbox. By default it is deselected.
 When a Bind DN and password are required to bind to the external LDAP/LDAPS server, select this checkbox.
13. Bind DN - Specify the DN of the user who is permitted to search the
LDAP directory in the defined search base. This information is required only when the Use Bind Credentials checkbox is selected.
14. Bind Password and Confirm Bind Password - Enter the Bind password in the Bind Password field first and then the Confirm Bind
Password field. This information is required only when the Use Bind
Credentials checkbox is selected.
15. Base DN for Search - Enter the name you want to bind against the
LDAP/LDAPS (up to 31 characters), and where in the database to begin searching for the specified Base DN. An example Base Search value might be: cn=Users,dc=raritan,dc=com. Consult your authentication server administrator for the appropriate values to enter into these fields.
16. Type the following information in the corresponding fields. LDAP needs this information to verify user names and passwords.
125
126
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. To verify if the LDAP/LDAPS configuration is done correctly, you may click Test Connection to check whether the EMX can connect to the LDAP/LDAPS server successfully.
Tip: You can also do this by using the Test Connection button in the
Authentication Settings dialog.
19. Click OK to save the changes. The new LDAP server is listed in the
Authentication Settings dialog.
20. To add additional LDAP/LDAPS servers, repeat Steps 3 to 19.
21. Click OK to save the changes. The LDAP authentication is now in place.
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. To ensure proper synchronization, administrators should configure the EMX and the LDAP server to use the same NTP server.
More Information about AD Configuration
For more information about the LDAP configuration using Microsoft
Active Directory, see
LDAP Configuration Illustration
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.
Note: After successfully connecting to one LDAP/LDAPS server, the
EMX STOPS trying to access the remaining LDAP/LDAPS servers in the list regardless of the user authentication result.
To re-sort the LDAP server access list:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Select the LDAP/LDAPS server whose priority you want to change.
3. Click "Move up" or "Move down" until the selected server reaches the desired position in the list.
4. Click OK to save the changes.
Testing the LDAP Server Connection
You can test the connection to any LDAP/LDAPS server to verify the server accessibility or the validity of the authentication settings.
To test the connection to an LDAP/LDAPS server:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Select the LDAP/LDAPS server that you want to test.
3. Click Test Connection to start the connection test.
Editing the LDAP Server Settings
If the configuration on any LDAP/LDAPS server has been changed, such as the port number, bind DN and password, you must modify the
LDAP/LDAPS settings on the EMX device accordingly, or the authentication fails.
To modify the LDAP authentication configuration:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Select the LDAP/LDAPS server that you want to edit.
3. Click Edit. The Edit LDAP Server Configuration dialog appears.
4. Make necessary changes to the information shown.
127
128
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. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
3. Click Delete.
4. A message appears, prompting you to confirm the operation. Click
Yes to confirm the deletion.
5. Click OK to save the changes.
Disabling the LDAP Authentication
When the remote authentication service is disabled, the EMX authenticates users against the local database stored on the EMX device.
To disable the LDAP authentication service:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Select the Local Authentication radio button.
3. Click OK to save the changes.
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.
ï‚·
When the connection to every LDAP/LDAPS server fails, the EMX allows authentication against the local database.
To enable both authentication services:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Ensure the LDAP radio button has been selected.
3. Select the "Use Local Authentication if Remote Authentication service is not available" checkbox.
4. Click OK to save the changes.
Enabling and Editing the Security Banner (Restrictive Service Agreement
Banner)
Use the EMX restricted service agreement (security banner) if you want to require users to read and accept a security agreement when they log on to the EMX.
A default agreement is provided. You can edit or replace the default text as needed by typing directly in the security dialog or pasting text into it.
A maximum of 10,000 characters can be entered or pasted into the security banner.
If a user declines the agreement, they cannot log in. An event notifying you if a user has accepted or declined the agreement can be created.
See
Default Log Messages
To enable the service agreement:
1. Click Device Services > Security > Restricted Service Agreement
Banner. The Restricted Service Agreement Setup dialog opens.
2. Select the Enforce Restricted Service Agreement checkbox.
3. Edit the text or replace it as needed.
129
130
Chapter 6: Security
4. Click OK.
Chapter 7 Event Rules, Event Actions and
Application Logs
In This Chapter
Event Rules and Actions ....................................................................... 131
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. This event notification or reaction is an
"event rule."
The EMX is shipped with two built-in event rules, which cannot be deleted.
ï‚·
System Event Log Rule: This causes ANY event occurred to the
EMX to be recorded in the internal log. It is enabled by default.
ï‚·
System SNMP Notification Action: This causes SNMP traps or informs to be sent to specified IP addresses or hosts when ANY event occurs to the EMX. It is disabled by default.
If these two do not satisfy your needs, you can create additional rules to respond to different events.
Note: Internet Explorer
®
8 (IE8) does not use compiled JAVA script.
When using IE8 to create or change event rules, the CPU performance may be degraded, resulting in the appearance of the connection time out message. When this occurs, click Ignore to continue.
Components of an Event Rule
An event rule defines what the EMX does in certain situations and is composed of two parts:
ï‚·
Event: This is the situation where the EMX or part of it meets a certain condition. For example, the temperature sensor exceeds the warning threshold.
ï‚·
Action: This is the response to the event. For example, the EMX notifies the system administrator of the event and records the event in the log.
Note: Asset management sensor event rules must be recreated after an
EMX firmware upgrade.
131
132
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.
By default, the EMX provides two built-in event rules -- System Event
Log Rule and System SNMP Notification Action. If the built-in rules do not satisfy your needs, create new ones.
To create event rules:
1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. On the Rules tab, click New.
3. In the "Rule name" field, type a new name for identifying the rule.
The default name is New Rule <number>, where <number> is a sequential number.
4. Select the Enable checkbox to enable the SNMP notification feature.
5. Click Event to select an event for which you want to trigger an action.
A pull-down menu showing various types of events appears.
 Select the desired event type from the pull-down menu, and if a submenu appears, continue the navigation until the desired event is selected.
Note: The option <Any sub-event> refers to all events/items listed on the same submenu, <Any slot> refers to all slots, <Any server> refers to all servers, and <Any user> refers to all users.
6. According to the event you selected in the previous step, the "Trigger condition" field containing three radio buttons may or may not appear.
Chapter 7: Event Rules, Event Actions and Application Logs
Event types
Numeric sensor threshold-crossing events, or the occurrence of the selected event -- true or false
Radio buttons
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. This means the status of the described event transits from TRUE to FALSE.
 Both: The EMX takes the action both when the event occurs (asserts) and when the event condition disappears (deasserts).
ï‚·
For connection state for USB cascading and auxiliary/RS-485 devices, assertion is displayed as "connected" and deassertion as "disconnected"
Discrete (on/off) sensor state change
Available radio buttons include "Alarmed," "No longer alarmed" and "Both."
 Alarmed: The EMX takes the action only when the chosen sensor enters the alarmed state, that is, the abnormal state.
 No longer alarmed: The EMX takes the action only when the chosen sensor returns to normal.
 Both: The EMX takes the action both when the chosen sensor enters or quits the alarmed state.
Sensor availability Available radio buttons include "Unavailable,"
"Available" and "Both."
 Unavailable: The EMX takes the action only when the chosen sensor is NOT detected and becomes unavailable.
 Available: The EMX takes the action only when the chosen sensor is detected and becomes available.
 Both: The EMX takes the action both when the chosen sensor becomes unavailable or available.
133
134
Chapter 7: Event Rules, Event Actions and Application Logs
Event types
Network interface link state
Function enabled or disabled
Available radio buttons include "Enabled,"
"Disabled" and "Both."
 Enabled: The EMX takes the action only when the chosen function is enabled.
 Disabled: The EMX takes the action only when the chosen function is disabled.
 Both: The EMX takes the action when the chosen function is either enabled or disabled.
User logon state
Radio buttons
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.
Server monitoring event
Available radio buttons include "Logged in,"
"Logged out," and "Both."
 Logged in: The EMX takes the action only when the selected user logs in.
 Logged out: The EMX takes the action only when the selected user logs out.
 Both: The EMX takes the action both when the selected user logs in and logs out.
Available radio buttons include "Monitoring started," "Monitoring stopped," and "Both."
 Monitoring started: The EMX takes the action only when the monitoring of any specified server starts.
 Monitoring stopped: The EMX takes the action only when the monitoring of any specified server stops.
 Both: The EMX takes the action when the monitoring of any specified server starts or stops.
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. From the Available Actions box, select the actions to be taken when the event occurs. Use the Add arrow to add the action to the
Selected Actions box.
If none of the existing actions accommodate the event rule you are creating, click Create New Action to create a new action. See
Creating Actions
(on page 136) for details on creating an action.
To add additional actions, repeat Step 7. Remove actions by selecting them in the Selected Actions box and clicking the Remove arrow.
2. Click Save to save the new event rule.
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.
3. Repeat Steps 2 to 10 to create additional event rules.
4. Click Close to quit the dialog.
Note: Asset management sensor event rules must be recreated after an
EMX firmware upgrade.
135
136
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.
Note: No IP addresses are specified for the "System SNMP Notification
Action" by default so you must specify IP addresses before applying this action to any event rule.
The default actions cannot be deleted.
SNMP traps and informs can be created for an action. See
Configuring the SNMP Settings, Traps and Informs
information on traps and informs.
Executing an Action Group
This option allows you to select the action or actions performed when an event is triggered. When more than one action is selected, all actions are performed with the is event triggered.
Note: A supported modem, such as the Cinterion
®
GSM MC52i modem, must be plugged in to the EMX in order to send SMS messges.
To create a action group:
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 <number>, where <number> 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 an action from the Available Actions box, then click the Add arrow to add to the Used Actions box. All actions in the Used Actions box are executed when the event is triggered.
7. Click OK to save the new action.
8. Click Close to quit the dialog.
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 <number>, where <number> 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. Click OK to save the new action.
7. Click Close to quit the dialog.
Send a Snapshot via Email
This option notifies one or multiple persons of the selected events by emailing snapshots or videos captured by a connected Logitech
® webcam.
To create a send snapshot via email action:
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 <number>, where <number> 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. 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.
8. To use a different SMTP server, select the Use Custom SMTP
Settings checkbox. If the SMTP server settings are not configured yet, click Configure. See
Configuring the SMTP Settings
(on page
92) for the information of each field.
9. Select the webcam that is capturing the images you want sent in the email.
137
138
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.
 "Time before first Snapshot (s):" - the amount of time (in seconds) between when the event is triggered and the webcam begins taking snapshots.
 "Time between Snapshots (s):" - the amount of time between when each snapshot is taken.
11. Click OK to save the new action.
12. Click Close to quit the dialog.
Send EMail
You can configure emails to be sent when an event occurs and can customize the message.
Messages consist of a combination of free text and EMX placeholders.
The placeholders represent information is pulled from the EMX and inserted into the message.
For example:
[USERNAME] logged into the device on [TIMESTAMP] translates to
JQPublic logged into the device on 2012-January-30
21:00
See
Email and SMS Message Placeholders
and definition of available variables.
To configure sending emails:
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 <number>, where <number> 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.
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.
See
Configuring the SMTP Settings
information of each field. Default messages are sent based on the event. See
Default Log Messages
(on page 148) for a list of default
log messages and events that trigger them.
8. If needed, select the Use Custom Log Message checkbox, and then create a custom message in the provided field.
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
details.
9. Click OK to save the new action.
10. Click Close to quit the dialog.
Send an SNMP Notification
This option sends an SNMP notification to one or multiple SNMP destinations.
To configure sending an SNMP notification:
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 <number>, where <number> 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 the type of SNMP notification. See either procedure below according to your selection.
To send SNMP v2c notifications:
1. From the Notification Type drop-down, select SNMP v2c Trap or
SNMP v2c Inform.
2. For SNMP INFORM communications, leave the resend settings at their default or:
139
140
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. In the Host fields, enter the IP address of the device(s) you want to access. This is the address to which notifications are sent by the
SNMP system agent.
4. In the Port fields, enter the port number used to access the device(s).
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.
To send SNMP v3 notifications:
1. From the Notification Type drop-down, select SNMP v3 Trap or
SNMP v3 Inform.
2. For SNMP TRAPs, the engine ID is prepopulated.
3. For SNMP INFORM communications, leave the resend settings at their default or: a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. 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.
4. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings: a. Host name b. Port number c. User ID needed to access the host d. Select the host security level
Chapter 7: Event Rules, Event Actions and Application Logs
Security level
"noAuthNoPriv"
"authNoPriv"
"authPriv"
Description
Select this if no authorization or privacy protocols are needed.
ï‚·
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.
ï‚·
Select the authentication protocol - MD5 or
SHA
ï‚·
Enter the authentication passphrase and confirm the authentication passphrase
ï‚·
Select the Privacy Protocol - DES or AES
ï‚·
Enter the privacy passphrase and then confirm the privacy passphrase
ï‚·
Click OK
Syslog Message
Use this action automatically forward event messages to the specified syslog server.
To configure a syslog message action:
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 <number>, where <number> 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. In the "Syslog server" field, specify the IP address to which the syslog is forwarded.
141
142
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.
A supported modem, such as the Cinterion ® GSM MC52i modem, must be plugged in to the EMX in order to send SMS messges.
Note: The EMX cannot receive SMS messages.
For example:
[USERNAME] logged into the device on [TIMESTAMP] translates to
JQPublic logged into the device on 2012-January-30
21:00
See
Email and SMS Message Placeholders
and definition of available variables.
To configure SMS 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 <number>, where <number> 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. In the Recipients Phone Number field, specify the phone number(s) of the recipient(s). Use a comma to separate multiple phone numbers.
7. Select the Use Custom Log Message checkbox, then create a custom message in the provided field.
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
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. See
Schroff
LHX Heat Exchangers
Use this action to switch the LHX on or off when, for example, temperature thresholds are reached.
To create a switch LHX action:
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 <number>, where <number> 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. From the Option drop-down, select Turn LHX On or Turn LHX Off.
7. From the available LHXs box, click on the LHX to be turned on or off, then click the Add arrow to add to the Switched LHXs box. Use the
Remove arrow to remove the LHX from the list, thereby removing the action.
8. Click Close to quit the dialog.
9. Click OK to save the new action.
Record Snapshots to Webcam Storage
This option allows you to define an action that starts or stops a specific webcam from taking snapshots.
To configure a record snapshot to webcame storage action:
1. Choose Device Settings > Event Rules. The Event Rules Settings dialog opens.
2. Click the Actions tab.
143
144
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 <number>, where <number> 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. Use the slide bar to specify the total number of snapshots to be taken when the event occurs. The maximum amount of snapshots that can be stored on the EMX is ten (10). If you set it for a number greater than ten, after the tenth snapshot is taken and stored, the oldest snapshots are overwritten.
9. In the "Time before first Snapshot (s):" field, use the slide bar or enter the amount of time (in seconds) between when the event is triggered and the webcam begins taking snapshots.
10. In the "Time between Snapshots (s):" field, use the slide bar or enter the amount of time between when each snapshot is taken.
11. Click OK to save the new action.
12. Click Close to quit the dialog.
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.
Placeholder
[AMSBLADEOVERFLOW]
Description
The asset strip overflow indicator
[AMSBLADESIZE] The slot count of a blade extension
[AMSBLADESLOTNUMBER] The numeric index of a blade slot
[AMSBLADESLOTPOSITION] The (horizontal) slot position, an action applies to
[AMSCOMPONENTCOUNT] The number of components, a composite asset strip consists of
[AMSLEDCOLOR]
[AMSLEDMODE]
[AMSLEDOPMODE]
[AMSNAME]
[AMSNUMBER]
The RGB LED color
The LED indication mode
The LED operating mode
The name of an asset strip
The numeric ID of an asset strip
[AMSOLDCOMPONENTCOU
NT]
The number of components, a composite asset strip consisted of
[AMSRACKUNITNUMBER] The numeric index of a rack unit
[AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to
[AMSSTATE]
[AMSTAGID]
The human readable state of an asset strip
The asset tag ID
[CONFIGPARAM]
The name of a configuration parameter
[CONFIGPARAMID] The ID of a configuration parameter
145
146
Chapter 7: Event Rules, Event Actions and Application Logs
Placeholder
[CONFIGVALUE]
[DATETIME]
[DEVICEIP]
[DEVICENAME]
[EXTSENSORCHANNEL]
[EXTSENSORNAME]
[EXTSENSORSERIAL
[EXTSENSORSLOT]
[EXTSENSORSUBTYPE]
[IFNAME]
[INLETPOLE]
[INLETSENSOR]
[ISASSERTED]
[LDAPERRORDESC]
[LHXERRORCODE
[LHXFANID]
[LHXGWOLDOPSTATE]
[LHXGWOPSTATE]
[LHXGWSENSORID]
[LHXGWSENSORTYPEID]
[LHXPOWERSUPPLYID]
[LHXSENSORID]
Description
The new value of a parameter
The human readable timestamp of the event occurrence
The IP address of the device, the event occurred on.
The name of the device, the event occurred on
The channel of an external sensor (e.g. contact closure)
The name of an external sensor
The serial number of an external sensor
The ID of an external sensor slot
The subtype of an external contact closure sensor
The human readable name of an network interface
The inlet power line identifier
The inlet sensor name
Boolean flag whether an event condition was entered (1) or left (0)
An LDAP error occurred
The error code supplied by an LHX
The ID of a fan connected to an LHX
The recent operational state of an LHX
The present operational state of an LHX
The 0-based sensor index
The sensor type ID derived from LHX-MIB
The ID of an LHX power supply
The ID of an LHX sensor probe
Chapter 7: Event Rules, Event Actions and Application Logs
Placeholder
[LHXSUPPORTENABLED]
[MONITOREDHOST]
[OLDSENSORSTATE]
[OLDVERSION]
[OUTLETPOLE]
[OUTLETSENSOR]
[PDUPOLESENSOR]
[PLSENSOR]
[PLSENSORNAME]
[PORTID]
[PORTTYPE]
[RACKSLOT]
[SENSORINTVALUE]
[SENSORREADING]
[SENSORREADINGUNIT]
[SENSORSTATE]
[SENSORTYPE]
[SERVER]
[SMTPRECIPIENTS]
[SMTPSERVER]
[TIMESTAMP]
[TYPEDPORTID]
[UMTARGETROLE]
Description
The Schroff LHX Support state
The name or IP address of a monitored host
The numeric ID of the previous sensor state
The firmware version the device is being upgraded from
The outlet power line identifier
The outlet sensor name
The sensor name for a certain power line
The Power Logic Device sensor id
The Power Logic Device sensor name
The label of the external port, the event triggering device is connected to
The type of the external port (for example,
'feature' or 'auxiliary', the event triggering device is connected to)
The (horizontal) slot position, an action applies to
The integer value of a sensor reading or state
The value of a sensor reading
The unit of a sensor reading
The numeric ID of the current sensor state
The type of a sensor
The name or IP address of a server
The list of recipients, an SMTP message was sent to
The name or IP address of an SMTP server
The timestamp of the event occurance
The port id with type prefix ('A' for auxiliary,
'F' for feature)
The name of a user management role, an action was applied on
147
148
Chapter 7: Event Rules, Event Actions and Application Logs
Placeholder
[UMTARGETUSER]
[USERIP]
[USERNAME]
[VERSION]
[WIRESENSOR]
Description
The user, an action was triggered for
The IP address, a user connected from
The user who triggered an action
The firmware version the device is upgrading to
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). See
Event Rules and Actions
information configuring email messages to be sent when specified events occur.
Event/Context
Device > System started
Device > System reset
Device > Firmware validation failed
Device > Firmware update started
Device > Firmware update completed
Device > Firmware update failed
Device > Device identification changed
Default Assertion Message when the Event = TRUE
System started.
System reset performed by user
'[USERNAME]' from host '[USERIP]'.
Firmware validation failed by user
'[USERNAME]' from host '[USERIP]'.
Firmware upgrade started from version
'[OLDVERSION]' to version
'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Firmware upgraded successfully from version '[OLDVERSION]' to version
'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Firmware upgrade failed from version
'[OLDVERSION]' to version
'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Config parameter '[PARAMETER]' changed to '[VALUE]' by user
'[USERNAME]' from host '[USERIP]'.
Default Assertion Message when the Event = FALSE*
Chapter 7: Event Rules, Event Actions and Application Logs
Event/Context
Device > Event log cleared
Device > Bulk configuration saved
Device > Bulk configuration copied
Default Assertion Message when the Event = TRUE
Event log cleared by user
'[USERNAME]' from host '[USERIP]'.
Bulk configuration saved from host
'[USERIP]'.
Bulk configuration copied from host
'[USERIP]'.
Default Assertion Message when the Event = FALSE*
Device > Network interface link state is up
Device > Sending SMTP message failed
Device > An LDAP error occured
The [IFNAME] network interface link is now up.
The [IFNAME] network interface link is now down.
Sending SMTP message to
'[RECIPIENTS]' using server
'[SERVER]' failed.
An LDAP error occured:
[LDAPERRORDESC].
Device > USB slave connected USB slave connected.
Device > Features > Schroff
LHX Support
Schroff LHX support enabled.
USB slave disconnected.
Schroff LHX support disabled.
User Administration > User added
User Administration > User modified
User Administration > User deleted
User '[TARGETUSER]' deleted by user
'[USERNAME]' from host '[USERIP]'.
User Administration > Password changed
Password of user '[TARGETUSER]' changed by user '[USERNAME]' from host '[USERIP]'.
User Administration > Password settings changed
Password settings changed by user
'[USERNAME]' from host '[USERIP]'.
User Administration > Role added
User Administration > Role modified
User '[TARGETUSER]' added by user
'[USERNAME]' from host '[USERIP]'.
User '[TARGETUSER]' modified by user '[USERNAME]' from host
'[USERIP]'.
Role '[TARGETROLE]' added by user
'[USERNAME]' from host '[USERIP]'.
Role '[TARGETROLE]' modified by user '[USERNAME]' from host
'[USERIP]'.
User Administration > Role deleted
User Activity > * > User accepted the Restricted Service
Agreement
Role '[TARGETROLE]' deleted by user
'[USERNAME]' from host '[USERIP]'.
Restricted Service Agreement accepted by [USERNAME]
Restricted Service Agreement declined by [USERNAME]
User Activity > * > User logged User '[USERNAME]' from host User '[USERNAME]' from host
149
150
Chapter 7: Event Rules, Event Actions and Application Logs
Event/Context Default Assertion Message when the Event = TRUE
'[USERIP]' logged in. in
User Activity > * >
Authentication failure
Authentication failed for user
'[USERNAME]' from host '[USERIP]'.
User Activity > * > User blocked User '[USERNAME]' from host
'[USERIP]' was blocked.
User Activity > * > Session timeout
Overcurrent Protector > * >
Sensor > * > Unavailable
External Sensor Slot > * >
Numeric Sensor > Unavailable
Session of user '[USERNAME]' from host '[USERIP]' timed out.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' unavailable.
Default Assertion Message when the Event = FALSE*
'[USERIP]' logged out.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' available.
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' unavailable.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' available.
External Sensor Slot > * >
Numeric Sensor > Above upper critical threshold
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted
'above upper critical'.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'above upper critical'.
External Sensor Slot > * >
Numeric Sensor > Above upper warning threshold
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted
'above upper warning'.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'above upper warning'.
External Sensor Slot > * >
Numeric Sensor > Below lower warning threshold
External Sensor Slot > * >
Numeric Sensor > Below lower critical threshold
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted
'below lower warning'.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'below lower warning'.
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted
'below lower critical'.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'below lower critical'.
External Sensor Slot > * > State
Sensor > Unavailable
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' unavailable.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' available.
External Sensor Slot > * > State
Sensor > Closed
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is closed.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' is open.
External Sensor Slot > * > State
Sensor > On
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is on.
External sensor
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' is off.
External Sensor Slot > * > State
Sensor > Alarmed
External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is
External sensor
'[EXTSENSORNAME]' in slot
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 Monitoring > * >
Unreachable
Asset Management > State
Asset Management > Rack Unit
> * > Tag Connected
Server '[SERVER]' is now being monitored.
Server '[SERVER]' is unreachable.
State of asset strip [STRIPID]
('[STRIPNAME]') changed to
'[STATE]'.
Asset tag with ID '[TAGID]' connected at rack unit [RACKUNIT], slot
[RACKSLOT] of asset strip [STRIPID]
('[STRIPNAME]').
Server '[SERVER]' is no longer being monitored.
Server '[SERVER]' is reachable.
Asset Management > Rack Unit
> * > Blade Extension
Connected
Blade extension with ID '[TAGID]' connected at rack unit [RACKUNIT] of asset strip [STRIPID]
('[STRIPNAME]').
Blade extension with ID '[TAGID]' disconnected at rack unit
[RACKUNIT] of asset strip
[STRIPID] ('[STRIPNAME]').
Asset Management > Firmware
Update
Firmware update for asset strip
[STRIPID] ('[STRIPNAME]'): status changed to '[STATE]'.
Asset tag with ID '[TAGID]' disconnected at rack unit
[RACKUNIT], slot [RACKSLOT] of asset strip [STRIPID]
('[STRIPNAME]').
Asset Management > Device
Config Changed
Config parameter '[PARAMETER]' of asset strip [STRIPID] ('[STRIPNAME]') changed to '[VALUE]' by user
'[USERNAME]'.
Asset Management > Rack Unit
Config Changed
Config of rack unit [RACKUNIT] of asset strip [STRIPID] ('[STRIPNAME]') changed by user '[USERNAME]' to:
LED Operation Mode '[LEDOPMODE]',
LED Color '[LEDCOLOR]', LED Mode
'[LEDMODE]'
Asset Management > Blade
Extension Overflow
Blade extension overflow occured on strip [STRIPID] ('[STRIPNAME]').
Blade extension overflow cleared for strip [STRIPID]
('[STRIPNAME]').
Asset Management >
Composite Asset Strip
Composition Changed
Composition changed on composite asset strip [STRIPID]
('[STRIPNAME]').
LHX > Auxiliary Port 2 >
Connected
LHX > Auxiliary Port 2 >
Operational State
LHX has been connected to
[PORTTYPE] port [PORTID].
LHX connected to [PORTTYPE] port
[PORTID] has been switched on.
LHX has been disconnected from
[PORTTYPE] port [PORTID].
LHX connected to [PORTTYPE] port [PORTID] has been switched off.
151
152
Chapter 7: Event Rules, Event Actions and Application Logs
Event/Context
LHX > Sensor > Unavailable
Default Assertion Message when the Event = TRUE
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' unavailable.
Default Assertion Message when the Event = FALSE*
Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' available.
LHX > Sensor > Auxiliary Port 2
> Above upper critical threshold
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'above upper critical'.
Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'above upper critical'.
LHX > Sensor > Auxiliary Port 2
> Above upper warning threshold
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'above upper warning'.
Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'above upper warning'.
LHX > Sensor > Auxiliary Port 2
> Below lower warning threshold
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'below lower warning'.
Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'below lower warning'.
LHX > Sensor > Auxiliary Port 2
>Auxiliary Port 2 > Below lower critical threshold
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'below lower critical'.
Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'below lower critical'.
LHX > Emergency Cooling >
Auxiliary Port 2
LHX > Maximum cooling request > Auxiliary Port 2
Emergency cooling on LHX at
[PORTTYPE] port '[PORTID]' was activated.
Maximum cooling was requested for
LHX at [PORTTYPE] port '[PORTID]'.
Emergency cooling on LHX at
[PORTTYPE] port '[PORTID]' was deactivated.
LHX > Parameter Data Loss >
Auxiliary Port 2
Data loss in parameter memory was detected on LHX at [PORTTYPE] port
'[PORTID]'.
Maximum cooling is not any more requested for LHX at
[PORTTYPE] port '[PORTID]'.
LHX > ST-Bus Communication
Error > Auxiliary Port 2
LHX > Collective fault >
Auxiliary Port 2
LHX > Auxiliary Port 2 > Door
Contact
LHX > Sensor Failure Auxiliary
Port 2 > Sensor
An ST-Bus communication error was detected on LHX at [PORTTYPE] port
'[PORTID]'.
A collective fault occurred on LHX at
[PORTTYPE] port '[PORTID]'.
The door of LHX at [PORTTYPE] port
'[PORTID]' was opened.
A sensor failure (broken or short circuit) occurred on LHX at
[PORTTYPE] port '[PORTID]' at sensor '[LHXSENSORID]'.
The door of LHX at [PORTTYPE] port '[PORTID]' was closed.
LHX > Fan Failure > Auxiliary
Port 2 > LHX fan
LHX > Power Supply Failure
A fan motor failure occurred on LHX at
[PORTTYPE] port '[PORTID]' at fan
'[LHXFANID]'.
A power supply failure occurred on
Chapter 7: Event Rules, Event Actions and Application Logs
Event/Context Default Assertion Message when the Event = TRUE
Auxiliary Port 2 > Power supply LHX at [PORTTYPE] port '[PORTID]' at power supply
'[LHXPOWERSUPPLYID]'.
LHX > Threshold Humidity
Auxiliary Port 2
LHX > External Water Cooling
Failure > Auxiliary Port 2
LHX > Water Leak > Auxiliary
Port 2
Power Logic Device > * >
Connected
The humidity threshold on LHX at
[PORTTYPE] port '[PORTID]' was crossed.
An external water cooling failure occurred on LHX at [PORTTYPE] port
'[PORTID]'.
Water leakage was detected on LHX at [PORTTYPE] port '[PORTID]'.
PowerLogic Device has been connected to [PORTTYPE] port
[PORTID].
Default Assertion Message when the Event = FALSE*
The humidity on LHX at
[PORTTYPE] port '[PORTID]' is within thresholds.
PowerLogic Device has been disconnected from [PORTTYPE] port [PORTID].
Power Logic Device > * > Alarm PowerLogic Device connected to
[PORTTYPE] port [PORTID] entered an alarm condition.
Power Logic Device > * >
Sensor > * > Unavailable
Sensor '[PLSENSORNAME]' on Power
Logic Device at [PORTTYPE] port
'[PORTID]' unavailable.
PowerLogic Device connected to
[PORTTYPE] port [PORTID] left an alarm condition.
Sensor '[PLSENSORNAME]' on
Power Logic Device at
[PORTTYPE] port '[PORTID]' available.
Power Logic Device > * >
Sensor > * > Above upper critical threshold
Power Logic Device > * >
Sensor > * > Above upper warning threshold
Sensor '[PLSENSORNAME]' on Power
Logic Device at [PORTTYPE] port
'[PORTID]' asserted 'above upper critical' at [SENSORREADING]
[SENSORREADINGUNIT].
Sensor '[PLSENSORNAME]' on
Power Logic Device at
[PORTTYPE] port '[PORTID]' deasserted 'above upper critical' at [SENSORREADING]
[SENSORREADINGUNIT].
Sensor '[PLSENSORNAME]' on Power
Logic Device at [PORTTYPE] port
'[PORTID]' asserted 'above upper warning' at [SENSORREADING]
[SENSORREADINGUNIT].
Sensor '[PLSENSORNAME]' on
Power Logic Device at
[PORTTYPE] port '[PORTID]' deasserted 'above upper warning' at [SENSORREADING]
[SENSORREADINGUNIT].
Power Logic Device > * >
Sensor > * > Below lower warning threshold
Sensor '[PLSENSORNAME]' on Power
Logic Device at [PORTTYPE] port
'[PORTID]' asserted 'below lower warning' at [SENSORREADING]
[SENSORREADINGUNIT].
Sensor '[PLSENSORNAME]' on
Power Logic Device at
[PORTTYPE] port '[PORTID]' deasserted 'below lower warning' at [SENSORREADING]
[SENSORREADINGUNIT].
153
154
Chapter 7: Event Rules, Event Actions and Application Logs
Event/Context
Power Logic Device > * >
Sensor > * > Below lower critical threshold
Default Assertion Message when the Event = TRUE
Default Assertion Message when the Event = FALSE*
Sensor '[PLSENSORNAME]' on Power
Logic Device at [PORTTYPE] port
'[PORTID]' asserted 'below lower critical' at [SENSORREADING]
[SENSORREADINGUNIT].
Sensor '[PLSENSORNAME]' on
Power Logic Device at
[PORTTYPE] port '[PORTID]' deasserted 'below lower critical' at
[SENSORREADING]
[SENSORREADINGUNIT]."))
User Activity > * > User accepted the Restricted Service
Agreement
User '[USERNAME]' from host
'[USERIP]' accepted the Restricted
Service Agreement.
User '[USERNAME]' from host
'[USERIP]' declined the Restricted
Service Agreement.
*Note: Not set for 'trigger' events (see [ASSERTION] ctx)
Sample Event Rules
Sample Asset-Management-Level Event Rule
In this example, we want the EMX to record in the internal log when an asset sensor network link goes up or down. The sample event rule looks like this:
ï‚·
Event: Device > Network interface link state is up
ï‚·
Trigger condition: Both
ï‚·
Actions: System Event Log Action
To create the above event rule:
1. Enter a name for the rule.
2. Select the Enabled checkbox to enable the rule.
3. From the Event drop-down, select Device > "Network interface link state is up". These selections indicate we are specifying an event regarding asset sensor management, and we want the EMX to respond to the event related to physical connections and/or disconnections.
4. Select the Both radio button since we want both connection and disconnection actions to be recorded when either action is taken.
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. To do that we would set up an event rule like this:
ï‚·
Event: External sensor slot > Slot 1 > Numeric Sensor > Any subevent
ï‚·
Actions: System SNMP Trap Action
To create the above event rule:
1. Select "External sensor slot" in the Event field to indicate we are specifying an event at the environmental sensor level.
2. Select "Slot 1" from the submenu because we want the report about the sensor connected to sensor port #1.
3. Select "Numeric Sensor" to indicate the sensor is a numeric sensor.
Note: A numeric sensor uses numeric values to indicate the environmental condition while a discrete (on/off) sensor uses alphabetical characters to indicate the sensor state.
155
156
Chapter 7: Event Rules, Event Actions and Application Logs
4. Select "<Any sub-event>" 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.
Sample User-Activity-Level Event Rule
In this example, we want the EMX to record the user activity event in the internal log when any user logs in or logs out. The event rule is set like this:
ï‚·
Event: User activity > Any user > User logged in
ï‚·
Trigger condition: Both
ï‚·
Actions: System Event Log Action
To create the above event rule:
1. Select "User activity" in the Event field to indicate we are specifying an event regarding the user activity.
2. Select "<Any user>" from the submenu because we want to record the activity of all users.
3. Select "User logged in" to select the user login-related events.
4. Select the Both radio button since we want both login and logout actions to be recorded when either event occurs.
5. Select "System Event Log Action" as we intend to record this event in the internal log when the specified events occur.
Modifying an Event Rule
You can change an event rule's event, action, trigger condition and other settings, if any.
Exception: Events and actions selected in the built-in event rules are not changeable, including System Event Log Rule and System SNMP
Notification Rule.
To modify an event rule:
1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. On the Rules tab, select the event rule that you want to modify in the left pane.
3. To disable the event rule, deselect the Enabled checkbox.
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 <Any user>).
5. If radio buttons are available, you may select a radio button other than the current selection to change the rule triggering condition.
6. To change the action(s), do any of the following in the Actions field:
 To add a new action, click the drop-down arrow, select the action from the list, and click Add Action.
7. To remove any action, select it from the "Added actions" list box, and click the Remove button to move it back to the "Available actions" list box. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
 To remove all actions at a time, simply click the Remove All button .
8. Click Save to save the changes.
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.
9. Click Close to quit the dialog.
Modifying an Action
An existing action can be changed so that all event rules where this action is involved change their behavior accordingly.
Exception: The built-in action "System Event Log Action" is not userconfigurable.
To modify an action:
1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. Click the Actions tab.
3. Select the action that you want to modify from the left list.
4. Make necessary changes to the information shown.
5. Click Save to save the changes.
157
158
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. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. To delete an event rule: a. Ensure the Rules tab is selected. If not, click the Rules tab. b. Select the desired rule from the left list, and click Delete Rule. c. A message appears, prompting you to confirm the operation.
Click Yes to confirm the deletion.
3. To delete an action: a. Click the Actions tab. b. Select the desired action from the left list, and click Delete
Action. c. A message appears, prompting you to confirm the operation.
Click Yes to confirm the deletion.
4. Click Close to quit the dialog.
A Note about Untriggered Rules
In some cases, a measurement exceeds a threshold causing the EMX to generate an alert. The measurement then returns to a value within the threshold, but the EMX does not generate an alert message for the
Deassertion event. Such scenarios can occur due to the hysteresis tracking the EMX uses. See
What is Deassertion Hysteresis?
(on page
Event Logging
By default, the EMX captures certain system events and saves them in a local (internal) event log.
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.
Each event entry in the local log consists of:
 Date and time of the event
 Type of the event
 A description of the event
 ID number of the event
2. The dialog shows the final page by default. You can:
 Switch between different pages by doing one of the following:
- Click or to go to the first or final page.
- Click or to go to the prior or next page.
- Type a number in the Page text box and press Enter to go to a specific page.
 Select a log entry from the list and click Show Details, or simply double-click the log entry to view detailed information.
Note: Sometimes when the dialog is too narrow, the icon takes the place of the Show Details button. In that case, click and select
Show Details to view details.
 Click
to view the latest events.
3. Enlarge the dialog if necessary.
4. You can re-sort the list or change the columns displayed.
5. Click Close to quit the dialog.
Clearing Event Entries
If it is not necessary to keep existing event history, you can remove all of it from the local log.
To delete all event entries:
1. Choose Maintenance > View Event Log. The Event Log dialog appears.
159
160
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. Choose Maintenance > View Communication Log. The
Communication Log dialog appears.
2. The dialog shows the final page by default. You can:
 Switch between different pages by doing one of the following:
- Click or to go to the first or final page.
- Click or to go to the prior or next page.
- Type a number in the Page text box and press Enter to go to a specific page.
 Select a log entry from the list and click Show Details, or simply double-click the log entry to view detailed information.
Note: Sometimes when the dialog is too narrow, the icon takes the place of the Show Details button. In that case, click and select
Show Details to view details.
3. To immediately update the communication log, click .
4. To save the communication log on your computer, click .
5. Enlarge the dialog if necessary.
6. You can re-sort the list or change the columns displayed.
7. Click Close to quit the dialog.
Chapter 8 Managing External Devices
Overview
In This Chapter
EMX and PX2 PDU Cascading Connections ........................................ 162
Configuring the Serial Port .................................................................... 169
Environmental Sensors ......................................................................... 169
Schroff LHX Heat Exchangers .............................................................. 192
PowerLogic PM710 ............................................................................... 198
The EMX provides you with ability to monitor devices and conditions in your data center such as the status of servers, environmental conditions, and so on using third party sensors and devices.
You are also able to use a webcam to view data center activity, and a
GSM modem to send SMS messages when a specific event occurs.
161
162
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.
The following configurations are supported:
ï‚·
EMX EMX EMX EMX
ï‚·
EMX PX2 PX2 PX2
The first EMX is the master device, and all devices connected to the master are its slaves. The master device is device 1 in the chain, and all subsequent devices are numbered sequentially.
The first slave device connects to the USB-A port on the EMX master device from the slave's USB-B port via a USB cable. If another device is added to the chain, connect the new device's USB-B port to the existing devices USB-A port using a USB cable.
All EMX devices must be using the EMX 2.2 (or later) firmware, and all
PX2 devices must be using PX-2.3 (or later) firmware. If the devices are not running the supported firmware, upgrade your device before you connect each device in the chain.
All devices in the chain are accessible over an IP network, with the master EMX acting as a network bridge. The USB-cascading configuration only supports wired networking so you must make sure:
ï‚·
The master device has "wired" Ethernet connectivity.
ï‚·
None of the slave devices has wired Ethernet connectivity. Even though you connect any slave device to the LAN through a network cable, its wired Ethernet interface is automatically disabled.
ï‚·
None of the devices in the chain has wireless connectivity.
The devices in the chain are displayed in the explorer pane on the left once they are connected and detected by the master EMX. Clicking on the master EMX displays all available ports in the data pane.
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. If you are adding an additional EMXs to the chain, plug a USB cable into USB-B port on the additional EMX, then plug the other end into
USB-A on the EMX that is already connected to the master EMX. Up to three (3) EMXs can be connected to the master EMX.
Cascading PX2 Devices with a EMX
Note: When cascading devices, use a wired network connection.
Wireless connections are not supported when cascading devices.
To connect PX2 devices to an EMX:
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 PX2 and connect it to the USB-A port on the master EMX.
163
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.
164
Server Accessibility
You can monitor whether specific IT devices are alive by having the EMX device continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.
This function is especially useful when you are not located in an area with Internet connectivity.
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.
Tip: To make the EMX automatically log, send notifications or perform other actions for any server accessibility or inaccessibility events, you can create event rules associated with server monitoring. See
Configuring Event Rules
To add IT equipment for ping monitoring:
1. Choose Device Settings > Server Reachability. The Server
Reachability dialog appears.
2. Click New. The Add New Server dialog appears.
3. By default, the "Enable Ping Monitoring for this Server" checkbox is selected. If not, select it to enable the ping monitoring feature.
4. Provide the information required.
Field Description
IP Address/Hostname IP address or host name of the IT equipment whose accessibility you want to monitor.
Number of
Successful Pings to
Enable Feature
Wait Time (in seconds) after
Successful Ping
The number of successful pings required to declare that the monitored equipment is
"Reachable." Valid range is 0 to 200.
The wait time before sending the next ping if the previous ping was successfully responded. Valid range is 5 to 600
(seconds).
Wait Time (in seconds) after
Unsuccessful Ping
Number of
Consecutive
Unsuccessful Pings for Failure
The wait time before sending the next ping if the previous ping was not responded.
Valid range is 3 to 600 (seconds).
The number of consecutive pings without any response before the monitored equipment is declared "Unreachable."
Valid range is 1 to 100.
165
166
Chapter 8: Managing External Devices
Field
Wait Time (in seconds) before
Resuming Pinging
Description
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.
In the beginning, the status of the monitored equipment shows "Waiting for reliable connection," which means the requested number of consecutive successful or unsuccessful pings has not reached before the
EMX can declare that the monitored device is reachable or unreachable.
Example: Ping Monitoring and SNMP Notifications
In this illustration, it is assumed that a significant PDU (IP address:
192.168.84.95) shall be monitored by your EMX to make sure that PDU is properly operating all the time, and the EMX must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure. The prerequisite for this example is that the power source for your EMX is different from the power source for that
PDU.
This requires two steps: set up the PDU monitoring and create an event rule.
Step 1: Set up the ping monitoring for the target PDU
1. Choose Device Settings > Server Reachability. The Server
Reachability dialog appears.
2. Type 192.168.84.95 in the IP Address/Hostname field.
3. To make the EMX declare the accessibility of the monitored PDU every 15 seconds (3 pings * 5 seconds) when that PDU is accessible, do the following: a. In the Number of Successful Pings to Enable Feature field, type
3. b. In the Wait Time (in seconds) after Successful Ping field, type 5.
4. To make the EMX declare the inaccessibility of the monitored PDU when that PDU becomes inaccessible for around 12 seconds (4 pings * 3 seconds), do the following: a. In the Number of Consecutive Unsuccessful Unsuccessful Pings for Failure field, type 4. b. In the Wait Time (in seconds) after Unsuccessful Ping field, type
3.
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. In the "Rule name" field, type "Send SNMP notifications for PDU
(192.168.84.95) inaccessibility."
4. Select the Enabled checkbox to enable this new rule.
5. In the Event field, choose Server Monitoring > 192.168.84.95 >
Unreachable.
6. In the "Trigger condition" field, select the Unreachable radio button.
This makes the EMX react only when the target PDU becomes inaccessible.
7. Select the System SNMP Notification Action from the "Available actions" list box, and click to add it to the "Selected actions" list box.
Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see
Configuring SNMP Notifications
Editing Ping Monitoring Settings
You can edit the ping monitoring settings for any IT device whenever it requires changes.
To modify the ping monitoring settings for an IT device:
1. Choose Device Settings > Server Reachability. The Server
Reachability dialog appears.
2. Select the IT device whose settings you want to modify by clicking it.
3. Click Edit or double-click the IT device. The Edit Server 'XXX' dialog appears, where XXX is the IP address or host name of the IT device.
4. Make changes to the information shown.
5. Click OK to save the changes.
167
168
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. A message appears, prompting you to confirm the operation. Click
Yes to confirm the deletion.
5. Click Close to quit the dialog.
Checking Server Monitoring States
Server monitoring results are available in the Server Reachability dialog after specifying servers for the EMX device to monitor.
To check the server monitoring states and results:
1. Choose Device Settings > Server Reachability. The Server
Reachability dialog appears.
2. The column labeled "Ping Enabled" indicates whether the monitoring for the corresponding server is activated or not.

: This icon denotes that the monitoring for the corresponding server is enabled.

: This icon denotes that the monitoring for the corresponding server is disabled.
3. The column labeled "Status" indicates the accessibility of each monitored server.
Status
Reachable
Unreachable
Waiting for reliable connection
Description
The server is accessible.
The server is inaccessible.
The connection between the EMX device and the server is not established yet.
You may change the sorting order of the list if necessary.
4. Click Close to quit the dialog.
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.
Note: The serial port setting is especially useful when the EMX works in conjunction with Raritan's Dominion LX KVM switch. The Dominion LX only supports 19200 bps for communications over the serial interface.
To change the serial port baud rate settings:
1. Choose Device Settings > Serial Port Settings. The Serial Port
Configuration dialog appears.
2. In the Baud Rate field, click the drop-down arrow, and select the desired baud rate from the list.
3. If needed, configure GSM modem settings. a. Enter the SIM PIN. b. Select 'Use custom SMS center number' if a custom SMS will be used. c. Enter the SMS center number in the SMS Center field. d. Click Advanced Information and complete all required information. e. Enter the number of the recipients phone in the Recipients
Phone field, then click Send SMS Test to send a test SMS message.
4. Click OK.
Environmental Sensors
The EMX can monitor the environmental conditions, such as temperature and humidity, where environmental sensors are placed.
When a sensor is plugged in to the EMX and there are free sensor numbers available, the sensor is manged automatically. Specifically, it a sensor number is assigned to it, and the EMX starts polling its readings.
Additionally, the LCD display switches to most recently added external sensor so you can confirm that the sensor has been added.
To add environmental sensors:
1. Physically connect environmental sensors to the EMX device. See
Connecting Environmental Sensors (Optional)
169
170
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
4. The EMX should automatically manage the detected sensors. Verify whether detected sensors are managed. If not, have them managed.
See
Managing Environmental Sensors
5. Configure the sensors. See
Configuring Environmental Sensors
(on page 172). The steps include:
a. Name the sensor. b. If the connected sensor is a Raritan contact closure sensor, specify an appropriate sensor type. c. Mark the sensor's physical location on the rack or in the room.
Note: Numeric sensors use numeric values to indicate the environmental or internal conditions while discrete (on/off) sensors use alphabetical characters only to indicate the state changes.
Identifying Environmental Sensors
An environmental sensor includes a serial number tag on the sensor cable.
The serial number for each sensor appears listed in the web interface after each sensor is detected by the EMX.
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
#
Port
Information
The ID number assigned to each environmental sensor.
The number of the SENSOR port where each environmental sensor is physically connected.
"CC1" and "CC2" refer to the onboard contact closure sensor termination.
Managing Environmental Sensors
The EMX starts to retrieve an environmental sensor's reading and/or state and records the state transitions after the environmental sensor is managed.
If a Raritan sensor hub is used, you can connect up to 16 environmental sensors per SENSOR port. That is,
ï‚·
For EMX2-111, which has only 1 SENSOR port, a maximum of 16 environmental sensors can be connected.
ï‚·
For EMX2-888, which has 8 SENSOR ports, a maximum of 128 environmental sensors can be connected. Since the EMX2-888 device is implemented with two channels of onboard contact closure termination, it supports a maximum of 130 environmental sensors.
ï‚·
Each SENSOR port can only support a maximum of two Raritan contact closure sensors, which has the shortest update interval among all Raritan sensors. See
Information about Update Interval
When the total number of managed sensors has not reached the maximum, the EMX automatically brings detected environmental sensors under management. You should only have to manually manage a sensor when it is not under management.
To manually manage an environmental sensor:
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
2. Click the External Sensors folder in the EMX Explorer pane, and the
External Sensors page opens in the right pane.
3. Click the sensor you want to manage on the External Sensors page.
171
172
Chapter 8: Managing External Devices
Note: To identify all detected sensors, see
Identifying
Environmental Sensors
4. Click Manage. The "Manage sensor <serial number> (<sensor type>)" dialog appears, where <serial number> is the sensor's serial number and <sensor type> is the sensor's type.
Note: For a contact closure sensor, a channel number is added to the end of the <sensor type>.
5. There are two ways to manage the sensor:
 To manage this sensor by letting the EMX assign a number to it, select "Automatically assign a sensor number." This method does not release any managed sensors.
 To manage this sensor by assigning the number you want to it, select "Manually select a sensor number." Then click the drop-down arrow to select a number.
If the number you selected was already assigned to a sensor, that sensor becomes released after losing this ID number.
Tip: The information in parentheses following each ID number indicates whether the number has been assigned to any sensor. If it has been assigned to a sensor, it shows that sensor's serial number.
Otherwise, it shows the term "unused."
6. Click OK. The EMX starts to track and display the managed sensor's reading and/or state.
7. To manage additional sensors, repeat Steps 3 to 6.
Note: When the number of managed sensors reaches the maximum, you
CANNOT manage additional sensors until you remove or replace any managed sensors. To remove a sensor, see
Unmanaging
Environmental Sensors
Configuring Environmental Sensors
You may change the default name for easily identifying the managed sensor, and describe its location with X, Y and Z coordinates.
To configure 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
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
3. Select the sensor that you want to configure.
4. Click Setup. The "Setup of external sensor <serial number> (<sensor type>)" dialog appears, where <serial number> is the serial number of this sensor and <sensor type> 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. If the selected environmental sensor is the Raritan contact closure sensor connected with a third-party detector/switch, select the appropriate sensor type in the Binary Sensor Subtype field.
 Contact: The detector/switch is designed to detect the door lock or door open/closed status.
 Smoke Detection: The detector/switch is designed to detect the appearance of smoke.
 Water Detection: The detector/switch is designed to detect the appearance of water on the floor.
 Vibration: The detector/switch is designed to detect the vibration in the floor.
6. Type a new name in the Name field.
7. Describe the sensor's location by assigning alphanumeric values to the X, Y and Z coordinates. See
Describing the Sensor Location
8. If the selected environmental sensor is a numeric sensor, its threshold settings are displayed in the dialog. Click Edit or doubleclick the Threshold Configuration table to adjust the threshold, deassertion hysteresis and assertion timeout settings.
 To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.
 After any threshold is enabled, type an appropriate numeric value in the accompanying text box.
 To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See
What is Deassertion Hysteresis?
 To enable the assertion timeout for all thresholds, type a numeric value other than zero in the Assertion Timeout (samples) field.
See
What is Assertion Timeout?
The Upper Critical and Lower Critical values are points at which the
EMX considers the operating environment critical and outside the range of the acceptable threshold.
9. Click OK to save the changes.
173
174
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
2. Click Setup on the Settings page. The EMX Setup dialog appears.
3. In the "External sensors Z coordinate format" field, click the dropdown arrow and select an option from the list.
 Rack Units: The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors.
 Free-Form: Any alphanumeric string can be used for specifying the Z coordinate.
4. Click OK to save the changes.
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. For example:
X = Brown Cabinet Row
Y = Third Rack
Z = Top of Cabinet
Values for the X, Y and Z coordinates may consist of:
ï‚·
For X and Y: Any combination of alphanumeric characters. The coordinate value can be 0 to 24 characters long.
ï‚·
For Z when the Z coordinate format is set to Rack Units, any numeric value ranging from 0 to 60.
ï‚·
For Z when the Z coordinate format is set to Free-Form, any alphanumeric characters from 0 to 24 characters.
Tip: To configure and retrieve these coordinate values over SNMP, see the EMX MIB. To configure and retrieve these values over the CLI, see
Using the Command Line Interface
175
176
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. Since the environmental sensors are measured per second, specifying a value of 60, for example, would cause measurements to be written to the data log once every minute. Since there are 120 measurements of storage per sensor, specifying a value of 60 means the log can store the last two hours of measurements before the oldest one in log gets overwritten in the log.
Though the environmental sensors are measured per second, their readings may not be updated per second. See
Information about
Update Interval
(on page 177). The update interval varies depending on
how many environmental sensors are connected to the EMX device and the sensor type. The more the environmental sensors are connected, the larger the update interval is. Therefore, type a large number in the
Measurements Per Log Entry field when there are a large number of environmental sensors connected.
Whenever measurements are written to the log, three values for each sensor are written: the average, minimum and maximum values. For example, if measurements are written every minute, the average of all measurements that occurred during the preceding 60 seconds along with the minimum and maximum measurement values are written to the log.
Note: The EMX's SNMP agent must be enabled for this feature to work.
See
Enabling SNMP
(on page 202) for more details. In addition, using
an NTP time server ensures accurately time-stamped measurements.
Enabling Data Logging
By default, data logging is disabled. Only users having the
"Administrator" or "Change Data Logging Settings" permissions can enable or disable this feature. See
Setting Up Roles
To configure the data logging feature:
1. Choose Device Settings > Data Logging. The Data Logging Options dialog appears.
2. To enable the data logging feature, select the "enable" checkbox in the Enable Data Logging field.
3. Type a number in the Measurements Per Log Entry field. Valid range is from 1 to 600. The default is 60.
4. Select the environmental sensors whose data logging you want to enable.
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.
ï‚·
Normal type: Sensor readings or states are updated in a longer interval, which varies between 3 to 40 seconds according to the total number of connected environmental sensors. Most Raritan environmental sensors belong to this type, such as the temperature or humidity sensor.
ï‚·
High priority type: Sensor readings or states are updated in a shorter interval, which is less than or equal to 3 seconds. Raritan contact closure sensors belong to this type.
Viewing Sensor Data
Readings of the environmental sensors will display in the web interface after these sensors are properly connected and managed.
The Dashboard page shows the information for managed environmental sensors only, while the External Sensors page shows the information for both of managed and unmanaged ones.
If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds, or at least one LHX built-in sensor fails on the heat exchanger. See
Readings Highlighted in Yellow or Red
(EMX)
Readings Highlighted in Yellow or Red
To view managed environmental sensors only:
1. Click the Dashboard icon in the EMX Explorer pane, and the
Dashboard page opens in the right pane.
2. Locate the External Sensors section on the Dashboard page. The section shows:
 Total number of managed sensors
 Total number of unmanaged sensors
 Information of each managed sensor, including:
- Name
- Reading
- State
177
178
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
2. Click the External Sensors folder in the EMX Explorer pane, and the
External Sensors page opens in the right pane.
Detailed information for each connected sensor is displayed, including:
 Label (number)
 Serial number
 Sensor type
 Name
 Reading
 State
 Channel (for a contact closure sensor only)
Sensor Measurement Accuracy
Raritan environmental sensors are with the following factory specifications. Calibration is not required for environmental sensors.
ï‚·
Temperature: +/-2 degrees Celsius
ï‚·
Humidity: +/-5% (when humidity < 60%) or +/-8% (when humidity >
60%)
ï‚·
Differential air pressure: +/-1.5%
ï‚·
Air flow: +/-6.5%
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.
Note: Numeric sensors use numeric values to indicate the environmental or internal conditions while discrete (on/off) sensors use alphabetical characters only to indicate the state changes.
Sensor state
unavailable alarmed normal below lower critical below lower warning above upper warning above upper critical
Applicable to
All sensors
Discrete sensors
All sensors
Numeric sensors
Numeric sensors
Numeric sensors
Numeric sensors
"unavailable" State
The unavailable state means the connectivity to the sensor is lost.
The EMX pings all managed sensors at regular intervals in seconds. If it does not detect a particular sensor for three consecutive scans, the
unavailable state is displayed for that sensor.
When the communication with a contact closure sensor's processor is lost, all detectors (that is, all switches) connected to the same sensor module show the "unavailable" state.
Note: When the sensor is deemed unavailable, the existing sensor configuration remains unchanged. For example, the ID number assigned to the sensor remains associated with it.
The EMX continues to ping unavailable sensors, and moves out of the
unavailable state after detecting the sensor for two consecutive scans.
179
180
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.
For a Raritan's floor water sensor, the normal state must be set to
Normally Closed, which means no water is detected.
Note: See
Configuring a Contact Closure Sensor
information on setting the normal state or dip switch. For the onboard contact closure sensor termination, see
Connecting Third-Party
Detectors/Switches to the EMX
(on page 38) for how to set the normal
state.
For a numeric sensor, this state means the sensor reading is within the acceptable range as indicated below:
Lower Warning threshold <= Reading < Upper Warning threshold
Note: The symbol <= means smaller than (<) or equal to (=).
"alarmed" State
This state means a discrete (on/off) sensor is in the "abnormal" state.
Usually for a contact closure sensor, the meaning of this state varies based on the sensor's normal state setting.
ï‚·
If the normal state is set to Normally Closed, the alarmed state means the contact closure switch is open.
ï‚·
If the normal state is set to Normally Open, the alarmed state means the contact closure switch is closed.
Note: See
Configuring a Contact Closure Sensor
information on setting the normal state or dip switch. For the onboard contact closure sensor termination, see
Connecting Third-Party
Detectors/Switches to the EMX
(on page 38) for how to set the normal
state.
Tip: A contact closure sensor's LED is lit after entering the alarmed state.
If the sensor module has two channels for connecting two switches, two
LEDs are available. Check which contact closure switch is in the
"abnormal" status according to the channel number of the LED.
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 (=).
"above upper warning" State
This state means a numeric sensor's reading is above the upper warning threshold as indicated below:
Upper Warning Threshold <= Reading < Upper Critical Threshold
Note: The symbol <= means smaller than (<) or equal to (=).
"above upper critical" State
This state means a numeric sensor's reading is above the upper critical threshold as indicated below:
Upper Critical Threshold <= Reading
Note: The symbol <= means smaller than (<) or equal to (=).
Unmanaging Environmental Sensors
When it is unnecessary to monitor a particular environmental factor, you can unmanage or release the corresponding environmental sensor so that the EMX device stops retrieving the sensor's reading and/or state.
To release a managed sensor:
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
2. Click the External Sensors folder in the EMX Explorer pane, and the
External Sensors page opens in the right pane.
3. Click the sensor you want to unmanage on the External Sensors page.
4. Click Release.
181
182
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.
ï‚·
Upper and Lower Warning thresholds indicate the sensor reading enters the warning range before the critical threshold.
ï‚·
Upper and Lower Critical thresholds indicate the sensor reading is at the critical level.
To avoid generating a large amount of alert events, the deassertion hysteresis for each threshold is enabled. You can change the default hysteresis value if necessary. For more information on the deassertion hysteresis, see
What is Deassertion Hysteresis?
Note: After setting the thresholds, remember to configure the event rules.
See
Configuring Event Rules
For information on configuring an environmental sensor's threshold, see
Configuring Environmental Sensors
(on page 172). For information on
configuring thresholds for a Schroff LHX heat exchanger, see
Configuring Temperature and Fan Thresholds
LHX Temperature and Fan Thresholds
What is Deassertion Hysteresis?
The hysteresis setting determines when a threshold condition is reset.
This diagram illustrates how hysteresis values relate to thresholds:
Upper Critical Threshold
Hysteresis
Upper Critical Reset
Upper Warning Threshold
Hysteresis
Upper Warning Reset
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.
What is Assertion Timeout?
When the assertion timeout is enabled, the EMX device asserts any warning or critical condition only after a specified number of consecutive samples that cross a particular threshold are generated. This prevents a number of threshold alerts from being generated if the measurements return to normal immediately after rising above any upper threshold or dropping below any lower threshold.
183
184
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. After connecting a webcam, you can visually monitor environmental conditions near the EMX through the web interface from anywhere.
For more information on the QuickCam webcam, see the user documentation accompanying it. For information on connecting a webcam to the EMX, see
Connecting a Logitech Webcam (Optional)
Snapshots or videos captured by the webcam are displayed in the right pane of EMX web interface once a webcam is selected in the navigation tree. Snapshots and videos can also be displayed in Live Preview mode in the Primary Standalone Live Preview window by clicking on the Live
Preview icon .
EMX allows you to take and store snapshots from each webcam. See
Taking, Viewing and Managing Webcam Snapshots
additional information.
Images can be stored locally on the EMX, or on another location. Locally,
10 images can be saved on the EMX. Storing images in alternate locations allows you to save as many images as that location allows. See
Configuring Webcam Storage
(on page 186) for more information.
Note: Rebooting the EMX deletes the snapshots taken via webcam.
Links to video being captured by a webcam can be sent via email or instant message. See
Sending Videos in an Email or Instant Message
Events that trigger emails containing snapshots from a webcam can be created. Events can be defined for each individual webcam. See
Event
Rules and Actions
(on page 131).You must have Change Webcam
Configuration permission applied to your role in order to configure webcams, and the View Webcam Images and Configuration permission to view images in EMX.
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)
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. Select a resolution for the webcam.
5. Select the webcam mode. This can be changed as needed once the webcam is configured. a. Video - the webcam is in video mode. Set the Framerate (frames per second) rate. b. Snapshot - the webcam displays images from the webcam. Set the Time Between Image(s) rate as measured in seconds.
6. Click OK. The image or video from the webcam is now available in the EMX once you click on the webcam in the navigation tree.
To edit a webcam configuration:
1. In the navigation tree, click on the Webcam Management folder. The
Webcam Management page opens.
2. Double-click on the webcam you want to edit. The webcam image or video opens in a new tab.
3. Click Setup.
4. Edit the information as needed. Changes to the resolution do not apply to existing, stored images - it applies only to images and videos taken after the resolution is changed.
5. Click OK.
185
186
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. In the navigation tree, click Snapshot under the Webcam
Management folder. The Snapshots page opens.
2. Click on the Setup Storage icon . The Storage Setup dialog opens.
3. By default, Local, meaning the EMX, is the designated default storage.
4. Select CIFS/Samba as the storage location.
5. Enter the server on which to store the images.
6. If needed, enter the share drive/folder to store the images in.
7. Enter the username and password needed to access the server the images are stored on.
8. Enter or use the slide bar to set the number of images that can be saved to the storage location.
9. Click OK.
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
Snapshots or videos captured by a webcam are displayed in the right pane of EMX web interface once a webcam is selected in the navigation tree.
187
188
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. The location of the webcam is displayed in the Location pane below the image, along with any labels applied to the webcam. See
Configuring
Webcams
Up to five (5) Live Preview sessions can be displayed at once in different tabs in the EMX interface, or in separate Live Preview windows that are accessed by clicking on the Live Preview icon snapshot/video.
located above the
Note: For remote Live Preview sessions, such as those accessed via link in an email or instant message, a total of up to three (3) simultaneous
Live Preview sessions are supported at a time. One (1) from the originator in the EMX interface, and up to two (2) remote sessions.
Individual snapshots taken by a webcam are viewed by clicking on
Snapshots under Webcam Management in the navigation tree. Once selected, the Snapshots tab opens in the right pane. See
Taking,
Viewing and Managing Webcam Snapshots
Viewing and Managing Stored Snapshots for details.
Taking, Viewing and Managing Webcam Snapshots
Once 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. Unless snapshots are deleted manually, the oldest snapshot is automatically deleted from the device when the number of snapshots exceeds ten.
Note: Rebooting the EMX deletes the snapshots taken via webcam.
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.
See
Configuring Webcam Storage
(on page 186) for more information
on configuration an image storage location.
Snapshot files are saved as JPG files. The snapshot file is named based on the number of the snapshot starting from 1. So the first snapshot that is taken is named 1.jpg, the second is 2.jpg and so on.
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. Once the snapshot image being taken by the selected webcam is displayed in the right pane, click the Store Snapshot to Webcam
Storage icon above the image to take a snapshot. Up to ten (10) snapshots can be stored at once on the device.
To view existing snapshots:
1. In the navigation tree, click Snapshot under the Webcam
Management folder. The snapshots are displayed in the right pane in the Storage section of the page.
2. View an individual snapshot by clicking on a snapshot file in the
Storage section of the page.
The size of each snapshot file, the date and time each snapshot was taken, and the webcam that took each snapshot, is displayed when viewing snapshots.
Details, such as the webcam location and/or labels, if any, are displayed in the Details section below the snapshot in the right pane.
This information is defined when the webcam is initially configured.
See
Configuring Webcams
189
190
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. To select and delete all snapshots at once, click the checkbox in the checkbox column header, then click the Delete icon.
Sending Videos in an Email or Instant Message
You are able to email or instant message up to two (2) recipients a link to webcams attached to the EMX. Users can then click on the links and view snapshots or videos.
Note: For remote Live Preview sessions, such as those accessed via link in an email or instant message, a total of up to three (3) simultaneous
Live Preview sessions are supported at a time. One (1) from the originator in the EMX interface, and up to two (2) remote sessions.
Note: For the purposes of this topic, the message sender is User A and the recipient is User B.
The recipient is able to access the video image via the link so long as either:
ï‚·
The video remains open in Live Preview mode in the User A's EMX interface, and User A does not log out of the interface and the session does not time out.
Or
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.
Best Practice
As a best practice, in the EMX interface, User A should open the video in a secondary Live Preview window and leave the Live Preview window open at least until User B opens the video via the link.
Once User B opens the video via the link, the secondary Live Preview mode window can be closed in the User A's EMX interface.
User B must manually let User A know they have opened the link, or
User A can check to see if User B is currently connected to the application by clicking Maintenance > Connected Users.
To send a video link via email or instant message:
1. In the navigation tree, click on the webcam that is capturing the video you want to provide a link to in the email. The video is displayed in
Live Preview mode in the right pane.
2. Click on the Live Preview icon located above the video. The video opens in a secondary Live Preview window.
3. Copy the URL from the Live Preview window, paste it into the email or instant message application. Leave the Live Preview window open at least until the recipient opens the video via the link.
GSM Modems
A Cinteron
®
MC52iT or MC55iT GSM modem must be connected to the
EMX in order to send SMS event messages. See
Creating Actions
(on
page 136) for more information on SMS event messages.
Note: The EMX cannot receive SMS messages.
To connect the GSM modem:
1. Connect the GSM modem to the DB9 serial port on the EMX.
2. Configure the GSM modem as needed. See the supporting GSM modem help for information on configuring the GSM modem.
3. Configure the GSM modem settings in EMX. a. Click Device Settings > Serial Port Settings. The Serial Port
Configuration dialog opens. b. If needed, enter the GSM modem SIM PIN.
191
192
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.
From the EMX, you can remotely do the following:
ï‚·
Name a connected LHX heat exchanger
ï‚·
Configure the air outlet temperature setpoint
ï‚·
Configure air outlet temperature thresholds
ï‚·
Configure air inlet temperature thresholds
ï‚·
Configure water inlet temperature thresholds
ï‚·
Configure fan speed thresholds
ï‚·
Monitor the air inlet temperature
ï‚·
Monitor the air outlet temperature
ï‚·
Monitor the fan speed
ï‚·
Configure basic settings for the connected heat exchanger, such as the sensor thresholds
Note: 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.
See
Connecting a Schroff LHX Heat Exchanger (Optional)
(on page
41) for how to connect the heat exchanger.
Enabling and Disabling Schroff LHX Heat Exchanger Support
By default, Schroff LHX Heat Exchanger support is disabled. As such, support needs to be enabled before the device appears in the navigation tree or on the dashboard. Additionally, Schroff LHX Heat Exchanger support must be enabled in order for the LHX-MIB to be accessible through SNMP.
To enable the Schroff LHX Heat Exchanger:
1. Select Device Settings > Features, and then select the Schroff Heat
Exchanger checkbox on the menu.
2. Click Yes to confirm.
3. Reboot the EMX.
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. 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
3. Click the Auxiliary Ports folder. The Auxiliary Ports page opens in the right pane, listing all RS-485 ports.
4. Select the port where the desired heat exchanger is connected on the Auxiliary Ports page, and click Setup. Or simply double-click that port. The Auxiliary Ports Setup dialog for the selected port appears.
5. Type a name for the heat exchanger in the Name field.
6. Click OK to save the changes.
To name a heat exchanger using the setup dialog for a heat exchanger:
1. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports.
2. Click the desired heat exchanger in the EMX Explorer pane. The page specific to that heat exchanger opens in the right pane.
3. Click Setup in the Settings section.
4. Type a name for the heat exchanger in the Name field.
5. Click OK to save the changes.
193
194
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.
To configure the thresholds for a sensor:
1. Connect the LHX heat exchanger to EMX if it is not already connected.
2. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports.
3. Click the desired heat exchanger in the EMX Explorer pane. The page specific to that heat exchanger opens in the right pane.
4. Select the desired sensor in the Sensors table and click Setup
Thresholds, or simply double-click that sensor. The setup dialog for the selected sensor appears.
5. Adjust the threshold and deassertion hysteresis settings. The Upper
Critical and Lower Critical values are points at which the EMX considers the operating environment critical and outside the range of the acceptable threshold.
 To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.
 After any threshold is enabled, type an appropriate numeric value in the accompanying text box.
 To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See
What is Deassertion Hysteresis?
6. Click OK to save the changes.
Monitoring the Heat Exchanger
The EMX web interface lets you monitor the status of each connected
LHX heat exchanger as well as the status of each LHX built-in sensor.
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. Click the Dashboard icon in the EMX Explorer pane. The Dashboard page opens in the right pane.
2. Locate the LHX Heat Exchanger section where a list of connected
LHX heat exchangers is displayed.
To view the LHX summary on the Auxiliary Ports page:
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
2. Click the Auxiliary Ports folder. The Auxiliary Ports page opens in the right pane, listing all RS-485 ports.
Viewing Details
An LHX heat exchanger page shows detailed information, including:
ï‚·
Device information and settings, such as the RS-485 port number and device name
ï‚·
The air outlet temperature
ï‚·
Readings and states of all LHX built-in sensors
ï‚·
Accumulative operating hours
ï‚·
Errors, such as failed LHX sensors or emergency cooling activation
To view details of a specific LHX heat exchanger:
1. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports.
Click the desired heat exchanger in the EMX Explorer pane. The page specific to that heat exchanger opens in the right pane.
195
196
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
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.
The heat exchanger is turned ON but enters the critical state because of any LHX sensor failure.
At least one of the LHX sensor readings has crossed the upper or lower warning threshold.
NO device is detected on this RS-485 port.
To identify the cause of the critical state, view one of the following:
ï‚·
The LHX Heat Exchanger section of the Dashboard page. See
Monitoring the Heat Exchanger
ï‚·
The Auxiliary Ports page. See
Monitoring the Heat Exchanger
(on
ï‚·
The Alert States section of the LHX heat exchanger page. See
Alert
States and LHX Event Log
Alert States and LHX Event Log
When an LHX heat exchanger is physically connected to the EMX device, a section labeled Alert States appears on its device page. The
Alert States section shows information identifying the LHX sensors that currently fail.
Tip: The Dashboard and Auxiliary Ports pages also point out failed sensors. See
Monitoring the Heat Exchanger
A button labeled Show Event Log is located in the Alert States section.
To view the events associated with the EMX, click this button.
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.
Below are the time units used for operating hours:
ï‚· h: hour(s)
ï‚· d: day(s)
For example, "3d 5h" means the total operating time is 3 days and 5 hours.
Controlling the Heat Exchanger
The EMX allows you to remotely turn on or off a connected heat exchanger.
To control the LHX heat exchanger:
1. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports.
Click the desired heat exchanger in the EMX Explorer pane. The page specific to that heat exchanger opens in the right pane.
2. Locate the Information section.
 To turn off the LHX heat exchanger, click Switch Off.
 To turn on the LHX heat exchanger, click Switch On.
197
198
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
PowerLogic PM710
The Schneider Electric PowerLogic
®
PM710 power meter is connected to the EMX-111 RS485 port. Once it is connected and the EMX detects it, the PM710 is viewed under the Auxiliary Port folder in the navigation tree.
Note: The EMX-888 does not support the PowerLogic PM710.
This device is only supported when plugged into the RS485 port using a
PM710 supported cable (not provided by Raritan with the EMX. Refer to your Schneider Electric PowerLogic PM710 documentation for information on the pinouts for the meter.
Note: For information on the PM710 and any sensor-specific configuration required, see the PM710 user guide.
From the EMX, you can remotely reset the PM710 energy accumulators, and the PM710 minimum and maximum reading values. Additionally, you can create event rules and actions for the PM710, such as emailing or sending an SMS message when thresholds are reached, and so on. See
Creating an Event Rule
The PM710 line speed, parity and address, as well as the thresholds for
PM710 numeric sensors, can be configured on the PM710. These settings need to be the match in EMX. For example, if the address is 42 in the PM710 it must also be 42 in EMX.
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.
Note: PM710 meters are not supported through SNMP or the command line interface (CLI).
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. Pin the auxiliary port to the PM710.
3. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports.
4. Click the desired sensor in the EMX Explorer pane. The page specific to that sensor opens in the right pane.
5. Click Setup in the Settings section. The Setup dialog opens.
6. Enter a name for the sensor in the Name field.
7. Leave the device address, line speed and parity as is so it matches the PM710 settings.
8. Click OK.
9. Configure the threshold settings if needed. Click on Thresholds at the bottom right of the Sensors section or Power Quality section of the page. The Thresholds dialog opens and displays the sensor readings gathered by EMX.
10. Select a reading and then click Edit, or double click on a reading to open its corresponding Threshold dialog.
11. Check the checkboxes next to the readings you want to set thresholds for, then edit the thresholds as needed. Click OK to save the changes.
Resetting the PM710 Minimum and Maximum Values
The PM710 saves readings when they reach their highest and lowest value. The highest value and lowest value are the minimum and maximum values, which can be reset as needed. Review your PM710 documentation for additional information.
To reset the PM710 minimum and maximum values:
1. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports.
2. Click the desired sensor in the EMX Explorer pane. The page specific to that sensor opens in the right pane.
199
200
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. Click the desired sensor in the EMX Explorer pane. The page specific to that sensor opens in the right pane.
3. Click on "Clear all Energy Accumulators" at the bottom left of the
Sensors section of the page.
4. Click OK to confirm. All values are clear.
Chapter 9 Using SNMP
Overview
In This Chapter
Configuring SNMP Notifications ............................................................ 204
Configuring Users for Encrypted SNMP v3 ........................................... 208
SNMP Gets and Sets ............................................................................ 209
This SNMP section helps you set up the EMX for use with an SNMP manager. The EMX can be configured to send traps or informs to an
SNMP manager, as well as receive GET and SET commands in order to retrieve status and configure some basic settings.
201
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.
202
2. Select the "enable" checkbox in the "SNMP v1 / v2c" field to enable communication with an SNMP manager using SNMP v1 or v2c protocol.
 Type the SNMP read-only community string in the Read
Community String field. Usually the string is "public."
 Type the read/write community string in the Write Community
String field. Usually the string is "private."
3. Select the "enable" checkbox in the "SNMP v3" field to enable communication with an SNMP manager using SNMP v3 protocol.
Tip: You can permit or disallow a user to access the EMX via the
SNMP v3 protocol. See
Configuring Users for Encrypted SNMP v3
4. Enter the MIB-II system group information, if applicable:
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
6. Click OK to save the changes.
203
204
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.
SNMP TRAP communications capture and send information via SNMP, but no confirmation that the communication between the devices has succeeded is provided to the receiving device.
SNMP INFORM communications capture and send information via
SNMP, and an acknowledgment that the communication was received by the receiving device is provided. If the inform communication fails, it is resent. You can define the number of times and the intervals to resend the inform communication, or leave the defaults of five (5) resends in three (3) second intervals.
Note: SNMP INFORM communications may take up slightly more network resources than SNMP TRAP communications since there are additional communications between the devices, and due to additional network traffic created should the initial communication fail and another is sent.
Use SNMP TRAP rules if you do not need confirmation that the communication has succeeded, and if you need to conserve network resources. Use SNMP INFORM communications to ensure more reliable communications, and if network resources can be managed with the potential additional network traffic.
Note: You should update the MIB used by your SNMP manager when updating to a new EMX release. This ensures your SNMP manager has the correct MIB for the release you are using. See
Downloading SNMP
MIB
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.
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
4. Click OK to save the changes.
5. On the Notifications tab, select the Enable checkbox to enable the
SNMP notification feature.
6. From the Notification Type drop-down, select the type of SNMP notification.
7. For SNMP INFORM communications, leave the resend settings at their default or:
205
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. In the Host fields, enter the IP address of the device(s) you want to access. This is the address to which notifications are sent by the
SNMP system agent. You can specify up to 3 SNMP destinations.
9. In the Port fields, enter the port number used to access the device(s).
10. 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.
11. Click OK.
SNMPv3 Notifications
To configure the EMX to send SNMPv3 notifications:
1. Choose Device Settings > Network Services > SNMP. The SNMP
Settings dialog appears.
206
2. Enter the MIB-II system group information, if applicable:
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
4. Click OK to save the changes.
5. On the Notifications tab, select the Enable checkbox to enable the
SNMP notification feature.
6. From the Notification Type drop-down, select the type of SNMP notification.
7. For SNMP TRAPs, the engine ID is prepopulated.
8. For SNMP INFORM communications, leave the resend settings at their default or: a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. 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.
9. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings: a. Host name b. Port number c. User ID needed to access the host d. Select the host security level
207
208
Chapter 9: Using SNMP
Security level
"noAuthNoPriv"
"authNoPriv"
"authPriv"
Description
Select this if no authorization or privacy protocols are needed.
ï‚·
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.
ï‚·
Select the authentication protocol - MD5 or
SHA
ï‚·
Enter the authentication passphrase and confirm the authentication passphrase
ï‚·
Select the Privacy Protocol - DES or AES
ï‚·
Enter the privacy passphrase and then confirm the privacy passphrase
ï‚·
Click OK
Configuring Users for Encrypted SNMP v3
The SNMP v3 protocol allows for encrypted communication. To take advantage of this, users need to have an Authentication Pass Phrase and Privacy Pass Phrase, which act as shared secrets between them and the EMX.
To configure users for SNMP v3 encrypted communication:
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. To change the SNMPv3 access permissions, click the SNMPv3 tab and make necessary changes. For details, see Step 6 of
Creating a
User Profile
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. When you change the SNMP system name, the device name shown in the web interface is also changed.
The EMX does NOT support configuring IPv6-related parameters using the SNMP set requests.
Valid objects for these requests are limited to those found in the SNMP
MIB-II System Group and the custom EMX MIB.
The EMX MIB
The SNMP MIB file is required for using your EMX device with an SNMP manager. An SNMP MIB file describes the SNMP functions.
Downloading SNMP MIB
The SNMP MIB file for the EMX can be easily downloaded from the web interface. There are two ways to download the SNMP MIB file.
To download the file from the SNMP Settings dialog:
1. Choose Device Settings > Network Services > SNMP. The SNMP
Settings dialog appears.
2. Click Download MIB. A submenu of MIB files appear.
3. Select the desired MIB file to download.
 EMD-MIB: The SNMP MIB file for managing the EMX device.
 ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.
 LHX-MIB: The SNMP MIB file for managing the LHX heat exchanger(s).
Note: Schroff LHX Support must be enabled in order for the LHX-
MIB to be available. See
Enabling and Disabling Schroff LHX
Heat Exchanger Support
209
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, ASSETMANAGEMENT-
MIB 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.
As standard, these objects are first presented at the beginning of the file, listed under their parent group. The objects then appear again individually, defined and described in detail.
210
For example, the measurementsGroup group contains objects for environmental sensors connected to the EMX device. One object listed under this group, measurementsExternalSensorState, is described later in the MIB as "The sensor state." boardFirmwareVersion, part of the configGroup group, describes the firmware version.
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
description of how thresholds work.
Note: When configuring the thresholds via SNMP set commands, ensure the value of upper critical threshold is higher than that of upper warning threshold.
211
Chapter 10 Using the Command Line Interface
In This Chapter
Restricted Service Agreement ............................................................... 216
Configuring the EMX Device and Network ............................................ 231
Network Troubleshooting ....................................................................... 323
Querying Available Parameters for a Command ................................... 326
Retrieving Previous Commands ............................................................ 327
Automatically Completing a Command ................................................. 327
Resetting to Factory Defaults (CLI) ....................................................... 328
About the Interface
The EMX provides a command line interface that enables data center administrators to perform some basic management tasks.
Using this interface, you can do the following:
ï‚·
Reset the EMX device
ï‚·
Display the EMX and network information, such as the device name, firmware version, IP address, and so on
ï‚·
Configure the EMX and network settings
ï‚·
Troubleshoot network problems
You can access the interface over a serial connection using a terminal emulation program such as HyperTerminal, or via a Telnet or SSH client such as PuTTY.
Note: Telnet access is disabled by default because it communicates openly and is thus insecure. To enable Telnet, see
Modifying the
Network Service Settings
212
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.
This section illustrates HyperTerminal, which is part of Windows operating systems prior to Windows Vista.
To log in using HyperTerminal:
1. Connect your computer to the EMX device via a local connection.
2. Launch HyperTerminal on your computer and open a console window. When the window first opens, it is blank.
Make sure the COM port settings use this configuration:
 Bits per second = 115200 (115.2Kbps)
 Data bits = 8
 Stop bits = 1
 Parity = None
 Flow control = None
Tip: For a USB connection, you can find out which COM port is assigned to the EMX by choosing Control Panel > System >
Hardware > Device Manager, and locating the "Dominion Serial
Console" under the Ports group.
3. Press Enter. The Username prompt appears.
4. Type a name and press Enter. The name is case sensitive, so make sure you capitalize the correct letters. Then you are prompted to enter a password.
213
214
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
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.
With SSH or Telnet
You can remotely log in to the command line interface using an SSH or
Telnet client, such as PuTTY.
Note: PuTTY is a free program you can download from the Internet. See
PuTTY's documentation for details on configuration.
To log in using SSH or Telnet:
1. Ensure SSH or Telnet has been enabled. See
Modifying the
Network Service Settings
(on page 84) in the EMX User Guide.
2. Launch an SSH or Telnet client and open a console window. A login prompt appears.
3. Type a name and press Enter. The name is case sensitive, so make sure you capitalize the correct letters.
Note: If using the SSH client, the name must NOT exceed 25 characters. Otherwise, the login fails.
Then you are prompted to enter a password.
4. Type a password and press Enter. The password is case sensitive, so make sure you capitalize the correct letters.
Chapter 10: Using the Command Line Interface
5. After properly entering the password, the # or > system prompt appears. See
Different CLI Modes and Prompts
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.
Different CLI Modes and Prompts
Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.
ï‚·
User Mode: When you log in as a normal user, who does not have full permissions to configure the EMX device, the > prompt appears.
ï‚·
Administrator Mode: When you log in as an administrator, who has full permissions to configure the EMX device, the # prompt appears.
ï‚·
Configuration Mode: You can enter the configuration mode from the administrator mode. In this mode, the prompt changes to config:# and you can change EMX device and network configurations. See
Entering the Configuration Mode
ï‚·
Diagnostic Mode: You can enter the diagnostic mode from the administrator mode. In this mode, the prompt changes to diag:> and you can perform the network troubleshooting commands, such as the ping command. See
Entering the Diagnostic Mode
(on page
Closing a Serial Connection
Close the window or terminal emulation program when you finish accessing a EMX device over the serial connection.
When accessing or upgrading multiple EMX devices, do not transfer the serial cable from one device to another without closing the serial connection window first.
215
216
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.
Unauthorized access and activities or any criminal activity will be reported to appropriate authorities.
# config config:# security restrictedServiceAgreement enabled bannerContent config:# security restrictedServiceAgreement enabled true false config:# security restrictedServiceAgreement enabled true config:# security restrictedServiceAgreement bannerContent
Please input the Restricted Service Agreement banner content.
Maximum content length is 10000 characters, no special characters allowed.
Terminate the input with '<Enter>--END--<Enter>'.
This is my new restricted service agreement.
--END--
Successfully entered Restricted Service Agreement (44 characters) config:# apply
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.
I understand and accept the Restricted Service
Agreement [y/n] y
Welcome to EMX CLI!
217
218
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.
Tip: You can check what parameters are available for a specific CLI command by adding a question mark to the end of the command. See
Querying Available Parameters for a Command
Showing Information
You can use the show commands to view current settings or status of the EMX device or part of it, such as the IP address, networking mode, firmware version, and so on.
Some "show" commands have two formats: one with the parameter
"details" and the other without. The difference is that the command without the parameter "details" displays a shortened version of information while the other displays in-depth information.
After typing a "show" command, press Enter to execute it.
Note: Depending on your login name, the # prompt may be replaced by the > prompt. See
Different CLI Modes and Prompts
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 <option>
Variables:
ï‚·
<option> is one of the options: all, v4 or v6.
Option
all v4 v6
Description
This options shows both of IPv4 and IPv6 settings.
Tip: You can also type the command without adding this option "all" to get the same data.
This option shows the IPv4 settings only.
This option shows the IPv6 settings only.
LAN Interface Settings
This command shows the LAN interface information only, such as LAN interface speed, duplex mode, and current LAN interface status.
# show network interface
Networking Mode
This command shows whether the current networking mode is wired or wireless.
# show network mode
219
220
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.
# show network services <option>
Variables:
ï‚·
<option> is one of the options: all, http, https, telnet, ssh, snmp and
zeroconfig.
Option
all http https telnet ssh snmp zeroconfig
Description
Displays the settings of all network services, including HTTP, HTTPS, Telnet, SSH and SNMP.
Tip: You can also type the command without adding this option "all" to get the same data.
Only displays the TCP port for the HTTP service.
Only displays the TCP port for the HTTPS service.
Only displays the settings of the Telnet service.
Only displays the settings of the SSH service.
Only displays the SNMP settings.
Only displays the settings of the zero configuration advertising.
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 <n>
Variables:
ï‚·
<n> is one of the options: all, or a number.
Option
all
Description
Displays all asset sensor information.
Tip: You can also type the command without adding this option "all" to get the same data.
A specific asset sensor number
Displays the settings of the asset sensor connected to the specified FEATURE port number.
For the EMX device with only one FEATURE port, the valid number is always 1.
221
222
Chapter 10: Using the Command Line Interface
Environmental Sensor Information
This command syntax shows the environmental sensor's information.
# show externalsensors <n>
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.
# show externalsensors <n> details
External sensor 3 (Temperature):
Reading: 31.8 deg C
State: normal
Resolution: 0.1 deg C
Accuracy: +/- 1.00 %
Tolerance: +/- 0.05 deg C
Range: -55.0 deg C - 125.0 deg C
Lower critical threshold: 15.0 deg C
Lower warning threshold: 20.0 deg C
Upper warning threshold: 55.0 deg C
Upper critical threshold: 60.0 deg C
Chapter 10: Using the Command Line Interface
Deassertion hysteresis: 1.0 deg C
Assertion timeout: 0 samples
Variables:
ï‚·
<n> is one of the options: all, or a number.
Option
all
Description
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 environmental sensor number*
Displays the information for the specified environmental sensor only.
* The environmental sensor number is the ID number assigned to the sensor, which can be found on the External Sensors page of the EMX web interface.
Displayed information:
ï‚·
Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Note: A state (on/off) sensor displays the sensor state instead of the numeric reading.
ï‚·
With the parameter "details," more information is displayed in addition to the ID number and sensor reading, such as the serial number and X, Y, and Z coordinates.
223
224
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 <n>
To show detailed information, add the parameter "details" to the end of the command.
# show sensor externalsensor <n> details
Variables:
ï‚·
<n> is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the External Sensors page of the EMX web interface.
Displayed information:
ï‚·
Without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed.
ï‚·
With the parameter "details," more sensor information is displayed, including accuracy and range.
Note: For a discrete (on/off) sensor, the threshold-related and accuracyrelated data is NOT available.
Show Serial
# show serial
Output baudRate The baud rate
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.
Security Settings
This command shows the security settings of the EMX.
# show security
To show detailed information, add the parameter "details" to the end of the command.
# show security details
Displayed information:
ï‚·
Without the parameter "details," the information including IP access control, role-based access control, password policy, and HTTPS encryption is displayed.
ï‚·
With the parameter "details," more security information is displayed, such as user blocking time and user idle timeout.
225
226
Chapter 10: Using the Command Line Interface
Existing User Profiles
This command shows the data of one or all existing user profiles.
# show user <user_name>
To show detailed information, add the parameter "details" to the end of the command.
# show user <user_name> details
Variables:
ï‚·
<user_name> 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
all
Description
This option shows all existing user profiles.
Tip: You can also type the command without adding this option "all" to get the same data.
a specific user's name This option shows the profile of the specified user only.
Displayed information:
ï‚·
Without the parameter "details," only four pieces of user information are displayed: user name, "enabled" status, SNMP v3 access privilege, and role(s).
ï‚·
With the parameter "details," more user information is displayed, such as the telephone number, e-mail address, preferred measurement units and so on.
Chapter 10: Using the Command Line Interface
Existing Roles
This command shows the data of one or all existing roles.
# show roles <role_name>
Variables:
ï‚·
<role_name> is the name of the role whose permissions you want to query. The variable can be one of the following options:
Option
all
Description
This option shows all existing roles.
Tip: You can also type the command without adding this option "all" to get the same data.
a specific role's name This option shows the data of the specified role only.
Displayed information:
ï‚·
Role settings are displayed, including the role description and privileges.
227
228
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 <n> <rack_unit>
Variables:
ï‚·
<n> 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.
ï‚·
<rack_unit> is one of the options: all or a specific rack unit's index number.
Option
all
A specific number
Description
Displays the settings of all rack units on the specified asset sensor.
Tip: You can also type the command without adding this option "all" to get the same data.
Displays the settings of the specified rack unit on the specified asset sensor.
Use the index number to specify the rack unit. The index number of each rack unit is available on the
Asset Strip page of the web interface.
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 <n> <rack_unit> <blade_slot>
Variables:
ï‚·
<n> 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.
ï‚·
<rack_unit> is the index number of the desired rack unit (tag port) on the selected asset sensor. The index number of each rack unit is available on the Asset Strip page of the web interface.
ï‚·
<blade_slot> is one of the options: all or a specific number of a tag port on the blade extension strip.
Option
all
A specific number
Description
Displays the information of all tag ports on the specified blade extension strip connected to a particular rack unit.
Tip: You can also type the command without adding this option "all" to get the same data.
Displays the information of the specified tag port on the blade extension strip connected to a particular rack unit.
The number of each tag port on the blade extension strip is available on the Asset Strip page.
Command History
This command syntax shows the command history for current connection session.
# show history
Displayed information:
ï‚·
A list of commands that were previously entered in the current session is displayed.
229
230
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. Ensure you have entered the administrator mode and the # prompt is displayed.
Note: If you enter the configuration mode from the user mode, you may have limited permissions to make configuration changes. See
Different CLI Modes and Prompts
2. Type config and press Enter. The config:# prompt appears, indicating that you have entered the configuration mode.
3. Now you can type any configuration command and press Enter to change the settings.
Important: To apply new configuration settings, you must issue the
"apply" command before closing the terminal emulation program.
Closing the program does not save any configuration changes. See
231
232
Chapter 10: Using the Command Line Interface
Quitting the Configuration Mode
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. config:# emd name "<name>"
Variables:
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
Example
The following command assigns the name "my emx888" to the EMX device. config:# emd name "my emx888"
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 <option>
Variables:
ï‚·
<option> is one of the options: rackUnits or freeForm.
Option
rackUnits freeForm
Description
The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors.
Any alphanumeric string can be used for specifying the Z coordinate.
Note: After determining the format for the Z coordinate, you can set a value for it. See
Setting the Z Coordinate
Example
The following command determines that the unit of rack is used for specifying the Z coordinate of environmental sensors. config:# emd externalSensorsZCoordinateFormat rackUnits
Enabling or Disabling Data Logging
This command syntax enables or disables the data logging feature. config:# emd dataRetrieval <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
Enables the data logging feature.
Disables the data logging feature.
233
234
Chapter 10: Using the Command Line Interface
For more information, see
Setting Data Logging
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 <number>
Variables:
ï‚·
<number> is an integer between 1 and 600. The default is 60 samples per log entry.
For more information, see
Setting Data Logging
Example
The following command determines that 66 measurements are accumulated per log entry for sensors, that is, 66 seconds. config:# emd measurementsPerLogEntry 66
Networking Configuration Commands
A network configuration command begins with network. A number of network settings can be changed through the CLI, such as the IP address, transmission speed, duplex mode, and so on.
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 <mode>
Variables:
ï‚·
<mode> is one of the modes: wired or wireless.
Mode
wired wireless
Description
Enables the wired networking mode.
Enables the wireless networking mode.
Note: If you enable the wireless networking mode, and the EMX does not detect any wireless USB LAN adapter or the connected wireless USB
LAN adapter is not supported, the message "Supported Wireless device not found" is displayed.
Example
The following command enables the wired networking mode. config:# network mode wired
Configuring IP Protocol Settings
By default, only the IPv4 protocol is enabled. You can enable both the
IPv4 and IPv6 protocols, or only the IPv6 protocol for your EMX device.
An IP protocol configuration command begins with network ip.
235
236
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 <protocol>
Variables:
ï‚·
<protocol> is one of the options: v4Only, v6Only or both.
Mode
v4Only v6Only both
Description
Enables IPv4 only on all interfaces. This is the default.
Enables IPv6 only on all interfaces.
Enables both IPv4 and IPv6 on all interfaces.
Example
The following command determines that both of IPv4 and IPv6 protocols are enabled. config:# network ip proto both
Selecting IPv4 or IPv6 Addresses
This command syntax determines which IP address is used when the
DNS server returns both of IPv4 and IPv6 addresses. You need to configure this setting only after both of IPv4 and IPv6 protocols are enabled on the EMX. config:# network ip dnsResolverPreference <resolver>
Variables:
ï‚·
<resolver> is one of the options: preferV4 or preferV6.
Option
preferV4 preferV6
Description
Use the IPv4 addresses returned by the DNS server.
Use the IPv6 addresses returned by the DNS server.
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.
Note: If current networking mode is not wireless, the SSID, PSK and
BSSID values are not applied until the networking mode is changed to
"wireless." In addition, a message appears, indicating that the active network interface is not wireless.
The commands are case sensitive so ensure you capitalize them correctly.
Setting the SSID
This command syntax specifies the SSID string. config:# network wireless SSID <ssid>
Variables:
ï‚·
<ssid> is the name of the wireless access point, which consists of:
- Up to 32 ASCII characters
- No spaces
- ASCII codes 0x20 ~ 0x7E
Example
The following command assigns "myssid" as the SSID. config:# network wireless SSID myssid
237
238
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 <method>
Variables:
ï‚·
<method> is one of the authentication methods: PSK or EAP.
Method
PSK
EAP
Description
The wireless authentication method is set to PSK.
The wireless authentication method is set to EAP.
Example
The following command sets the wireless authentication method to PSK. config:# network wireless authMethod PSK
Setting the PSK
If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command syntax. config:# network wireless PSK <psk>
Variables:
ï‚·
<psk> is a string or passphrase that consists of:
- Up to 32 ASCII characters
- No spaces
- ASCII codes 0x20 ~ 0x7E
Example
This command assigns "encryp-key" as the PSK. config:# network wireless PSK encryp-key
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. config:# network wireless eapOuterAuthentication <outer_auth>
Variables:
ï‚·
The value of <outer_auth> is PEAP because EMX only supports
Protected Extensible Authentication Protocol (PEAP) as the outer authentication.
Example
The following command determines the outer authentication protocol for the EAP authentication is Protected Extensible Authentication Protocol
(PEAP). config:# network wireless eapOuterAuthentication PEAP
Setting the Inner Authentication
This command syntax determines the inner authentication protocol for the EAP. config:# network wireless eapInnerAuthentication <inner_auth>
Variables:
ï‚·
The value of <inner_auth> is MSCHAPv2 because EMX only supports Microsoft's Challenge Authentication Protocol Version 2
(MSCHAPv2) as the inner authentication.
Example
The following command determines the inner authentication protocol for the EAP authentication is MSCHAPv2. config:# network wireless eapInnerAuthentication MSCHAPv2
239
240
Chapter 10: Using the Command Line Interface
Setting the EAP Identity
This command syntax determines the EAP identity. config:# network wireless eapIdentity <identity>
Variables:
ï‚·
<identity> 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. config:# network wireless eapPassword
Variables:
ï‚·
<password> is your password for EAP authentication.
Example
The following command sets the EAP password to "user01_password." config:# network wireless eapPassword user01_password
Providing the EAP CA Certificate
You may need to provide a third-party CA certificate for the EAP authentication.
To provide a CA certificate:
1. Type the CA certificate command as shown below and press Enter. config:# network wireless eapCACertificate
2. The system prompts you to enter the contents of the CA certificate.
Do the following to input the contents: a. Open your CA certificate with a text editor. b. Copy the contents between the "--- BEGIN CERTIFICATE ---" and "--- END CERTIFICATE ---" lines in a certificate. c. Paste the certificate contents into the terminal.
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. Your CA certificate contents should be different from the contents displayed in this example.
To provide a CA certificate:
1. Make sure you have entered the configuration mode. See
Entering the Configuration Mode
2. Type the following command and press Enter. config:# network wireless eapCACertificate
3. The system prompts you to enter the contents of the CA certificate.
4. Open a CA certificate using a text editor. You should see certificate contents similar to the following.
5. Select and copy the contents, excluding the starting line containing
"BEGIN CERTIFICATE" and the ending line containing "END
CERTIFICATE" as illustrated below.
241
242
Chapter 10: Using the Command Line Interface
MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk
GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW
NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE
BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw
YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ
QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta
W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w
C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/
A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH
H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb
EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+z4IBO
6. Paste the contents in the terminal.
7. Press Enter.
8. Verify whether the system shows the following command prompt, indicating the provided CA certificate is valid. config:#
Setting the BSSID
This command syntax specifies the BSSID. config:# network wireless BSSID <bssid>
Variables:
ï‚·
<bssid> is the MAC address of the wireless access point.
Example
The following command specifies that the BSSID is 00:14:6C:7E:43:81. config:# network wireless BSSID 00:14:6C:7E:43:81
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 <mode>
Variables:
ï‚·
<mode> is one of the modes: dhcp or static.
Mode
dhcp static
Description
The IPv4 configuration mode is set to DHCP.
The IPv4 configuration mode is set to static IP address.
Example
The following command enables the Static IP configuration mode. config:# network ipv4 ipConfigurationMode static
Setting the IPv4 Preferred Host Name
After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command syntax: config:# network ipv4 preferredHostName <name>
Variables:
ï‚·
<name> is a host name which:
 Consists of alphanumeric characters and/or hyphens
 Cannot begin or end with a hyphen
 Cannot contain more than 63 characters
 Cannot contain punctuation marks, spaces, and other symbols
243
244
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 <ip address>
Variables:
ï‚·
<ip address> is the IP address being assigned to your EMX device.
The value ranges from 0.0.0.0 to 255.255.255.255.
Example
The following command assigns the static IPv4 address
"192.168.84.222" to the EMX device. config:# network ipv4 ipAddress 192.168.84.222
Setting the IPv4 Subnet Mask
After selecting the static IP configuration mode, you can use this command syntax to define the subnet mask. config:# network ipv4 subnetMask <netmask>
Variables:
ï‚·
<netmask> is the subnet mask address. The value ranges from
0.0.0.0 to 255.255.255.255.
Example
The following command sets the subnet mask to 192.168.84.0. config:# network ipv4 subnetMask 192.168.84.0
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 <ip address>
Variables:
ï‚·
<ip address> 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.0
Setting the IPv4 Primary DNS Server
After selecting the static IP configuration mode, you can use this command syntax to specify the primary DNS server. config:# network ipv4 primaryDNSServer <ip address>
Variables:
ï‚·
<ip address> is the IP address of the primary DNS server. The value ranges from 0.0.0.0 to 255.255.255.255.
Example
The following command determines that the primary DNS server is
192.168.84.30. config:# network ipv4 primaryDNSServer 192.168.84.30
245
246
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 <ip address>
Variables:
ï‚·
<ip address> 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. If two IPv4 DNS servers and two IPv6 DNS servers are available, the EMX only uses the primary IPv4 and IPv6 DNS servers.
Example
The following command determines that the secondary DNS server is
192.168.84.33. config:# network ipv4 secondaryDNSServer 192.168.84.33
Overriding the IPv4 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 ipv4 overrideDNS <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
This option overrides the DHCP-assigned DNS server with the primary/secondary DNS server you assign.
This option resumes using the DHCP-assigned
DNS server.
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. config:# network ipv6 ipConfigurationMode <mode>
Variables:
ï‚·
<mode> is one of the modes: automatic or static.
Mode
automatic static
Description
The IPv6 configuration mode is set to automatic.
The IPv6 configuration mode is set to static IP address.
Example
The following command sets the IP configuration mode to the static IP address mode. config:# network ipv6 ipConfigurationMode static
247
248
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 <ip address>
Variables:
ï‚·
<ip address> 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. config:# network ipv6 ipAddress 3210:4179:0:8:0:800:200:417/128
Setting the IPv6 Gateway
After selecting the static IP configuration mode, you can use this command syntax to specify the gateway. config:# network ipv6 gateway <ip address>
Variables:
ï‚·
<ip address> is the IP address of the gateway. This value uses the
IPv6 address format.
Example
The following command sets the gateway to 500:0:330:0:4:9:3:2. config:# network ipv6 gateway 500:0:330:0:4:9:3:2
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
config:# network ipv6 primaryDNSServer <ip address>
Variables:
ï‚·
<ip address> is the IP address of the primary DNS server. This value uses the IPv6 address format.
Example
The following command determines that the primary DNS server is
2103:288:8201:1::14. config:# network ipv6 primaryDNSServer 2103:288:8201:1::14
Setting the IPv6 Secondary DNS Server
After selecting the static IP configuration mode, you can use this command syntax to specify the secondary 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
config:# network ipv6 secondaryDNSServer <ip address>
Variables:
ï‚·
<ip address> is the IP address of the secondary DNS server. This value uses the IPv6 address format.
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.
Example
The following command determines that the secondary DNS server is
2103:288:8201:1::700. config:# network ipv6 secondaryDNSServer 2103:288:8201:1::700
249
250
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 <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable
Description
This option overrides the DHCP-assigned DNS server with the primary/secondary DNS server you assign. disable This option resumes using the DHCP-assigned
DNS server.
Example
The following command overrides the DHCP-assigned DNS server with the one you specified. config:# network ipv6 overrideDNS enable
Setting the LAN Interface Parameters
A LAN interface configuration command begins with network interface.
The commands are case sensitive so ensure you capitalize them correctly.
Changing the LAN Interface Speed
This command syntax determines the LAN interface speed. config:# network interface LANInterfaceSpeed <option>
Variables:
ï‚·
<option> is one of the options: auto, 10Mbps, and 100Mbps.
Option
auto
Description
System determines the optimum LAN speed through auto-negotiation.
Chapter 10: Using the Command Line Interface
Option
10Mbps
100Mbps
Description
The LAN speed is always 10 Mbps.
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. config:# network interface LANInterfaceDuplexMode <mode>
Variables:
ï‚·
<mode> is one of the modes: auto, half or full.
Option
auto half full
Description
The EMX selects the optimum transmission mode through auto-negotiation.
Half duplex:
Data is transmitted in one direction (to or from the
EMX device) at a time.
Full duplex:
Data is transmitted in both directions simultaneously.
Example
The following command lets the EMX determine the optimal transmission mode through auto-negotiation. config:# network interface LANInterfaceDuplexMode auto
Setting the Network Service Parameters
A network service command begins with network services.
251
252
Chapter 10: Using the Command Line Interface
Changing the HTTP Port
This command syntax changes the HTTP port. config:# network services http port <n>
Variables:
ï‚·
<n> 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. config:# network services https port <n>
Variables:
ï‚·
<n> is a TCP port number between 1 and 65535. The default HTTPS port is 443.
Example
The following command sets the HTTPS port to 333. config:# network services https port 333
Changing the Telnet Configuration
You can enable or disable the Telnet service, or change its TCP port using the CLI commands.
A Telnet command begins with network services telnet.
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 <option>
Variables:
ï‚·
<option> is one of the options: true or false.
Option
true false
Description
The Telnet service is enabled.
The Telnet service is disabled.
Example
The following command enables the Telnet service. config:# network services telnet enabled true
Changing the Telnet Port
This command syntax changes the Telnet port. config:# network services telnet port <n>
Variables:
ï‚·
<n> is a TCP port number between 1 and 65535. The default Telnet port is 23.
Example
The following command syntax sets the TCP port for Telnet to 44. config:# network services telnet port 44
Changing the SSH Configuration
You can enable or disable the SSH service, or change its TCP port using the CLI commands.
An SSH command begins with network services ssh.
253
254
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 <option>
Variables:
ï‚·
<option> is one of the options: true or false.
Option
true false
Description
The SSH service is enabled.
The SSH service is disabled.
Example
The following command enables the SSH service. config:# network services ssh enabled true
Changing the SSH Port
This command syntax changes the SSH port. config:# network services ssh port <n>
Variables:
ï‚·
<n> is a TCP port number between 1 and 65535. The default SSH port is 22.
Example
The following command syntax sets the TCP port for SSH to 555. config:# network services ssh port 555
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 <auth_method>
Variables:
ï‚·
<option> is one of the options: passwordOnly, publicKeyOnly or
passwordOrPublicKey.
Option
passwordOnly
Description
Enables the password-based login only. publicKeyOnly Enables the public key-based login only. passwordOrPublicKey Enables both the password- and public key-based login. This is the default.
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. See
Specifying the SSH Public Key
Example
The following command causes users to have to type a password for the
SSH login. Use of the SSH public key is not permitted. config:# network services ssh authentication passwordOnly
Setting the SNMP Configuration
You can enable or disable the SNMP v1/v2c or v3 agent, configure the read and write community strings, or set the MIB-II parameters, such as sysContact, using the CLI commands.
An SNMP command begins with network services snmp.
Enabling or Disabling SNMP v1/v2c
This command syntax enables or disables the SNMP v1/v2c protocol. config:# network services snmp v1/v2c <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable
Description
The SNMP v1/v2c protocol is enabled.
255
256
Chapter 10: Using the Command Line Interface
Option
disable
Description
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 <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
The SNMP v3 protocol is enabled.
The SNMP v3 protocol is disabled.
Example
The following command enables the SNMP v3 protocol. config:# network services snmp v3 enable
Setting the SNMP Read Community
This command syntax sets the SNMP read-only community string. config:# network services snmp readCommunity <string>
Variables:
ï‚·
<string> is a string comprising 4 to 64 ASCII printable characters.
ï‚·
The string CANNOT include spaces.
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 <string>
Variables:
ï‚·
<string> is a string comprising 4 to 64 ASCII printable characters.
ï‚·
The string CANNOT include spaces.
Example
The following command sets the SNMP read/write community string to
"private." config:# network services snmp writeCommunity private
Setting the sysContact Value
This command syntax sets the SNMP MIB-II sysContact value. config:# network services snmp sysContact <value>
Variables:
ï‚·
<value> is a string comprising 0 to 255 alphanumeric characters.
Example
The following command sets the SNMP MIB-II sysContact to
"John_Krause." config:# network services snmp sysContact John_Krause
257
258
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 <value>
Variables:
ï‚·
<value> 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. config:# network services snmp sysLocation <value>
Variables:
ï‚·
<value> is a string comprising 0 to 255 alphanumeric characters.
Example
The following command sets the SNMP MIB-II sysLocation to
"New_TAIPEI" config:# network services snmp sysLocation New_TAIPEI
Security Configuration Commands
A security configuration command begins with security.
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.
259
260
Chapter 10: Using the Command Line Interface
Modifying the Firewall Control Parameters
There are different commands for modifying firewall control parameters.
ï‚·
IPv4 commands
To enable or disable the IPv4 firewall control feature, use this command syntax:
config:# security ipAccessControl ipv4 enabled <option>
To determine the default IPv4 firewall control policy, use this command syntax:
config:# security ipAccessControl ipv4 defaultPolicy <policy>
ï‚·
IPv6 commands
To enable or disable the IPv6 firewall control feature, use this command syntax:
config:# security ipAccessControl ipv6 enabled <option>
To determine the default IPv6 firewall control policy, use this command syntax:
config:# security ipAccessControl ipv6 defaultPolicy <policy>
Variables:
ï‚·
<option> is one of the options: true or false.
Option
true
Description
Enables the IP access control feature. false Disables the IP access control feature.
ï‚·
<policy> is one of the options: accept, drop or reject.
Option
accept drop
Description
Accepts traffic from all IP addresses.
Discards traffic from all IP addresses, without sending any failure notification to the source host.
Chapter 10: Using the Command Line Interface
Option
reject
Description
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
Example
The following command sets up two parameters of the IPv4 access control feature. config:# security ipAccessControl ipv4 enabled true defaultPolicy accept
Results:
ï‚·
The IPv4 access control feature is enabled.
ï‚·
The default policy is set to "accept."
Managing Firewall Rules
You can add, delete or modify firewall rules using the CLI commands.
ï‚·
An IPv4 firewall control rule command begins with security
ipAccessControl ipv4 rule.
ï‚·
An IPv6 firewall control rule command begins with security
ipAccessControl ipv6 rule.
Adding a Firewall Rule
Depending on where you want to add a new firewall rule in the list, the command syntax for adding a rule varies.
ï‚·
IPv4 commands
To add a new rule to the bottom of the IPv4 rules list, use this command syntax:
config:# security ipAccessControl ipv4 rule add <ip_mask> <policy>
To add a new IPv4 rule by inserting it above or below a specific rule, use this command syntax:
261
262
Chapter 10: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <ip_mask> <policy> <insert>
<rule_number>
-- OR -- config:# security ipAccessControl ipv4 rule add <insert> <rule_number>
<ip_mask> <policy>
ï‚·
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 <ip_mask> <policy>
To add a new IPv6 rule by inserting it above or below a specific rule, use this command syntax:
config:# security ipAccessControl ipv6 rule add <ip_mask> <policy> <insert>
<rule_number>
-- OR -- config:# security ipAccessControl ipv6 rule add <insert> <rule_number> <ip_mask>
<policy>
Variables:
ï‚·
<ip_mask> is the combination of the IP address and subnet mask values, which are separated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.
ï‚·
<policy> is one of the options: accept, drop or reject.
Policy
accept drop reject
Description
Accepts traffic from the specified IP address(es).
Discards traffic from the specified IP address(es), without sending any failure notification to the source host.
Discards traffic from the specified IP address(es), and an ICMP message is sent to the source host for failure notification.
Chapter 10: Using the Command Line Interface
ï‚·
<insert> is one of the options: insertAbove or insertBelow.
Option
insertAbove insertBelow
Description
Inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number
Inserts the new rule below the specified rule number. Then: new rule's number = the specified rule number + 1
ï‚·
<rule_number> is the number of the existing rule which you want to insert the new rule above or below.
Example
The following command adds a new IPv4 access control rule and specifies its location in the list. config:# security ipAccessControl ipv4 rule add 192.168.84.123/24 accept insertAbove 5
Results:
ï‚·
A new IPv4 firewall control rule is added, allowing all packets from the IPv4 address 192.168.84.123 to be accepted.
ï‚·
The newly-added rule is inserted above the 5th rule. That is, the new rule becomes the 5th rule, and the original 5th rule becomes the 6th rule.
Modifying a Firewall Rule
Depending on what to modify in an existing rule, the command syntax varies.
ï‚·
IPv4 commands
The command syntax to modify an IPv4 rule's IP address and/or subnet mask:
config:# security ipAccessControl ipv4 rule modify <rule_number> ipMask
<ip_mask>
The command syntax to modify an IPv4 rule's policy:
263
264
Chapter 10: Using the Command Line Interface config:# security ipAccessControl ipv4 rule modify <rule_number> policy
<policy>
The command syntax to modify all contents of an existing IPv4 rule:
config:# security ipAccessControl ipv4 rule modify <rule_number> ipMask
<ip_mask> policy <policy>
ï‚·
IPv6 commands
The command syntax to modify an IPv6 rule's IP address and/or subnet mask:
config:# security ipAccessControl ipv6 rule modify <rule_number> ipMask
<ip_mask>
The command syntax to modify an IPv6 rule's policy:
config:# security ipAccessControl ipv6 rule modify <rule_number> policy
<policy>
The command syntax to modify all contents of an IPv6 existing rule:
config:# security ipAccessControl ipv6 rule modify <rule_number> ipMask
<ip_mask> policy <policy>
Variables:
ï‚·
<rule_number> is the number of the existing rule that you want to modify.
ï‚·
<ip_mask> is the combination of the IP address and subnet mask values, which are separated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.
ï‚·
<policy> is one of the options: accept, drop or reject.
Option
accept
Description
Accepts traffic from the specified IP address(es).
Chapter 10: Using the Command Line Interface
Option
drop reject
Description
Discards traffic from the specified IP address(es), without sending any failure notification to the source host.
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.123/24 policy accept
Results:
ï‚·
The IPv4 address is changed to 192.168.84.123, and the subnet mask to 255.255.255.0.
ï‚·
The policy now becomes "accept."
Deleting a Firewall Rule
The following commands remove a specific IPv4 or IPv6 rule from the list.
ï‚·
IPv4 commands config:# security ipAccessControl ipv4 rule delete <rule_number>
ï‚·
IPv6 commands config:# security ipAccessControl ipv6 rule delete <rule_number>
Variables:
ï‚·
<rule_number> is the number of the existing rule that you want to remove.
265
266
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 <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
Enables the HTTPS access to the web interface.
Disables the HTTPS access to the web interface.
Example
The following command disables the HTTPS access feature. config:# security enforceHttpsForWebAccess disable
Login Limitation
The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before being forced to log out.
A login limitation command begins with security loginLimits.
You can combine multiple commands to modify the login limitation parameters at a time. See
Multi-Command Syntax
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 <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
Enables the single login feature.
Disables the single login feature.
Example
The following command disables the single login feature so that more than one user can log in using the same user name at the same time. config:# security loginLimits singleLogin disable
Password Aging
This command syntax enables or disables the password aging feature, which controls whether the password should be changed at a regular interval: config:# security loginLimits passwordAging <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
Enables the password aging feature.
Disables the password aging feature.
Example
The following command enables the password aging feature. config:# security loginLimits passwordAging enable
267
268
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 <value>
Variables:
ï‚·
<value> 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. config:# security loginLimits passwordAgingInterval 90
Idle Timeout
This command syntax determines how long a user can remain idle before that user is forced to log out of the EMX web interface. config:# security loginLimits idleTimeout <value>
Variables:
ï‚·
<value> is a numeric value in minutes set for the idle timeout. The timeout ranges from 1 to 1440 minutes (24 hours).
Example
The following command sets the idle timeout to 10 munites. config:# security loginLimits idleTimeout 10
User Blocking
There are different commands for changing different user blocking parameters. These commands begin with security userBlocking.
To determine the maximum number of failed logins before blocking a user, use this command syntax:
Chapter 10: Using the Command Line Interface config:# security userBlocking maximumNumberOfFailedLogins <value1>
To determine how long a user's login is blocked, use this command syntax:
config:# security userBlocking blockTime <value2>
Variables:
ï‚·
<value1> is an integer between 3 and 10, or unlimited, which sets no limit on the maximum number of failed logins and thus disables the user blocking function.
ï‚·
<value2> is a numeric value in minutes.
Tip: You can combine multiple commands to modify the user blocking parameters at a time. See
Multi-Command Syntax
Example
The following command sets up two user blocking parameters. config:# security userBlocking maximumNumberOfFailedLogins 5 blockTime 30
Results:
ï‚·
The maximum number of failed logins is set to 5.
ï‚·
The user blocking time is set to 30 minutes.
Strong Passwords
The strong password commands determine whether a strong password is required for login, and what a strong password should contain at least.
A strong password command begins with security strongPasswords.
You can combine multiple strong password commands to modify different parameters at a time. See
Multi-Command Syntax
(on page
269
270
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 <option>
Variables:
ï‚·
<option> is one of the options: true or false.
Option
true false
Description
Enables the strong password feature.
Disables the strong password feature.
Example
This command syntax enables the strong password feature. config:# security strongPasswords enabled true
Minimum Password Length
This command syntax determines the minimum length of the password. config:# security strongPasswords minimumLength <value>
Variables:
ï‚·
<value> is an integer between 8 and 32.
Example
This command syntax determines a password must comprise at least 8 characters. config:# security strongPasswords minimumLength 8
Chapter 10: Using the Command Line Interface
Maximum Password Length
This command syntax determines the maximum length of the password. config:# security strongPasswords maximumLength <value>
Variables:
ï‚·
<value> is an integer between 16 and 64.
Example
This command syntax determines that a password must NOT comprise more than 20 characters. config:# security strongPasswords maximumLength 20
Lowercase Character Requirement
This command syntax determines whether a strong password includes at least a lowercase character. config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
At least one lowercase character is required.
No lowercase character is required.
Example
This command syntax determines that a password must include at least a lowercase character. config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter enable
Uppercase Character Requirement
This command syntax determines whether a strong password includes at least a uppercase character.
271
272
Chapter 10: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
At least one uppercase character is required.
No uppercase character is required.
Example
This command determines a password must comprise at least one uppercase character. config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter enable
Numeric Character Requirement
This command syntax determines whether a strong password includes at least a numeric character. config:# security strongPasswords enforceAtLeastOneNumericCharacter <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
At least one numeric character is required.
No numeric character is required.
Example
The following command determines that a password must comprise at least one numeric character. config:# security strongPasswords enforceAtLeastOneNumericCharacter enable
Special Character Requirement
This command syntax determines whether a strong password includes at least a special character.
Chapter 10: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option>
Variables:
ï‚·
<option> is one of the options: enable or disable.
Option
enable disable
Description
At least one special character is required.
No special character is required.
Example
The following command determines that a password must comprise at least one special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter enable
Maximum Password History
This command syntax determines the number of previous passwords that CANNOT be repeated when changing the password. config:# security strongPasswords passwordHistoryDepth <value>
Variables:
ï‚·
<value> is an integer between 1 and 12.
Example
The following command determines that the previous 7 passwords
CANNOT be re-used when changing the password. config:# security strongPasswords passwordHistoryDepth 7
273
274
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.
Modifying the Role-Based Access Control Parameters
There are different commands for modifying role-based access control parameters.
ï‚·
IPv4 commands
To enable or disable the IPv4 role-based access control feature, use this command syntax:
config:# security roleBasedAccessControl ipv4 enabled <option>
To determine the IPv4 role-based access control policy, use this command syntax:
config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>
ï‚·
IPv6 commands
To enable or disable the IPv6 role-based access control feature, use this command syntax:
config:# security roleBasedAccessControl ipv6 enabled <option>
To determine the IPv6 role-based access control policy, use this command syntax:
Chapter 10: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 defaultPolicy <policy>
Variables:
ï‚·
<option> is one of the options: true or false.
Option
true
Description
Enables the role-based access control feature. false Disables the role-based access control feature.
ï‚·
<policy> is one of the options: allow or deny.
Policy
allow deny
Description
Accepts traffic from all IP addresses regardless of the user's role.
Drops traffic from all IP addresses regardless of the user's role.
Tip: You can combine both commands to modify all role-based access control parameters at a time. See
Multi-Command Syntax
(on page
Example
The following command sets two parameters of the role-based IPv4 access control feature. config:# security roleBasedAccessControl ipv4 enabled true defaultPolicy allow
Results:
ï‚·
The role-based IPv4 access control feature is enabled.
ï‚·
The default policy is set to "allow."
Managing Role-Based Access Control Rules
You can add, delete or modify role-based access control rules.
ï‚·
An IPv4 role-based access control command for managing rules begins with security roleBasedAccessControl ipv4 rule.
ï‚·
An IPv6 role-based access control command for managing rules begins with security roleBasedAccessControl ipv6 rule.
275
276
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.
ï‚·
IPv4 commands
To add a new rule to the bottom of the IPv4 rules list, use this command syntax:
config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role>
<policy>
To add a new IPv4 rule by inserting it above or below a specific rule, use this command syntax:
config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role>
<policy> <insert> <rule_number>
ï‚·
IPv6 commands
To add a new rule to the bottom of the IPv6 rules list, use this command syntax:
config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role>
<policy>
To add a new IPv6 rule by inserting it above or below a specific rule, use this command syntax:
config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role>
<policy> <insert> <rule_number>
Variables:
ï‚·
<start_ip> is the starting IP address.
ï‚·
<end_ip> is the ending IP address.
ï‚·
<role> is the role for which you want to create an access control rule.
ï‚·
<policy> is one of the options: allow or deny.
Policy
allow
Description
Accepts traffic from the specified IP address range when the user is a member of the specified role
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
ï‚·
<insert> is one of the options: insertAbove or insertBelow.
Option
insertAbove
Description
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
ï‚·
<rule_number> is the number of the existing rule which you want to insert the new rule above or below.
Example
The following command creates a newIPv4 role-based access control rule and specifies its location in the list. config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3
Results:
ï‚·
A new IPv4 role-based access control rule is added, dropping all packets from any IPv4 address between 192.168.78.50 and
192.168.90.100 when the user is a member of the role "admin."
ï‚·
The newly-added IPv4 rule is inserted above the 3rd rule. That is, the new rule becomes the 3rd rule, and the original 3rd rule becomes the
4th rule.
Modifying a Role-Based Access Control Rule
Depending on what to modify in an existing rule, the command syntax varies.
ï‚·
IPv4 commands
To modify a rule's IPv4 address range, use this command syntax:
277
278
Chapter 10: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip>
To modify an IPv4 rule's role, use this command syntax:
config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role
<role>
To modify an IPv4 rule's policy, use this command syntax:
config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy
<policy>
To modify all contents of an existing IPv4 rule, use this command syntax:
config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy
<policy>
ï‚·
IPv6 commands
To modify a rule's IPv6 address range, use this command syntax:
config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip>
To modify an IPv6 rule's role, use this command syntax:
config:# security roleBasedAccessControl ipv6 rule modify <rule_number> role
<role>
To modify an IPv6 rule's policy, use this command syntax:
Chapter 10: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> policy
<policy>
To modify all contents of an existing IPv6 rule, use this command syntax:
config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy
<policy>
Variables:
ï‚·
<rule_number> is the number of the existing rule that you want to modify.
ï‚·
<start_ip> is the starting IP address.
ï‚·
<end_ip> is the ending IP address.
ï‚·
<role> is one of the existing roles.
ï‚·
<policy> is one of the options: allow or deny.
Policy
allow deny
Description
Accepts traffic from the specified IP address range when the user is a member of the specified role
Drops traffic from the specified IP address range when the user is a member of the specified role
Example
The following command modifies all contents of the 8th IPv4 rule. config:# security roleBasedAccessControl ipv4 rule modify 8 startIpAddress 192.168.8.8 endIpAddress 192.168.90.90 role operator policy allow
Results:
ï‚·
The starting IPv4 address is changed to 192.168.8.8, and the ending
IPv4 address to 192.168.90.90.
ï‚·
The role is changed to "operator."
ï‚·
The policy now becomes "allow."
279
280
Chapter 10: Using the Command Line Interface
Deleting a Role-Based Access Control Rule
This command removes a specific rule from the list.
ï‚·
IPv4 commands config:# security roleBasedAccessControl ipv4 rule delete <rule_number>
ï‚·
IPv6 commands config:# security roleBasedAccessControl ipv6 rule delete <rule_number>
Variables:
ï‚·
<rule_number> is the number of the existing rule that you want to remove.
Example
The following command removes the 7th IPv6 rule. config:# security roleBasedAccessControl ipv6 rule delete 7
Environmental Sensor Configuration Commands
An environmental sensor configuration command begins with
externalsensor. You can configure the name and location parameters of an individual environmental sensor.
Changing the Sensor Name
This command syntax names an environmental sensor. config:# externalsensor <n> name "<name>"
Variables:
ï‚·
<n> 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.
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
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. config:# externalsensor <n> sensorSubType <type>
Variables:
ï‚·
<n> 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.
ï‚·
<type> is one of these types: contact, smokeDetection,
waterDetection or vibration.
Type
contact
Description
The connected detector/switch is for detection of door lock or door closed/open status. smokeDetection The connected detector/switch is for detection of the smoke presence. waterDetection The connected detector/switch is for detection of the water presence. vibration The connected detector/switch is for detection of the vibration.
Example
The following indicates that a smoke detector is being connected to
Raritan's contact closure sensor (DPX-CC2-TR) whose ID number shown in the EMX web interface is 2. config:# externalsensor 2 sensorSubType smokeDetection
281
282
Chapter 10: Using the Command Line Interface
Setting the X Coordinate
This command syntax specifies the X coordinate of an environmental sensor. config:# externalsensor <n> xlabel "<coordinate>"
Variables:
ï‚·
<n> 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.
ï‚·
<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
Example
The following command sets the value "The 2nd cabinet" to the X coordinate of the environmental sensor with the ID number 4. config:# externalsensor 4 xlabel "The 2nd cabinet"
Setting the Y Coordinate
This command syntax specifies the Y coordinate of an environmental sensor. config:# externalsensor <n> ylabel "<coordinate>"
Variables:
ï‚·
<n> is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16.
ï‚·
<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
Example
The following command sets the value "The 4th row" to the Y coordinate of the environmental sensor with the ID number 4. config:# externalsensor 4 ylabel "The 4th row"
Chapter 10: Using the Command Line Interface
Setting the Z Coordinate
This command syntax specifies the Z coordinate of an environmental sensor. config:# externalsensor <n> zlabel "<coordinate>"
Variables:
ï‚·
<n> is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16.
ï‚·
Depending on the Z coordinate format you set, there are two types of values for the <coordinate> variable:
Type
Free form
Description
<coordinate> is a string comprising up to 24
ASCII printable characters, and it must be enclosed in quotes.
<coordinate> is an integer number in rack units. Rack units
Note: To specify the Z coordinate using the rack units. See
Setting the Z
Coordinate Format for Environmental Sensors
Example
The following command sets the value "The 5th rack" to the Z coordinate of the environmental sensor with the ID number 4 after the Z coordinate's format is set to freeForm. config:# externalsensor 4 zlabel "The 5th rack"
283
284
Chapter 10: Using the Command Line Interface
Changing the Sensor Description
This command syntax provides a description for a specific environmental sensor. config:# externalsensor <n> description "<description>"
Variables:
ï‚·
<n> is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16.
ï‚·
<description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
Example
The following command gives the description "humidity detection" to the environmental sensor with the ID number 4. config:# externalsensor 4 description "humidity detection"
Environmental Sensor Threshold Configuration Commands
A sensor threshold configuration command for environmental sensors begins with sensor externalsensor.
Setting the Sensor's Upper Critical Threshold
This command syntax configures the Upper Critical threshold of a numeric environmental sensor.
Chapter 10: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperCritical <option>
Variables:
ï‚·
<n> 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.
ï‚·
<sensor type> is one of these sensor types: temperature, humidity,
airPressure or air Flow.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<sensortype>)," where XXX is the specified sensor type, and
<sensortype> is the correct sensor type.
ï‚·
<option> is one of the options: enable, disable or a numeric value.
Option
enable disable
A numeric value
Description
Enables the upper critical threshold for the specified environmental sensor.
Disables the upper critical threshold for the specified environmental sensor.
Sets a value for the upper critical threshold of the specified environmental sensor and enables this threshold at the same time.
Example
The following command sets the Upper Critical threshold of the environmental "temperature" sensor with the ID number 2 to 40 degrees
Celsius. It also enables the upper critical threshold if this threshold has not been enabled yet. config:# sensor externalsensor 2 temperature upperCritical 40
Setting the Sensor's Upper Warning Threshold
This command syntax configures the Upper Warning threshold of a numeric environmental sensor.
285
286
Chapter 10: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperWarning <option>
Variables:
ï‚·
<n> 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.
ï‚·
<sensor type> is one of these sensor types: temperature, humidity,
airPressure or air Flow.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<sensortype>)," where XXX is the specified sensor type, and
<sensortype> is the correct sensor type.
ï‚·
<option> is one of the options: enable, disable or a numeric value.
Option
enable disable
A numeric value
Description
Enables the upper warning threshold for the specified environmental sensor.
Disables the upper warning threshold for the specified environmental sensor.
Sets a value for the upper warning threshold of the specified environmental sensor and enables this threshold at the same time.
Example
The following command enables the Upper Warning threshold of the environmental "temperature" sensor with the ID number 4. config:# sensor externalsensor 4 temperature upperWarning enable
Setting the Sensor's Lower Critical Threshold
This command syntax configures the Lower Critical threshold of a numeric environmental sensor.
Chapter 10: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> lowerCritical <option>
Variables:
ï‚·
<n> 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.
ï‚·
<sensor type> is one of these sensor types: temperature, humidity,
airPressure or air Flow.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<sensortype>)," where XXX is the specified sensor type, and
<sensortype> is the correct sensor type.
ï‚·
<option> is one of the options: enable, disable or a numeric value.
Option
enable disable
A numeric value
Description
Enables the lower critical threshold for the specified environmental sensor.
Disables the lower critical threshold for the specified environmental sensor.
Sets a value for the lower critical threshold of the specified environmental sensor and enables this threshold at the same time.
Example
The following command sets the Lower Critical threshold of the environmental "humidity" sensor with the ID number 1 to 15%. It also enables the lower critical threshold if this threshold has not been enabled yet. config:# sensor externalsensor 1 humidity lowerCritical 15
Setting the Sensor's Lower Warning Threshold
This command syntax configures the Lower Warning threshold of a numeric environmental sensor.
287
288
Chapter 10: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> lowerWarning <option>
Variables:
ï‚·
<n> 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.
ï‚·
<sensor type> is one of these sensor types: temperature, humidity,
airPressure or air Flow.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<sensortype>)," where XXX is the specified sensor type, and
<sensortype> is the correct sensor type.
ï‚·
<option> is one of the options: enable, disable or a numeric value.
Option
enable disable
A numeric value
Description
Enables the lower warning threshold for the specified environmental sensor.
Disables the lower warning threshold for the specified environmental sensor.
Sets a value for the lower warning threshold of the specified environmental sensor and enables this threshold at the same time.
Example
The following command disables the Lower Warning threshold of the environmental "humidity" sensor with the ID number 3. config:# sensor externalsensor 3 humidity lowerWarning disable
Setting the Sensor's Deassertion Hysteresis
This command syntax configures the deassertion hysteresis value of a numeric environmental sensor.
Chapter 10: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> hysteresis <value>
Variables:
ï‚·
<n> 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.
ï‚·
<sensor type> is one of these sensor types: temperature, humidity,
airPressure or air Flow.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<sensortype>)," where XXX is the specified sensor type, and
<sensortype> is the correct sensor type.
ï‚·
<value> is a numeric value that is assigned to the hysteresis for the specified environmental sensor. See
What is Deassertion
Hysteresis?
(on page 182) for the function of the deassertion
hysteresis.
Example
The following command sets the deassertion hysteresis of the environmental "temperature" sensor with the ID number 4 to 2 degrees
Celsius. That is, the temperature must drop by at least 2 degrees Celsius below the upper threshold or rise by at least 2 degrees Celsius above the lower threshold before any threshold-crossing event is deasserted. config:# sensor externalsensor 4 temperature hysteresis 2
Setting the Sensor's Assertion Timeout
This command syntax configures the assertion timeout value of a numeric environmental sensor.
289
290
Chapter 10: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> assertionTimeout <value>
Variables:
ï‚·
<n> 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.
ï‚·
<sensor type> is one of these sensor types: temperature, humidity,
airPressure or air Flow.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<sensortype>)," where XXX is the specified sensor type, and
<sensortype> is the correct sensor type.
ï‚·
<value> is a number in samples that is assigned to the assertion timeout for the specified environmental sensor. See
What is
Assertion Timeout?
Example
The following command sets the assertion timeout of the environmental
"temperature" sensor with the ID number 3 to 4 samples. That is, at least
4 consecutive samples must cross a specific current threshold before that threshold-crossing event is asserted. config:# sensor externalsensor 3 temperature assertionTimeout 4
User Configuration Commands
Most user configuration commands begin with user except for the password change command.
Creating a User Profile
This command syntax creates a new user profile. config:# user create <name> <option> <roles>
After performing the user creation command, the EMX prompts you to assign a password to the newly-created user. Then:
1. Type the password and press Enter.
Chapter 10: Using the Command Line Interface
2. Re-type the same password for confirmation and press Enter.
Variables:
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable CANNOT contain spaces.
ï‚·
<option> is one of the options: enable or disable.
Option
enable
Description
Enables the newly-created user profile. disable Disables the newly-created user profile.
ï‚·
<roles> is a role or a list of comma-separated roles assigned to the specified user profile.
Example
The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin
Results:
ï‚·
A new user profile "May" is created.
ï‚·
The new user profile is enabled.
ï‚·
The admin role is assigned to the new user profile.
Modifying a User Profile
A user profile contains various parameters that you can modify.
Tip: You can combine all commands to modify the parameters of a specific user profile at a time. See
Multi-Command Syntax
(on page
291
292
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 <name> 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:
ï‚·
<name> is the name of the user whose settings you want to change.
Example
The following procedure illustrates how to change the password of the user "May."
1. Verify that you have entered the configuration mode. See
Entering the Configuration Mode
2. Type the following command to change the password for the user profile "May." config:# user modify May password
3. Type a new password when prompted, and press Enter.
4. Type the same new password and press Enter.
5. If the password change is completed successfully, the config:# prompt appears.
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.
To change a user's full name, use this command syntax:
config:# user modify <name> fullName "<full_name>"
To change a user's telephone number, use this command syntax:
config:# user modify <name> telephoneNumber "<phone_number>"
To change a user's email address, use this command syntax:
config:# user modify <name> eMailAddress <email_address>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<full_name> is a string comprising up to 32 ASCII printable characters. The <full_name> variable must be enclosed in quotes when it contains spaces.
ï‚·
<phone_number> is the phone number that can reach the specified user. The <phone_number> variable must be enclosed in quotes when it contains spaces.
ï‚·
<email_address> is the email address of the specified user.
Tip: You can combine all commands to modify the parameters of a specific user profile at a time. See
Multi-Command Syntax
(on page
Example
The following command modifies two parameters for the user profile --
May:
293
294
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. config:# user modify <name> enabled <option>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option> is one of the options: true or false.
Option
true false
Description
Enables the specified user profile.
Disables the specified user profile.
Example
The following command enables the user profile -- May. config:# user modify May enabled true
Forcing a Password Change
This command syntax determines whether the password change is forced when a user logs in to the specified user profile next time.
Chapter 10: Using the Command Line Interface config:# user modify <name> forcePasswordChangeOnNextLogin <option>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option> is one of the options: true or false.
Option
true false
Description
A password change is forced on the user's next login.
No password change is forced on the user's next login.
Example
The following command enforces a password change on May's next login. config:# user modify May forcePasswordChangeOnNextLogin true
Modifying the SNMPv3 Settings
There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See
Multi-Command Syntax
To enable or disable the SNMP v3 access to EMX for the specified user:
config:# user modify <name> snmpV3Access <option1>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option1> is one of the options: enable or disable.
Option
enable disable
Description
Enables the SNMP v3 access permission for the specified user.
Disables the SNMP v3 access permission for the specified user.
295
296
Chapter 10: Using the Command Line Interface
To determine the security level:
config:# user modify <name> securityLevel <option2>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option2> is one of the options: noAuthNoPriv, authNoPriv or
authPriv.
Option Description
noAuthNoPriv No authentication and no privacy. authNoPriv authPriv
Authentication and no privacy.
Authentication and privacy.
To determine whether the authentication passphrase is identical to the password:
config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option3> is one of the options: true or false.
Option
true false
Description
Authentication passphrase is identical to the password.
Authentication passphrase is different from the password.
To determine the authentication passphrase:
Chapter 10: Using the Command Line Interface config:# user modify <name> authenticationPassPhrase <authentication_passphrase>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<authentication_passphrase> is a string used as an authentication passphrase, comprising up to 32 ASCII printable characters.
To determine whether the privacy passphrase is identical to the authentication passphrase:
config:# user modify <name> useAuthenticationPassPhraseAsPrivacyPassPhrase <option4>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option4> is one of the options: true or false.
Option
true false
Description
Privacy passphrase is identical to the authentication passphrase.
Privacy passphrase is different from the authentication passphrase.
To determine the privacy passphrase:
297
298
Chapter 10: Using the Command Line Interface config:# user modify <name> privacyPassPhrase <privacy_passphrase>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<privacy_passphrase> is a string used as a privacy passphrase, comprising up to 32 ASCII printable characters.
To determine the authentication protocol:
config:# user modify <name> authenticationProtocol <option5>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option5> is one of the options: MD5 or SHA-1.
Option
MD5
SHA-1
Description
MD5 authentication protocol is applied.
SHA-1 authentication protocol is applied.
To determine the privacy protocol:
config:# user modify <name> privacyProtocol <option6>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option6> is one of the options: DES or AES-128.
Option
DES
AES-128
Description
DES privacy protocol is applied.
AES-128 privacy protocol is applied.
Example
The following command sets three SNMPv3 prameters of the user "May."
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. config:# user modify <name> roles <roles>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<roles> is a role or a list of comma-separated roles assigned to the specified user profile.
Example
The following command assigns two roles to the user "May." config:# user modify May roles admin,tester
Results:
ï‚·
The user May has the union of all privileges of "admin" and "tester."
Changing the Measurement Units
You can change the measurement units displayed for temperatures, length, and pressure for a specific user profile. Different measurement unit commands can be combined so that you can set all measurement units at a time. To combine all commands, see
Multi-Command Syntax
Note: The measurement unit change only applies to the web interface and command line interface.
299
300
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 <name> preferredTemperatureUnit <option1>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option1> is one of the options: C or F.
Option
C
F
Description
This option displays the temperature in Celsius.
This option displays the temperature in
Fahrenheit.
To set the preferred length unit:
config:# user modify <name> preferredLengthUnit <option2>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option2> is one of the options: meter or feet.
Option
meter feet
Description
This option displays the length or height in meters.
This option displays the length or height in feet.
To set the preferred pressure unit:
config:# user modify <name> preferredPressureUnit <option3>
Variables:
ï‚·
<name> is the name of the user whose settings you want to change.
ï‚·
<option3> is one of the options: pascal or psi.
Option
pascal
Description
This option displays the pressure value in Pascals
(Pa).
Chapter 10: Using the Command Line Interface
Option
psi
Description
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.
Setting Up User Preferences (Units of Measure)
Change user preferences: config:# user modify admin preferredTemperatureUnit C or F config:# user modify admin preferredLengthUnit meter or feet config:# user modify admin preferredPressureUnit pascal or psi
Change default preferences: config:# user defaultPreferences preferredPressureUnit pascal or psi
Specifying the SSH Public Key
If the SSH key-based authentication is enabled, specify the SSH public key for each user profile using the following procedure.
To specify the SSH public key for a specific user:
1. Type the SSH public key command as shown below and press
Enter. config:# user modify <name> sshPublicKey
2. The system prompts you to enter the contents of the SSH public key.
Do the following to input the contents:
301
302
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. See
Determining the SSH Authentication Method
SSH public key contents should be different from the contents displayed in this example.
To specify the SSH public key for the user "May":
1. Make sure you have entered the configuration mode. See
Entering the Configuration Mode
2. Type the following command and press Enter. config:# user modify May sshPublicKey
1. The system prompts you to enter the contents of the SSH public key.
2. Open the SSH public key using a text editor. You should see the
SSH public key contents similar to the following.
3. Select and copy all contents of the SSH public key.
4. Paste the contents in the terminal.
5. Press Enter.
Chapter 10: Using the Command Line Interface
Deleting a User Profile
This command syntax deletes an existing user profile. config:# user delete <name>
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. config:# password
After performing this command, the EMX prompts you to enter both current and new passwords respectively.
Important: After the password is changed successfully, the new password is effective immediately no matter you type the command
"apply" or not to save the changes.
Example
This procedure changes your own password:
1. Verify that you have entered the configuration mode. See
Entering the Configuration Mode
2. Type the following command and press Enter. config:# password
3. Type the existing password and press Enter when the following prompt appears.
Current password:
4. Type the new password and press Enter when the following prompt appears.
Enter new password:
5. Re-type the new password for confirmation and press Enter when the following prompt appears.
303
304
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 <local>]
# show user admin details
[...]
Preferred temperature unit: deg C
Preferred length unit: Meter
Preferred pressure unit: Pascal
[...]
# config config:# user modify admin preferredTemperatureUnit
C F config:# user modify admin preferredTemperatureUnit C config:# user modify admin preferredLengthUnit meter feet config:# user modify admin preferredLengthUnit meter config:# user modify admin preferredPressureUnit pascal psi config:# user modify admin preferredPressureUnit pascal config:# apply
#
Time Configuration Commands
A time configuration command begins with time.
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 <method>
Variables:
ï‚·
<method> is one of the time setup options: manual or ntp.
Mode
manual ntp
Description
The date and time settings are customized.
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. config:# time method ntp
Setting the NTP Parameters
A time configuration command that is used to set the NTP parameters begins with time ntp.
Specifying the Primary NTP Server
This command syntax specifies the primary time server if synchronization with the NTP server is enabled. config:# time ntp firstServer <first_server>
Variables:
ï‚·
The <first_server> is the IP address or host name of the primary
NTP server.
305
306
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 <second_server>
Variables:
ï‚·
The <second_server> is the IP address or host name of the secondary NTP server.
Example
The following command sets the secondary time server to
192.168.80.78. config:# time ntp secondServer 192.168.80.78
Overriding the DHCP-Assigned NTP Servers
This command syntax determines whether the customized NTP server settings override the DHCP-specified NTP servers. config:# time ntp overrideDHCPProvidedServer <option>
Variables:
ï‚·
<option> is one of these options: true or false.
Mode
true false
Description
Customized NTP server settings override the
DHCP-specified NTP servers.
Customized NTP server settings do NOT override the DHCP-specified NTP servers.
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. config:# role create <name> <privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, that privilege should be followed by a colon and the argument(s). config:# role create <name> <privilege1>:<argument1>,<argument2>...;
<privilege2>:<argument1>,<argument2>...;
<privilege3>:<argument1>,<argument2>...;
...
Variables:
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
ï‚·
<privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See
All Privileges
ï‚·
<argument1>, <argument2> and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.
All Privileges
This table lists all privileges.
Privilege
adminPrivilege
Description
Administrator Privileges
307
308
Chapter 10: Using the Command Line Interface
Privilege
changeAssetStripConfiguration changeAuthSettings changeDataTimeSettings changeEmdConfiguration changeEventSetup changeExternalSensorsConfiguratio n changeLhxConfiguration changeNetworkSettings changePassword changeSecuritySettings changeSnmpSettings changeUserSettings changeWebcamSettings clearLog firmwareUpdate performReset viewEventSetup viewLog viewSecuritySettings viewSnmpSettings viewUserSettings viewWebcamSettings
Description
Change Asset Strip
Configuration
Change Authentication Settings
Change Date/Time Settings
Change EMD Configuration
Change Event Settings
Change External Sensors
Configuration
Change LHX Configuration
Change Network Settings
Change Own Password
Change Security Settings
Change SNMP Settings
Change Local User
Management
Change Webcam Configuration
Clear Local Event Log
Firmware Update
Reset (Warm Start)
View Event Settings
View Local Event Log
View Security Settings
View SNMP Settings
View Local User Management
View Webcam Images and
Configuration
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.
To modify a role's description:
config:# role modify <name> description "<description>"
Variables:
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
ï‚·
<description> is a description comprising alphanumeric characters.
The <description> variable must be enclosed in quotes when it contains spaces.
To add more privileges to a specific role:
config:# role modify <name> addPrivileges
<privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege.
309
310
Chapter 10: Using the Command Line Interface config:# role modify <name> addPrivileges
<privilege1>:<argument1>,<argument2>...;
<privilege2>:<argument1>,<argument2>...;
<privilege3>:<argument1>,<argument2>...;
...
Variables:
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
ï‚·
<privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See
All Privileges
ï‚·
<argument1>, <argument2> and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.
To remove specific privileges from a role:
config:# role modify <name> removePrivileges
<privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege.
Chapter 10: Using the Command Line Interface config:# role modify <name> removePrivileges
<privilege1>:<argument1>,<argument2>...;
<privilege2>:<argument1>,<argument2>...;
<privilege3>:<argument1>,<argument2>...;
...
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.
Variables:
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
ï‚·
<privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See
All Privileges
ï‚·
<argument1>, <argument2> and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.
Example
The following command modifies the privileges of the role "tester." config:# role modify tester addPrivileges changeAuthSettings removePrivileges firmwareUpgrade
Results:
ï‚·
The "changeAuthSettings" (Change Authentication Settings) privilege is added to the role.
ï‚·
The "firmwareUpgrade" (Firmware Upgrade) privilege is removed from the role.
Deleting a Role
This command syntax deletes an existing role. config:# role delete <name>
311
312
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.
Setting the Serial Port Baud Rate
The following command syntax sets the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the EMX device. Change the baud rate before connecting it to any Raritan device, such as Raritan's
P2CIM-SER, through the serial port, or there are communications errors.
If you change the baud rate dynamically after the connection has been made, you must reset the EMX or power cycle the other Raritan device for proper communications. config:# serial baudRate <baud_rate>
Variables:
ï‚·
<baud_rate> is one of the baud rate options: 1200, 2400, 4800,
9600, 19200, 38400, 57600, 115200.
Note: The serial port setting is especially useful when the EMX works in conjunction with Raritan's Dominion LX KVM switch. The Dominion LX only supports 19200 bps for communications over the serial interface.
Example
The following command sets the baud rate of the EMX device's serial port to 9600 bps. config:# serial baudRate 9600
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 <n> name "<name>"
Variables:
ï‚·
<n> 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.
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
Example
This command syntax names or changes the name of an asset sensor connected to the EMX device. config:# assetStrip 1 name "Red Rack"
Specifying the Number of Rack Units
This command syntax specifies the total number of rack units on an asset sensor connected to the EMX device. config:# assetStrip <n> numberOfRackUnits <number>
Note: For the Raritan asset sensor, a rack unit refers to a tag port.
Variables:
ï‚·
<n> is the number of the FEATURE port where the selected asset sensor is physically connected. For the EMX device with only one
FEATURE port, the number is always 1.
ï‚·
<number> is the total number of rack units available on the connected asset sensor. This value ranges from 8 to 64.
313
314
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. config:# assetStrip <n> rackUnitNumberingMode <mode>
Variables:
ï‚·
<n> 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.
ï‚·
<mode> is one of the numbering modes: topDown or bottomUp.
Mode
topDown bottomUp
Description
The rack units are numbered in the ascending order from the highest to the lowest rack unit.
The rack units are numbered in the descending order from the highest to the lowest rack unit.
Example
The following command causes the rack units of the asset sensor #1 to be numbered in an ascending order from the one closest to the asset sensor's RJ-45 connector to the farthest one. That is, the rack unit that is most close to the RJ-45 connector is numbered 1. config:# assetStrip 1 rackUnitNumberingMode topDown
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 <n> rackUnitNumberingOffset <number>
Variables:
ï‚·
<n> 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.
ï‚·
<number> is a starting number for numbering rack units on the connected asset sensor. This value is an integer number.
Example
The following command specifies the starting number of rack units of the asset sensor #1 to be 5. That is, the rack units are numbered 5, 6, 7 and so on from the first to the final rack unit on the asset sensor #1. config:# assetStrip 1 rackUnitNumberingOffset 5
Specifying the Asset Sensor Orientation
This command syntax specifies the orientation of the asset sensors connected to the EMX device. Usually you do not need to perform this command unless your asset sensors do NOT come with the tilt sensor, causing the EMX unable to detect the asset sensors' orientation. config:# assetStrip <n> assetStripOrientation <orientation>
Variables:
ï‚·
<n> 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.
ï‚·
<orientation> is one of the options: topConnector or
bottomConnector.
Orientation
topConnector
Description
This option indicates that the asset sensor is mounted with the RJ-45 connector located on the top.
315
316
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. A rack unit configuration command begins with rackUnit.
Naming a Rack Unit
This command syntax assigns or changes the name of the specified rack unit on the specified asset sensor. config:# rackUnit <n> <rack_unit> name "<name>"
Variables:
ï‚·
<n> 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.
ï‚·
<rack_unit> is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
ï‚·
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
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. config:# rackUnit <n> <rack_unit> LEDOperationMode <mode>
Variables:
ï‚·
<n> 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.
ï‚·
<rack_unit> is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
ï‚·
<mode> is one of the LED modes: automatic or manual.
Mode
automatic manual
Description
This option makes the LED of the specified rack unit follow the global LED color settings. See
Global LED Color Settings.
This is the default.
This option enables selection of a different LED color and LED mode for the specified rack unit.
When this option is selected, see
Setting an LED
Color for a Rack Unit
Setting an LED Mode for a Rack Unit
set different LED settings.
Example
The following command allows the rack unit whose index number is 25 on the asset sensor#1 to have a different LED color and mode. config:# rackUnit 1 25 LEDOperationMode manual
317
318
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 <n> LEDColorForDisconnectedTags <color>
Setting an LED Color for a Rack Unit
This command syntax sets the LED color for a specific rack unit on the specified asset sensor. You need to set a rack unit's LED color only when the LED operation mode of this rack unit has been set to "manual." config:# rackUnit <n> <rack_unit> LEDColor <color>
Variables:
ï‚·
<n> 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.
ï‚·
<rack_unit> is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
ï‚·
<color> is the hexadecimal RGB value of a color in HTML format.
The <color> variable ranges from #000000 to #FFFFFF.
Note: A rack unit's LED color setting overrides the global LED color setting on it. See Global LED Color Settings.
Example
The following command sets the LED color of the rack unit whose index number is 25 on the asset sensor#1 to PINK (that is, FF00FF). config:# rackUnit 1 25 LEDColor #FF00FF
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 <n> <rack_unit> LEDMode <mode>
Variables:
ï‚·
<n> 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.
ï‚·
<rack_unit> is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
ï‚·
<mode> is one of the LED modes: on, off, blinkSlow or blinkFast.
Mode
on off blinkSlow blinkFast
Example
Description
This mode has the LED stay lit permanently.
This mode has the LED stay off permanently.
This mode has the LED blink slowly.
This mode has the LED blink quickly.
The following command causes the LED of the rack unit whose index number is 25 on the asset sensor#1 to blink quickly. config:# rackUnit 1 25 LEDMode blinkFast
319
320
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 <n>
Variables:
ï‚·
<n> is an integer number between 1 and 250.
ï‚·
If you leave the <n> 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.
A multi-command syntax looks like this:
<setting 1> <value 1> <setting 2> <value 2> <setting
3> <value 3> ...
Example 1 - Combination of IP, Subnet Mask and Gateway Parameters
The following multi-command syntax configures IPv4 address, subnet mask and gateway for the network connectivity simultaneously. config:# network ipv4 ipAddress 192.168.84.225 subnetMask
255.255.255.0 gateway 192.168.84.0
Results:
ï‚·
The IP address is set to 192.168.84.225.
ï‚·
The subnet mask is set to 255.255.255.0.
ï‚·
The gateway is set to 192.168.84.0.
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. The difference is that "apply" saves all changes you made in the configuration mode while "cancel" aborts all changes.
To quit the configuration mode, use either command:
config:# apply
-- OR -- config:# cancel
The # prompt appears after pressing Enter, indicating that you have entered the administrator mode.
Unblocking a User
If any user is blocked from accessing the EMX, you can unblock them at the local console.
To unblock a user:
1. Log in to the CLI interface using any terminal program via a local connection. See
With HyperTerminal
2. When the Username prompt appears, type unblock and press
Enter.
321
322
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. Ensure you have entered the administrator mode and the # prompt is displayed.
2. Type either of the following commands to restart the EMX device.
# reset unit
-- OR --
# reset unit /y
3. If you entered the command without "/y" in Step 2, a message appears prompting you to confirm the operation. Type y to confirm the reset.
4. Wait until the Username prompt appears, indicating the reset is complete.
Resetting to Factory Defaults
This command restores all settings of the EMX device to factory defaults.
To reset EMX settings, use either command:
# reset factorydefaults
-- OR --
# reset factorydefaults /y
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. Type diag and press Enter. The diag> prompt appears, indicating that you have entered the diagnostic mode.
3. Now you can type any diagnostic commands for troubleshooting.
Diagnostic Commands
The diagnostic command syntax varies from command to command.
Querying the DNS Servers
This command syntax queries Internet domain name server (DNS) information of a network host. diag> nslookup <host>
Variables:
ï‚·
<host> is the name or IP address of the host whose DNS information you want to query.
Example
The following command checks the DNS information regarding the host
192.168.84.222. diag> nslookup 192.168.84.222
323
324
Chapter 10: Using the Command Line Interface
Showing the Network Connections
This command syntax displays network connections and/or status of ports. diag> netstat <option>
Variables:
ï‚·
<option> is one of the options: ports or connections.
Option
ports connections
Example
Description
Shows TCP/UDP ports.
Shows network connections.
The following command displays the server connections to your EMX device. diag> netstat connections
diag>
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 <host>
Variables:
ï‚·
<host> is the host name or IP address whose networking connectivity you want to check.
Options:
ï‚·
You can include any or all of additional options listed below in the ping command.
Options Description
count <number1> Determines the number of messages to be sent. <number1> is an integer number. size <number2> Determines the packet size. <number2> is an integer number in bytes. timeout <number3> Determines the waiting period before timeout. <number3> is an integer number in seconds.
The command looks like this syntax when it includes all options: ping <host> count <number1> size <number2> timeout <number3>
Example
The following command checks the network connectivity of the host
192.168.84.222 by sending the ICMP ECHO_REQUEST message to the host for 5 times. diag> ping 192.168.84.222 count 5
325
326
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 <host>
Variables:
ï‚·
<host> 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.222
Quitting the Diagnostic Mode
To quit the diagnostic mode, use this command:
diag> exit
The # prompt appears after pressing Enter, indicating that you have entered the administrator mode.
Querying Available Parameters for a Command
If you are not sure what commands or parameters are available for a particular type of CLI command, you can have the CLI show them by adding a space and then a question mark or the word "help" to the end of that command. A list of available parameters and their descriptions will be displayed.
The following shows a few query examples.
To query available parameters for the "show" command, the syntax is:
# show ?
OR
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.
Automatically Completing a Command
A CLI command always consists of several words. For some unique CLI commands, such as the "reset" command, you can easily complete them by pressing the Tab or Ctrl+i instead of typing the whole command word by word.
To have a unique command completed automatically:
1. Type initial letters or words of the command. For example, type the first word of the "reset factorydefaults" command, that is, reset.
2. Press Tab or Ctrl+i until the complete command appears. For example, although you typed only one word for the reset command, the rest of the command appears after pressing Tab or Ctrl+i.
327
328
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. For information on CLI, see
Using the Command Line Interface
To reset to factory defaults using the CLI command:
1. Connect a computer to the EMX device. See
Connecting the EMX to a Computer
2. Launch a terminal emulation program such as HyperTerminal,
Kermit, or PuTTY, and open a window on the EMX.
3. Log in to the CLI by typing the user name "admin" and its password.
See Step 4 of
Initial Network Configuration
4. After the # system prompt appears, type either of the following commands and press Enter.
5. Type:
# reset factorydefaults
OR
# reset factorydefaults /y
6. Wait until the Username prompt appears, indicating the reset is complete.
7. If you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset.
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. Once the asset tags are adhered to items, plugged in to asset management sensors, and the asset management sensors are configured in EMX, you can remotely track the item's location.
In EMX, a Feature port is identified with a combination of the name
"Asset Strip" and the port number.
After connecting an asset sensor, you must provide the total number of rack units (tag ports) the connected asset sensor has to the EMX device.
If necessary, you can also manually change the LED color settings for a specific rack unit on the asset sensor to make that LED behave differently from other LEDs.
A daisy chain AMS-M2-Z asset sensors is supported by the EMX. See
AMS-M2-Z Daisy-Chain Limitations
(on page 334) for information on
AMS-M2-Z daisy chain limitations. Once connected, EMX recognizes each AMS-M2-Z asset sensor that is part of the chain. Blade extensions can be connected to each AMS-M2-Z asset sensor in the chains, as needed. As AMS-M2-Z asset sensors are added or removed from the chain, events are generated in EMX.
329
330
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.
Note: In this context, the label refers to the port number where the asset sensor is connected.
To configure an asset sensor:
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. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).
Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.
4. Click Setup in the Settings section. The Setup of Asset Strip dialog appears.
5. Enter a name of the asset sensor.
6. 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.
7. Determine how to number all rack units on the asset sensor by selecting an option in the Numbering Mode.
 Top-Down: The rack units are numbered in the ascending order from the highest to the lowest rack unit.
 Bottom-Up: The rack units are numbered in the descending order from the highest to the lowest rack unit.
8. 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.
9. 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 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.
 Bottom Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.
10. To change the LED color denoting the presence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color with connected Tag" field.
11. To change the LED color denoting the absence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color without connected Tag" field.
12. Click OK to save the changes.
331
332
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. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).
Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.
4. Select the rack unit whose LED settings you want to change.
5. Click Configure Rack Unit or double-click the selected rack unit. The setup dialog for the selected rack unit appears.
6. In the Name field, type a name for identifying this rack unit.
7. 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.
 Manual Override: This option differentiates this LED's behavior.
After selecting this option, you must select an LED mode and/or an LED color for the selected rack unit.
 LED Mode: Select On to have the LED stay lit, Off to have it stay off, "Slow blinking" to have it blink slowly, or "Fast blinking" to have it blink quickly.
 LED Color: If you select On, "Slow blinking" or "Fast blinking" in the LED Mode field, select an LED color by either clicking a color in the color palette or typing the hexadecimal RGB value of a color in the accompanying text box.
8. Click OK to save the changes.
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 in the cabinet.
Item
A
B
Description
RJ-45 connectors
Tag ports
To connect the AMS-M2-Z asset sensors to the EMX:
1. Connect the AMS-M2-Z to the EMX via a Category 5e/6 cable. a. Connect one end of the cable to the RJ-45 port labeled "Input" on the AMS-M2-Z. 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
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.
See
AMS-M2-Z Daisy-Chain Limitations
cable length limitations. b. Connect one end of the Category 5e/6 cable to the RJ-45 connector labeled "Output" on the AMS-M2-Z being connected to the EMX.
333
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
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.
334
4. Repeat Step 2 to connect IT devices to the other AMS-M2-Z's in the chain via the asset tags.
AMS-M2-Z Daisy-Chain Limitations
There are some limitations when daisy chaining the AMS-M2-Z asset sensors. The limitations vary according to the Raritan product model connected to the first AMS-M2-Z.
Models
All PDUs whose model names begin with
PX2
EMX2-111
Daisy-chain limitations
ï‚·
Up to 4 AMS-M2-Z can be daisy chained.
ï‚·
The maximum cable length between each AMS-M2-Z in the chain is 2 meters.
ï‚·
Up to 2 AMS-M2-Z can be daisy chained.
ï‚·
The maximum cable length between each AMS-M2-Z in the chain is 2 meters.
Appendix A: Using Raritan Asset Management Sensors with the EMX
Models
EMX2-888
Daisy-chain limitations
ï‚·
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.
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.
To expand a blade extension strip folder:
1. Click the desired asset sensor in the left pane. The selected asset sensor's page opens in the right pane.
2. Locate the rack unit (tag port) where the blade extension strip is connected.
335
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.
336
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.
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.
The diagram illustrates a tag connector cable and a blade extension strip with 16 tag ports.
Tag connector cable
Appendix A: Using Raritan Asset Management Sensors with the EMX
Item
A
B
C
Description
Barcode (ID number) for the tag connector cable
Tag connector
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.
Blade extension strip
Item
D
E
F
Description
Mylar section with the adhesive tape
Tag ports
Cable socket(s) for connecting the tag connector cable
Note: Each tag port on the blade extension strip is labeled a number, which is displayed as the slot number in the 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.
337
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. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape. b. Plug the tag connector of the asset tag into the tag port on the blade extension strip.
338
4. Repeat the above step until all blade servers in the chassis are connected to the blade extension strip via asset tags.
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.
339
Appendix B Integrating EMX and Asset
Management Sensors with dcTrack
In This Chapter
EMX Asset Sensor Management .......................................................... 343
340
Overview
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack 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.
The AMTs are plugged in to an asset management sensor (AMS) mounted on the rack. The asset sensors are then connected to an EMX device and configured in the EMX.
Once the asset management sensors are connected to and configured in
EMX, they can be added to dcTrack where readings are pulled from
EMX to dcTrack.
Note: There may be a short delay between when the asset tag is plugged in to the asset sensor and when that information becomes available in EMX.
341
342
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. Add the EMX to dcTrack as a probe. See
Adding an EMX to EMX
adding the EMX to dcTrack. It is important you add the EMX as a probe in order for the EMX to be recognized and its information retrieved.
4. Once the EMX is added to dctrack, when tags are adhered to an item and plugged in to the asset management sensor connected to the EMX, the tag ID of the asset management sensor is automatically updated in dcTrack. dcTrack, through Power IQ, receives location data via the IP connection to the EMX. EMX receives this data by polling Power IQ every few minutes to pull in new data and display it. See in the diagram.
The items the asset tags are adhered to must be tracked as part of the dcTrack change management workflow, just as with any other device in the data center. This allows dcTrack to manage and monitor the status of the items the tags are adhered to. See the Change Control Process section in the dcTrack User Help for more information.
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.
Note: dcTrack does not support asset management blade extension strips.
Setting Up Asset Sensors in EMX
Before asset sensors can be managed in dcTrack
™
, they must be configured in EMX, and the EMX needs to be added to dcTrack as a probe item.
Configuring Asset Sensors in EMX
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.
Note: In this context, the label refers to the port number where the asset sensor is connected.
See
Connecting Asset Sensors to the EMX
information on connecting asset sensors.
To configure asset sensors:
1. If you have not already done so, log in to the EMX.
2. Connect the asset sensor to the EMX if it is not already.
3. Click on the Feature Ports folder in the navigation tree to expand it.
4. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).
Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.
343
344
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.
 Top-Down: The rack units are numbered in the ascending order from the highest to the lowest rack unit.
 Bottom-Up: The rack units are numbered in the descending order from the highest to the lowest rack unit.
Raritan strongly suggests you select Bottom-Up as the numbering for the rack units because dcTrack numbers rack units from the bottom-up, where rack units are numbered in the descending order from the highest to the lowest rack unit. For example, the top rack unit may be 48 and the bottom rack unit is 1.
The EMX allows you to number racks from the top down (ascending order from the highest to the lowest rack unit), or from the bottom up.
9. In the Numbering Offset field, select the starting number. For example, if you select 3, the first rack unit is numbered 3, the second is numbered 4, the third is numbered 5, and so on until the final number.
10. 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.
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.
 Bottom Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.
11. Determine how to number all rack units on the asset sensor by selecting an option in the Numbering Mode.
 Top-Down: The rack units are numbered in the ascending order from the highest to the lowest rack unit.
 Bottom-Up: The rack units are numbered in the descending order from the highest to the lowest rack unit.
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.
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.
 Bottom Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.
14. To change the LED color denoting the presence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color with connected Tag" field.
15. To change the LED color denoting the absence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color without connected Tag" field.
16. Click OK to save the changes.
See the EMX Help for additional information on using the EMX device.
Setting EMX Asset Sensor LED Colors
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. If you have not already done so, log in to the EMX.
2. Connect the asset sensor to the EMX if it is not already.
3. Click on the Feature Ports folder in the navigation tree to expand it.
4. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).
Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.
5. Select the rack unit whose LED settings you want to change.
345
346
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.
 Manual Override: This option differentiates this LED's behavior.
After selecting this option, you must select an LED mode and/or an LED color for the selected rack unit.
 LED Mode: Select On to have the LED stay lit, Off to have it stay off, "Slow blinking" to have it blink slowly, or "Fast blinking" to have it blink quickly.
 LED Color: If you select On, "Slow blinking" or "Fast blinking" in the LED Mode field, select an LED color by either clicking a color in the color palette or typing the hexadecimal RGB value of a color in the accompanying text box.
9. Click OK to save the changes.
Adding an EMX to dcTrack
Once the asset management sensor has been connected to and configured in the EMX, add the EMX to dcTrack
™
as a probe.
Following are the steps for creating a single EMX and its asset management sensors in dcTrack. If you have a large number of EMXs and asset management sensors to add to dcTrack, consider using the
Import wizard to import multiple devices at once. See Import Wizard for details.
The EMX goes through the change management workflow just like any other item that is added to dcTrack. However, asset sensor readings are available immediately in dcTrack once they are attached to the EMX.
Important: dcTrack recognizes EMX devices as probes, so it is important to add them as such.
The asset management sensors that are detected by dcTrack are listed in the Temp/Humidity section of the Probes list page in Classic View.
After adding a Humidity/Temperature sensor to an EMX make sure that the Order column is set exactly to the same order appearing in the EMX
To add the EMX to dcTrack as a probe:
1. Open dcTrack Classic View.
2. From the Explorer menu, select Environ. Items > Probe.
3. Select Add from the Page Mode drop-down in the toolbar.
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. If login credentials are required to access the EMX or you are using
SNMP on the EMX, click the EMX Credentials and SNMP v3
Settings button to open the EMX Credentials and SNMP v3 Settings dialog.
Note: For SNMP v2, enter the SNMP v2 community string in the
DataPort field for that probe when you create a data port.
a. Enter the username, password and password confirmation information for the login credentials (if applicable). b. Enable or disable the use of the device's SNMP settings.
9. Click Create Ports. The Create Ports dialog opens. a. Select Asset Strip from the Port Type drop-down. b. Enter a name for the port. Required c. Select the cabinet and position of the port. Required d. Enter comments as needed. e. Click Create Port. A confirmation that the port was created is at the top of the dialog. Click Close.
10. Create a comm port for the EMX and assign it the IP address used to locate the device on the network. Click Create Ports in the Comm
Ports section of the page. The Create Ports dialog appears.
Note: After adding a Humidity/Temperature sensor to an EMX, make sure that the Order column in dcTrack is the same order on the EMX.
a. Create the port manually or by selecting it from the port library.
 Manually select or enter the port name in the Port Name dropdown, then select the connector, media, protocol and speed.
Required
Or
 If the port is available in the Port Library, it is displayed in the
"Create from the Model's Port Definition in the Library" list at the bottom of the dialog. Select the appropriate port and click Use
Selected. a. Assign an IP address to the port. Required
347
348
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.
Note: After adding a Humidity/Temperature sensor to an EMX, make sure that the Order column in dcTrack is the same order on the EMX.
c. Click Create Port.
11. Click Detail 2 to open the Detail 2 page for the EMX, then enter any additional information that is needed. Optional
12. Click Save. The saved item is tagged with a status of New. The item appears in red on the cabinet elevation, which indicates that the item is new.
Appendix C Raritan PX Asset Management
Overview
In This Chapter
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.
Important: When handling asset sensors that are connected to each, put as little stress as possible on the joints between the asset sensors in order to avoid them breaking at the connection point.
Letter
A
B
C
D
Item
The Dominion PX device
Asset sensors
Asset tags
IT devices, such as servers
349
350
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. Connect the other end of the cable to the FEATURE port on the Dominion PX device.
For more information on the Dominion PX product, see the Dominion PX documentation that accompanies the Dominion PX device, which can be downloaded from the Raritan website's
Firmware and Documentation section
(
http://www.raritan.com/support/firmware-anddocumentation/
). Or you can access the product's online help in the
Product Online Help section (http://www.raritan.com/support/onlinehelp/).
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
Altitude Correction Factors (EMX)
If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device can serve as an altitude correction factor. That is, the reading of the differential air pressure sensor will be multiplied by the correction factor to get a correct reading.
This table shows the relationship between different altitudes and correction factors.
Altitude (meters)
0
250
425
500
740
1500
2250
3000
Altitude (feet)
0
820
1394
1640
2428
4921
7382
9842
Correction factor
0.95
0.98
1.00
1.01
1.04
1.15
1.26
1.38
Maximum Ambient Operating Temperature (EMX)
The maximum ambient operating temperature (TMA) for the EMX is the same for all models regardless of the certification standard (CE or UL).
Specification
Max Ambient Temperature
Measure
60 degrees Celsius
351
352
Appendix D: Specifications
Serial RS-232 Port Pinouts
RS-232 Pin/signal definition
Pin No. Signal Direction Description
7
8
5
6
9
3
4
1
2
DCD
RxD
TxD
DTR
GND
DSR
RTS
CTS
RI
Input
Input
Output
Output
―
Input
Output
Input
Input
Data
Receive data (data in)
Transmit data
Data terminal ready
Signal ground
Data set ready
Request to send
Clear to send
Ring indicator
Sensor RJ-12 Port Pinouts
4
5
6
2
3
RJ-12 Pin/signal definition
Pin No. Signal Direction Description
1 +12V
―
GND
―
―
―
Power
(500mA, fuse protected)
Signal Ground
―
―
GND
1-wire
―
―
―
Signal Ground
Used for Feature Port
RS-485 Port Pinouts
1
2
RS-485 Pin/signal definition
Pin No. Signal Direction Description
―
―
―
―
―
―
RS-485 Pin/signal definition
3 D+ bidirectional
4
5
―
―
―
―
6
7
8
D-
―
― bidirectional
―
―
Data +
―
―
Data -
―
―
Appendix D: Specifications
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 .................................... 354
Step B. Configure User Groups on the AD Server ............................... 355
Step C. Configure LDAP Authentication on the EMX Device ............... 356
Step D. Configure User Groups on the EMX Device ............................ 358
Step A. Determine User Accounts and Groups
Determine the user accounts and groups that are authenticated for accessing the EMX. In this example, we will create two user groups with different permissions. Each group will consist of two user accounts available on the AD server.
User groups
EMX_User
User accounts (members)
usera emxuser2
EMX_Admin userb emxuser
Group permissions:
ï‚·
The EMX_User group will only have read-only permissions.
ï‚·
The EMX_Admin group will have full system permissions.
354
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.
Note: See the documentation or online help accompanying Microsoft
AD for detailed instructions.
2. Add the emxuser2 and usera accounts to the EMX_User group.
3. Add the emxuser and userb accounts to the EMX_Admin group.
4. Verify whether each group comprises correct users.
355
356
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
Role of a DNS
Server
ï‚·
The AD server's domain name is techadssl.com, and its IP address is 192.168.56.3.
ï‚·
The AD protocol is NOT encrypted over SSL.
ï‚·
The AD server uses the default TCP port 389.
ï‚·
Anonymous bind is used.
To configure LDAP authentication:
1. Choose Device Settings > Security > Authentication. The
Authentication Settings dialog appears.
2. Select the LDAP radio button to activate remote LDAP/LDAPS server authentication.
3. Click New to add an LDAP/LDAPS server for authentication. The
"Create new LDAP Server Configuration" dialog appears.
4. Provide the EMX with the information about the AD server.
 IP Address / Hostname - Type the domain name techadssl.com or IP address 192.168.56.3.
Important: Without the SSL encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the SSL encryption is enabled.
 Use settings from LDAP server - Leave the checkbox deselected.
 Type of LDAP Server - Select "Microsoft Active Directory" from the drop-down list.
 LDAP over SSL - Have the checkbox deselected since the SSL encryption is not applied in this example.
 Port - Ensure the field is set to 389.
 SSL Port and Server Certificate - Skip the two fields since the
SSL encryption is not enabled.
 Use Bind Credentials - Do NOT select this checkbox because anonymous bind is used.
 Bind DN, Bind Password and Confirm Bind Password -- Skip the three fields because anonymous bind is used.
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. The subfilter information is also useful for filtering out additional objects in a large directory structure. In this example, we leave it blank.
 Active Directory Domain - Type techadssl.com.
357
358
Appendix E: LDAP Configuration Illustration
Note: For more information on LDAP configuration, see
Setting Up
LDAP Authentication
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. To ensure proper synchronization, administrators should configure the EMX and the LDAP server to use the same NTP server.
Step D. Configure User Groups on the EMX Device
A role on the EMX device determines the system permissions. You must create the roles whose names are identical to the user groups created for the EMX on the AD server or authorization will fail. Therefore, we will create the roles named EMX_User and EMX_Admin on the EMX device.
In this illustration, we assume:
ï‚·
Users assigned to the EMX_User role can only access the EMX device and view settings.
ï‚·
Users assigned to the EMX_Admin role can both access and configure the EMX device because they have the Administrator permissions.
To create the EMX_User role with appropriate permissions assigned:
1. Choose User Management > Roles. The Manage Roles dialog appears.
Tip: You can also access the Manage Roles dialog by clicking the
Manage Roles button in the Edit User 'XXX' dialog.
2. Click New. The Create New Role dialog appears.
3. Type EMX_User in the Role Name field.
4. Type a description for the EMX_User role in the Description field. In this example, we type "The role can only view EMX settings" to describe the role.
5. Click the Privileges tab to select all View XXX permissions (where
XXX is the name of the setting). A View XXX permission lets users view the XXX settings without the capability to configure or change them. a. Click Add. The "Add Privileges to new Role" dialog appears. b. Select a permission beginning with the word "View" from the
Privileges list, such as View Event Settings.
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.
359
360
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. Select the permission named Administrator Privileges from the
Privileges list. c. Click Add.
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.
361
Index
A
A Note about Untriggered Rules • 158
About C ontact 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
Asset Management Commands • 312
Asset Management In formation • 49
Asset Sensor Management • 313
Asset Sensor Settings • 221
Asset Sensors and Tags • 329
Automatically Completing a Command • 327
B
Backup and Restore the EMX Device Settings
• iii, 96
Before You Begin • 7
Blade Extension Strip Settings • 229
Browser-
Defined Shortcut Menu • 60
C
Cascading EMX Devices • 163
Cascading PX2 Devices with a EMX • 163
Certificate Signing Request • 118
Changing a Specific LED's Color Settings •
332
Changing a User's Password • 292
Changing the Default Policy • 105, 113, 114
Changing the Device Name • 232
Changing the HTTP Port • 252
Changing the HTTP(S) Settings • 84
Changing the HTTPS Port • 252
Changing the LAN Duplex Mode • 251
Changing the LAN Interface Speed • 250
Changing the Measurement Units • 74, 75,
299
Changi ng the Role(s) • 299
Changing the Sensor Description • 284
Changing the Sensor Name • 280
Changing the SSH Configuration • 253
Changing the SSH Port • 254
Changing the SSH Settings • 65, 90
Changing the Telnet Configuration • 252
Changing the Telnet Port • 253
Changing the Telnet Settings • 91
Changing the User List View • 68
Changing Your Own Password • 303
Changing Your Password • 53
Checking Server Monitoring States • 168
Clearing Event Entries • 159
Clearing the PM710 Energy Accumulators •
200
Closing a
Serial Connection • 215
Combining Asset Sensors • 22
Command History • 229
Components of an Event Rule • 131
Configuring a Contact Closure Sensor
• 37,
180
Configuring Asset Sensors in EMX • 343
Configuring Environmental Sensors • 34, 59,
170, 172, 182
Co nfiguring IP Protocol Settings • 235
Configuring LHX Temperature and Fan
Thresholds • 182, 194
Configuring SNMP Notifications
• 167, 204
Configuring the Asset Sensor • 26, 28, 330
Configuring the EMX • 11, 80
Configuring the EMX Device and Network •
231
Co nfiguring the Firewall • 105
Configuring the IPv4 Parameters • 243
Configuring the IPv6 Parameters • 247
Configuring the PM710 and Configuring
Threshold Settings • 199
Configuring the Serial Port
• 169
Configuring the SMTP Settings • 92, 137, 139
Configuring the SNMP Settings, Traps and
Informs • iii, 63, 85, 136
Configuring Users for Encrypted SNMP v3 •
86, 202, 208
Configuring Webcam Storage • iii, 184, 186,
188
Configuring Webcams • 41, 185, 187, 188,
189
363
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-CC2-
TR
• 36
Connecting Differential Air Pressure Sensors •
40
Connecting Environmental Sensors (Optional)
• 33, 169
Connecting the EMX to a Computer • 12, 102,
328
Connecting the EMX to a Power Source • 11
Connecting the EMX to Your Network • 14, 78,
79
Connecting Third-
Party Detectors/Switches •
35
Connecting Third-Party Detectors/Switches to the EMX • 38, 51, 180
Connection Ports • 43
Contact Closure Senso r LEDs • 39, 51
Contact Closure Sensor Termination • 51
Control Buttons • 47
Controlling the Heat Exchanger • 197
Copying a EMX Configuration • 96
Creating a Certificate Signing Request • 118
Creating a Role • 65, 69, 307
Creating a Self-Signed Certificate
• 120
Creating a User Profile • 51, 62, 66, 67, 69,
70, 75, 91, 208, 290
Creating Actions • 135, 136, 191
Creating an Event Rule • 132, 198
Creating Firewall Rules • 105, 106
Creating Role-
Based Access Control Rules •
113, 115
Creating Rules • 132
D
Data
Pane • 57
Default Log Messages • 129, 139, 148
Deleting a Firewall Rule • 265
Deleting a Role • 71, 311
364
Deleting a Role-
Based Access Control Rule •
280
Deleting a User Profile • 66, 303
Deleting an Event Rule or Action • 158
Deleting Firewall Rules • 110
D eleting Ping Monitoring Settings • 168
Deleting Role-
Based Access Control Rules •
117
Deleting the LDAP Server Settings • 128
Describing the Sensor Location • 173, 175
Determining How to Display Tree Items • 76,
77
Determining the SSH Authentication Method
•
255, 302
Determining the Time Setup Method • 305
Device Configuration Commands • 232
Device States and Icon Variations • 78, 196,
198
Diagnostic Commands • 323
Different CLI Modes and Prompts • 214, 215,
218, 231
Disabling the LDAP Authentication • 128
Displaying the Device Information • 73
Downloading Diagnostic Information • 100
Downloading Key and Certificate Files • 122
Downloading SNMP MIB • 203, 204, 205, 207,
209
E
Editing Firewall Rules • 109
Editing Ping Monitoring Settings • 167
Editing Role-Ba sed Access Control Rules •
116
Editing the LDAP Server Settings • 127
Email and SMS Message Placeholders • iii,
138, 139, 142, 143, 145
EMX and PX2 PDU Cascading Connections • iii, 162
EMX Asset Sensor Management • 343
EMX Device Management • 72
EMX2-
111 • iv
EMX2-
888 • iv
Enabling and Disabling Schroff LHX Heat
Exchanger Support • 77, 192, 209
Enabling and Editing the Security Banner
(Restrictive Service Agreement Banner) • iii,
51, 129
Enabling Data Logging • 176
Enabling IPv4 or IPv6 • 236
Enabling LDAP and Local Authentication
Services • 129
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 S
SH • 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 Fire wall • 105
Enabling User Blocking • 110
Entering the Configuration Mode • 215, 231,
241, 292, 302, 303
Entering the Diagnostic Mode • 215, 323
Environmental Sensor Configuration
Commands • 280
Environmental Sensor Information • 47, 222
Environmental Sensor Threshold
Configuration Commands • 284
Environmental Sensor Threshold Information •
224
Environmental Sensors • 169
Event Logging • 158
Event Rules and Actions • iii, 85, 92, 131, 148,
165, 182, 184, 204
Event Rules, Event Actions and Application
Logs • 131
Example
• 232, 233, 234, 235, 236, 237, 238,
239, 240, 241, 242, 243, 244, 245, 246,
247, 248, 249, 250, 251, 252, 253, 254,
255, 256, 257, 258, 261, 263, 265, 266,
267, 268, 269, 270, 271, 272, 273, 275,
277, 279, 280, 281, 282, 283, 284, 285,
286, 287, 288, 289, 290, 291, 292, 293,
294, 295, 298, 299, 301, 302, 303, 305,
306, 307, 309, 311, 312, 313, 314, 315,
316, 317, 318, 319, 323, 324, 325, 326
Ping Monitoring and SNMP Notifications
•
166
Example 1 -
Basic Security Information • 230
Example 1 - Combination of IP, Subnet Mask and Gateway Parameters • 320
Example 2 - Combination of SSID and PSK
Parameters • 321
Example 2 - In-
Depth Security Information •
231
Examples • 230
Executing an Action Group • 136
Index
Existing Roles • 227
Existing User Profiles • 226
Expanding a Blade Extension Strip • 335
F
Firewall Control • 259
Firmware Upgrade • 96, 97
Forcing a Password Change • 294
Forcing HTTPS Encryption • 84, 104, 118
Full Disaster Recovery • 99
G
Gathering the LDAP Information • 123
Getting Started • 43
GS
M Modems • 191
H
Help Command
• 218
History Buffer Length • 230
How to Display Asset Sensors • 76
How to Display LHX Heat Exchangers • 77
HTTPS Access • 266
I
Identifying Environmental Sensors • 170, 172
Idle Timeout • 268
Information about Update Interval
• 33, 171,
176, 177
Initial Network Configuration • 15, 51, 55, 78,
79, 328
Installing a CA-
Signed Certificate • 120
Installing and Configuring the EMX Device • 7
Installing Existing Key and Certificate Files
•
122
Installing the USB-to-
Serial Driver • 12
Integrating EMX and Asset Management
Sensors with dcTrack • iii, 340
Introduction • 1
Introduction to the Web Interface • 54
IP Address • 49
IP Configuration • 219
L
LAN Interface Settings • 219
Layout • 210
LCD Display • 45, 47, 49
LCD Display Panel • 45
LDAP Configuration Illustration • 126, 354
Listing TCP Connections • 100
Log an Event Message • 137
Logging In • 51
365
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 Passw ord History • 273
Maximum Password Length • 271
Menus • 55
Minimum Password Length • 270
Modifying a Firewall Rule • 263
Modifying a Role • 65, 66, 70, 309
Modifying a Role-
Based Access Control Rule •
277
Modifying a User Profile • 53, 66, 70, 291
Modifyin g a User's Personal Data • 293
Modifying an Action • 157
Modifying an Event Rule • 156
Modifying the Firewall Control Parameters •
260
Modifying the IPv4 Settings • 82
Modifying the IPv6 Settings • 83
Modifying the Network Configuration • 15, 78
Modifying the Network Interface Settings • 78
Modifying the Network Service Settings • 84,
212, 214
Modifying the Network Settings • 55, 80, 356
Modifying the Role-Based Access Control
Parameters • 274
Modifying the SNMPv3 Settings • 295
Monitoring the Heat Exchange r • 194, 196
More Information about AD Configuration •
126
Mounting a 1U EMX Device • 9
Mounting a Zero U EMX Device • 8
Mounting the EMX Device • 7
Multi-
Command Syntax • 261, 266, 269, 275,
291, 293, 295, 299, 320
N
Naming a Heat Exchanger • 193
Naming a
Rack Unit • 316
Naming an Asset Sensor • 313
Naming the EMX Device • 55, 72, 75, 171,
172, 174, 178, 181, 193, 195
Network Configuration • 219
Network Diagnostics • 99
Network Service Settings • 220
Network Troubleshooting • 99, 323
Networking Configurati on Commands • 234
Networking Mode • 219
Numeric Character Requirement • 272
O
Operating Hours • 197
Overriding the DHCP-
Assigned NTP Servers •
306
Overriding the IPv4 DHCP-Assigned DNS
Server • 246
Overriding the IPv6 DHCP-Assigned DNS
Server • 249, 250
Ov erview • 2, 62, 72, 161, 201, 341, 349
P
Package Contents • vi
Password Aging • 267
Password Aging Interval • 268
Pinging a Host • 100
Power Switch • 51
PowerLogic PM710 • iii, 198
Product Features • v
Product Models • iv
Providing the EAP CA Certificate • 240
Q
Querying Available Parameters for a
Command
• 218, 326
Querying the DNS Servers • 323
Quitting the Configuration Mode • 232, 321
Quitting the Diagnostic Mode • 326
R
Rack Unit Configuration • 316
Rack Unit Settings of an Asset Sensor • 228
Raritan P
X Asset Management • 349
Readings Highlighted in Yellow or Red • 58,
61, 177, 196
Rebooting the EMX • 102
366
Record Snapshots to Webcam Storage • 143
Reset Button • 50
Resetting the EMX • 322
Resetting the PM710 Minimum and Maximum
Values • 199
Resetting to F actory 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 C ontrol • 274
RS-
485 Port Pinouts • 352
S
Sample Asset-Management-Level Event Rule
• 154
Sample Event Rules • 154
Sample Sensor-
Level Event Rule • 155
Sample User-Activity-
Level Event Rule • 156
Saving an EMX Configuration • 95
Schroff LHX Heat Exchangers • 42, 58, 143,
192
Security • 104
Security Configuration Commands • 258
Security Settings • 225
Selecting IPv4 or IPv6 Addresses • 236
Selecting the Internet Protocol • 81, 82, 83
Send a Snapshot via Email • 137
Send an SNMP Notification
• 139
Send EMail • 138
Send SMS Message • 142
Sending Videos in an Email or Instant
Message • 184, 190
Sensor Measurement Accuracy
• 178
Sensor RJ-
12 Port Pinouts • 352
Serial
• 225
Serial Port Configuration Commands • 312
Serial RS-
232 Port Pinouts • 352
Server Accessibilit y • 164
Setting an LED Color for a Rack Unit • 317,
318
Setting an LED Mode for a Rack Unit • 317,
319
Setting Data Logging • 176, 234
Setting EMX Asset Sensor LED Colors • 345
Setting the Authentication Method • 238
Setting the BSSID • 242
Setting the Data Logging Measurements Per
Entry • 234
Setting the Date and Time • 73
Index
Setting the EAP Identity • 240
Setting the EAP Parameters • 239
Setting the EAP Password • 240
Setting the History Buffer Length • 320
Setting the Inner Authentication • 239
Setting the
IPv4 Address • 244
Setting the IPv4 Configuration Mode • 243
Setting the IPv4 Gateway • 245
Setting the IPv4 Preferred Host Name • 243
Setting the IPv4 Primary DNS Server • 245
Setting the IPv4 Secondary DNS Server • 246
Setting the IPv4 Subnet Mask • 244
Setting the IPv6 Address • 248
Setting the IPv6 Configuration Mode • 247
Setting the IPv6 Gateway • 248
Setting the IPv6 Primary DNS Server • 249
Setting the IPv6 Secondary DNS Server • 249
Setting the LAN Interface Parameters • 250
Setting the LED Disconn ect Color • 318
Setting the LED Operation Mode • 317
Setting the Network Service Parameters • 251
Setting the Networking Mode • 235
Setting the NTP Parameters • 305
Setting the Outer Authentication • 239
Setting the PSK • 238
Setting the Sensor's Assertion
Timeout • 289
Setting the Sensor's Deassertion Hysteresis •
288
Setting the Sensor's Lower Critical Threshold •
286
Setting the Sensor's Lower Warning Threshold
• 287
Setting the Sensor's Upper Critical Threshold •
284
Setting the Sensor's Upper Warning Threshold
• 285
Setting the Serial Port Baud Rate
• 312
Setting the SNMP Configuration • 255
Setting the SNMP Read Community • 256
Setting the SNMP Write Community • 257
Setting the SSID • 237
Setting the sysContact Value • 257
Setting the sysLocation Value
• 258
Setting the sysName Value • 258
Setting the Wireless Parameters • 237
Setting the X Coordinate • 282
Setting the Y Coordinate • 282
Setting the Z Coordinate • 233, 283
Setting the Z Coordinate Format • 174
Setting the Z Coordinate Format for
Environ mental Sensors • 233, 283
367
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
Showing Information • 218
Showing the Network Connections • 324
Single Login Limitation • 267
SNMP Gets and Sets • 209
SNMP Sets and Thresholds • 211
SNMPv2c Notifications • 205
SNMPv3 Notifications • 206
Sorting Firewall Rules • 109
Sorting Role-
Based Access Control Rules •
117
Sorting the LDAP Access Order • 127
Special Character Requirement • 272
Specifications • 351
Specifying the Asset Sensor Orientation • 315
Specifying the Device Altitude • 74
Specifying the Number of Rack Units • 313
Specifying the Primary NTP Server • 305
Specifying the Rack Unit Numbering Mode •
314
Specifying the Rack Unit Numbering Offset •
315
Specifying the Secondary NTP Server • 306
Specifying the Sensor Type • 281
Specifying the SSH Public Key • 255, 301
States of Managed Sensors • 179
Status Bar • 55
Step A. Determine User Accounts and Groups
• 354
Step B. Configure User Groups on the AD
Server • 355
Step C. Configure LDAP Authentication on the
EMX Device • 356
Step D. Configure User Groups on the EMX
Device • 358
Strong Passwords • 269
Supported Web Browsers • 43
Supported Wireless LAN Configuration • 14
Switch LHX • 143
Syslog Message • 141
T
Taking, Viewing and Managing Webcam
Snapshots • 184, 188
Testing the LDAP Server Connection • 127
Testing the Network C onnectivity • 325
The EMX MIB • 209
Threshold Information • 182, 211
Time Configuration Commands • 304
Tracing the Network Route • 100
Tracing the Route • 326
U
Unblocking a User • 110, 321
Unmanaging Environmental Sensors • 172,
181
Updating the Asset Sen sor Firmware • 99
Updating the Firmware • 97
Uppercase Character Requirement • 271
User and Role Management • 62
User Blocking • 268
User Configuration Commands • 290
Using Raritan Asset Management Sensors with the EMX • 329
Using SNMP • 201
Using the Comm and Line Interface • 84, 175,
212, 328
V
Viewing Connected Users • 68
Viewing Details • 195
Viewing Firmware Update History • 98
Viewing Sensor Data • 177
Viewing the Communication Log • 160
Viewing the Dashboard • 61
Viewing the Local Event Log • 159
View ing the Summary • 195
Viewing Webcam Snapshots and Videos • 187
W
Warning Icon • 57
Webcams • iii, v, 41, 184
What is Assertion Timeout? • 173, 183, 290
What is Deassertion Hysteresis? • 158, 173,
182, 194, 289
What's New in EMX Help • iii
368
Wired Network Se ttings • 78
Wireless Configuration • 220
Wireless Network Settings • 79
With HyperTerminal • 213, 321
With SSH or Telnet • 214
Index
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: [email protected]
Email for all other products: [email protected]
China
Beijing
Monday - Friday
9 a.m. - 6 p.m. local time
Phone: +86-10-88091890
Shanghai
Monday - Friday
9 a.m. - 6 p.m. local time
Phone: +86-21-5425-2499
GuangZhou
Monday - Friday
9 a.m. - 6 p.m. local time
Phone: +86-20-8755-5561
India
Monday - Friday
9 a.m. - 6 p.m. local time
Phone: +91-124-410-7881
Japan
Monday - Friday
9:30 a.m. - 5:30 p.m. local time
Phone: +81-3-3523-5991
Email: [email protected]
Europe
Europe
Monday - Friday
8:30 a.m. - 5 p.m. GMT+1 CET
Phone: +31-10-2844040
Email: [email protected]
United Kingdom
Monday - Friday
8:30 a.m. to 5 p.m. GMT
Phone +44(0)20-7090-1390
France
Monday - Friday
8:30 a.m. - 5 p.m. GMT+1 CET
Phone: +33-1-47-56-20-39
Germany
Monday - Friday
8:30 a.m. - 5:30 p.m. GMT+1 CET
Phone: +49-20-17-47-98-0
Email: [email protected]
Melbourne, Australia
Monday - Friday
9:00 a.m. - 6 p.m. local time
Phone: +61-3-9866-6887
Taiwan
Monday - Friday
9 a.m. - 6 p.m. GMT -5 Standard -4 Daylight
Phone: +886-2-8919-1333
Email: [email protected]
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project