|Applies To||RSA Product Set: NetWitness Logs and Packets, NetWitness NextGen (Legacy), Security Analytics|
RSA Version/Condition: 9.6.x and above
|Issue||How to configure SNMP traps in RSA NetWitness NextGen and RSA Security Analytics.|
Once the SNMP agent has been enabled, following the instructions in the knowledgebase article How to enable SNMP in RSA NetWitness NextGen 9.6 and above or in RSA Security Analytics, how do I configure it to send SNMP traps?
Follow the instructions below to configure SNMP traps for the appliance. The examples provided are for a Decoder but apply the same to Concentrators and Brokers.
The screenshots also depict the RSA NetWitness Administrator thick client, but is comparable to the Explore view in RSA Security Analytics.
4. Navigate to /logs/config/log.snmp.agent. Enter the IP address of your SNMP trap receiver into the right-hand column.
5. SNMP traps can be generated when an integer statistic reaches a low or high-watermark. Locate a statistic that you would like to alert on in explorer view. Take for instance /decoder/stats/capture.dropped.percent. You will see both a 'Low' and a 'High' column next to the statistic. If you wish to alert when the dropped packet percentage exceeds 5%, double-click on the 'High' column and enter the number 5. Now, if the Decoder's dropped percentage rate exceeds 5%, it will send an SNMP trap.
Another example: to alert when the capture rate drops below a certain threshold, say 50 mbps, set the 'Low' value for /decoder/stats/capture.rate to 50.
6. To alert when a text statistic changes, i.e. /decoder/stats/capture.started, enter the state you would like to alert on in the 'Low' field. For instance, if you would like to alert when capture is in a stopped state, type 'stopped' into the 'Low' field.
|Notes||Note 1: As of version 18.104.22.168, there is no capability to customize the SNMP community string for traps.|
Note 2: SNMP trap messages are sent via UDP port 162. This cannot be customized.
Note 3: As of version 22.214.171.124, string comparisons are only capable of equality logic, but not inequality, meaning that it cannot be configured to alert when capture.started does NOT equal 'started'. Inequality logic functionality may be added in a future NextGen release.
|Legacy Article ID||a58872|