Emerson MONITORING OpenComms User manual

Category
Networking
Type
User manual

This manual is also suitable for

MONITORING
OpenComms NIC
USER MANUAL
i
TABLE OF CONTENTS
1.0 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 OpenComms Compatibility . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Retrofit Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Self-Contained Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 User Connections for OpenComms NIC . . . . . . . . . . . . . 6
2.3.1 Network Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3.2 BMS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3.3 Configuration Port / Service Terminal . . . . . . . . . . . . . . . . 6
3.0 SYSTEM CONFIGURATION. . . . . . . . . . . . . . . . . . . . . . . 9
3.1 DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Service Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.0 OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Liebert Global Products MIB. . . . . . . . . . . . . . . . . . . . . 14
4.3 RFC 1628 UPS MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3.1 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4 MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.5 HTTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.6 Modbus RTU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.7 System Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.8 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.0 MODBUS COMMUNICATIONS AND CONNECTIVITY. . . . . 19
5.1 Implementation Basics . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1.1 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.2 Transmission Format. . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3 Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
ii
5.4 Modbus Slave Functions . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.1 Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.2 Function Code Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.3 Read/Write Holding Registers (0x03, 0x06, 0x10) . . . . . . 22
5.4.4 Read Input Registers (0x04) . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.5 Read, Set Coil Status (0x01, 0x05, 0x0F) . . . . . . . . . . . . . 22
5.4.6 Read Input Status (0x02) . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4.7 Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5 RTU Framing Examples . . . . . . . . . . . . . . . . . . . . . . . . 24
5.5.1 Read Registers (Function Code 0x03 & 0x04) . . . . . . . . . 24
5.5.2 Write single holding register (Function Code 0x06) . . . . 24
6.0 NIC SETUP AND TESTING. . . . . . . . . . . . . . . . . . . . . . 25
6.1 Jumper Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2 Testing the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3 Service Terminal Troubleshooting . . . . . . . . . . . . . . . . 26
6.4 SNMP Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.5 Web Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.6 Modbus Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 27
7.0 FIRMWARE UPDATES . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.1 Establishing Communication—Necessary
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2 Establishing Communication—Service Terminal
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3 Firmware Update Procedure . . . . . . . . . . . . . . . . . . . . . 30
8.0 EXTERNAL ENCLOSURES . . . . . . . . . . . . . . . . . . . . . . 33
8.1 Power Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8.2 Communication Connection. . . . . . . . . . . . . . . . . . . . . . 33
9.0 RETROFIT INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 34
9.1 Environmental Installation . . . . . . . . . . . . . . . . . . . . . . 34
9.1.1 Deluxe System/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2 System Wiring (SM, AM, AG Microprocessors) . . . . . . 37
iii
9.3 Power Connection (SM, AM, AG Microprocessors). . . . 37
9.3.1 Power Connection (Level 0 and Level 10
Microprocessors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.3.2 Communication Connection (SM, AM, AG
Microprocessor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.3.3 Communication Connection (Level 0 and Level 10
Microprocessors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.4 Himod (LNA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.4.1 System Wiring (Himod). . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.4.2 Power Connection (Himod) . . . . . . . . . . . . . . . . . . . . . . . . 39
9.4.3 Communication Connection (HiMod) . . . . . . . . . . . . . . . . 39
9.5 Mini-Mate2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.6 Emerson Network Power (CEMS100 / LECS15) . . . . . 40
9.7 UPS Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.8 Npower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.8.1 Power Connection for NPower . . . . . . . . . . . . . . . . . . . . . 40
9.8.2 Communication Connection for NPower . . . . . . . . . . . . . 40
9.9 7200 UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
9.10 HiPulse UPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.11 Static Switch2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.12 STS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.13 PDU and DataWave with PMP & EPMP . . . . . . . . . . . 47
iv
FIGURES
Figure 1 Typical installation of OpenComms NIC card . . . . . . . . . . . . . . . 1
Figure 2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 3 Null modem cable diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 4 NIC main menu in HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 5 LED locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 6 Typical maximum installation . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 7 Exceeding maximum specifications . . . . . . . . . . . . . . . . . . . . . . 21
Figure 8 Jumper positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 9 NIC-ENCL1 internal view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 10 Deluxe System 3 NIC installation . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 11 Deluxe System 3 chilled water control cavity . . . . . . . . . . . . . . 35
Figure 12 ICS control cavity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 13 Challenger installation location . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 14 Himod NIC installation location . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 15 NPower UPS NIC installation . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 16 7200 UPS NIC installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 17 HiPulse installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 18 STS2 typical NIC location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 19 STS2 NIC installation, 800-1000A units . . . . . . . . . . . . . . . . . . 46
Figure 20 STS2 NIC installation, 100 - 600A units . . . . . . . . . . . . . . . . . . 47
TABLES
Table 1 OpenComms availability . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Table 3 Service terminal navigation . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 4 Exception response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Introduction
1
1.0 INTRODUCTION
The OpenComms NIC Card transforms Liebert units into manageable
nodes within your Network, NMS, and BMS systems.
The OpenComms NIC Card contains a standard Ethernet and EIA-485
(2-wire) port designed to support viewing and management through:
HTTP for Web browsers (I.E. 5.5 or later)
SNMP (v1, v2c) for network management systems
Modbus RTU for building management systems (and SiteScan)
For the first time, the system that monitors the status of your comput-
ing, communication and facility infrastructure can comprehensively
monitor your Liebert equipment concurrently.
These standard open protocols allow simple integration into your mon-
itoring system, leveraging prior infrastructure investments and estab-
lished procedures.
Figure 1 Typical installation of OpenComms NIC card
Building
Management
System
SNMP HTTP
Modbus
Air
ETHERNET
UPS
Power
OpenComms NIC
Network
Management
Systems
Internet Web
Browsers
Introduction
2
1.1 OpenComms Compatibility
The OpenComms NIC may be installed and used with these units:
Environmental Units
Deluxe System3—Advanced Microprocessor with Graphics,
Advanced Microprocessor and standard microprocessor
Challenger 3000—Advanced Microprocessor with Graphics,
Advanced Microprocessor and standard microprocessor
Mini-Mate2
Level 00—Deluxe System3, Challenger 3000
Level 10—Deluxe System3, Challenger 3000
Level 05/15 (UK)
•Himod
Emerson Network Power (CEMS100 / LECS15)
3-Phase UPS
•Npower
Hiross 7200 (Italy)
Hiross HiPulse (Italy)
3-Phase Power
PDU with PMP or EPMP monitoring
DataWave with PMP or EPMP monitoring
Static Switch
Static Switch2
Static Switch2/PDU
NOTE
All units are manufactured in North America unless otherwise
noted.
Introduction
3
Retrofit Kits are designed specifically for individual units. Consult
your local Emerson and Liebert sales representative for pricing, part
numbers and installation help.
Table 1 OpenComms availability
Unit
Factory
Option
Retrofit
Kit
Retrofit Kit
Part #
Environmental Products
Deluxe System 3 and
ICS
Yes Yes NIC-K-SYS3
Challenger Yes Yes NIC-K-CHALL
Mini-Mate2 Yes
1
NIC-ENCL1 OR 2
Level 00/05/10/15 Yes NIC
Himod Yes Yes NIC
Emerson Network
Power (CEMS100 /
LECS15)
Yes
3
Yes
3
Consult sales department
3-Phase UPS
Npower Yes Yes
2
37OP000NIC8
Hiross 7200 (Italy) Yes Yes
2
4645114G
Hiross HiPulse (Italy) Yes Yes
2
4645114d
3-Phase power
PDU DataWave With
PMP or EPMP
Yes
1,2
NIC-ENCL1 OR 2
Static Switch Yes
1,2
NIC-ENCL1 OR 2
Static Switch 2 Yes Yes
2
STSNIC
1
Requires an external enclosure assembly
2
Contact your sales / service representative or liebert global services for installation.
3
For Australian units, contact the international sales department @
Introduction
4
Table 2 Specifications
Electrical Requirements
Voltage
18 to 24VAC
50/60 Hz, Single Phase
12 to 36VDC
Power 6VA maximum
Environmental Conditions, °F (°C)
Operating Ambient Temperature 41 to 104 (5 to 40)
Storage Ambient Temperature -4 to 140 (-20 to 60)
Relative Humidity 10% to 90% RH (Non-condensing)
Dimensions, Inches (mm)
Unit Only 7 x 4 x 1.5 (178 x 102 x 38)
As Shipped 9.75 x 7.0 x 2.5 (248 x 178 x 64)
Weight, lb (kg)
Unit Only 0.4 (0.2)
As Shipped 1.3 (0.6)
Installation
5
2.0 INSTALLATION
The OpenComms NIC card may be ordered as a factory-installed
option, and it may be installed as a kit for field retrofit to existing Lie-
bert units or as a self-contained unit in its own enclosure.
If ordered as a factory-installed option, proceed to 2.3 - User Connec-
tions for OpenComms NIC.
2.1 Retrofit Kit
As a retrofit kit, the circuit board is secured to a metal mounting
plate. The mounting plate then is attached to a flat metal surface in a
low-voltage section of the Liebert unit.
2.2 Self-Contained Unit
The self-contained model packages the interface card inside a steel
enclosure, for mounting external to the Liebert unit. A low-voltage
transformer is also provided.
Figure 2 Connections
Input Power
(Input to TB3)
Network Port for
NMS and Web access
DTE Serial Port
for Configuration
Modbus Output for BMS
(Output from TB2)
IGMnet or SiteScan
Comms from Unit
(input to TB1)
Installation
6
2.3 User Connections for OpenComms NIC
The OpenComms NIC can use simultaneous connections, sometimes
requiring three user connections:
Permanent network connection
Modbus 485 connection
Temporary serial connection for configuration/setup
2.3.1 Network Port
Consult with the network administrator or other responsible party for
arranging a network drop to the Liebert equipment. The OpenComms
NIC communicates via standard 10 Base-T Ethernet network connec-
tion. Route the 10 Base-T cable to the Liebert unit and connect to J3,
the RJ45 jack on the interface card. The OpenComms Network card
will operate with any 10 Base-T Ethernet, regardless of operating sys-
tem used.
2.3.2 BMS Port
The Modbus 485 connection will use the terminals marked “Repeater.”
(TB2) The Modbus server uses RTU protocol and will allow for a maxi-
mum of 32 units on 4000ft. of wire on a common line. EIA-485 repeat-
ers may be necessary to accommodate additional units or longer
cables. Point availability may be referenced in the document, “NIC
Reference Library,” which may be downloaded at www.liebert.com
under the OpenComms product family.
2.3.3 Configuration Port / Service Terminal
A temporary serial connection to the interface card is necessary for
configuration and setup.
Using a DB9F-DB9F null-modem cable, connect the “DTE Serial Port”
P18 to an ASCII terminal or computer running terminal emulation
application. HyperTerminal® and Procomm® are examples of termi-
nal emulation applications running on Microsoft Windows® operating
systems. All trademarks are property of their respective owners.
Installation
7
Accessing the Configuration Port
What you will need:
PC capable of running a terminal emulation application, such as
Microsoft Windows® HyperTerminal®.
DB9 Null modem or file transfer cable. (The correct cable will have
at a minimum, pins 2 and 3 crossed at the ends.) Null modem
cables are commonly found in computers stores and may also be
referred to as a file transfer cable.
Figure 3 Null modem cable diagram
1. Launch HyperTerminal. When you see the
screen at right, select Cancel.
2. Select the disconnect icon from the menu bar.
This step ensures that you will be able to
modify the configuration settings.
3. Go to File > Properties to make
configuration changes. Under the Connect
To setting, choose the appropriate communications port for your
computer. Generally this is Com 1.
4. Select the Configure button
and adjust the terminal
communication settings to:
Bits per second: 9600
•Data Bits: 8
Parity: None
Stop Bit: 1
Flow Control: None
•Select OK to close both win-
dows.
5. After the communication
settings are adjusted, press
NOTE
Turn off the power management on your PC or laptop to ensure
that the communications port will not “go to sleep” during the
configuration process.
Null Connection
DTE Device
Receive Rx (pin2)
Transmit Tx (pin3)
DTE Device
Receive Rx (pin2)
Transmit Tx (pin3)
Installation
8
the Enter key on your keyboard. This will initiate
communications with the card and the following screen should be
displayed.
Figure 4 NIC main menu in HyperTerminal
(You can also cycle power on the OpenComms NIC card. This will
also initiate communications and provide information on current
revision status.)
6. When the message “Initializing Network…” appears, hit the
Enter key on your keyboard. (Additional network information
may appear)
!
CAUTION
Cycling power on either the 7200 or the HiPulse UPS is not
recommended unless the unit is in bypass mode. Consult the
UPS user manual for further instructions.
System Configuration
9
3.0 SYSTEM CONFIGURATION
3.1 DIP Switch Settings
A four-position DIP switch is provided, but no user configuration via
DIP switches is necessary at this time.
3.2 Service Terminal
Refer to Accessing the Configuration Port on page 7 for explicit
details on accessing the service terminal / configuration port.
By default, the service terminal communication parameters are:
9600 bps
•No parity
8 data bits
1 stop bit
Flow Control: None
After connecting to the OpenComms NIC card, press the space bar or
<Enter> key to activate the service terminal session. If no response is
apparent and you have verified connectivity, cycle power on the Open-
Comms NIC and the service terminal sessions should appear automat-
ically.
!
CAUTION
Cycling power on either the 7200 or the HiPulse UPS is not
recommended unless the unit is in bypass mode. Consult the
UPS user manual for further instructions.
System Configuration
10
Table 3 Service terminal navigation
Main Menu
1. System Information
1.1 Name
1.2 Contact
1.3 Location
1.4 Description
2. Network Settings
2.1 Boot / IP Settings
2.1.1 Boot Mode
2.1.1.1 Static
2.1.1.2 BootP
2.1.1.3 DHCP
2.1.2 IP Address
2.1.3 Netmask
2.1.4 Default Gateway
2.2 SNMP Communications
2.2.1 SNMP agent (enable/disable)
2.2.2 Authentication Traps (enable/disable)
2.2.3 Display / Modify Communities
2.2.4 Display / Modify Trap Communities
2.3 Web Server
2.3.1 Web Server (enable/disable)
2.3.2 Configuration Control (enable/disable)
2.3.3 Refresh rate
2.4 Telnet Server
2.4.1 Telnet server (enable/disable)
System Configuration
11
System Information Menu
The System Information Menu seeks descriptive input to enable the
unit to be identified. This data is readable via SNMP queries. The (“)
character is not permitted in any of the descriptive fields
Network Settings Menu
The Network Settings Menu configures network parameters essential
for proper network operation. The network administrator or other per-
sonnel responsible for the network should be consulted for the proper
parameters to be entered in this menu.
In the static mode, the IP address is entered. Use the standard four-
part dotted decimal format. The NetMask and Default Gateway
should also be entered in dotted decimal format. The NetMask, also
known as subnet mask, delineates devices on the same physical net-
work segment, versus devices that require the services of a network
router for access to other networks. The Default Router is the address
of default router on the local segment.
BOOTP and DHCP Mode
The OpenComms NIC supports DHCP and BOOTP if a DCHP or
BOOTP server must exist on the network. When this feature is
enabled, at boot-up the card will perform a DHCP or BOOTP request
for configuration information, including automatic assignment of an
IP address. If the card receives the information, no further requests
are made. If, at boot-up, a response is not received, the card will con-
tinue to send a request approximately every 30 seconds until a
response is received. When this condition is encountered, pushing the
<Enter> key returns the unit to the service terminal mode.
SNMP Communications Menu
The SNMP (Simple Network Management Protocol) Communications
Menu specifies parameters particular to the SNMP interface. Commu-
nities are used as a means of security for SNMP v1; only specified
hosts with the appropriate community name(s) are allowed to perform
particular SNMP operations. Up to 20 different communities can be
assigned.
For each community, specify the dotted decimal IP address of the
remote host, the privilege level (read or read/write), and community
name. Trap Communities specify the recipient(s) of SNMP trap mes-
sages generated by the OpenComms Network Interface Card. Typi-
cally; the recipient is the management station of the NMS. Specify the
!
CAUTION
Consult your network administrator to ascertain the
parameters appropriate to your network.
System Configuration
12
destination IP address, and the community name for that host. Up to
20 trap communities can be assigned. For Communities and Trap
Communities, the information can be entered as a “complex” line —
all parameters space-delimited on the command line. Otherwise, the
menu items will prompt for each individual parameter.
Authentication failure traps may be enabled, so that the network
management system can be warned when unauthorized access (i.e.:
incorrect community name) is attempted.
Web Server
The Web Server section will allow the user to disable / enable the
HTTP session for the card. Disabling the Web Server means that web
browsers will not be able to access the devices status graphical page
(GUI).
Telnet
This section allows users to enable or disable the Telnet session.
Change User Name / Password
This section allows users to set or change the default user name and
password.
Default user name is “Liebert” (case sensitive).
Default password is “Liebert” (case sensitive).
Firmware Updates Menu
The Firmware Update Menu is intended for Liebert service personnel only. No
user configurable parameters are accessed in this selection. If entered, to escape,
power must be cycled on the card.
Factory Settings Menu
The Factory Settings Menu displays the manufacture date, serial
number and MAC address of the card. These parameters are read-
only. Once all parameters have been entered, press Escape to return
to the Main menu; then press x to save configuration, exit and reboot
to enable the new configuration. All parameters are stored in non-vol-
atile flash memory. Pressing q after Escape will abort all changes.
Neither selection is case-sensitive.
NOTE
SNMP v1 communities are transmitted in plain (unencrypted)
text across the network.
System Configuration
13
Auxiliary Communications
The Auxiliary Communications Menu allows the user to set up the
parameters necessary for Modbus communications. The user can
enable / disable the Modbus sessions as well as assign the slave ID.
Q. <q> will abort all changes.
X. <x> will save configuration changes.
Once all parameters have been entered, press <escape> to return
to the Main menu; then press exit and reboot using the new con-
figuration. All parameters are stored in non-volatile flash mem-
ory.
Neither selection is case-sensitive.
Operation
14
4.0 OPERATION
4.1 SNMP
The OpenComms Network Interface Card supports “get,” “getnext,”
“set,” “response” and “trap” packets of SNMP (Simple Network Man-
agement Protocol). The OpenComms NIC supports MIB-II, RFC1628
and Liebert Global Products MIBs. The terms “alarms” and “condi-
tions” will be used interchangeably through out this description.
Alarms are generated and maintained through the RFC 1628 UPS
MIB. Conditions are generated and maintained through the Liebert
Global Products MIB.
The RFC 1628 UPS MIB provides information for the supported UPS
devices. The Liebert Global Products MIB provides information for the
supported environmental devices. All conditions that are listed are
dependent upon what the unit itself supports. When a condition
occurs within the unit, it is logged into the condition table within the
appropriate MIB and a unique ID is assigned. A description of the con-
dition along with the value of the system up-time when the condition
was generated is placed into the table as well. A trap is then sent out
to the monitoring system.
4.2 Liebert Global Products MIB
Environmental units log conditions in the Liebert Global Products
MIB. Traps for the environmental units are generated out of the Lie-
bert Global Products MIB. Currently, there are only two traps that are
sent for environmental units through the MIB: Event Condition Entry
Added and Event Condition Entry Removed. The Event Condition
Entry Added is sent each time a condition is inserted into the condi-
tions table. This trap provides the condition ID, the condition descrip-
tion, and the condition time. The Event Condition Entry Removed is
sent each time a condition is removed from the conditions table. This
trap provides the condition ID, the condition description, and the con-
dition time.
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56

Emerson MONITORING OpenComms User manual

Category
Networking
Type
User manual
This manual is also suitable for

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI