Download Print this page

LEGRAND Raritan SRC-0100 User Manual

LEGRAND Raritan SRC-0100 User Manual

Smart rack controller

Hide thumbs Also See for Raritan SRC-0100:

Quick setup manual (10 pages)

,

Quick setup manual (9 pages)

Table Of Contents

Table of Contents

Advertisement

Quick Links

Smart Rack Controller

User Guide

Xerus

Firmware v3.5.10

™

Copyright © 2019 Raritan, Inc.

SRC_UserGuide_0A_3.5.10_E

May 2019

255-80-0064-00

Table of Contents

Advertisement

Table of Contents

Troubleshooting

Need help?

Need help?

Do you have a question about the Raritan SRC-0100 and is the answer not in the manual?

Questions and answers

Summary of Contents for LEGRAND Raritan SRC-0100

Page 1 Smart Rack Controller User Guide Xerus Firmware v3.5.10 ™ Copyright © 2019 Raritan, Inc. SRC_UserGuide_0A_3.5.10_E May 2019 255-80-0064-00...
Page 2 This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of Raritan, Inc. © Copyright 2019 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
Page 3 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 2019 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
Page 4: Table Of Contents
Contents Chapter 1 Introduction Overview............................1 Product Models..........................3 SRC-0100..........................3 SRC-0102..........................4 Package Contents..........................5 Optional Accessories ......................5 APIPA and Link-Local Addressing ....................6 Before You Begin ..........................7 Chapter 2 Rackmount ...
Page 5 Contents Connecting Door Handles or a SmartLock Kit................43 Limitations ........................... 44 Connecting a SmartLock Kit to DX2-DH2C2................ 45 Connecting Raritan's Door Handles to SRC Onboard Ports ..........47 Connecting Contact Closure Detectors..................48 Connecting Contact Closure Detectors to DX2-DH2C2............
Page 6 Contents Quick Access to a Specific Page ..................106 Sorting a List ........................107 Dashboard ............................ 108 Dashboard - Alerted Sensors .................... 110 Dashboard - Alarms......................111 SRC ............................... 113 Internal Beeper State ......................113 ...
Page 7 Contents Updating the SRC Firmware ....................326 Viewing Firmware Update History ..................329 Bulk Configuration ......................330 Backup and Restore of Device Settings................335 Network Diagnostics......................337 Downloading Diagnostic Information ................338 Hardware Issue Detection ....................338 ...
Page 8 Contents Environmental Sensor Information ................... 386 Environmental Sensor Package Information ..............387 Actuator Information......................388 Environmental Sensor Threshold Information..............389 Environmental Sensor Default Thresholds ............... 390 Security Settings ........................ 391 Authentication Settings...................... 392 ...
Page 9 Contents Unblocking a User ........................519 Resetting the SRC......................... 520 Restarting the Device......................520 Resetting to Factory Defaults .................... 520 Network Troubleshooting......................521 Entering Diagnostic Mode....................521 Quitting Diagnostic Mode....................521 Diagnostic Commands ....................... 522 ...
Page 10 Contents Firmware Upgrade via USB......................552 Appendix C Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................555 TFTP Requirements........................556 DHCP IPv4 Configuration in Windows..................556 DHCP IPv6 Configuration in Windows..................566 ...
Page 11 Contents Setting the Registry to Permit Write Operations to the Schema..........595 Creating a New Attribute......................595 Adding Attributes to the Class ..................... 596 Updating the Schema Cache ......................598 Editing rciusergroup Attributes for User Members ..............598 Appendix H RADIUS Configuration Illustration ...
Page 12 Contents Browsing through the Online Help....................672 Appendix J Integrating Asset Management Strips with Other Products Asset Management Strips and Raritan PDUs ................674 Asset Management Strips and dcTrack ..................675 Index ...
Page 13: Chapter 1 Introduction
Chapter 1 Introduction In This Chapter Overview ......................1 Product Models ...................3 Package Contents..................5 APIPA and Link-Local Addressing ..............6 Before You Begin..................7 Overview Raritan's Smart Rack Controller (SRC) provides a rack management solution that combines the capabilities of environmental monitoring, asset management, image surveillance, event notifications and support for Schroff heat exchangers.
Page 14 Chapter 1: Introduction  You must purchase the SmartLock kit if your model does NOT have onboard door handle ports, such as SRC-0100. Raritan's SmartLock kit contains one DX2-DH2C2 and a pair of door handles. After properly connecting and configuring door handles or the SmartLock kit, you can control the access to the selected cabinet via SRC.
Page 15: Product Models
Chapter 1: Introduction Product Models There are two SRC models:  SRC-0100  SRC-0102 They are functionally identical except that SRC-0100 does NOT have onboard door handle ports and contact closure terminals while the other model has them. Note: For a list of available asset management strips and tags, visit the Raritan website's Product Selector page http://www.findmypdu.com/...
Page 16: Src-0102
Chapter 1: Introduction  Ethernet port x 2 (green and white) Connection Ports For details, see (on page 71). Note: Expansion port is reserved for future use so it does NOT function now. FRONT PANEL LCD and CONTROL BUTTONS: Front panel LCD and buttons let users view real-time device information and/or alerts without logging in to the SRC software.
Page 17: Package Contents
Chapter 1: Introduction  Feature port x 1 (red)  Ethernet port x 2 (green and white) Connection Ports For details, see (on page 71). Note: Expansion port is reserved for future use so it does NOT function now. FRONT PANEL LCD and CONTROL BUTTONS: Front panel LCD and buttons let users view real-time device information and/or alerts without logging in to the SRC software.
Page 18: Apipa And Link-Local Addressing
Chapter 1: Introduction APIPA and Link-Local Addressing SRC supports Automatic Private Internet Protocol Addressing (APIPA). With APIPA, your SRC automatically configures a link-local IP address and a link-local host name when it cannot obtain a valid IP address from any DHCP server in the TCP/IP network. the same subnet Only IT devices connected to can access the SRC using...
Page 19: Before You Begin
Chapter 1: Introduction 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 SRC for cabling and equipment connections.
Page 20: Chapter 2 Rackmount
Chapter 2 Rackmount There are two ways to mount an SRC device, using the same Raritan rackmount brackets.  1U Rackmount Method (on page 8) SRC is mounted like a 1U device in the rack.  0U Rackmount Method (on page 9) SRC is mounted like a 0U device in the rack.
Page 21 Chapter 2: Rackmount 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 other end of the device. 4. After both L-brackets are installed, fasten the device to the rack, using rack screws, through two identical round holes of each L-bracket.
Page 22 Chapter 2: Rackmount 3. Repeat Steps 1 to 2 to screw another L-bracket to the other end of the device. 4. After both L-brackets are installed, fasten the device to the rack, using rack screws, through slots of each L-bracket.
Page 23: Chapter 3 Initial Installation And Configuration
Chapter 3 Initial Installation and Configuration This chapter explains how to install your SRC and configure it for network connectivity. In This Chapter Connecting SRC to Power ................. 11 Connecting the SRC to Your Network ............11 Configuring the SRC .................. 15 Bulk Configuration Methods ..............23 Cascading Multiple SRC Devices for Sharing Ethernet Connectivity ..
Page 24: Usb Wireless Lan Adapters
Chapter 3: Initial Installation and Configuration  The two Ethernet ports must be connected to different subnets. Dual Ethernet Connection (on page 14).  The "green" Ethernet port labeled "ETH 10/100/1000" supports up to 1000 Mbps so it is highly recommended for network connection.
Page 25: Supported Wireless Lan Configuration
Chapter 3: Initial Installation and Configuration Wi-Fi LAN adapters Supported 802.11 protocols Zyxel NWD271N Edimax EW-7722UnD A/B/G/N TP-Link TL-WDN3200 v1 A/B/G/N Raritan USB WIFI A/B/G/N Supported Wireless LAN Configuration If wireless networking is preferred, ensure that the wireless LAN configuration of your SRC matches the access point. The following is the wireless LAN configuration that the SRC supports.
Page 26: Dual Ethernet Connection
Chapter 3: Initial Installation and Configuration Dual Ethernet Connection One SRC device has two Ethernet (LAN) ports:  green ETH 10/100/1000 (marked in ) supports up to 1000 Mbps. This is "ETH1".  ETH 10/100 (marked in white ) supports up to 100 Mbps. This is "ETH2".
Page 27: Configuring The Src
Chapter 3: Initial Installation and Configuration Configuring the SRC You can initially configure the SRC via one of the following:  A TCP/IP network that supports DHCP  A mobile device with PDView installed  A computer physically connected to the SRC Configuration via a DHCP-enabled network: Connecting the SRC 1.
Page 28: Connecting A Mobile Device To Src
Chapter 3: Initial Installation and Configuration Connecting a Mobile Device to SRC Raritan's PDView is a free app that turns your iOS or Android mobile device into a local display for SRC. PDView is especially helpful when your SRC is not connected to the network but you need to check the SRC status, retrieve its information, or change its settings.
Page 29 Chapter 3: Initial Installation and Configuration  Android : USB-B port Step C: Launch PDView to access the SRC 1. Launch the PDView app from your mobile device. Below illustrate iPad's PDView screens. a. The "Disconnected" message displays first when PDView has not detected the SRC yet.
Page 30 Chapter 3: Initial Installation and Configuration Note: PDView also shows the 'Disconnected' status during the firmware upgrade. If so, wait until the firmware upgrade finishes. b. The PDView shows the "Connected" message when it detects the connected SRC. 2. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the web interface of SRC.
Page 31 Chapter 3: Initial Installation and Configuration Saving User Credentials for PDView's Automatic Login When PDView detects SRC for the "first" time, it automatically attempts to log in with the factory-default user credentials -- admin (user name) raritan (password). If you have modified the factory-default user credentials, PDView's automatic login fails and the login screen displays for you to manually enter user credentials.
Page 32 Per default, three administrator user credentials are pre-configured for three companies' products:  Raritan  Legrand  ServerTech (Server Technology) 5. Modify existing user credentials or type new ones, and tap Save.  The pre-configured admin credentials can be removed or...
Page 33: Connecting The Src To A Computer
Chapter 3: Initial Installation and Configuration Connecting the SRC to a Computer The SRC can be connected to a computer for configuration via one of the following ports.  Ethernet ports  USB-B port  RS-232 serial port (RJ-45) To use the command line interface (CLI) for configuration, establish an RS-232 or USB connection.
Page 34 Chapter 3: Initial Installation and Configuration 2. Connect a USB cable between a computer's USB-A port and the USB-B port of SRC. Initial Network Configuration via CLI 3. Perform (on page 657). Note: Not all serial-to-USB converters work properly with the SRC so Raritan does not introduce the use of such converters.
Page 35: Bulk Configuration Methods
Chapter 3: Initial Installation and Configuration Note: The blue Cisco RJ-45 to DB9 adapter cable CANNOT be used for connecting a modem. See RJ45-to-DB9 Cable Requirements for Modem Connections (on page 637). Bulk Configuration Methods If you have to set up multiple SRC devices, you can use one of the following configuration methods to save your time.
Page 36: Cascading Multiple Src Devices For Sharing Ethernet Connectivity
Chapter 3: Initial Installation and Configuration A USB flash drive:  Requirement : A FAT32- or supperfloppy-formatted USB flash drive containing two special configuration files and one devices list file is required.  Procedure : Plug this USB drive into the SRC. When a happy smiley is shown on the front panel display, press and hold one of the control buttons on the front panel until the display turns blank.
Page 37 Chapter 3: Initial Installation and Configuration  The cascading mode of all devices in the chain must be the same.  In the Bridging mode, the master device can have "only one" connection to the network. DO NOT connect both Ethernet ports to the network(s) unless your network has the R/STP protocol enabled.
Page 38: Cascading All Devices Via Usb
Chapter 3: Initial Installation and Configuration Cascading All Devices via USB You must set the cascading mode before establishing the chain. See Setting the Cascading Mode (on page 187). Any certified USB 2.0 cable up to 5 meters (16 feet) long can be used. Both cascading modes support a maximum of 16 devices in a chain.
Page 39 Chapter 3: Initial Installation and Configuration Number Device role Slave 2 Slave 3 To cascade SRC devices via USB: 1. Make sure all Raritan devices are running firmware version 3.3.10 or later. Note that SRC must run 3.5.10 or later. 2.
Page 40 Chapter 3: Initial Installation and Configuration For example, you can have some devices use DHCP-assigned IP addresses and the others use static IP addresses.  Port Forwarding mode: Only the master device's network settings should be configured. A tip for USB cascading: The "USB-cascading"...
Page 41: Extended Cascading With Src Devices
Chapter 3: Initial Installation and Configuration Extended Cascading with SRC Devices SRC supports cascading via either Ethernet or USB ports. This is because they have "two" Ethernet ports. You can use either Ethernet port on the SRC PDU for cascading. You must set the cascading mode before establishing the chain.
Page 42 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3...
Page 43 Chapter 3: Initial Installation and Configuration Cascading All Devices via USB For instructions on USB cascading, see (on page 26). Suggestions for extended cascading:  Ethernet cascading is recommended because of the longer distance, lower latency and more reliable connection it supports. ...
Page 44 Chapter 3: Initial Installation and Configuration  Bridging mode: Each cascaded device has its own network settings. For example, you can have some devices use DHCP-assigned IP addresses and the others use static IP addresses.  Port Forwarding mode: Only the master device's network settings should be configured.
Page 45: Restrictions Of Port-Forwarding Connections
Chapter 3: Initial Installation and Configuration Restrictions of Port-Forwarding Connections The following guidelines must be obeyed for establishing a cascading chain in the Port Forwarding mode.  Each cascaded device, except for the master device, must have only one upstream device. ...
Page 46 Chapter 3: Initial Installation and Configuration  One cascaded device has two upstream devices via Ethernet and USB cables.  One cascaded device has two downstream devices.
Page 47 Chapter 3: Initial Installation and Configuration  One device is connected to another device via two cascading cables - USB and Ethernet cables.
Page 48 Chapter 4 Connecting External Equipment (Optional) More features are available if you connect Raritan's or third-party external equipment to your SRC. In This Chapter Connecting Raritan Environmental Sensor Packages ......37 Connecting Door Handles or a SmartLock Kit.......... 43 Connecting Contact Closure Detectors ............ 48 Connecting Asset Management Strips............
Page 49: Chapter 4 Connecting External Equipment (Optional)
Chapter 4: Connecting External Equipment (Optional) Connecting Raritan Environmental Sensor Packages Raritan's DX or DX2 environmental sensor packages are required for SRC to detect the surrounding condition like the temperature, and/or to control a system or mechanism like door handles. Warning: SRC does NOT support other Raritan environmental sensor packages than DX and DX2 series.
Page 50: Identifying The Sensor Port
Chapter 4: Connecting External Equipment (Optional) Identifying the Sensor Port Warning: If you purchase Raritan's environmental sensor packages, make sure you connect them to the correct port on the SRC, or damages may be caused to SRC and/or connected sensor packages. How to identify the SENSOR port: ...
Page 51 Chapter 4: Connecting External Equipment (Optional) Numbers Components LED, which indicates the sensor package's status Connect DX2 to the SRC: 1. Connect a standard network patch cable (CAT5e or higher) to either RJ-45 port on a DX2 sensor package. 2. If you want to cascade DX2 packages, get an additional standard network patch cable (CAT5e or higher) and then: a.
Page 52 Chapter 4: Connecting External Equipment (Optional) DX2-DH2C2 DX2-DH2C2 is one of DX2 environmental sensor package. It is designed for cabinet access control so it is included in Raritan's SmartLock kit. For information on how to connect door handles and/or contact closure sensors, refer to: ...
Page 53: Dx Sensor Packages
Chapter 4: Connecting External Equipment (Optional) DX Sensor Packages Most DX sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to DX terminals, refer to the Environmental Sensors and Actuators Guide (or Support page Online Help) on Raritan website's http://www.raritan.com/support/ You can cascade up to 12 DX sensor packages.
Page 54: Using An Optional Dpx3-Envhub4 Sensor Hub
Chapter 4: Connecting External Equipment (Optional) a. Plug one end of the cable into the remaining RJ-45 port on the prior DX package. b. Plug the other end into either RJ-45 port on an additional DX package. Repeat the same steps to cascade more DX packages. Exception: You CANNOT cascade DX-PD2C5 sensor packages.
Page 55: Connecting Door Handles Or A Smartlock Kit
Chapter 4: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. A standard network cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages Connecting Door Handles or a SmartLock Kit Raritan's door handles or SmartLock kits are required for SRC to control the access to a cabinet.
Page 56: Limitations
Chapter 4: Connecting External Equipment (Optional)  For SRC without onboard door handle ports, such as SRC-0100, you Connecting a SmartLock Kit to need a SmartLock kit. See DX2-DH2C2 (on page 45).  For SRC with onboard door handle ports, such as SRC-0102, you can only purchase and connect Raritan's door handles instead of a Connecting Raritan's Door Handles to SRC SmartLock kit.
Page 57: Connecting A Smartlock Kit To Dx2-Dh2C2
Chapter 4: Connecting External Equipment (Optional) Connecting a SmartLock Kit to DX2-DH2C2 You need a SmartLock kit if your SRC does NOT include a built-in DX2-DH2C2, such as SRC-0100. Overview: Component Function Two pairs of Connect to third-party contact closure contact closure detectors/switches for detecting the door sensor terminals...
Page 58 Chapter 4: Connecting External Equipment (Optional) Component Function Two RJ-45 ports Connect a standard network patch cable for either or both purposes below:  Connect to the SENSOR port (yellow) of SRC.  Cascade DX2 sensor package(s). DX2 Sensor Packages (on page 38).
Page 59: Connecting Raritan's Door Handles To Src Onboard Ports
Chapter 4: Connecting External Equipment (Optional) Connecting Raritan's Door Handles to SRC Onboard Ports You only need to purchase door handles if your SRC has a built-in DX2-DH2C2, such as SRC-0102. SRC door handle ports and terminals: Component Function Two pairs of Connect to third-party contact closure contact closure detectors/switches for detecting the door...
Page 60: Connecting Contact Closure Detectors
Chapter 4: Connecting External Equipment (Optional) Component Function The two door handles are usually attached to different doors of the same cabinet. Connection procedure: 1. Connect Raritan door handles to onboard door handle ports of SRC. 2. (Optional) Connect contact closure detectors/switches for detecting Connecting door status to contact closure terminals of SRC.
Page 61: Connecting Contact Closure Detectors To Dx2-Dh2C2
Chapter 4: Connecting External Equipment (Optional) Connecting Contact Closure Detectors to DX2-DH2C2 Overview: Component Function Two pairs of Connecting See the table in the topic titled contact closure a SmartLock Kit to DX2-DH2C2 (on page sensor terminals 45). Two door handle ports Two RJ-45 ports...
Page 62: Connecting Contact Closure Detectors To Src Onboard Terminals
Chapter 4: Connecting External Equipment (Optional) Connection procedure: Connecting 1. Connect contact closure sensors to the terminals. See Detectors/Switches to Contact Closure Terminals (on page 51). 2. Connect DX2-DH2C2 to the SENSOR port of SRC. Connecting Contact Closure Detectors to SRC Onboard Terminals Overview: Component Function...
Page 63: Connecting Detectors/Switches To Contact Closure Terminals
Chapter 4: Connecting External Equipment (Optional) Component Function Ports (on page 47). Two door handle ports Connection procedure: 1. First turn the SRC upside down. 2. Connect contact closure sensors to the terminals. See Connecting Detectors/Switches to Contact Closure Terminals (on page 51).
Page 64 Chapter 4: Connecting External Equipment (Optional) The following illustrates the procedure of connecting contact closure detectors/switches to DX2-DH2C2. This procedure can also apply to SRC onboard contact closure terminals but you have to turn the terminal module upside down so that you can see the four screws for four termination points.
Page 65 Chapter 4: Connecting External Equipment (Optional) 3. Strip the insulation around 12 mm from the end of each wire of discrete detectors/switches. 4. 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.
Page 66 Chapter 4: Connecting External Equipment (Optional) 6. After connecting detectors/switches to the terminal module, plug the terminal module back into the sensor box, and then tighten the screws at two sides of the terminal module. To make connections when the terminal module is attached: You can also connect a detector/switch when the terminal module remains attached to the sensor box.
Page 67: Connecting Asset Management Strips
Chapter 4: Connecting External Equipment (Optional)  If you are attaching wires to SRC onboard contact closure terminals, turn it upside down to tighten the screws. Connecting Asset Management Strips You can remotely track the locations of up to 64 IT devices in the rack by connecting asset management strips (asset strips) to the SRC after IT devices are tagged electronically.
Page 68: Combining Regular Asset Strips
Chapter 4: Connecting External Equipment (Optional) Combining Regular Asset Strips Each tag port on the regular asset strips corresponds to a rack unit and can be used to locate IT devices in a specific rack (or cabinet). For each rack, you can attach asset strips up to 64U long, consisting of one MASTER and multiple SLAVE asset strips.
Page 69 Chapter 4: Connecting External Equipment (Optional)  Make sure that the U-shaped sheet metal adjacent to the male DIN connector is inserted into the rear slot of the master strip. Screw up the U-shaped sheet metal to reinforce the connection. 2.
Page 70: Introduction To Asset Tags
Chapter 4: Connecting External Equipment (Optional) Introduction to Asset Tags You need both asset strips and asset tags for tracking IT devices. Asset tags provide an ID number for each IT device. The asset tags are adhered to an IT device at one end and plugged in to an asset strip at the other.
Page 71 Chapter 4: Connecting External Equipment (Optional) Connecting Asset Tags to SRC The following asset tag connection procedure applies to all SRC models. Note that the maximum cabling distance supported for each connected asset strip assembly is 10 meters. To connect a regular asset strip assembly to SRC: 1.
Page 72: Connecting Blade Extension Strips
Chapter 4: Connecting External Equipment (Optional) Connecting Blade Extension Strips For blade servers, which are contained in a single chassis, you can use a blade extension strip to track individual blade servers. Raritan's blade extension strip functions similar to a Raritan asset strip but requires a tag connector cable for connecting it to a tag port on the regular or composite asset strip.
Page 73 Chapter 4: Connecting External Equipment (Optional) 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 SRC device's web interface. To install a blade extension strip: 1.
Page 74 Chapter 4: Connecting External Equipment (Optional) a. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape. b. Plug the tag connector of the asset tag into a tag port on the blade extension strip.
Page 75: Connecting Composite Asset Strips (Ams-Mx-Z)
Chapter 4: Connecting External Equipment (Optional) Connecting Composite Asset Strips (AMS-Mx-Z) A composite asset strip is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset strip that functions the same as regular MASTER asset strips except for the following differences: ...
Page 76 Chapter 4: Connecting External Equipment (Optional) c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on the secondary composite asset strip. d. Repeat the same steps to connect more composite asset strips. Daisy-Chain Limitations of Composite Asset Strips page 65) for the maximum number of composite asset strips supported per chain.
Page 77 Chapter 4: Connecting External Equipment (Optional) 5. Repeat Step 3 to connect IT devices to the other composite asset strips in the chain. Daisy-Chain Limitations of Composite Asset Strips There are some limitations when daisy chaining composite asset strips "AMS-Mx-Z," where x is a number. ...
Page 78: Connecting A Logitech Webcam
Chapter 4: Connecting External Equipment (Optional) Connecting a Logitech Webcam Connect webcams to SRC in order to view videos or snapshots of the webcam's surrounding area. The following USB Video Class (UVC) compliant webcam is supported:  Logitech HD pro C920 ®...
Page 79: Connecting A Gsm Modem
Chapter 4: Connecting External Equipment (Optional) Connecting a GSM Modem The following Cinterion GSM modems can be connected to the SRC in ® order to send SMS messages containing event information.  MC52iT  MC55iT  EHS6 Available Actions (on page 253) for more information on SMS messages.
Page 80: Connecting An Analog Modem
Chapter 4: Connecting External Equipment (Optional) Connecting an Analog Modem The SRC supports remote dial-in communications to access the CLI through an analog modem. This dial-in feature provides an additional alternative to access the SRC when the LAN access is not available. To dial in to the SRC, the remote computer must have a modem connected and dial the correct phone number.
Page 81: Connecting A Schroff Lhx/Shx Heat Exchanger
Chapter 4: Connecting External Equipment (Optional) The beeper can be located at a distance up to 330 feet (100 m) away from the SRC. Connecting a Schroff LHX/SHX Heat Exchanger To remotely monitor and administer the Schroff LHX-20, LHX-40 and ®...
Page 82 Chapter 4: Connecting External Equipment (Optional)  The Modbus RTU devices on the bus are identified with their Modbus RTU addresses using the Modbus unit identifier addresses in the Modbus TCP protocol. If the Modbus TCP client does not support unit identifier addressing, Changing Modbus Settings refer to (on page 204).
Page 83: Chapter 5 Introduction To Src Components
Chapter 5 Introduction to SRC Components This chapter explains how to use the SRC device, including:  Introduction to connection ports  Operation of the front panel display  The internal beeper's behavior  The reset button In This Chapter Connection Ports ..................71 Dot-Matrix LCD Display ................74 Reset Button ....................94...
Page 84 Chapter 5: Introduction to SRC Components Port Used for...  Cascading SRC devices for sharing a network connection. See USB-B Cascading All Devices via USB (on page 26).  Establishing a USB connection between a computer and the SRC for: ...
Page 85 Chapter 5: Introduction to SRC Components Port Used for... CONSOLE/ Establishing a serial connection between the SRC and a computer or MODEM modem. (RJ-45) You need a third-party RJ-45 to DB9 adapter/cable for the connection(s). Note that the RJ-45 to DB9 adapter/cable for connecting a computer is different from the one for connecting a modem.
Page 86: Onboard Door Handle Ports And Contact Closure Terminals
Chapter 5: Introduction to SRC Components Onboard Door Handle Ports and Contact Closure Terminals Only specific SRC models like SRC-0102 have onboard door handle ports and contact closure terminals. See Product Models (on page 3). These ports are functionally identical to DX2-DH2C2. Port Description Door handle ports...
Page 87: Automatic And Manual Modes
Chapter 5: Introduction to SRC Components Automatic and Manual Modes After powering on or resetting the SRC, the front panel LCD display first shows some dots, then Raritan logo and finally enters the automatic mode. Automatic mode without alerts available: In this mode, the LCD display cycles through the sensor/actuator information as long as there are no alerts.
Page 88: Control Buttons
Chapter 5: Introduction to SRC Components Control Buttons Use the control buttons to navigate to the menu in the manual mode. Button Function Down Back -- OR -- Switch between automatic and manual modes...
Page 89: Operating The Dot-Matrix Lcd Display
Chapter 5: Introduction to SRC Components Operating the Dot-Matrix LCD Display Enter manual mode when you want to operate the dot-matrix LCD display. You can use the dot-matrix LCD display to:  Show information of the SRC, built-in components, or connected peripheral devices ...
Page 90 Chapter 5: Introduction to SRC Components Main Menu The Main Menu contains 5 menu commands. Control buttons that can be used and the system time are shown at the bottom of the LCD display. If any alerts exist, the top and bottom bars on the LCD display change the color from black to yellow or red.
Page 91 Chapter 5: Introduction to SRC Components Alerts The "Alerts" menu command shows a list of the following alerted sensors, including both internal and external sensors.  Any numeric sensor that enters the warning or critical range if the thresholds have been enabled ...
Page 92 Chapter 5: Introduction to SRC Components Number Description The time the alarm occurred. If the alarm occurred at least two times, then more information is shown.  Number of alarms  The first occurrence time  The last occurrence time Alerted sensor names.
Page 93 Chapter 5: Introduction to SRC Components  To mute the beep sound immediately, press . See Muting the Internal Beeper (on page 81). 3. Press to show the status of the 12V power supply to the controller. For details on this sensor, see +12V Power Supply Sensor (on page 114).
Page 94 Chapter 5: Introduction to SRC Components  If the desired sensor or actuator is not visible, press to scroll up or down.  When the list exceeds one page, the currently-selected sensor/actuator's ID number and total of managed sensors/actuators are indicated in the top-right corner of the display.
Page 95 Chapter 5: Introduction to SRC Components Number Description Sensor or actuator states as listed below. For further information, see Sensor/Actuator States (on page 125).  = unavailable  Normal  Alarmed  Lower Critical = below lower critical  Lower Warning = below lower warning ...
Page 96 Chapter 5: Introduction to SRC Components Number Description The following information is listed.  Serial number  Chain position, which involves the following information:  Port <N> : <N> is the number of the sensor port where this sensor or actuator is connected.
Page 97 Chapter 5: Introduction to SRC Components 2. Press to turn on or off the actuator. A confirmation message similar to the following is shown. 3. Press to select Yes or No, and then press 4. Verify that the actuator status shown on the LCD display has been changed.
Page 98 Chapter 5: Introduction to SRC Components  Type - the asset strip type.  Asset Strip Numbering - the numbering mode. See (on page 139).  Offset - the starting number of the rack unit numbering.  Orientation - the strip's orientation. 4.
Page 99 Chapter 5: Introduction to SRC Components Number Description Device name. Firmware version, model name and serial number 3. Press to show the Network Common page. Number Description DNS servers. Default gateways. 4. Press to show the Network Cascading page.
Page 100 Chapter 5: Introduction to SRC Components Number Description Cascading status, which can be one of the following:  No Cascading: This device's cascading mode is set to None. See Setting the Cascading Mode (on page 187).  Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP address is also displayed on this page.
Page 101 Chapter 5: Introduction to SRC Components 6. A SRC has two Ethernet pages -- ETH1 and ETH2. Number Description Ethernet interface information, including:  MAC address.  Speed.  Full or half duplex. IPv4/IPv6 network information, including:  Network configuration: DHCP (or Automatic), or Static. Static represents Static IP.
Page 102 Chapter 5: Introduction to SRC Components 7. Press to show the WIRELESS page. Number Description If NO supported WLAN adapter is plugged or detected, the message "No Adapter Detected" is shown. If a supported WLAN adapter is detected and configured properly, wireless network information is shown instead, including: ...
Page 103: Alerts Notice In A Yellow Or Red Screen
Chapter 5: Introduction to SRC Components Alerts Notice in a Yellow or Red Screen In the automatic mode, if an alert occurs, the LCD display automatically shows a yellow or red screen which indicates the total number of alerted sensors and information of the latest transitions. ...
Page 104 Chapter 5: Introduction to SRC Components When there is any alarm present: The LCD display looks similar to the above diagram except that it shows the alarm(s) and the available command in the bottom-right corner is 'Actions' instead of 'Alert list'. Available operations: ...
Page 105: Showing The Firmware Upgrade Progress
Chapter 5: Introduction to SRC Components  Show alert list : This option lists all of alerted sensors and alarms. You still can choose to acknowledge alarms after Alerts viewing the list. See (on page 79).  Acknowledge all alarms : This option immediately acknowledges all existing alarms, without showing the list of alarms.
Page 106: Reset Button
Chapter 5: Introduction to SRC Components Reset Button The reset button is located inside the small hole labeled RESET near the display panel.  Pressing this reset button restarts the SRC software.  The SRC can be reset to its factory default values using this button when a serial connection is available.
Page 107: Chapter 6 Using The Web Interface
Chapter 6 Using the Web Interface This chapter explains how to use the web interface to administer the SRC. In This Chapter Supported Web Browsers ................. 95 Login, Logout and Password Change ............95 Web Interface Overview................100 Dashboard ....................108 SRC ......................
Page 108 Chapter 6: Using the Web Interface  If the link-local addressing has been enabled, you can type pdu.local APIPA and Link-Local instead of an IP address. See Addressing (on page 6). Tip: You can also enter the desired page's URL so that you can immediately go to that page after login.
Page 109 Chapter 6: Using the Web Interface Depending on your hardware configuration, your web interface shown onscreen may look slightly different from the image below. Note: The address to access a slave device in the Port Forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an IP address and a port number.
Page 110: Changing Your Password
Chapter 6: Using the Web Interface Changing Your Password You need appropriate permissions to change your password. Refer to the following for details. To change other users' passwords, Administrator Privileges are required Editing or Deleting Users instead. See (on page 160). Password change request on first login: first login , if you have both the Change Local User Management and...
Page 111: Remembering User Names And Passwords
Chapter 6: Using the Web Interface  A password comprises 4 to 64 characters. Remembering User Names and Passwords SRC supports the password manager of common web browsers, including:  Microsoft Internet Explorer ®  Mozilla Firefox ®  Google Chrome ®...
Page 112: Web Interface Overview
Chapter 6: Using the Web Interface Web Interface Overview The web interface consists of four areas as shown below. Operation: 1. Click any menu or submenu item in the area of 2. That item's data/setup page is then opened in the area of 3.
Page 113 Chapter 6: Using the Web Interface 4. To return to the main menu and the Dashboard page, click on the top-left corner.
Page 114 Chapter 6: Using the Web Interface...
Page 115: Menu
Chapter 6: Using the Web Interface Number Web interface element Menu (on page 104) Data/setup page of the selected menu item.  Left side: - SRC device name. Note: To customize the device name, see (on page 113).  Right side: - Displayed language, which is English (EN) by default.
Page 116: Dashboard
Chapter 6: Using the Web Interface Menu Depending on your model and hardware configuration, your SRC may show all or some menu items shown below. Menu Information shown Dashboard Summary of the SRC status, which shows a list of alerted sensors and alarms, if any.
Page 117: Feature Port
Chapter 6: Using the Web Interface Menu Information shown Feature Port Status and settings of the device connected to the Feature port(s), which can be one of the following. The name  Asset Strip 'Feature Port(s)'  External Beeper will be replaced ...
Page 118: Quick Access To A Specific Page
Chapter 6: Using the Web Interface If a menu item contains the submenu, the submenu is shown after clicking that item. To return to the previous menu list, do any below:  Click the topmost link with the symbol <. For example, click ...
Page 119: Sorting A List
Chapter 6: Using the Web Interface Page Peripherals https://192.168.84.118/#/peripherals Event Log https://192.168.84.118/#/maintenance/eventLog/0 Sorting a List If any list displays an arrow ( ) in one of its column headers, you are allowed to resort the list by clicking any column header. The list will be resorted in the ascending or descending order based on the selected column.
Page 120: Dashboard
Chapter 6: Using the Web Interface 5. The arrow now appears adjacent to the selected column 'Event Class,' indicating the list is sorted in the ascending order based on that column. Dashboard The Dashboard page contains two sections.
Page 121 Chapter 6: Using the Web Interface Number Section Information shown  When no sensors enter the alarmed state, this section shows Alerted the message "No Alerted Sensors." Sensors  When any sensor enters the alarmed state, this section lists all of them.
Page 122: Dashboard - Alerted Sensors
Chapter 6: Using the Web Interface Dashboard - Alerted Sensors When any internal sensors or environmental sensor packages connected to the SRC enter an abnormal state, the Alerted Sensors section in the Dashboard show them for alerting users. To view detailed information or configure each alerted sensor, you can Individual click each sensor's name to go to individual sensor pages.
Page 123: Dashboard - Alarms
Chapter 6: Using the Web Interface  1 Warned: 1 'numeric' sensor enters the warning state. List of alerted sensors: Two icons are used to indicate various sensor states. Icons Sensor states Numeric sensors:  above upper warning  below lower warning Numeric sensors: ...
Page 124 Chapter 6: Using the Web Interface This table explains each column of the alarms list. Field Description Name Custom name of the Alarm action. Reason The first event that triggers the alert. First Appearance Date and time when the event indicated in the Reason column occurred for the first time.
Page 125: Src
Chapter 6: Using the Web Interface The SRC device's generic information and SRC settings are available on the SRC page. Menu To open the SRC page, click 'SRC' in the (on page 104). Device information shown:  Firmware version  Serial number ...
Page 126: +12V Power Supply Sensor
Chapter 6: Using the Web Interface States Description "Activation Reason" is displayed, indicating why the beeper sounds an alarm. For example, if the beeper is turned on because of a specific event rule "XXX," the activation reason looks like: Event Action triggered by rule: XXX Event Rules and Actions (on page 237).
Page 127: Peripherals
Chapter 6: Using the Web Interface Peripherals Only DX and DX2 environmental sensor packages are supported. SRC does NOT support other Raritan environmental sensor packages than DX and DX2 series. If there are Raritan environmental sensor packages connected to the Connecting Raritan SRC, they are listed on the Peripherals page.
Page 128 Chapter 6: Using the Web Interface  Go to an individual sensor's or actuator's data/setup page by clicking its name.
Page 129 Chapter 6: Using the Web Interface If wanted, you can resort the list by clicking the desired column header. Sorting a List (on page 107). Sensor/actuator overview on this page: If any sensor enters an alarmed state, it is highlighted in yellow or red. Yellow- or Red-Highlighted Sensors (on page 123).
Page 130 Chapter 6: Using the Web Interface To release or manage sensors/actuators: When the total of managed sensors/actuators reaches the maximum value, you cannot manage additional ones. The only way to manage any sensor/actuator is to release or replace the managed ones. To replace a managed sensor/actuator, see Managing One Sensor or Actuator page 129).
Page 131 Chapter 6: Using the Web Interface  The management action triggers a "Manage Peripheral Device" multiple dialog. Simply click Manage if you are managing sensors/actuators.  If you are managing only sensor/actuator, you can choose to assign an ID number by selecting "Manually select a sensor Managing One Sensor or Actuator number."...
Page 132 Chapter 6: Using the Web Interface Field Function Note  The default is to enable it.  The device's altitude is associated Altitude Specifies the altitude of SRC above with the altitude correction factor. sea level when a Raritan's differential Altitude Correction Factors air pressure sensor is attached.
Page 133 Chapter 6: Using the Web Interface To configure default threshold settings: Note that any changes made to default threshold settings not only re-determine the initial threshold values that will apply to newly-added sensors but also the threshold values of the already-managed sensors Individual where default thresholds are being applied.
Page 134 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 642). 4. Click Save. Tip: To customize the threshold settings on a per-sensor basis, go to (on page 131).
Page 135: Yellow- Or Red-Highlighted Sensors
Chapter 6: Using the Web Interface Yellow- or Red-Highlighted Sensors The SRC highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled their thresholds. Tip: When an actuator is turned ON, it is also highlighted in red for drawing attention.
Page 136: Managed Vs Unmanaged Sensors/Actuators
Chapter 6: Using the Web Interface Sensor status Color States shown in Description the interface alarmed State sensors enter the abnormal state. Alarmed If you have connected a Schroff LHX/SHX heat exchanger, when any ® sensor implemented on that device fails, it is also highlighted in red. Managed vs Unmanaged Sensors/Actuators To manually manage or unmanage/release a sensor or actuator, see Peripherals...
Page 137 Chapter 6: Using the Web Interface  They do have an ID number.  They show the "unmanaged" state. Sensor/Actuator States An environmental sensor or actuator shows its real-time state after being managed. Available sensor states depend on the sensor type -- numeric or state sensors.
Page 138: Finding The Sensor's Serial Number
Chapter 6: Using the Web Interface Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors and Actuators Guide (or Online Help) for detailed information, which is available on Raritan's Support page http://www.raritan.com/support/...
Page 139: Identifying The Sensor Position And Channel
Chapter 6: Using the Web Interface The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the SRC. Match the serial number from the tag to those listed in the sensor table. Identifying the Sensor Position and Channel SRC can indicate where each sensor or actuator is connected on the Peripheral Devices page.
Page 140 Chapter 6: Using the Web Interface Example Physical position  Connected to the sensor port #1. Port 1,  The sensor/actuator is located in the 4th sensor package of the sensor chain. Chain Position 4  Connected to the sensor port #1. Port 1, ...
Page 141: How The Automatic Management Function Works
Chapter 6: Using the Web Interface How the Automatic Management Function Works This setting is configured on Peripherals (on page 115). After enabling the automatic management function: When the total number of managed sensors and actuators has not reached the upper limit yet, SRC automatically brings newly-connected environmental sensors and actuators under management after detecting them.
Page 142 Chapter 6: Using the Web Interface 2. The Manage Peripheral Device dialog appears.  To let SRC randomly assign an ID number to it, select "Automatically assign a sensor number." This method does not release any managed sensor or actuator. ...
Page 143 Chapter 6: Using the Web Interface However, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed. Note that relative and absolute values of the same humidity sensor do NOT share the same ID number though they share the same serial number and position.
Page 144 Chapter 6: Using the Web Interface 2. Select or deselect 'Use default thresholds' according to your needs.  To have this sensor follow the default threshold settings configured for its own sensor type, select the 'Use default thresholds' checkbox. The default threshold settings are configured on the page of Peripherals (on page 115).
Page 145 Chapter 6: Using the Web Interface To set up a sensor's or actuator's physical location and additional settings: 1. Click Edit Settings. 2. Make changes to available fields, and then click Save. Fields Description Name A name for the sensor or actuator. Description Any descriptive text you want.
Page 146 Chapter 6: Using the Web Interface Fields Description Sensor Polarity This field is available for DX2-CC2 contact closure sensors only. Determine the normal state of your DX2-CC2.  Normal Open: The open status of the connected detector/switch is considered normal. An alarm is triggered when the detector/switch turns closed. ...
Page 147 Chapter 6: Using the Web Interface  To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To turn on or off an actuator: 1.
Page 148 Chapter 6: Using the Web Interface Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time. To change this limitation of "powered dry contact" actuators, modify the active powered dry contact setting.
Page 149: Individual Sensor/Actuator Pages
Chapter 6: Using the Web Interface Format Description of any environmental sensors or actuators. Free-form Any alphanumeric string can be used for specifying the Z coordinate. The value comprises 0 to 24 characters. Individual Sensor/Actuator Pages 2. Configure Z coordinates on the (on page 131).
Page 150 Chapter 6: Using the Web Interface Device Description LHX 40 Schroff LHX-40 heat exchanger. ® Power CIM Only Raritan PDUs support the connection to a Raritan power CIM or digital KVM. SRC does NOT support this feature so you can ignore this option. When the SRC detects the connection of any listed device, it replaces 'Feature Port' in the menu with that device's name and shows that Asset Strip...
Page 151: Asset Strip
Chapter 6: Using the Web Interface Mode Description Asset Strip, Force the SRC to show the selected device's data/setup page regardless of the physical Raritan asset connection status. strips, LHX 20, SHX 30, LHX 40, Power CIM Note: 'LHX 20', 'SHX 30', and 'LHX 40' are not available when the support of LHX/SHX heat exchangers is disabled.
Page 152 Chapter 6: Using the Web Interface 2. Make changes to the settings by directly typing a new value, or clicking that field to select a different option. Field Description Name Name for this asset strip assembly. Number of rack Total of available tag ports on this asset strip units assembly, ranging between 8 and 64.
Page 153 Chapter 6: Using the Web Interface Field Description Color without Click this field to determine the LED color connected tag denoting the absence of an asset tag.  Default is red. For color settings, there are two ways to set the color. ...
Page 154 Chapter 6: Using the Web Interface  If wanted, you can resort the list by clicking the desired column Sorting a List header. See (on page 107). To customize a single rack unit's settings: You can make a specific rack unit's LED behave differently from the others on the asset strip, including the LED light and color.
Page 155 Chapter 6: Using the Web Interface Field Description LED Mode This field is configurable only after the Operation Mode is set to Manual Override. Determine how the LED light behaves for this particular rack unit.  : The LED stays lit. ...
Page 156 Chapter 6: Using the Web Interface 2. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the Slot column.  To hide the blade extension slots list, click...
Page 157 Chapter 6: Using the Web Interface To customize asset IDs on programmable asset tags: You can customize asset IDs only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the ID of a blade extension strip.
Page 158 Chapter 6: Using the Web Interface  An asset ID contains up to 12 characters that comprise only numbers and/or UPPER CASE alphabets. Lower case alphabets are NOT accepted. 3. Verify the correctness of customized asset IDs and modify as needed.
Page 159 Chapter 6: Using the Web Interface Tip: Another way to abort changes is to click Rack Units. Refer to the diagram below. Asset Strip Automatic Firmware Upgrade After connecting the asset strip to the SRC, it automatically checks its own firmware version against the version of the asset strip firmware stored in the SRC firmware.
Page 160: External Beeper
Chapter 6: Using the Web Interface External Beeper After connecting and detecting a supported external beeper, the SRC shows 'External Beeper' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting an External Beeper (on page 68). Menu To open the External Beeper page, click it in the (on page 104).
Page 161: Schroff Lhx/Shx
Chapter 6: Using the Web Interface Schroff LHX/SHX You must enable the LHX/SHX support for the SRC to detect the presence of a supported Schroff LHX/SHX heat exchanger. See ® Miscellaneous (on page 314). After enabling the LHX/SHX support and connecting a supported Schroff ®...
Page 162 Chapter 6: Using the Web Interface Feature For the functionality of this icon on the top-right corner, see Port (on page 137). To view the LHX/SHX device state: The Operation State field indicates whether the device is operating fine, and the Switch State field indicates its power status. If the device does not operate properly, such as some sensor failure, it shows "critical"...
Page 163 Chapter 6: Using the Web Interface To configure LHX/SHX settings: 1. Click Edit Settings. 2. Configure the settings as needed.  Provide a customized name.  Specify the desired air outlet setpoint temperature.  Specify the default fan speed. 3. Click Save. To view all sensor data and configure thresholds: 1.
Page 164 Chapter 6: Using the Web Interface b. Click Edit Thresholds. c. Enable and set the desired thresholds and deassertion hysteresis. Note that assertion timeout is NOT available on LHX/SHX. d. Click Save. 3. After thresholds are enabled, sensors may be highlighted in yellow Yellow- or or red if they enter the warning or critical range.
Page 165 Chapter 6: Using the Web Interface 2. If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure. 3. To view the history of LHX events, click Show Event Log to go to the Event Log page. Operation time statistics: This section indicates the accumulative operation hours of the LHX/SHX device and its fans since the device is connected to the SRC and turned...
Page 166 Chapter 6: Using the Web Interface SHX Request Maximum Cooling The SRC allows you to remotely activate the Schroff SHX 30's maximum cooling feature. Both LHX 20 and LHX 40 do not support remote activation of maximum cooling. The Request Maximum Cooling feature is available only after the SRC detects SHX 30.
Page 167: User Management
Chapter 6: Using the Web Interface User Management User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis. SRC is shipped with one built-in administrator account: admin, which is ideal for initial login and system administration. You cannot delete 'admin' or change its permissions, but you can and should change its password.
Page 168 Chapter 6: Using the Web Interface Creating Users All users must have a user account, containing the login name and password. Multiple users can log in simultaneously using the same login name. To add users, choose User Management > Users > Note that you must enter information in the fields showing the message 'required.' User information:...
Page 169 Chapter 6: Using the Web Interface Field/setting Description Force password When selected, a password change request change on next automatically appears the next time the user logs login Changing Your Password For details, see page 98). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
Page 170 Chapter 6: Using the Web Interface Field/setting Description Password, Type the authentication password if the 'Same as User Password' checkbox is deselected. Confirm password The password must consist of 8 to 32 ASCII printable characters.  Privacy Password: This section is configurable only when 'Authentication &...
Page 171 Chapter 6: Using the Web Interface Field Description Length unit Preferred units for length or height -- Meter or Feet. Pressure unit Preferred units for pressure -- Pascal or Psi.  Pascal = one newton per square meter  Psi = pounds per square inch Note: Users can change the measurement units at any time by setting their own preferences.
Page 172: Editing Or Deleting Users
Chapter 6: Using the Web Interface Editing or Deleting Users To edit or delete users, choose User Management > Users to open the Users page, which lists all users. In the Enabled column:  : The user is enabled.  : The user is disabled.
Page 173 Chapter 6: Using the Web Interface  To delete this user, click , and confirm the operation. 3. Click Save. To delete multiple user accounts: 1. On the Users page, click to make checkboxes appear in front of user names. Tip: To delete only one user, you can simply click that user without making the checkboxes appear.
Page 174: Creating Roles
Chapter 6: Using the Web Interface Creating Roles A role is a combination of permissions. Each user must have at least one role. The SRC provides two built-in roles. Built-in role Description Admin Provide full permissions. Operator Provide frequently-used permissions, including: ...
Page 175: Editing Or Deleting Roles
Chapter 6: Using the Web Interface a. Click on that privilege's row to display a list of available arguments for that privilege. b. Select the desired arguments.  To select all arguments, simply select the checkbox labeled 'All XXX'. Tip: The other way to select all arguments is to select that privilege's checkbox while the arguments list is not expanded yet.
Page 176 Chapter 6: Using the Web Interface The Admin role is not user-configurable so the lock icon displays, indicating that you are not allowed to configure it. To edit a role: 1. On the Roles page, click the desired role. The Edit Role page opens. 2.
Page 177: Setting Your Preferred Measurement Units
Chapter 6: Using the Web Interface Setting Your Preferred Measurement Units You can change the measurement units shown in the SRC user interface according to your own preferences regardless of the permissions you have. Tip: Preferences can also be changed by administrators for specific users on the Edit User page.
Page 178 Chapter 6: Using the Web Interface Setting Default Measurement Units Default measurement units are applied to all SRC user interfaces across all users, including users accessing the SRC via external authentication servers. User Interfaces Showing For a list of affected user interfaces, see Default Units (on page 166).
Page 179: Device Settings
Chapter 6: Using the Web Interface Device Settings Menu Click 'Device Settings' in the (on page 104), and the following submenu displays. Menu command Submenu command Refer to... Configuring Network Settings Network (on page 169) Changing HTTP(S) Settings Network Services HTTP (on page 198) Configuring SNMP Settings...
Page 180 Chapter 6: Using the Web Interface Menu command Submenu command Refer to... Configuring SMTP Settings SMTP Server (on page 201) Changing SSH Settings (on page 203) Changing Telnet Settings Telnet (on page 204) Changing Modbus Settings Modbus (on page 204) Enabling Service Advertising Server Advertising (on page 207)
Page 181 Chapter 6: Using the Web Interface Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the Network page after Connecting the SRC to Your Network (on page 11). You can enable both the wired and wireless networking on SRC so that it has multiple IP addresses -- wired and wireless IP.
Page 182 Chapter 6: Using the Web Interface Ethernet 5. To configure the ETH1/ETH2 interface settings, see Interface Settings (on page 173). 6. Click Save. After enabling either or both Internet protocols: After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with the selected Internet protocol(s): ...
Page 183 Chapter 6: Using the Web Interface Field/setting Description  Static : Manually configure the IPv4 settings. Preferred Enter the hostname you prefer for IPv4 hostname connectivity  DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements: ...
Page 184 Chapter 6: Using the Web Interface (Optional) To view the diagnostic log for EAP authentication:  Diagnostic Log for Click Show EAP Authentication Log. See Network Connections (on page 182). Common Network Settings Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements.
Page 185 Chapter 6: Using the Web Interface Field Description First/Second/Third Manually specify static DNS server(s). DNS server  If any static DNS server is specified in these fields, it will override the DHCP-assigned DNS server.  If DHCP (or Automatic) is selected for IPv4/IPv6 settings, and there are NO static DNS servers specified, the SRC will use DHCP-assigned DNS servers.
Page 186 Chapter 6: Using the Web Interface Field Description transmission mode through auto-negotiation.  Full: Data is transmitted in both directions simultaneously.  Half: Data is transmitted in one direction (to or from the SRC) at a time. Show the LAN's current status, including the Current state current speed and duplex mode.
Page 187 Chapter 6: Using the Web Interface Field Description Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' Client private key, are all selected. Client private key password PEM encoded X.509 certificate and PEM encoded private key are required for certification-based authentication methods.
Page 188 Chapter 6: Using the Web Interface Field/setting Description chain validity of the TLS certificate that will be installed.  For example, the SRC will check the certificate's validity period against the system time. Click this button to import a certificate file. Then you can: ...
Page 189 Chapter 6: Using the Web Interface Wireless Network Settings If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be Setting the Cascading Mode disabled. See (on page 187).
Page 190 Chapter 6: Using the Web Interface Field/setting Description Outer This field appears when 'EAP' is selected. authentication There are two authentication methods for EAP.  PEAP: A TLS tunnel is established, and an inner authentication method can be specified for this tunnel. ...
Page 191 Chapter 6: Using the Web Interface Field/setting Description Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' Client private key, are all selected. Client private key password PEM encoded X.509 certificate and PEM encoded private key are required for certification-based authentication methods.
Page 192 Chapter 6: Using the Web Interface Field/setting Description Click this button to import a certificate file. Then you can:  Click Show to view the certificate's content.  Click Remove to delete the installed certificate if it is inappropriate.  Select this checkbox to make the Allow expired and authentication succeed regardless of the not yet valid...
Page 193 Chapter 6: Using the Web Interface  Cannot contain more than 63 characters  Cannot contain punctuation marks, spaces, and other symbols  Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length". 192.168.84.99/24 Example: IPv6 settings: Field/setting Description Enable IPv6...
Page 194 Chapter 6: Using the Web Interface Diagnostic Log for Network Connections SRC provides a diagnostic log for inspecting connection errors that occurred during the EAP authentication or the wireless network connection. The information is useful for technical support. Note that the diagnostic log shows data only after connection errors are detected.
Page 195 Chapter 6: Using the Web Interface Static Route Examples This section describes two static route examples: IPv4 and IPv6. Both examples assume that two network interface controllers (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled.
Page 196 Chapter 6: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your SRC to communicate with any device in the other subnet 192.168.200.0. In the IPv4 "Static Routes" section, you should enter the data as shown below.
Page 197 Chapter 6: Using the Web Interface Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click to delete it. IPv6 example:  fd07:2fa:6cff:2405::30 Your SRC: ...
Page 198 Chapter 6: Using the Web Interface In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your SRC to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the IPv6 "Static Routes" section, you should enter the data as shown below.
Page 199 Chapter 6: Using the Web Interface Interface list: Interface name Description When another wired network is connected to the BRIDGE Ethernet port of your SRC, and your SRC has been set to the bridging mode, select this interface name instead of the Ethernet interface. When another wired network is connected to the ETH1 ETH1 port of your SRC, select this interface name.
Page 200 Chapter 6: Using the Web Interface Mode Description No cascading mode is enabled. This is the None default. Each device in the cascading chain is Bridging accessed with a different IP address. Each device in the cascading chain is Port Forwarding accessed with the same IP address(es) but with a different port number assigned.
Page 201 Chapter 6: Using the Web Interface  In the Port Forwarding mode, all cascaded devices share the master device's network settings. You only need to configure the master device's network settings in the ETH1/ETH2 and/or WIRELESS section. Wired Network Settings Wireless Network (on page 170) or Settings...
Page 202 Chapter 6: Using the Web Interface Overview of the Cascading Modes You must apply a cascading mode to the cascading chain. See Setting the Cascading Mode (on page 187). There are two cascading modes: Bridging and Port Forwarding. In the following illustration, it is assumed that users enable the DHCP networking for the cascading chain comprising four devices.
Page 203 Chapter 6: Using the Web Interface Comparison between cascading modes:  The Bridging mode supports the wired network only, while the Port Forwarding mode supports both wired and wireless networks.  Both cascading modes support a maximum of 16 devices in a chain. ...
Page 204 Chapter 6: Using the Web Interface  XX is a two-digit number representing the device position as shown below. Position Position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12 Slave 5 Slave 13 Slave 6...
Page 205 Chapter 6: Using the Web Interface In the Port Forwarding mode, the cascaded device does NOT allow you to modify the standard TCP/UDP port configuration, including HTTP, HTTPS, SSH, Telnet and Modbus/TCP. Port Forwarding Examples To access a cascaded device in the Port Forwarding mode, assign a port number to the IP address.
Page 206 Chapter 6: Using the Web Interface  To access the master device via SSH, the command is: ssh -p 22 192.168.84.77 Slave 1 device: Position code for Slave 1 is '01' so each port number is 5NN01 as shown below. Protocols Port numbers HTTPS...
Page 207 Chapter 6: Using the Web Interface Examples:  To access Slave 2 via HTTPS, the IP address is: https://192.168.84.77:50002/  To access Slave 2 via HTTP, the IP address is: http://192.168.84.77:50102/  To access Slave 2 via SSH, the command is: ssh -p 50202 192.168.84.77 Adding, Removing or Swapping Cascaded Devices Change a device's cascading mode first before adding that device to a...
Page 208 Chapter 6: Using the Web Interface To swap the master and slave device:  In the Bridging mode, you can swap the master and slave devices by simply disconnecting ALL cascading cables from them, and then reconnecting cascading cables. No changes to software settings are required.
Page 209: Configuring Network Services
Chapter 6: Using the Web Interface Configuring Network Services SRC supports the following network communication services. HTTPS and HTTP enable the access to the web interface. Telnet and SSH enable the access to the command line interface. See Using the Command Line Interface (on page 374).
Page 210 Chapter 6: Using the Web Interface Submenu command Refer to Enabling Service Advertising Server Advertising (on page 207) Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
Page 211 Chapter 6: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the SRC. Enabling SNMP communication allows the manager to retrieve data and configures SRC. Besides, you may need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule"...
Page 212 Chapter 6: Using the Web Interface 2. Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking the corresponding checkbox.  The SNMP v1/v2c read-only access is enabled by default. The default 'Read community string' is "public."  To enable read-write access, type the 'Write community string.' Usually the string is "private."...
Page 213 Chapter 6: Using the Web Interface 4. To configure SNMP notifications: a. Select the 'Enable SNMP notifications' checkbox. b. Select a notification type -- SNMPv2c trap, SNMPv2c inform, SNMPv3 trap, and SNMPv3 inform. c. Specify the SNMP notification destinations and enter necessary information.
Page 214 Chapter 6: Using the Web Interface Field Description Port Type the port number.  Default is 25 Sender email Type an email address for the sender. address Number of sending Type the number of email retries. retries  Default is 2 retries Time between Type the interval between email retries in sending retries...
Page 215 Chapter 6: Using the Web Interface 3. Now that you have set the SMTP settings, you can test it to ensure it works properly. a. Type the recipient's email address in the 'Recipient email addresses' field. Use a comma to separate multiple email addresses.
Page 216 Chapter 6: Using the Web Interface Changing Telnet Settings You can enable or disable the Telnet access to the command line interface, or change the TCP port. To change Telnet settings: 1. Choose Device Settings > Network Services > Telnet. 2.
Page 217 Chapter 6: Using the Web Interface Modbus Gateway: If connecting the Modbus RTU devices to SRC and enabling the Modbus Gateway feature, the Modbus TCP clients on your network will be able to communicate with those Modbus RTU devices attached to SRC. See Connecting a Modbus RTU Device or Bus (on page 69).
Page 218 Chapter 6: Using the Web Interface Field Description Use the default port 503, or assign a different port. Valid TCP port range is 1 to 65535. Note: Port 502 is the default Modbus/TCP port for SRC, so you cannot use that port for the Modbus Gateway. Use the default values, or update if the Modbus RTU devices Parity, are using different communication parameters.
Page 219 Chapter 6: Using the Web Interface Enabling Service Advertising The SRC 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: ...
Page 220: Configuring Security Settings
Chapter 6: Using the Web Interface Configuring Security Settings The SRC provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for access control.
Page 221 Chapter 6: Using the Web Interface Creating IP Access Control Rules IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the SRC, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind: ...
Page 222 Chapter 6: Using the Web Interface ADD a rule to the end of the list  Click Append.  Type an IP address and subnet mask in the IP/Mask field.  Select an option in the Policy field.  Accept: Accepts traffic from/to the specified IP address(es).
Page 223 Chapter 6: Using the Web Interface  You can select any existing rule and then click to change its priority. 7. Click Save. The rules are applied.
Page 224 Chapter 6: Using the Web Interface To configure IPv6 access control rules: 1. On the same page, select the 'Enable IPv6 access control' checkbox to enable IPv6 access control rules. 2. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.
Page 225 Chapter 6: Using the Web Interface Creating Role Based Access Control Rules Role-based access control rules are similar to IP access control rules, except that they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.
Page 226 Chapter 6: Using the Web Interface 5. When finished, the rules are listed on this page.  You can select any existing rule and then click to change its priority. 6. Click Save. The rules are applied. To configure IPv6 access control rules: 1.
Page 227 Chapter 6: Using the Web Interface 4. Perform the desired action.  Make changes to the selected rule, and then click Save. For Creating Role Based Access information on each field, see Control Rules (on page 213).  Click to remove it. ...
Page 228 Chapter 6: Using the Web Interface Creating a CSR Follow this procedure to create the CSR for your SRC. Note that you must enter information in the fields showing the message 'required.' To create a CSR: 1. Choose Device Settings > Security > TLS Certificate. 2.
Page 229 Chapter 6: Using the Web Interface  Key Creation Parameters: Field Do this Key length Select an available key length (bits). A larger key length enhances the security, but slows down the response of SRC.  Only 2048 is available now. Self-sign For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
Page 230 Chapter 6: Using the Web Interface 2. Click to navigate to the CA-signed certificate file. 3. Click Upload to install it. 4. To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section. Creating a Self-Signed Certificate When appropriate certificate and key files for SRC are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a...
Page 231 Chapter 6: Using the Web Interface Field Description Validity in days This field appears after the Self-sign checkbox is selected. Type the number of days for which the self-signed certificate will be valid. A password is not required for a self-signed certificate so the Challenge and Confirm Challenge fields disappear.
Page 232 Chapter 6: Using the Web Interface Active TLS Certificate 2. In the section, click Download Key and Download Certificate respectively. Note: The Download Key button in the New TLS Certificate section, if present, is for downloading the newly-created private key rather than the one of the currently-installed certificate.
Page 233 Chapter 6: Using the Web Interface For security purposes, users attempting to log in to SRC must be authenticated. SRC supports the following authentication mechanisms:  Local user database on the SRC  Lightweight Directory Access Protocol (LDAP)  Remote Access Dial-In User Service (Radius) protocol By default, SRC is configured for local authentication.
Page 234 Chapter 6: Using the Web Interface Special note about the AES cipher: The SRC device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between SRC and the client (such as a web browser), which is impacted by the cipher priority of SRC and the client's cipher availability/settings.
Page 235 Chapter 6: Using the Web Interface Adding LDAP/LDAPS Servers To use LDAP authentication, enable it and enter the information you have gathered. Note that you must enter information in the fields showing the message 'required.' To add LDAP/LDAPS servers: 1. Choose Device Settings > Security > Authentication. 2.
Page 236 Chapter 6: Using the Web Interface Field/setting Description Enable verification Select this checkbox if it is required to validate the LDAP server's of LDAP server certificate by the SRC prior to the connection. certificate If the certificate validation fails, the connection is refused. CA certificate Consult your AA server administrator to get the CA certificate file for the LDAPS server.
Page 237 Chapter 6: Using the Web Interface Field/setting Description User entry object The object class for user entries. class  Usually it is inetOrgPerson. User search Search criteria for finding LDAP user objects within the directory subfilter tree. Active Directory The name of the Active Directory Domain. domain ...
Page 238 Chapter 6: Using the Web Interface Note: If the SRC clock and the LDAP server clock are out of sync, the installed TLS certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the SRC and the LDAP server to use the same NTP server(s).
Page 239 Chapter 6: Using the Web Interface Field/setting Description Shared secret, The shared secret is necessary to protect communication with the Radius server. Confirm shared secret 4. To verify if the authentication configuration is set correctly, click Test Connection to check whether the SRC can connect to the new server successfully.
Page 240 Chapter 6: Using the Web Interface  Click Delete to delete the server, and then confirm the operation.  Click Test Connection to verify the connection to the selected server. User credentials may be required.  Click to change the server order, which determines the access priority, and click Save Order to save the new sequence.
Page 241 Chapter 6: Using the Web Interface  If you type a value, the value must be followed by a time unit, Time Units such as '4 min.' See (on page 229). 3. In the 'Maximum number of failed logins' field, type a number. This is the maximum number of login failure the user is permitted before the user is blocked from accessing the SRC.
Page 242 Chapter 6: Using the Web Interface Configuring Password Policy Choose Device Settings > Security > Password Policy to open the Password Policy page, where you can:  Force users to use strong passwords.  Force users to change passwords at a regular interval -- that is, password aging.
Page 243 Chapter 6: Using the Web Interface Enabling the Restricted Service Agreement The restricted service agreement feature, if enabled, forces users to read a security agreement when they log in to the SRC. Users must accept the agreement, or they cannot log in. An event notifying you if a user has accepted or declined the agreement Default Log Messages can be generated.
Page 244 Chapter 6: Using the Web Interface Login manner after enabling the service agreement: After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails:  In the web interface, select the checkbox labeled "I understand and accept the restricted service agreement."...
Page 245: Setting The Date And Time
Chapter 6: Using the Web Interface Setting the Date and Time Set the internal clock on the SRC manually, or link to a Network Time Protocol (NTP) server. Note: If you are using Sunbird's Power IQ to manage the SRC, you must configure Power IQ and the SRC to have the same date/time or NTP settings.
Page 246 Chapter 6: Using the Web Interface Use the NTP server  Select "Synchronize with NTP server."  There are two ways to assign the NTP servers:  To use the DHCP-assigned NTP servers, DO NOT enter any NTP servers for the First and Second time server.
Page 247 Chapter 6: Using the Web Interface Calendar The calendar icon in the Date field is a convenient tool to select a custom date. Click it and a calendar similar to the following appears. Number Item Description arrows Switch between months. dates All dates of the selected month.
Page 248 Chapter 6: Using the Web Interface Windows NTP Server Synchronization Solution The NTP client on the SRC follows the NTP RFC so the SRC rejects any NTP servers whose root dispersion is more than one second. An NTP server with a dispersion of more than one second is considered an inaccurate NTP server by the SRC.
Page 249: Event Rules And Actions
Chapter 6: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule." An event rule consists of two parts: ...
Page 250 Chapter 6: Using the Web Interface Note: When creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like "Alarm," "Log event message," "Send email," "Syslog message" and the like. 2. Click to schedule the desired action.
Page 251 Chapter 6: Using the Web Interface Event rule configuration illustration: 1. Choose Device Settings > Event Rules > 2. Click the Event field to select an event type.  <Any sub-event> means all events shown on the list.  <Any Numeric Sensor> means all numeric sensors of the SRC, including internal and environmental sensors.
Page 252 Chapter 6: Using the Web Interface 5. In this example, Numeric Sensor is selected because we want to select numeric-sensor-related event(s). Then a field for numeric-sensor-related events appears. Click this field to select one of the numeric-sensor-related events from the list. 6.
Page 253 Chapter 6: Using the Web Interface  To select all available actions, click Select All. 9. To remove any action(s) from the 'Selected actions' field, click that action's  To remove all actions, click Deselect All. Radio buttons for different events: According to the event you select, the "Trigger condition"...
Page 254 Chapter 6: Using the Web Interface Event types Radio buttons Sensor availability Available radio buttons include "Unavailable," "Available" and "Both."  Unavailable: SRC takes the action only when the chosen sensor is NOT detected and becomes unavailable.  Available: SRC takes the action only when the chosen sensor is detected and becomes available.
Page 255 Chapter 6: Using the Web Interface Event types Radio buttons  Monitoring started: SRC takes the action Server monitoring only when the monitoring of any specified event server starts.  Monitoring stopped: SRC takes the action only when the monitoring of any specified server stops.
Page 256 Chapter 6: Using the Web Interface Default Log Messages These default log messages are recorded internally and emailed to specified recipients when SRC events occur (are TRUE) or, in some cases, Send Email stop or become unavailable (are FALSE). See (on page 262) to configure email messages.
Page 257 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Asset Management > Composition changed on composite Composite Asset Strip asset strip [AMSNUMBER] Composition Changed ('[AMSNAME]'). Card Reader Management > Card of type '[SMARTCARDTYPE]' with Card Reader >...
Page 258 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > Device identification Config parameter '[CONFIGPARAM]' changed changed to '[CONFIGVALUE]' by user '[USERNAME]' from host '[USERIP]'. Device > Device settings saved Device settings saved by user '[USERNAME]' from host '[USERIP]'.
Page 259 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > A Radius error A Radius error occurred: occurred [ERRORDESC]. Device > Raw configuration Raw configuration downloaded by user downloaded '[USERNAME]' from host '[USERIP]'.
Page 260 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Below lower '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot warning threshold [EXTSENSORSLOT] asserted 'below [EXTSENSORSLOT] deasserted...
Page 261 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Server Monitoring > * > Error Error monitoring server '[MONITOREDHOST]': [ERRORDESC] Server Monitoring > * > Server '[MONITOREDHOST]' is now Server '[MONITOREDHOST]' is no Monitored being monitored.
Page 262: Webcam Management
Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE User Administration > Role Role '[UMTARGETROLE]' added by added user '[USERNAME]' from host '[USERIP]'. User Administration > Role Role '[UMTARGETROLE]' modified by modified user '[USERNAME]' from host '[USERIP]'.
Page 263 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Sensor > Above Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at upper warning threshold [PORTTYPE] port '[PORTID]' asserted [PORTTYPE] port '[PORTID]' 'above upper warning' at deasserted 'above upper warning'...
Page 264 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Door Contact The door of LHX at [PORTTYPE] port The door of LHX at [PORTTYPE] port '[PORTID]' was opened. '[PORTID]' was closed.
Page 265 Chapter 6: Using the Web Interface The asterisk symbol (*) represents anything you select for the 'trigger' events. Available Actions The SRC comes with three built-in actions, which cannot be deleted. You can create additional actions for responding to different events. Built-in actions: ...
Page 266 Chapter 6: Using the Web Interface Action Function Alarm Requires the user to acknowledge the alert after it is generated. If needed, you can have the alert notifications regularly generated until a person takes the acknowledgment action. Alarm (on page 255). Execute an action Creates a group of actions comprising existing Action Group...
Page 267 Chapter 6: Using the Web Interface Action Function Send SNMP Sends SNMP traps or informs to one or Send an notification multiple SNMP destinations. See SNMP Notification (on page 269). Start/stop Lua script If you are a developer who can create a Lua script, you can upload it to the SRC, and have the SRC automatically perform or stop the Start or...
Page 268 Chapter 6: Using the Web Interface 3. In the Alarm Notifications list box, specify one or multiple ways to issue the alert notifications. Available methods vary, depending on how many notification-based actions have been created. Notification-based action types include:  External beeper ...
Page 269 Chapter 6: Using the Web Interface Action Group You can create an action group that performs up to 32 actions. After creating such an action group, you can easily assign this set of actions to any event rule rather than selecting all needed actions one by one per rule.
Page 270 Chapter 6: Using the Web Interface Warning: If you create an event rule for the external beeper but disconnect it when an event causes it to beep, the beeper no longer beeps after it is re-connected even though the event triggering the beeping action remains asserted.
Page 271 Chapter 6: Using the Web Interface Push Out Sensor Readings You can configure the SRC to push sensor log to a remote server after a certain event occurs, including logs of internal sensors, environmental sensors and actuators. If you have connected Raritan's asset strips to the SRC, you can also configure the SRC to push the data to a server.
Page 272 Chapter 6: Using the Web Interface The maximum amount of snapshots that can be stored on the SRC is 10. If you set it for a number greater than 10 and the storage location is on the SRC, after the 10th snapshot is taken and stored, the oldest snapshots are overwritten.
Page 273 Chapter 6: Using the Web Interface Folder name options Definition Serial number / Webcam name Three folders will be created. / Formatted timestamp  Definitions of the parent folder and first subfolder are the same as the first row.  The final subfolder's name is the time when the recording event occurs, which is a format comprising year, month, date, hour, minute, second and timezone.
Page 274 Chapter 6: Using the Web Interface 3. In the Available LHX/SHX field, select the desired SHX-30 device one by one, or click Select All. 4. To remove any SHX-30 device from the Selected LHX/SHX field, click that device's or click Deselect All. Send Email You can configure emails to be sent when an event occurs and can customize the message.
Page 275 Chapter 6: Using the Web Interface When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 283).
Page 276 Chapter 6: Using the Web Interface Send Sensor Report You may set the SRC so that it automatically reports the latest readings or states of one or multiple sensors by sending a message or email or simply recording the report in a log. These sensors can be either internal or environmental sensors listed below.
Page 277 Chapter 6: Using the Web Interface b. Click the second to select the specific sensor for the target from the list. c. Click to add the selected sensor to the Report Sensors list box. For example, to monitor the current reading of the Inlet 1, select Inlet 1 from the left field, and then select RMS Current from the right field.
Page 278 Chapter 6: Using the Web Interface Send SMS Message You can configure SMS messages to be sent when an event occurs and can customize the message. Only the 7-bit ASCII charset is supported for SMS messages. Messages consist of a combination of free text and SRC placeholders. The placeholders represent information which is pulled from the SRC and inserted into the message.
Page 279 Chapter 6: Using the Web Interface  When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 283).
Page 280 Chapter 6: Using the Web Interface 4. By default, the SMTP server specified on the SMTP Server page will be the SMTP server for performing this action. To use a different SMTP server, select the 'Use custom SMTP server' checkbox. The fields for customized SMTP settings appear. For Configuring SMTP Settings information on each field, see (on page...
Page 281 Chapter 6: Using the Web Interface  To start a new line in the text box, press Enter. Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket.
Page 282 Chapter 6: Using the Web Interface Tip: An SNMP v2c notification action permits only a maximum of three SNMP destinations. To assign more than three SNMP destinations to a specific rule, first create several SNMP v2c notification actions, each of which contains completely different SNMP destinations, and then add all of these SNMP v2c notification actions to the same rule.
Page 283 Chapter 6: Using the Web Interface Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" Select this if authorization is required but no privacy protocols are required.  Select the authentication protocol - MD5 or ...
Page 284 Chapter 6: Using the Web Interface b. Type the key and value. c. Repeat the same steps to enter more arguments as needed.  To remove any existing argument, click adjacent to Switch LHX/SHX If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available.
Page 285 Chapter 6: Using the Web Interface 4. To select the actuator(s) where this action will be applied, select them one by one from the 'Available actuators' list.  To add all actuators, click Select All. 5. To remove any selected actuator from the 'Selected actuators' field, click that actuator's ...
Page 286 Chapter 6: Using the Web Interface Transport Next steps protocols A TLS certificate is required. Do the following: a. Type an appropriate port number in the 'TCP port' field. Default is 6514. b. In the 'CA certificate' field, click to select a TLS certificate. After importing the certificate, you may: ...
Page 287 Chapter 6: Using the Web Interface  To select all available actions, click Select All. 3. To remove any action(s) from the 'Selected actions' field, click that action's  To remove all actions, click Deselect All. 4. Select the desired frequency in the 'Execution time' field, and then specify the time interval or a specific date and time in the field(s) that appear.
Page 288 Chapter 6: Using the Web Interface Execution Frequency settings time Click the Frequency field to select an option. Minutes The frequency ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes. Type a value in the Minute field, which is set to either of the Hourly following: ...
Page 289 Chapter 6: Using the Web Interface Execution Frequency settings time This option requires three settings: Yearly  Month - January through December.  Day of month - 1 to 31.  Time - the value is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.
Page 290 Chapter 6: Using the Web Interface  If wanted, you can customize the subject and content of this email in this action.
Page 291 Chapter 6: Using the Web Interface...
Page 292 Chapter 6: Using the Web Interface 2. Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination Send Sensor Report action. For details, see (on page 264).  Send Temperature Sensor In this example, this action is named Readings...
Page 293 Chapter 6: Using the Web Interface  You can specify more than one temperature sensor as needed in this action. 3. Click to create a timer for performing the 'Send Temperature Sensor Readings' action hourly. Scheduling an Action For details, see (on page 274).
Page 294 Chapter 6: Using the Web Interface  Hourly Temperature Sensor In this example, the timer is named Reports  To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set the Minute to 30. Then the SRC will send out an email containing the specified temperature sensor readings hourly every day.
Page 295 Chapter 6: Using the Web Interface Placeholders for Custom Messages Actions of "Send email" and "Send SMS message" allow you to customize event messages. See Send Email (on page 262) or Send SMS Message (on page 266). In addition, you can add custom text message to Send Snapshots via Email the "Send snapshots via email"...
Page 296 Chapter 6: Using the Web Interface Placeholder Definition [AMSLEDOPMODE] The LED operating mode [AMSNAME] The name of an asset strip [AMSNUMBER] The numeric ID of an asset strip [AMSRACKUNITPOSITION] The (vertical) rack unit position [AMSSTATE] The human-readable state of an asset strip [AMSTAGID] The asset tag ID [CARDREADERCHANNEL]...
Page 297 Chapter 6: Using the Web Interface Placeholder Definition [ISASSERTED] Boolean flag whether an event condition became true (1) or false (0) [LDAPERRORDESC] The LDAP error occurred [LHXFANID] The ID of a fan connected to an LHX/SHX [LHXPOWERSUPPLYID] The ID of an LHX/SHX power supply [LHXSENSORID] The ID of an LHX/SHX sensor probe [LOGMESSAGE]...
Page 298 Chapter 6: Using the Web Interface Placeholder Definition [SMARTCARDTYPE] The type of a smart card [SMTPRECIPIENTS] The list of recipients of an outgoing mail [SMTPSERVER] The name or IP address of an SMTP server [SYSCONTACT] SNMP MIB-II sysContact field [SYSLOCATION] SNMP MIB-II sysLocation field [SYSNAME] SNMP MIB-II sysName field...
Page 299 Chapter 6: Using the Web Interface  To delete it, click on the top-right corner. Then click Delete on the confirmation message. Sample Event Rules Sample Device-Level Event Rule In this example, we want the SRC to record in the internal log when the network link is up to down.
Page 300 Chapter 6: Using the Web Interface Sample Sensor-Level Event Rule In this example, we want the SRC to send a notification email when a contact closure sensor enters the alarmed state. This event rule requires creating a new action before creating the rule. Step 1: create a new action for sending an email 1.
Page 301 Chapter 6: Using the Web Interface 6. Click Create to finish the creation.
Page 302 Chapter 6: Using the Web Interface After the new action is created, follow the procedure below to create an event rule that sends a notification email when the contact closure sensor enters the alarmed state. This event rule involves the following: ...
Page 303 Chapter 6: Using the Web Interface 8. Select "Send a Notification" from the Available Actions list. Sample Asset-Management-Level Event Rule In this example, we want the SRC to record the connection and disconnection events of a specific asset tag in the internal log. The event rule is set like this: ...
Page 304 Chapter 6: Using the Web Interface 4. Select "Tag Connected" as the events we want to record are related to physical tag connections or disconnections. 5. Select the Both radio button since we want both connection and disconnection actions to be recorded when either event occurs. 6.
Page 305 Chapter 6: Using the Web Interface Example 1 This example illustrates an event rule which continuously causes the SRC to send out email messages. Event selected Action included Device > Sending SMTP message failed Send email Example 2 This example illustrates an event rule which continuously causes the SRC to send out SMTP messages when one of the selected events listed on the Device menu occurs.
Page 306: Setting Data Logging
Chapter 6: Using the Web Interface Setting Data Logging The SRC can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using SNMP. You can configure how often measurements are written into the data log using the Measurements Per Log Entry field.
Page 307: Configuring Data Push Settings
Chapter 6: Using the Web Interface  If any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages.
Page 308 Chapter 6: Using the Web Interface Note: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see (on page 665). Certificate Chain 5. If the destination server requires authentication, select the 'Use authentication' checkbox, and enter the following data.
Page 309 Chapter 6: Using the Web Interface  To modify settings, make necessary changes and then click Save.  To delete it, click , and then confirm it on the confirmation message. Data Push Format Each push message contains exactly one JSON object. The data format is formally defined in IDL files, sharing several definitions from the JSON-RPC data model.
Page 310 Chapter 6: Using the Web Interface Asset Management Tag List The root object of the asset management tag list message is an AssetStripsMessage structure. It contains current data about all connected asset management strips and tags, which is similar to the illustration below.
Page 311 Chapter 6: Using the Web Interface...
Page 312 Chapter 6: Using the Web Interface (Continued)
Page 313 Chapter 6: Using the Web Interface Asset Management Tag Log The root object of the asset management log message is an AssetLogPushMessage structure. It contains a list of tag or strip events since the last successful push. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.
Page 314: Monitoring Server Accessibility
Chapter 6: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the SRC continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.
Page 315 Chapter 6: Using the Web Interface Field Description Wait time after The wait time before sending the next ping unsuccessful ping if the previous ping was not responded. Valid range is 3 to 600 (seconds). Number of The number of consecutive pings without consecutive any response before the monitored unsuccessful pings...
Page 316 Chapter 6: Using the Web Interface In the beginning, the status of the added IT equipment shows "Waiting for reliable connection," which means the requested number of consecutive successful or unsuccessful pings has not reached before SRC can declare that the monitored device is reachable or unreachable. To check the server monitoring states and results: 1.
Page 317 Chapter 6: Using the Web Interface Example: Ping Monitoring and SNMP Notifications In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored by your SRC to make sure that PDU is properly operating all the time, and the SRC must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure.
Page 318 Chapter 6: Using the Web Interface Field Data entered Wait time before resuming pinging after failure  The "Number of consecutive failures before disabling feature (0 = unlimited)" can be set to any value you want. 5. Click Create. Step 2: Create an event rule to send SNMP notifications for the target PDU 1.
Page 319: Front Panel Settings
Chapter 6: Using the Web Interface Front Panel Settings You can set up the default mode of the front panel display, and front panel functions for outlet switching, actuator control, beeper mute or RCM self-test. Below are available front panel settings: ...
Page 320: Configuring The Serial Port
Chapter 6: Using the Web Interface Configuring the Serial Port You can change the bit rate of the serial port labeled CONSOLE / MODEM on the SRC. The default bit rate for console and modem operation is 115200 bps. The SRC supports using the following devices via the serial interface: ...
Page 321: Lua Scripts
Chapter 6: Using the Web Interface 2. Click the 'Console baud rate' field to select the baud rate intended for console management. Note: For a serial RS-232 or USB connection between a computer and the SRC, leave it at the default (115200 bps). 3.
Page 322 Chapter 6: Using the Web Interface Writing or Loading a Lua Script You can enter or load up to 4 scripts to the SRC. Tip: If you can no longer enter or load a new script after reaching the upper limit, you can either delete any existing script or simply modify/replace an existing script's codes.
Page 323 Chapter 6: Using the Web Interface 5. In the Source Code section, do one of the following. It is recommended to leave the Enable Syntax Highlighting checkbox selected unless you do not need different text colors to identify diverse code syntaxes. ...
Page 324 Chapter 6: Using the Web Interface Manually Starting or Stopping a Script You can manually start or stop an existing Lua script at any time. When starting a script, you can choose to start it either with its default arguments or with new arguments. Tip: To have the SRC automatically start or stop a script in response to an event, create an event rule.
Page 325 Chapter 6: Using the Web Interface  Click if needing additional arguments. 5. Click Start. 6. The script output will be shown in the Script Output section.  If needed, click to delete the existing output data. To manually stop a script: 1.
Page 326 Chapter 6: Using the Web Interface To return to the scripts list:  Click "Lua Scripts" on the top of the page.  Menu Or click "Lua Scripts" in the (on page 104). Checking Lua Scripts States Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script.
Page 327: Miscellaneous
Chapter 6: Using the Web Interface Modifying or Deleting a Script You can edit an existing script's codes or even replace it with a new script. Or you can simply remove a unnecessary script from the SRC. To modify or replace a script: 1.
Page 328 Chapter 6: Using the Web Interface disabling USB-A. To enable the support for Schroff LHX/SHX: 1. Select the LHX/SHX checkbox. Features 2. Click Save in the section. 3. Click Apply on the confirmation message. 4. SRC reboots. To disable the access to USB-A port(s): 1.
Page 329: Maintenance
Chapter 6: Using the Web Interface Maintenance Menu Click 'Maintenance' in the (on page 104), and the following submenu displays. Submenu command Refer to... Device Information Device Information (on page 318)
Page 330: Viewing Connected Users
Chapter 6: Using the Web Interface Submenu command Refer to... Viewing Connected Users Connected Users (on page 323) Viewing or Clearing the Local Event Log Event Log (on page 325) Updating the SRC Firmware Update Firmware (on page 326) Viewing Firmware Update History Firmware History (on page 329) Bulk Configuration...
Page 331 Chapter 6: Using the Web Interface Device Information Using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your SRC. Tip: If the information shown on this page does not match the latest status, press F5 to reload it.
Page 332 Chapter 6: Using the Web Interface 2. Click the desired section's title bar to show that section's information. For example, click the Network section. The number of available sections is model dependent. Section title Information shown Information General device information, such as model name, serial number, firmware version, hardware revision, MIB download link(s) and so on.
Page 333 Chapter 6: Using the Web Interface Identifying Cascaded Devices Cascading Multiple For information on how to cascade SRC devices, see SRC Devices for Sharing Ethernet Connectivity (on page 24). This section explains how to identify a cascaded device on the Device Information page.
Page 334 Chapter 6: Using the Web Interface Cascading information in the Port Forwarding mode:  The Common section contains three read-only fields for indicating the cascading status. Fields Description Port forwarding Indicates the Port Forwarding is enabled. See Setting the Cascading Mode (on page 187).
Page 335 Chapter 6: Using the Web Interface  A master device shows (zero) in the 'Cascade position' field and in the 'Cascaded device connected' field.  A slave device in the middle position shows a non-zero number which indicates its exact position in the 'Cascade position' field in the 'Cascaded device connected' field.
Page 336 Chapter 6: Using the Web Interface The following diagram shows 2, indicating it is the second slave device - Slave 2. The 'Cascaded device connected' field shows indicating that it is the final one in the chain.  For a list of port numbers required for accessing each cascaded device in the Port Forwarding mode, click the Port Forwarding title bar on the same page.
Page 337 Chapter 6: Using the Web Interface If wanted, you can resort the list by clicking the desired column Sorting a List header. See (on page 107). Column Description User Name The login name of each connected user. IP Address The IP address of each user's host. For the login via a local connection (serial RS-232 or USB), <local>...
Page 338 Chapter 6: Using the Web Interface The IP address refers to the IP address of the host where the Primary Standalone Live Preview window exists, NOT the IP address of the other two associated sessions. Webcam Management For more webcam information, see (on page 342).
Page 339 Chapter 6: Using the Web Interface Updating the SRC Firmware Firmware files are available on Raritan website's Support page http://www.raritan.com/support/ You must be the administrator or a user with the Firmware Update permission to update the SRC firmware. Before starting the upgrade, read the release notes downloaded from Support page http://www.raritan.com/support/ Raritan website's...
Page 340 Chapter 6: Using the Web Interface  Other users' operation, if any, is forced to suspend. 7. When the update is complete, the SRC resets, and the Login page re-appears.  Other logged-in users are logged out when the firmware update is complete.
Page 341 3.5.0, 3.4.0, and so on. Therefore, it is suggested to AVOID downgrading your cascading chain unless instructed by Raritan or Legrand Technical Support. For minimum firmware versions, see Cascading Restrictions in the...
Page 342 There is no downgrade sequence limitation. However, firmware downgrade in a cascading chain is NOT recommended. Consult Raritan (or Legrand) Technical Support first if downgrade is needed. Firmware versions earlier than 3.3.10 are compatible with any pre-3.3.10 version so you can downgrade or upgrade all devices of the chain in a random order when all firmware versions in the chain are prior to version 3.3.10.
Page 343: Bulk Configuration
Chapter 6: Using the Web Interface Bulk Configuration The Bulk Configuration feature lets you save generic settings of a configured SRC device to your computer. You can use this configuration file to copy common settings to other SRC devices of the same model and firmware version.
Page 344 Chapter 6: Using the Web Interface Note: On startup, SRC performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the "Bulk configuration copied"...
Page 345 Chapter 6: Using the Web Interface 2. Choose Maintenance > Bulk Configuration. 3. Click in the Bulk Profiles section. 4. In the 'Profile name' and 'Description' fields, enter information for identifying the new profile. 5. To make this new profile the default one for future bulk configuration operations, select the 'Select as default profile' checkbox.
Page 346 Chapter 6: Using the Web Interface 8. Repeat the same steps if you want to create more bulk profiles. Performing Bulk Configuration On the source device, make sure the wanted profile has been set as the default one. If not, start from step 1 below. If yes, go to step 2 directly. Step 1: Select the desired bulk configuration profile (optional) 1.
Page 347 Chapter 6: Using the Web Interface 4. Click Download Bulk Configuration. 5. When prompted to open or save the configuration file, click Save. Step 3: Perform bulk configuration You must have the Administrator Privileges to upload the configuration. 1. Log in to the target SRC, which is of the same model and runs the same firmware as the source SRC.
Page 348 Chapter 6: Using the Web Interface 2. Change the settings you want. 3. Click Save. To remove a single profile: 1. Click on the row of the wanted profile. 2. Click on the top-right corner. 3. Click Delete on the confirmation message. To remove one or multiple profiles: 1.
Page 349: Backup And Restore Of Device Settings
Chapter 6: Using the Web Interface Backup and Restore of Device Settings Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specific data like device names and all network settings. To back up or restore the settings of SRC, you should perform the Backup/Restore feature.
Page 350: Network Diagnostics
Chapter 6: Using the Web Interface 5. Wait until the SRC resets and the Login page re-appears, indicating that the restore is complete. Note: On startup, SRC performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset.
Page 351: Downloading Diagnostic Information
Chapter 6: Using the Web Interface Field Description Number of A number up to 20. requests This determines how many packets are sent for pinging the host. 2. Click Run Ping to ping the host. The Ping results are then displayed. Trace Route: 1.
Page 352: Hardware Issue Detection
Chapter 6: Using the Web Interface Hardware Issue Detection This page lists any internal hardware issues SRC has detected, including current events and historical records. Choose Maintenance > Hardware Failures, and the page similar to either of the following diagrams opens. NO hardware failures detected: Hardware failure(s) detected: Hardware Failure alerts on the Dashboard page:...
Page 353: Rebooting The Src
Chapter 6: Using the Web Interface Rebooting the SRC You can remotely reboot the SRC via the web interface. Warning: Rebooting the SRC deletes all webcam snapshots that are saved onto the SRC locally. If needed, download important snapshots Viewing and Managing before rebooting the device.
Page 354: Retrieving Software Packages Information
Chapter 6: Using the Web Interface To reset the device to factory defaults: 1. Choose Maintenance > Unit Reset > 2. Type your password and then click Factory Reset to reset the SRC to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation.
Page 355: Webcam Management
Chapter 6: Using the Web Interface Webcam Management The 'Webcams' menu item appears when there is any webcam(s) connected to the SRC, or when there are snapshots saved onto the SRC Connecting a Logitech Webcam already. See (on page 66).
Page 356 Chapter 6: Using the Web Interface With a Logitech webcam connected to the SRC, you can visually monitor ® the environment around the SRC via snapshots or videos captured by the webcam. Permissions required: To do... Permission(s) required Either permission below: View snapshots and videos ...
Page 357: Configuring Webcams And Viewing Live Images
Chapter 6: Using the Web Interface Configuring Webcams and Viewing Live Images To configure a webcam or view live snapshot/video sessions, choose Menu Webcams in the (on page 104). Then click the desired webcam to open that webcam's page. Note that default webcam names are determined by the detection order. Webcam The one that is detected first is named , and the other that is...
Page 358 Chapter 6: Using the Web Interface Tip: The date and time shown on the SRC web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of SRC to your computer or mobile device.
Page 359 Chapter 6: Using the Web Interface Settings: 1. By default the Settings section is open. If not, click the Settings title bar. 2. Click Edit Settings. 3. Enter a name for the webcam. Up to 64 ASCII printable characters are supported. ...
Page 360: Sending Links To Snapshots Or Videos
Chapter 6: Using the Web Interface To return to the Webcam Management page:  Click Webcam Management on the top of the page.  Menu Or click Webcams again in the (on page 104). Sending Links to Snapshots or Videos When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session.
Page 361 Chapter 6: Using the Web Interface  Note that default webcam names are determined by the Webcam detection order. The one that is detected first is named Webcam 2 and the other that is detected later is named 3. Click in the Live Preview section.
Page 362: Viewing And Managing Locally-Saved Snapshots
Chapter 6: Using the Web Interface How Long a Link Remains Accessible For documentation purposes, the one who opens and sends the URL of the Primary Standalone Live Preview window is called User A and the two recipients of the same URL link are called User B User C is able to access the snapshot or video image via the link when the URL link remains valid, which can be one of these scenarios:...
Page 363 Chapter 6: Using the Web Interface saved onto the SRC locally. If needed, download important snapshots before rebooting the device. To view saved snapshots: 1. Choose Webcams > . The Snapshots page opens. 2. Click the snapshot you want to view from the list. Tip: The date and time shown on the SRC web interface are automatically converted to your computer's time zone.
Page 364 Chapter 6: Using the Web Interface  To select all images, select the topmost checkbox in the header row. 3. On the top of the list, click 4. Click Delete on the confirmation message. To download any image onto the computer: ...
Page 365: Changing Storage Settings
Chapter 6: Using the Web Interface Changing Storage Settings Important: The SRC web interface only lists the snapshots stored locally on the SRC device, but does NOT list those saved onto remote servers. You must launch appropriate third-party applications, such as an FTP client, to access and manage the snapshots stored on remote servers.
Page 366 Chapter 6: Using the Web Interface Storage location Description 'Local' means the SRC. This is the default. Local  It can store a maximum of 10 snapshots only.  The web interface can list and display all Viewing and snapshots stored on the SRC. See Managing Locally-Saved Snapshots (on page 349).
Page 367 Chapter 6: Using the Web Interface Tip for notifications showing the snapshots path on FTP: If you are using SNMP to retrieve SRC data, you can make SRC automatically send a notification containing the full path or URL to the snapshots saved onto FTP with this SNMP code: webcamStorageUploadStarted.
Page 368 Chapter 6: Using the Web Interface Number Folder name description The name of the webcam that your SRC detects first. This is the folder where the snapshots captured by the first webcam are stored.  The first webcam's default name is "Webcam". ...
Page 369: Smartlock And Card Reader
Chapter 6: Using the Web Interface SmartLock and Card Reader Menu SmartLock and Card Reader pages show up in the (on page 104) in either scenario below:  Your SRC is a model with onboard door handle ports. Such a model contains a built-in DX2-DH2C2 module.
Page 370: Smartlock
Chapter 6: Using the Web Interface Note that "SmartLock" appears only when your door handles are connected to SRC via DX2-DH2C2, but "Card Readers" appears as long as SRC detects the presence of any card reader -- either a standalone USB card reader or a card reader integrated with the door handles.
Page 371 Chapter 6: Using the Web Interface SmartLock To open the SmartLock page, choose SmartLock in the Menu (on page 104). The page shows information of all DX2-DH2C2 modules attached to SRC, including its serial number, position and its door handle configuration. On this page you can: ...
Page 372 Chapter 6: Using the Web Interface  Configure the door handles connected to DX2-DH2C2. You must set this because SRC cannot detect the types of connected door handles.  Control the door handles connected to DX2-DH2C2. To configure the door handles: There are two door handle sections per DX2-DH2C2 because a DX2-DH2C2 has two door handle ports.
Page 373 Chapter 6: Using the Web Interface Section Description  Specify how long the door handle lock can remain Timeout open after someone opens the door handle via a smart card or via remote control using the software. When the timeout expires, the door handle lock will be automatically closed.
Page 374 Chapter 6: Using the Web Interface Door Handle Status and Control After configuring the door handle type properly, two more sections are shown for the configured door handle -- Door State and Card Reader.
Page 375: Card Readers
Chapter 6: Using the Web Interface To view the status of the door and card reader: Section Description Shows all sensor states detected by DX2-DH2C2, Door State including:  Door : States of contact closure sensors connected to DX2-DH2C2. Contact closure sensors detect whether the door is physically opened or closed.
Page 376 Chapter 6: Using the Web Interface 2. Go to the proper door handle section, and click Open or Close to open or close the door handle lock. 3. Confirm the operation when prompted. 4. Now you can physically open the cabinet door with the opened door handle.
Page 377 Chapter 6: Using the Web Interface When a user scans his/her smart card with the card reader, SRC will retrieve the card's type and ID and show them in the corresponding Card Type and Card ID column. If no data is shown in the two columns, it means the scanned card may not be supported by the card reader.
Page 378: Chapter 7 Using Snmp
Chapter 7 Using SNMP This SNMP section helps you set up the SRC for use with an SNMP manager. The SRC can be configured to send traps or informs to an SNMP manager, as well as receive GET and SET commands in order to retrieve status and configure some basic settings.
Page 379: Snmpv2C Notifications
Chapter 7: Using SNMP To enable SNMP notifications: 1. Choose Device Settings > Network Services > SNMP. 2. In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to:  SNMPv2c Notifications (on page 366) ...
Page 380 Chapter 7: Using SNMP Field Description Timeout 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. Number of retries The number of times you want to resend the inform communication if it fails.
Page 381 Chapter 7: Using SNMP 3. In the SNMP Notifications section, make sure the 'Enable SNMP notifications' checkbox is selected. 4. Select 'SNMPv3 trap' or 'SNMPv3 inform' as the notification type. 5. For SNMP TRAPs, the engine ID is prepopulated. 6. Type values in the following fields. Field Description Host...
Page 382 Chapter 7: Using SNMP Field Description This is the address to which notifications are sent by the SNMP agent. Port The port number used to access the device(s). User ID User name for accessing the device.  Make sure the user has the SNMP v3 access permission.
Page 383: Downloading Snmp Mib
Chapter 7: Using SNMP Downloading SNMP MIB You must download an appropriate SNMP MIB file for successful SNMP communications. Always use the latest SNMP MIB downloaded from the current firmware of your SRC. You can download the MIBs from two different pages of the web interface.
Page 384: Snmp Gets And Sets
Chapter 7: Using SNMP SNMP Gets and Sets In addition to sending notifications, the SRC is able to receive SNMP get and set requests from third-party SNMP managers.  Get requests are used to retrieve information about the SRC, such as the system location.
Page 385 Chapter 7: Using SNMP Layout Opening the MIB reveals the custom objects that describe the SRC system. As standard, these objects are first presented at the beginning of the file, listed under their parent group. The objects then appear again individually, defined and described in detail.
Page 386: A Note About Enabling Thresholds
Chapter 7: Using SNMP Configuring NTP Server Settings Using SNMP, you can change the following NTP server-related settings in the unitConfigurationTable:  Enable or disable synchronization of the device's date and time with NTP servers (synchronizeWithNTPServer)  Enable or disable the use of DHCP-assigned NTP servers if synchronization with NTP servers is enabled (useDHCPProvidedNTPServer) ...
Page 387: Chapter 8 Using The Command Line Interface
Chapter 8 Using the Command Line Interface This section explains how to use the command line interface (CLI) to administer the SRC. Note that available CLI commands are model dependent. CLI commands are case sensitive. In This Chapter About the Interface.................. 374 Logging in to CLI..................
Page 388: Logging In To Cli
Chapter 8: Using the Command Line Interface Logging in to CLI Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or Telnet. If a security login agreement has been enabled, you must accept the agreement in order to complete the login.
Page 389: With Ssh Or Telnet
Chapter 8: Using the Command Line Interface After properly entering the password, the # or > system prompt Different CLI Modes and Prompts appears. See (on page 377) in the User Guide for more information. Tip: The 'Last login' information, including the date and time, is also displayed if the same user account was used to log in to this product's web interface or CLI.
Page 390: With An Analog Modem
Chapter 8: Using the Command Line Interface With an Analog Modem The SRC supports remote access to the CLI via a connected analog modem. This feature is especially useful when the LAN access is not available. To connect to the SRC via the modem: 1.
Page 391: Different Cli Modes And Prompts
Chapter 8: Using the Command Line Interface Different CLI Modes and Prompts Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.  User Mode: When you log in as a normal user, who may not have full permissions to configure the SRC, the >...
Page 392: Querying Available Parameters For A Command
Chapter 8: Using the Command Line Interface config:# In the diagnostic mode: diag:# Press Enter after pressing the ? command, and a list of main commands for the current mode is displayed. Tip: To automatically complete a command after typing part of the full command, see (on page 524).
Page 393: Showing Information
Chapter 8: Using the Command Line Interface config:# role create ? Tip: To automatically complete a command after typing part of the full command, see (on page 524). Automatically Completing a Command To re-execute one of the previous commands, see Retrieving Previous (on page 524).
Page 394 Chapter 8: Using the Command Line Interface IP Configuration This command shows the IP settings shared by all network interfaces, such as DNS and routes. Information shown will include both IPv4 and IPv6 configuration. Tip: To show IPv4-only and IPv6-only configuration data, see IPv4-Only (on page 382).
Page 395 Chapter 8: Using the Command Line Interface IPv4-Only or IPv6-Only Configuration To show IPv4-only or IPv6-only configuration, use any of the following commands. Tip: To show both IPv4 and IPv6 configuration data, see IP Configuration (on page 381). To show IPv4 settings shared by all network interfaces, such as DNS and routes: show network ipv4 common To show IPv6 settings shared by all network interfaces, such as...
Page 396 Chapter 8: Using the Command Line Interface Interface Description bridge Show the IPv4 or IPv6 configuration of the BRIDGE interface. Show the IPv4 or IPv6 configuration of all interfaces. Tip: You can also type the command without adding this option "all" to get the same data. That show network ipv4 interface Network Interface Settings This command shows the specified network interface's information...
Page 397 Chapter 8: Using the Command Line Interface Network Service Settings This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS, SSH and Modbus/TCP services, and SNMP settings. show network services <option> Variables:  <option>...
Page 398: Src Configuration
Chapter 8: Using the Command Line Interface SRC Configuration This command shows the SRC configuration, such as the device name, firmware version, model type and upper limit of active powered dry contact actuators. show src To show detailed information, add the parameter "details" to the end of the command.
Page 399: Environmental Sensor Information
Chapter 8: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. show externalsensors <n> To show detailed information, add the parameter "details" to the end of the command. show externalsensors <n> details Variables: ...
Page 400: Environmental Sensor Package Information
Chapter 8: Using the Command Line Interface * The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the SRC web interface. Displayed information:  Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Page 401: Actuator Information
Chapter 8: Using the Command Line Interface Actuator Information This command syntax shows an actuator's information. show actuators <n> To show detailed information, add the parameter "details" to the end of the command. show actuators <n> details Variables:  <n> is one of the options: , or a number.
Page 402: Environmental Sensor Threshold Information
Chapter 8: Using the Command Line Interface Environmental Sensor Threshold Information This command syntax shows the specified environmental sensor's threshold-related information. show sensor externalsensor <n> To show detailed information, add the parameter "details" to the end of the command. show sensor externalsensor <n> details...
Page 403: Environmental Sensor Default Thresholds
Chapter 8: Using the Command Line Interface Variables:  <n> is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the SRC web interface. Displayed information: ...
Page 404: Security Settings
Chapter 8: Using the Command Line Interface Sensor types Description vibration Vibration sensors All of the above numeric sensors Tip: You can also type the command without adding this option "all" to get the same data. Displayed information:  Without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed.
Page 405: Authentication Settings
Chapter 8: Using the Command Line Interface Authentication Settings General authentication settings: This command displays the authentication settings of the SRC, including both LDAP and Radius settings. show authentication One LDAP server's settings: To show the configuration of a specific LDAP server, assign the desired LDAP server with its sequential number in the command.
Page 406: Existing User Profiles
Chapter 8: Using the Command Line Interface  With the parameter "details" added, detailed information of the specified server is displayed, such as an LDAP server's bind DN and the login name attribute, or a Radius server's timeout and retries values.
Page 407: Existing Roles
Chapter 8: Using the Command Line Interface Existing Roles This command shows the data of one or all existing roles. show roles <role_name> Variables:  <role_name> is the name of the role whose permissions you want to query. The variable can be one of the following options: Option Description This option shows all existing roles.
Page 408: Asset Strip Settings
Chapter 8: Using the Command Line Interface Asset Strip Settings This command shows the asset strip settings, such as the total number of rack units (tag ports), asset strip state, numbering mode, orientation, available tags and LED color settings. show assetStrip <n> Variables: ...
Page 409: Event Log
Chapter 8: Using the Command Line Interface Option Description A specific Displays the settings of the specified rack unit on number the specified asset strip. Use the index number to specify the rack unit. The index number is available on the asset strip or the Asset Strip page of the web interface.
Page 410: Network Connections Diagnostic Log
Chapter 8: Using the Command Line Interface Event type Description device Device-related events, such as system starting or firmware upgrade event. userAdministration User management events, such as a new user profile or a new role. userActivity User activities, such as login or logout. sensor Internal or external sensor events, such as state changes of any sensors.
Page 411 Chapter 8: Using the Command Line Interface Server Reachability Information for a Specific Server To show the server reachability information for a certain IT device only, use the following command. show serverReachability server <n> To show detailed information, add the parameter "details" to the end of the command.
Page 412: Command History
Chapter 8: Using the Command Line Interface Command History This command 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. Reliability Data This command shows the reliability data.
Page 413: Examples
Chapter 8: Using the Command Line Interface Examples This section provides examples of the show command. Example 1 - Basic Security Information show security The diagram shows the output of the command.
Page 414: Clearing Information
Chapter 8: Using the Command Line Interface Example 2 - In-Depth Security Information More information is displayed when typing the show security details command. Clearing Information You can use the clear commands to remove unnecessary data from the SRC. After typing a "clear" command, press Enter to execute it. Note: Depending on your login name, the # prompt may be replaced by the >...
Page 415: Clearing Event Log
Chapter 8: Using the Command Line Interface Clearing Event Log This command removes all data from the event log. clear eventlog -- OR -- clear eventlog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the event log or n to abort the operation.
Page 416: Entering Configuration Mode
Chapter 8: Using the Command Line Interface Entering Configuration Mode Configuration commands function in configuration mode only. To enter configuration mode: 1. Ensure you have entered administrator mode and the # prompt is displayed. Note: If you enter configuration mode from user mode, you may have limited permissions to make configuration changes.
Page 417: Src Configuration Commands
Chapter 8: Using the Command Line Interface SRC Configuration Commands One SRC configuration command begins with . You can use the SRC configuration commands to change the settings that apply to the whole SRC device. Configuration commands are case sensitive so ensure you capitalize them correctly.
Page 418 Chapter 8: Using the Command Line Interface Setting Data Logging Measurements Per Entry This command defines the number of measurements accumulated per log entry. config:# src measurementsPerLogEntry <number> Variables:  <number> is an integer between 1 and 600. The default is 60 samples per log entry.
Page 419: Network Configuration Commands
Chapter 8: Using the Command Line Interface Setting the Z Coordinate Format for Environmental Sensors This command enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors. config:# src externalSensorsZCoordinateFormat <option> Variables:  <option>...
Page 420 Chapter 8: Using the Command Line Interface Setting the IPv4 Configuration Mode This command determines the IP configuration mode. config:# network ipv4 interface <ETH> configMethod <mode> Variables:  <ETH> is one of the network interfaces: ETH1/ETH2 WIRELESS , or BRIDGE .
Page 421 Chapter 8: Using the Command Line Interface Setting the IPv4 Preferred Host Name After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command: config:# network ipv4 interface <ETH> preferredHostName <name> Variables: ...
Page 422 Chapter 8: Using the Command Line Interface Setting the IPv4 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the SRC. config:# network ipv4 interface <ETH> address <ip address> Variables: ...
Page 423 Chapter 8: Using the Command Line Interface Setting IPv4 Static Routes If the IPv4 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the SRC and devices in the other subnet.
Page 424 Chapter 8: Using the Command Line Interface config:# network ipv4 staticRoutes modify <route_ID> dest <dest-2> interface <ETH> Variables:  <dest-1> is a combination of the IP address and subnet mask of the other subnet. The format is IP address/subnet mask ...
Page 425 Chapter 8: Using the Command Line Interface Interface Description wireless Determine the IPv6 configuration mode of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 configuration mode of the BRIDGE interface (that is, bridging mode).  automatic static <mode>...
Page 426 Chapter 8: Using the Command Line Interface Interface Description bridge Determine the IPv6 preferred host name of the BRIDGE interface (that is, bridging mode).  <name> is a host name which:  Consists of alphanumeric characters and/or hyphens  Cannot begin or end with a hyphen ...
Page 427 Chapter 8: Using the Command Line Interface  <ip address> is the IP address being assigned to your SRC. This value uses the IPv6 address format. Note that you must add which indicates a prefix length of bits such as /64, to the end of this IPv6 address.
Page 428 Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes delete <route_ID> Modify an existing static route: config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2> nextHop <hop> -- OR -- config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2> interface <ETH>...
Page 429 <suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching for any device via SRC. For example, <suffix1> can be raritan.com , and <suffix2> can be legrand.com . You can specify up to 6 suffixes by separating them with commas.  preferV4 preferV6.
Page 430 Chapter 8: Using the Command Line Interface Option Description preferV6 Use the IPv6 addresses returned by the DNS server. Setting LAN Interface Parameters network ethernet A LAN interface configuration command begins with Enabling or Disabling the LAN Interface This command enables or disables the LAN interface. config:# network ethernet <ETH>...
Page 431 Chapter 8: Using the Command Line Interface Option Description eth2 ETH2 port  auto 10Mbps 100Mbps or 1000Mbps <option> is one of the options: Option Description auto System determines the optimum LAN speed through auto-negotiation. 10Mbps The LAN speed is always 10 Mbps. 100Mbps The LAN speed is always 100 Mbps.
Page 432 Chapter 8: Using the Command Line Interface Option Description full Full duplex: Data is transmitted in both directions simultaneously. Setting the Ethernet Authentication Method This command sets the authentication method for the selected Ethernet interface to either none or Extensible Authentication Protocol (EAP). config:# network ethernet <ETH>...
Page 433 Chapter 8: Using the Command Line Interface config:# network ethernet <ETH> eapInnerAuthentication <inner_auth> Set the EAP identity: config:# network ethernet <ETH> eapIdentity <identity> Set the EAP password: config:# network ethernet <ETH> eapPassword After performing the above command, the SRC prompts you to enter the password.
Page 434 Chapter 8: Using the Command Line Interface config:# network ethernet <ETH> allowConnectionWithIncorrectClock <option3> Set the RADIUS authentication server for EAP: config:# network ethernet <ETH> eapAuthServerName <FQDN> Variables:  eth1 or eth2 <ETH> is one of the options -- Option Description eth1 ETH1 port eth2...
Page 435 Chapter 8: Using the Command Line Interface  true false <option2> is one of the options: Option Description true Always make the network connection successful even though the TLS certificate chain contains any certificate which is outdated or not valid yet. false The network connection is NOT successfully established when the TLS certificate chain contains...
Page 436 Chapter 8: Using the Command Line Interface 5. Select and copy the contents as illustrated below, excluding the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE." MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA...
Page 437 Chapter 8: Using the Command Line Interface config:# Removing the Uploaded Certificate or Private Key The procedures of removing an existing client certificate, client private key or CA certificate in CLI are similar. This section illustrates such a procedure for the Ethernet interface "ETH1."...
Page 438 Chapter 8: Using the Command Line Interface Setting 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. network wireless A wireless configuration command begins with Note: If wireless networking mode is not enabled, the SSID, PSK and BSSID values are not applied until the wireless networking mode is...
Page 439 Chapter 8: Using the Command Line Interface Setting the Wireless Authentication Method This command 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: Method Description The authentication method is set to PSK.
Page 440 Chapter 8: Using the Command Line Interface Setting Wireless EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, client certificate, client private key, password, CA certificate, and RADIUS authentication server. For more information, see Wireless Network Settings (on page 177).
Page 441 Chapter 8: Using the Command Line Interface Allow expired and not yet valid TLS certificates: config:# network wireless allowOffTimeRangeCerts <option2> Allow wireless network connection with incorrect system time: config:# network wireless allowConnectionWithIncorrectClock <option3> Set the RADIUS authentication server for EAP: config:# network wireless eapAuthServerName <FQDN>...
Page 442 Chapter 8: Using the Command Line Interface  true false <option2> is one of the options: Option Description true Always make the network connection successful even though the TLS certificate chain contains any certificate which is outdated or not valid yet. false The network connection is NOT successfully established when the TLS certificate chain contains...
Page 443 Chapter 8: Using the Command Line Interface Configuring the Cascading Mode This command determines the cascading mode. config:# network <mode> enabled <option1> Variables:  <mode> is one of the following cascading modes. Mode Description bridge The Bridging mode, where each cascaded device is assigned a unique IP address.
Page 444 Chapter 8: Using the Command Line Interface If Port Forwarding mode is enabled, you must configure two more settings to finish the configuration: On ALL cascaded devices, you must configure the 'role' setting one by one. config:# network portForwarding role <option2> On the master device, you must configure the 'downstream interface' setting.
Page 445 Chapter 8: Using the Command Line Interface Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http Change the HTTP port: config:# network services http port <n> Enable or disable the HTTP port: config:# network services http enabled <option>...
Page 446 Chapter 8: Using the Command Line Interface Setting the HTTPS Port The commands used to configure the HTTPS port settings begin with network services https Change the HTTPS port: config:# network services https port <n> Enable or disable the HTTPS access: config:# network services https enabled <option>...
Page 447 Chapter 8: Using the Command Line Interface Option Description false The Telnet service is disabled. Changing the Telnet Port This command changes the Telnet port. config:# network services telnet port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Telnet port is 23.
Page 448 Chapter 8: Using the Command Line Interface Changing the SSH Port This command 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. Determining the SSH Authentication Method This command syntax determines the SSH authentication method.
Page 449 Chapter 8: Using the Command Line Interface Enabling or Disabling SNMP v1/v2c This command enables or disables the SNMP v1/v2c protocol. config:# network services snmp v1/v2c <option> Variables:  <option> is one of the options: enable disable Option Description enable The SNMP v1/v2c protocol is enabled.
Page 450 Chapter 8: Using the Command Line Interface Setting the SNMP Write Community This command 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.
Page 451 Chapter 8: Using the Command Line Interface Enabling or Disabling Modbus This command enables or disables the Modbus protocol. config:# network services modbus enabled <option> Variables:  <option> is one of the options: true false Option Description true The Modbus agent is enabled. false The Modbus agent is disabled.
Page 452 Chapter 8: Using the Command Line Interface Enabling or Disabling Service Advertising This command enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services. See Enabling Service Advertising (on page 207) for details. config:# network services zeroconfig <method>...
Page 453: Time Configuration Commands
Chapter 8: Using the Command Line Interface Example 3 - Wireless Authentication Method The following command sets the wireless authentication method to PSK. config:# network wireless authMethod PSK Example 4 - Static IPv4 Configuration The following command enables the Static IPv4 configuration mode on the ETH1 interface.
Page 454 Chapter 8: Using the Command Line Interface Setting NTP Parameters A time configuration command for NTP-related parameters begins with time ntp Specify the primary time server: config:# time ntp firstServer <first_server> Specify the secondary time server: config:# time ntp secondServer <second_server> To delete the primary time server: config:# time ntp firstServer ""...
Page 455 Chapter 8: Using the Command Line Interface Customizing the Date and Time To manually configure the date and time, use the following CLI commands to specify them. Note: You shall set the time configuration method to "manual" prior to customizing the date and time. See Determining the Time Setup (on page 440).
Page 456 Chapter 8: Using the Command Line Interface 2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter. 3. Type apply for the selected time zone to take effect. Setting the Automatic Daylight Savings Time This command determines whether the daylight saving time is applied to the time settings.
Page 457: Checking The Accessibility Of Ntp Servers
Chapter 8: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your SRC and then shows the result. For instructions on specifying NTP servers via CLI, see Setting NTP Parameters (on page 441).
Page 458 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 enabled <option> Determine the default IPv4 firewall control policy for inbound traffic: config:# security ipAccessControl ipv4 defaultPolicyIn <policy> Determine the default IPv4 firewall control policy for outbound traffic: config:# security ipAccessControl ipv4 defaultPolicyOut <policy>...
Page 459 Chapter 8: Using the Command Line Interface  <policy> is one of the options: accept, drop reject Option Description accept Accepts traffic from all IP addresses. drop Discards traffic from all IP addresses, without sending any failure notification to the source host. reject Discards traffic from all IP addresses, and an ICMP message is sent to the source host for...
Page 460 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <direction> <insert> <rule_number> <ip_mask> <policy>  IPv6 commands Add a new rule to the bottom of the IPv6 rules list: config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy> Add a new IPv6 rule by inserting it above or below a specific rule: config:# security ipAccessControl ipv6 rule add <direction>...
Page 461 Chapter 8: Using the Command Line Interface  <insert> is one of the options: insertAbove insertBelow Option Description insertAbove Inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number insertBelow Inserts the new rule below the specified rule number.
Page 462 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> policy <policy> Modify all contents of an IPv6 existing rule: config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask <ip_mask> policy <policy> Variables:  <direction> is one of the options: Direction Description Inbound traffic.
Page 463 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule delete <direction> <rule_number> IPv6 commands config:# security ipAccessControl ipv6 rule delete <direction> <rule_number> Variables:  <direction> is one of the options: Direction Description Inbound traffic. Outbound traffic.  <rule_number>...
Page 464 Chapter 8: Using the Command Line Interface After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails:  In the web interface, select the checkbox labeled "I understand and accept the restricted service agreement."...
Page 465 Chapter 8: Using the Command Line Interface Specifying the Agreement Contents This command allows you to create or modify contents of the Restricted Service Agreement. config:# security restrictedServiceAgreement bannerContent After performing the above command, do the following: 1. Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
Page 466 Chapter 8: Using the Command Line Interface Single Login Limitation This command enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted. config:# security loginLimits singleLogin <option> Variables:  <option> is one of the options: enable disable Option...
Page 467 Chapter 8: Using the Command Line Interface Idle Timeout This command determines how long a user can remain idle before that user is forced to log out of the SRC web interface or CLI. config:# security loginLimits idleTimeout <value> Variables: ...
Page 468 Chapter 8: Using the Command Line Interface Strong Passwords The strong password commands determine whether a strong password is required for login, and what a strong password should contain at least. A strong password command begins with security strongPasswords. You can combine multiple strong password commands to modify different parameters at a time.
Page 469 Chapter 8: Using the Command Line Interface Lowercase Character Requirement This command determines whether a strong password includes at least a lowercase character. config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables:  enable disable <option> is one of the options: Option Description enable At least one lowercase character is required.
Page 470 Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneNumericCharacter <option> Variables:  enable disable <option> is one of the options: Option Description enable At least one numeric character is required. disable No numeric character is required. Special Character Requirement This command determines whether a strong password includes at least a special character.
Page 471 Chapter 8: Using the Command Line Interface Role-Based 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.  security An IPv4 role-based access control command begins with roleBasedAccessControl ipv4 ...
Page 472 Chapter 8: Using the Command Line Interface Option Description false Disables the role-based access control feature.  allow deny <policy> is one of the options: Policy Description allow Accepts traffic from all IP addresses regardless of the user's role. deny Drops traffic from all IP addresses regardless of the user's role.
Page 473 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> Add a new IPv6 rule by inserting it above or below a specific rule: config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy>...
Page 474 Chapter 8: Using the Command Line Interface Modifying a Role-Based Access Control Rule Depending on what to modify in an existing rule, the command syntax varies.  IPv4 commands Modify a rule's IPv4 address range: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip>...
Page 475 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> policy <policy> Modify all contents of an existing IPv6 rule: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables: ...
Page 476 Chapter 8: Using the Command Line Interface Enabling or Disabling Front Panel Actuator Control The following CLI commands control whether you can turn on or off connected actuator(s) by operating the front panel LCD display. To enable the front panel actuator control feature: config:# security frontPanelPermissions add switchActuator To disable the front panel actuator control feature:...
Page 477 Chapter 8: Using the Command Line Interface Example 1 - IPv4 Firewall Control Configuration The following command sets up two parameters of the IPv4 access control feature. config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results:  The IPv4 access control feature is enabled. ...
Page 478: User Configuration Commands
Chapter 8: Using the Command Line Interface Example 4 - Adding an IPv4 Role-based Access Control Rule The following command creates a newIPv4 role-based access control rule and specifies its location in the list. config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3 Results: ...
Page 479 Chapter 8: Using the Command Line Interface  <roles> is a role or a list of comma-separated roles assigned to the specified user profile. Modifying a User Profile A user profile contains various parameters that you can modify. Tip: You can combine all commands to modify the parameters of a specific user profile at a time.
Page 480 Chapter 8: Using the Command Line Interface Modifying a User's Personal Data You can change a user's personal data, including the user's full name, telephone number, and email address. Various commands can be combined to modify the parameters of a Multi-Command Syntax specific user profile at a time.
Page 481 Chapter 8: Using the Command Line Interface Enabling or Disabling a User Profile This command enables or disables a user profile. A user can log in to the SRC only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: ...
Page 482 Chapter 8: Using the Command Line Interface Modifying SNMPv3 Settings There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 517).
Page 483 Chapter 8: Using the Command Line Interface config:# user modify <name> privacyPassPhrase After performing the above command, SRC prompts you to enter the privacy passphrase. Determine the authentication protocol: config:# user modify <name> authenticationProtocol <option5> Determine the privacy protocol: config:# user modify <name>...
Page 484 Chapter 8: Using the Command Line Interface Option Description false Authentication passphrase is different from the password.  true false <option4> is one of the options: Option Description true Privacy passphrase is identical to the authentication passphrase. false Privacy passphrase is different from the authentication passphrase.
Page 485 Chapter 8: Using the Command Line Interface Changing 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 Multi-Command Syntax units at a time.
Page 486 Chapter 8: Using the Command Line Interface  pascal <option3> is one of the options: Option Description pascal This option displays the pressure value in Pascals (Pa). This option displays the pressure value in 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.
Page 487 Chapter 8: Using the Command Line Interface Deleting a User Profile This command deletes an existing user profile. config:# user delete <name> Changing Your Own Password Every user can change their own password via this command if they have the Change Own Password privilege. Note that this command does not user begin with config:#...
Page 488 Chapter 8: Using the Command Line Interface Setting Default Measurement Units Default measurement units, including temperature, length, and pressure units, apply to the SRC user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator.
Page 489 Chapter 8: Using the Command Line Interface Option Description feet This option displays the length or height in feet.  pascal <option3> is one of the options: Option Description pascal This option displays the pressure value in Pascals (Pa). This option displays the pressure value in psi. Examples This section illustrates several user configuration examples.
Page 490: Role Configuration Commands
Chapter 8: Using the Command Line Interface Example 3 - Default Measurement Units The following command sets all default measurement units at a time. config:# user defaultpreferences preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi Results:  The default temperature unit is set to Fahrenheit. ...
Page 491 Chapter 8: Using the Command Line Interface config:# role create <name> <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a All Privileges semi-colon.
Page 492 Chapter 8: Using the Command Line Interface Privilege Description changeUserSettings Change Local User Management changeWebcamSettings Change Webcam Configuration clearLog Clear Local Event Log firmwareUpdate Firmware Update performReset Reset (Warm Start) switchActuator* Switch Actuator viewAuthSettings View Authentication Settings viewEventSetup View Event Settings viewEverything Unrestricted View Privileges viewLog...
Page 493 Chapter 8: Using the Command Line Interface Modifying a Role You can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify <name> description "<description>" Add more privileges to a specific role: config:# role modify <name>...
Page 494 Chapter 8: 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.
Page 495: Authentication Commands
Chapter 8: Using the Command Line Interface Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results:  A new role "tester" is created.  Two privileges are assigned to the role: firmwareUpdate (Firmware Update) and viewEventSetup (View Event Settings).
Page 496 Chapter 8: Using the Command Line Interface Option Description ldap Enable LDAP authentication. radius Enable Radius authentication.  true false <option2> is one of the options: Option Description true Remote authentication is the first priority. The device will switch to local authentication when the remote authentication is not available.
Page 497 Chapter 8: Using the Command Line Interface config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> "Optional Parameters" Note: "Optional Parameters" refer to one or multiple parameters listed in the section (on page 485). They are required Optional Parameters only when your server settings need to specify these parameters.
Page 498 Chapter 8: Using the Command Line Interface  anonymouseBind <bind_type> is one of the bind options: , or authenticatedBind Type Description anonymousBind Enable the anonymous Bind. Bind DN and password are NOT required. authenticatedBind Enable the Bind with authentication. Bind DN and password are required. ...
Page 499 Chapter 8: Using the Command Line Interface Parameters To configure adDomain <AD_domain> Active Directory Domain name verifyServerCertificate <verify_cert> Certificate verification setting  After setting to true, the system will prompt you to upload a certificate. For Illustrations of Adding LDAP details, see Servers (on page 486).
Page 500 Chapter 8: Using the Command Line Interface config:# authentication ldap add ac-ldap.raritan.com 389 activeDirectory none anonymousBind dc=raritan,dc=com sAMAccountName user adDomain raritan.com An LDAP server with a TLS certificate uploaded: a. Enter the CLI command with the following two TLS-related options set and/or added: ...
Page 501 Chapter 8: Using the Command Line Interface Copying an Existing Server's Settings If the server that you will add completely shares the same settings with any server that has been configured, use the following command. Add an LDAP server by copying an existing server's settings: config:# authentication ldap addClone <server_num>...
Page 502 Chapter 8: Using the Command Line Interface Parameters Description Change the IP address or host name. host <host>  <host> is the new IP address or host name. Change the TCP port number. port <port>  <port> is the new TCP port number. Change the server type.
Page 503 Chapter 8: Using the Command Line Interface Parameters Description Re-upload a different certificate. certificate a. First add the "certificate" parameter to the command, and press Enter. b. The system prompts you for the input of the certificate. c. Type or copy the content of the certificate in the CLI and press Enter.
Page 504 Chapter 8: Using the Command Line Interface config:# authentication ldap modify 1 host 192.168.3.3 port 633 serverType activeDirectory Removing an Existing LDAP Server This command removes an existing LDAP server from the server list. config:# authentication ldap delete <server_num> Variables: ...
Page 505 Chapter 8: Using the Command Line Interface  <auth_port> is the authentication port number.  <acct_port> is the accounting port number.  <timeout> is the timeout value in seconds. It ranges between 1 to 10 seconds.  <retries> is the number of retries. It ranges between 0 to 5. To enter the shared secret: 1.
Page 506 Chapter 8: Using the Command Line Interface config:# authentication radius modify <server_num> retries <retries> Change the shared secret: config:# authentication radius modify <server_num> secret Change the priority of the specified server: config:# authentication radius modify <server_num> sortPositon <position> Tip: You can add more than one parameters to the command. For example, "...
Page 507: Environmental Sensor Configuration Commands
Chapter 8: Using the Command Line Interface Removing an Existing Radius Server This command removes an existing Radius server from the server list. config:# authentication radius delete <server_num> Variables:  <server_num> is the sequential number of the specified server in the Radius server list.
Page 508 Chapter 8: Using the Command Line Interface Specifying the CC Sensor Type Raritan's contact closure sensor supports the connection of diverse third-party. You must specify the type of connected detector/switch for proper operation. Use this command when you need to specify the sensor type.
Page 509 Chapter 8: Using the Command Line Interface Setting the Y Coordinate This command 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.
Page 510 Chapter 8: Using the Command Line Interface Changing the Sensor Description This command 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.
Page 511 Chapter 8: Using the Command Line Interface Setting the Alarmed to Normal Delay for DX-PIR This command determines the value of the Alarmed to Normal Delay setting for a Raritan presence detector. config:# externalsensor <n> alarmedToNormalDelay <time> Variables:  <n> is the ID number of the environmental sensor that you want to configure.
Page 512: Configuring Environmental Sensors' Default Thresholds
Chapter 8: Using the Command Line Interface Configuring Environmental Sensors' Default Thresholds You can set the default values of upper and lower thresholds, deassertion hysteresis and assertion timeout on a sensor type basis, including temperature, humidity, air pressure and air flow sensors. The default thresholds automatically apply to all environmental sensors that are newly detected or added.
Page 513 Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> assertionTimeout <as_value> Variables:  <sensor type> is one of the following numeric sensor types: Sensor types Description absoluteHumidity Absolute humidity sensors relativeHumidity Relative humidity sensors temperature Temperature sensors airPressure Air pressure sensors airFlow Air flow sensors...
Page 514: Environmental Sensor Threshold Configuration Commands
Chapter 8: Using the Command Line Interface Example - Default Upper Thresholds for Temperature It is assumed that your preferred measurement unit for temperature is set to degrees Celsius. Then the following command sets the default Upper Warning threshold to 20 and Upper Critical threshold to 24 for all temperature sensors.
Page 515 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an environmental sensor: config:# sensor externalsensor <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an environmental sensor: config:# sensor externalsensor <n>...
Page 516 Chapter 8: Using the Command Line Interface Option Description disable Disables the specified threshold for a specific environmental sensor. A numeric Sets a value for the specified threshold of a value specific environmental sensor and enables this threshold at the same time. ...
Page 517: Actuator Configuration Commands
Chapter 8: Using the Command Line Interface Actuator Configuration Commands An actuator configuration command begins with actuator . You can configure the name and location parameters of an individual actuator. You can configure various parameters for one actuator at a time. See Multi-Command Syntax (on page 517).
Page 518: Server Reachability Configuration Commands
Chapter 8: Using the Command Line Interface Note: To specify the Z coordinate using the rack units, see Setting the Z Coordinate Format for Environmental Sensors (on page 406).  <description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes when it contains spaces.
Page 519 Chapter 8: Using the Command Line Interface  <succ_ping> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.  <fail_ping> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100.
Page 520 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> ipAddress <IP_host> Enable or disable the ping monitoring feature for the device: config:# serverReachability modify <n> pingMonitoringEnabled <option> Modify the number of successful pings for declaring "Reachable": config:# serverReachability modify <n> numberOfSuccessfulPingsToEnable <succ_number>...
Page 521 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> numberOfFailuresToDisable <disable_count> Variables:  <n> is a number representing the sequence of the IT device in the server monitoring list.  <IP_host> is the IP address or host name of the IT device whose settings you want to modify.
Page 522: Asset Management Commands
Chapter 8: Using the Command Line Interface Asset Management Commands You can use the CLI commands to change the settings of the connected asset strip (if any) or the settings of LEDs on the asset strip. Asset Strip Management An asset strip management configuration command begins with assetStrip.
Page 523 Chapter 8: Using the Command Line Interface Specifying the Rack Unit Numbering Mode This command syntax specifies the numbering mode of rack units on the asset strips connected to the SRC device. The numbering mode changes the rack unit numbers. config:# assetStrip <n>...
Page 524 Chapter 8: Using the Command Line Interface Specifying the Asset Strip Orientation This command syntax specifies the orientation of the asset strips connected to the SRC device. Usually you do not need to perform this command unless your asset strips do NOT come with the tilt sensor, causing the SRC unable to detect the asset strips' orientation.
Page 525 Chapter 8: Using the Command Line Interface Setting LED Colors for Disconnected Tags This command syntax sets the LED color for all rack units on the connected asset strip(s) to indicate the absence of a connected asset tag. config:# assetStrip <n> LEDColorForDisconnectedTags <color> Variables: ...
Page 526 Chapter 8: Using the Command Line Interface Setting the LED Operation Mode This command syntax determines whether a specific rack unit on the specified asset strip follows the global LED color settings. config:# rackUnit <n> <rack_unit> LEDOperationMode <mode> Variables:  <n>...
Page 527 Chapter 8: Using the Command Line Interface Setting an LED Color for a Rack Unit This command syntax sets the LED color for a specific rack unit on the specified asset strip. You need to set a rack unit's LED color only when the LED operation mode of this rack unit has been set to "manual."...
Page 528: Serial Port Configuration Commands
Chapter 8: Using the Command Line Interface Mode Description blinkSlow This mode has the LED blink slowly. blinkFast This mode has the LED blink quickly. Examples This section illustrates several asset management examples. Example 1 - Asset Strip LED Colors for Disconnected Tags This command syntax sets the LED color for all rack units on the asset sensor #1 to BLACK (that is, 000000) to indicate the absence of a connected asset tag.
Page 529 Chapter 8: Using the Command Line Interface Setting the Baud Rates The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the SRC device. Change the baud rate before connecting it to the desired device, such as a computer, a Raritan's P2CIM-SER, or a modem, through the serial port, or there are communications errors.
Page 530: Multi-Command Syntax
Chapter 8: Using the Command Line Interface Option Description forceConsole The SRC attempts to recognize that the connected device is set for the console mode. forceAnalogModem The SRC attempts to recognize that the connected device is an analog modem. forceGsmModem The SRC attempts to recognize that the connected device is a GSM modem.
Page 531: Actuator Control Operations
Chapter 8: Using the Command Line Interface Example 2 - Combination of SSID and PSK Parameters This multi-command syntax configures both 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. ...
Page 532: Switching Off An Actuator
Chapter 8: Using the Command Line Interface  Type n to abort the operation Switching Off an Actuator This command syntax turns off one actuator. control actuator <n> off To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.
Page 533: Resetting The Src
Chapter 8: Using the Command Line Interface 2. When the Username prompt appears, type unblock and press Enter. 3. When the "Username to unblock" prompt appears, type the name of the blocked user and press Enter. 4. A message appears, indicating that the specified user was unblocked successfully.
Page 534: Network Troubleshooting
Chapter 8: Using the Command Line Interface -- OR -- reset factorydefaults /y To reset SRC settings before login: Username: factorydefaults Using the CLI Command (on page 584) for details. Note: Device reset will cause CLI communications over an "USB" connection to be lost.
Page 535: Diagnostic Commands
Chapter 8: Using the Command Line Interface Diagnostic Commands The diagnostic command syntax varies from command to command. Querying DNS Servers This command syntax queries Internet domain name server (DNS) information of a network host. diag> nslookup <host> Variables:  <host>...
Page 536 Chapter 8: Using the Command Line Interface Testing the Network Connectivity This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding properly, the network connectivity is good. If not, either the host is shut down or it is not being properly connected to the network.
Page 537: Retrieving Previous Commands
Chapter 8: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your SRC and a network host. diag> traceroute <host> <useICMP> Variables:  <host> is the name or IP address of the host you want to trace. ...
Page 538: Logging Out Of Cli
Chapter 8: Using the Command Line Interface Examples:  Example 1 (only one possible command): a. Type the first word and the first letter of the second word of the "reset factorydefaults" command -- that is, reset f. b. Then press Tab or Ctrl+i to complete the second word. ...
Page 539: Chapter 9 Using Scp Commands
Chapter 9 Using SCP Commands You can perform a Secure Copy (SCP) command to update the SRC firmware, do bulk configuration, or back up and restore the configuration. In This Chapter Firmware Update via SCP ............... 526 Bulk Configuration via SCP ..............527 Backup and Restore via SCP..............
Page 540: Bulk Configuration Via Scp
Chapter 9: Using SCP Commands SCP example: scp pdu-px2-030410-44599.bin admin@192.168.87.50:/fwupdate Windows PSCP command: PSCP in Windows works in a similar way to the SCP.  pscp <firmware file> <user name>@<device ip>:/fwupdate Bulk Configuration via SCP Like performing bulk configuration via the web interface, there are two steps with the bulk configuration using the SCP commands: a.
Page 541: Backup And Restore Via Scp
Chapter 9: Using SCP Commands 2. Type the user password when prompted. 3. The system copies the configuration included in the file "bulk_config.txt" to another SRC, and displays the following message. Starting restore operation. The connection will be closed now. SCP examples: ...
Page 542 Chapter 9: Using SCP Commands  <user name> is the "admin" or any user profile with Administrator Privileges  <device ip> is the IP address or hostname of the SRC whose settings you want to back up. 2. Type the user password when prompted. 3.
Page 543: Downloading Diagnostic Data Via Scp
Chapter 9: Using SCP Commands Downloading Diagnostic Data via SCP You can download the diagnostic data via SCP. To download the diagnostic data via SCP: 1. Type one of the following SCP commands and press Enter. Scenario 1: Use the default SCP port and default filename ...
Page 544: Uploading Or Downloading Raw Configuration Data
Chapter 9: Using SCP Commands  <port> is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.  <filename> is the new filename of the downloaded file. 2. Type the password when prompted. 3.
Page 545 Chapter 9: Using SCP Commands Scenario 1: Use the default SCP port and default filename  SSH/SCP port is the default (22), and the accessed SRC is a standalone device.  The raw configuration file's default filename "raw_config.txt" is wanted. Then add a dot (.) in the end of the SCP command as shown below.
Page 546 Chapter 9: Using SCP Commands  If you do NOT specify a new filename in the command, such as Scenarios 1 or 2, the downloaded file's default name is "raw_config.txt."  If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file is renamed accordingly.
Page 547 Chapter 9: Using SCP Commands  <user name> is the "admin" or any user profile with Administrator Privileges.  <device ip> is the IP address or hostname of the SRC where you want to upload the specified file.  <port> is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.
Page 548: Keys That Cannot Be Uploaded
Chapter 9: Using SCP Commands Windows PSCP commands: PSCP in Windows works in a similar way to the SCP.  pscp -P <port> <user name>@<device ip>:/raw_config.txt <filename>  pscp -P <port> <CSV file> <config file> <user name>@<device ip>:/raw_config_update /match=<col> Alternative of bulk configuration via SCP: Both methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve the purpose of bulk configuration.
Page 549: Appendix A Specifications
Appendix A Specifications In This Chapter Maximum Ambient Operating Temperature........... 536 Serial RS-232 "RJ-45" Port Pinouts ............536 Sensor RJ-45 Port Pinouts..............536 Feature RJ-45 Port Pinouts ..............537 Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for SRC is 60 degrees Celsius.
Page 550: Feature Rj-45 Port Pinouts
Appendix A: Specifications RJ-45 Pin/signal definition +12V ― Power (fuse protected) +12V ― Power (fuse protected) ― Signal Ground RS485_DP bi-directional Data Positive of the RS-485 bus RS485_DN bi-directional Data Negative of the RS-485 bus ― Signal Ground 1-wire ― 1-wire signal for Raritan environmental sensor packages...
Page 551 Appendix A: Specifications RJ-45 Pin/signal definition Pin No. Signal Direction Description intended for use with Raritan devices. Do NOT connect. ― Signal Ground Input Reserved...
Page 552: Appendix B Configuration Or Firmware Upgrade With A Usb Drive
Appendix B Configuration or Firmware Upgrade with a USB Drive You can accomplish part or all of the following tasks simultaneously by plugging a USB flash drive which contains one or several special configuration files into the SRC.  Configuration changes ...
Page 553: System And Usb Requirements
Appendix B: Configuration or Firmware Upgrade with a USB Drive 4. Plug the USB drive into the USB-A port of the SRC. 5. The initial message shown on the front panel display depends on the first task performed by the SRC. ...
Page 554: Configuration Files
Appendix B: Configuration or Firmware Upgrade with a USB Drive USB drive requirements:  The drive contains either a single partition formatted as a Windows FAT32 filesystem, or NO partition tables (that is, a superfloppy-formatted drive).  fwupdate.cfg The drive contains a configuration file called in its root fwupdate.cfg directory.
Page 555 Appendix B: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg The configuration file, fwupdate.cfg , is an ASCII text file containing key-value pairs, one per line. Each value in the file must be separated by an equal sign (=), without any surrounding spaces.
Page 556 Appendix B: Configuration or Firmware Upgrade with a USB Drive logfile  Specify the name of a text file where the SRC will append the log messages when interpreting the USB drive contents.  If the specified file does not exist in the USB drive, it will be automatically created.
Page 557 Appendix B: Configuration or Firmware Upgrade with a USB Drive For example, mac:7 instructs the SRC to search for the MAC address in the 7th column of the "devices.csv" file.  The default value is serial:1, making the SRC search for its serial number in the first column.
Page 558 Appendix B: Configuration or Firmware Upgrade with a USB Drive  The SRC device beeps after it finishes writing the diagnostic data to the USB drive. tls_cert_file  Specify the filename of the wanted TLS server certificate. The filename can contain a single placeholder ${SERIAL} that is replaced with the serial number of the SRC.
Page 559 Appendix B: Configuration or Firmware Upgrade with a USB Drive config.txt To perform device configuration using a USB drive, you must:  Copy the device configuration file "config.txt" to the root directory of the USB drive.  Reference the "config.txt" file in the config option of the "fwupdate.cfg"...
Page 560 Appendix B: Configuration or Firmware Upgrade with a USB Drive Special configuration keys: There are 3 special configuration keys that are prefixed with magic:.  A special key that sets a user account's password without knowing the firmware's internal encryption/hashing algorithms is implemented.
Page 561 Appendix B: Configuration or Firmware Upgrade with a USB Drive To encrypt any settings: Data You can encrypt the value of any setting in the config.txt. See Encryption in 'config.txt' (on page 551). To restore a specific setting to factory default: Add "delete:"...
Page 562 Appendix B: Configuration or Firmware Upgrade with a USB Drive devices.csv If there are device-specific settings to configure, you must create a device list configuration file - devices.csv , to store unique data of each SRC device. This file must be: ...
Page 563: Creating Configuration Files Via Mass Deployment Utility
Appendix B: Configuration or Firmware Upgrade with a USB Drive Creating Configuration Files via Mass Deployment Utility The Mass Deployment Utility is an Excel file that lets you fill in basic information required for the three configuration files, such as the admin account and password.
Page 564: Data Encryption In 'Config.txt
Appendix B: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg 6. Verify that at least 3 configuration files are created - config.txt devices.csv . You are ready to configure or upgrade any Configuration or Firmware Upgrade with SRC with these files. See a USB Drive (on page 539).
Page 565: Firmware Upgrade Via Usb
Appendix B: Configuration or Firmware Upgrade with a USB Drive Illustration: In this example, we will encrypt the word "private", which is the value of the SNMP write community in the "config.txt" file. 1. In the CLI, type the following command to encrypt "private." 2.
Page 566 Appendix B: Configuration or Firmware Upgrade with a USB Drive 4. The SRC performs the firmware upgrade.  The front panel display shows the firmware upgrade progress. Tip: You can remove the USB drive and plug it into another SRC for firmware upgrade when the firmware upgrade message displays.
Page 567 Appendix C Bulk Configuration or Firmware Upgrade via DHCP/TFTP If a TFTP server is available, you can use it and appropriate configuration files to perform any or all of the following tasks for a large number of SRC devices in the same network. ...
Page 568: Appendix C Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp
Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure Any firmware downgrade using "fwupdate.cfg" is NOT supported by default. Only firmware upgrade is permitted with "fwupdate.cfg". A special parameter is required to permit firmware downgrade via fwupdate.cfg "fwupdate.cfg".
Page 569: Tftp Requirements
Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 6. Re-boot these SRC devices. The DHCP server will execute the commands in the "fwupdate.cfg" file on the TFTP server to configure or upgrade those SRC devices supporting DHCP in the same network.
Page 570 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Click Add to add a new vendor class. c. Specify a unique name for this vendor class and type the binary codes of "Raritan PDU 1.0" in the New Class dialog. The vendor class is named "Raritan PDU"...
Page 571 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Right-click the IPv4 node in DHCP to select Set Predefined Options. b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank.
Page 572 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
Page 573 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. d. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field.
Page 574 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. c. Click Add to add a new condition.
Page 575 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok. e. Click Next.
Page 576 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Select DHCP Standard Options in the "Vendor class" field, select "060 Vendor Class Identifier" from the Available Options list, and type "Raritan PDU 1.0" in the "String value" field.
Page 577 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv4 address in the "IP address" field.
Page 578 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.
Page 579: Dhcp Ipv6 Configuration In Windows
Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Important: The magic cookie is transmitted to and stored in SRC at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in SRC. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg"...
Page 580 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Right-click the IPv6 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class. c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)"...
Page 581 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 2. Add three options to the "Raritan PDU 1.0" vendor class. a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
Page 582 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. c. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
Page 583 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. e. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field.
Page 584 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.
Page 585 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.
Page 586: Dhcp Ipv4 Configuration In Linux
Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Important: The magic cookie is transmitted to and stored in SRC at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in SRC. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg"...
Page 587 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Configure the same option in DHCP accordingly. The SRC accepts the configuration or firmware upgrade only when this value in DHCP matches. 3. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). ...
Page 588: Dhcp Ipv6 Configuration In Linux
Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP IPv4 illustration example in dhcpd.conf: DHCP IPv6 Configuration in Linux Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server is running Linux. Required Linux IPv6 settings in DHCP: 1. Locate and open the "dhcpd6.conf" file of the DHCP server. 2.
Page 589 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP  code 3 (pdu-update-magic) = any string This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly. It does NOT matter whether the IPv6 magic cookie is identical to or different from the IPv4 magic cookie.
Page 590: Appendix D Raw Configuration Upload And Download
Appendix D Raw Configuration Upload and Download You can modify any existing "config.txt", and then upload it to a specific SRC for modifying part or all of its settings. There are two ways to get one "config.txt":  You create this file by yourself, either using or not using the Mass Deployment Utility.
Page 591: Download Via Curl
Appendix D: Raw Configuration Upload and Download http(s)://<user>:<password>@<device IP>/cgi-bin/raw_config_download.cgi Parameter Description <user> Any user name that has the Administrator Privileges. <password> The password of the specified user name. <device IP> Hostname or IP address of the SRC whose raw configuration you want to download. ...
Page 592: Uploading Raw Configuration
Appendix D: Raw Configuration Upload and Download Parameter Description <user> Any user name that has the Administrator Privileges. <password> The password of the specified user name. <device IP> Hostname or IP address of the SRC whose raw configuration you want to download. 2.
Page 593: Upload Via Curl
Appendix D: Raw Configuration Upload and Download Upload via Curl If curl is available on your computer, you can upload the raw configuration to SRC with the curl command. There are two scenarios with the curl upload methods.  When there are NO device-specific settings involved, you upload the configuration file only, regardless of the number of SRC devices to update.
Page 594 Appendix D: Raw Configuration Upload and Download Parameter Description Refer to the above table for explanation. <user>,  For device-specific settings in the <config <password>, file>, refer each device-specific <device IP>, configuration key to a specific column in the <config config.txt <dev_list file>.
Page 595: Curl Upload Return Codes
Appendix D: Raw Configuration Upload and Download Curl Upload Return Codes After performing raw configuration Upload via Curl (on page 580), curl will return a code to indicate the result of the file upload. Code Description Operation was successful. An internal error occurred. A parameter error occurred.
Page 596: Appendix E Resetting To Factory Defaults
Appendix E Resetting to Factory Defaults You can use either the reset button or the command line interface (CLI) to reset the SRC. Important: Exercise caution before resetting the SRC to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.
Page 597: Using The Cli Command
Appendix E: Resetting to Factory Defaults Note: PuTTY is a free program you can download from the Internet. See PuTTY's documentation for details on configuration. Using the CLI Command The Command Line Interface (CLI) provides a reset command for restoring the SRC to factory defaults. For information on CLI, see Using the Command Line Interface (on page 374).
Page 598: Appendix F Ldap Configuration Illustration
Appendix F 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 roles (groups) intended for the SRC b.
Page 599: Step B. Configure User Groups On The Ad Server
Appendix F: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups (roles) for the SRC on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: ...
Page 600 Appendix F: LDAP Configuration Illustration srcuser userb 3. Add the accounts to the SRC_Admin group. 4. Verify whether each group comprises correct users.
Page 601: Step C. Configure Ldap Authentication On The Src
Appendix F: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the SRC You must enable and set up LDAP authentication properly on the SRC to use external authentication. In the illustration, we assume:  Wired The DNS server settings have been configured properly. See Network Settings Role of a DNS Server (on page 170) and...
Page 602 Appendix F: LDAP Configuration Illustration Field/setting Do this... Bind DN, Skip the three fields because of anonymous bind. Bind password, Confirm bind password Base DN for search Type dc=techadssl,dc=com as the starting point where your search begins on the AD server. Login Name Attribute Ensure the field is set to sAMAccountName because the LDAP server is Microsoft Active Directory.
Page 603 Appendix F: LDAP Configuration Illustration 4. Click Add Server.The LDAP server is saved. 5. In the Authentication Type field, select LDAP. 6. Click Save. The LDAP authentication is activated.
Page 604: Step D. Configure Roles On The Src
Appendix F: LDAP Configuration Illustration Note: If the SRC clock and the LDAP server clock are out of sync, the installed TLS certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the SRC and the LDAP server to use the same NTP server(s).
Page 605 Appendix F: LDAP Configuration Illustration c. In the Privileges list, select Unrestricted View Privileges, which includes all View permissions. The Unrestricted View Privileges permission lets users view all settings without the capability to configure or change them. d. Click Save. 3.
Page 606 Appendix F: LDAP Configuration Illustration c. In the Privileges list, select Administrator Privileges. The Administrator Privileges allows users to configure or change all SRC settings. d. Click Save. The SRC_Admin role is created.
Page 607: Appendix G Updating The Ldap Schema
Appendix G Updating the LDAP Schema In This Chapter Returning User Group Information ............594 Setting the Registry to Permit Write Operations to the Schema ... 595 Creating a New Attribute................. 595 Adding Attributes to the Class ..............596 Updating the Schema Cache ..............598 Editing rciusergroup Attributes for User Members .......
Page 608: Setting The Registry To Permit Write Operations To The Schema
Appendix G: Updating the LDAP Schema Setting the Registry to Permit Write Operations to the Schema To allow a domain controller to write to the schema, you must set a registry entry that permits schema updates. To permit write operations to the schema: 1.
Page 609: Adding Attributes To The Class
Appendix G: Updating the LDAP Schema 3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. 4. Type rciusergroup in the Common Name field. rciusergroup 5. Type in the LDAP Display Name field. 6.
Page 610 Appendix G: Updating the LDAP Schema 2. Scroll to the user class in the right pane and right-click it. 3. Choose Properties from the menu. The user Properties dialog appears. 4. Click the Attributes tab to open it. 5. Click Add.
Page 611: Updating The Schema Cache
Appendix G: Updating the LDAP Schema 6. Choose rciusergroup from the Select Schema Object list. 7. Click OK in the Select Schema Object dialog. 8. Click OK in the User Properties dialog. Updating the Schema Cache To update the schema cache: 1.
Page 612 Appendix G: Updating the LDAP Schema 3. Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window opens. 4. Open the Domain. 5. In the left pane of the window, select the CN=Users folder.
Page 613 Appendix G: Updating the LDAP Schema 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties. 7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.
Page 614: Appendix H Radius Configuration Illustration
Appendix H RADIUS Configuration Illustration This section provides illustrations for configuring RADIUS authentication. One illustration is based on the Microsoft Network Policy Server (NPS), ® and the other is based on a FreeRADIUS server. The following steps are required for any RADIUS authentication: Adding Radius 1.
Page 615 Appendix H: RADIUS Configuration Illustration b. On the NPS, configure Connection Request Policies and the standard Step B: Configure Connection Policies and Standard attribute. See Attributes (on page 606). Some configuration associated with Microsoft Active Directory (AD) is AD-Related Configuration also required for RADIUS authentication.
Page 616 Appendix H: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your SRC. In this example, they are 1812 and 1813. Then close this dialog.
Page 617 Appendix H: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your SRC to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 618 Appendix H: RADIUS Configuration Illustration Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your SRC. 5. Click OK.
Page 619 Appendix H: RADIUS Configuration Illustration Step B: Configure Connection Policies and Standard Attributes You need to configure the following for connection request policies:  IP address or host name of the SRC  Connection request forwarding method  Authentication method(s) ...
Page 620 Appendix H: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 621 Appendix H: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
Page 622 Appendix H: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 623 Appendix H: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the SRC IP address -- 192.168.56.29 , and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Page 624 Appendix H: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the SRC uses "CHAP" in this example...
Page 625 Appendix H: RADIUS Configuration Illustration Note: If your SRC uses PAP, then select "PAP."...
Page 626 Appendix H: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
Page 627 Appendix H: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
Page 628 Appendix H: RADIUS Configuration Illustration 12. In the Attribute Information dialog, click Add. Raritan:G{Admin} 13. Select String, type in the text box, and then click...
Page 629 Appendix H: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the SRC. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
Page 630 Appendix H: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
Page 631 Appendix H: RADIUS Configuration Illustration 15. Click Next to continue.
Page 632: Freeradius Standard Attribute Illustration
Appendix H: RADIUS Configuration Illustration 16. A summary showing connection request policy settings is displayed. Click Finish to close the dialog. FreeRADIUS Standard Attribute Illustration With standard attributes, NO dictionary files are required. You simply add all user data, including user names, passwords, and roles, in the following FreeRADIUS path.
Page 633: Vendor-Specific Attributes
Appendix H: RADIUS Configuration Illustration steve Cleartext-Password := "test123" Filter-ID = "Raritan:G{Admin}", Filter-ID = "Raritan:G{SystemTester}" Vendor-Specific Attributes You must specify the following properties when using a RADIUS vendor-specific attribute (VSA).  Vendor code = 13742  Vendor-assigned attribute number = 26 ...
Page 634 Appendix H: RADIUS Configuration Illustration Step A: Add Your SRC as a RADIUS Client The RADIUS implementation on the SRC follows the standard RADIUS Internet Engineering Task Force (IETF) specification so you must select "RADIUS Standard" as its vendor name when configuring the NPS server.
Page 635 Appendix H: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your SRC. In this example, they are 1812 and 1813. Then close this dialog.
Page 636 Appendix H: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your SRC to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 637 Appendix H: RADIUS Configuration Illustration Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your SRC. 5. Click OK.
Page 638 Appendix H: RADIUS Configuration Illustration Step B: Configure Connection Policies and Vendor-Specific Attributes You need to configure the following for connection request policies:  IP address or host name of the SRC  Connection request forwarding method  Authentication method(s) ...
Page 639 Appendix H: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 640 Appendix H: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
Page 641 Appendix H: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 642 Appendix H: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the SRC IP address -- 192.168.56.29 , and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Page 643 Appendix H: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the SRC uses "CHAP" in this example...
Page 644 Appendix H: RADIUS Configuration Illustration Note: If your SRC uses PAP, then select "PAP." 10. Select Vendor Specific to the left of the dialog, and click Add. The Add Vendor Specific Attribute dialog appears. 11. Select Custom in the Vendor field, and click Add. The Attribute Information dialog appears.
Page 645: Freeradius Vsa Illustration
Appendix H: RADIUS Configuration Illustration Note that multiple roles are separated with a space. 16. Click OK. FreeRADIUS VSA Illustration A vendor-specific dictionary file is required for the vendor-specific-attribute configuration on FreeRADIUS. Therefore, there are two major configuration steps. a. Use a dictionary to define the Raritan vendor-specific attribute b.
Page 646: Ad-Related Configuration
Appendix H: RADIUS Configuration Illustration VENDOR Raritan 13742 BEGIN-VENDOR Raritan ATTRIBUTE Raritan-User-Roles 26 string END-VENDOR Raritan Step B -- create a user profile for "steve" in FreeRADIUS: 1. Go to this location: /etc/raddb/users. 2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=) must be enclosed in double quotes (").
Page 647 Appendix H: RADIUS Configuration Illustration 2. Right-click NPS (Local) and select "Register server in Active Directory." 3. Click OK, and then OK again. To grant SRC users remote access permission: 1. Open Active Directory Users and Computers.
Page 648 Appendix H: RADIUS Configuration Illustration 2. Open the properties dialog of the user whom you want to grant the access permission. 3. Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: 1. Open Active Directory Users and Computers. 2.
Page 649 Appendix H: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
Page 650 Appendix I Additional SRC Information In This Chapter RJ45-to-DB9 Cable Requirements for Modem Connections ....637 Reserving IP Addresses in DHCP Servers ..........638 Sensor Threshold Settings..............642 Altitude Correction Factors..............650 Ways to Probe Existing User Profiles ............. 651 Raritan Training Website.................
Page 651: Appendix I Additional Src Information
Appendix I: Additional SRC Information Note: The RJ45-to-DB9 adapter/cable used for connecting modems CANNOT be used to connect the SRC to a computer. See RJ45-to-DB9 Cable Requirements for Computer Connections (on page 22). Reserving IP Addresses in DHCP Servers SRC uses its serial number as the client identifier in the DHCP request. Therefore, to successfully reserve an IP address for the SRC in a DHCP server, use the SRC device's serial number as the unique ID instead of the MAC address.
Page 652: Reserving Ip In Windows
Appendix I: Additional SRC Information Reserving IP in Windows To reserve the IP address of any network interface in the Windows DHCP server, you must convert that interface's client identifier into hexadecimal ASCII codes. Reserving IP Addresses in For each interface's client identifier, see DHCP Servers (on page 638).
Page 653: Reserving Ip In Linux
Appendix I: Additional SRC Information Reserving IP in Linux There are two methods to reserve the IP address of any network interface in the standard Linux DHCP server (ISC DHCP server):  hexadecimal Convert an interface's client identifier into ASCII codes. ...
Page 654 Appendix I: Additional SRC Information Interface Client identifier conversion WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53  The suffix comprising the dash symbol and the word "WIRELESS"...
Page 655: Sensor Threshold Settings
Appendix I: Additional SRC Information Sensor Threshold Settings This section explains the thresholds settings for a numeric sensor. Thresholds and Sensor States A numeric sensor has four thresholds: Lower Critical, Lower Warning, Upper Warning and Upper Critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state.
Page 656 Appendix I: Additional SRC Information above upper critical Upper Critical above upper warning Upper Warning normal Lower Warning below lower warning Lower Critical below lower critical Available sensor states:...
Page 657 Appendix I: Additional SRC Information The more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal' state is always available regardless of whether any threshold is enabled. For example:  When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal and above upper critical.
Page 658: To Assert" And Assertion Timeout
Appendix I: Additional SRC Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the SRC asserts a state for it whenever a bad state change occurs. To assert a state: To assert a state is to announce a new, "worse" state. Below are bad state changes that cause the SRC to assert.
Page 659 Appendix I: Additional SRC Information In the threshold settings, the Assertion Timeout field postpones the "assertion" action. It determines how long a sensor must remain in the "worse" new state before the SRC triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the SRC does NOT assert the worse state.
Page 660: To De-Assert" And Deassertion Hysteresis
Appendix I: Additional SRC Information "To De-assert" and Deassertion Hysteresis After the SRC asserts a worse state for a sensor, it may de-assert that state later on if the readings improve. To de-assert a state: To de-assert a state is to announce the end of the previously-asserted worse state.
Page 661 Appendix I: Additional SRC Information...
Page 662 Appendix I: Additional SRC Information In the threshold settings, the Deassertion Hysteresis field determines a new level to trigger the "deassertion" action. This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds a pre-determined level.
Page 663: Altitude Correction Factors
Appendix I: Additional SRC Information Assumption: Upper Warning threshold is enabled. Upper Warning = 20 (degrees Celsius) Deassertion Hysteresis = 3 (degrees Celsius) "Deassertion" level = 20-3 = 17 (degrees Celsius) When the SRC detects that a temperature sensor's reading drops below 20 degrees Celsius, moving from the "above upper warning"...
Page 664: Ways To Probe Existing User Profiles
Appendix I: Additional SRC Information Ways to Probe Existing User Profiles This section indicates available ways to query existing user accounts on the SRC.  With SNMP v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist. ...
Page 665: Cascading Troubleshooting
Appendix I: Additional SRC Information Cascading Troubleshooting Any accessibility problem occurred on one of the devices in the cascading chain may result in failure to access all downstream slave devices that are connected to it. Possible Root Causes The following lists the network accessibility issues and possible root causes.
Page 666 Appendix I: Additional SRC Information Symptom Probable cause  One of the following issues occurs on the master device: Failure to access a slave device  Network connection is lost.  Power is lost.  The Ethernet or wireless interface is disabled. ...
Page 667: Slave Device Events In The Log
Appendix I: Additional SRC Information Tip: To determine which SRC may be the failure point of network, you may ping each SRC in the cascading chain, or check the slave-related events in the event log of each SRC. See The Ping Tool (on page 655) and Slave Device Events in the Log (on page 654).
Page 668 Appendix I: Additional SRC Information Messages for the USB-cascading chain: In the Bridging mode, events regarding connection/disconnection of a downstream slave device via USB is NOT logged. However, in the Port Forwarding mode, whenever the connection or disconnection of a downstream slave device via USB is detected, the SRC at the USB-A end of the USB cable logs it in the internal log.
Page 669: Installing The Usb-To-Serial Driver (Optional)
Appendix I: Additional SRC Information Installing the USB-to-Serial Driver (Optional) The SRC can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Dominion PX2Serial Console" is required for Microsoft Windows operating systems. ® ® Download the Windows driver for USB serial console from the Raritan website's Support page http://www.raritan.com/support/...
Page 670: Initial Network Configuration Via Cli
Appendix I: Additional SRC Information Note: If the SRC enters the disaster recovery mode when the USB serial driver is not installed yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it. In Linux: No additional drivers are required, but you must provide the name of the tty device, which can be found in the output of the "dmesg"...
Page 671 Appendix I: Additional SRC Information b. Default password: raritan (or a new password if you have changed it). 4. If prompted to change the default password, change or ignore it.  To change it, follow onscreen instructions to type your new password.
Page 672 Appendix I: Additional SRC Information To set or Use this command enable network dns resolverPreference IP address <resolver> returned by the DNS <resolver> = preferV4 preferV6 server  Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address>...
Page 673 Appendix I: Additional SRC Information To set or Use this command enable network ethernet <ETH> EAP outer eapOuterAuthentication authentication <outer_auth> PEAP <outer_auth> = network ethernet <ETH> EAP inner eapInnerAuthentication authentication <inner_auth> MSCHAPv2 <inner_auth> = network ethernet <ETH> EAP identity eapIdentity <identity> <identity>...
Page 674 Appendix I: Additional SRC Information To set or Use this command enable network ethernet <ETH> EAP CA eapCACertificate certificate When prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program. network ethernet <ETH>...
Page 675 Appendix I: Additional SRC Information Commands for wireless networking:  General wireless settings: To set or Use this command enable network wireless enabled Wireless <option> interface true false <option> = , or network wireless SSID <ssid> SSID <ssid> = SSID string network wireless BSSID <bssid>...
Page 676 Appendix I: Additional SRC Information To set or Use this command enable network wireless Wireless EAP eapClientCertificate TLS client certificate When prompted to enter the client certificate, open the certificate with a text editor, copy and paste the content into the communications program. network wireless Wireless EAP eapClientPrivateKey...
Page 677 Appendix I: Additional SRC Information The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing "END CERTIFICATE." If a certificate is installed, configure the following: Whether to Use this command network wireless Verify the enableCertVerification...
Page 678: Device-Specific Settings
Appendix I: Additional SRC Information To verify network settings: After exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings.  show network The IP address configured may take seconds to take effect. Device-Specific Settings A bulk configuration file will NOT contain any device-specific information like the following list.
Page 679: What Is A Certificate Chain
Appendix I: Additional SRC Information What is a Certificate Chain If you are familiar with a certificate chain, you can ignore this topic Illustration - GMAIL SMTP Certificate Chain and refer to (on page 669). A certificate or a chain of certificates is used for trusting a TLS server that you want to connect.
Page 680 Appendix I: Additional SRC Information Each certificate in the chain is the issuer certificate of the certificate that follows it. That is, A is the issuer certificate of B, and B is the issuer certificate of C. Note: In fact many certificate chains may comprise only the root certificate and a TLS server's certificate and do not have any intermediate certificate(s) like 'Certificate B' involved.
Page 681 Appendix I: Additional SRC Information Warning: The certificate (chain) uploaded to the receiver must always contain the ROOT certificate even though the TLS server provides the root certificate. When uploading a (partial) chain onto the SRC, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to SRC.
Page 682: Illustration - Gmail Smtp Certificate Chain
Appendix I: Additional SRC Information It is NOT recommended to upload the server certificate to the receiver except when it is a self-signed certificate. Using self-signed server certificates is also not recommended and may not even work in all cases. Order of the chain in the certificate file: The order of a certificate chain's content in the certificate file uploaded to the receiver must look like the following.
Page 683 Appendix I: Additional SRC Information openssl s_client -showcerts -connect smtp.gmail.com:465 Alternative: To view the certificate chain instead of all certificates, you can remove the "-showcerts" option from the above command. 2. Information that shows the certificates the SMTP server has is displayed.
Page 684 Appendix I: Additional SRC Information 3. Onscreen information under the title 'Certificate chain' indicates that there are three issuers and three certificates on this server.  Each line beginning with the letter "i" indicates an issuer. They are:  Google Internet Authority G2 ...
Page 685: Browsing Through The Online Help
Appendix I: Additional SRC Information  Content copying must include the lines of "BEGIN CERTIFICATE" and "END CERTIFICATE". .pem .crt .cer 2. Save that file as a file. In this example, it is named as "my-root.pem." 3. Upload the file "my-root.pem" to SRC for using the GMAIL SMTP service.
Page 686 Appendix I: Additional SRC Information  To collapse any expanded topic, click the black, gradient arrow prior to the topic, or double-click the expanded topic. The arrow then turns into a white arrow , and all sub-topics below that topic disappear. 6.
Page 687: Asset Management Strips And Raritan Pdus
Appendix J Integrating Asset Management Strips with Other Products In This Chapter Asset Management Strips and Raritan PDUs......... 674 Asset Management Strips and dcTrack ..........675 Asset Management Strips and Raritan PDUs Asset strips also work with the following Raritan power distribution units (PDUs) or transfer switches: ...
Page 688: Asset Management Strips And Dctrack
Appendix J: Integrating Asset Management Strips with Other Products Asset Management Strips and dcTrack If any asset strips are connected to the SRC, the SRC can transmit their information to Sunbird's dcTrack. All you have to do is to add the SRC to dcTrack, and also add each IT item where an asset tag is attached to dcTrack.
Page 689 Index Asset Management Strips and dcTrack • 676 + Asset Management Strips and Raritan PDUs • +12V Power Supply Sensor • 81, 113, 114 Asset Management Tag List • 297, 298 0 Asset Management Tag Log • 297, 301 Asset Strip • 58, 86, 138, 139 0U Rackmount Method •...
Page 690: Index
Index Cascading Multiple SRC Devices for Sharing Configuring Environmental Sensors' Default Ethernet Connectivity • 11, 14, 24, 172, 187, Thresholds • 500 Configuring IPv4 Parameters • 407 Cascading Troubleshooting • 25, 195, 653 Configuring IPv6 Parameters • 412 Changing a User's Password • 467 Configuring Login Settings •...
Page 691 Index Connecting Door Handles or a SmartLock Kit • Date and Time Settings • 386 43, 357 Deassertion Hysteresis Example for Connecting External Equipment (Optional) • 36, Temperature Sensors • 650 Default Log Messages • 231, 238, 244, 258, Connecting Raritan Environmental Sensor Packages •...
Page 692 Index DX2 Sensor Packages • 38, 46, 272 Environmental Sensor Configuration DX2-DH2C2 • 40 Commands • 495 Environmental Sensor Default Thresholds • E Environmental Sensor Information • 387 EAP CA Certificate Example • 421, 423, 428 Environmental Sensor Package Information • Editing or Deleting a Rule/Action •...
Page 693 Index Example 2 - Enabling IPv6 Protocol on the How Long a Link Remains Accessible • 348, Ethernet Interface • 440 Example 2 - In-Depth Security Information • How the Automatic Management Function Works • 119, 129 Example 2 - Modifying a User's Roles • 477 I ...
Page 694 Index LDAP Settings • 484 Modifying or Deleting a Script • 310, 315 Limitations • 44 Modifying or Removing Bulk Profiles • 335 Log an Event Message • 254, 258 Modifying Role-Based Access Control Logging in to CLI • 376, 552, 585 Parameters •...
Page 695 Index Port Forwarding Examples • 97, 189, 192, 193 Resetting to Factory Defaults • 94, 342, 521, Port Number Syntax • 188, 190, 191, 193, 654 Possible Root Causes • 653 Restarting the Device • 521 Product Models • 3, 11, 74 Restricted Service Agreement •...
Page 696 Index Sensor/Actuator States • 80, 83, 111, 117, 118, Setting the IPv4 Configuration Mode • 408 124, 125 Setting the IPv4 Gateway • 410 Serial Port Configuration Commands • 516 Setting the IPv4 Preferred Host Name • 409 Serial Port Settings • 395 Setting the IPv6 Address •...
Page 697 Index Sorting a List • 107, 110, 117, 142, 160, 163, Switching On an Actuator • 519 182, 283, 325, 330 Syslog Message • 255, 273 Special Character Requirement • 458 System and USB Requirements • 540, 541 Specifications • 537 T ...
Page 698 Index Using the CLI Command • 522, 585 Using the Command Line Interface • 114, 197, 375, 585 Using the Reset Button • 584 Using the Web Interface • 95 V Vendor-Specific Attributes • 602, 621 Viewing and Managing Locally-Saved Snapshots •...

This manual is also suitable for:

Raritan src-0102