Session handling

Learn about session limitations in the Hardware Management Console (HMC).

Session limitations

The HMC does not support disconnected sessions. A session logoff and a session disconnect are both considered as a session logoff. This means that you cannot reconnect to the same session to resume your task or tasks that were initiated from a previous session. Every login through the HMC creates a new session.

  1. If you initiate long running tasks from the HMC interface and then log off from the session, the long running tasks continue to run in the background. However, when you log in again, a new session is created and the task progress panels (which helps track the progress of the previous tasks) are no longer available. In this scenario, if you need to check the progress of the tasks that were initiated from a previous session, you can run the respective command line interface (CLI) commands, check the state of the managed resource, or check the console event logs.
    Note: Some examples of long running tasks include the following tasks:
    System management for servers:
    • Deploy system plan
    • Code update
    • Hardware - Prepare for hot repair or upgrade
    System management for partitions:
    • DLPAR memory in large units in the order of Terabytes
    • Live Partition Mobility (LPM)
    • Suspend or resume
    HMC management:
    • Backup management console data
    • Restore management console data
    • Save upgrade data
  2. If you fail to reauthenticate within the time that is specified in the verify timeout settings, you are automatically logged off from the current session.
  3. The idle timeout user property task is not functional. The HMC interface uses the default value of 0 for the idle timeout setting. If you set a different value for this setting, it is ignored.
    Note: Session, idle, and verify timeout properties are set for a user and it can be different for different users on the same HMC.