Observer Analyzer : Observer Analyzer : SNMP Management Console : Using the MIB editor : Adding, modifying, and deleting SNMP agents
Adding, modifying, and deleting SNMP agents
To collect information from your SNMP-enabled network devices, you must add an agent entry for each SNMP agent on your network.
To add a new SNMP agent entry:
On the Home tab, in the Probe group, click Setup > Add SNMP Device.
 
Name
Name that is displayed to the right of the agent icon in the SNMP Agents list. Enter any descriptive name.
IP Address
IP address of the SNMP agent you want to add.
Device type
A request file based on the RFC1213 standard MIB request file is included with SNMP Extension. Click the browse (…) button to browse the desired request file.
Comment
Allows you to fill in any comment you want here.
SNMP Version
SNMP Management Console supports both SNMPv1, SNMPv2, and SNMPv3. SNMPv2 includes a superset of the SNMPv1 features. SNMPv3 adds security and encryption to SNMPv2, while remaining backward compatible with SNMPv1 and SNMPv2. Some SNMP devices do not support SNMPv2 and SNMPv3. If in doubt, leave this setting at the default, SNMPv1.
Security user name
Provide the user name by which Observer will access the agent.
Context engine ID
The context engine ID uniquely identifies the SNMP entity; check the HEX box if you wish to enter the string as a hexadecimal entry (for example, 80 FF 00).
Community/context name
The community name. This is typically public. By convention, SNMP uses the community name and management station IP address the same way login name and password are used in a Telnet (terminal) session.
Some SNMP agents will respond to a menu request only if the management station IP address exists in the agent's list and if the request contains the proper password.
In SNMPv1 and SNMPv2, the community string provides rudimentary password protection. To remain accessible to any SNMP station, most SNMP agents use the default community name public.
If you do not specify the correct community name (or, in the case of those agents who maintain an IP address table, if your SNMP Management Console IP address is unknown to the SNMP agent), the agent will not respond to your requests. SNMP Management Console will re-send the request until it times out.
If you are polling the SNMP agent for the first time, a failure to respond may be caused by any one, or more, of the following:
The SNMP agent is up and running, but SNMP Management Console is not entered as a management station in the agent's database.
The community name is wrong.
SNMP services are not enabled on the device.
The SNMP agent's device is down.
If you have previously successfully polled the SNMP agent, only the last one is possible, unless the configuration of the SNMP agent’s device has changed.
Table 32. SNMP security options
Apply USM key localization to passwords
USM key localization allows a principle to share unique authentication and encryption key with each remote engine, while maintaining only a single set of keys locally.
Authentication protocol menu
Specifies the mechanism used for authentication: noAuth (none), HMAC - MD5, HMAC - SHA1
Authentication password (key)
The password used for authenticating users.
Privacy protocol
Specify the encryption method to use when transferring data between the agent and the management console.
Privacy password (key)
Specify the password to use when transferring data between the agent and the management console.
Authentication time window (seconds)
When messages are delivered outside the time window, SNMPv3 security will not process them. This provides a way of ensuring that previously captured messages are not being replayed.
Notify on Trap/Alarm:
e-mail address—allows you to enter the e-mail address to send notifications to (from traps or alarms for this agent).
This is a different issue from the IP address (of the computer running Observer with SNMP Extension) to which the SNMP agent itself is to send traps. In this case, you are specifying the e-mail address of the person who is to be notified when a trap message is received by SNMP Extension.
Time to log data (24 Hour Clock):—You can choose to have device data logged all the time, or schedule times to collect and log data on particular days of the week within particular hours.
Keep polling even if not logging Chart Request data—Check this box to have the SNMP agent poll the device even if it is not logging chart request data.