This agent can monitor several parameters of Power supply units manufactured by Unite. It has been tested against CL-Amp current meters switch in Power Distribution Units PDU http://www.unitetechnologies.com/products.aspx and temperature sensors. However, we recommend checking its functionality before implanting it in a production environment.

This Agent has been developed using functionalities and enhancements of Osmius framework and ACE libraries, so it is necessary to install the ACE libraries for the proper deployment and operation of agente. See chapter: installation.

This PowerHawk2 osmius agent provides up to 32 basic events with configuration parameters to allow scaling of a very simple way. The basic events have been chosen by network experts. This agent also provides a general interface so the Osmius users can create customized events and associate them with any Instance within the monitoring system. Using the Osmius Web Console the users access to a MIB Navigator to load MIBS and to search for the appropriate snmp oid to create their own events.

In this agent all the provided events are non-intrusive events, remote events, so they can be retrieved from the network outside of the Instance being monitored. Events are build upon SNMP protocol version 1 or 2.

Osmius also has an agent to receive and process **SNMP Traps** and to redirect them into the event correlation system as they were Osmius “normal” events. For each Agent Type (Instance Type) we can configure several “Trap Events” and in this PowerHawk2 Agent we only need one trap event because all powerhawk2 threshold alarms (current, temperature, humidity, etc..) use these same three traps: trapCritical, trapWarning and trapCleared.

As a general rule each Osmius agent can monitor one instance type. If you are not familiar with these concepts check out the glossary. Each instance is individually defined in the configuration file (if you want further information go to agents and instances); depending on agent type is the instance type and depending on instance is the connection info.

The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info)

In the particular case of PowerHawk2 agent the CONNECTION_INFO field has no information needs as it uses the generic SNMP fields like Nodename, read community and snmp port.

CONNECTION_INFO= 

The type defines the instance type to be monitored. Every declared instance must be associated with a type as you can see here

In PowerHawk2 devices:

TYPE= POWRHAWK

Here is briefly the capabilities of this agent, further down on this page each event is described in more detail.

• If you want capacity plannings unset silent mode in events

PHNAMEUN returns Unit Name of the device

Return values:

Recommended parameters:

Parameter setting example:

PHNAMEUN = -t 86400 -c 1 -w 0 -a 0 -T "Unit Name"

Remarks: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

PHSERNUM returns the Serial Number of the decice.

Return values:

Recommended parameters:

Parameter setting example:

PHSERNUM = -t 86400 -c 1 -w 0 -a 0 -T "Serial Number"

Remarks: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

PHMACADR returns the MAC Adress of the device.

Return values:

Recommended parameters:

Parameter setting example:

PHMACADR = -t 86400 -c 1 -w 0 -a 0 -T "MAC address"

Remarks: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

PHHWTYPE returns the Hardware Type of the device.

Return values:

Recommended parameters:

Parameter setting example:

PHHWTYPE = -t 86400 -c 1 -w 0 -a 0 -T "Hardware Type"

Remarks: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

PHFMWREV returns the Firmware revision of the device.

Return values:

Recommended parameters:

Parameter setting example:

PHFMWREV = -t 86400 -c 1 -w 0 -a 0 -T "Firmware revision number"

Remarks: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

PHBOLREV returns the Bootloader revision of the device.

Return values:

Recommended parameters:

Parameter setting example:

PHBOLREV = -t 86400 -c 1 -w 0 -a 0 -T "Bootloader revision number"

Remarks: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

PHINP1AV to PHINP1AV return sensors INPUT1 to INPUT2 availability than can be measure temperature, humidity or other analogue values.

Possible values: active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6)

Return values:

Recommended parameters:

Parameter setting example:

PHINP1AV = -t 300 -c 0 -w 2 -a 2 -T "Sensor 1 Availability"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHINP1VL to PHINP2VL return INPUT1 to INPUT2 values than can be temperature, humidity or other analogue values.

Return values:

Recommended parameters:

Parameter setting example:

AMINTEMP = -t 300 -c 0 -w 0 -a 0 -T "Sensor 1 value"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHPDU1AV to PHPDU2AV return PDU1 to PDU2 availability.

Possible values: active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6)

Return values:

Recommended parameters:

Parameter setting example:

PHPDU1AV = -t 300 -c 0 -w 0 -a 0 -T "PDU1 Availability"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHPDU1PO a PHPDU2PO return PDU1 to PDU2 power RMS Volts value in volts.

Return values:

Recommended parameters:

Parameter setting example:

PHPDU1PO = -t 300 -c 0 -w 245 -a 250 -T "RMS Volts value in volts"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHPDU1CU to PHPDU2CU return PDU1 to PDU2 current value in RMS current value in 0.1 Amps.

Return values:

Recommended parameters:

Parameter setting example:

PHPDU1CU = -t 300 -c 0 -w 110 -a 120 -T "RMS current value in 0.1 Amps"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHPDU1TE to PHPDU1TE return PDU1 to PDU2 total energy value in 0.1 kWh.

Return values:

Recommended parameters:

Parameter setting example:

PHPDU1TE = -t 300 -c 0 -w 480000 -a 500000 -T "Total energy value in 0.1 kWh"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHPDU1KV to PHPDU2KV return PDU1 to PDU2 Kilo Volt-Amperes value in 0.1 kVA.

Return values:

Recommended parameters:

Parameter setting example:

PHPDU1KV = -t 300 -c 0 -w 45 -a 55 -T "Kilo Volt-Amperes value in 0.1 kVA"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHPDU1KW to PHPDU2KW return PDU1 to PDU2 Kilo Watts value in 0.1 kW.

Return values:

Recommended parameters:

Parameter setting example:

PHPDU1KW = -t 300 -c 0 -w 45 -a 55 -T "Kilo Watts value in 0.1 kW"

Remarks: This event uses the Osmius SNMP interface which in turn uses Net-SNMP libraries.

PHUSER01 to PHUSER10 launches a SNMP get using the provided parameters. If the oid result is numeric this event returns a numeric value. If the oid result is a string this event returns 1 when everything is ok and the string within the event text. If something fails the returned value is 0.

Extra parameters:

Return Values:

Recommended Parameters:

Parameter setting example:

PHUSER01 = -t 300 -c 1 -w 0 -a 0 -T "Product data signature" -O ".1.3.6.1.4.1.3711.24.1.1.99.0" -K secret_community -P 177 -Q 3 -V 1

Remarks: The associated SNMP text will be into the event text.
This event uses the Net-SNMP libraries

Here is briefly the capabilities of this agent about its trap events, further down on this page we will describe each of the trap events in more detail.

This Agent only need one trap event because all powerhawk2 threshold alarms (current, temperature, humidity, etc..) use these same three traps: trapCritical, trapWarning and trapCleared.

• TRAP: .1.3.6.1.4.1.3711.24.0.1
• DESCRIPCIÓN: trapCritical
• VARBINDS: trapCode: Decimal number to be carried on notifications identifying the event which caused it.
  trapDescription: A string to be carried on notifications identifying the event which caused it.
• SEVERITY: 2 → Critical.

• TRAP: .1.3.6.1.4.1.3711.24.0.2
• DESCRIPCIÓN: trapWarning
• VARBINDS: trapCode: Código que distingue el tipo de alarma
  trapDescription: Descripción de la alarma
• SEVERITY: 1 → Warning.

• TRAP: .1.3.6.1.4.1.3711.24.0.4
• DESCRIPCIÓN: trapCleared
• VARBINDS: trapCode: Decimal number to be carried on notifications identifying the event which caused it.
  trapDescription: A string to be carried on notifications identifying the event which caused it.
• SEVERITY: 1 → OK.

• TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
• DESCRIPCIÓN: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
• VARBINDS: No
• SEVERITY: 0 → OK.

In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.

In this particular agent you must also install Net-SNMP librares (Ubuntu “libsnmp”) that can be found here: http://net-snmp.sourceforge.net/ and in you OS repositories.

• Make Project Creator (MPC) is used by Osmius, so creating Makefiles is a trivial task. If you want to learn more about MPC and Osmius check out the section of Makefiles on Osmius.

• In order to compile this agent we need include files and libraries provided by Net-SNMP (Ubuntu “libsnmp-dev”).

• You can generate the Makefile in this way:

From the agent directory using console or terminal.

$ACE_ROOT/bin/mpc.pl -type gnuace osm_ag_POWRHAWK.mpc

• Now that you have created the Makefile, agent compiling is extremely simple.

make -f Makefile.Osm_Ag_POWRHAWK_Osmius

Binaries are automatically installed in the bin directory of OSM_ROOT base directory.

The Osmius POWRHAWK Agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.

Without Osmius web console:

The Osmius POWRHAWK Osmius agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests.

Basically you have to add a new value, called SNDCMD, to Osmius agent configuration file (osm_ag_POWRHAWK.ini) as shown here.

Setting Master Agent communications port to zero, for example:

Test performed to POWRHAWK Osmius agent.