TroubleShooting - General

Tool does not start and appear to be hanged

The database connection could not be obtained

Possible solutions:

1. Check the port number '2306' (by default, simulation toolkit will start the mysql server at 2306) is free. If the port number is already occupied, kindly edit the file NDTStartup.prop inside the <SimulatorHome>/conf/settings directory and update the port number with some other, which is free and then restart the product.

2. Check if the file my.cnf is present inside the directory /etc/ and if so, rename the file and then restart the product.

 3. If you are still not succeeded in starting the mysql server, then you can start the server separately using the shell file StartMySql.sh from within  <SimulatorHome>/bin directory and then start the product (NetworkDesigner.sh).

Note :Make sure, you are starting the product as 'root' user with 'admin' previlleges

Out of environment space

This is a problem with the windows' environment variable settings

 If  Out of environment space error is thrown, do the following steps to rectify the error:

• Open the Command Prompt, right click on the Title bar of the prompt and select the properties menu item. A window titled MS-DOS Prompt Properties will be opened.

• Select the 'Memory' option in the menu.

• Select the value '4096' in the 'Initial environment' field

• Click on the Apply button and restart the Command Window.

• Now Start the product

An unexpected exception has been detected in native code outside the VM.

This is an issue of jdk1.4 due to the incompatibility of the Java 's dll with some of the hardwares.

Please use the jdk1.3 in your machine. For more details on the issue , you can refer to the following URL.

http://developer.java.sun.com/developer/bugParade/bugs/4482430.html

You have to change the java home in setenv.bat file in <simulator home >/ bin directory and the SimulationToolkit.bat in the < simulator home > directory.

NoClassDefFoundError

This problem generally occurs in Windows 98 & Windows ME. When the classpath variable is set from the bat file the out of environment space error will be thrown. In this case the classpath will not be set and the No Class Found Error will be thrown.

• Edit the SnmpAgentSimulator.bat file under the <Simulator_Home>/bin directory.

• Remove "@echo off" present in the SnmpAgentSimulator.bat file and save the file.

• Edit the setenv.bat file under the <Simulator_Home>/bin directory.

• Remove "@echo off" present in the setenv.bat file and save the file.

• Open a command prompt and move to <Simulator Home>/bin directory. Now execute the SnmpAgentSimulator.bat in this command prompt.             

Exception while starting the SNMP Agent Simulator in Simulation Toolkit:

Exception while copying the file ./logs/agent.log to ./logs/agent1.log FileLogWriter: error opening agent.log:java.io.FileNotFoundException: ./logs/agent.log (Permission denied) Warning !!! InstantiationException while trying to create the Logger. Using DefaultLogger instead !!!

This problem  occurs if  SNMP Agent Simulator is started as Normal user

All the tools in Simulation Toolkit must be used only as Admin user.  

Exception with error code 515 while starting SNMP MIB Browser in Simulation Toolkit:

Exception: java.io.FileNotFoundException: ./conf/settings/mibbrowserset.conf (Permission denied)        at java.io.FileOutputStream.open(Native Method)        at java.io.FileOutputStream.<init>(Unknown Source)

This problem  occurs if SNMP MIB Browser is started as Normal user

All the tools in Simulation Toolkit must be used only as Admin user.  

"Invalid FileName! Please enter a filename without white spaces"

This is a restriction with Simulation toolkit. The Simulator does not allow to save the Agent Configuration in a directory which has space in its path.

Save the agent configuration in a different directory, which does not have white spaces.

"Error in parsing configuration file... "

The error occurs due to the space present in the Configuration file path of the SNMP Agent Simulator

Save the agent configuration in a different directory, which does not have white spaces.

Unable to start the SNMP Agent at port 161

This error will occur if the port (161/162) your are trying to start the Agent is used by another UDP service.

For Windows OS :

To check the UDP Port, type the following command in the command prompt:

netstat -anp udp

If the port is occupied by any other service, then you have to stop that service and start the simulated agent.

To start the agent at port 161 in Windows OS, follow the steps given below:

1. Select Start -> Settings -> Control Panel -> Administrative Tools -> Services. You will find all the services listed in the Services dialog.

2. Select the SNMP Service. The SNMP Service Properties dialog will pop up. Here, you will find the SNMP service status as Started.  

3. Select the Stop button, to stop the SNMP service and click OK.

Note : In the SNMP Service Properties dialog, if the Startup Type is mentioned as Automatic, you will need to perform the above steps, each time the system is started. Hence, you can make the Startup Type as Manual.

Now, you will be able to start the simulated agent at port 161.

For Linux/Solaris OS :

If you are using Linux/Solaris machine then check the port by using the command  netstat -anu in the console.

If the port is free, then you can start the simulated agent in 161/162 only if you have Root privilege. So kindly login as root and start the agent.

If the port is occupied by any other service , then you have to stop that service and start the simulated agent. To start the agent at port 161 in Linux OS, follow the steps given below:

You have to have root user privileges to stop the snmpd daemon. So, login as root user.

Use the command /etc/rc.d/init.d/snmpd  stop for stopping the snmpd in linux. Now. you will be able to start the simulated agents at port 161.