To enable, disable, and specify where to send SNMP notifications, use the following rhino-console commands.

enablesnmpnotifications

Command

 
enablesnmpnotifications
  Description
    Enables SNMP notification sending (while the SNMP agent is active).

disablesnmpnotifications

Command

 
disablesnmpnotifications
  Description
    Disables SNMP notification sending.

addsnmptarget

Command

 
addsnmptarget <v2c|v3> <address>
  Description
    Adds the target address for SNMP notifications.

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
Note Specify addresses as udp:address/port. Currently supports udp transport only.

removesnmptarget

Command

 
removesnmptarget <target>
  Description
    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

Command

 
listsnmpnotificationtypes
  Description
    Lists the notification types supported for SNMP notification type filtering.

Example

To list notification types:

[Rhino@localhost (#1)] listsnmpnotificationtypes
Supported SNMP Notification types:
  AlarmNotification
  LogNotification
  LogRolloverNotification
  ResourceAdaptorEntityStateChangeNotification
  ServiceStateChangeNotification
  SleeStateChangeNotification
  TraceNotification
  UsageNotification

setsnmpnotificationenabled

Command

 
setsnmpnotificationenabled <type> <true|false>
  Description
    Specifies whether the notification type should be forwarded by the SNMP
    subsystem.

Example

To disable SleeStateChangeNotification delivery:

[Rhino@localhost (#4)] setsnmpnotificationenabled SleeStateChangeNotification false
SNMP notifications for type 'SleeStateChangeNotification' are now disabled.
Warning These settings have no effect if SNMP notification delivery is disabled globally.

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.

Warning LogNotification and, to a lesser degree, TraceNotification will cause performance degradation due to additional platform load.
Note
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.
Previous page Next page
Rhino Version 2.6.0