Designing and Managing Behavior Models
-
Configuring SNMP Settings for Nodes - Manually Changing the SNMP Version Used to Manage a Node -
NerveCenter must use different SNMP protocols to communicate with the different versions of SNMP agents. Most often, you will want NerveCenter to classify the SNMP version for nodes when they are added to your database. You can, however, manually change the version that NerveCenter uses for communicating with a particular node.
You might want to change the version manually, for example, if the node supports SNMP versions v1, v2c, and v3, and the version currently assigned -say it's SNMP v3 -- is not configured correctly at the agent. Rather than continue sending SNMP v3 polls that may generate numerous alarms, you can temporarily change the node's SNMP version to v2c (which is supported on the node) until you have a chance to reconfigure the v3 information at the agent. With this change, you can still poll the node for certain MIB variables defined in your behavior models and continue monitoring minimal MIB information for the node.
This feature also provides a way to override the maximum version classification value configured in NerveCenter Administrator. For example, say the maximum classification value is v2c, you can specify SNMP v3 for a particular node and run a test poll against that node.
To change a node's SNMP version manually:
From the client's
Admin
menu, select Node List
.
The Node List window is displayed.
New
if defining a new node, or select the node and then Open
to change an existing node.The Node Definition window appears.
SNMP Version
list box.
Remember that if you select Unknown
or a version that's incorrect, NerveCenter can not poll
the node or process traps from the node.
Save
button. Configuring SNMP Settings for Nodes | Changing the Security Level of an SNMP v3 Node |
29 July 2003 |