This section provides two examples that show how Rhino constructs OIDs from their constituent parts.

Example one

The first example uses a SIP resource adaptor to illustrate how all the pieces fit together to create the OID for a counter statistic.

The example makes the following assumptions:

  • A resource adaptor entity of the SIP resource adaptor called sipra is created, and its name is statically mapped to the OID suffix of 1.

  • The adaptor has a parameter set type called BigGroupStats, and this parameter set type has a counter called forksStarted. The following static OID information is defined for this counter:

    • The SIP resource adaptor has a base OID of 1.3.6.1.4.1.19808.20.2.1.

    • The BigGroupStats parameter set type has an OID suffix of 2.4.

    • The forksStarted counter has an OID mapping of 2.

Based on the OID structure, each part of the OID is as follows:

  • Base OID: 1.3.6.1.4.1.19808.20.2.1

  • Intermediate OID subtree suffix: This part doesn’t apply to resource adaptors.

  • Intermediate OID: 1

  • Usage parameter subtree suffix: 1

  • Usage parameter OID: 2.4 for the parameter set type and 2 for the counter.

Putting these together, Rhino registers the forksStarted counter of the BigGroupStats parameter set type that the sipra resource adaptor entity creates with the OID of 1.3.6.1.4.1.19808.20.2.1.1.1.2.4.2.

Example two

The second example still uses the base OID and the intermediate OID in the first example.

In this example, consider the Transactions parameter set type of the SIP resource adaptor. This type has a counter statistic called serverTransactionsActive, and the following static OID information is defined for this counter:

  • The TransactionStats parameter set type has an OID suffix of 2.2.

  • Some parameter set names are defined for the parameter set type TransactionStats, and one of these maps the parameter set name Transactions.INVITE to the OID suffix of 2.

  • The serverTransactionsActive counter in the Transactions.INVITE parameter set has an OID suffix of 9.

For the usage parameter OID, the value of the parameter set subtree suffix is 1 because the parameter set is non-singleton and the OID suffix of the parameter set is statically mapped.

Putting these together similarly, Rhino registers the serverTransactionsActive counter in the parameter set Transactions.INVITE of the Transactions parameter set type with the OID of 1.3.6.1.4.1.19808.20.2.1.1.1.2.2.1.2.9.

Previous page Next page