AlphaSense SNMP Features

All models in the AlphaSense For Networks product family, except the AFN Express, support the SNMP inbound and outbound features described below. In summary, these AlphaSense models and feature packages are able to receive SNMP traps from devices located anywhere which are SNMP-enabled, and turn them into messages using normal AFN ruleset processing. And, message data resulting from any AlphaSense input source may be delivered out as an SNMP trap, notification, or inform PDU to a user-designated manager destination as an additional messaging option. Here are the AlphaSense SNMP feature details:

It should be noted that in current AFN firmware, SNMP agent support does not exist for query or variable-setting functions such as snmpget, snmpwalk, or snmpset. The AFN MIB file contains some elements for this, which may be implemented in a future firmware version. Customer comments and feature requests are always a part of our product development decisions, so if there is something you would like, we encourage you to communicate it to us.

SNMP traps directed to the IP address of an AFN unit are received on the standard port. They are parsed into raw elemental data, and each trap OID data element is submitted to the AFN ruleset processing system to be evaluated for messaging. Trap data is processed immediately upon reception for up to 25 elements. All remaining trap data elements are then queued, and the next 25 are processed during the next AFN firmware job-stack loop. The overall time of the loop varies with workload, but typically is 2-3 seconds. New traps may be received at any time, and are either processed immediately, or added to the queue if more than 25 previous trap data elements are already present and awaiting processing.

For ruleset processing, any partial portion of the "OID = value" pair can be used as actrule content to detect and trigger messaging for either a desired specific OID (or group of), or specific value (varbind) contents. Unique portions of the origination IP could also be used of course, and since AFN supports Regex in the actrule field, powerful combinations can be made. As always, shorter actrule lengths are better.

AFN models that support SNMP features can send message content using 3 types of SNMP message formats - v1 Trap, v2c Notification, and v2c Inform. The Inform type expects a response to validate that the message was received. If no response is received within the few-seconds timeout period, AFN will look for a ruleset having its activeflag set to 7, and process further messaging in accordance with the contents of that rule. The imaddr field in a given ruleset indicates the type and destination for the SNMP delivery, as explained in the imaddr and activeflag descriptions in the ruleset help file. The choice for SNMP message delivery may be made in addition to or instead of other supported messaging delivery options such as instant messaging, network email, or modem dialout.

As can be seen in the AFN MIB file, all trap, notification, and inform messages sent by AFN are packaged under an OID that is unique to the originating data source to further assist processing by the receiving manager system. The OID separations at its final afnTraps OID element are as follows: