HP 3PAR Service Processor Troubleshooting Guide (QR483-96013, December 2012)

2 Guidelines for Troubleshooting the Service Processor
This chapter provides troubleshooting guidelines and explains how to use this document for
troubleshooting Service Processor (SP) issues.
Troubleshooting Guidelines
General troubleshooting guidelines are as follows:
• Identify the problem or problems.
• Assess the situation.
• Determine how the criticality of the problem. If more than one problem exists, determine which
problem is the most significant in terms of impact.
• Collect as much information as possible relevant to the problem.
• Generate an action plan and then execute it.
• If the action does not resolve the problem, escalate.
Troubleshooting Tools
You can use the following tools to collect data from the SP:
• Audit and Logging Information - Provides audit information regarding SP usage.
• SPLOR - Gathers files to diagnose SP issues.
Audit and Logging Information
HP 3PAR SP Audit Information is contained in the SP_USER_ACTIVITY log file, which provides
the following audit information:
• Users who accessed the SP
• Logon and logoff times
• The functionality used, such as Interactive CLI, Added System, and Started Guided Maintenance
Available through SPOCC-Reports, this file is gathered as part of a SPLOR and can be viewed by
HP Support personnel using Service Tools and Technical Support (STaTS).
Output examples:
yy/mm/dd 15:12:48 Remote Operation requested by userID as SP user #
yy/mm/dd 15:13:20 #( userID-pts0 )/spmaint -- spmaint starting
yy/mm/dd 15:14:47 #( userID-pts0 )/spmaint -- InFormOS validating update status --
InServ: myInServ. RC: 0
yy/mm/dd 16:20:56 #( userID-pts0 )/spmaint -- interactive CLI requested for InServ:
myInServ
yy/mm/dd 16:22:58 #( userID-pts0 )/spmaint -- csstatus launched for myInServ
yy/mm/dd 16:35:36 Remote Operation terminated for userID as SP user #
The actual commands that were executed can be found in other logs that are available to HP 3PAR
Support personnel.
HP 3PAR SP command logging includes the following:
• Commands that were executed using SPMAINT are logged in SPMNTLOG, which is available
as a unique file in STaTS.
• Commands that were initiated from the SP GUI (SPOCC) are logged in SPOCCMNTLOG.
This log is available as part of SPLOR.
Troubleshooting Guidelines 5