Collecting PEDBG Logs Using V10R3 or V11 HMC

Collecting PEDBG Using the V11 HMC GUI (Send Service Data)

This method uses the Send service data task in the V11 HMC Service management area to collect and transmit pedbg diagnostic data directly to IBM. No manual file handling or FTP steps are required.

Applies to: 7063 Power-based HMCs and Virtual HMCs (vHMC) running HMC V11R2M1120 and later.

Prerequisite — IBM Electronic Services connectivity required: The HMC must have Call Home enabled and be able to reach IBM Electronic Services. If the HMC cannot connect to IBM electronically, use the HMC CLI Method tab instead.

Section 1 — Navigate to Service Management

From the V11 HMC, click Service management in the left navigation panel.

Navigation path: Left navigation panel > Service management

The Service management task area opens. A sub-menu on the left provides access to: Serviceable events, Dumps, FTP connection, Schedule service data, Remote support connection, and Miscellaneous Equipment Specification (MES).

Section 2 — Open the Send Service Data Task

In the upper-right corner of the Service management task area, click the Service actions drop-down. Two options appear:

• Create serviceable event
• Send service data ← select this option

Select Send service data. A large task panel opens.

Section 3 — Complete the Send Service Data Form

Step 1: Fill in the header fields

Note: Sending service data will take some time. Duration depends on the number of files selected and their size.

Step 2: Scroll past routine Call Home data categories

Below the header fields is a grid of service data category tiles. The following categories are sent to IBM automatically on a routine schedule (weekly by default) when Call Home is configured. You do not need to select these for pedbg collection — scroll past them:

• Management console trace log
• Disk health data
• Fix level recommendation tool data (FLRT)
• Hardware service data (VPD)
• Software service data
• Operational heartbeat data
• Update access key / AIX update access key data

Step 3: Select the HMC diagnostics tile

Continue scrolling to find the HMC diagnostics tiles. Check the checkbox on the appropriate tile based on the guidance from your support representative:

Guidance on which tile to choose:

• Most software cases → check HMC diagnostics (pedbg -c -q 4)
• Hardware cases, or when dumps are requested → check HMC diagnostics with dumps (pedbg -c -q d4)
• Both tiles can be checked simultaneously if needed
• Two-HMC environments: Repeat this procedure on the second HMC as well

Step 4 (Optional): Also collect VIOS or AIX diagnostic data

Further down the page, additional tiles allow VIOS and AIX data to be collected and submitted in the same operation. These options require Power11 systems with supported VIOS/AIX versions and active RMC connections. If systems do not meet the requirements, the tile displays "No capable systems were found."

Step 5: Send the data

Once all desired tiles are checked, click the blue Send button at the bottom-right of the panel. A Cancel button is also available at the bottom-left. The HMC initiates data collection and transmission directly to IBM Electronic Services. No manual file handling or FTP is required.

What happens next: The data will appear in IBM's service support system under the associated case number. If no case number was provided, IBM will assign one and notify the registered contact.

↑ Back to tabs

Collecting PEDBG Using the HMC CLI

Use this method when the HMC cannot connect to IBM Electronic Services (Call Home not enabled, firewall restrictions, or network isolation), or when working on HMC versions prior to V11. This method collects the pedbg file locally and requires a separate manual transfer step to get the data to IBM.

Applies to: 7063 Power-based HMCs and Virtual HMCs (vHMC) on any supported HMC version. For issues involving servers managed by two HMCs, data must be collected on both HMCs.

Section 1 — Preparing to Collect the Data

Step 1: Enable SSH remote access (for remote collection only)

To collect pedbg via SSH from a remote workstation:

(a) Enable SSH and firewall settings on the HMC:

Navigation path: HMC UI > HMC Management > Network settings > LAN adapters > Edit > Allow Secure Shell > Save

Then select HMC Settings, scroll to Remote Control, and click Enable Remote Command Execution through SSH.

(b) Obtain an SSH client. PuTTY is recommended for Windows. macOS and Linux include a built-in ssh command.

Step 2: Ensure the hscpe user ID exists

You must be in a restricted shell session as user hscpe (role: hmcpe) to run pedbg. This is not a built-in HMC user — it must be created. You must be logged in as hscroot or an hmcsuperadmin user to manage HMC users.

Opening a restricted shell terminal locally at the HMC:

• V10.1.1020 or earlier: HMC Console Management > Console Management > Open Restricted Shell Terminal
• V10.2.1030 / V11 and later: HMC Management > HMC actions > Open restricted shell terminal

Or open a remote SSH session using PuTTY or any SSH client.

Check whether the hscpe user exists:

lshmcusr --filter "names=hscpe"

Expected output when user exists:

name=hscpe,taskrole=hmcpe,description=Service,pwage=99999,resourcerole=

If "No results were found", create the user:

mkhmcusr -u hscpe -a hmcpe -d "IBM Service"

You will be prompted to set a password. To reset a forgotten password:

chhmcusr -u hscpe -t passwd

Section 2 — Collecting Data Using PEDBG

Step 1: Log in as hscpe

You must be in a restricted shell session as hscpe (role: hmcpe) to run pedbg.

• Remotely: Start an SSH session directly as user hscpe
• Locally: Open the restricted shell terminal as described in Section 1, Step 2
• Already logged in locally as another user? Switch to hscpe (Remote Command Execution must be enabled):

ssh hscpe@localhost

If prompted to verify host authenticity, reply yes and press Enter. Enter the hscpe password when prompted.

Step 2: Re-create the problem (if possible)

Re-creating the problem immediately before running pedbg maximises the relevant diagnostic data captured. If re-creation is not possible, note the HMC date and time of the original event and communicate this to your IBM support representative, including any known offset between HMC clock time and real event time.

Example note to support: "The problem occurred approximately 2:00 PM on March 16. The HMC time is 30 minutes slow, so that would be about 1:30 PM HMC time."

Step 3: Run the pedbg command

Note: For problems involving servers managed by two HMCs, collect pedbg from both HMCs.

Section 3 — Getting the Data to IBM

After collection, the pedbg file is saved to /dump/ as a .zip archive. Use ls /dump to display the file name. Tip: type /dump/HMClo then press Tab to auto-complete the name. The following transfer methods are listed from quickest to most manual.

Method 1 — Secure FTP directly from HMC to IBM ECuRep (preferred)

Important: IBM no longer allows unsecured FTP. The -S (strict SFTP) or -s (SCP) flag must always be used.

Send directly to IBM ECuRep:

sendfile -S -f /dump/HMClogsxxxxxxxx.zip \
  -h sftp.ecurep.ibm.com \
  -d /toibm/hw/ \
  -n TSddddddddd.HMClogsxxxxxxxxx.zip \
  -u Your_IBM_Support_File_Transfer_ID

Note — IBM Blue Diamond Secure FTP is retiring June 30, 2026 and is being replaced by IBM SecureDrop. If you previously used Blue Diamond to submit service data, you must transition to SecureDrop before June 30, 2026 to avoid a service disruption. See Method 4 — IBM SecureDrop below. For questions contact securetransfer@ibm.com.

An IBM Support File Transfer ID linked to your IBMid is required for ECuRep. The password is only shown at creation time. If lost, delete the Transfer ID and create a new one.

Method 2 — Copy to USB media

1. Insert a formatted USB flash drive and wait several seconds for it to be detected.
2. Run: pedbg -c -q 9
3. Reply yes when prompted to move the .zip file to a device.
4. Enter the device mount point when prompted — for example, /media/sdb1 for the first USB drive.
5. Transfer the USB drive to a workstation with internet access, then upload using Method 4 below.

Method 3 — SCP or FTP to another workstation with internet access

If another server or workstation on the network has internet access and network access to the HMC, the data can be copied to that system first. From a Windows, Mac, or Linux workstation:

# Standard scp (Windows 10+, macOS, Linux)
scp hscpe@myhmc:/dump/HMClogs.HMClogsxxxxxxxxx.zip .

# PuTTY pscp (older Windows without built-in scp)
"C:\Program Files\PuTTY\pscp" -scp hscpe@myhmc:/dump/HMClogs.cs6hmcb0312H04.zip c:\temp\

Or use the sendfile command from the HMC to push the file to an on-premises server:

sendfile -f /dump/HMClogsxxxx.zip -h <hostname/IP> -u <user> -d <directory> -s

Method 4 — Upload from a workstation to IBM

(a) Rename the file to include the IBM case number at the beginning:

TSddddddddd.HMClogsxxxxxxxxx.zip

Where TSddddddddd is the IBM support case number and HMClogsxxxxxxxxx.zip is the original file name from /dump/.

(b) Send the file to IBM using one of the following:

• IBM ECuRep (general use): https://www.ecurep.ibm.com/
• IBM SecureDrop (replaces Blue Diamond for Fyre Protected / healthcare customers): https://securedrop.im-ies.ibm.com/

Using IBM SecureDrop: SecureDrop is IBM's next-generation secure file transfer portal, replacing the Blue Diamond Secure FTP service (retirement date: June 30, 2026). SecureDrop requires prior registration and login. Once logged in, select HTTPS File Upload from the left navigation, enter your IBM case number in the Please Enter Case Number field, then upload the renamed pedbg .zip file via drag-and-drop or file selection. Real-time upload progress and clear success/error status are provided. For registration or assistance contact securetransfer@ibm.com.

sendfile parameter reference

↑ Back to tabs