HP 9000 rp8440 HP Servers running HP-UX - getsysinfo.sh 9.19 data collection s - Page 5

How to capture additional data from an MP or OA with hpmpl.jar ?, and Superdome 2 Servers.

Get HP 9000 rp8440 PDF manuals and user guides View all HP 9000 rp8440 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 5 highlights

rst.log sas.txt sautil.txt service_guard.txt sfmconfig.txt sfm_event.log sfmlog.txt shutdownlog spmgr.out sw_inventory.xml swlist.txt syslog.log OLDsyslog.log system.krs tddiag_date.txt.gz tombstones tombstones/sfm_sal vmunix.nm.gz vxvm.txt xpinfo.out RST event.log file /var/opt/resmon/log/rst.log sasdiag like information about SAS disks and cards connected to LSI SAS HBAs (improved own script) information about Smartarray raid controllers cmclview -v output (if Service Guard cmcld is running) output of sfmconfig -w -q (system fault manager config) /var/opt/sfm/log/event.log system fault manager logs similar to EMS event.log /etc/shutdownlog EVA diskarray infos used by mission critical HP support for patch analysis output of swlist -l bundle, swlist -l product and swlist -l fileset -a state | grep inst (last 2048 MB each) use -f option to capture the complete files krs information from /stand/krs/system.krs contains f.e. SAS dynamic hardware path assignments. (only collected if SAS is used) -san: Output of tddiag if fibre channel cards exist for this driver Directory with tombstone files (HPMC or MCA). Also: crashinfo outputs and EFI binary MCA files. Directory with binary CPEs and CMCs from logExtract (comes with SysFltMgr) gzipped output of nm /stand/vmunix. Needed for software support for extended analysis of MCAs when no creash dump is written. Information about Veritas Volumemanager (VXVM) config output of xpinfo (for XP diskarrays) How to capture additional data from an MP or OA with hpmpl.jar ? At least java 1.5 is needed for this feature. If you do not have getsysinfo.mp.sh or getsysinfo.all.sh (which have the hpmpl tool embedded), the hpmpl.285.jar file needs to be in the same directory as getsysinfo.sh. Note: getsysinfo.sh is trying to guess the MP IP or OA address with the cprop utility. If successful, it will connect automatically to this IP. getsysinfo.sh -mp #getsysinfo will ask for login data to MP or OA getsysinfo.sh -mp -mpopt "-ssh" #access MP via ssh (default for i2, i4 server) getsysinfo.sh -mp -mpopt "-h hostname -u user -p password" IMPORTANT: hpmpl will ask for login and password to MP or OA during the getsysinfo.sh run !!! Note: hpmpl also supports capturing logs via the Onboard Administrator (OA) of C-Class Blade enclosures and Superdome 2 Servers. It will automatically (if no -mpopt option is set) detect if an enclosure is present and by default connect via ssh to the OA instead of the iLO. For i2 and i4 blades, it will then try capturing the MP logs from the Onboard Administrator. Enhanced example (give OA IP and login when hpmpl asks): getsysinfo.sh -mp -mpopt "-ssh -oamp " #capture OA+ ilO-MP data from blades and C7000 OA via ssh without -oamp, only "show all" is captured. To capture only MP logs data from blades in bays 1 and 2 via the OA:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
rst.log
RST event.log file /var/opt/resmon/log/rst.log
sas.txt
sasdiag like information about SAS disks and cards connected to LSI SAS HBAs
(improved own script)
sautil.txt
information about Smartarray raid controllers
service_guard.txt
cmclview -v output (if Service Guard cmcld is running)
sfmconfig.txt
output of
sfmconfig -w -q
(system fault manager config)
sfm_event.log
/var/opt/sfm/log/event.log
sfmlog.txt
system fault manager logs similar to EMS event.log
shutdownlog
/etc/shutdownlog
spmgr.out
EVA diskarray infos
sw_inventory.xml
used by mission critical HP support for patch analysis
swlist.txt
output of
swlist -l bundle
,
swlist -l product
and
swlist -l fileset -a state | grep inst
syslog.log
OLDsyslog.log
(last 2048 MB each) use –f option to capture the complete files
system.krs
krs information from /stand/krs/system.krs
contains f.e. SAS dynamic hardware path assignments.
(only collected if SAS is used)
tddiag_date.txt.gz
-san: Output of
tddiag if fibre channel cards exist for this driver
tombstones
Directory with tombstone files (HPMC or MCA). Also:
crashinfo
outputs and EFI binary MCA files.
tombstones/sfm_sal
Directory with binary CPEs and CMCs from
logExtract
(comes with SysFltMgr)
vmunix.nm.gz
gzipped output of nm /stand/vmunix. Needed for software support for extended analysis of MCAs
when no creash dump is written.
vxvm.txt
Information about Veritas Volumemanager (VXVM) config
xpinfo.out
output of xpinfo (for XP diskarrays)
How to capture additional data from an MP or OA with hpmpl.jar ?
At least java 1.5 is needed for this feature. If you do not have getsysinfo.mp.sh or getsysinfo.all.sh
(which have the hpmpl tool embedded), the hpmpl.285.jar file needs to be in the same directory as
getsysinfo.sh.
Note: getsysinfo.sh is trying to guess the MP IP or OA address with the cprop utility. If successful,
it will connect automatically to this IP.
getsysinfo.sh -mp
#getsysinfo will ask for login data to MP or OA
getsysinfo.sh -mp -mpopt “-ssh”
#access MP via ssh (default for i2, i4 server)
getsysinfo.sh -mp -mpopt “-h hostname -u user -p password”
IMPORTANT: hpmpl will ask for login and password to MP or OA during the getsysinfo.sh run !!!
Note: hpmpl also supports capturing logs via the Onboard Administrator (OA) of C-Class Blade
enclosures
and Superdome 2 Servers.
It will automatically (if no -mpopt option is set) detect if an enclosure is present and by default
connect via ssh to the OA instead of the
iLO. For i2 and i4 blades, it will then try capturing the MP
logs from the Onboard Administrator.
Enhanced example (give OA IP and login when hpmpl asks):
getsysinfo.sh -mp -mpopt “-ssh -oamp ”
#capture OA+ ilO-MP data from blades and C7000 OA via ssh
without
-oamp
, only “show all” is captured.
To capture only MP logs data from blades in bays 1 and 2
via the OA: