SNMP Request Agent Configuration

Owned by Jenni Wallin
Last updated: Mar 31, 2023 by Former user (Deleted)
4 min read

You open the SNMP Request agent configuration dialog from a workflow configuration: you can right-click the agent icon and select Configuration..., or double-click the agent icon.


SNMP Request Tab

This tab contains the configuration required to select the target UDR fields from the MIB modules defined in the SNMP Collection profile. You can either select to configure the UDR fields to poll directly in the agent configuration by referencing and SNMP Collection profile, or you can create an OID profile for this and then configure the agent to reference the OID profile instead. Using an OID profile will allow several agents to use the same configuration and the configuration only needs to be maintained in one place. You can also select to use different SNMP OID profiles for different workflow instances in the same workflow configuration.

The network elements that are going to be polled, must be listed in a network element CSV file. The file should be located on the EC host, where you are going to execute the SNMP workflows.

SNMP Request agent configuration dialog - SNMP Request tab


SettingDescription
Profile TypeSelect which profile type you want the SNMP Request agent to use; an SNMP Collection profile or an SNMP OID profile.

SNMP Collection Profile

Select the SNMP Collection Profile.

Full Path

The full path to the network element file, including directory at the EC where the Network Element File file is located and the file name. The file should be in CSV format.


Poll/Field/Instances
(only available when having selected SNMP Collection as profile type) 

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 then be sent out.

Do not enable this, if you want to send out dynamic requests from APL to that OID by using the generated structure.

Network Element File

The Network Element File holds the list of Network Elements to poll. The file should be in CSV format.  After the IP address or FQDN of your target network element you can specify a number of parameters, see below. The IP-address or FQDN of target network element is mandatory parameter. The rest of parameters (see below) are optional. So if you skip them the agent will use the default settings from selected SNMP Collection Profile.

Order of parameters in Network Element File

CSV_COMMUNITY,
CSV_DESCRIPTION,
CSV_VERSION (1-SNMPv1, 2-SNMPv2c, 3-SNMPv3),
CSV_TIMEOUT,
CSV_RETRIES,
CSV_USER,
CSV_CONTEXT_NAME,
CSV_CONTEXT_ENGINE_ID,
CSV_AUTH_PROTO (1-None, 2-MD5, 3-SHA1),
CSV_AUTH_PASSWORD,
CSV_PRIV_PROTO (1-None, 2-DES, 3-AES),
CSV_PRIV_PASSWORD

The format of the Network Element File

This is an example of how a Network Elements CSV file can look like: (In this case 4 Network Elements are using IP addresses and one is defined using FQDN)

10.46.48.104,public,,2,10000,3,initial,,,3,12345678,1,12345678
10.46.48.108,public,,2,10000,3,initial,,,3,xxxxx,,
10.46.48.33
10.46.48.177,public,,2,5000,20,initial,,,3,abc123,1,12345678
Router_abc,public,,2,10000,3,initial,,,3,xxxxx,,

The network element file is checked for changes every 10 seconds. If the file is updated, the information will be reloaded into executing workflows without need to restart the workflow.e

Adding UDR Fields

Click on the Add new UDR field button and the OID UDR Browser dialog appears. Select the UDR fields you want to poll. You can add several UDR fields. Click OK or Apply to add selected fields.

Dynamic requests - SnmpRequestUDR

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 will make the response have the flattened OID - Value form
  • tree (boolean) - Set to true to make the request a tree request, which will retrieve the entire subtree 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, but can be either 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.

Using an OID Profile

If you want the OID configuration, i e UDR types and fields to be polled, to be available for several agents, you can select to create an SNMP OID profile. See SNMP OID Profile for further information.