psm command

You can 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].

automation command

Use this command to reload the Platform System Manager automation policy, which affects the high availability, monitoring and recovery functions of the Platform System Manager services. Before you run this command, use the psm info all command to validate that no services are currently starting or stopping. The psm automation reload command is needed only when a resource becomes stuck in the Unknown state. Use the psm info all command to verify a good state of the services after reloading the automation policy.

Usage
psm automation reload

clean command

Use this command to remove files on the specified file system and increase the amount of free space.

Usage
psm clean <file_system_display_name>

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 bsr
Contains data about block storage replication.
collect computenodes
Contains diagnostics and dump information about the compute nodes on the system.
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 fiber
Contains diagnostics and dump information about the SAN64B-6 Scalable Switches on the system.
list
list all
collect management
Contains data to help resolve problems with the console and run time.
collect network
Contains switch diagnostics and dump information from TOR switch SN2410 devices in the system.
collect system
The default log collection consisting of the management collection set and deploy collection set.
collect ip-<address>
Collects data from specific components, such as storage components, networking components, management nodes, and compute nodes.
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]

info command

Use this command to return information about the Platform System Managers. The return results include the following details for each management node:
  • Serial number
  • Location in the rack
  • Service state
  • Operating system version
  • Console version
  • High availability status
  • Recovery Subsystems Status
Options
all
Includes details about the management nodes for the purpose of troubleshooting.
filesystem
Shows the file system usage of the Platform System Managers.
Usage
psm info <option>

passwd command

Use this command to change the SSH account password. The change is applied only to one Platform System Manager at a time, therefore run the command on the other Platform System Manager to ensure the passwords remain synchronized.

Usage
psm passwd

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.
Options
remote
Restarts the other management node (if it is powered on) instead of the local management node as indicated in the psm info command return results. If the remote option is not specified, the local management node is restarted.
Usage
psm reboot [remote]

recovery restart command

Use this command to restart the Platform System Manager recovery engine, which affects the high availability, monitoring, and recovering functions of the Platform System Manager.

Usage
psm recovery restart

psm reset command

Attention: To use this command, contact IBM Support.
Use this command to reset or restart a specified service, as indicated by the service name, with guidance from IBM Support.
Note: Command processing can take awhile to complete depending on the number of services that are restarting or the current state of the Platform System Manager.
Usage
psm reset [<service name>]

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.
Note: When you use this command to power off the primary Platform System Manager, it is restarted after a delay of five to 30 minutes. Instead, use the Power Off button in the console to power off the device.
Options
remote
Powers off the other management node (if it is powered on) instead of the local management node as indicated in the psm info command return results. If the remote option is not specified, the local management node is powered off.
Usage
psm shutdown [remote]
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]

User-initiated failover

Before you initiate a failover using any of the methods that are listed below, put the system in maintenance mode to prevent compute nodes from temporarily transitioning to a quiesced state.
  • Issue a psm failover command.
  • Power off the leader management node from the console.
  • Issue a psm reboot command on the leader management node (or psm reboot remote from the non-leader management node).
  • On the leader Platform System Manager on the physical rack, press the power button quickly and release it without holding it down. This action is sometimes referred to as a soft press.
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.

To put the system in maintenance mode:
  1. Click System > Settings.
  2. Expand Maintenance Mode.
  3. Specify a start and end time.
  4. Click Submit.