Rhino includes an SNMP agent, for interoperability with external SNMP-aware management clients. The Rhino SNMP agent provides a read-only view of Rhino’s statistics (through SNMP polling) and supports sending SNMP notifications for platform events to an external monitoring system.
In a clustered environment, individual Rhino nodes will run their own instances of the SNMP agent, so that statistics and notifications can still be accessed in the event of node failure. When multiple Rhino nodes exist on the same host, Rhino assigns each SNMP agent a unique port, so that the SNMP agents for each node can be distinguished. The port assignments are also persisted by default, so that in the event of node failure or cluster restart the Rhino SNMP agent for a given node will resume operation on the same port it was using previously.
By default, Rhino enables the SNMP v1 and v2c protocols. You can query statistics by configuring a monitoring system to connect to port 16100 (or other port as noted above). To use SNMP v3, configure authentication and enable SNMP v3 first.
- Accessing SNMP Statistics and Notifications
- Exporting MIB Files
- Configuring and Managing the Rhino SNMP Agent
- Managing the Status of the SNMP Agent
- Configuring Authentication Details
- Configuring Port and Interface Bindings
- Setting SNMP System Information
- Configuring SNMP Notifications
- Managing Per-Node State
- Configuring OID Registration Model Support
- Viewing SNMP Static OIDs
- Configuring SNMP Legacy OID Mappings
- Configuring SNMP Legacy Counter Mappings
- Removing the Log Notification Appender
- Static OID Model
- Static OID Conflicts
- Legacy OID Model
- Differences between the static and legacy OID models
- Rhino SNMP OID Mappings
