RPC2™ Communications Module User Manual - Network Interface card for the Rack PDU family of power distribution products
TABLE OF CONTENTS SYMBOLS USED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 1.1 1.2 Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Ports on the RPC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.8 System Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.8.6 4.8.7 System Tab—Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Tab—Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Tab—Device Change . . . . . . . . . . . . . . . .
FIGURES Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 RPC2 communications module ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 RPC2 communications module in an MPH2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Symbols Used SYMBOLS USED The following symbols may appear in the documentation or on the product. Table 1 Symbol Symbols on RPC2 communications module and documentation Meaning High Temperature Alerts the user where the enclosure temperature may exceed 158°F (70°C) while operating under high-ambient temperature and at maximally rated load. Instructions Signifies the presence of important operating and maintenance (servicing) instructions in the literature accompanying the appliance.
Introduction 1.0 INTRODUCTION The RPC2 communications module is a network interface module that provides network connectivity to the Liebert® rack PDU family of products. The RPC2 (Rack PDU card) is factory-installed installed in managed versions of Emerson Network Power’s MPH2™ Rack PDU’s. It can be field-installed in Liebert MPH™ and Liebert MPX™ rack PDU’s to provide network monitoring and control capabilities. The module is factory-set for service in DHCP-based applications.
Introduction MPH2 Rack PDU Management A user can use the RPC2 communications module to interact with a rack PDU by referencing the user-assigned receptacle labels or loads. Wide Range of IT Network Capabilities The RPC2 communications module provides a flexible set of IT networking capabilities, including DHCP, BOOTP, DNS, SNTP and SNMP. Hot Swappable The RPC2 communications module may be removed and reinserted without interrupting power from the rack PDU or affecting the connected load.
Introduction 1.2 Ports on the RPC2 The module has six ports designated by icons (see Figure 1). Connect an Ethernet cable (not included) to the Network port. Connect that cable to the network.
Installation 2.0 INSTALLATION 2.1 Getting Started The RPC2 communications module should be factory-installed on Liebert and Emerson Network Power® rack PDU’s. If it is being field-installed, refer to 2.1.1 - RPC2 Communications Module Kit Contents and 2.1.2 - Required Cables to be sure to have all items necessary for proper installation. Figure 2 2.1.
Installation 2.3 Configure an RPC2 Communications Module for Static IP The RPC2 communications module is factory-set for DHCP, making it ready for service immediately. The module can be configured for operation on a network using static IP or BootP. To configure a module for a network that uses static IP: 1. Insert an additional Ethernet cable (not included) into the module’s Link port for the port location).
Installation 2.4 User Level Privileges The RPC2 communications module permits four user levels: • • • • Administrator—can configure and control all rack PDU’s in the system Power User—can configure rack PDU’s; no receptacle control Appliance—can view rack PDU’s; no configuration or control User—can view rack PDU’s specified by administrator; no receptacle control Because of the varying authorization levels, the user interface’s appearance will be different for each level of user.
Installation 2.5 Create a Rack PDU Array™ Up to four MPH2 or Liebert MPX rack PDU’s may be integrated into a Rack PDU Array, which permits central control and monitoring of each rack PDU through a single Web interface. Each rack PDU must have an RPC2 communications module installed. NOTE Creating a Rack PDU Array does not require powering down either the MPH2 rack PDUs or the connected load. The level of monitoring and control depends on the type of MPH2.
Installation Figure 3 Rack PDU Array layout examples TO NETWORK Ethernet cable between Link Port and Network Port RPC2 communications module in MASTER PDU Ethernet cable between Link Port and Network Port RPC2 communications module in Sibling PDU Ethernet cable between Link Port and Network Port RPC2 communications module in Sibling PDU RPC2 communications module in Sibling PDU Ethernet cable between Link Port and Network Port Ethernet cable between Link Port and Network Port RPC2 communications
Monitoring and Configuration Overview 3.0 MONITORING AND CONFIGURATION OVERVIEW 3.
Monitoring and Configuration Overview 3.3 Liebert Rack PDU Viewing and Browsing This manual covers the following methods of viewing and browsing information on a Liebert Rack PDU. Control functions are available via the Web interface but not with the RPC BDM. Method 3.3.1 Monitoring Control Configuration For details, refer to: Summary ✔ — — 3.3.1 - Summary Tab 4.2 - Summary Tab PDU Explorer™ ✔ ✔ ✔ 3.3.2 - PDU Explorer Overview 4.3 - PDU Explorer Tab Device Explorer™ ✔ ✔ — 3.3.
Monitoring and Configuration Overview 3.3.2 PDU Explorer Overview PDU Explorer is Web-based software that displays a hierarchical view of the system. The PDU Explorer permits browsing components starting at the PDU level, through to the branches of the PDU, and down to the receptacles of those branches. See 4.0 - Accessing an RPC2 Communications Module via the Web Interface for details on using PDU Explorer.
Monitoring and Configuration Overview Figure 6 Device Explorer screen Details about MPH2 receptacles Hyperlinks open PDU Explorer to a receptacle’s data 3.3.4 Events Tab Overview The Events tab lists events that have occurred on the MPH2 system, with more recent events at the top of the list. When the number of events exceeds the limit of 1024, the oldest events are removed first.
Monitoring and Configuration Overview 3.3.5 System Tab Overview The System tab is the control and configuration center for the RPC2 rack communications module. Pages on the tab permit updatinge firmware, joining networks, setting security levels, adding and removing users, setting access privileges and alarm threshholds and setting automatic messages for events and alarms (see Figure 8).
Accessing an RPC2 Communications Module via the Web Interface 4.0 ACCESSING AN RPC2 COMMUNICATIONS MODULE VIA THE WEB INTERFACE Emerson’s RPC2 communications module can be accessed with a Web browser once it is connected to a network. The browser obtains direct access to the RPC2 communications module via a graphical user interface. The data and appearance will vary according to the types of Liebert or Emerson rack PDU being viewed through the RPC2 communications module.
Accessing an RPC2 Communications Module via the Web Interface 4.2 Summary Tab Click the Summary tab (Figure 11) to view recent events as well as rack PDU status information. This tab gives access to a rack PDU’s ID, status, number of receptacles and how many are turned On as well as measurements and utilization information. Click on a rack PDU under the PDU Status heading to open it in the PDU Explorer tab (refer to 4.3 - PDU Explorer Tab for more information).
Accessing an RPC2 Communications Module via the Web Interface 4.3 PDU Explorer Tab The PDU Explorer displays data from connected equipment, starting with the rack PDU view at the highest level, allowing users to browse down one level to view branches, then another to view the receptacles. It also permits viewing sensors and editing sensor settings.
Accessing an RPC2 Communications Module via the Web Interface 4.3.1 PDU Explorer Tabs: Measurements The PDU Explorer’s Measurements tab presents available data about the rack PDU. At the system level and PDU level, the page permits resetting energy for the PDU or for a branch. At the branch level, the page permits turning power On or Off to a branch or receptacles, locking and unlocking a branch or receptacles and causing a receptacle’s LED to blink.
Accessing an RPC2 Communications Module via the Web Interface Figure 14 PDU Explorer tabs: Status A white checkmark on a green background indicates normal operation. A white X on a red background indicates an abnormal condition. Data shown are: Over Current Under Current Under Voltage Channel OK Information is shown at branch level 4.3.
Accessing an RPC2 Communications Module via the Web Interface Figure 15 PDU Explorer tabs: Settings Settings Tab at Rack PDU Level One item or all may be selected for changing by putting a checkmark in the boxes. Clicking in the top box puts a checkmark in all the boxes. The Edit icon is a pencil. Pencil is replaced by Save and Cancel icons after the Edit icon is clicked. X Settings Tab at Branch 4.3.
Accessing an RPC2 Communications Module via the Web Interface Figure 16 Sensor information on Summary Tab and details on Settings Tab Sensor Information (Summary Tab) Click on a Sensor to open the PDU Explorer to the sensor information on the Settings tab.
Accessing an RPC2 Communications Module via the Web Interface To edit sensor information: 1. Put a checkmark, ✔, in the box to the left of the portion to be changed. 2. Click the Edit icon • If assigning a label: Enter the new label (the default is the sensor’s serial number). • If changing the Asset (sensor in this case): Enter a new name for the sensor (default names are Tag01 and Tag02. • If changing the Alarm Config, click on the drop-down menu and choose Alarm when close, Alarm when open or None. 3.
Accessing an RPC2 Communications Module via the Web Interface Click the PDU Explorer tab to view all connected rack PDU’s. Each rack PDU is displayed along with its summary information. Energy can be reset by checking the box next to a rack PDU then clicking either the Reset All Energy or the Reset Selected Energy icon at the top of the page. Table 7 PDU summary descriptions Item 4.4 Description Label The rack PDU name. ID The position in an array of the rack PDU.
Accessing an RPC2 Communications Module via the Web Interface To edit a branch: 1. Log in with the privileges required to change these settings. 2. From the PDU Explorer tab, click the rack PDU with the branch to be edited. 3. Highlight the branch to be edited by clicking in one of its fields. NOTE Clicking a branch will open its receptacle page. 4. In the table at the bottom of the page, click the Settings tab. 5. Check the box or boxes next to the settings to be edited. 6. Click the Edit icon . 7.
Accessing an RPC2 Communications Module via the Web Interface The Measurements tab displays the receptacle’s current, voltage, real power, apparent power, power factor, energy and crest factor information. The Status tab displays whether the receptacle is within acceptable limits for overcurrent and low current thresholds. The Information tab displays general information about the receptacle. The Settings tab permits editing settings on a receptacle. To edit a receptacle: 1.
Accessing an RPC2 Communications Module via the Web Interface 4.6 Device Explorer The Device Explorer tab permits viewing the status of all receptacles on a rack PDU. As with the PDU Explorer, place a check mark (✔) in the box or boxes next to receptacles and then use the icons at the top of the page to Reset Energy, Enable Receptacle Power, Disable Receptacle Power, Cycle Receptacle Power, Lock Receptacle, Unlock Receptacle or Blink Receptacle LED.
Accessing an RPC2 Communications Module via the Web Interface Figure 20 Receptacle group screen All Receptacles in RGROUP2 are On Receptacles in My Group is Mixed (some On, some Off); My Group is a custom-named receptacle group Edit Group icon All Receptacles in RGROUP3 are Off Click to display the groups from 1 to 16; clicking on subsequent ranges in the list reveals other groups Create a Receptacle Group 1. 2. 3. 4. 5. Navigate to the Device Explorer tab. Click the Edit Group icon.
Accessing an RPC2 Communications Module via the Web Interface 4.7 Events Tab Click the Events tab to see a list of rack PDU events. Use the drop-down menus to filter events. Events can be configured for SNMP Traps, Syslog, Email and SMS in the System Tab. Click the Download icon at the top of the page to download a log file for all events. A downloaded event log can be imported into Microsoft® Excel® and viewed as a spreadsheet. Figure 22 Events tab 4.
Accessing an RPC2 Communications Module via the Web Interface 4.8.2 System Tab—Devices Click Devices in the System tab navigation tree to view a read-only page about the MPH2 rack PDU and the RPC2 communications module. Available information includes the System Name (userspecified), system location, system description, contact personnel names, MPH2 manufacturer, the RPC2 serial number and firmware label and the MPH2 model, serial number and firmware version.
Accessing an RPC2 Communications Module via the Web Interface 4.8.4 System Tab—Firmware Update Firmware updates may be downloaded from the Downloads section of the Emerson Network Power® Web site (www.emerson.com). Once downloaded, the update may be applied to all RPC2 communications modules in an installation through the RPC2 communications module’s Web interface. The RPC2 communications module permits unattended firmware updates. The browser being used may be closed after the progress bar is displayed.
Accessing an RPC2 Communications Module via the Web Interface DNS From the Domain Name Server (DNS) settings menu, an administrator can configure the servers the RPC2 communications module will use for hostname resolution. When configured, host addresses for SNMP, Network Time and Email/SMS can be specified in either full Domain Name format or hostonly format, provided that the appropriate Domain Name Suffix is used. The DNS menu is used to set parameters for network access to the RPC card.
Accessing an RPC2 Communications Module via the Web Interface Notification The RPC2 communications module will generate notifications for a wide variety of events. It can be configured to direct or store those event notifications for immediate use or for analysis later. To configure notifications: 1. Log in with the privileges required to change these settings. 2. From the side navigation bar of the System tab, click Notification. 3.
Accessing an RPC2 Communications Module via the Web Interface To configure e-mail and SMS event consolidation: 1. From the side navigation bar of the System tab, click Notification>Messaging>Customize Message. 2. Under Configure Email/SMS Event Consolidation, check the boxes to enable e-mail or SMS consolidation. 3. Enter the consolidation time limit in number of seconds and enter the consolidation event limit in number of events. 4. Click the Save icon, ✔, at the top of the page.
Accessing an RPC2 Communications Module via the Web Interface Backup and Restore An administrator can configure an FTP site to backup a configuration file or restore configuration from a backup file. To configure where the backup will be stored: 1. Log in with the privileges required to change these settings. 2. From the side navigation bar of the System tab, click Notification>Backup and Restore. 3.
Accessing an RPC2 Communications Module via the Web Interface SNMPv1/v2 Access From the side navigation bar of the System tab, click SNMP-v1/v2 Access to configure the SNMP v1/v2 communities settings. Up to 20 devices can be configured with permission to access the RPC2 communications module, identified by IP address or hostname, read/write privileges and community string. Table 10 SNMPv1/v2 access description Parameter Description Entry As many as 20 devices may be configured for access.
Accessing an RPC2 Communications Module via the Web Interface SNMPv1/v2 Traps An administrator can configure up to 20 users to receive notifications from the RPC2 communications module, identified by IP address or hostname, trap listen port and community string. To configure SNMPv1/v2 Traps: 1. 2. 3. 4. 5. From the side navigation bar of the System tab, click Manage Protocol>SNMP>V1V2 Traps. Enter the network name, port number and community string in the appropriate fields.
Accessing an RPC2 Communications Module via the Web Interface 4.8.6 Authentication Authentication can be performed locally or on a remote Kerberos, LDAP, Radius or TACACS+ authentication server. If the rack PDU is managed by an Avocent® DSView server, DSView authentication is also supported. The rack PDU also supports remote group authorizations for the LDAP, Radius and TACACS+ authentication methods. An administrator can configure authentication using the Web interface or the command line interface.
Accessing an RPC2 Communications Module via the Web Interface To configure a TACACS+ authentication server: 1. From the side navigation bar of the System tab, click Authentication>Remote Servers>TACACS+. 2. Enter the IP addresses for the First Authentication Server and First Accounting Server. 3. If used, enter the IP addresses of the Second Authentication Server and Second Accounting Server. 4. Select the desired service (PPP, raccess or shell) from the Service drop-down menu. 5.
Accessing an RPC2 Communications Module via the Web Interface To add a group: 1. 2. 3. 4. From the System tab’s navigation tree, click Authorization>Groups. To add a group, click the Add icon at the top of the page, enter the name for the new group. Set the access level for members of the group by granting access to receptacles. Click the Save icon, ✔. To delete a group: 1. Check the box next to the group to be deleted 2. Click the Delete icon. To add a user to a group: 1. 2. 3. 4.
Accessing an RPC2 Communications Module via the Web Interface Users From the User Names page, an administrator can add or delete users and change user passwords. NOTE The administrator’s user password cannot be changed on this page. To add a user: 1. 2. 3. 4. From the System tab’s navigation tree, click Authorization>Users. Click the Create Local User icon. Enter the username and password and confirm the password. Click the Save icon, ✔. To delete a user: 1. 2. 3. 4.
RPC BDM™ (Optional) 5.0 RPC BDM™ (OPTIONAL) The RPC BDM is a small monitoring device that displays data from an MPH2, Liebert MPX™ or Liebert MPH™ units through a connection to an RPC2 communications module. The unit provides another way to browse PDU data using the PDU Explorer and Device Explorer, as in the Web interface. Views shown by the RPC BDM are essentially the same as those shown by the MPH2’s onboard LCD.
RPC BDM™ (Optional) 5.2.1 Set the IP Address for the RPC2 The RPC2 and the RPC BDM may be used on a network or on stand-alone rack PDU’s. Either mode requires initializing the RPC2 with an IP address before the RPC BDM can display data. Follow the appropriate steps to initialize the RPC2 in a networked or stand-alone environment. Refer to Figure 25 for location of ports on the RPC2.
RPC BDM™ (Optional) 5.4 Navigation Tips The RPC BDM has a scroll button for navigation (see Figure 24). To navigate and select items: • Use the scroll button to move the cursor to highlight an item on the screen. • Depress the scroll button to select the highlighted item. Figure 26 RPC BDM navigation icons PDU LEVEL VIEW 1.98A MPH2 Shows the ID numbers of available PDUs, branches or receptacles, depending on level 119.7V 204W RPC BDM Operation 5.5.
RPC BDM™ (Optional) 5.5.2 Types of Data Available at PDU, Branch and Receptacle Levels The following table shows the types of data available at each level.
RPC BDM™ (Optional) 5.6.1 View PDU Data To view data for a PDU: • Select a PDU number in the bottom left corner. The selected number will be highlighted. • The screen displays information for the selected PDU. The example below shows data for PDU #1, one of two PDUs that are communicating with the RPC BDM unit. • The PDU view displays information collected at the PDU input point for each of the three input phases: L1, L2 and L3. Up to three phases may be used.
RPC BDM™ (Optional) 5.6.2 View Branch Data The availability of branch information depends on the capabilities of the PDU. Branch information and PDU information are the same for rack PDU’s without branch management; that information is seen at the PDU view level. To view data for a branch module: • Select a branch in the bottom left corner. The selected letter will be highlighted. • The screen displays information for the selected branch module.
RPC BDM™ (Optional) 5.6.3 View Receptacle Data The availability of receptacle information depends on the capabilities of the PDU. To view data for a receptacle: • Select a receptacle number in the bottom left corner. The selected number will be highlighted. • The screen displays information for the selected receptacle. The example below shows data for Receptacle #7, one of eight receptacles on Branch #A of PDU #1 that are communicating with the RPC BDM unit.
RPC BDM™ (Optional) 5.7 RPC BDM: Receptacle Information The RPC BDM displays a list of all receptacles on a single rack PDU. To access the receptacle list: • Select the Information icon in the Receptacle view, shown below left. • Select the Receptacle to be viewed, below right. Selected component ID 1.98A 1-A-7 119.
Liebert SN™ Sensor Installation (Optional) 6.0 LIEBERT SN™ SENSOR INSTALLATION (OPTIONAL) The RPC2 is designed to monitor Liebert SN integrated and modular sensors. • Integrated sensors are attached to a single cable. These Liebert SN sensors are available in several varieties, including single or multiple temperature sensors. • Modular sensors are separate probes shipped with a cable for connection to the RPC2 communications module.
Liebert SN™ Sensor Installation (Optional) 6.4 Connect the Sensor Each sensor is shipped with a cable to connect to the Liebert SN™ port on your Liebert product. The RPC2 (Rack PDU Card) must be installed before the sensor can be connected (see 2.0 - Installation for more information). To connect the sensor: • After securely mounting the sensor (see 6.3 - Mount the Sensor), determine the location of the Liebert SN port, identified by the icon shown below.
Liebert SN™ Sensor Installation (Optional) 6.5 Confirm the Module Change After connecting the sensor, you must acknowledge the change via the Web interface before the sensor may be monitored. You will need the sensor address recorded in 6.2 - Record the Sensor Address.
RPC2 Communications Module Icons 7.
Specifications 8.0 SPECIFICATIONS Table 18 Electrical and physical specifications Parameter Limits Voltage 7-12VDC Power 4W Maximum Operating Temperature Range, °F (°C) 41 to 140 (5 to +60) Ambient Storage Temperature Range, °F (°C) -4 to 140 (-20 to +60) Relative Humidity 0% to 95% (non-condensing) Maximum Operating Altitude, ft. (m) 6560 (2000) Dimensions, WxDxH, in. (mm) 4.0 x 0.84 x 1.78 (101.6 x 21.3 x 45.
Technical Support / Service Web Site www.liebert.com Monitoring liebert.monitoring@emerson.com 800-222-5877 Outside North America: +00800 1155 4499 Single-Phase UPS & Server Cabinets liebert.upstech@emerson.
