IBM Tivoli Monitoring

A 32-bit IBM Tivoli Monitoring 6.2.1 AMI, based on the Linux operating system is available for production use. This AMI has been pre-bundled with both agent-based and agent-less monitoring solutions for Linux and Windows OS environments.

The IBM Tivoli Monitoring AMI is designed primarily as a monitoring appliance, acting as a management hub for collecting and reporting on the data metrics gathered by IBM Tivoli Monitoring agents. The IBM Tivoli Monitoring agents monitor other AMI’s that you are developing, or using in a production mode within the Amazon EC2 environment. This offering is only provided as a paid AMI; there is no development IBM Tivoli Monitoring AMI available at this time.

Yes. The Tivoli Monitoring agent-less monitoring and Universal Agent components will support monitoring of any instance size (32 or 64 bit); the Tivoli Monitoring agent-based monitoring will only support monitoring of 32-bit environments. The Tivoli Monitoring AMI is available in three different images, depending on the size of your monitored environment. All three Tivoli Monitoring AMIs are based on a 32-bit EC2 instance.

See AMI pricing details on Amazon. The three Tivoli AMIs are priced based on the number of virtual cores being monitored, which is calculated by multiplying the number of EC2 instances that you want to manage by the number of virtual cores allocated to your EC2 instances. Find more information about Amazon EC2 instance types and their associated virtual cores on Amazon.

Below are the three Tivoli Monitoring AMI images available based on the maximum number of virtual cores being monitored:

The IBM Tivoli Monitoring AMI comes pre-bundled with both Linux and Windows OS agents. Both agent-based and agent-less monitors have been preinstalled and pre-configured with the AMI. You can use the IBM Tivoli Monitoring AMI to remote deploy these OS agents to other AMI’s you are developing, or using in a production mode. In addition, the Tivoli Monitoring AMI is bundled with the install image associated with the Tivoli Monitoring Universal Agent (UA) package. This type of agent can be used to monitor environments not currently covered by any existing Tivoli Monitoring solutions. For a complete list of the agent packages available for deployment and installation, see the IBM Tivoli Monitoring Amazon Machine Image Get Started Guide.

Yes. The Tivoli Monitoring AMI has been pre-installed with data warehousing support, but these components are not activated by default at start-up. To configure and start the Tivoli Monitoring data warehousing support, see Create the Tivoli Data Warehouse data-base in the IBM Tivoli Monitoring documentation.

Yes. Assuming that you have existing product licenses for other IBM Tivoli Monitoring agent solutions that are compatible with IBM Tivoli Monitoring v6.2.1, you can add these monitoring agents to your IBM Tivoli Monitoring AMI and then rebundle the AMI for deployment and activation. For more details, see the IBM Tivoli Monitoring Amazon Machine Image (AMI) Rebundling Guide.

Yes. Existing IBM Tivoli Monitoring licenses can be used to create AMIs and run them in Amazon EC2. A Processor Value Unit conversion table is available to assist you in determining PVUs required for each instance size in Amazon EC2.

For detailed instructions, see the IBM Tivoli Monitoring Amazon Machine Image Get Started Guide.

Community assistance is available from the Tivoli and AWS online forums. If you have an existing IBM Tivoli Monitoring Enterprise license that you are using with your IBM Tivoli Monitoring AMI, you can contact IBM support.

Use the AWS Elastic IP address feature to allocate a pool of public static ad-dresses that you can associate with a running AMI instance. After you assign the Elastic IP address to the IBM Tivoli Monitoring AMI, run the following commands from a terminal session connected to your IBM Tivoli Monitoring AMI to reconfigure the IBM Tivoli Monitoring AMI with the new public IP address you have assigned:

cd /opt/IBM/ITM/bin
./manage_itm.sh reset

This procedure is only required if you launch a new IBM Tivoli Monitoring AMI instance and want to ensure that the public IP address used by clients, or other IBM Tivoli Monitoring agents running on your managed AMI’s, stays the same. This procedure is not required if you simply reboot a running IBM Tivoli Monitoring AMI instance. An AMI reboot does not change the public IP address used by the rebooted instance.

The IBM Tivoli Monitoring AMI startup scripts automatically start all required components when you reboot. The Linux OS agent is also restarted, but please be patient as this process can take up to 10 minutes to complete.