What fields should I enter when connecting to a SNMPv3 agent?
Getting an error "Received engineID xxx does not match the configured engineID yyy" when I open a previously saved agent configuration file.
Q What fields should I enter when connecting to a SNMPv3 agent?
A To do proper SNMPv3 testing, there must be a configured SNMPv3 user in the agent you wish to test with a full view of the MIB and full privileges. Each network device has its own way of configuring agents. This process is independent of SilverCreek.
Though you may connect as a noAuth/NoPriv user, to reap the full benefits of our tests we recommend that you configure and use an auth/priv user.
Enter the SNMPv3 information in the New Agent Dialog in SilverCreek found under the file menu. In the New Agent Dialog, at a minimum, you should enter:
1. The IP Address of the agent to be tested.
2. Select SNMPv3 protocol
3. Enter the username as configured in your agent
4. The corresponding authentication and privacy passcodes (if any) and algorithms.
If the v3 user does not require privacy (encryption), then simply leave the priv pass field blank.
If the v3 user does not require authentication, then simply leave the auth pass field blank.
At this point SilverCreek will go through several steps to obtain the information it needs from the agent so it can do proper key localization and communicate successfully. The following steps occur automatically without any interaction needed from you, the tester. However, it is useful to be aware of how the localization occurs for debugging purposes in case you run across difficulties.
The following steps will occur:
1. SilverCreek sends a get-next on 'sysDescr' with the EngineID = NULL, engineBoots = 0 and engineTime = 0.
2. SilverCreek should receive an usmStats UnknownEngineIDs report from the agent being connected to.
3. At this point, key localization occurs, using the Authoritative Engine ID obtained from the report returned from your agent that is acting
as the Authoritative Engine.
4. SilverCreek sends a get-next on sysDescr with EngineID = 'the received value', engineBoots = 0 and engineTime = 0.
5. SilverCreek receives a usmStatsNotInTimeWindows report from the agent being connected to.
6. SilverCreek sends a get-next on 'sysDescr' with EngineID, engineBoots and engineTime all containing received values.
7. SilverCreek receives a get-response with the values of sysDescr.0 and considers the context successfully connected to.
Hints & Tips
Below are a few tips for your information and common problems:
1. Entering a localized key in non-hex format. If you are entering an already localized key into the SilverCreek Agent Setup, it must be entered in strict hex form (for example 0x11:22:33...). If it is entered in any other format, the tool will assume it is not localized and attempt to localize it.
2. Receiving an Error Report (this is generated by your agent not by SilverCreek!): "Error usmStatsWrongDigests.0 report selecting agent."
This may indicate that the digest contained in the request (this is the calculated digest) differs from the digest calculated by the agent using the auth secret key. Try comparing the auth/priv keys derived at both ends (your agent and SilverCreek). Any difference in these keys indicates an incorrect configuration.
3. Receiving an Error Report (this is generated by your agent not by SilverCreek!): "Errors snmpUnknownPDUHandlers.0 report selecting agent."
This may indicate that the agent does not support the GET-NEXT request sent by SilverCreek.
4. Receiving an Error Report (this is generated by your agent not by SilverCreek!): "Error usmStatsUnsupportedSecLevels.0 report selecting agent.
This may indicate that the agent does not support the specified security level specified in the GET-NEXT request.
5. Receiving an Error Report (this is generated by your agent not by SilverCreek!): "Error usmStatsUnknownUserNames.0 report selecting agent."
This may indicate that the agent does not have a user name configured locally as specified in the GET-NEXT request.
QGetting an error "Received engineID xxx does not match the configured engineID yyy" when I open a previously saved agent configuration file
A SilverCreek fails to connect to the agent and reports an error window:
Received engineID 0x80:00:0c:62:03:00:00:2a:4b:e4:8a does not match the configured engineID 0x80:01:0c:62:03:00:00:2a:4b:e4:8a, please enter using 0x11:22:33... form or leave the Agent's engineID field blank and let the tool uses what is discovered
This is because the engineID contained in the agent configuration file is different from the current engineID value the agent has currently. Most like the agent had reset itself another engineID.
To resolve the issue please leave the agent's engineID field blank and let the tool uses whatever is going to be discovered
Want to Know More?