SNMP V1 V2c Error Messages

Errors that are likely to occur while working with SNMP Agents are listed under two categories. It has been categorizedbased on the versions. Please follow the links to know about them:

Troubleshooting Tips - SNMP v1/v2Troubleshooting Tips - SNMPv3

SNMP V1 / V2c Error Messages The following are some of the errors and their possible causes:

Error Message Request Timed Out to localhost.

Cause of the Problem

This error is sent by the Mib Browser for the following conditions:If Community String is not valid, agent will send authentication trap butwill not send any response to the manager.This error occurs when the agent is not running or if the port number atwhich the agent listens to is different from the port number specified inthe Mib Browser settings.The TCP/IP is selected as the communication protocol inSettings->SNMP options of the Agent Compiler. In this case, the agentcan be tested only by using the Command line Applications (TCP/IP).This error occurs when the get-bulk operation is given a value morethan max-repetitions. The Agent will not send a response to theManager within 5 seconds.

How to correct itFind out the reason for your problem from the above listed reasons and correctit. The get-bulk error can be rectified by increasing the timeout value.

Error Message General Error :Cause of the Problem This error is send by the agent when a request is forwarded by the ProxyAgent to the Sub-agent and the sub-agent is not running in the specified port.

How to correct it Find out the reason for your problem from the above listed reasons andcorrect it.

Error Message No data available in this MIB.

Cause of the Problem A node is not registered (implemented) in the agent.There is no entry available in the table.

How to correct it Find out the reason for your problem from the above listed reasons and correctit.

Error Message End of Mib view.

SNMP https://www.webnms.com/cagent/help/troubleshoot/c_troubleshoot_snmp...

1 de 4 29/03/2015 08:09 p.m.


This error might occur when a get-bulk request is made. The Get Bulk requestuses nonrepeaters and maxrepetitions fields as specified in the Mib BrowserSetting panel. The default value for maxrepetitions is 50 and the nonrepeatersvalue is 0. It means that the agent will do GET-NEXT 50 times. Initially agentwill not have 50 MIB objects value, so it will give the following error :Error Indication in response: This is a end of Mib View.

How to correct it If you reduce the maxrepetitions value to 10 then you will get the properresponse from the agent.

Error Message No ObjectID specified.Cause of the Problem This error occurs when a request is made without selecting an object in theMibTree.

How to correct it Select an object in the Mib Tree before making the request.

Error Message In VxWorks : No Such Variable Name.Cause of the Problem This error may occur, if -fsigned-char is not added to the VxWorks Compilertab.

How to correct it Add -fsigned-char to the VxWorks compiler tab. SNMP V3 Error Messages The following are some of the errors and their possible causes which you might encounter while adding new users ortesting for the v3 agent:

Error Message Discovery Failed

Cause of the Problema. You will get this error if you try to add a user with "Auth,Priv", or"Auth,noPriv", or "noAuthnoPriv" security level in the v3settings tab of theMibbrowser without starting the agent.b. The Port number specified may be wrong.c. The Ip Address may be wrong.

How to correct it Check if the agent is started at the correct port number as specified in the v3settings tab. If not, start the agent and add the new user entry.

Error Message Time sync failed for user .

Cause of the ProblemYou will get this error in the following cases if you provide the wrong username/password while adding the user in the Manager to test the v3 agent.That is, the user name provided does not exist in the USM user table.

How to correct it Enter the correct UserName and password as provided in the USM user table.

Error Message A authorization failed error occurred.


You will get this error in the text area of the Mib Browser while trying to do aget/set for the v3 agent. This error occurs in the following cases :a. If the v3 user is not provided access in the vacmviewtreefamilytable for theobject being queried. For example, the access provided for the userauthUserSHA in the vacmviewtreefamilytable is .1.3.6.1.6.3.16. If thisuser tries to do a get on the v3 agent with Object ID.1.3.6.1.4.1.2162.4.1.1, the above error is displayed.b. If the context name provided in the Mib Browser is not the same as thatconfigured in the vacmContextTable for that user. For example, the context


2 de 4 29/03/2015 08:09 p.m.

name provided for the user authUserSHA in the vacmcontexttable is "auth". Ifthis user tries to access the v3 agent by providing the context name as"noauth" in the Mib Browser, the above error is displayed.

How to correct it Find out the cause of your problem from the above listed reasons and do thenecessary changes.

Error Message End of Mib view error.


You will get this error in the text area of the Mib Browser while trying to do aget-next for the v3 agent. This error occurs if the context name provided inthe Mib Browser is not the same as that configured in the vacmContextTablefor that user. For example, the context name provided for the userauthUserSHA in the vacmcontexttable is "auth". If this user tries to access thev3 agent by providing the context name as "noauth" in the Mib Browser, theabove error is displayed.

How to correct it Find out the cause of your problem from the above listed reason and do thenecessary changes.

Error Message If I do a request on my OID, I get the response:usmStatsNotInTimeWindows(.1.3.6.1.6.3.15.1.1.2.0)

Cause of the ProblemThe error , "Not In Time Window", means that the sent request EngineTime andEngineBootCnt may be different from agent's EngineTime and EngineBootCnt. Thepossible reason is, the agent would have restarted.

How to correct it The subsequent queries will be success, since the "Not In Time Window" errorresponse has both the latest EngineTime and EngineBootCnt of agent.

Error Message "User not successfully cloned" error when usingsnmpUSMRemoteConfigure.java command line tool.


You will get this error when you try to create a new user in the agent using anexisting user from the remote. The possible reasons are

Remote agent may not be running.1. Clone-from user name, or password, or security level may be wrong.2. Clone-from user's context name is not having access in USM table.3. Clone-from user and new user's authProtocol (MD5 & SHA) may bedifferent.

4.

How to correct itFind out the reason of your problem from the above listed reasons. Delete therow from the USM table of new user if created. RunsnmpUSMRemoteConfigure.java command line tool again with correct inputs.

Error Message Getting "USM keychange is not successful" error when usingsnmpUSMKeyChange.java command line tool.


You will get this error when you try to change the auth password or privpassword of another user or yours. The possible reasons if key change foranother user are,

Remote agent may not be running.1. Template user name, or password, or security level may be wrong.2. Template user's context name is not having access in USM table.3.


3 de 4 29/03/2015 08:09 p.m.

Template user and the other user, whose key is to be changed toauthProtocol (MD5 & SHA) may be different

4.

The possible reasons if key change for same user areRemote agent may not be running.1. User name, or password, or security level may be wrong.2. User's context name is not having access in USM table.3.

How to correct it Find out the reason for your problem from the above listed reasons and providethe correct inputs.

Error Message Unable to Decode PDU.

Cause of the Problem This error will occur when the cryptix classes or jdk1.2 classes are not in theclasspath for the privacy support.How to correct it The classes should be set correctly.

Copyright 2012, ZOHO Corp. All Rights Reserved.


4 de 4 29/03/2015 08:09 p.m.

SNMP V1 V2c Error Messages

Documents

Transcript of SNMP V1 V2c Error Messages