AlphaSense SNMP Features

All models in the AlphaSense For Networks product family, except the AFN Express, support the SNMP features described below. In summary, these AlphaSense models 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 to a user-designated destination as an additional messaging option. Here are the AlphaSense SNMP feature details:

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 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 are already present and awaiting processing.

For message 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 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 as an SNMP trap to a specified IP and port recipient. This choice may be made in addition to or instead of other supported messaging delivery options such as network email, or modem dialout.

The delivery destination, if SNMP trap delivery is desired, is set using the ruleset snmpip field and is entered either as ipaddress or ipaddress:port. For most all applications, no port needs to be specified; which means the default port will be used.