---

HMC Manual Reference Pages  - MIGRDBG (1)

---

migrdbg - partition migration debug tools

CONTENTS

Synopsis
Description
Options
Examples
Environment
Bugs
Author
See Also

To enable or disable automatic partition migration failure debug data collection:
migrdbg -o {e | d} [--help]

To manually collect partition migration debug data:
migrdbg -o c [-m managed-system] [-t target-managed-system]
[-p partition-names | --id partition-IDs]
[--tp target-partition-names | --tid target-partition-IDs]
[--help]

To remove a partition migration debug data package:
migrdbg -o r {-f file | --all} [--help]

migrdbg provides partition migration debug tools.

-o	The operation to perform. Specify e to enable automatic collection of partition migration debug data on this management console. When enabled, debug data will be collected automatically for every partition migration that fails on this management console. If you are performing partition migrations to destination managed systems that are managed by other management consoles, you should enable automatic collection of partition migration debug data on those other management consoles also. Specify d to disable automatic collection of partition migration debug data on this management console. Specify c to manually collect partition migration debug data on this management console after a partition migration failure occurs when automatic collection of partition migration debug data on this management console is not enabled. It is recommended that you collect the debug data as close to the partition migration failure as possible. Performing another operation that affects the same source or destination managed system may cause the partition migration debug data for that managed system to be overwritten. If you perform multiple partition migrations with a single migrlpar command, it is recommended that you use automatic collection of partition migration debug data, since only debug data for the most recent partition migration is likely to be available after the migrlpar command completes. If a failed partition migration was performed using different source and destination management consoles, you should collect partition migration debug data on both management consoles. Specify r to remove a partition migration debug data package from this management console.
-m	The name of the source managed system for the partition migration for which you want to collect debug data. The name may either be the user-defined name for the managed system, or be in the form tttt-mmm*sssssss, where tttt is the machine type, mmm is the model, and sssssss is the serial number of the managed system. The tttt-mmm*sssssss form must be used if there are multiple managed systems with the same user-defined name. If the source managed system is not managed by this management console, the debug data must be collected from the management console that manages the source managed system.
-t	The name of the target, or destination, managed system for the partition migration for which you want to collect debug data. The name may either be the user-defined name for the managed system, or be in the form tttt-mmm*sssssss, where tttt is the machine type, mmm is the model, and sssssss is the serial number of the managed system. The tttt-mmm*sssssss form must be used if there are multiple managed systems with the same user-defined name. If the destination managed system is not managed by this management console, the debug data must be collected from the management console that manages the destination managed system.
-p	The name of one or more Virtual I/O Server (VIOS) partitions on the source managed system from which to collect partition migration debug data. Multiple partition names must be comma separated. You can either use this option to specify the names of the VIOS partitions from which to collect partition migration debug data, or use the --id option to specify the IDs of the partitions. The -p and the --id options are mutually exclusive. If neither this option nor the --id option is used to specify a list of VIOS partitions from which to collect partition migration debug data, partition migration debug data will be collected from all of the VIOS partitions on the source managed system.
-id	The ID of one or more VIOS partitions on the source managed system from which to collect partition migration debug data. Multiple partition names must be comma separated. You can either use this option to specify the IDs of the VIOS partitions from which to collect partition migration debug data, or use the -p option to specify the names of the partitions. The --id and the -p options are mutually exclusive. If neither this option nor the -p option is used to specify a list of VIOS partitions from which to collect partition migration debug data, partition migration debug data will be collected from all of the VIOS partitions on the source managed system.
--tp	The name of one or more VIOS partitions on the target, or destination, managed system from which to collect partition migration debug data. Multiple partition names must be comma separated. You can either use this option to specify the names of the VIOS partitions from which to collect partition migration debug data, or use the --tid option to specify the IDs of the partitions. The --tp and the --tid options are mutually exclusive. If neither this option nor the --tid option is used to specify a list of VIOS partitions from which to collect partition migration debug data, partition migration debug data will be collected from all of the VIOS partitions on the destination managed system.
--tid	The ID of one or more VIOS partitions on the target, or destination, managed system from which to collect partition migration debug data. Multiple partition names must be comma separated. You can either use this option to specify the IDs of the VIOS partitions from which to collect partition migration debug data, or use the --tp option to specify the names of the partitions. The --tid and the --tp options are mutually exclusive. If neither this option nor the --tp option is used to specify a list of VIOS partitions from which to collect partition migration debug data, partition migration debug data will be collected from all of the VIOS partitions on the destination managed system.
-f	The file name of the partition migration debug data package to remove from this management console.
--all	Specify this option to remove all partition migration debug data packages from this management console.
--help	Display the help text for this command and exit.

Enable automatic partition migration failure debug data collection on this management console:

migrdbg -o e

Manually collect partition migration debug data for the failed partition migration from managed system system1 to managed system system2:

migrdbg -o c -m system1 -t system2

Manually collect partition migration debug data for the failed partition migration from managed system S1 to a managed system managed by another management console:

migrdbg -o c -m S1

Manually collect partition migration debug data for the failed partition migration from a managed system managed by another management console to managed system S2:

migrdbg -o c -t S2

Manually collect partition migration debug data for the failed partition migration from managed system system1 to managed system system2, and only collect partition migration debug data from VIOS’s msp11 and vios11 on managed system system1 and from the VIOS’s msp21 and vios21 on managed system system2:

migrdbg -o c -m system1 -t system2 -p msp11,vios11 --tp msp21,vios21

Remove a partition migration debug data package from this management console:

migrdbg -o r -f lpmfdc-140728152436.tgz

Remove all partition migration debug data packages from this management console:

migrdbg -o r --all

None

None

IBM Austin

lsmigrdbg