Below is an overview of the statistics and notifications available from the Rhino SNMP agent, and the OIDs they use.

SNMP statistics

The Rhino SNMP agent provides access to all non-sample based Rhino statistics (all gauges and counters), in the form of SNMP tables that each represent a single parameter set type. The values in each table represent statistics from the individual parameter sets associated with the table’s parameter set type. Each table uses the name of a parameter set, converted to an OID, as a table index. Individual table rows represent parameter sets, while the table columns represent statistics from the parameter set type. The first column is special, as it contains the parameter set index value as a string. For the purposes of SNMP, the name of the root parameter set for each parameter set type can be considered to be "(root)". All other parameter sets use their normal parameter set names, converted to OIDs, as index keys.

For example, the following output (generated using snmpwalk) shows the JVM parameter set type’s representation in the SNMP agent as OIDs:

. = INTEGER: 1
. = STRING: "(root)"
. = Gauge32: 96177712
. = Gauge32: 536674304
. = Gauge32: 536870912
. = Gauge32: 536674304
. = Gauge32: 27251608
. = Gauge32: 41299968
. = Gauge32: 19136512
. = Gauge32: 117440512
. = Gauge32: 4316
. = Gauge32: 4316
. = Gauge32: 0

What the colors represent
  • blue = The base OID for the JVM parameter set type.

  • yellow = A subindex for data associated with this parameter set type:
    .1 represents the parameter set count for this parameter set type.
    .2 represents the parameter set data table.

  • olive = a fixed number representing the table entry OID. This will always be .1.

  • green = Statistic columns. The first column (.1) represents the parameter set name for a given table row. The rest of the columns correspond to individual statistics.

  • red = The table index — in this case "(root)" converted into an OID is

  • purple = The raw statistic values.

Warning Exceptionally long parameter set names may be truncated if their OID representation is longer than 255 characters. This is to prevent pathname length problems with management clients which store SNMP statistics in files named after the index OID.
Note The statistics provided by this interface can be considered the "raw" statistics values for individual Rhino nodes. They will not in general reflect any activity which is occurring on Rhino nodes other than the one the SNMP agent is providing statistics for. Unlike the command-line statistics client, the SNNP agent does not collate statistics from other nodes.
Tip For usage parameter set types, the base OID and individual statistics can be specified in annotations described in Annotations. For stats parameter set type in resource adaptor, the base OID can be specified in element stats-parameter-set-type in oc-resource-adaptor-jar.xml. Otherwise, they will be dynamically allocated according to the range specified in Dynamic Rhino monitoring parameter sets.
Tip You can get the mapping of table columns to statistics by exporting the parameter set type specific MIB, using the Rhino command-line console.

SNMP notifications

The Rhino SNMP agent supports sending SNMP notifications to a designated host/port. It forwards the following, which include all standard JAIN SLEE 1.1 notifications, plus several Rhino specific notifications. See Configuring SNMP Notifications for instructions on how to configure Rhino to send SNMP notifications.

Notifications Sent when…​ Details Trap type OID (


…​alarms are raised or cleared (only once per alarm)

Resource Adaptor

…​an RA entity changes state


…​a service changes state


…​the SLEE changes state


…​a trace message is generated by a component


…​usage notifications required


…​log messages exceed a specified threshold

Logfile Rollover

…​a log file rolls over

The notification MIB structure is a set of SNMP variable bindings containing the time ticks since Rhino started, the notification message, type, timestamp, node IDs and additional data. These are also documented in the RHINO-NOTIFICATIONS.MIB file generated by rhino-console exportmibs.

Common Notification VarBinds (Notification argument data)

Name OID Description


Notification message. For alarms this is the alarm message text


Notification type. A notification type in dotted hierachical notation e.g. ""


An incrementing sequence number, indexed for each notification type


A timestamp in ms since 1-Jan-1970


The node IDs reporting this notification. An array of Rhino node IDs represented as a string [101,102,…​]


The source of the notification. This can be an SBB, RA entity or subsystem.


The namespace of the notification. The field will be an empty string for default namespace.

Component state change

Name OID Description


Old state of the component


new state of the component


ID of the component. This can be a service or RA entity name


Name OID Description


Alarm ID


Alarm level (Critical, Major, Minor, etc)


Alarm instance ID.


Alarm type ID. The value of this depends on the source of the alarm, for example a failed connection alarm from the DB Query RA would have a value like localhost (Oracle).


Name OID Description


Tracer level (Error, Warning, Info, …​)

Usage parameter notification (Rhino Statistics)

Name OID Description


Usage parameter name, one per parameter in the parameter set.


Parameter set name


Value of the usage parameter at the moment the notification was generated


Name OID Description


Log key


Log level (ERROR, WARN, INFO, …​)


Thread the message was logged from

Log file rollover

Name OID Description


The log file that was rolled over


The new name of the log file

A sample SNMP trap for an alarm follows. The OctetString values are text strings containing the alarm notification data.

Simple Network Management Protocol
    version: v2c (1)
    community: public
    data: snmpV2-trap (7)
            request-id: 1760530310
            error-status: noError (0)
            error-index: 0
            variable-bindings: 11 items
                    Object Name: (iso.
                    Value (Timeticks): 559356
       (iso. 1
                    Object Name: (iso.
                    Value (OID): (iso.
       44617461536f7572636520686173206661696c6564  2
                    Object Name: (iso.
                    Value (OctetString): 6a617661782e736c65652e6d616e6167656d656e742e616c...
       34 4
       31343634313535323331333630 5
       5b3130315d 6
       5241456e746974794e6f74696669636174696f6e5b656e74... 7
       3130313a313836363934363631333134353632 8
       4d616a6f72 9
       6c6f63616c686f737420284f7261636c6529 10
       646271756572792e64732e6661696c757265 11
1 Notification trap type OID: (Alarm)
2 Message: "DataSource has failed"
3 Notification type:
4 Sequence number: 34
5 Timestamp: 1464155231360
6 Node IDs: [101]
7 Source: RAEntityNotification[entity=dbquery-0]
8 Alarm ID: 101:186694661314562
9 Alarm level: Major
10 Alarm instance: localhost (Oracle)
11 Alarm type: dbquery.ds.failure
Log notification appender

Rhino 2.2 introduced a log notification appender for use with the SNMP agent. This appender will create notifications for all log messages above its configured threshold. These notifications will in turn be forwarded by the SNMP agent to the designated host/port. This is intended as a catch-all for any errors or warnings which don’t have specific alarms associated with them.

OID hierarchy

The Rhino SNMP agent uses the following OIDs. (All statistics and notifications that it provides use these OIDs as a base.)


OpenCloud Enterprise OID




Rhino Statistics


Rhino Notifications


Rhino Notification VarBinds

Previous page Next page
Rhino Version 2.6.2