psm command

Use the psm command to troubleshoot and diagnose problems related to the Platform System Managers.

Use the following list of commands as a reference when you are using the psm command. The optional parameters are in square brackets [ ].

To invoke help for a specific command, type COMMAND [? | help] [SUBCOMMAND].

psm gatherlogs command

Use this command to collect Platform System Manager logs.

Options
collection type
Specifies the type of logs to collect. Some of the choices are listed as follows:
collect deploy
Contains data to help resolve problems with workload management.
collect dumps
Contains diagnostic information about the Java™ virtual machine (JVM), which supports the console functions.
collect management
Contains data to help resolve problems with the console and run time.
collect system
The default log collection consisting of the management collection set and deploy collection set.
collect vios
Collects information from the virtual image management code that runs on the specified compute node. Data is collected for both endpoints on the compute node.
list
list all
Note: If there is an issue with HTTP access and the console is not available, the hardware administrator cannot examine or transfer the log file collection. Contact IBM® Support for assistance with copying the log file collection from the Platform System Manager by way of SCP.
Usage
psm gatherlogs [collection type]

psm info command

Use the command to return information about the Platform System Manager. The return results include the following details:
  • Serial number
  • Core version
  • Console version
  • System management status
  • Recovery Subsystems Status
Options
all
Includes details about the management node for the purpose of troubleshooting.
Usage
psm info all

psm reboot command

Attention: Contact IBM Support for assistance before you run this command.
Use this command to stop all services on the server and restart the specified Platform System Manager. This command reboots the Platform System Manager and all services on it.
Usage
psm reboot

psm shutdown command

Attention: Contact IBM Support for assistance before you run this command.
Use this command to stop all services on the server and power off a specified Platform System Manager. This command shuts down the Platform System Manager and all services on it.
Usage
psm shutdown
Note: A separate command to start services is not provided because the services automatically start when the Platform System Manager is started. To start the services, start (or restart) the Platform System Manager virtual machine.

psm tls command

Use this command to add, remove, or check the status of TLS protocols for the system console. Changing this setting will restart Service3.
Important: If the TLSv1.2 protocol is the only protocol that is enabled, then all ciphers that support SHA1 are disabled. Ciphers supporting SHA1 are enabled only when using TLSv1 and TLSv1.1 protocols.
Usage
psm tls <add|remove|status> [TLSv1|TLSv1.1]
Note: A manually initiated or scheduled system backup is needed post Platform System Manager (PSM) failover. Each PSM has an unique encryption-related key that must be copied to the backup server host. Hence, it is essential to initiate a full system backup and avoid delta backup after a PSM failover.

If the full system restore is successful, verify whether the High Availability Status in PSM is online before you attempt operations, for example, pattern deployment.

If PSM failover occurs, then restore to any backup that was taken after the failover. This action ensures that there are no encryption related key mismatch and the restore is successful. If you initiate restore after PSM failover without a system backup, then the system restore fails with the following errors:

  • PSM nodes change to Ineligible state.
  • After a few hours, one of the PSM node state changes to 'Non-leader'.

To restore the PSM and resume online services, contact IBM Support.

The full system restore job might fail with other network errors even though the metadata files and databases are restored and the system restarts successfully. As a troubleshooting step, check whether the system is in a healthy state. If the system is not healthy, contact IBM Support.