HMC Classic View: Collecting PEDBG from the HMC

Resolving The Problem

This document describes how to collect HMC diagnostic data (pedbg data) for use with problem determination. For issues involving servers managed by two HMCs, the data should be collected on both HMCs.

Section 1. Preparing to Collect the Data

Step 1: (Optional) Enable remote command execution
To collect pedbg remotely you must:

For further information see IBM support document "Configuring the Version 7 HMC to Accept SSH Connections and Remote Commands" at http://www.ibm.com/support/docview.wss?uid=nas8N1012875

Step 2: Ensure a user ID of hscpe with a task role of hmcpe exists on the HMC.
The hcpe id is not a built-in id like hscroot, it must be created. To administer HMC users you must be logged in as hscroot or a hmcsuperadmin user.

Locally (at the HMC): Open a restricted shell locally on the HMC by selecting HMC Management in the left frame. Select Open a Restricted Shell in the right frame.

Remotely: Open a ssh session (PuTTY) to the HMC.

Section 2. Collecting Data Using PEDBG

Step 1: Log in as user hscpe.
You must be logged in to a restricted shell terminal session as user hscpe with role hmcpe to collect pedbg.

Remotely: Log into a ssh (PuTTY) session with user hscpe.

Locally: Log into the local HMC as user hscpe then open a restricted shell by selecting HMC Management in the navigation area, then select Open a Restricted Shell in the work frame (right frame).

Optional: Switch to user hscpe when Logged on as Another User
The following uses ssh to switch to user ID hscpe when the user is already logged on with another user ID. HMC Management > Remote Command Execution must be enabled. In the restricted shell terminal run the command:

ssh hscpe@localhost

If prompted to verify authenticity of the host, reply yes and press enter.
The authenticity of host 'localhost (127.0.0.1)' can't be established.
RSA key fingerprint is 5c:c7:df:d0:a0:14:e2:5b:45:5d:09:a7:0f:7a:77:5c.
Are you sure you want to continue connecting (yes/no)? yes
Failed to add the host to the list of known hosts (/home/hscroot/.ssh/known_hosts).
Password:
Last login: Thu Jan 24 14:23:49 2013 from localhost.localdomain
hscpe@hmc770:~>

Step 2: Recreate the problem.
If possible, recreate the problem prior to collecting pedbg. Otherwise, note the HMC date and time. Notify your support representative of the date and time of the problem being investigated relative to the HMC clock and HMC time delta if it is incorrect. For example "The problem occurred approximately 2pm on 3/16. The HMC time is 30 minutes slow so that would be about 1:30pm HMC time.".

Step 3: Collect pedbg
Note: For problems involving managed servers managed by two HMCs, perform this on both HMCs.

Run PEDBG command
Run the pedbg command with the options specified by the support representative.

If the support representative did not specify the options (or for issues that may need more than a few hours of historic data) type the following:
pedbg -c -q 4

If the problem was recreated immediately prior to pedbg collection, the "-q 3" option can typically be used (this results in a much smaller file):
pedbg -c -q 3


Section 3. Getting the Data to IBM
There are many ways the data can be sent to IBM. The following is a list of preferred methods, starting with the quickest and easiest method. The method used varies depending on the type of network access available to the HMC and the availability of media.