User's Manual

HP StorageWorks File System Extender Software user guide 283
you describe a wrong problem, you might end up with the original problem still present after technical
support have already put significant effort into investigating and finding a solution to another problem.
Log and debug traces of the problem
Reproduce the problem with debugging enabled — for details, see ”Debugging FSE processes” on
page 275. Save the evidence, such as wrong command output or strange error messages, and send it for
lab investigation.
Note that without knowing the contents of the fse.log and error.log files, technical support cannot
start investigating the problem.
Reproduction procedure
Write down the procedure for reproducing the problem. This is important for technical support to be able
to investigate and solve the problem.
Workaround discovered?
If you managed to develop your own workaround, describe it and add the description as a part of your
problem report. It might be a useful hint to technical support and other users, or it can lead to an even
better solution.
System information
Linux specific
Use the /opt/fse/sbin/tools/fse_sysinfo.sh script to collect data about the system the FSE
software is running on. The output is shown on stdout, and stored in the file
/var/opt/fse/log/Hostname_info.log. Send this file and the contents of the directory
/var/opt/fse/cfg to technical support.
Windows specific
Use System Information to collect data about the system. Click Start > Programs > Accessories > System
Tools > System Information to open System Information. From the Action menu, select the Save As System
Information option and send the file to technical support.
One archive package
Pack everything collected in previous steps into a .tar file (on Linux platform) or .zip file (on Windows
platform). It is easier to handle one file per problem. This way you make sure technical support receive
everything you provide for problem investigation.
Contact
See ”HP technical support” on page 8.
Technical support will contact you as soon as possible, depending on the data you provide and especially
on the problem you reported.
FSE error codes
Code Description Log Analyzer
e-mail alert
Log Analyzer
SNMP alert
General errors
0 No error.
1 Singleton violation: Class instance already exists.
2 File access error.
3 Out of memory. error error
4 Invalid arguments passed to a function.
5 MAJOR INTERNAL ERROR: Data corruption detected. error critical