Request Timed Out to localhost.

This error is sent by the Mib Browser for the following conditions:

• If Community String is not valid, agent will send authentication trap but will not send any response to the manager.

• This error occurs when the agent is not running or if the port number at which the agent listens to is different from the port number specified in the Mib Browser settings.

• The TCP/IP is selected as the communication protocol in Settings->SNMP options of the Agent Compiler. In this case, the agent can be tested only by using the Command line Applications (TCP/IP).

• This error occurs when the get-bulk operation is given a value more than max-repetitions. The Agent will not send a response to the Manager within 5 seconds.

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

The get-bulk error can be rectified by increasing the timeout value.

General Error :

This error is send by the agent when a request is forwarded by the Proxy Agent to the Sub-agent and the sub-agent is not running in the specified port.

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

No data available in this MIB.

• A node is not registered (implemented) in the agent.

• There is no entry available in the table.

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

End of Mib view.

This error might occur when a get-bulk request is made. The Get Bulk request uses nonrepeaters and maxrepetitions fields as specified in the Mib Browser Setting panel. The default value for maxrepetitions is 50 and the nonrepeaters value is 0. It means that the agent will do GET-NEXT 50 times. Initially agent will not have 50 MIB objects value, so it will give the following error :

Error Indication in response: This is a end of Mib View.

If you reduce the maxrepetitions value to 10 then you will get the proper response from the agent.

No ObjectID specified.

This error occurs when a request is made without selecting an object in the MibTree.

Select an object in the Mib Tree before making the request.

In VxWorks : No Such Variable Name.

This error may occur, if -fsigned-char is not added to the VxWorks Compiler tab.

Add -fsigned-char to the VxWorks compiler tab.

Discovery Failed

a. 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 the Mibbrowser without starting the agent.

b. The Port number specified may be wrong.

c. The Ip Address may be wrong.

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

Time sync failed for user <username>.

You will get this error in the following cases if you provide the wrong user name/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.

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

A authorization failed error occurred.

You will get this error in the text area of the Mib Browser while trying to do a get/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 the object being queried. For example, the access provided for the user authUserSHA in the vacmviewtreefamilytable is .1.3.6.1.6.3.16. If this user 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.

Find out the cause of your problem from the above listed reasons and do the necessary changes.

End of Mib view error.

You will get this error in the text area of the Mib Browser while trying to do a get-next for the v3 agent. This error occurs if the context name provided in the Mib Browser is 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, the above error is displayed.

Find out the cause of your problem from the above listed reason and do the necessary changes.

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

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

The subsequent queries will be success, since the "Not In Time Window" error response has both the latest EngineTime and EngineBootCnt of agent.

"User not successfully cloned" error when using snmpUSMRemoteConfigure.java command line tool.

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

1. Remote agent may not be running.

2. Clone-from user name, or password, or security level may be wrong.

3. Clone-from user's context name is not having access in USM table.

4. Clone-from user and new user's authProtocol (MD5 & SHA) may be different.

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 when using snmpUSMKeyChange.java command line tool.

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 key change for another user are,

1. Remote agent may not be running.

2. Template user name, or password, or security level may be wrong.

3. Template user's context name is not having access in USM table.

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

The possible reasons if key change for same user are

1. Remote agent may not be running.

2. User name, or password, or security level may be wrong.

3. User's context name is not having access in USM table.

Find out the reason for your problem from the above listed reasons and provide the correct inputs.

Unable to Decode PDU.

This error will occur when the cryptix classes or jdk1.2 classes are not in the classpath for the privacy support.

The classes should be set correctly.