Viewing virtual machine details

Each virtual application instance has a set of virtual machines that represent a physical node in an application server environment.

Before you begin

You must be granted access to the virtual application instance or have the Workload resources administration with full permissions to complete this task.

About this task

You can view the details for each virtual machine.

You can use the console or the command line interface to complete this task. For the command line information, see the Related information section.

Procedure

  1. Click Patterns > Virtual Application Instances.
  2. Select a virtual application instance.
  3. Expand Virtual machines to view a list of the virtual machines in the virtual application instance.
    The number of virtual machines is dependent on the virtual application that was deployed. You can view the following details for each virtual machine.
    Name
    This field displays the name of the virtual machine.
    Public IP
    This field displays the public IP address and fully qualified host name of the virtual machine.
    VM Status
    This field shows the status and health of the virtual machine.
    For example, if any of the following areas are greater then 75%, the status of the health is WARNING:
    • CPU
    • Memory
    • Storage
    • Current status of auto-scaling
    If any of these items exceed 90%, the health status is CRITICAL.
    Note: For CoreOS virtual machines, the CPU and Memory details are displayed as unknown.
    Log
    This link opens the log file for the virtual machine in the file viewer.
    Monitor
    This link takes you to the monitoring page for the virtual machine.
    Started on
    This column shows when the virtual machine started.
    Middleware Status
    This column shows the status of the middleware. Click Endpoint to view the endpoint for the application. Click Monitor to open the monitoring page for the middleware.
    Action
    Click Manage to display the available actions for a virtual machine. If an action is not available, it is not active.
    Stop
    If a virtual machine is running, then it can be stopped by using the stop action.
    Note:
    • The virtual machines in Stopped state are not displayed under the the Manage > Logging. Restart the virtual machines to view the entire list.
    • You must put the virtual application instance in maintenance mode before you can use this action. Click Maintain on the toolbar to put the virtual application instance in maintenance mode.
    Start
    If a virtual machine is stopped, then it can be started by using this action.
    Note: You must put the virtual application instance in maintenance mode before you can use this action. Click Maintain on the toolbar to put the virtual application instance in maintenance mode.
    Edit
    Configure the memory and processor resources of the virtual machine.
    Note: You must put the virtual application instance in maintenance mode before you can use this action. Click Maintain on the toolbar to put the virtual application instance in maintenance mode.
    Test connection
    Use this action to test the connection between Cloud Pak System Software and the deployed virtual machine.
    Login
    Use this action to open an SSH connection to the virtual machine. Click Login, and then enter the password or browse to your private key. Then, click OK.
    Script Packages
    In the Must Gather Logs section, click Execute Now to run a script package that collects the Must Gather logs and saves them to a compressed file. After the script completes, click the link for the log file to download it.
    Note: You are prompted to enter credentials when you execute the script. Leave the fields blank and click OK to proceed. These credentials are not used to run the script package. The script package runs by using the root user context. These credentials are passed to the script package so that they can be used by the script if needed for tasks such as product administration. If no credentials are needed for the tasks that are carried out by the script package, such as the Must Gather Logs script, the script completes successfully even when these credentials are left blank.