Accessing virtual machines in classic virtual system instances

Each classic virtual system instance consists of a set of virtual machines that represent a physical node in an application server environment. You can access and view details about the individual virtual machines from your classic virtual system instance.

1. Click Patterns > Virtual System Instances (Classic).
2. Select the classic virtual system instance associated with the virtual machine that you want to access.
3. Expand Virtual machines to view the list of virtual machines in the classic virtual system instance.
4. Expand the details for your selected virtual machine by clicking the Expand icon next to the virtual machine name.
   The number of virtual machines that exist for the classic virtual system instance is dependent on the pattern that was deployed to create it.

   You can view the following details for each virtual machine:

   CPU

   Graphically displays the percentage of the virtual CPU power that is currently being used. The number of virtual CPUs available is determined by the pattern used to create the virtual system. The default number of virtual CPUs for a virtual machine is one.

   Memory

   Graphically displays the percentage of the memory that is currently being used by the virtual machine. The amount of memory available is determined by the pattern used to create the classic virtual system instance. The default amount of virtual memory for a virtual machine is 2048 MB.

   SSH

   A Login link to log in to your virtual machine by using Secure Shell (SSH).

   Actions

   The available actions for a virtual machine. If an action is not available, it is not active. Click the Manage link to display a submenu of actions that you can perform:

   Clone (Deprecated)

   Deploys another instance of the same image from the same pattern that was used to deploy the selected virtual machine. The same settings are used and the same script packages are run as they were at the time of deployment of the original virtual machine. In addition, any maintenance that was applied to the original virtual machine will also be applied to the newly deployed virtual machine.

   Any changes that were made by users to the original virtual machine, outside of Cloud Pak System Software, such as changing passwords, file system, or security system, will not be applied to the new virtual machine.

   Tip: Specify an optional password for the Clone operation to allow users to access the cloned virtual machine. The password that is provided during deployment sets a new password for all the product users who are defined by the image template. This excludes any users from user add-ons or any additional OS users that you defined.

   Tip: For WebSphere® cluster patterns, the WebSphere administrator user ID and password are set to be the same as the non-root user (default is virtuser), but is a separate entity. If you change the WebSphere administrator password from the WebSphere administrative console, clone operations on custom nodes appear to succeed but will not be federated into the cluster because the activation script uses the WebSphere administrator password that is specified at initial pattern deployment. You must log in to the new virtual machine and manually run the addNode command to federate the node.

   Start

   Restarts a virtual machine that has been stopped.

   Stop

   Stops a virtual machine that has been started.

   Delete

   Deletes a virtual machine after it is stopped. Resources associated with the virtual machine are released.

   Configure

   Configure the memory and CPU resources of the virtual machine.

5. To access the virtual machine, use one of the following steps:
   • If you are accessing a classic virtual system pattern:
     • Click Login under the SSH column to open a new browser window and access the virtual machine by using SSH. You must enter the current user name and password, or use the appropriate SSH key file if you do not select the password option. Otherwise, you cannot access the virtual machine.
     • Click WebSphere under the Consoles section to access the WebSphere Application Server administrative console on your virtual machine. Your virtual machine must be accessible from the computer that is accessing the console. If a firewall is preventing the connection on the required port, then the port must be opened for this link to establish a connection.
   • If you are accessing a virtual system pattern:
     • Click Manage > Login.
       Note: If the Login link is not available, SSH access to the virtual machine might be disabled through a security policy.
     • If console links exist, click a link in the Consoles section to open the specified administrative console.