Non-sample based Rhino statistics (all gauges and counters) that are registered according to the legacy OID model are accessible via SNMP tables.

SNMP Table Structure

Each SNMP table represents a single parameter set type. The values in each SNMP 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 "(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 legacy OID model registered example Usage.Services.SbbID[name=UsageTestSbb,vendor=OpenCloud,version=1.0] parameter set type’s representation in the SNMP agent as OIDs: = INTEGER: 2 = STRING: "Services.S-7cb11624-,vendor=OpenCloud,version=1.0].(default)" = STRING: "[Services.S-f36d2ae2-ageTestSbb,vendor=OpenCloud,version=1.0]" = Counter64: 0 = Counter64: 0 = Counter64: 0 = Counter64: 0

What the colors represent
  • Blue: The base OID for the Usage.Services.SbbID[name=UsageTestSbb,vendor=OpenCloud,version=1.0] parameter set type. This can be either statically or dynamically set.

  • 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. This example has substituted the OID representation of the table index with the TestSBBTableIndex and TestSBBTableIndex.(default) variables.

  • Purple: The raw statistic values.

The OID representation of the table indices in this example is as follows:

  • TestSBBTableIndex is the string Services.S-f36d2ae2-ageTestSbb,vendor=OpenCloud,version=1.0] stored in an OID representation as:
  • TestSBBTableIndex.(default) is the string Services.S-7cb11624-,vendor=OpenCloud,version=1.0].(default) stored in an OID representation as:

These table indices have parameter set names that are longer than 255 characters. Therefore, the stored representation is truncated, leading to the -f36d2ae2- and -7cb11624- gaps in the decoded strings.


For static model non-statically mapped parameter sets and legacy model parameter sets, 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 that store SNMP statistics in files named after the index OID.


For usage parameter set types, the base OID and individual statistics can be specified in annotations described in Annotations. For statistics 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.

Previous page Next page
Rhino Version 3.2