TroubleShooting - SNMP Agent Simulator

Unable to encode PDU

This error will occur if the security provider has not been added to the java.security file.(assuming that you are using JCE).

The security provider has to be added by manually editing the java.security file under jdk1.2/jre/lib/security. Some sample entries are :

  security.provider.1=sun.security.provider.Sun

  security.provider.2=com.sun.crypto.provider.SunJCE

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:

a. If you provide the wrong user name/password while adding the user in the Manager to test the v3 agent. (i.e) the user name provided does not exist in the USM user table.

Hence, 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.

b. 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" and 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 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 in the following cases :

a. 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 reasons and do the necessary changes.

Please select valid Trap/Notification Node from the tree

The above error will be displayed, while configuring default traps defined in the MIB, using Generate Traps option. It occurs, if a node other than the Trap /Notification node is selected as the Trap node.

While specifying the Trap Name in the Generate Traps dialog, you have to select only the Trap/Notification nodes defined in the loaded MIB.

For example, if RFC-1213 MIB is loaded, you have to select the Trap node as egpNeighborLoss.  On selecting the trap node,  you will find  the Trap Name, Varbinds and Description displayed on the right-side dialog.  You can then proceed to configure the Manager entries and Sent traps

Invalid value for node "XXXXX"

One of the possible cause:

Simulation Toolkit does not support BITS and OPAQUE datatypes. The MIB file might have these TCs defined.
 

Change the type 'Opaque'  and 'BITS' as 'Integer32' in the required MIBs and then reload the MIBs.