To configure the monitoring agent, you must complete specific
steps.
About this task
Before you configure your monitoring agent, complete the
following tasks:
- Ensure that one of the VIOS V2.2.1 releases or V2.2.2
releases is running.
- Verify that you know the correct user ID, password, and host name
of the HMC and have established an SSH connection to the HMC.
- The VIOS agent must be configured and started under the padmin
user ID.
- Verify that this LPAR has the Allow processor pool utilization
authority or Allow performance information collection option
checked in the Hardware Management Console (HMC), if you want to monitor
the Available CPU Units in Pool attribute.
Procedure
To configure and start the monitoring agent, perform
the following steps:
Note: This procedure can also be used to configure
the IBM Tivoli Monitoring CEC
Base agent that is installed on the VIOS. Replace the string ITM_premiumwith ITM_cec and
repeat the configuration steps.
- List all available monitoring agents by using the lssvc command. For example:
$lssvc
ITM_premium
- Based on the output of the lssvc command,
specify the monitoring agent that you want to configure (in this case,
ITM_premium).
- List all attributes that are associated with the monitoring
agent using the cfgsvc command. For
example:
$cfgsvc -ls ITM_premium
HOSTNAME
RESTART_ON_REBOOT
MANAGING_SYSTEM
- Configure the monitoring agent with its associated attributes
by using the cfgsvc command: For
example:
$cfgsvc ITM_agent_name -attr Restart_On_Reboot=value hostname=address1 mirror=address2
managing_system=address3
Where:
- ITM_agent_name
- Name of the monitoring agent. For example, ITM_premium for the
VIOS Premium agent.
- value
- Either TRUE or FALSE:
- TRUE: ITM_agent_name restarts when the Virtual I/O Server restarts.
- FALSE: ITM_agent_name does not restart whenever the Virtual I/O
Server restarts.
- address1
- Either the host name or IP address of the Tivoli Enterprise
Monitoring Server to which the
agent sends data.
- address2
- Either the host name or IP address of the backup or secondary Tivoli Enterprise
Monitoring Server to which the
agent connects if the primary Tivoli Enterprise
Monitoring Server is unavailable.
- address3
- Either the host name or 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. In this field, address can
be specified as HMCuser@HMChostname if the administrator wants to
specify an HMC user ID other than hscroot on the HMC host. If the
HMCuser ID is not specified, it is assumed to be hscroot.
Note: address3 can
also be the host name or IP address of the IBM Flex System Manager
(FSM), in which case address3 can be specified
as FSMuser@FSMhostname.
Examples:
- cfgsvc ITM_premium -attr Restart_On_Reboot=TRUE hostname=tems_server
managing_system=hmc_console
In this example, the ITM_premium
monitoring agent is configured to send data to tems_server, and to
restart whenever the Virtual I/O Server restarts.
- cfgsvc ITM_premium -attr Restart_On_Reboot=TRUE hostname=tems_server
managing_system=hmcuser@hmc_console
In this example the
HMC user ID (hmcuser) is specified to be different from hscroot.
- The cfgsvc command configures default
values for IBM Tivoli Monitoring -specific
values. Use the itmcmd command to configure nondefault Tivoli Monitoring configuration
values (such as KDC_FAMILIES):
- Enter the AIX shell:
oem_setup_env
- Run the itmcmd configcommand:
# /opt/IBM/ITM/bin/itmcmd config -A va.
- Respond to the prompts to set protocols for communicating to the Tivoli Enterprise
Monitoring Server and the ports
to use for communication methods as you do for any IBM Tivoli Monitoring
agent not in a VIOS environment.
- From the HMC, complete the following steps to enable the
monitoring agent to gather information from the HMC. 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. This server is the
name of the CEC.
- 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
- Name of the CEC to be monitored.
- vios_name
- Name of the Virtual I/O Server logical partition (with the monitoring
agent or client) as defined on the HMC.
- ITM_agent_name
- Name of the monitoring agent. For example, ITM_premium.
- 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.
For
example:
$ viosvrcmd -m commo126041 -p VIOS7 -c "cfgsvc ITM_premium -key"
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvjDZsS0guWzfzfp9Bbwe\
G0QMXv1tbDrtyWsgPbA2ExHA+xduWA51K0oFGarK2FC7e7Nj\
KW+UmgQbrh/KSyKKwozjp4xWGNGhLmfan85ZpFR7wy9UQG1b\
LgXZxYrY7yyQQQODjvwosWAfzkjpG3iW/xmWD5PKLBmob2QkKJ\
bxjne+wqGwHTRYDGIiyhCBIdfFaLZgkXTZ2diZ98rL8LIv3qb+TsM1B\
28AL4t+1OGGeW242lsB+8p4kamPJCYfKePHo67yP4NyKyPBFHY\
3TpTrca4/y1KEBT0Va3Pebr5JEIUvWYs6/RW+bUQk1Sb6eYbcRJFH\ hN5l3F+ofd0vj39zwQ==
root@vios7.vios.austin.ibm.com
$ mkauthkeys --add 'ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvjDZsS0guWzfzfp9Bbwe\
G0QMXv1tbDrtyWsgPbA2ExHA+xduWA51K0oFGarK2FC\
7e7NjKW+UmgQbrh/KSyKKwozjp4xWGNGhLmfan85Zp\
FR7wy9UQG1bLgXZxYrY7yyQQQODjvwosWAfzkjpG\
3iW/xmWD5PKLBmob2QkKJbxjne+wqGwHTRYDGIiyh\
CBIdfFaLZgkXTZ2diZ98rL8LIv3qb+TsM1B28AL4t+1OG\
GeW242lsB+8p4kamPJCYfKePHo67yP4NyKyPBFHY\
3TpTrca4/y1KEBT0Va3Pebr5JEIUvWYs6/RW+bUQk1\
Sb6eYbcRJFHhN5l3F+ofd0vj39zwQ==
root@vios7.vios.austin.ibm.com'
- Start the monitoring agent by using the startsvc command. For example: $startsvc ITM_premium
- See the following commands for more information:
- cfgsvc (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphcg/cfgsvc.htm)
- lssvc (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphcg/lssvc.htm)
- startsvc (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphcg/startsvc.htm)
- stopsvc (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphcg/stopsvc.htm)
What to do next
When you are finished, you can view the data gathered by
the monitoring agent from the Tivoli Enterprise
Portal.