Uptime Infrastructure Monitor can collect workload information from IBM pSeries servers that have logical partitions (LPARs). For data collection to occur, you need to install an Uptime Infrastructure Monitor Agent on the Virtual I/O partition (VIO) and each LPAR whose workload you want to profile.

There are two scenarios for installing agents on IBM pSeries servers with LPARs:

In both cases, you will need to install the agent on each LPAR; installing the Uptime Infrastructure Monitor Agent on the VIO partition depends on whether you use an HMC.

Installing the Uptime Infrastructure Monitor Agent on a pSeries Server with an HMC

  1. Ensure you are logged in to the HMC as a super administrator user.
    Uptime Infrastructure Monitor communicates with the HMC to acquire LPAR information.
  2. Install Uptime Infrastructure Monitor Agents on each partition whose workload you want to monitor.
    Refer to Installing the Uptime Infrastructure Monitor Agent on an LPAR Running Linux or Installing the Uptime Infrastructure Monitor Agent on an LPAR Running AIX below, depending on which operating system is running on the partition.
  3. Once you have installed Uptime Infrastructure Monitor Agents on all LPARs, install the Agent on the VIO partition. To begin, log into the VIO as root.
  4. Run the following command:
    oem_setup_env
  5. Copy the archive containing the Agent to the partition.
  6. Extract the contents of the archive using the following command:
    tar -xvf <agentname>
    Where <agentname> is the name of the archive that contains the agent that you are installing (e.g., uptmagnt-AIX-5.1.tar).
  7. Run the following command to install the agent:
    ./INSTALL.sh

    Do not install the agent as a Virtual I/O Server by using the -vio attribute with the install command. Doing so may lead to conflicts with HMC-managed systems, and can result in incorrect performance statistics.

Installing the Uptime Infrastructure Monitor Agent on a VIO Server Using IVM

  1. Install Uptime Infrastructure Monitor Agents on each partition whose workload you want to monitor.
    Refer to Installing the Uptime Infrastructure Monitor Agent on an LPAR Running Linux or Installing the Uptime Infrastructure Monitor Agent on an LPAR Running AIX below, depending on which operating system is running on the partition.

  2. Once you have installed Uptime Infrastructure Monitor Agents on all LPARs, install the Agent on the VIO partition. To begin, log into the VIO as root.
  3. Copy the archive containing the Agent to the partition.
  4. Extract the contents of the archive using the following command:
    tar -xvf <agentName>
    Where <agentName> is the name of the archive that contains the agent that you are installing (e.g., uptmagnt-AIX-5.1.tar).
  5. Run the following command to install the agent:
    ./INSTALL.sh -vio

Installing the Uptime Infrastructure Monitor Agent on an LPAR Running Linux

If Linux is running on the LPAR, do the following to install the Uptime Infrastructure Monitor Agent:

  1. Log into the LPAR as root.
  2. Copy the .rpm file containing the Uptime Infrastructure Monitor Agent to the LPAR.
  3. Run the following command:
    rpm -i <agentName>.rpm
    Where <agentName> is the name of the .rpm file for the agent that you are installing (e.g., uptimeagent-6.0.0-linux-x86_64.rpm).

Installing the Uptime Infrastructure Monitor Agent on an LPAR Running AIX

If AIX is running on the LPAR, do the following to install the Uptime Infrastructure Monitor Agent:

  1. Log into the LPAR as root.
  2. Copy the archive containing the Uptime Infrastructure Monitor Agent to the LPAR.
  3. Extract the contents of the archive using the following command:
    tar -xvf <agentName>
    Where <agentName> is the name of the archive that contains the agent that you are installing (e.g., uptmagnt-AIX-5.1.tar).
  4. Run the following command to install the Uptime Infrastructure Monitor Agent:
    ./INSTALL.sh if the LPAR is manged by HMC

    If you are using an HMC, do not install the Agent as a Virtual I/O Server by using the -vio attribute with the install command. Doing so may lead to conflicts with HMC-managed systems, and can result in incorrect performance statistics.