Access Keys:
Skip to content (Access Key - 0)


2 Managing the Status of the SNMP Agent

Print this page

To display the status, active, deactivate, and restart the SNMP agent...

...use the following rhino-console commands:

snmpstatus

What it does Displays the status of the Rhino SNMP agent.
Example The initial status for a freshly installed single-node cluster looks like this:
Output What it means
SNMP Status
============

Agent status: enabled 
The current state of the Rhino SNMP Agent. Note that this should be considered the "desired" state of the agent and not the actual state of the SNMP agents for each cluster node. Individual SNMP agents on different nodes may have a different state, for example if a failure during startup (such as an port being unavailable) prevented an agent from starting.
Agent details:
 Name: Node ${node-id}
 Description: OpenCloud Rhino
 Location: Unknown location
 Contact: OpenCloud Support (support@opencloud.com)
Descriptions for the SNMP agent when queried, corresponding to the sysName, sysDescr, sysLocation, and sysContact variables from the SNMPv2 MIB. Any system property string (in the form ${property.name} will be replaced, on a per-node basis, so node-specific information can be included (if required). The ${node-id} property is special, and will be substituted with the node ID of the node the agent is running on.
 Enabled versions: v1, v2c, v3
The versions of SNMP currently enabled.
SNMP v1/v2c details:
 Community: public
The current configuration for SNMP v1/v2c.
SNMP v3 details:
 Username:         rhino
 Auth Protocol:    SHA
 Auth Key:         password
 Privacy Protocol: AES128
 Privacy Key:      password
 EngineBoots:      3
 EngineTime:       814
The current configuration for SNMP v3. This configuration is used for both statistics collection and notification delivery.
Network:
 Default subnet: 0.0.0.0/0
 Default port range: 16100-16200
 Loopback addresses: ignored
 Address bindings: not saved
 Port bindings: saved
How the SNMP agent responds to automatic port and interface discovery for newly booted Rhino nodes.
 Notifications: enabled
Whether to generate notifications.
Notification configuration
==========================
 Notification targets:
   v3:udp:127.0.0.1/163
   v2c:udp:127.0.0.1/162
Where notifications will be sent (if enabled and not filtered).
 TraceNotification                                  forwarded
 UsageNotification                                  forwarded
 ResourceAdaptorEntityStateChangeNotification       forwarded
 LogNotification                                    forwarded
 SleeStateChangeNotification                        not forwarded
 ServiceStateChangeNotification                     forwarded
 LogRolloverNotification                            forwarded
 AlarmNotification                                  forwarded
Which types of notifications will be sent.
Saved per-node configuration
=============================
 101 <default>:16100
 102 <default>:16101
Persisted per-node state of the SNMP system; used to determine what ports/interfaces the SNMP agent for each node should bind to on startup.
Per-node agent status
======================
 101 Running 192.168.0.7:16100
 102 Running 192.168.0.7:16101
State of the SNMP agent on each node; includes the actual state of the agent, which may differ from the persisted or desired state.

activatesnmp

What it does Activates the Rhino SNMP agent

deactivatesnmp

What it does Deactivates the Rhino SNMP agent

restartsnmp

What it does Deactivates (if required) and then reactivates the Rhino SNMP agent

If SNMP agent could not be started successfully, alarms will be raised. Check active alarms using listactivealarms console command for detail.

Adaptavist Theme Builder Powered by Atlassian Confluence