Chapter 3 Installation and Application Troubleshooting

This chapter addresses potential scenarios in which troubleshooting might be necessary. This troubleshooting section covers both installation and software application issues.

Installation Troubleshooting

This section addresses problems that might occur during the installation process.

Error Messages Display When Installing Packages

When you install the SUNWescad and SUNWescas packages, the following error messages might be displayed:

ERROR: CA-TNG is not installed, you should install 
CA-TNG first.
ERROR: Agent Factory is not installed, you should install Agent 
Factory first.

If either of these error messages are displayed, verify the following information:

• Unicenter is installed.

• Environment variables $CAIGLBL0000 and $AGENTWORKS_DIR exist.

SUNWescas Package Installation Does Not Install After Substantial Period of Time

If the installation of the SUNWescas package has not completed after several hours, type the following commands, to ensure that all Unicenter processes are working:

# unifstat 
# awservices status 

For more information, refer to the Unicenter TNG User's Guide.

Application Troubleshooting

This section addresses problems that might occur while using the Sun Management Center Unicenter TNG^TM application and tasks.

Cannot Discover a Sun Management Center Agent in Unicenter TNG

If you cannot discover the Sun Management Center agent when the SUNWescad and SUNWescas packages have been installed, type the following command:

# dscvrbe -R Unicenter_TNG_repository_address \
-7 Sun_Management_Center_agent _address

This command will discover the Sun Management Center host in Unicenter TNG. The command can be run more than once, if necessary.

Verify the following information:

• The simple MIB-II module or MIB-II instrumentation module has been loaded on the Sun Management Center agent.

• If the Sun Management Center agent is not running on the default port, 161, make sure you followed the procedure to discover a Sun Management Center Agent. See To Discover Sun Management Center Agents.

• If the Sun Management Center platform agents cannot be discovered, make sure the event adapter is running and pointing to the correct Unicenter DSM port.

Unicenter TNG WorldView Cannot Display Status of Sun Management Center Agent

To ensure that Unicenter TNG and all related processes are working, type the following commands:

# unifstat 
# awservices status 

If all processes are working, and the agent status still does not display, verify that the Sun Management Center software is using port 161.

If the correct port is being used, and the agent status still does not display, try restarting the EventAdaptor. See To Start the EventAdaptor.

For more information about the unifstat and awservices commands, refer to the Unicenter TNG User's Guide.

EventAdaptor Does Not Work

If the EventAdaptor does not work, verify the following information:

• Sun Management Center console is installed with the EventAdaptor.

• Java^TM environment, the JAVA_HOME variable, is correct.

• The SUNWescad and SUNWescas packages are installed correctly.

• Unicenter TNG works.

• Your user name and password for Sun Management Center are correct.

Details Application Does Not Work

If the Details application does not work, verify the following information:

• Sun Management Center console is installed with SUNWescah.

• Java environment variable, JAVA_HOME, is set correctly in the environment of the web browser from which Unicenter WorldView is launched.

  For specific instructions on how to set the Java environment variables, see “Java Environment Variables and Path” in the Sun Management Center 3.5 Installation and Configuration Guide.

Load or Unload Module Information Does Not Display in Unicenter TNG WorldView Console

If the Load or Unload module information does not display in the Unicenter TNG WorldView console, check the following information:

• Warning messages that are displayed about the module load and unload function. If the following warning message displays when starting the EventAdaptor:

  Warning: Cannot provide Module Load and Unload Feature! (Community Setting failed!)

  Verify that the login user is a member of the esadmin group.

  If the following warning message is displayed when starting the EventAdaptor:

  Warning: Cannot provide Module Load and Unload Feature! (Subscription failed!)

  To ensure that your Sun Management Center server's trap handler is working, and that you can restart it, type the following commands:

  # /opt/SUNWsymon/sbin/es-stop -t # /opt/SUNWsymon/sbin/es-start -t

  To view the trap log, refer to the Sun Management Center User's Guide.

• Exceptions displayed. Restart the EventAdaptor. See To Start the EventAdaptor.

Log File Not Created When Starting EventAdaptor

The following error message might be displayed if certain conditions exist:

java.io.FileNotFoundException: XXX.log

For example:

• The log file has already been created by another user, and you do not have write permission on the file.

• The log file cannot be created in the specified directory.

For details on the SunMCtoTngAdaptorMain.cfg default location. See To Install the EventAdaptor Component.

Error Messages Are Displayed When Starting EventAdaptor

If the following error messages are displayed when starting the EventAdaptor:

	java.lang.UnsatisfiedLinkError: no SsStack in java.library.path
	at java.lang.Throwable.fillInStackTrace(Native Method)
	at java.lang.Throwable.fillInStackTrace(Compiled Code)
	at java.lang.Throwable.<init>(Compiled Code)
	at java.lang.Error.<init>(Error.java:50)
	at java.lang.LinkageError.<init>(LinkageError.java:43),...,

Verify that the SUNWescaa package was installed in the correct version of the operating environment.

Unicenter TNG Cannot Receive Alarms from EventAdaptor

If you notice that valid alarms are missing, or cannot be received, follow these steps:

• Verify that the Unicenter TNG SNMP gateway, aws_snmp, and trap MUX, aws_listen, are working.

• Verify that no other process is using port number 161.