Troubleshooting a Synthetic Test Engine
If NetIM fails to communicate with specific test engines, Riverbed Technical Support may ask you to perform the following procedure.
Troubleshooting test engine communication with NetIM
1. Log in to NetIM.
2. Choose More > Synthetic Tests.
3. Select the Synthetic Test Sources tab at the top of the page. This displays a list of the installed test engines and their status.
4. On the Synthetic Test Sources page, note the list of test engines that are registered to NetIM. Those with green status icons are communicating with this host. If a test engine is not listed, or if it has a red status icon and is listed as Not Connected, follow these steps to verify that the test engine is running and pointing to NetIM.
Make sure that all test engines have unique Computer Names. If you have installed test engines on multiple machines that have the same Computer Name, only one will be recognized by NetIM. If necessary, you can change a host’s Computer Name in the System group of the Windows Control Panel. Changing the Computer Name requires a system restart.
– Connect to the test engine host that is missing or listed as “Not Connected” on the Synthetic Testing Sources page.
– Navigate to <TestEngineHome>\TestEngine\active_agent\conf\ and open active_agent.cfg in a text editor.
– Verify that the PRIMARY_HUB_IP is the IP of NetIM core. If the IP is incorrect, rerun the configureTestEngine.bat file and enter the correct IP address of NetIM core when prompted.
– Restart the Riverbed Test Engine Windows service.
5. On NetIM, refresh the Synthetic Test Sources page and see whether the test engine is now available. If not available, continue.
6. If the test engine host fails to appear on the Synthetic Test Sources page, log in to the test engine’s host, and try to connect back to NetIM using ping and telnet. Ping the IP of NetIM, and telnet to port 2162 (or port 2163 for SSL). If you cannot connect to NetIM using ping and telnet, there may be a network communication or firewall issue.
Telnet may not be enabled on every machine.
7. If you can ping and telnet from the test-engine host to NetIM core, log in to NetIM core and attempt to ping and telnet to the test-engine host on port 2165 (or port 2163 for SSL). If you can ping and telnet from NetIM core to the Test Engine host, but the Test Engine still does not appear on the Synthetic Test Sources tab, continue to the next step.
8. Log in to the NetIM UI as admin.
9. In the browser, change the URL to http://<NetIM IP address>:8543 /vnes/TestDeployedStatus.htm. This page displays the status of both the configured tests and test sources.
The default ports are 9190 and 8543 for HTTP and HTTPS, respectively. NetIM is configured to use HTTPS by default.
10. At the bottom of the Deployed Test Status page, click Debug On. This causes log files to be created on NetIM core in the <install dir>/og/synTest/ directory, which contains all the communications between NetIM and its test engines. Riverbed support will be able to diagnose problems using these log files.
Uninstalling a Synthetic Test Engine
Should you decide you no longer need the test engine on a particular system, uninstall it using the following procedure.
Uninstalling the Test Engine from a Windows or Linux Host
1. Log in to the host where the test engine is installed, directly or remotely.
2. Open a command window as administrator.
3. Navigate to the <Parent_Dir>\Riverbed\TestEngine directory.
4. Stop and remove the Riverbed Test Engine service:
On Linux:
su - root
cd <Parent_Dir>\Riverbed\TestEngine
te.sh -R /svc_cmd remove TE
On Windows:
te.bat /svc_cmd remove TE
5. Remove the Riverbed directory:
On Linux:
su - root
cd /home/xyz
rm -rf Riverbed
On Windows:
cd ..\..
del Riverbed
6. Log in to NetIM, choose More > Synthetic Tests, and select the Synthetic Test Sources tab. If the name of the source that you just uninstalled is listed, select the test source and use the actions menu to delete it.
About te.env and te.bat
<Parent_Dir>\Riverbed\TestEngine\te.env contains environment variables for the test engine.
<Parent_Dir>\Riverbed\TestEngine\te.bat (or te.sh) is a utility for maintenance of the test engine.
If /ks_dir or /ks_pass is omitted from any command that allows it, corresponding values from te.env are used.
• te.bat /svc_cmd [install | remove | start | stop | restart | console | status] TE acts on the Riverbed NetIM Test Engine service.
– The install action is utilized by the install.bat (or install.sh) script and is not usually used manually, but is useful if test engine files are present but the service is not.
– The console action starts the test engine as an application rather than a service, for development purposes only. Do not use.
• te.bat /ks_cmd verify /ks_dir <dir> /ks_pass <password> KEYSTORE verifies that a keystore exists at <dir> with password <password>. There can be multiple keystores in different directories. The active keystore is the one in the directory named by the KEYSTORE_DIR variable in te.env. typically c:\Riverbed\TestEngine\te_keystore.jks.
• te.bat /ks_cmd empty /ks_dir <dir> /ks_pass <password> KEYSTORE empties the keystore named in te.env, or the keystore at <dir>
• te.bat /ks_cmd create /ks_dir <dir> /ks_pass <password> KEYSTORE creates an empty keystore at <dir> with password <password>
• te.bat /ks_cmd change_password /ks_dir <dir> /ks_pass <password> /ks_old_pass <old_password> KEYSTORE changes the password of the keystore at named in te.env or at <dir>
• te.bat SET_ENV activates all variables as set in te.env. Use this if you have modified variables with a text editor.
• te.bat /env_var <variable> SET_ENV_VAR activates one <variable> as set in te.env. Use this if you have modified <variable> with a text editor.
Reconfiguring a test engine if NetIM’s IP address changes
If test engines are installed with the NetIM hostname rather than the IP address, those test engines will resolve the NetIM IP address even if it changes.
But if test engines are installed with the NetIM IP address, and the host’s IP address is not static and it changes, every test engine loses its link to NetIM. In that case, perform the following procedure on the host of every test engine.
Resetting the IP address of NetIM in a test engine’s configuration file
1. Navigate to the installation directory such as C:\Riverbed\TestEngine.
2. Stop the test engine service by running te.bat /svc_cmd stop te.
3. Use any editor to modify te.env.
4. Change the HUB_IP value to the new IP address of NetIM, or to the new hostname of NetIM: for example, HUB_IP NetSensorServ-2.ourCompany.com.
5. Save and close the te.env file.
6. Activate the newly set parameter by running te.bat /env_var HUB_IP SET_ENV_VAR.
7. Restart the test engine service by running te.bat /svc_cmd start te.