HP General IO Connectivity manual Reporting Problems

Troubleshooting

Reporting Problems

Reporting Problems

If you have a service contract with HP, ask your service representative to document the problem as a Service Request (SR).

Include the following information where applicable:<

•A detailed description of the problem. Describe the events leading up to the problem and the symptoms of the problem. Include information on HP-UX commands, communication subsystem commands, job streams, result codes, and error messages (the exact wording).

•A record of the output from x25 stat -cor a copy of the configuration file for each node. Record the output from netstat.

•A printout of the existing configuration files.

•A copy of the ipmap file.

•A copy of the PSI upload file.

•The version, update, and fix information for all software. From this information HP can determine if the problem is already known and if the correct software is installed at your site.

•Use the what command to check your X.25 version.

•Any network log files produced using the netfmt command (see Chapter 7, Tracing and Logging Utilities, for details of netfmt), and formatted copies of any X.25 trace files that were active when the problem occurred.

•A short description of your application and how it should work.

•In the event of a system failure, take a full memory dump. Use the HP-UX utility /etc/savecore to save a core dump.

•For PAD Problems:

—Copies of the x29hosts and x3config files.

—A copy of the output from the ls -l /dev/x29command if you are running x29printd or x29uucpd.

Chapter 8 213