The Troubleshooting tips for SMNPv3 Agents are as follows:
Time Sync Error in V3
Reason : A Time sync error occurs, when the agent is not configured for a particular user and we try doing a GET/SET request for that user. Say for example, after starting the agent, we give the following values in the MIB Browser v3 settings.
Target Host - localhost (by default)
Target Port - 8001
User Name - senior
Security Level - Auth,noPriv
Auth Password - senior
and "Add the Entry". You will get the time sync error as no such user senior exist by default.
Solution : Enter the correct UserName and password as provided in the USM user table
General Failure in V3
Reason : A general failure occurs when you add the user entries properly but do not give a context name or give a wrong context name in the MIB Compiler test tab. Also when view access in the MIB is restricted up to a particular OID, in the VACM Family View Table and you want to access it further.
Solution : Specify the exact context name.
Discovery Failure in V3
Reason : This error occurs when you try to add an user without the agent running. Of course, it is possible to add an agent with "noAuthnoPriv" security level as the agent will be treated as a v2c agent.
Solution : Start the Agent in the specified port before sending a query to the Agent.
Authorization Error
Reason : This error occurs when the security level and the context name contradicts each other. Say, you give the security level as "noAuthnoPriv" and the User Name as "auth". After adding the entry in the MIB Browser V3 settings , specify the context name in MIB Compiler test tab as "auth" and try doing a GET/SET request . An "authorization failure" error occurs.
Solution : Find out the cause of your problem from the above listed reasons and do the necessary changes.
Exceptions thrown - (class Cipher not found)
Reason : "Class not found" exceptions are thrown when we send a request for the private users (privUser). Though the entry gets added in the MIB Browser v3 settings, the exceptions are thrown in the command prompt. This happens when, the privacy packages required for v3 agent's private users are not present in the classpath. Please go through the privacy package settings in V3 for more information.
Solution : Ensure that the Privacy Packages settings are configured properly in the classpath.
End of MIB view error
Reason : You will get this error while trying to do a get-next for the v3 agent. For Example : If the context name provided in the Mib Browser if not the same as that configured in the vacmContextTable for that user. For example, the context name provided for the user authUserSHA in the vacmcontexttable is "auth". If this user tries to access the v3 agent by providing the context name as "noauth" in the Mib Browser.
Solution :Find out the cause of your problem from the above listed reason and do the necessary changes.
usmStatsNotInTimeWindows(.1.3.6.1.6.3.15.1.1.2.0)
Reason :The meaning of the error , "Not In Time Window" is when the sent request EngineTime and EngineBootCnt are different with the agent's EngineTime and EngineBootCnt. The possible reason is, the agent would have restarted.
Solution :The subsequent queries will be success, when the "Not In Time Window" error response has both the latest EngineTime and EngineBootCnt of agent.
User not successfully cloned error
Reason : You will get this error when you try to create a new user in the agent using an existing user from the remote. The possible reasons are,
Remote agent may not be running.
Clone-from user name or password or security level may be wrong.
Clone-from user's context name is not having access in USM table.
Clone-from user and new user's authProtocol (MD5 & SHA) may be different
Solution : Find out the reason of your problem from the above listed reasons. Delete the row from the USM table of new user if created. Run snmpUSMRemoteConfigure.java command line tool again with correct inputs.
Getting "USM keychange is not successful" error
Reason : You will get this error when you try to change the auth password or priv password of another user or yours. The possible reasons if the key changes for another user are,
Remote agent may not be running.
Template user name or password or security level may be wrong
Template user's context name is not having access in USM table.
Template user's and the other user whose key is to be changed authProtocol (MD5 & SHA) may be different
The possible reasons if key change for same user are,
Remote agent may not be running.
User name or password or security level may be wrong
User's context name is not having access in USM table.
Solution : Find out the reason for your problem from the above listed reasons and provide the correct inputs.
Unable to Decode PDU
Reason : This error will occur when the cryptix classes or jdk1.2 classes are not in the classpath for the privacy support. Also when the java.security file is not edited properly to include the exact privacy packages.
Solution :The classes should be set correctly in the classpath of setenv.bat file.
Unable to Encode PDU
Reason : This error will occur when the Context Name and ContextEngineID are not specified. This exception is thrown for get, getnext, getbulk & set operations.
Solution :Check if the context engine id and context name are specified correctly. If not, modify them accordingly.