To enable, disable, and specify where to send SNMP notifications, use the following rhino-console commands.
enablesnmpnotifications
What it does  | 
Enables SNMP notifications. Rhino then forwards any notifications it generates to the target specified by the addsnmptarget command.  | 
|---|
addsnmptarget
| 
 | 
 Introduced in Rhino 2.3 
With removesnmptarget, replaces   | 
Argument  | 
<v2c|v3> <address>  | 
||
|---|---|---|---|
What it does  | 
Adds a target address for SNMP notification delivery.  | 
||
Example  | 
To send version v2c notifications to 127.0.0.1 port 162: [Rhino@localhost (#8)] addsnmptarget v2c udp:127.0.0.1/162 Added SNMP notifications target: v2c:udp:127.0.0.1/162 
  | 
removesnmptarget
| 
 | 
 Introduced in Rhino 2.3 
With addsnmptarget, replaces   | 
Argument  | 
<target>  | 
|---|---|
What it does  | 
Removes the specified SNMP notification target.  | 
Example  | 
To remove a target: [Rhino@localhost (#10)] removesnmptarget v2c:udp:127.0.0.1/162 Removed SNMP notifications target: v2c:udp:127.0.0.1/162  | 
listsnmpnotificationtypes
What it does  | 
Lists the valid SNMP notification types for use with setsnmpnotificationenabled command.  | 
|---|---|
Example  | 
To list notification types: [Rhino@localhost (#1)] listsnmpnotificationtypes Supported SNMP Notification types: AlarmNotification LogNotification LogRolloverNotification ResourceAdaptorEntityStateChangeNotification ServiceStateChangeNotification SleeStateChangeNotification TraceNotification UsageNotification  | 
setsnmpnotificationenabled
Argument  | 
<type> <true|false>  | 
||
|---|---|---|---|
What it does  | 
Enables or disables SNMP notification delivery for the specified notification type.  | 
||
Example  | 
To disable  [Rhino@localhost (#4)] setsnmpnotificationenabled SleeStateChangeNotification false SNMP notifications for type 'SleeStateChangeNotification' are now disabled. 
  | 
The notification types that can be configured to generate SNMP traps are:
- 
AlarmNotification
 - 
LogNotification
 - 
LogRolloverNotification
 - 
ResourceAdaptorEntityStateChangeNotification
 - 
ServiceStateChangeNotification
 - 
SleeStateChangeNotification
 - 
TraceNotification
 - 
UsageNotification
 
Frequently it is desired to only send SNMP traps for AlarmNotification and UsageNotification.
In other cases ResourceAdaptorEntityStateChangeNotification, ServiceStateChangeNotification and SleeStateChangeNotification are also desired.
| 
 | 
LogNotification and, to a lesser degree, TraceNotification will cause performance degradation due to additional platform load.
 | 
| 
 | 
 Notification configuration and snmpstatus 
Below is an example of output from the snmpstatus command showing notification configuration. Notification configuration ========================== Notification targets: v2c:udp:127.0.0.1/162 v3:udp:127.0.0.1/163 TraceNotification forwarded UsageNotification forwarded ResourceAdaptorEntityStateChangeNotification forwarded LogNotification forwarded SleeStateChangeNotification forwarded ServiceStateChangeNotification forwarded LogRolloverNotification forwarded AlarmNotification forwarded  | 
Thread pooling
By default, Rhino uses a thread pool for SNMP notifications.
The pool can be configured by setting the notifications.notification_threads system property.
Value  | 
Effect  | 
|---|---|
0  | 
Disable notification threadpooling, use same thread.  | 
1  | 
Default, a single dedicated thread for notification delivery.  | 
>1  | 
Threadpool of N threads for notification delivery.  | 
