Appendix A: Troubleshooting; Troubleshooting Aids; Using The Stand-Alone Client Application - Extreme Networks EPICenter Guide Manual

A Troubleshooting
This appendix describes how to:
Resolve problems you may encounter that are related to the EPICenter server
●
Resolve problems you may encounter while using the EPICenter client application
●

Troubleshooting Aids

If you are having problems with EPICenter, there are several things you can do to help prevent or
diagnose problems.
One of the first things you should do is run the Package EPICenter Info command. This command
packages the various log, property, syslog and other debugging information files and archives them into
a zip file. You can email this file to Extreme Networks technical support to provide them with detailed
information on the state of the EPICenter server.
You can run this command while the server is running, or while the server is stopped.
To run the Package EPICenter Info command, go to
<EPICenter_install_dir>/jboss/bin
(
PackageEPICenterInfo.bin
You can also run the Package EPICenter Info command from the Windows Programs menu:
Start > Programs > Extreme Networks > EPICenter 6.0 > Package EPICenter Info. In this case, a DOS
window appears that will display the progress of the commands as they are executed.
See "Package EPICenter Info Utility" on page 235

Using the Stand-alone Client Application

At any time while running the EPICenter installed client application, you can capture client debugging
information by going to the "About EPICenter" pop-up:
From the Help menu, select About EPICenter, then click Client Information.
●
You can then copy and paste the output information into a text file to send to Extreme Networks
Technical Support, if necessary.
Enabling Debug Mode for the Client
To enable debugging and log the output to a file in the stand-alone client application, you can run the
EPICenter client in debug mode.
Go to the EPICenter
client\bin
runclient.exe DEBUG DEBUG
EPICenter Concepts and Solutions Guide
and run
PackageEPICenterInfo.exe
in Linux or Solaris).
for details about using this command.
subdirectory and run the following command:
179