Configuring the IBM Tivoli Monitoring agent

You can configure and start the IBM® Tivoli® Monitoring agent on the Virtual I/O Server.

With Tivoli Monitoring System Edition for System p®, you can monitor the health and availability of multiple IBM System p servers (including the Virtual I/O Server) from the Tivoli Enterprise Portal. IBM Tivoli Monitoring System Edition for System p gathers data from the Virtual I/O Server, including data about physical volumes, logical volumes, storage pools, storage mappings, network mappings, real memory, processor resources, mounted file system sizes, and so on. From the Tivoli Enterprise Portal, you can view a graphical representation of the data, use predefined thresholds to alert you on key metrics, and resolve issues based on recommendations provided by the Expert Advice feature of Tivoli Monitoring.

Before you start, complete the following tasks:

Ensure that the Virtual I/O Server is running fix pack 8.1.0. For instructions, see Updating the Virtual I/O Server.
Verify that you are a super administrator of the HMC.
Verify that you are the prime administrator of the Virtual I/O Server.

To configure and start the monitoring agent, complete the following steps:

List all of the available monitoring agents using the lssvc command. For example,
```
$lssvc
ITM_base
```
Based on the output of the lssvc command, decide which monitoring agent you want to configure. For example, ITM_base
List all of the attributes that are associated with the monitoring agent using the cfgsvc command. For example:
```
$cfgsvc –ls ITM_base
 HOSTNAME
RESTART_ON_REBOOT
MANAGING_SYSTEM
```
Configure the monitoring agent with its associated attributes using the cfgsvc command:
```
cfgsvc ITM_agent_name -attr Restart_On_Reboot=value hostname=name_or_address1 
managing_system=name_or_address2
```
Where:
- ITM_agent_name is the name of the monitoring agent. For example, ITM_base.
- value must be either TRUE of FALSE as follows:
  - TRUE: ITM_agent_name restarts whenever the Virtual I/O Server restarts
  - FALSE: ITM_agent_name does not restart whenever the Virtual I/O Server restarts
- name_or_address1 is either the hostname or IP address of the Tivoli Enterprise Monitoring Server (TEMS) server to which ITM_agent_name sends data.
- name_or_address2 is either the hostname of IP address of the Hardware Management Console (HMC) attached to the managed system on which the Virtual I/O Server with the monitoring agent is located.
For example:
```
cfgsvc ITM_base –attr Restart_On_Reboot=TRUE hostname=tems_server managing_system=hmc_console
```
In this example, the ITM_base monitoring agent is configured to send data to tems_server, and to restart whenever the Virtual I/O Server restarts.
Start the monitoring agent using the startsvc command. For example:
```
startsvc ITM_base
```

From the HMC, complete the following steps so that the monitoring agent can gather information from the HMC.

Note: After you configure a secure shell connection for one monitoring agent, you do not need to configure it again for any additional agents.

Determine the name of the managed system on which the Virtual I/O Server with the monitoring agent is located.
Obtain the public key for the Virtual I/O Server by running the following command:
```
viosvrcmd -m managed_system_name -p vios_name -c "cfgsvc -key ITM_agent_name"
```
Where:
- managed_system_name is the name of the managed system on which the Virtual I/O Server with the monitoring agent or client is located.
- vios_name is the name of the Virtual I/O Server logical partition (with the monitoring agent) as defined on the HMC.
- ITM_agent_name is the name of the monitoring agent. For example, ITM_base.
Update the authorized_key2 file on the HMC by running the mkauthkeys command:
```
mkauthkeys --add public_key
```
where public_key is the output from the viosvrcmd command in step 6b.

For example:

$ viosvrcmd -m commo126041 -p VIOS7 -c "cfgsvc ITM_base -key"
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvjDZ
  sS0guWzfzfp9BbweG0QMXv1tbDrtyWsgPbA2ExHA+xduWA51K0oFGarK2F
  C7e7NjKW+UmgQbrh/KSyKKwozjp4xWGNGhLmfan85ZpFR7wy9UQG1bLgXZ
  xYrY7yyQQQODjvwosWAfzkjpG3iW/xmWD5PKLBmob2QkKJbxjne+wqGwHT
  RYDGIiyhCBIdfFaLZgkXTZ2diZ98rL8LIv3qb+TsM1B28AL4t+1OGGeW24
  2lsB+8p4kamPJCYfKePHo67yP4NyKyPBFHY3TpTrca4/y1KEBT0Va3Pebr
  5JEIUvWYs6/RW+bUQk1Sb6eYbcRJFHhN5l3F+ofd0vj39zwQ== root@vi
  os7.vios.austin.ibm.com
$ mkauthkeys --add 'ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvjDZ
  sS0guWzfzfp9BbweG0QMXv1tbDrtyWsgPbA2ExHA+xduWA51K0oFGarK2F
  C7e7NjKW+UmgQbrh/KSyKKwozjp4xWGNGhLmfan85ZpFR7wy9UQG1bLgXZ
  xYrY7yyQQQODjvwosWAfzkjpG3iW/xmWD5PKLBmob2QkKJbxjne+wqGwHT
  RYDGIiyhCBIdfFaLZgkXTZ2diZ98rL8LIv3qb+TsM1B28AL4t+1OGGeW24
  2lsB+8p4kamPJCYfKePHo67yP4NyKyPBFHY3TpTrca4/y1KEBT0Va3Pebr
  5JEIUvWYs6/RW+bUQk1Sb6eYbcRJFHhN5l3F+ofd0vj39zwQ== root@vi
  os7.vios.austin.ibm.com'

When you are finished, you can view the data gathered by the monitoring agent from the Tivoli Enterprise Portal.