...
| Setting | Description |
|---|---|
| Profile Type | Select 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, |
| 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 |
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
| Excerpt |
|---|
Adding UDR FieldsClick 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
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).
|
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 9.75.3 SNMP OID Profile for further information.
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||