SNMP OID (3.0)
With the SNMP OID profile, you can configure which OIDs, that is UDR types and fields to poll, outside of the SNMP Request agent itself. This way, several agents can use the same configuration.
Configuration
To create a new SNMP OID profile configuration, click the New Configuration button in the upper left part in Desktop, and then select SNMP OID Profile from the menu.
The SNMP OID profile configuration contains the following settings:
| Setting | Description |
|---|---|
SNMP Collection Profile | Select which SNMP Collection profile the OID profile should use. |
| Poll/Field/Instances | Add the UDR types and fields you want to have available for polling in this section, and select the Poll check box for the ones you want to poll. Continuous requests for the specified OIDs will be sent out. Do not enable this if you want to send out dynamic requests from APL to the OID by using the generated structure. |
Adding UDR Fields
Click on the Add new UDR field button and the OID UDR Browser dialog appears. Select the UDR fields to poll. You can add several UDR fields. Click OK or Apply to add selected fields.
Sometimes the exact OID to request is not known in advance. For instance, the OID string can be composed from a base OID part and an instance part that is the value of a previous response message. A dynamic request can then be performed by creating an SnmpRequestUDR from APL and routing it to the SNMP collection agent.
You create an SnmpRequestUDR in APL and configure it by setting:
- remotehost (string) - The address of the network element to request.
- remoteport (int) - The port of the network element to request.
- community (string) - The community string to be used in the request.
- baseoid (string) - The base part of the OID to request.
- instanceoid (string) - The instance part of the OID to request.
- unresolved (boolean) - Set to true to make the request an unresolved request, which makes the response get the flattened OID - Value form.
- tree (boolean) - Set to true to make the request a tree request, which retrieves the entire sub tree from the specified OID. Works only for unresolved requests.
The UDR is then routed to the SNMP Request agent. This triggers a request to the specified host + port using the specified OID and community string. The response is received as usual, in the flattened unresolved form or in the hierarchical UDR structure, depending on whether the unresolved flag was set in the request or not. For resolved requests, the specified OID must be in the SNMP Collection profile. The specified host + port + community must be included in the list of network elements (CSV file + profile input).
SnmpRequestUDR example: hrSWRun.zip. Download this export and import it to see an example on how dynamic, triggered requests can be used.