Table Of Contents; Why Should I Use The Script; What Options Should I Use - HP 9000 rp3410 Faq

Only if external script hpmpl.jar is in same dir or with getsysinfo.mp.sh or getsysinfo.all.sh:
-mp : run external mp collection java program hpmpl.285.jar
-mpopt "options" - set additional options for hpmpl.285.jar
Only if external script sd2collect.pl is in same dir or with getsysinfo.sd2.sh or getsysinfo.all.sh:
-sd2 : capture Superdome 2 or C[37]000 OA logs with external sd2collect.pl
-sd2opt "options" - set additional options for sd2collect.pl
Only if external script sd2collect.pl is in same dir or with getsysinfo.sd2.sh or getsysinfo.all.sh:
-sginfo : capture Service Guard logs with external script sginfo
The option -s prevents "hanging" commands like ioscan -f, diskinfo, vgdisplay etc.
(hanging means, the command may hang due to a hardware problem, NOT the server !)
Frequently Asked Questions
Why should I use the script ?......................................................................................................2
What options should I use ?........................................................................................................2
How long does a script run take ?...............................................................................................3
How big is the output ?...............................................................................................................3
Can the script crash the server ?..................................................................................................3
How can I give feedback to improve the script or report problems ?.........................................3
What is NOT collected by the script ?........................................................................................3
What is collected ?......................................................................................................................4
How to capture additional data from an MP or OA with hpmpl.jar ?.........................................5
How to capture additional data from C-Class or Superdome 2 OA ?.........................................6
How to capture Service Guard related information ?.................................................................7
How to automatically run crashinfo ?.........................................................................................7
How can I modify the temporary directory ?.............................................................................7
Can I modify the script ?.............................................................................................................7
How to transfer data via ASCII terminal applications with cut&paste ?....................................8
Can I run the script regularly from cron ?...................................................................................8

Why should I use the script ?

It simply saves time if the support engineer gets all information from the OS needed for
troubleshooting in one step. And running a script is much more easy than collecting everything
manually.

What options should I use ?

The script should be run as root with ksh without any option by default. It then collects all data
necessary to troubleshoot recent hardware problems.
ksh getsysinfo.sh
Note: The script is only tested with Korn Shell (/usr/bin/ksh) and also works with the Posix default
shell for the root user (/sbin/sh). Other shells like csh or bash may cause problems.
To also capture MP or OA data (C3000,C7000, Superdome 2) via network:
ksh getsysinfo.all.sh -mp
(java >1.5 needed, only for getsysinfo.mp.sh/getsysinfo.all.sh or if hpmpl.jar is in the same
dir)
If one of the commands in the script hangs (usually ioscan), you can abort the current script run