How to use LLDIAG on the DataPower gateways to gather diagnostic information.

How To

Summary

LLDiag is a diagnostic tool for DataPower Support and Development to investigate unexpected behavior of the appliance. LLDiag specializes in detecting problems during high cpu, load, memory, or an unexpected outage (hang, reload, reboot). The contents of LLDiag are encoded and not all contents are easily interpreted by the user as it is intended for internal diagnostics.

Steps

1. Getting Started

LLDiag must be configured and enabled per Step 2 before an event to capture data. LLDiag is ran before, leading into and during the unexpected event to be tracked.
LLDiag could impact performance during capture. The impact scales with appliance load, traffic volume, and lldiag settings used so monitoring to determine impact is suggested.
If the appliance reloads or reboots, then lldiag must be reenabled.

2. Staging Environment

To enable LLDIAG, open an SSH/CLI/Serial console on the DataPower Gateway and login by using the admin ID.

A. Enter the following commands:

diag
lldiag on miniwd
lldiag check 50
lldiag timeout 100
lldiag monitor 250

The results of the session will be:

idg# diag
Diagnostics mode
WARNING: Running commands in this mode can result in performance degradation. Use this mode only when directed by IBM Support.
idg(diag)# lldiag on miniwd
idg(diag)# lldiag check 50
idg(diag)# lldiag timeout 100
idg(diag)# lldiag monitor 250
idg(diag)#

B. Specify the lldiag directory to save the files (replacing <raid> with your raid-volume directory):

lldiag dir local:///<raid>
If no raid, use lldiag dir local:///

The results of the session will be similar (replacing <raid> with your raid-volume directory):

idg(diag)# lldiag dir local:///ondisk

If needed you can obtain your raid-volume directory name through the CLI (example is "ondisk"):

idg(diag)# top
idg# show raid-volume
raid-volume: raid0 [up]
------------------
admin-state enabled
read-only off
directory ondisk

Note: If you do check for your raid-volume, be sure to reenter 'diag' mode before the 'lldiag dir' command and moving to Step C.

For Example:

idg# diag
Diagnostics mode
WARNING: Running commands in this mode can result in performance degradation. Use this mode only when directed by IBM Support.
idg(diag)#

C. Validate the LLDiag settings by using 'lldiag show':

lldiag show

The results of the session should be similar to:

idg(diag)# lldiag show
      enabled: yes
         mode: 1
      timeout: 100 msec
      monitor: 250 msec
        check: 50 msec
      log dir: local:///ondisk
max. log size: 1048576 bytes
log rotation: 3
idg(diag)#

D. Validate LLDiag Captures are being recorded (replacing <raid> with your raid-volume directory):

top
co
dir local:///<raid>

The results of the session should be similar to:

idg(diag)# top
idg# co
Global mode
idg(config)# dir local:///ondisk
   File Name                    Last Modified                    Size
   ---------                    -------------                    ----
   dpmon.1                      Sep 12, 2019 2:43:04 PM          2356212
   dpmon.2                      Sep 12, 2019 2:28:04 PM          2371040
   dpmon.7                      Sep 12, 2019 1:12:05 PM          2370618
   dpmon.6                      Sep 12, 2019 1:28:00 PM          2423521
   dpmon.5                      Sep 12, 2019 1:43:01 PM          2398166
   lldiag.txt                   Mar 4, 2020 12:23:02 PM          146604
   dpmon.3                      Sep 12, 2019 2:13:03 PM          2398393
   dpmon.4                      Sep 12, 2019 1:58:02 PM          2430853
   dpmon.8                      Sep 12, 2019 12:57:04 PM         2402553
   dpmon                        Sep 12, 2019 2:53:03 PM          1524295
   1125292.9 MB available to local:///ondisk

Note: Look for the lldiag.txt file to be created with the Last Modified date being current.

3. Replicate Issue, Collect Data

Re-create the issue or await the issue to occur
Once replicated, by using the WebGUI in the Control Panel select File Management, immediately save the file local:///raid/lldiag.txt and iterations of lldiag (.1, .2, .3, etc) that are created.
Download "dpmon" and "dpmon.x" where x is numerical iterations to your local system, by default these are located in temporary:///dpmon
Generate an Error Report. Download the result error report to your local system.
Provide the result files to IBM Support.

4. Disabling of LLDiag

LLDiag will automatically disable upon a reload/reboot of the system.
To disable lldiag, it can be performed through 'diag; lldiag off'. Additionally, 'lldiag show' will report "Enabled: no" when disabled.

Additional Information

More options that might be needed or requested by support are:

Modes:
miniwd
lowmem
sched
queues
workers

Modes can be combined with a plus symbol, for example:
lldiag on miniwd+lowmem

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","Platform":[{"code":"PF009","label":"Firmware"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Product Synonym

DataPower

Was this topic helpful?

Document Information

Modified date:
03 June 2026

UID

ibm10719605

Tips