In our environment, we setup the monitoring device to send SNMP traps to SolarWinds. The traps include alarms and notifications.
It is observed that SolarWinds will send GET-NEXT-REQUEST to the device in responding to the notifications. The GET-NEXT-REQUEST used the community in the notifications but not the community that setup for active monitoring. As the community in the notification does not allow read or write SNMP operation, it is observed that SolarWinds repeatedly send out the same GET-NEXT-REQUEST and delayed the processing of other traps received.
Is there is any way / parameters to configure SolarWinds not to send out GET-NEXT-REQUEST in responding to the notifications received ?
Regards
Antony

