Page 2: Welcome
Raritan, Inc. © Copyright 2018 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 BCM2 Series Power Meter - Xerus ™ Firmware v3.4.0 User Guide...
Page 4: Safety Information
Safety Information DANGER! HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH  Follow safe electrical work practices. See NFPA 70E in the USA, or applicable local codes.  This equipment must only be installed and serviced by qualified electrical personnel. ...
Page 5 RISK OF EQUIPMENT DAMAGE  This product is designed only for use with 0.33V output current transducers (CTs).  DO NOT USE CURRENT OUTPUT (e.g. 5A) CTs ON THIS PRODUCT.  Failure to follow these instructions can result in overheating and permanent equipment damage. For use in a Pollution Degree 2 or better environment only.
Page 6: Table Of Contents
Chapter 1 Installation and Initial Configuration Product Models..........................1 Hardware Installation ........................2 BCM2 Series Hardware Installation ..................2 PM Series Hardware Installation: PMC-1000, PMC-1001, PMM-1000, PMB-1960, PMMC-1000 .......................... 13 Login and Configuration ......................... 28 Configuring Power Meters and Branch Circuit Monitors ............ 29 Using the BCM2's Display ......................
Page 7 Contents Connecting a Logitech Webcam ..................... 76 Connecting a GSM Modem ......................76 Connecting an Analog Modem ....................... 77 Connecting an External Beeper ..................... 78 Connecting a Schroff LHX/SHX Heat Exchanger ................78 Wireless Network Connection ......................79 USB Wireless LAN Adapters ....................79 Supported Wireless LAN Configuration ................
Page 8 Contents User Management ........................152 Creating Users ........................153 Editing or Deleting Users ....................157 Creating Roles ........................159 Editing or Deleting Roles ....................160 Setting Your Preferred Measurement Units ..............162 Setting Default Measurement Units .................. 163 Setting Up Roles ........................... 164 Permissions ........................
Page 9 Contents Chapter 4 Using SNMP Enabling and Configuring SNMP ....................345 SNMPv2c Notifications ....................... 346 SNMPv3 Notifications ......................347 Downloading SNMP MIB ......................350 SNMP Gets and Sets ........................351 The BCM2 MIB ........................351 Retrieving Energy Usage ....................354 A Note about Enabling Thresholds ..................
Page 10 Contents Reliability Data ........................381 Reliability Error Log ......................381 Examples ..........................381 Clearing Information ........................383 Clearing Event Log ......................384 Clearing WLAN Log ......................384 Configuring the BCM2 Device and Network................. 384 Entering Configuration Mode ..................... 385 Quitting Configuration Mode ....................385 Network Configuration Commands ...................
Page 11 Contents Retrieving Previous Commands ....................512 Automatically Completing a Command ..................512 Logging out of CLI......................... 513 Chapter 6 Using SCP Commands Firmware Update via SCP ......................514 Bulk Configuration via SCP ......................515 Backup and Restore via SCP ......................516 Downloading Diagnostic Data via SCP ..................
Page 12 "To De-assert" and Deassertion Hysteresis ..............581 Altitude Correction Factors ......................584 Ways to Probe Existing User Profiles ..................585 Raritan Training Website ......................585 Role of a DNS Server ........................585 Installing the USB-to-Serial Driver (Optional) ................586 Initial Network Configuration via CLI ................... 587 Device-Specific Settings .......................
Page 13: Chapter 1 Installation And Initial Configuration
Chapter 1 Installation and Initial Configuration  This equipment must only be installed and serviced by qualified electrical personnel.  Read, understand and follow the instructions before installing this product. Safety Information  See (on page iv). In This Chapter Product Models ...................
Page 14: Hardware Installation
BCM2 9600 series BCM2 Series Hardware Installation (see " " on • page 2) PM Series: PMC-1000, PMC-1001, PMM-1000, PMB-1960, • PMMC-1000 PM Series Hardware Installation: PMC-1000, (see " PMC-1001, PMM-1000, PMB-1960, PMMC-1000 " on page 13) BCM2 Series Hardware Installation...
Page 15 Raritan authorized service personnel. Failure to comply with this warning may result in electric shock, personal injury and death. Raritan 400 Cottontail Lane, Somerset, NJ 08873 USA Product Overview Raritan's BCM2 hardware is a branch circuit monitor that supports the Xerus technology platform.
Page 16 Chapter 1: Installation and Initial Configuration  96 channel branch circuit BCM2_96xx (with built-in External meter controller monitor. controller)  Models available with or without built-in meter controller, with power line cords or field wiring terminals.  One meter controller (built-in or external) interconnects one to eight BCM2.
Page 17 Chapter 1: Installation and Initial Configuration *Ratings for models with field wiring terminals. For models with factory installed line-cords, rating is limited by plug and ratings are labeled on back on unit. Current Measurement Inputs: Input Range 0-400mV Input Impedance CT Type Voltage Output = 333mV at rated current...
Page 18 Chapter 1: Installation and Initial Configuration Operating Elevation 0-3000m Conformance: Safety UL/EN 61010-1 EMC/EMI EN61326-1, FCC Part 15 Class A BCM2 Rear Panel Connectors and Controls Voltage measurement input. Model dependent: line cord or conduit knockout Meter power input. Not present on line cord models.
Page 19 Chapter 1: Installation and Initial Configuration Meter Controller Connectors and Controls RS-232 for serial CLI or phone-line modem access. RJ45 port provided on iX7 models. LCD displays meter readings and configuration. Keypad: up, down, select, cancel. 10/100 base-t Ethernet. Sensor port (temperature, humidity, contact closure) USB A &...
Page 20 Chapter 1: Installation and Initial Configuration Voltage Measurement and Power Wiring BCM2-96xx series products are available with factory installed line cords (PLUGGABLE EQUIPMENT) or conduit knockouts and field wiring terminals (PERMANENTLY CONNECTED EQUIPMENT). This section describes how to wire models with conduit knockouts and field wiring terminals.
Page 21 Chapter 1: Installation and Initial Configuration Panel Voltage Voltage Inputs Power CT ABCNE 1-phase 120V, 230V 1-phase 208V Split-phase 120/240 3-phase 4-wire 3-phase 5-wire...
Page 22 Chapter 1: Installation and Initial Configuration Current Transformer (CT) Wiring Multi-conductor CT cable. Available lengths: 3m, 10m. Connect labeled end into matching labeled rear panel connector CT plugs into 2-pin locking connector (Molex 43640-0201) Main Circuit: 3 phase lines (A,B,C), Neutral (N), Earth (E).
Page 23 Chapter 1: Installation and Initial Configuration Panel Wiring Example...
Page 24 Chapter 1: Installation and Initial Configuration Controller Wiring to Meters Daisy chain:  Meter with built-in controller + 1 to 7 controller-less meters  external controller + 1 to 8 controller-less meters. All cables shielded Cat-5, each cable: 100m max. length. Switch MBT (terminator) ON for devices at ends of daisy chain.
Page 25: Pm Series Hardware Installation: Pmc-1000, Pmc-1001, Pmm-1000, Pmb-1960, Pmmc-1000
Chapter 1: Installation and Initial Configuration PM Series Hardware Installation: PMC-1000, PMC-1001, PMM-1000, PMB-1960, PMMC-1000 Safety Information DANGER! HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH  Follow safe electrical work practices. See NFPA 70E in the USA, or applicable local codes.
Page 26 This product contains no user serviceable parts. Do not open, alter or disassemble this product. All repairs and servicing must be performed by Raritan authorized service personnel. Failure to comply with this warning may result in electric shock, personal injury and death.
Page 27 Chapter 1: Installation and Initial Configuration Product Overview - PM Series Power Meters Raritan PM series power meters is a modular power metering solution that is a flexible alternative to the all-in-one BCM2 hardware. All solutions support Xerus technology platform.
Page 28 Chapter 1: Installation and Initial Configuration Product Specification Voltage Measurement Inputs: Input Range* 90-277VLN, 156-480VLL Phase to Ground* 277V Measurement Category CAT III, Pollution Level 2 Frequency 47-63 Hz Input Impedance 10MΩ *Ratings for models with field wiring terminals. For models with factory installed line-cords, rating is limited by plug and ratings are labeled on back on unit.
Page 29 Chapter 1: Installation and Initial Configuration Power Requirements: Voltage 90-240V Current 0.1A Overvoltage Category CAT III, Pollution Level 2 Frequency 47-63 Hz Mechanical: Terminal Block Screw Torque 0.37 ft-lb (0.5Nm) to 0.44 ft-lb (0.6Nm) Terminal Block Wire Size 14-24AWG (.5-1.6mm) Terminal Wire Temperature Rating >...
Page 30 Chapter 1: Installation and Initial Configuration Power Meter (PMM) Connectors and Controls Voltage Measurement. Power Factory Use (Do not connect.) Meter Bus Terminator Switch Meter Bus Connectors. Connects PMM to Controller. Factory Use (Do not connect.) Multi-conductor Cable CT ABCNE Connector Meter ID Configuration Switch BOTTOM...
Page 31 Chapter 1: Installation and Initial Configuration Power Meter Branch Monitor (PMB) Connectors Multi-conductor cable CT 1 connector. Multi-conductor cable CT 2 connector. Multi-conductor cable CT 3 connector. Multi-conductor cable CT 4 connector. Multi-conductor cable CT 5 connector. Multi-conductor cable CT 6 connector.
Page 32 Chapter 1: Installation and Initial Configuration Power Meter with Controller (PMMC) Meter Bus Connectors Meter Bus Terminator Switch Meter ID Configuration Switch Power Ethernet USB-A and USB-B Sensor Port Multi-conductor Cable CT ABCNE Connector Modbus Voltage Measurement Expansion Port is on bottom side of unit.
Page 33 Power Meter Controller (PMC) iX6/iX7 MODBUS RTU isolated RS-485 Meter bus connector (to PMM) Meter bus terminator switch 10/100 base-t Ethernet. Feature port (Raritan asset strip) Sensor port (temperature, humidity, etc.) USB A & B (flash drives, WIFI, serial port) RS-232 (terminal CLI,...
Page 34 Chapter 1: Installation and Initial Configuration DIN Rail Mounting PMM + PMB BOTTOM Expansion Connector supplied with PMB. Do not hot-plug the Expansion Port! PMM and PMB must be disconnected from all power source before plugging Expansion Port. Snap Expansion Connector to Expansion Ports on bottoms of PMM and PMB or PMMC and PMB.
Page 35 Chapter 1: Installation and Initial Configuration Voltage and Current Measurement Wiring Protect phase lines with fused disconnects rated for available short circuit current at connection point. All wiring: 14-22 AWG, 75°C, solid or stranded. Do not solder tin wire ends. All CT: 333mV output at rated current.
Page 36 Chapter 1: Installation and Initial Configuration PMB Branch Circuit Wiring CT plugs into 2-pin locking connector (Molex 43640-0201) Branch Circuits have two labels: Red labels for odd/even numbered panels. White labels for sequentially numbered panels. Multi-conductor CT cable. Available lengths: 3m, 10m. Connect labeled end into matching labeled connector All CTs 333mV output.
Page 37 Chapter 1: Installation and Initial Configuration PMM Power Wiring PMM can be powered from the voltage measurement inputs or from an auxiliary AC power source. Powering from the voltage measurement inputs minimizes circuitry, but the meter may stop functioning if the voltage turns off.
Page 38 Chapter 1: Installation and Initial Configuration PMMC Power Wiring PMMC can be powered from the voltage measurement inputs or from an auxiliary AC power source. Powering from the voltage measurement inputs minimizes circuitry, but the meter may stop functioning if the voltage turns off.
Page 39 Chapter 1: Installation and Initial Configuration Controller Wiring to Meters The PMC controller supports up to 70 power meters (PMM) OR eight branch circuit meters (PMM+PMB) using daisy-chain wiring with shielded cat 5 Ethernet cable. The wiring order of the modules and controller is not important.
Page 40: Login And Configuration
Chapter 1: Installation and Initial Configuration  Panel Layout Login and Configuration Connect your PC directly to the BCM2 to complete the initial configuration. To access the web interface at the rack: 1. Disable the wireless interface of the PC. 2.
Page 41: Configuring Power Meters And Branch Circuit Monitors
You can configure your product with a spreadsheet, or in the product's web interface. To configure with a spreadsheet: Go to Raritan.com and download the configuration spreadsheet from the BCM2 Support page. Follow the instructions in the spreadsheet. To configure with the product web interface: Login and Configuration Make a network connection to the product.
Page 42 Chapter 1: Installation and Initial Configuration Scan Power Meters Click Power Meters. If nothing is configured, scan begins immediately in Unconfigured Meters section. Click Rescan to refresh the list. Click the power meter or panel in the discovered list to configure it. Types: PM: 3-phase Panel: BCM...
Page 43 Chapter 1: Installation and Initial Configuration Configure Power Meter Enter a name. Select the circuit type:  Single Phase  Split Phase  3-phase Enter the mains circuit breaker rating. Select the checkbox for each CT installed. Enter the CT rating. Ratings are marked on the CT.
Page 44 Chapter 1: Installation and Initial Configuration Configure Panel Mains Circuit Enter a name. Select the circuit type:  Single Phase  Split Phase  3-phase Enter the number of circuit positions in the panel. Select the panel layout: one or two columns.
Page 45 Chapter 1: Installation and Initial Configuration Configure Panel Branch Circuits In the Power Meters page, click the panel. The Panel details page opens. In the Panel Branch Circuits section, click the circuit position to open the pop-up menu. Click Create Circuit. The Create Circuit dialog opens.
Page 46 Chapter 1: Installation and Initial Configuration Circuits appear in the list with a black bracket around the circuit positions.
Page 47: Using The Bcm2'S Display
Chapter 1: Installation and Initial Configuration Using the BCM2's Display Automatic Mode: The BCM2 has a display with automatic and manual modes. In automatic mode, the display scrolls through readings. Manual Mode: In manual mode, you can select readings and settings to view. Press to view the Main Menu.
Page 48: Operating The Dot-Matrix Lcd Display
Chapter 1: Installation and Initial Configuration 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 BCM2 device, built-in components, or connected peripheral devices •...
Page 49: Alerts
Chapter 1: Installation and Initial Configuration • Both bars turn black when there are NO alerts. Screen with black bars 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 •...
Page 50 Chapter 1: Installation and Initial Configuration The top and bottom bars on the LCD display may be yellow or red,  Operating the depending on the type(s) of available alerts. See Dot-Matrix LCD Display (on page 36). Number Description Sensor names. Sensor readings and/or states.
Page 51: Power Meters
Chapter 1: Installation and Initial Configuration Power Meters The Power Meters menu option displays information and readings for each power meter. Use the arrow buttons to navigate through all power meters.
Page 52 Chapter 1: Installation and Initial Configuration Panels Navigate to a panel from the power meter details and press O (select) to display the panel details and readings.
Page 53 Chapter 1: Installation and Initial Configuration Branch Circuits Navigate to a branch circuit from the panel details and press O (select) to display the branch circuit details and readings.
Page 54 Chapter 1: Installation and Initial Configuration Branch Circuit Details...
Page 55: Peripherals
Chapter 1: Installation and Initial Configuration Peripherals If there are no Raritan environmental sensor packages connected to your BCM2, the LCD display shows the message "No managed devices" for the "Peripherals" menu command. If you have enabled the front panel actuator control function, you can switch on or off a connected actuator using the LCD display.
Page 56 Chapter 1: Installation and Initial Configuration Number Description Sensor or actuator names. Sensor or actuator states as listed below. For further information, see Sensor/Actuator States (on page 123).  n/a = unavailable  Normal  Alarmed  Lower Critical = below lower critical ...
Page 57 Chapter 1: Installation and Initial Configuration Number Description Sensor or actuator name. 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 58 Chapter 1: Installation and Initial Configuration 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 59: Chapter 2 Connecting External Equipment (Optional)
Chapter 2 Connecting External Equipment (Optional) More features are available if you connect Raritan's or third-party external equipment to your BCM2. In This Chapter Connecting Environmental Sensor Packages .......... 47 Connecting Asset Management Strips ............66 Connecting a Logitech Webcam ..............76 Connecting a GSM Modem ................
Page 60: Identifying The Sensor Port
Chapter 2: 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 BCM2, or damages may be caused to the BCM2 and/or connected sensor packages.
Page 61 Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the BCM2. To directly connect a differential air pressure sensor: 1. Connect a Raritan-provided phone cable to the IN port of a differential air pressure sensor. 2. Get an RJ-12 to RJ-45 adapter. Connect the adapter's RJ-12 connector to the other end of the phone cable.
Page 62 DPX2, DPX3 or DX sensor packages to it. DPX-ENVHUB4 sensor hubs CANNOT be cascaded. You can connect only one hub to each SENSOR port on the BCM2. Tip: The Raritan sensor hub that supports ALL types of Raritan environmental sensor packages is . See...
Page 63 DPX-ENVHUB4 sensor hub DPX sensor packages Using an Optional DPX-ENVHUB2 cable DPX-ENVHUB2 A Raritan cable doubles the number of connected environmental sensors per SENSOR port. This cable supports DPX sensor packages only. Do NOT connect DPX2, DPX3 or DX sensor packages to it.
Page 64 Sensor connection restrictions: Connect a DPX sensor package to the BCM2 using the sensor cable • pre-installed (or provided) by Raritan. You MUST NOT extend or modify the sensor cable's length by using any tool other than the Raritan's sensor hubs.
Page 65: Dpx2 Sensor Packages
RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors and Actuators Guide (or Online Help) on Raritan Support page http://www.raritan.com/support/...
Page 66 Chapter 2: Connecting External Equipment (Optional) The following procedure illustrates a DPX2 sensor cable with three head connectors. Your sensor cable may have fewer head connectors. Warning: If there are free head connectors between a DPX2 sensor cable's RJ-12 connector and the final attached DPX2 sensor package, the sensor packages following the free head connector(s) on the same cable do NOT work properly.
Page 67: Dpx3 Sensor Packages
Chapter 2: Connecting External Equipment (Optional) b. Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the BCM2. OR you can directly connect the DPX2 sensor package to a DX sensor Connecting a chain without using any RJ-12 to RJ-45 adapter. See DPX2 Sensor Package to DX (on page 59).
Page 68 Chapter 2: Connecting External Equipment (Optional) Repeat the same steps to cascade more DPX3 sensor packages. 3. Connect the first DPX3 sensor package to the BCM2 by plugging its cable's connector into the RJ-45 SENSOR port of the BCM2. Connecting a DPX2 Sensor Package to DPX3 You can connect only one DPX2 sensor package to the "end"...
Page 69: Dx Or Dx2 Sensor Packages
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. When cascading DX, remember that the BCM2 only supports a maximum of 32 sensors and/or actuators.
Page 70 Chapter 2: Connecting External Equipment (Optional) Numbers Components RJ-45 ports, each of which is located on either end of a DX sensor package. RJ-12 port, which is reserved for future use and now blocked. Removable rackmount brackets. Note: A DX2 sensor does not have the RJ-12 port and looks slightly different from the above image.
Page 71 Chapter 2: Connecting External Equipment (Optional) Connecting a DPX2 Sensor Package to DX You can connect only one DPX2 sensor package to the "end" of a DX sensor chain. It is strongly recommended to use an RJ-12 to RJ-45 adapter for connecting the DPX2 to the final DX in the chain. The maximum number of DX sensor packages in the chain must be less than 12 when a DPX2 sensor package is involved.
Page 72: Using An Optional Dpx3-Envhub4 Sensor Hub
Plug the other end of the cable into the RJ-45 SENSOR port of the BCM2. 2. Connect the Raritan sensor packages to any of the four OUT ports on the hub. An RJ-12 to RJ-45 adapter is required for connecting a DPX or ...
Page 73 Chapter 2: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. The BCM2 A standard network cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages...
Page 74: Mixing Diverse Sensor Types
Chapter 2: Connecting External Equipment (Optional) Mixing Diverse Sensor Types You can mix DPX, DPX2, DPX3 and DX sensor packages on one BCM2 according to the following sensor combinations. In some scenarios, the DPX3-ENVHUB4 sensor hub is required. The BCM2 does NOT support any other sensor-mixing combinations than those described in this section.
Page 75 Chapter 2: Connecting External Equipment (Optional) An RJ-12 to RJ-45 adapter is recommended to connect a DPX or • DPX2 sensor package to DPX3-ENVHUB4. • In the following diagrams, the sensor package in "green" can be replaced by a DPX2 sensor package. The sensor package in "blue" can be one DPX2, DPX3 or DX sensor package.
Page 76 Chapter 2: Connecting External Equipment (Optional)
Page 77 Chapter 2: Connecting External Equipment (Optional) Mix DPX3 and DX in a sensor chain: Any DX sensor package in a chain can be replaced by a DPX3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12.
Page 78: Connecting Asset Management Strips
The difference between the master and slave asset strips is that the master asset strip has an RJ-45 connector while the slave does not. The following diagram illustrates some asset strips. Note that Raritan provides more types of asset strips than the diagram.
Page 79 Chapter 2: Connecting External Equipment (Optional) 8U MASTER asset strip with 8 tag ports 8U SLAVE asset strip with 8 tag ports 5U "ending" SLAVE asset strip with 5 tag ports Note: Unlike general slave asset strips, which have one DIN connector respectively on either end, the ending slave asset strip has one DIN connector on only one end.
Page 80: Introduction To Asset Tags
Chapter 2: Connecting External Equipment (Optional) Note: The asset strip is implemented with a tilt sensor so it can be mounted upside down. 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 81 Chapter 2: Connecting External Equipment (Optional) 3. Connect the asset strip assembly to the BCM2 device, using a network patch cable (CAT5e or higher). Connect one end of the cable to the RJ-45 connector on the  MASTER asset strip. Connect the other end of the cable to the FEATURE port on the ...
Page 82: 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 83 Chapter 2: 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 BCM2 device's web interface.
Page 84 Chapter 2: 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 85: Connecting Composite Asset Strips (Ams-Mx-Z)
Chapter 2: 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: It has two RJ-45 connectors.
Page 86 Chapter 2: 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 75) for the maximum number of composite asset strips supported per chain.
Page 87 It is NOT supported to hot swap or hot plug any AMS-Mx-Z in a • composite asset strip chain that has been connected to Raritan's PDU (or PMC). Therefore, first disconnect the chain from the device when you need to swap or add any AMS-Mx-Z to the chain.
Page 88: Connecting A Logitech Webcam
Pro 9000, Model 960-000048 ® ® Other UVC-compliant webcams may also work. However, Raritan has neither tested them nor claimed that they will work properly. Tip: You can easily find a list of UVC-compliant webcams on the Internet. The BCM2 supports up to two webcams. After connecting a webcam, you can retrieve visual information from anywhere through the BCM2 web interface.
Page 89: Connecting An Analog Modem
NETCOMM IG6000 Industrial Grade SmartModem • • US Robotics 56K modem The BCM2 may also support other analog modems which Raritan did not test. Note that the BCM2 does NOT support dial-out or dial-back operations via the modem. To connect an analog modem: 1.
Page 90: Connecting An External Beeper
Chapter 2: Connecting External Equipment (Optional) Connecting an External Beeper The BCM2 supports the use of an external beeper for audio alarms. External beepers that are supported include but may not be limited to the following: • Mallory Sonalert MODEL SNP2R After having an external beeper connected, you can create event rules for the BCM2 to switch on or off the external beeper when specific events Event Rules and Actions...
Page 91: Wireless Network Connection
TP-Link TL-WDN3200 v1 A/B/G/N Raritan USB WIFI A/B/G/N Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN adapter to connect to an wireless network, the handshake 802.11n timeout setting must be changed to 500 or greater, or the wireless connection will fail.
Page 92 Chapter 2: Connecting External Equipment (Optional) Key management: WPA-PSK, or WPA-EAP with PEAP and  MSCHAPv2 authentication Encryption: CCMP (AES)  Important: Supported 802.11 network protocols vary according to the USB Wireless wireless LAN adapter being used with the BCM2. See LAN Adapters (on page 79).
Page 93: Chapter 3 Using The Web Interface
Default login: Username: admin • • Password: raritan You are prompted to change the defaults at your first login. • To login to the web interface: 1. In a supported browser, go to the IP address of the PMC (BCM2).
Page 94: Supported Web Browsers
Chapter 3: Using the Web Interface Supported Web Browsers Internet Explorer • ® • Microsoft Edge Firefox 52 and later • ® Safari (Mac) • ® • Google Chrome 52 and later ® ® Android 4.2 and later • iOS 7.0 and later •...
Page 95: Changing Your Password
Chapter 3: Using the Web Interface Changing Your Password You must have the Change Own Password permission to change your Creating Roles Creating a Role own password. See (see " " on page 164, on page 159). You must have Administrator Privileges to change other users' Editing or Deleting Users passwords.
Page 96: Introduction To The Web Interface
Chapter 3: Using the Web Interface A password comprises 4 to 64 characters.  Introduction to the Web Interface The web interface consists of four areas as shown below. Operation: 1. Click any menu or submenu item in the area of 2.
Page 97 Chapter 3: Using the Web Interface To return to the main menu and the Dashboard page, click on the top-left corner. Number Web interface element Menu Data/setup page of the selected menu item.  Left side: - BCM2 device name. Note: To customize the device name, see .
Page 98  Online Documentation: link to the BCM2 online help. - See Browsing through the Online Help.  Raritan Support: link to the Raritan Technical Support webpage.  Date and time of your user account's last login. - Click Last Login to view your login history.
Page 99: Menu
Device data and settings, such as the device name and MAC address. See PMC. Power Meters Power meters and panels data and settings. See Power Meters. Peripherals Status and settings of Raritan environmental sensor packages, if connected. Peripherals (on page 115).
Page 100 Chapter 3: 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 101 Chapter 3: 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 102: The Yellow- Or Red-Highlighted Sensors
Chapter 3: Using the Web Interface The Yellow- or Red-Highlighted Sensors When a numeric sensor's reading enters the warning or critical range, the background color of that sensor's row turns to yellow or red for alerting you. For a discrete (on/off) sensor, the row changes the background color when the sensor enters the abnormal state.
Page 103: Viewing The Dashboard
Chapter 3: Using the Web Interface To find the exact meaning of the alert, read the information shown in the State (or Status) column: • below lower critical: The numeric sensor's reading drops below the lower critical threshold. • below lower warning: The numeric sensor's reading drops below the lower warning threshold.
Page 104: Dashboard - Power Meters
Chapter 3: Using the Web Interface Configured power meters with basic details and current readings for each phase . Dashboard - Power Meters (on page 92). Enabled thresholds show alerts in red and yellow. Dashboard - Alerted Sensors (on page 93) Alarms that need attention.
Page 105: Dashboard - Alerted Sensors
Chapter 3: Using the Web Interface Dashboard - Alerted Sensors When any internal sensors or environmental sensor packages connected to the BCM2 enter an abnormal state, the Alerted Sensors section in the Dashboard show them for alerting users. This section also lists tripped circuit breakers or blown fuses, if available.
Page 106: Dashboard - Alarms
Chapter 3: 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 For numeric sensors:  above upper warning  below lower warning For numeric sensors: ...
Page 107 Chapter 3: Using the Web Interface This table explains each column of the alarms list. Field Description Name The customized name of the Alarm action. Reason The first event that triggers the alert. First Appearance The date and time when the event indicated in the Reason column occurred for the first time.
Page 108: Dashboard - Power Meter History
Chapter 3: Using the Web Interface Dashboard - Power Meter History The history graph for the power meter helps you observe whether there were abnormal events within the past range of time. The default is to show the active power data. Select a different data type by clicking the selector below the diagram.
Page 109: Pmc Power Metering Controller
Chapter 3: Using the Web Interface Select the checkbox for the lines you want to add to the diagram. Each line is assigned a custom color. Hover the mouse over the graph line to view details for the minute. Each line color is coordinated in the details. PMC Power Metering Controller Click PMC in the Menu to open the Power Metering Controller page.
Page 110: Power Meters
Chapter 3: Using the Web Interface If set to Rack Units, the Z coordinate field in the peripheral device  settings only allows to enter numerical values. If set to Free-form, any input is allowed. The label of the input field on the peripheral device settings page will indicate which format is expected.
Page 111: Viewing The Power Meter Data
Chapter 3: Using the Web Interface Viewing the Power Meter Data To view power meter data, go to the Power Meters page and click to select a power meter. You can also select a power meter from the dashboard. The Power Meter details page opens with a list of sensor data and readings.
Page 112: Power Meter Management
Chapter 3: Using the Web Interface State indicates if readings are normal, warning or critical. Click actions menu for more options. Power Meter Management This section introduces the operations for a power meter module. For Viewing the Power information on the power meter's sensor data, see Meter Data (on page 99).
Page 113: Enable Modbus Access
Chapter 3: Using the Web Interface Enable Modbus Access For details on Modbus, see Configuring Modbus TCP and/or RTU. To enable Modbus access: 1. Select the power meter or panel in the Power Meters page. 2. Click the actions icon to open the options, then choose Configure. 3.
Page 114 Chapter 3: Using the Web Interface A short list of readings is available by default. To add more readings, click Select Readings, then choose the sensors to add. See graphic for menu details. Panel Mains Circuit Click actions menu for more options. See Management (on page 104).
Page 115 Chapter 3: Using the Web Interface Readings for each phase. Value contains the reading for the sensor. State indicates if readings are normal, warning or critical. Branch circuit details and readings. Click a branch circuit to show the menu: Circuit Details to open a new page.
Page 116: Panel Mains Circuit Management
Chapter 3: Using the Web Interface Readings for each phase. Each phase is labeled with the CT number. Value contains the reading for the sensor. State indicates if readings are normal, warning or critical. Panel Mains Circuit Management This section introduces the operations for a panel. For information on Viewing the Panel Data the panel's sensor data, see (on page 101).
Page 117: Panel Branch Circuits Operations
Chapter 3: Using the Web Interface Panel Branch Circuits Operations This section introduces the operations for the Panel Branch Circuits section. To manage branch circuits, click the desired branch circuit to open a menu. Note: For information on creating panel branch circuits, see Configure (on page 33).
Page 118: Setting Power Thresholds
Chapter 3: Using the Web Interface Configure Thresholds Edit Thresholds: See (on page 106). • Configure Circuit: Click to open the circuit's setup dialog. See • Configure Panel Branch Circuits (on page 33). • Reset Active Energy: This button resets this circuit's active energy to 0 (zero) Wh.
Page 119 Chapter 3: Using the Web Interface The details page opens. In the details page, click the actions icon, then choose Edit Thresholds. The sensor list displays. Click a sensor to open the Edit Threshold dialog. Select the checkbox for the level, and enter the threshold current in amps.
Page 120 Chapter 3: Using the Web Interface "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the BCM2 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 BCM2 to assert.
Page 121 Chapter 3: Using the Web Interface In the threshold settings, the Assertion Timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must remain in the "worse" new state before the BCM2 triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the BCM2 does NOT assert the worse state.
Page 122 Chapter 3: Using the Web Interface "To De-assert" and Deassertion Hysteresis After the BCM2 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 123 Chapter 3: Using the Web Interface...
Page 124 Chapter 3: Using the Web Interface 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 125: Export Readings As Csv
Chapter 3: Using the Web Interface Export Readings as CSV Export instantaneous readings from the power meter controller as a CSV file. The export file may be helpful to diagnose issues. You can export readings from each configured power meter and panel. Power meter includes the following readings: •...
Page 126 Chapter 3: Using the Web Interface  Position  Phase  CT Number  Current  Active Power  Reactive Power To export readings as CSV: 1. Click Power Meters in the Menu. 2. Click the actions icon, then choose Export Readings as CSV.
Page 127: Peripherals
Chapter 3: Using the Web Interface Peripherals If there are Raritan environmental sensor packages connected to the Connecting BCM2, they are listed on the Peripherals page. See Environmental Sensor Packages (on page 47). An environmental sensor package comprises one or some of the following sensors/actuators: •...
Page 128 Chapter 3: Using the Web Interface Go to an individual sensor's or actuator's data/setup page by • clicking its name. If wanted, you can resort the list by clicking the desired column header. See Sorting a List. Sensor/actuator overview on this page: If any sensor enters the alarmed state, it is highlighted in yellow or red.
Page 129 Chapter 3: Using the Web Interface Column Description Serial Number This is the serial number printed on the sensor package's label. It helps to identify your Raritan Finding the Sensor's Serial sensors/actuators. See Number (on page 125). Position The data indicates where this sensor or actuator is located in the sensor chain.
Page 130 Chapter 3: Using the Web Interface To select ALL sensors/actuators, select the topmost checkbox in  the header row. Figure 1: Select all checkboxes 3. To release selected ones, click > Release. To manage them, click > Manage. The management action triggers a "Manage peripheral device" ...
Page 131 Chapter 3: 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 applying to newly-added sensors but also the threshold values of the already-managed sensors Individual where default thresholds are being used.
Page 132 Chapter 3: Using the Web Interface For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 576). 4. Click Save. Tip: To customize the threshold settings on a per-sensor basis, go to (on page 129). Individual Sensor/Actuator Pages To turn on or off any actuator(s): in the same status...
Page 133: Yellow- Or Red-Highlighted Sensors
Chapter 3: Using the Web Interface Yellow- or Red-Highlighted Sensors The BCM2 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 134: Managed Vs Unmanaged Sensors/Actuators
Chapter 3: Using the Web Interface Sensor status Color States shown in Description the interface alarmed State sensors enter the abnormal state. Alarmed  Circuit breaker trips. OCP alarm Open -- OR --  Fuse blown. If you have connected a Schroff LHX/SHX heat exchanger, when any ®...
Page 135: Sensor/Actuator States
Chapter 3: Using the Web Interface Sensor/Actuator States They show one of the managed states. See • (on page 123). For managed 'numeric' sensors, their readings are retrieved and • displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable"...
Page 136 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 Support page available on Raritan's http://www.raritan.com/support/ Managed actuator states: State Description The actuator is turned on.
Page 137: Finding The Sensor's Serial Number
Chapter 3: Using the Web Interface Finding the Sensor's Serial Number A DPX environmental sensor package includes a serial number tag on the sensor cable. A DPX2, DPX3 or DX sensor package has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the BCM2.
Page 138: Identifying The Sensor Position And Channel
Port 1, Chain Position 2 For example, • If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DPX2, DPX3 and DX series, but NOT indicated for DPX series. Hub Port 3...
Page 139: Managing One Sensor Or Actuator
Chapter 3: Using the Web Interface Example Physical position Connected to the sensor port #1. Port 1  Connected to the sensor port #1. Port 1,  The sensor/actuator is the 2nd channel of the sensor package. Channel 2  Connected to the sensor port #1. Port 1, ...
Page 140 Otherwise, it shows the word "unused." 3. Click Manage. Special note for a Raritan humidity sensor: A Raritan humidity sensor is able to provide two measurements - relative and absolute humidity values. A relative humidity value is measured in percentage (%).
Page 141: Individual Sensor/Actuator Pages
Chapter 3: 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 142 Chapter 3: 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 143 Chapter 3: 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 Binary Sensor This field is available for a contact closure sensor only. Subtype Determine the sensor type of your contact closure detector.
Page 144 Chapter 3: Using the Web Interface To view a numeric sensor's chart This sensor's data within the past tens of minutes is shown in the chart. Note that only a numeric sensor has this diagram. State sensors and actuators do not have such data. To retrieve the exact data at a particular time, hover your mouse ...
Page 145 Chapter 3: Using the Web Interface To turn on or off an actuator: 1. Click the desired control button. : Turn ON. : Turn OFF. 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Note: If you try to turn on more than one "powered dry contact"...
Page 146: Sensor/Actuator Location Example
Power CIM This type represents one of the following Raritan products:  Raritan power CIM, D2CIM-PWR. This CIM is used to connect the BCM2 to the Raritan digital KVM switch -- Dominion KX II / III.  Dominion KSX II...
Page 147 Chapter 3: Using the Web Interface When the BCM2 detects the connection of any listed device, it replaces 'Feature Port' in the menu with that device's name and shows that Asset Strip External device's data/settings instead. See (on page 136), Beeper Schroff LHX/SHX Power CIM...
Page 148: Asset Strip
LHX/SHX heat exchangers is disabled. See (on page Miscellaneous 303). Asset Strip After connecting and detecting Raritan asset management strips (asset strips), the BCM2 shows 'Asset Strip' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting Asset Management (on page 66).
Page 149 Chapter 3: Using the Web Interface 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.  For the current generation of asset strips, which show the suffix "G3"...
Page 150 Chapter 3: Using the Web Interface For color settings, there are two ways to set the color. Click a color in the color palette.  Type the hexadecimal RGB value of the color, such as #00FF00.  3. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below.
Page 151 Chapter 3: Using the Web Interface To customize a single rack unit's settings: You can make a specific rack unit's LED behave differently from the others on the asset strip, including the LED light and color. 1. Click the desired rack unit on the Rack Units list. The setup dialog for the selected one appears.
Page 152 Chapter 3: 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 153 Chapter 3: 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 154 Chapter 3: 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 155 Chapter 3: 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 156 Chapter 3: 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 BCM2, it automatically checks its own firmware version against the version of the asset strip firmware stored in the BCM2 firmware.
Page 157: External Beeper
Chapter 3: Using the Web Interface External Beeper After connecting and detecting a supported external beeper, the BCM2 shows 'External Beeper' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting an External Beeper (on page 78). To open the External Beeper page, click it in the Menu.
Page 158: Schroff Lhx/Shx
Chapter 3: Using the Web Interface Schroff LHX/SHX You must enable the LHX/SHX support for the BCM2 to detect the presence of a supported Schroff LHX/SHX heat exchanger. See ® Miscellaneous (on page 303). After enabling the LHX/SHX support and connecting a supported Schroff ®...
Page 159 Chapter 3: Using the Web Interface Feature For the functionality of this icon on the top-right corner, see Port (on page 134). 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 160 Chapter 3: 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 161 Chapter 3: 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 162 Chapter 3: 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 BCM2 and turned...
Page 163: Power Cim
• Power CIM After connecting and detecting a Raritan power CIM, the BCM2 shows 'Power CIM' in place of 'Feature Port' in the menu. See Dominion KX II / III Configuration or Dominion KSX II, SX or SX II Configuration.
Page 164: User Management
Chapter 3: Using the Web Interface User Management User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis. The BCM2 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 165: Creating Users
Chapter 3: 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 166 Chapter 3: Using the Web Interface Field/setting Description Force password When selected, a password change request change on next automatically appears when next time the user login logs in. Changing Your Password For details, see page 83). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
Page 167 Chapter 3: 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 •...
Page 168 Chapter 3: 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 169: Editing Or Deleting Users
Chapter 3: 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 170 Chapter 3: 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 171: Creating Roles
Chapter 3: Using the Web Interface Creating Roles A role is a combination of permissions. Each user must have at least one role. Creating Users The BCM2 provides two built-in roles. See (on page 153). Built-in role Description Admin Provide full permissions. Operator Provide frequently-used permissions, including: •...
Page 172: Editing Or Deleting Roles
Chapter 3: Using the Web Interface 5. If any privilege requires the argument setting, the symbol well as the text 'Add XXX' display on that privilege's row, where XXX is the privilege's name. To select such a privilege: a. Click on that privilege's row to display a list of available arguments for this privilege.
Page 173 Chapter 3: 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 174: Setting Your Preferred Measurement Units
Chapter 3: Using the Web Interface Setting Your Preferred Measurement Units You can change the measurement units shown in the BCM2 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 175: Setting Default Measurement Units
Chapter 3: Using the Web Interface Setting Default Measurement Units Default measurement units are applied to all BCM2 user interfaces across all users, including users accessing the BCM2 via external User authentication servers. For a list of affected user interfaces, see Interfaces Showing Default Units (on page 163).
Page 176: Setting Up Roles
Chapter 3: Using the Web Interface Setting Up Roles A role defines the operations and functions a user is permitted to perform or access. Every user must be assigned at least a role. The BCM2 is shipped with two built-in roles: Admin and Operator. •...
Page 177: Modifying A Role
Chapter 3: Using the Web Interface 3. Type the role's name in the Role Name field. 4. Type a description for the role in the Description field. 5. Click the Privileges tab to assign one or multiple permissions. a. Click Add. The "Add Privileges to new Role" dialog appears. b.
Page 178 Chapter 3: Using the Web Interface a. Click Add. The "Add Privileges to Role XXX" dialog appears, where XXX is the role name. b. Select the permission you want from the Privileges list. c. If the permission you selected contains any argument setting, the Arguments list is shown to the right, such as the Switch Actuator permission.
Page 179: Device Settings
Chapter 3: Using the Web Interface Device Settings Click 'Device Settings' in the Menu, 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 193) Configuring SNMP Settings SNMP (on page 194)
Page 180 Chapter 3: Using the Web Interface Menu command Submenu command Refer to... Changing SSH Settings (on page 198) Changing Telnet Settings Telnet (on page 199) Changing Modbus Settings Modbus (on page 199) Enabling Service Advertising Server Advertising (on page 200) Creating IP Access Control Rules Security IP Access Control...
Page 181: Configuring Network Settings
Chapter 3: Using the Web Interface Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the Network page after connecting the BCM2 to your network. You can enable both the wired and wireless networking on the BCM2 so that it has multiple IP addresses -- wired and wireless IP.
Page 182 Chapter 3: Using the Web Interface Ethernet 5. To configure the ETHERNET interface settings, see Interface Settings (on page 172). 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): LDAP •...
Page 183 Chapter 3: Using the Web Interface Field/setting Description Static : Manually configure the IPv4 settings.  • DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements: Consists of alphanumeric characters and/or hyphens  Cannot begin or end with a hyphen ...
Page 184 Chapter 3: Using the Web Interface Field Description DNS Resolver Determine which IP address is used when the Reference DNS resolver returns both IPv4 and IPv6 addresses.  IPv4 Address: Use the IPv4 addresses.  IPv6 Address: Use the IPv6 addresses. DNS Suffixes Specify a DNS suffix name if needed.
Page 185 Chapter 3: Using the Web Interface Other Ethernet settings: Field Description Speed Select a LAN speed. Auto: System determines the optimum LAN • speed through auto-negotiation. • 10 MBit/s: Speed is always 10 Mbps. 100 MBit/s: Speed is always 100 Mbps. •...
Page 186 Chapter 3: Using the Web Interface Field/setting Description Hardware State Check this field to ensure that the BCM2 device has detected a wireless USB LAN adapter. If not, verify whether the USB LAN adapter is firmly connected or whether it is supported. Type the name of the wireless access point (AP) SSID Force AP BSSID...
Page 187 Chapter 3: Using the Web Interface • Available settings for the CA Certificate: If the required certificate file is a chain of certificates, and you are not TLS Certificate sure about the requirements of a certificate chain, see Chain (on page 592). Field/setting Description Enable verification...
Page 188 Chapter 3: Using the Web Interface Field/setting Description DHCP Configuration : Auto-configure IPv4 settings via DHCP  servers. Static : Manually configure the IPv4 settings.  DHCP settings: Optionally specify the preferred hostname, which • must meet the following requirements: Consists of alphanumeric characters and/or hyphens ...
Page 189 Chapter 3: Using the Web Interface Wireless LAN Diagnostic Log The BCM2 provides a diagnostic log for inspecting connection errors that occurred over the wireless network interface. The information is useful for technical support. Note that the WLAN Diagnostic Log shows data only after the Network Interface is set to Wireless.
Page 190 Chapter 3: 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 191 Chapter 3: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your BCM2 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 192 Chapter 3: 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 BCM2: • fd07:2fa:6cff:1111::50 fd07:2fa:6cff:2405::80 •...
Page 193 Chapter 3: Using the Web Interface In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your BCM2 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 194 Chapter 3: Using the Web Interface Interface list for BCM2: Interface name Description When another wired network is connected to the BRIDGE Ethernet port of your BCM2, and your BCM2 has been set to the bridging mode, select this interface name instead of the Ethernet interface. When another wired network is connected to the ETHERNET Ethernet port of your BCM2, and the bridging...
Page 195 Note: BCM2 in the Port Forwarding mode does not support APIPA. See APIPA and Link-Local Addressing. To configure the cascading mode: 1. Connect the Raritan device to the LAN and find its IP address, or connect it to a computer. For computer connection instructions, see Connecting the BCM2 ...
Page 196 Chapter 3: Using the Web Interface Note that if either setting below is incorrectly configured, a networking issue occurs. Field Description Master or Slave. Role This is to determine which device is the (available on all master and which ones are slave cascaded devices) devices.
Page 197 Chapter 3: Using the Web Interface Online cascading information: For detailed information on the cascading configuration and restrictions, Cascading Guide see the , which is available from Raritan website's Support page http://www.raritan.com/support/ Overview of the Cascading Modes Setting You must apply a cascading mode to the cascading chain. See the Cascading Mode (on page 183).
Page 198 Chapter 3: Using the Web Interface In this mode, the DHCP server communicates with the master device alone and assigns one IP address to the master device. All slave devices share the same IP address as the master device. You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave device with the shared IP address.
Page 199 Chapter 3: Using the Web Interface Protocols HTTP TELNET SNMP MODBUS • 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...
Page 200 • The Port Forwarding mode is applied to a cascading chain Assumption: comprising three Raritan devices. The IP address is 192.168.84.77. Master device: Position code for the master device is '00' so each port number is 5NN00 as listed below.
Page 201 Chapter 3: Using the Web Interface To access the master device via SSH, the command is: • ssh -p 50200 192.168.84.77 Examples using standard TCP/UDP ports: To access the master device via HTTPS, the IP address is: • https://192.168.84.77:443/ To access the master device via HTTP, the IP address is: •...
Page 202 Cascading Troubleshooting. To add a device to an existing chain: 1. Connect the Raritan device to the LAN and find its IP address, or connect it to a computer. 2. Log in to this device and set its cascading mode to be the same as Setting the Cascading the existing chain's cascading mode.
Page 203 Chapter 3: 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 204: Configuring Network Services
Chapter 3: Using the Web Interface Configuring Network Services The BCM2 supports the following network communication services. HTTPS and HTTP enable the access to the web interface. Telnet and SSH Using the enable the access to the command line interface. See Command Line Interface (on page 355).
Page 205 Enabling Service Advertising Service Advertising (on page 200) 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 206 Chapter 3: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the BCM2 device. Enabling SNMP communication allows the manager to retrieve and even control the power status of each outlet. Besides, you may need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule"...
Page 207 Chapter 3: 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. ...
Page 208 Chapter 3: Using the Web Interface sysName - the name assigned to the system  sysLocation - the location of the system  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.
Page 209 Chapter 3: Using the Web Interface Field Description Server Name Type the name or IP address of the mail server. 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.
Page 210 Chapter 3: Using the Web Interface Field/setting Description  Select this checkbox to make the Allow expired and authentication succeed regardless of the not yet valid certificate's validity period. certificates  After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
Page 211 Chapter 3: Using the Web Interface Password authentication only: Enables the password-based login  only. Public key authentication only: Enables the public key-based  login only. Password and public key authentication: Enables both the  password- and public key-based login. This is the default. 5.
Page 212 Chapter 3: Using the Web Interface Enabling Service Advertising The BCM2 advertises all enabled services that are reachable using the IP network. This feature uses DNS-SD (Domain Name System-Service Discovery) and MDNS (Multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and MDNS. The advertised services include the following: HTTP •...
Page 213: Configuring Security Settings
Chapter 3: Using the Web Interface Configuring Security Settings The BCM2 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 214 Chapter 3: 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 BCM2, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind: Rule order is important.
Page 215 Chapter 3: 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 216 Chapter 3: Using the Web Interface You can select any existing rule and then click  to change its priority. 7. Click Save. The rules are applied. To configure IPv6 access control rules: 1. On the same page, select the Enable IPv6 Access Control checkbox to enable IPv6 access control rules.
Page 217 Chapter 3: Using the Web Interface Editing or Deleting IP Access Control Rules When an existing IP access control rule requires updates of IP address range and/or policy, modify them accordingly. Or you can delete any unnecessary rules. To modify or delete a rule: 1.
Page 218 Chapter 3: Using the Web Interface Deny: Rejects any user's login attempt when no matching rules  are present. 4. Create rules. Refer to the tables below for different operations. ADD a rule to the end of the list  Click Append. ...
Page 219 Chapter 3: Using the Web Interface 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. On the same page, select the "Enable Role Based Access Control for IPv6"...
Page 220 IPv6 rules are not saved. Setting Up an SSL/TLS Certificate 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 221 IP addresses of the wanted hosts to this CSR so that a single certificate will be valid for all of them. Click when there are more than one additional hosts to add. support.raritan.com  Examples of subject alternative names: help.raritan.com help.raritan.net 192.168.77.50...
Page 222 Chapter 3: 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 BCM2 device's response.  Only 2048 is available now. Self Sign For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
Page 223 Chapter 3: 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 SSL Certificate section. Creating a Self-Signed Certificate When appropriate certificate and key files for the BCM2 device are unavailable, the alternative, other than submitting a CSR to the CA, is to...
Page 224 Chapter 3: 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 225 Active SSL Certificate section. Setting Up External Authentication 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...
Page 226 Chapter 3: Using the Web Interface For security purposes, users attempting to log in to the BCM2 must be authenticated. The BCM2 supports the following authentication mechanisms: • Local user database on the BCM2 Lightweight Directory Access Protocol (LDAP) • Remote Access Dial-In User Service (Radius) protocol •...
Page 227 Chapter 3: Using the Web Interface Special note about the AES cipher: The BCM2 device's SSL/TLS-based protocols, including LDAPS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the BCM2 and the client (such as a web browser), which is impacted by the cipher priority of the BCM2 and the client's cipher availability/settings.
Page 228 Chapter 3: Using the Web Interface  If using a Microsoft Active Directory server, consult your AD administrator for the name of the Active Directory Domain. • Bind Distinguished Name (DN) and password (if anonymous bind is NOT used) • The Base DN of the server (used for searching for users) The login name attribute (or AuthorizationString) •...
Page 229 Chapter 3: Using the Web Interface Field/setting Description Type of LDAP Server Choose one of the following options:  OpenLDAP  Microsoft Active Directory. Active Directory is an implementation of LDAP/LDAPS directory services by Microsoft for use in Windows environments. Security Determine whether you would like to use Transport Layer Security (TLS) encryption, which allows the BCM2 to communicate securely...
Page 230 Chapter 3: Using the Web Interface Field/setting Description Anonymous Bind Use this checkbox to enable or disable anonymous bind.  To use anonymous bind, select this checkbox.  When a Bind DN and password are required to bind to the external LDAP/LDAPS server, deselect this checkbox.
Page 231 Chapter 3: Using the Web Interface 5. Click Add Server. The new LDAP server is listed on the Authentication page. 6. To add more servers, repeat the same steps. 7. In the Authentication Type field, select LDAP. Otherwise, the LDAP authentication does not work.
Page 232 Chapter 3: Using the Web Interface Field/setting Description Type of RADIUS Select an authentication protocol. Authentication  PAP (Password Authentication Protocol)  CHAP (Challenge Handshake Authentication Protocol)  MS-CHAPv2 (Microsoft Challenge Handshake Authentication Protocol) CHAP is generally considered more secure because the user name and password are encrypted, while in PAP they are transmitted in the clear.
Page 233 Chapter 3: Using the Web Interface Managing External Authentication Settings Choose Device Settings > Security > Authentication to open the Authentication page, where you can: • Enable both the external and local authentication Edit or delete a server • Resort the access order of servers •...
Page 234 Chapter 3: Using the Web Interface 2. Select the following checkbox. Then the BCM2 always tries external authentication first. Whenever the external authentication fails, the BCM2 switches to local authentication. 3. Click Save. To disable external authentication: 1. In the Authentication Type, select Local. 2.
Page 235 Chapter 3: Using the Web Interface Tip: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command over a local connection. (on page 507). Unblocking a User To set limitations for login timeout and use of identical login names: 1.
Page 236 Chapter 3: Using the Web Interface To force users to create strong passwords: 1. Select the 'Enabled' checkbox of Strong Passwords to activate the strong password feature. The following are the default settings: Minimum length = 8 characters Maximum length = 32 characters At least one lowercase character = Required...
Page 237 Chapter 3: 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 238: Setting The Date And Time
Chapter 3: Using the Web Interface Setting the Date and Time Set the internal clock on the BCM2 device manually, or link to a Network Time Protocol (NTP) server. Note: If you are using Sunbird's Power IQ to manage the BCM2, you must configure Power IQ and the BCM2 to have the same date/time or NTP settings.
Page 239 Chapter 3: 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 ...
Page 240 Chapter 3: 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 241 Chapter 3: Using the Web Interface Windows NTP Server Synchronization Solution The NTP client on the BCM2 follows the NTP RFC so the BCM2 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 BCM2.
Page 242: Event Rules And Actions
Chapter 3: 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: Event: This is the situation where the BCM2 or a device connected to •...
Page 243 Chapter 3: 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 244 Chapter 3: 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 BCM2, ...
Page 245 Chapter 3: 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 246 Chapter 3: 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 247 Chapter 3: Using the Web Interface Event types Radio buttons Sensor availability Available radio buttons include "Unavailable," "Available" and "Both."  Unavailable: The BCM2 takes the action only when the chosen sensor is NOT detected and becomes unavailable.  Available: The BCM2 takes the action only when the chosen sensor is detected and becomes available.
Page 248 Chapter 3: Using the Web Interface Event types Radio buttons  Monitoring started: The BCM2 takes the Server monitoring action only when the monitoring of any event specified server starts.  Monitoring stopped: The BCM2 takes the action only when the monitoring of any specified server stops.
Page 249 Chapter 3: Using the Web Interface Default Log Messages These default log messages are recorded internally and emailed to specified recipients when BCM2 events occur (are TRUE) or, in some Send Email cases, stop or become unavailable (are FALSE). See page 258) to configure email messages.
Page 250 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. Card Reader Card Reader with id '[CARDREADERID]' Management >...
Page 251 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. Device > Device settings Device settings saved by user saved '[USERNAME]' from host '[USERIP]'.
Page 252 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. Device > A Radius error A Radius error occurred: occurred [ERRORDESC].
Page 253 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. Peripheral Device Slot > * > Peripheral device '[EXTSENSORNAME]' Peripheral device '[EXTSENSORNAME]' in Numeric Sensor >...
Page 254 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. Supply Status > fault fault state. fault PDU >...
Page 255 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. User Administration > Password of user '[UMTARGETUSER]' Password changed changed by user '[USERNAME]' from host '[USERIP]'.
Page 256 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. LHX/SHX > Sensor > Above Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at upper critical threshold [PORTTYPE] port '[PORTID]' asserted...
Page 257 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. LHX/SHX > Parameter Data Data loss in parameter memory was Loss detected on LHX at [PORTTYPE] port '[PORTID]'.
Page 258 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > State State of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[AMSSTATE]'. LHX/SHX > Voltage Low The supply voltage on LHX at The supply voltage on LHX at [PORTTYPE] [PORTTYPE] port '[PORTID]' is low.
Page 259 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE [POWERMETERSENSOR] > unavailable. available. Unavailable Power Meter Controller > Sensor '[POWERMETERSENSOR]' on Sensor '[POWERMETERSENSOR]' Power Meter > power meter '[POWERMETER]' on power meter '[POWERMETER]' [POWERMETER] >...
Page 260 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Power Meter Controller > Sensor '[PDUPOLESENSOR]' on pole Sensor '[PDUPOLESENSOR]' on Power Meter > '[POWERMETERPOLE]' of power meter pole '[POWERMETERPOLE]' of [POWERMETER] >...
Page 261 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE [CIRCUIT] > Sensor > [SENSORREADING] warning' at [SENSORREADING] [CIRCUITSENSOR] > Below [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. lower warning threshold Power Meter Controller > Sensor '[CIRCUITSENSOR]' on panel Sensor '[CIRCUITSENSOR]' on Power Meter >...
Page 262 Chapter 3: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE [PDUPOLESENSOR] > Below [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. lower warning threshold Power Meter Controller > Sensor '[PDUPOLESENSOR]' on pole Sensor '[PDUPOLESENSOR]' on Power Meter >...
Page 263 Chapter 3: Using the Web Interface System Tamper Alarm: • This action causes the BCM2 to show the alarm for the DX tamper sensor, if any, on the Dashboard page until a person acknowledges it. By default, this action has been assigned to the built-in tamper detection event rules.
Page 264 Chapter 3: Using the Web Interface Action Function Record snapshots to Makes a connected webcam start or stop Record Snapshots to webcam storage taking snapshots. See Webcam Storage (on page 256). Request LHX/SHX Applies the maximum cooling to the LHX/SHX Request LHX/SHX Maximum maximum cooling device.
Page 265 Chapter 3: Using the Web Interface Action Function Syslog message Makes the BCM2 automatically forward event messages to the specified syslog server. See Syslog Message (on page 268). 4. Enter the information as needed and click Create. 5. Then you can assign the newly-created action to an event rule or Event Rules and Actions schedule it.
Page 266 Chapter 3: Using the Web Interface 5. In the "Re-scheduling Period" field, specify the time interval (in minutes) at which the alert notification is resent or regenerated regularly. 6. In the "Re-scheduling Limit" field, specify the maximum number of times the alert notification is resent. Values range from 1 to infinite. 7.
Page 267 Chapter 3: Using the Web Interface 3. In the Operation field, select either one below: Start Load Shedding: Enters the load shedding mode when the  specified event occurs. Stop Load Shedding: Quits the load shedding mode when the  specified event occurs.
Page 268 If you have connected Raritan's asset strips to the BCM2, you can also configure the BCM2 to push the data to a server. Before creating this action, make sure that you have properly defined the destination servers and the data to be sent on the Data Push page.
Page 269 Chapter 3: Using the Web Interface 4. Select the action to perform - "Start recording" or "Stop recording." If "Start recording" is selected, adjust the values of the following: Number of Snapshots - the number of snapshots to be taken ...
Page 270 Chapter 3: Using the Web Interface Send Email You can configure emails to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and BCM2 placeholders. The placeholders represent information which is pulled from the BCM2 and inserted into the message.
Page 271 Chapter 3: 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. Placeholders for Custom Messages For details, see (on page 276).
Page 272 (for outlet-switching capable PDUs only). Overcurrent protector sensors, including RMS current and tripping • state. Peripheral device sensors, which can be any Raritan environmental • sensor packages connected to the BCM2, such as temperature or humidity sensors. Send Sensor...
Page 273 Chapter 3: Using the Web Interface a. Click the first to select a target component from the list. 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.
Page 274 Chapter 3: 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 BCM2 placeholders. The placeholders represent information which is pulled from the BCM2 and inserted into the message.
Page 275 Chapter 3: 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. Placeholders for Custom Messages For details, see (on page 276).
Page 276 Chapter 3: Using the Web Interface To use a different SMTP server, select the "Use custom settings" radio button. The fields for customized SMTP settings appear. For Configuring SMTP Settings information on each field, see (on page 196). 5. Select the webcam that is capturing the images you want sent in the email.
Page 277 Chapter 3: Using the Web Interface 3. In the Host fields, enter the IP address of the device(s) you want to access. This is the address to which notifications are sent by the SNMP system agent. 4. In the Port fields, enter the port number used to access the device(s).
Page 278 Chapter 3: 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 279 Chapter 3: 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 Miscellaneous be available.
Page 280 Chapter 3: Using the Web Interface 6. If "Turn Outlet On" or "Cycle Outlet" is selected in step 3, you can choose to select the "Use sequence order and delays" checkbox so that all selected outlets will follow the power-on sequence defined on the page of Outlets.
Page 281 Chapter 3: Using the Web Interface 3. In the Syslog Server field, specify the IP address to which the syslog is forwarded. 4. In the Transport Protocol field, select one of the syslog protocols: TCP, UDP or TCP+TLS. The default is UDP. Transport Next steps protocols...
Page 282 Chapter 3: Using the Web Interface Scheduling an Action An action can be regularly performed at a preset time interval instead of being triggered by a specific event. For example, you can make the BCM2 report the reading or state of a specific sensor regularly by scheduling the "Send Sensor Report"...
Page 283 Chapter 3: 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 284 Chapter 3: 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 285 Chapter 3: Using the Web Interface If intended, you can customize the email messages in this action.  2. Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination action. Send Sensor Report For details, see (on page 260).
Page 286 Chapter 3: 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 270).
Page 287 Chapter 3: Using the Web Interface 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 BCM2 will send out an email containing the specified temperature sensor readings hourly every day.
Page 288 Chapter 3: Using the Web Interface Placeholders for Custom Messages Actions of "Send email" and "Send SMS message" allow you to Send Email Send SMS customize event messages. See (on page 258) or Message (on page 262). When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions.
Page 289 Chapter 3: Using the Web Interface Placeholder Definition [AMSNUMBER] The numeric ID of an asset strip [AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to [AMSSTATE] The human readable state of an asset strip [AMSTAGID] The asset tag ID [CARDREADERID] The id of a card reader [CIRCUITCTRATING]...
Page 290 Chapter 3: Using the Web Interface Placeholder Definition [ISASSERTED] Boolean flag whether an event condition became true (1) or false (0) [LDAPERRORDESC] An 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 291 Chapter 3: Using the Web Interface Placeholder Definition [POWERMETER] The PMC power meter ID [RADIUSERRORDESC] A Radius error occurred [ROMCODE] The rom code of an attached peripheral device [SENSORREADINGUNIT] The unit of a sensor reading [SENSORREADING] The value of a sensor reading [SENSORREPORT] The formatted sensor report contents [SENSORSTATENAME]...
Page 292 Chapter 3: Using the Web Interface 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. That is, \[ or \]. Otherwise, the message sent will not display the square brackets.
Page 293 Chapter 3: Using the Web Interface 3. To make the BCM2 record the firmware update failure event in the internal log, select "System Event Log Action" in the Available Actions field. Sample Outlet-Level Event Rule In this example, we want the BCM2 to send SNMP notifications to the SNMP manager for any sensor change event of outlet 3.
Page 294 Chapter 3: Using the Web Interface Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP Notification Action. See (on page Enabling and Configuring SNMP 345). Then the SNMP notifications are sent when: Any numeric sensor's reading enters the warning or critical ...
Page 295 Chapter 3: Using the Web Interface 3. Select "Any sub-event" to include all events related to all sensors of this inlet and all thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on. 4.
Page 296 Chapter 3: Using the Web Interface Sample Environmental-Sensor-Level Event Rule This section applies to outlet-switching capable models only. In this example, we want BCM2 to activate the load shedding function when a contact closure sensor enters the alarmed state. This event rule requires creating a new action before creating the rule.
Page 297 Chapter 3: Using the Web Interface 2. In this illustration, assign the name "Contact Closure Triggered Load Shedding" to the new rule. 3. In the Event field, select "Peripheral Device Slot" to indicate we are specifying an event related to the environmental sensor package. 4.
Page 298 Chapter 3: Using the Web Interface A Note about Infinite Loop You should avoid building an infinite loop when creating event rules. The infinite loop refers to a condition where the BCM2 keeps busy because the action or one of the actions taken for a certain event triggers an identical or similar event which will result in an action triggering one more event.
Page 299: Setting Data Logging
Chapter 3: Using the Web Interface A Note about Untriggered Rules In some cases, a measurement exceeds a threshold causing the BCM2 to generate an alert. The measurement then returns to a value within the threshold, but the BCM2 does not generate an alert message for the Deassertion event.
Page 300: Configuring Data Push Settings
Chapter 3: Using the Web Interface You can also click the topmost checkbox labeled "Logging  Enabled" in the header row of each section to select all sensors of the same type. If any section's number of sensors exceeds 35, the remaining ...
Page 301 Chapter 3: Using the Web Interface Click Remove to delete the installed certificate if it is  inappropriate. 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 592).
Page 302: Monitoring Server Accessibility
Chapter 3: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the BCM2 device continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.
Page 303 Chapter 3: Using the Web Interface Field Description Number of The number of consecutive pings without consecutive any response before the monitored unsuccessful pings equipment is declared "Unreachable." for failure Valid range is 1 to 100. Wait time before The wait time before the BCM2 resumes resuming pinging pinging after the monitored equipment is after failure...
Page 304 Chapter 3: Using the Web Interface Editing or Deleting Ping Monitoring Settings You can edit the ping monitoring settings of any IT device or simply delete it if no longer needed. To modify or delete any monitored IT device: 1. Choose Device Settings > Server Reachability. 2.
Page 305 Chapter 3: Using the Web Interface Field Data entered Wait time after successful ping To make the BCM2 declare the inaccessibility of the monitored  PDU when that PDU becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data. Field Data entered Wait time after unsuccessful ping...
Page 306: Front Panel Settings
Chapter 3: Using the Web Interface 5. Select the System SNMP Notification Action. Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see Editing or Deleting a Rule/Action (on page 280). Front Panel Settings You can set up the default mode of the front panel display, and front panel functions for outlet switching, actuator control, or RCM self-test.
Page 307: Configuring The Serial Port
Note: The serial port bit-rate change is required when the BCM2 works in conjunction with Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over the serial interface. You can set diverse bit-rate settings for console and modem operations.
Page 308 Chapter 3: Using the Web Interface Options Description Force console The BCM2 attempts to recognize that the connected device is set for the console mode. Force analog modem The BCM2 attempts to recognize that the connected device is an analog modem. Force GSM modem The BCM2 attempts to recognize that the connected device is a GSM modem.
Page 309: Lua Scripts
Raritan also provides some Lua scripts examples, which you can load as needed. Note: Not all Raritan Lua script examples can apply to your BCM2 model. You should read each example's introduction before applying them. You must have the Administrator Privileges to manage Lua scripts.
Page 310 Source Code section. Therefore, do not load a new script if the current script meets your needs. 6. If you chose to load a script or Raritan's example in the previous step, its codes are then displayed in the Source Code section. Double check the codes.
Page 311 Chapter 3: Using the Web Interface Next steps: To execute the newly-added script immediately, click , or • Manually Starting or click > Start with Arguments. See Stopping a Script (on page 299). To add more scripts, first return to the scripts list by clicking "Lua •...
Page 312 Chapter 3: 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 313 Chapter 3: Using the Web Interface To return to the scripts list: Click "Lua Scripts" on the top of the page. • Or click "Lua Scripts" in the Menu. • 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 314 Chapter 3: 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 BCM2. To modify or replace a script: 1.
Page 315: Miscellaneous
Chapter 3: Using the Web Interface Miscellaneous By default, the Schroff LHX/SHX heat exchanger support and Cisco EnergyWise feature implemented on the BCM2 are disabled. Support needs to be enabled for the LHX/SHX information to appear in the BCM2 web interface. Besides, Schroff LHX/SHX support must be enabled in order for the LHX-MIB to be accessible through SNMP.
Page 316: Maintenance
Chapter 3: Using the Web Interface Field Description Polling interval Type a polling interval to determine how often the BCM2 is queried in the Cisco EnergyWise domain.  Range from 30 to 600 ms.  Default is 180 ms. EnergyWise 3.
Page 317 Chapter 3: Using the Web Interface Submenu command Refer to... Device Information Device Information (on page 306) Viewing Connected Users Connected Users (on page 311) Viewing or Clearing the Local Event Log Event Log (on page 313) Updating the BCM2 Firmware Update Firmware (on page 314) Viewing Firmware Update History...
Page 318: Device Information
Chapter 3: 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 BCM2. Tip: If the information shown on this page does not match the latest status, press F5 to reload it.
Page 319 Chapter 3: Using the Web Interface Section title Information shown Information General device information, such as model name, serial number, firmware version, hardware revision, MIB download link(s) and so on. Note that the download link of LHX-MIB is available only after enabling the Schroff Miscellaneous LHX/SHX support.
Page 320 Multiple BCM2 Devices for Sharing Ethernet Connectivity. This section explains how to identify a cascaded device on the Device Information page. Note: For detailed information on the cascading configuration and restrictions, see the , which is available from Raritan Cascading Guide website's Support page http://www.raritan.com/support/ To identify the USB-cascading status: 1.
Page 321 Chapter 3: 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 183).
Page 322 Chapter 3: 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 323: Viewing Connected Users
Chapter 3: Using the Web Interface The following diagram shows 2, indicating it is the second slave - 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 •...
Page 324 Chapter 3: Using the Web Interface 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> is displayed instead of an IP address. Client Type The interface through which the user is being connected to the BCM2.
Page 325: Viewing Or Clearing The Local Event Log
Chapter 3: 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 331).
Page 326: Updating The Bcm2 Firmware
Support page http://www.raritan.com/support/ the Raritan website's If you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading. On a multi-inlet PDU (any model with X2 or X3 suffixes), all inlets must be connected to power for the PDU to successfully upgrade its firmware.
Page 327 Chapter 3: Using the Web Interface 2. Click to select an appropriate firmware file. 3. Click Upload. A progress bar appears to indicate the upload process. 4. Once complete, information of both installed and uploaded firmware versions as well as compatibility and signature-checking results are displayed.
Page 328 Chapter 3: Using the Web Interface Upgrade Guidelines for Existing Cascading Chains You must obey the following guidelines when upgrading a chain. Otherwise, a networking issue occurs. Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10 • firmware versions in terms of the cascading feature so all devices in the cascading chain must run version 3.3.10 or later.
Page 329 . Note: Firmware downgrade in a cascading chain is NOT recommended. Consult Raritan Technical Support first if downgrade is needed. It is suggested to always stick to the same sequence as the above diagram. A Note about Firmware Upgrade Time The PDU firmware upgrade time varies from unit to unit, depending on various external and internal factors.
Page 330: Viewing Firmware Update History
Raritan. Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7/10 and Linux. In addition, an appropriate BCM2 firmware file is required in the recovery procedure.
Page 331: Bulk Configuration
Chapter 3: Using the Web Interface Bulk Configuration The Bulk Configuration feature lets you save generic settings of a configured BCM2 device to your computer. You can use this configuration file to copy common settings to other BCM2 devices of the same model Bulk Configuration Restrictions and firmware version.
Page 332 Chapter 3: Using the Web Interface Note: On startup, the BCM2 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 333 Chapter 3: Using the Web Interface Mechanical designs ignored by bulk configuration: When the source and target devices share the same technical specifications but are only different with any "mechanical designs" which are indicated in the table below, the bulk configuration remains feasible. These mechanical designs are represented by suffixes added to the model name of a BCM2 device.
Page 334 Chapter 3: Using the Web Interface Customizing Bulk Configuration Profiles A bulk profile defines which settings are downloaded/saved from the source device and which are not. The default is to apply the built-in bulk profile, which downloads all settings from the source device except for device-specific data.
Page 335 Chapter 3: Using the Web Interface Option Description Built In The setting will follow the same setting in Raritan's built-in profile.  If "Excluded" is selected in the built-in profile, this setting will be also excluded.  If "Included" is selected in the built-in profile, this setting will be also included.
Page 336 Chapter 3: Using the Web Interface Step 2: Save a bulk configuration file You must have the Administrator Privileges or "Unrestricted View Privileges" to download the configuration. 1. Log in to the source BCM2 if you have not yet. 2. Choose Maintenance > Bulk Configuration. 3.
Page 337 Chapter 3: Using the Web Interface Modifying or Removing Bulk Profiles You can modify or remove any bulk profile except for the built-in one. Choose Maintenance > Bulk Configuration. A list of profiles displays and then do one of the following. To modify an existing profile: 1.
Page 338: Backup And Restore Of Device Settings
Chapter 3: 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 a BCM2 device's settings, you should perform the Backup/Restore feature.
Page 339: Network Diagnostics
Chapter 3: Using the Web Interface 5. Wait until the BCM2 device resets and the Login page re-appears, indicating that the restore is complete. Note: On startup, the BCM2 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 340: Downloading Diagnostic Information
Raritan Technical Support. You can download the diagnostic file from the BCM2 to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation. This feature is accessible only by users with Administrative Privileges or Unrestricted View Privileges.
Page 341: Rebooting The Bcm2 Device
Chapter 3: Using the Web Interface Rebooting the BCM2 Device You can remotely reboot the BCM2 device via the web interface. Resetting the BCM2 does not interrupt the operation of connected servers because there is no loss of power to outlets. During and after the reboot, outlets that have been powered on prior to the reboot remain powered on, and outlets that have been powered off remain powered off.
Page 342: Retrieving Software Packages Information
Chapter 3: Using the Web Interface To reset the device to factory defaults: 1. Choose Maintenance > Unit Reset > 2. Click Factory Reset to reset the BCM2 to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation.
Page 343: Webcam Management
Chapter 3: Using the Web Interface 2. You can click any link to access related information or download any software package. Webcam Management The 'Webcams' menu item appears only when there is any webcam(s) connected to the BCM2, or when there are snapshots saved onto the Connecting a Logitech Webcam BCM2 already.
Page 344 Chapter 3: Using the Web Interface With a Logitech webcam connected to the BCM2, you can visually ® monitor the environment around the BCM2 via snapshots or videos captured by the webcam. Permissions required: To do... Permission(s) required Either permission below: View snapshots and videos ...
Page 345: Configuring Webcams And Viewing Live Images
Chapter 3: Using the Web Interface Configuring Webcams and Viewing Live Images To configure a webcam or view live snapshot/video sessions, choose Webcams in the Menu. 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 346 Chapter 3: Using the Web Interface Tip: The date and time shown on the BCM2 web interface are automatically converted to your computer's time zone. To avoid any time confusion, you can apply the same time zone settings as those of BCM2 to your computer.
Page 347 Chapter 3: 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. remote If configured to store snapshots on a server, the...
Page 348: Sending Links To Snapshots Or Videos
Chapter 3: Using the Web Interface To return to the Webcam Management page: Click Webcam Management on the top of the page. • Or click Webcams again in the Menu. • Sending Links to Snapshots or Videos When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session.
Page 349 Chapter 3: 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 350: Viewing And Managing Locally-Saved Snapshots
Chapter 3: Using the Web Interface How Long a Link Remains Accessible For documentation purposes, the one who opens and sends the URL of User A the Primary Standalone Live Preview window is called and the User B two recipients of the same URL link are called 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: The Primary Standalone Live Preview window remains open on User...
Page 351 Chapter 3: Using the Web Interface saved on the BCM2 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 BCM2 web interface are automatically converted to your computer's time zone.
Page 352 Chapter 3: Using the Web Interface To select all images, select the top-most 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: To download an image onto your computer, move your mouse to that •...
Page 353: Changing Storage Settings
Chapter 3: Using the Web Interface Changing Storage Settings Important: As of release 3.4.0, the BCM2 web interface only lists the snapshots stored locally on the BCM2 device, but no longer lists those saved on the 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 354 Chapter 3: Using the Web Interface Storage location Description 'Local' means the BCM2. This is the default. Local  It can store a maximum of 10 snapshots only.  The web interface can list and display all Viewing snapshots stored on the BCM2. See and Managing Locally-Saved Snapshots page 338).
Page 355 Chapter 3: Using the Web Interface Identifying Snapshots Folders on Remote Servers If saving snapshots onto a remote server, you can access those snapshots via an appropriate third-party application, such as an FTP client. All snapshots are saved as JPEG and named according to the date and time when saving the snapshots.
Page 356 Chapter 3: Using the Web Interface Number Folder name description The name of the webcam that BCM2 detects later, if an additional webcam is connected. This is the folder where the snapshots captured by the second webcam are stored.  The second webcam's default name is "Webcam 2". ...
Page 357: Chapter 4 Using Snmp
Chapter 4 Using SNMP This SNMP section helps you set up the BCM2 for use with an SNMP manager. The BCM2 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 358: Snmpv2C Notifications
Chapter 4: 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 346) ...
Page 359: Snmpv3 Notifications
Chapter 4: 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 360 Chapter 4: 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.
Page 361 Chapter 4: Using SNMP Field Description Host The IP address of the device(s) you want to access. 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.
Page 362: Downloading Snmp Mib
Chapter 4: 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 BCM2. You can download the MIBs from two different pages of the web interface.
Page 363: Snmp Gets And Sets
Chapter 4: Using SNMP SNMP Gets and Sets In addition to sending notifications, the BCM2 is able to receive SNMP get and set requests from third-party SNMP managers. Get requests are used to retrieve information about the BCM2, such • as the system location, and the current on a specific outlet.
Page 364 Chapter 4: Using SNMP Layout Opening the MIB reveals the custom objects that describe the BCM2 system at the unit level as well as at the individual-outlet level. As standard, these objects are first presented at the beginning of the file, listed under their parent group.
Page 365 Chapter 4: Using SNMP SNMP Sets and Thresholds Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which causes the BCM2 to generate a warning and send an SNMP notification when certain Sensor Threshold Settings parameters are exceeded.
Page 366: Retrieving Energy Usage
Chapter 4: Using SNMP Retrieving Energy Usage You can discover how much energy an IT device consumes by retrieving the Active Energy for the outlet this IT device is plugged into. The Active Energy values are included in the outletSensorMeasurementsTable, along with other outlet sensor readings.
Page 367: Chapter 5 Using The Command Line Interface
Chapter 5 Using the Command Line Interface This section explains how to use the command line interface (CLI) to administer a BCM2 device. CLI commands are case sensitive. In This Chapter About the Interface .................. 355 Logging in to CLI ..................356 The ? Command for Showing Available Commands .......
Page 368: Logging In To Cli
Chapter 5: 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 369: With Ssh Or Telnet
Chapter 5: Using the Command Line Interface After properly entering the password, the # or > system prompt Different CLI Modes and Prompts appears. See (on page 359) 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 370: With An Analog Modem
Chapter 5: Using the Command Line Interface With an Analog Modem The BCM2 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 BCM2 via the modem: 1.
Page 371: Different Cli Modes And Prompts
Chapter 5: 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 BCM2 device, the >...
Page 372: Querying Available Parameters For A Command
Chapter 5: 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 512).
Page 373: Showing Information
Chapter 5: Using the Command Line Interface config:# role create ? Tip: To automatically complete a command after typing part of the full command, see (on page 512). To Automatically Completing a Command re-execute one of the previous commands, see Retrieving Previous (on page 512).
Page 374 Chapter 5: 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 363).
Page 375 Chapter 5: 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 362). 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 376 Chapter 5: Using the Command Line Interface Interface Description eth2 Show the IPv4 or IPv6 configuration of the ETH2 interface. (BCM2-iX7) wireless Show the IPv4 or IPv6 configuration of the WIRELESS interface. bridge Show the IPv4 or IPv6 configuration of the BRIDGE interface.
Page 377 Chapter 5: Using the Command Line Interface Interface Description wireless Show the WIRELESS interface's non-IP settings. bridge Show the BRIDGE interface's non-IP settings. Show the non-IP settings of all interfaces. Tip: You can also type the command without adding this option "all" to get the same data. That show network interface Network Service Settings This command shows the network service settings only, including the...
Page 378: Date And Time Settings
Chapter 5: Using the Command Line Interface Date and Time Settings This command shows the current date and time settings on the BCM2 device. show time To show detailed information, add the parameter "details" to the end of the command. show time details Default Measurement Units This command shows the default measurement units applied to the...
Page 379: Environmental Sensor Information
Chapter 5: 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: <n>...
Page 380: Environmental Sensor Package Information
Chapter 5: 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 BCM2 web interface. Displayed information: Without the parameter "details," only the sensor ID, sensor type and •...
Page 381: Actuator Information
Chapter 5: 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 382: Environmental Sensor Threshold Information
Chapter 5: Using the Command Line Interface Environmental Sensor Threshold Information This command syntax shows the specified environmental sensor's threshold-related information. show sensor externalsensor <n> To show detailed information, add the parameter "details" to the end of the command. show sensor externalsensor <n> details External sensor 3 (Temperature): Reading: 31.8 deg C State:...
Page 383: Environmental Sensor Default Thresholds
Chapter 5: Using the Command Line Interface Displayed information: • Without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed. With the parameter "details," more sensor information is displayed, •...
Page 384: Security Settings
Chapter 5: Using the Command Line Interface Without the parameter "details," only the default upper and lower • thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed. With the parameter "details," the threshold range is displayed in •...
Page 385: Authentication Settings
Chapter 5: Using the Command Line Interface Authentication Settings General authentication settings: This command displays the authentication settings of the BCM2, 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 386: Existing User Profiles
Chapter 5: 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 387: Existing Roles
Chapter 5: 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 388: Asset Strip Settings
Chapter 5: 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 389: Blade Extension Strip Settings
Chapter 5: 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 390: Event Log
Chapter 5: Using the Command Line Interface Event Log The command used to show the event log begins with show eventlog. limit class You can add either the parameters or both to show specific events. Show the last 30 entries: show eventlog Show a specific number of last entries in the event log: show eventlog limit <n>...
Page 391: Wireless Lan Diagnostic Log
Internal or external sensor events, such as state changes of any sensors. serverMonitor Server-monitoring records, such as a server being declared reachable or unreachable. assetManagement Raritan asset management events, such as asset tag connections or disconnections. Schroff LHX/SHX heat exchanger events. ® modem Modem-related events.
Page 392 Chapter 5: 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 393: Command History
Chapter 5: 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 394 Chapter 5: Using the Command Line Interface Example 1 - Basic Security Information show security The diagram shows the output of the command. Example 2 - In-Depth Security Information show security details More information is displayed when typing the command.
Page 395: Clearing Information
Chapter 5: Using the Command Line Interface Example 3 - Basic PDU Information show pdu The diagram shows the output of the command. Example 4 - In-Depth PDU Information show pdu details More information is displayed when typing the command. Displayed information varies depending on the model you purchased.
Page 396: Clearing Event Log
Chapter 5: 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 397: Entering Configuration Mode
Chapter 5: 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 398: Network Configuration Commands
Chapter 5: Using the Command Line Interface Network Configuration Commands network A network configuration command begins with . A number of network settings can be changed through the CLI, such as the IP address, transmission speed, duplex mode, and so on. Configuring IPv4 Parameters network ipv4 An IPv4 configuration command begins with...
Page 399 Chapter 5: Using the Command Line Interface Mode Description static The IPv4 configuration mode is set to static IP address. 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>...
Page 400 Chapter 5: 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 BCM2 device. config:# network ipv4 interface <ETH> address <ip address> Variables: ethernet wireless...
Page 401 Chapter 5: 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 BCM2 and devices in the other subnet.
Page 402 Chapter 5: Using the Command Line Interface config:# network ipv4 staticRoutes modify <route_ID> <dest-2> interface <ETH> Variables: <dest-1> is a combination of the IP address and subnet mask of the • IP address/subnet mask other subnet. The format is • <hop>...
Page 403 Chapter 5: 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 404 Chapter 5: Using the Command Line Interface Interface Description wireless Determine the IPv6 preferred host name of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 preferred host name of the BRIDGE interface (that is, bridging mode). <name> is a host name which: •...
Page 405 Chapter 5: Using the Command Line Interface Interface Description bridge Determine the IPv6 address of the BRIDGE interface (that is, the bridging mode). <ip address> is the IP address being assigned to your BCM2 device. • 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 406 Chapter 5: Using the Command Line Interface config:# network ipv6 staticRoutes add <dest-1> interface <ETH> Delete an existing static route: config:# network ipv6 staticRoutes delete <route_ID> Modify an existing static route: config:# network ipv6 staticRoutes modify <route_ID> <dest-2> <hop> -- OR -- config:# network ipv6 staticRoutes modify <route_ID>...
Page 407 <ip address> is the IP address of the DNS server. • <suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching for any device via BCM2. For raritan.com example, <suffix1> can be , and <suffix2> can be legrand.com .
Page 408 Chapter 5: 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 409 Chapter 5: Using the Command Line Interface Changing the LAN Interface Speed This command determines the LAN interface speed. config:# network ethernet <ETH> speed <option> Variables: ethernet eth1 or eth2 <ETH> is one of the options -- , which depends •...
Page 410 Chapter 5: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. network ethernet <ETH> duplexMode <mode> config:# Variables: ethernet eth1 or eth2 <ETH> is one of the options -- , which depends •...
Page 411 Chapter 5: 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 current networking mode is not wireless, the SSID, PSK and BSSID values are not applied until the networking mode is changed to...
Page 412 Chapter 5: Using the Command Line Interface Setting the PSK If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command. config:# network wireless PSK <psk> Variables: <psk> is a string or passphrase that consists of: •...
Page 413 Chapter 5: Using the Command Line Interface Setting EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, password, and CA certificate. Determine the outer authentication protocol: config:# network wireless eapOuterAuthentication <outer_auth>...
Page 414 Chapter 5: Using the Command Line Interface config:# network wireless allowConnectionWithIncorrectClock <option3> Variables: PEAP The value of <outer_auth> is because BCM2 only supports • Protected Extensible Authentication Protocol (PEAP) as the outer authentication. MSCHAPv2 • The value of <inner_auth> is because BCM2 only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.
Page 415 Chapter 5: Using the Command Line Interface Option Description false The wireless network connection is NOT successfully established when the BCM2 finds that the TLS certificate is not valid due to incorrect system time. EAP CA Certificate Example This section provides a CA certificate example only. Your CA certificate contents should be different from the contents displayed in this example.
Page 416 Chapter 5: Using the Command Line Interface MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/ A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+z4IBO 6. Paste the contents in the terminal. 7. Press Enter. 8. Verify whether the system shows the following command prompt, indicating the provided CA certificate is valid.
Page 417 Chapter 5: 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 418 Chapter 5: 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 419 Chapter 5: 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 420 Chapter 5: 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 421 Chapter 5: 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 •...
Page 422 Chapter 5: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication <auth_method> Variables: passwordOnly publicKeyOnly • <option> is one of the options: passwordOrPublicKey Option Description passwordOnly Enables the password-based login only.
Page 423 Chapter 5: Using the Command Line Interface Enabling or Disabling SNMP v3 This command enables or disables the SNMP v3 protocol. config:# network services snmp v3 <option> Variables: enable disable • <option> is one of the options: Option Description enable The SNMP v3 protocol is enabled.
Page 424 Chapter 5: Using the Command Line Interface Setting the sysName Value This command sets the SNMP MIB-II sysName value. config:# network services snmp sysName <value> Variables: • <value> is a string comprising 0 to 255 alphanumeric characters. Setting the sysLocation Value This command sets the SNMP MIB-II sysLocation value.
Page 425 Chapter 5: Using the Command Line Interface Enabling or Disabling the Read-Only Mode This command enables or disables the read-only mode for the Modbus agent. config:# network services modbus readonly <option> Variables: true false • <option> is one of the options: Option Description true...
Page 426: Time Configuration Commands
Chapter 5: Using the Command Line Interface Examples This section illustrates several network configuration examples. Example 1 - Networking Mode The following command enables the wired networking mode. config:# network mode wired Example 2 - Enabling Both IP Protocols The following command determines that both IPv4 and IPv6 protocols are enabled.
Page 427 Chapter 5: Using the Command Line Interface Determining the Time Setup Method This command determines the method to configure the system date and time. config:# time method <method> Variables: manual • <method> is one of the time setup options: Mode Description manual The date and time settings are customized.
Page 428 Chapter 5: 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 429 Chapter 5: Using the Command Line Interface Customizing the Date and Time If intending to manually configure the date and time, use the following CLI commands to specify them. Note: You shall set the time configuration method to "manual" prior to customizing the date and time.
Page 430 Chapter 5: 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 savings time is applied to the time settings.
Page 431: Checking The Accessibility Of Ntp Servers
Chapter 5: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your BCM2 and then shows the result. For instructions on Setting NTP Parameters specifying NTP servers via CLI, see (on page 416).
Page 432 Chapter 5: 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 433 Chapter 5: Using the Command Line Interface accept, drop reject • <policy> is one of the options: 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 434 Chapter 5: 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 435 Chapter 5: Using the Command Line Interface insertAbove insertBelow • <insert> is one of the options: 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 436 Chapter 5: 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: •...
Page 437 Chapter 5: 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 438 Chapter 5: 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 439 Chapter 5: 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 440 Chapter 5: Using the Command Line Interface Login Limitation The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before forcing a user to log out. security loginLimits A login limitation command begins with You can combine multiple commands to modify various login limitation Multi-Command Syntax...
Page 441 Chapter 5: Using the Command Line Interface Password Aging Interval This command determines how often the password should be changed. config:# security loginLimits passwordAgingInterval <value> Variables: <value> is a numeric value in days set for the password aging • interval. The interval ranges from 7 to 365 days. Idle Timeout This command determines how long a user can remain idle before that user is forced to log out of the BCM2 web interface or CLI.
Page 442 Chapter 5: 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 Multi-Command Syntax different parameters at a time.
Page 443 Chapter 5: 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 444 Chapter 5: Using the Command Line Interface Option Description disable No numeric character is required. Special Character Requirement This command determines whether a strong password includes at least a special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables: enable disable <option> is one of the options: •...
Page 445 Chapter 5: Using the Command Line Interface Modifying Role-Based Access Control Parameters There are different commands for modifying role-based access control parameters. IPv4 commands • Enable or disable the IPv4 role-based access control feature: config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>...
Page 446 Chapter 5: Using the Command Line Interface Tip: You can combine both commands to modify all role-based access control parameters at a time. See (on page Multi-Command Syntax 504). Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules. An IPv4 role-based access control command for managing rules •...
Page 447 Chapter 5: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> <insert> <rule_number> Variables: <start_ip> is the starting IP address. • <end_ip> is the ending IP address. • <role> is the role for which you want to create an access control •...
Page 448 Chapter 5: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> Modify an IPv4 rule's role: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy>...
Page 449 Chapter 5: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables: • <rule_number> is the number of the existing rule that you want to modify. • <start_ip> is the starting IP address. <end_ip>...
Page 450 Chapter 5: Using the Command Line Interface Enabling or Disabling Front Panel Outlet Switching This section applies to outlet-switching capable models only. The following CLI commands control whether you can turn on or off an outlet by operating the front panel display. To enable the front panel outlet control feature: config:# security frontPanelPermissions add switchOutlet...
Page 451 Chapter 5: 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 452: User Configuration Commands
Chapter 5: 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 453 Chapter 5: 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 454 Chapter 5: 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 455 Chapter 5: 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 BCM2 device only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: <name>...
Page 456 Chapter 5: 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 Multi-Command Syntax modify the SNMPv3 parameters at a time. See (on page 504).
Page 457 Chapter 5: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Variables: <name> is the name of the user whose settings you want to change. • true false • <option3> is one of the options: Option Description true Authentication passphrase is identical to the password.
Page 458 Chapter 5: Using the Command Line Interface Determine the privacy passphrase: config:# user modify <name> privacyPassPhrase <privacy_passphrase> Variables: <name> is the name of the user whose settings you want to change. • • <privacy_passphrase> is a string used as a privacy passphrase, comprising 8 to 32 ASCII printable characters.
Page 459 Chapter 5: Using the Command Line Interface Changing the Role(s) This command changes the role(s) of a specific user. config:# user modify <name> roles <roles> Variables: • <name> is the name of the user whose settings you want to change. •...
Page 460 Chapter 5: Using the Command Line Interface Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2> Variables: <name> is the name of the user whose settings you want to change. • meter feet • <option2> is one of the options: Option Description meter...
Page 461 Chapter 5: Using the Command Line Interface d. Press Enter. To remove an existing SSH public key: 1. Type the same command as shown above. 2. When the system prompts you to input the contents, press Enter without typing or pasting anything. Example The following procedure illustrates how to change the SSH public key for the user "assistant."...
Page 462 Chapter 5: Using the Command Line Interface config:# password 3. Type the existing password and press Enter when the following prompt appears. Current password: 4. Type the new password and press Enter when the following prompt appears. Enter new password: 5.
Page 463 Chapter 5: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2> Variables: meter feet <option2> is one of the options: • Option Description meter This option displays the length or height in meters. feet This option displays the length or height in feet. Set the default pressure unit: config:# user defaultpreferences preferredPressureUnit <option3>...
Page 464 Chapter 5: Using the Command Line Interface Example 1 - Creating a User Profile The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin Results: • A new user profile "May" is created. The new user profile is enabled.
Page 465: Role Configuration Commands
Chapter 5: Using the Command Line Interface Role Configuration Commands role A role configuration command begins with Creating a Role This command creates a new role, with a list of semicolon-separated privileges assigned to the role. config:# role create <name> <privilege1>;<privilege2>;<privilege3>... If a specific privilege contains any arguments, that privilege should be followed by a colon and the argument(s).
Page 466 Chapter 5: Using the Command Line Interface Privilege Description changeAuthSettings Change Authentication Settings changeDataTimeSettings Change Date/Time Settings changeExternalSensorsConfiguration Change Peripheral Device Configuration changeLhxConfiguration Change LHX/SHX Configuration changeModemConfiguration Change Modem Configuration changeNetworkSettings Change Network Settings changePassword Change Own Password changePduConfiguration Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration changeSecuritySettings...
Page 467 Chapter 5: Using the Command Line Interface * The "switchActuator" privilege requires an argument that is separated with a colon. The argument could be: • All actuators, that is, switchActuator:all An actuator's ID number. For example: • switchActuator:1 switchActuator:2 switchActuator:3 A list of comma-separated ID numbers of different actuators.
Page 468 Chapter 5: Using the Command Line Interface Modifying a Role You can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify <name> description "<description>" Variables: • <name> is a string comprising up to 32 ASCII printable characters. <description>...
Page 469 Chapter 5: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables: • <name> is a string comprising up to 32 ASCII printable characters. <privilege1>, <privilege2>, <privilege3> and the like are names of the • privileges assigned to the role. Separate each privilege with a All Privileges semi-colon.
Page 470: Authentication Commands
Chapter 5: Using the Command Line Interface Deleting a Role This command deletes an existing role. config:# role delete <name> Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results: •...
Page 471 Chapter 5: Using the Command Line Interface config:# authentication type <option1> useLocalIfRemoteUnavailable <option2> Note: You cannot enable or disable the option of switching to local authentication without determining the authentication type in the CLI. Therefore, always type "authentication type <option1>" when setting up "useLocalIfRemoteUnavailable".
Page 472 Chapter 5: Using the Command Line Interface Adding an LDAP Server Adding an LDAP server requires the entry of quite a lot of parameters, such as the server's IP address, TCP port number, Base DN and so on. You can repeat the following CLI command to add more than one LDAP server.
Page 473 Chapter 5: Using the Command Line Interface Type Description Microsoft Active Directory activeDirectory none startTls • <security> is one of the security options: Type Description No security none StartTLS startTls anonymouseBind <bind_type> is one of the bind options: , or •...
Page 474 Chapter 5: Using the Command Line Interface config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> bindDN <bind_DN> "Optional Parameters" table: Parameters To configure User search subfilter userSearchSubfilter <filter> bind DN bindDN <bind_DN>  The system will prompt you to enter and re-confirm the bind password after adding this parameter to the command.
Page 475  The "verifyServerCertificate" parameter is added to the  command and set to "true." authentication ldap add ldap.raritan.com 389 openldap startTls ... config:# inetOrgPerson verifyServerCertificate true b. The system now prompts you to enter the certificate's content. c. Type or copy the certificate's content in the CLI and press Enter.
Page 476 Chapter 5: Using the Command Line Interface config:# authentication ldap add op-ldap.raritan.com 389 openldap none authenticatedBind cn=Manager,dc=raritan,dc=com uid inetOrgPerson bindDN user@raritan.com b. The system prompts you to specify the bind DN password. c. Type the password and press Enter. d. Re-type the same password.
Page 477 Chapter 5: 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 478 Chapter 5: 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 479 Chapter 5: 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: <server_num>...
Page 480 Chapter 5: 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. •...
Page 481 Chapter 5: 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 482: Environmental Sensor Configuration Commands
Chapter 5: 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 •...
Page 483 Specifying the CC Sensor Type Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party or Raritan's detectors/switches. You must specify the type of connected detector/switch for proper operation. Use this command when you need to specify the sensor type.
Page 484 Chapter 5: 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 •...
Page 485 Chapter 5: 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 486 Chapter 5: 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 DX-PIR presence detector. config:# externalsensor <n> alarmedToNormalDelay <time> Variables: • <n> is the ID number of the environmental sensor that you want to configure.
Page 487: Configuring Environmental Sensors' Default Thresholds
Chapter 5: 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 488 Chapter 5: 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 489: Sensor Threshold Configuration Commands
Chapter 5: 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 490 Chapter 5: Using the Command Line Interface config:# sensor outlet <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an outlet sensor: config:# sensor outlet <n>...
Page 491 Chapter 5: Using the Command Line Interface Option Description A numeric Sets a value for the specified threshold of a value specific outlet sensor and enables this threshold at the same time. <hy_value> is a numeric value that is assigned to the hysteresis for •...
Page 492 Chapter 5: Using the Command Line Interface config:# sensor inlet <n> <sensor type> assertionTimeout <as_value> Variables: <n> is the number of the inlet that you want to configure. For a • single-inlet PDU, <n> is always the number 1. • <sensor type>...
Page 493 Chapter 5: Using the Command Line Interface • <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert" and Deassertion the specified inlet sensor. See Hysteresis (on page 110). • <as_value> is a numeric value that is assigned to the assertion "To Assert"...
Page 494 Chapter 5: Using the Command Line Interface config:# sensor inletpole <n> <p> <sensor type> assertionTimeout <as_value> Variables: <n> is the number of the inlet whose pole sensors you want to • configure. • <p> is the label of the inlet pole that you want to configure. Pole Label Current sensor...
Page 495 Chapter 5: Using the Command Line Interface • <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert" and Deassertion the specified inlet pole sensor. See Hysteresis (on page 110). • <as_value> is a number in samples that is assigned to the assertion "To Assert"...
Page 496 Chapter 5: Using the Command Line Interface config:# sensor ocp <n> <sensor type> assertionTimeout <as_value> Variables: <n> is the number of the overcurrent protector that you want to • configure. • <sensor type> is one of the following sensor types: Sensor type Description current...
Page 497 Chapter 5: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperCritical <option> Set the Upper Warning threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an environmental sensor: config:# sensor externalsensor <n>...
Page 498 Chapter 5: Using the Command Line Interface enable disable <option> is one of the options: or a numeric value. • Option Description enable Enables the specified threshold for a specific environmental sensor. disable Disables the specified threshold for a specific environmental sensor.
Page 499 Chapter 5: Using the Command Line Interface config:# sensor inlet 1 current upperWarning 20 lowerWarning 12 Results: The Upper Warning threshold for the inlet 1 RMS current is set to • 20A. It also enables the upper warning threshold if this threshold has not been enabled yet.
Page 500: Actuator Configuration Commands
Chapter 5: Using the Command Line Interface Actuator Configuration Commands actuator An actuator configuration command begins with . 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 504).
Page 501: Server Reachability Configuration Commands
Chapter 5: Using the Command Line Interface Note: To specify the Z coordinate using the rack units, see Setting the Z Coordinate Format for Environmental Sensors. • <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes. Example - Actuator Naming The following command assigns the name "Door lock"...
Page 502 Chapter 5: 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 503 Chapter 5: 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 504 Chapter 5: 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 •...
Page 505: Energywise Configuration Commands
Chapter 5: Using the Command Line Interface EnergyWise Configuration Commands energywise An EnergyWise configuration command begins with Enabling or Disabling EnergyWise This command syntax determines whether the Cisco EnergyWise ® endpoint implemented on the BCM2 device is enabled. config:# energywise enabled <option> Variables: true false...
Page 506 Chapter 5: Using the Command Line Interface Specifying the EnergyWise Secret This command syntax specifies the password (secret) to enter the Cisco ® EnergyWise domain. config:# energywise secret <password> Variables: • <password> is a string comprising up to 127 ASCII printable characters.
Page 507: Asset Management Commands
Chapter 5: Using the Command Line Interface Example - Setting Up EnergyWise The following command sets up two Cisco EnergyWise-related features. ® config:# energywise enabled true port 10288 Results: The EnergyWise feature implemented on the BCM2 is enabled. • The UDP port is set to 10288. •...
Page 508 Chapter 5: Using the Command Line Interface Specifying the Number of Rack Units This command syntax specifies the total number of rack units on an asset strip connected to the BCM2 device. config:# assetStrip <n> numberOfRackUnits <number> Note: A rack unit refers to a tag port on the asset strips. Variables: <n>...
Page 509 Chapter 5: Using the Command Line Interface Specifying the Rack Unit Numbering Offset This command syntax specifies the starting number of rack units on the asset strips connected to the BCM2 device. config:# assetStrip <n> rackUnitNumberingOffset <number> Variables: <n> is the number of the FEATURE port where the selected asset •...
Page 510 Chapter 5: Using the Command Line Interface Setting LED Colors for Connected Tags This command syntax sets the LED color for all rack units on the asset strip #1 to indicate the presence of a connected asset tag. config:# assetStrip <n> LEDColorForConnectedTags <color> Variables: <color>...
Page 511 Chapter 5: Using the Command Line Interface Naming a Rack Unit This command syntax assigns or changes the name of the specified rack unit on the specified asset strip. config:# rackUnit <n> <rack_unit> name "<name>" Variables: <n> is the number of the FEATURE port where the selected asset •...
Page 512 Chapter 5: Using the Command Line Interface Mode Description manual This option enables selection of a different LED color and LED mode for the specified rack unit. Setting an LED When this option is selected, see Color for a Rack Unit Setting (on page 500) and an LED Mode for a Rack Unit...
Page 513 Chapter 5: Using the Command Line Interface Setting an LED Mode for a Rack Unit This command syntax sets the LED mode for a specific rack unit on the specified asset strip. You need to set a rack unit's LED mode only when the LED operation mode of this rack unit has been set to "manual."...
Page 514: Serial Port Configuration Commands
CONSOLE / MODEM on the BCM2 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. If you change the baud rate dynamically after the connection has been made, you must reset the BCM2 or power cycle the connected device for proper communications.
Page 515 Chapter 5: Using the Command Line Interface Forcing the Device Detection Mode This command forces the serial port on the BCM2 to enter a specific device detection mode. config:# serial deviceDetectionType <mode> Variables: automatic forceConsole • <mode> is one of the detection modes: forceAnalogModem, forceGsmModem Option...
Page 516: Multi-Command Syntax
Chapter 5: Using the Command Line Interface Note: Serial Port options are hidden for PMMC controller models Multi-Command Syntax To shorten the configuration time, you can combine various configuration commands in one command to perform all of them at a time. All combined commands must belong to the same configuration type, such network user modify...
Page 517: Actuator Control Operations
Chapter 5: Using the Command Line Interface Example 3 - 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. The PSK value is set to encryp_key.
Page 518: Switching On An Actuator
Chapter 5: Using the Command Line Interface Switching On an Actuator This command syntax turns on one actuator. control actuator <n> on To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation. control actuator <n>...
Page 519: Example - Turning On A Specific Actuator
Chapter 5: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: Type y to confirm the operation, OR  Type n to abort the operation  Example - Turning On a Specific Actuator The following command turns on the actuator whose ID number is 8.
Page 520: Restarting The Pdu
Chapter 5: Using the Command Line Interface Restarting the PDU This command restarts the BCM2 device. It is not a factory default reset. To restart the BCM2 device: 1. Ensure you have entered administrator mode and the # prompt is displayed.
Page 521: Resetting To Factory Defaults
Chapter 5: Using the Command Line Interface -- OR -- reset activeEnergy outlet <outlet_n> /y If you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort it. Variables: •...
Page 522: Quitting Diagnostic Mode
Chapter 5: Using the Command Line Interface Quitting Diagnostic Mode To quit the diagnostic mode, use this command: diag> exit The # or > prompt appears after pressing Enter, indicating that you have Different CLI Modes and entered the administrator or user mode. See Prompts (on page 359).
Page 523 Chapter 5: 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 524: Retrieving Previous Commands
Chapter 5: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your BCM2 device and a network host. diag> traceroute <host> Variables: • <host> is the name or IP address of the host you want to trace. Example - Ping Command The following command checks the network connectivity of the host 192.168.84.222 by sending the ICMP ECHO_REQUEST message to the...
Page 525: Logging Out Of Cli
Chapter 5: 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 526: Chapter 6 Using Scp Commands
Chapter 6 Using SCP Commands You can perform a Secure Copy (SCP) command to update the BCM2 firmware, do bulk configuration, or back up and restore the configuration. In This Chapter Firmware Update via SCP ............... 514 Bulk Configuration via SCP ..............515 Backup and Restore via SCP ..............
Page 527: Bulk Configuration Via Scp
Chapter 6: Using SCP Commands SCP example: scp pdu-px2-030000-41270.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 528: Backup And Restore Via Scp
Chapter 6: Using SCP Commands 3. The system copies the configuration included in the file "bulk_config.txt" to another BCM2, and displays the following message. Starting restore operation. The connection will be closed now. SCP examples: Save operation: • scp admin@192.168.87.50:/bulk_config.txt Copy operation: •...
Page 529: Downloading Diagnostic Data Via Scp
Chapter 6: Using SCP Commands To restore the settings via SCP: 1. Type the following SCP command and press Enter. scp backup_settings.txt <user name>@<device ip>:/settings_restore <user name> is the "admin" or any user profile with the  administrator privileges. <device ip> is the IP address of the BCM2 whose settings you ...
Page 530 Chapter 6: Using SCP Commands Scenario 1: Use the default SCP port and default filename  SSH/SCP port is the default (22), and the accessed BCM2 is a standalone device.  The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot (.) in the end of the SCP command as shown below.
Page 531 Chapter 6: Using SCP Commands If you do NOT specify a new filename in the command, such as  Scenario 1 or 2, the downloaded file's default name is "diag-data.zip." If you specify a new filename in the command, such as Scenario 3 ...
Page 532: Appendix A Resetting To Factory Defaults
Appendix A Resetting to Factory Defaults You can use either the reset button or the command line interface (CLI) to reset the BCM2. Important: Exercise caution before resetting the BCM2 to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.
Page 533: Using The Cli Command
Appendix A: Resetting to Factory Defaults Using the CLI Command The Command Line Interface (CLI) provides a reset command for restoring the BCM2 to factory defaults. For information on CLI, see Using the Command Line Interface (on page 355). To reset to factory defaults after logging in to the CLI: Logging in to CLI 1.
Page 534: Appendix B Ldap Configuration Illustration
Configure LDAP authentication on the BCM2 device d. Configure roles on the BCM2 device Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
Page 535: Step B. Configure User Groups On The Ad Server
Appendix B: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups (roles) for the BCM2 on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: BCM_Admin BCM_User •...
Page 536 Appendix B: LDAP Configuration Illustration Field/setting Do this... 192.168.56.3.  Without the encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the encryption is enabled. Copy settings from Leave the checkbox deselected unless the new LDAP server's existing LDAP server...
Page 537: Step D. Configure Roles On The Bcm2
Appendix B: LDAP Configuration Illustration Step D. Configure Roles on the BCM2 A role on the BCM2 determines the system permissions. You must create the roles whose names are identical to the user groups created for the BCM2 on the AD server or authorization will fail. Therefore, we BCM_User BCM_Admin will create the roles named...
Page 538 Appendix B: LDAP Configuration Illustration 3. Type a description for the BCM_Admin role in the Description field. In this example, we type "The role includes all privileges" to describe the role. 4. Click the Privileges tab to select the Administrator permission. The Administrator permission allows users to configure or change all BCM2 settings.
Page 539: Appendix C Updating The Ldap Schema
Appendix C Updating the LDAP Schema In This Chapter Returning User Group Information ............527 Setting the Registry to Permit Write Operations to the Schema ... 528 Creating a New Attribute ................. 528 Adding Attributes to the Class ..............529 Updating the Schema Cache ..............
Page 540: Setting The Registry To Permit Write Operations To The Schema
Appendix C: 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 541: Adding Attributes To The Class
Appendix C: 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. rciusergroup 4. Type in the Common Name field. rciusergroup 5. Type in the LDAP Display Name field. 1.3.6.1.4.1.13742.50 6.
Page 542 Appendix C: 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 543: Updating The Schema Cache
Appendix C: 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 544 Appendix C: 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 545 Appendix C: 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 546: Appendix D Radius Configuration Illustration
If a user has multiple roles, configure multiple standard attributes • for this user. • The syntax of a standard attribute is: Raritan:G{role-name} NPS Standard Attribute Illustration For configuration on NPS, see page 535). FreeRADIUS Standard Attribute For configuration on FreeRADIUS, see Illustration (on page 553).
Page 547: Nps Standard Attribute Illustration
Appendix D: RADIUS Configuration Illustration NPS Standard Attribute Illustration standard attribute To configure Windows 2008 NPS with the , you must: Step A: Add Your BCM2 as a RADIUS a. Add your BCM2 to NPS. See Client (on page 536). b.
Page 548 Appendix D: RADIUS Configuration Illustration Step A: Add Your BCM2 as a RADIUS Client The RADIUS implementation on a BCM2 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 549 Appendix D: 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 BCM2. In this example, they are 1812 and 1813. Then close this dialog.
Page 550 Appendix D: 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 BCM2 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 551 Appendix D: 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 BCM2. 5. Click OK.
Page 552 Appendix D: 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 BCM2 Connection request forwarding method • Authentication method(s) • •...
Page 553 Appendix D: 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 554 Appendix D: RADIUS Configuration Illustration You can leave the "Type of network access server" field to the  default -- Unspecified.
Page 555 Appendix D: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 556 Appendix D: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the BCM2 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 557 Appendix D: 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 BCM2 uses "CHAP" in this example ...
Page 558 Appendix D: RADIUS Configuration Illustration Note: If your BCM2 uses PAP, then select "PAP."...
Page 559 Appendix D: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
Page 560 Appendix D: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
Page 561 Appendix D: 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 562 Appendix D: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the BCM2. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
Page 563 Appendix D: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
Page 564 Appendix D: RADIUS Configuration Illustration 15. Click Next to continue.
Page 565: Freeradius Standard Attribute Illustration
Appendix D: 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 566: Vendor-Specific Attributes
Appendix D: 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 567 Appendix D: RADIUS Configuration Illustration Step A: Add Your BCM2 as a RADIUS Client The RADIUS implementation on a BCM2 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 568 Appendix D: 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 BCM2. In this example, they are 1812 and 1813. Then close this dialog.
Page 569 Appendix D: 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 BCM2 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 570 Appendix D: 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 BCM2. 5. Click OK.
Page 571 Appendix D: 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 BCM2 Connection request forwarding method • Authentication method(s) • •...
Page 572 Appendix D: 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 573 Appendix D: RADIUS Configuration Illustration You can leave the "Type of network access server" field to the  default -- Unspecified.
Page 574 Appendix D: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 575 Appendix D: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the BCM2 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 576 Appendix D: 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 BCM2 uses "CHAP" in this example ...
Page 577 15. Click Configure Attribute, and then: a. Type in the "Vendor-assigned attribute number" field. b. Select String in the "Attribute format" field. Raritan:G{Admin User SystemTester} c. Type in the "Attribute value" field. In this example, three roles 'Admin,' 'User' and...
Page 578: 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. Add all user data, including user names, passwords, and roles Presumptions in the illustration: •...
Page 579: Ad-Related Configuration
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 ("). steve Cleartext-Password := "test123" Raritan-PDU-User-Roles = "Raritan:G{Admin User SystemTester}" AD-Related Configuration When RADIUS authentication is intended, make sure you also configure...
Page 580 Appendix D: RADIUS Configuration Illustration 2. Right-click NPS (Local) and select "Register server in Active Directory." 3. Click OK, and then OK again. To grant BCM2 users remote access permission: 1. Open Active Directory Users and Computers.
Page 581 Appendix D: 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 582 Appendix D: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
Page 583: Appendix E Additional Bcm2 Information
Sensor Threshold Settings ..............576 Altitude Correction Factors ..............584 Ways to Probe Existing User Profiles ............. 585 Raritan Training Website ................. 585 Role of a DNS Server ................585 Installing the USB-to-Serial Driver (Optional) ........586 Initial Network Configuration via CLI ............587 Device-Specific Settings ................
Page 584: Reserving Ip Addresses In Dhcp Servers
Appendix E: Additional BCM2 Information Note: The RJ45-to-DB9 adapter/cable used for connecting modems CANNOT be used to connect the iX7 to a computer. See RJ45-to-DB9 ™ Cable Requirements for Computer Connections (for iX7 Only). ™ Reserving IP Addresses in DHCP Servers The BCM2 uses its serial number as the client identifier in the DHCP request.
Page 585: Reserving Ip In Windows
Appendix E: Additional BCM2 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 572).
Page 586: Reserving Ip In Linux
Appendix E: Additional BCM2 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. Use an interface's original client identifier without converting it into •...
Page 587 Appendix E: Additional BCM2 Information Interface Client identifier conversion ETH2 PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45 54 48 32 (BCM2-iX7)  The suffix comprising the dash symbol and the word "ETH2" is also converted. WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53...
Page 588: Sensor Threshold Settings
Appendix E: Additional BCM2 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 589 Appendix E: Additional BCM2 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 590 Appendix E: Additional BCM2 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 591: To Assert" And Assertion Timeout
Appendix E: Additional BCM2 Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the BCM2 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 BCM2 to assert.
Page 592 Appendix E: Additional BCM2 Information In the threshold settings, the Assertion Timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must remain in the "worse" new state before the BCM2 triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the BCM2 does NOT assert the worse state.
Page 593: To De-Assert" And Deassertion Hysteresis
Appendix E: Additional BCM2 Information "To De-assert" and Deassertion Hysteresis After the BCM2 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 594 Appendix E: Additional BCM2 Information...
Page 595 Appendix E: Additional BCM2 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 596: Altitude Correction Factors
Altitude Correction Factors If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device can serve as an altitude correction factor. That is, the reading of the differential air pressure sensor will be multiplied by the correction factor to get a correct reading.
Page 597: Ways To Probe Existing User Profiles
Webcam-Live-Preview sessions, which show a list of associated user names. Raritan Training Website Raritan offers free training materials for various Raritan products on the Raritan training website http://www.raritantraining.com . The Raritan products introduced on this website include intelligent PDU, KVM, EMX, BCM, and CommandCenter Secure Gateway (CC-SG).
Page 598: Installing The Usb-To-Serial Driver (Optional)
The BCM2 can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Serial Console" is required for Microsoft ® Windows operating systems. ® Download the Windows driver for USB serial console from the Raritan Support page http://www.raritan.com/support/ website's ). The dominion-serial-setup-<n>.exe downloaded driver's name is , where <n>...
Page 599: Initial Network Configuration Via Cli
3. In the communications program, press Enter to send a carriage return to the BCM2. 4. The BCM2 prompts you to log in. Both user name and password are case sensitive. a. Username: admin b. Password: raritan (or a new password if you have changed it).
Page 600 Appendix E: Additional BCM2 Information 5. If prompted to change the default password, change or ignore it. To change it, follow onscreen instructions to type your new  password. To ignore it, simply press Enter.  6. The # prompt appears. 7.
Page 601 Appendix E: Additional BCM2 Information • Static IP configuration: To set Use this command Static IPv4 or network <ipvX> interface <ETH> IPv6 address address <ip address> <ip address> = static IP address, with a syntax similar to the example below. 192.168.7.9/24 ...
Page 602 Appendix E: Additional BCM2 Information To set or Use this command enable 802.11n network wireless enableHT protocol <option> true false <option> = , or Authentication network wireless authMethod method <method> <method> = network wireless PSK <psk> <psk> = PSK string EAP outer network wireless authentication...
Page 603 Appendix E: Additional BCM2 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 Verify the network wireless...
Page 604: Device-Specific Settings
Appendix E: Additional BCM2 Information 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. For further information, simply open the built-in bulk profile for a detailed list of 'excluded' settings.
Page 605: What Is A Certificate Chain
Appendix E: Additional BCM2 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 596). A certificate or a chain of certificates is used for trusting a TLS server that you want to connect.
Page 606 Appendix E: Additional BCM2 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 607 Appendix E: Additional BCM2 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 BCM2, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to BCM2.
Page 608: Illustration - Gmail Smtp Certificate Chain
Appendix E: Additional BCM2 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 609 Appendix E: Additional BCM2 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 610 Appendix E: Additional BCM2 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 611 Appendix E: Additional BCM2 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 BCM2 for using the GMAIL SMTP service.
Page 613: Index
Index A Note about Enabling Thresholds • 349 Backup and Restore of Device Settings • 300, A Note about Firmware Upgrade Time • 312 314, 321 A Note about Infinite Loop • 281 Backup and Restore via SCP • 322, 511 A Note about Untriggered Rules •...
Page 614 Index Checking the Accessibility of NTP Servers • Connecting a DPX2 Sensor Package to DX • 53, 56, 57, 63 Clearing Event Log • 379 Connecting a GSM Modem • 74, 257 Clearing Information • 378 Connecting a Logitech Webcam • 74, 326 Clearing WLAN Log •...
Page 615 Index Deassertion Hysteresis Example for Enable Modbus Access • 99 Temperature Sensors • 578 Enabling and Configuring SNMP • 277, 278, Default Log Messages • 234 282, 340 Default Measurement Units • 361 Enabling or Disabling a User Profile • 438 Deleting a Firewall Rule •...
Page 616 Index Ping Monitoring and SNMP Notifications • Example 3 - Upper Thresholds for Overcurrent 285, 287 Protector Sensors • 482 Example - Actuator Naming • 484 Example 3 - User Blocking • 434 Example - Creating a Role • 453 Example 3 - Wireless Authentication Method •...
Page 617 Index Identifying Snapshots Folders on Remote Managing Firewall Rules • 416 Servers • 330, 337, 338 Managing One Sensor or Actuator • 115, 116, Identifying the Sensor Port • 46 Identifying the Sensor Position and Channel • Managing Role-Based Access Control Rules • 115, 124 Idle Timeout •...
Page 618 Password Aging Interval • 424 Raritan • 3, 13 Performing Bulk Configuration • 314, 318 Raritan Training Website • 580 Peripherals • 41, 55, 85, 113, 120, 122, 125, Rebooting the BCM2 Device • 300, 324 127, 128, 280, 290 Record Snapshots to Webcam Storage •...
Page 619 Index Retrieving Previous Commands • 355, 356, Setting an LED Color for a Rack Unit • 495 Setting an LED Mode for a Rack Unit • 495, Retrieving Software Packages Information • 300, 325 Setting Data Logging • 165, 282, 284 Returning User Group Information •...
Page 620 Index Setting the sysContact Value • 406 Configure Connection Policies and Setting the sysLocation Value • 407 Standard Attributes • 530, 535 Setting the sysName Value • 407 Configure Connection Policies and Setting the Time Zone • 348, 412 Vendor-Specific Attributes • 549, 554 Setting the X Coordinate •...
Page 621 Index User Blocking • 424 Wireless Network Settings • 166, 170, 181 User Configuration Commands • 435 With an Analog Modem • 353 User Interfaces Showing Default Units • 160, With HyperTerminal • 351, 502, 515, 516 With SSH or Telnet • 352 User Management •...

This manual is also suitable for:

Pmm-1000 Pmb-1960 Pmmc-1000 Pmc-1001

Raritan PMC-1000 User Manual

Chapter 1 Installation and Initial Configuration

Chapter 2 Connecting External Equipment (Optional)

Chapter 3 Using the Web Interface

Chapter 4 Using SNMP

Chapter 5 Using the Command Line Interface

Chapter 6 Using SCP Commands

Appendix A Resetting to Factory Defaults

Appendix B LDAP Configuration Illustration

Appendix C Updating the LDAP Schema

Appendix D RADIUS Configuration Illustration

Appendix E Additional BCM2 Information

Quick Links

Related Manuals for Raritan PMC-1000

Summary of Contents for Raritan PMC-1000