Test 908: IBM Tivoli Monitoring V6.2 Implementation

Section 1 - Planning

1. Given a statement of work, interview customers in order to assess the implementation requirements to build the solution so that the system/network diagram, user requirements are obtained and installation worksheets have been completed

With emphasis on performing the following:
1. Interview customer in order to gather user requirements – systems to be monitored for availability, network topology, applications, hardware/software standards,

number of users, administrators, security requirements, budgets, and existing systems management tools to be integrated


2. Given the system/network diagram and user requirements, identify software and hardware component specifications so that a solution design is created

With emphasis on performing the following:
1. Identify OS platforms for infrastructure – Windows, Linux, UNIX, z/OS
2. Determine database platform for TDW – DB2, Oracle, MSSQL
3. Identify number, type, and location of agents required
4. Determine number of TEMS needed
5. Determine hardware configuration of TEMS – Windows, Linux, z/OS, UNIX
6. Determine hardware configuration of TEPS – Windows, Linux, UNIX
7. Identify server for Warehouse Proxy agent
8. Determine the integration solution for event management and other monitoring tools


3. Given the solution design and knowledge of current TMR deployment, identify probes to upgrade to ITM V6.2 and how to handle probes that can not be upgraded, run TME commands to assess the TMR environment so that the DM upgrade plan is created

With emphasis on performing the following:
2. Identify probes to be upgraded to ITM V6.2
3. Determine how to handle the probes that can not be upgraded.
4. Run TMR commands to assess Distributed Monitoring (DM) deployment

wlookup
wlseng
wgateway
wep


4. Given the solution design and knowledge of current ITM V5.1.x deployment, assess the TMR environment and determine which endpoints will require the integration agent so that the integration plan is created

With emphasis on performing the following:
1. Determine if ITM V5.1 meets the requirements for upgrading to ITM V6.2
2. Run TMR commands to assess ITM V5.1 deployment.

wlookup
wdmlseng
wep
wlsinst
3. Determine which ITM V5.1 endpoints require the integration agent


5. Given the solution design and knowledge of current OMEGAMON deployment, assess it so that the upgrade for OMEGAMON plan is created

With emphasis on performing the following:
1. Review current OMEGAMON deployment:

number of CMS
Hub/Remote architecture
number and type of agents deployed
custom situations
custom policies
custom queries
database type
CNPS install details
2. Based upon the finding determine how to upgrade.


6. Given the solution design, product documentation and knowledge of current ITM V6.1 deployment, assess the environment and determine which infrastructure components and TEMAs will require upgrading so that the integration plan is created

With emphasis on performing the following:
1. Identify infrastructure components and agents for upgrading
2. Verify infrastructure servers meet minimum requirements
3. Verify agent servers meet minimum requirements
4. Describe the recommended order for upgrading
5. Develop a plan for the upgrade

Section 2 - Prerequisites

1. Given the solution design, install and verify the DB2 UDB or the MS SQL 2000 database so that the prerequisite database requirement is met

With emphasis on performing the following:
1. Create DB admin users with DB administrator privileges and corresponding OS account
2. Install the appropriate version of DB2 UDB database or MS SQL 2000


2. Given the installation documentation, define the SSL requirements so that the prerequisite requirement SSL is defined

With emphasis on performing the following:
1. Windows/UNIX/Linux: GS Toolkit
2. AIX requires xlC


3. Given the ITM V6.2 product documentation, determine which databases are supported for components of ITM V6.2 so that the prerequisite requirement is met

With emphasis on performing the following:
1. TEPS: DB2 UDB or MSSQL Server 2000 SP3 at appropriate levels
2. TDW: DB2 UDB, MSSQL Server 2005 and Oracle at appropriate levels

Section 3 - Installation

1. Given the product software and the required access, log on to the TMR server, install the upgrade toolkit, and optional UNIX or Linux support via Desktop or CLI to enable the upgrade tools for ITM V5.1.2 on Framework

With emphasis on performing the following:
1. Log on to the TMR server and source the Tivoli environment
2. Demonstrate the ability to use desktop or CLI to install migration toolkit on TMR and gateways


2. Given product documentation, appropriate access and authority to infrastructure and target systems, endpoints, a TMR and the product software, install and configure the necessary components so that ITM V5.x endpoints are integrated into the ITM V6.2 environment for visualization and data warehousing

With emphasis on performing the following:
1. Demonstrate the ability to install and configure the interoperability components for ITM V5.x endpoints
2. Demonstrate the ability to visualize or collect warehouse data from ITM V5.x as a form of validation


3. Given ITM V6.2 Installation and Setup Guide, define the installation tasks required to install the application support files for OMEGAMON, so that a clear understanding of the installation steps are known

With emphasis on performing the following:
1. Install OMEGAMON application support on the monitoring server using one of the installation methods.
2. Install OMEGAMON application support on the portal server using one of the installation methods.
3. Install OMEGAMON application support on the portal desktop client using one of the installation methods.
4. Copy the product attribute file to the ATTRLIB directory on the Warehouse Proxy agent to enable the Tivoli Data Warehouse to collect data from existing OMEGAMON 350 or higher version agents.


4. Given the product software, all necessary prerequisites, appropriate access, and completed worksheets for all components, perform a product install on distributed platforms so that all ITM V6.2 infrastructure components are installed, configured, and running

With emphasis on performing the following:
1. Verify that the correct shell (KSH) is installed on Linux
2. Install infrastructure components (for example TEMS, TEPS, application support, populate depot) based on customer requirements (GUI, CLI or silent install)
3. Configure installed infrastructure components
4. Install and configure the warehouse proxy agent based on customer requirements
5. Configure TEPS with warehouse database user log in and database name
6. Install and configure the TEP Desktop
7. Start historical collection in the TEP
8. Install and configure the summarization and pruning agent as per customer requirements
9. Start (if required) and verify all installed infrastructure components


5. Given the availability of the product software, all necessary prerequisites, and completed worksheets for all components, perform a product install on a distributed platform so that necessary TEMAs are installed, configured, and running

With emphasis on performing the following:
1. Verify that the host system or application meets the minimum requirements for installing a TEMA
2. Install and configure TEMA on local system based on customer requirements
3. Remote deploy and configure a TEMA based on customer requirements
4. Start the TEMA(s) if needed
5. Verify TEMA connection to TEMS


6. Given product software and documentation, appropriate access and authorization to the TEMS, TEC, TMR, and ObjectServer, install and configure event synchronization so that events are synchronized to meet customer needs

With emphasis on performing the following:
1. Install event synchronization on the event server
2. Map ITM V6.2 events to the event server
3. Configure the TEMS to forward events to the event server
4. Restart the synchronization on the event server


7. Given installed ITM 6.2 infrastructure components and the administrator privileges, uninstall the product using the appropriate method so that all infrastructure components are uninstalled

With emphasis on performing the following:
1. Stop the components to be uninstalled
2. Click Add/Remove Programs (on Windows) and remove it
3. Run the $CANDLEHOME/bin/uninstall.sh command and select the product to be removed


8. Given a valid user ID and password, utilize the browser, Desktop or WebStart client to connect to the TEPS so that the TEP session is initiated

With emphasis on performing the following:
1. Utilize and confirm browser connectivity to TEPS
2. Utilize and confirm Desktop connectivity to TEPS
3. Utilize and confirm WebStart connectivity to TEPS


9. Given ITM V6.2 Installation and Setup Guide, define when the Candle Management Workstation (CMW) will be available, so that there is a clear understanding of the differences between a new IBM Tivoli Monitoring V6.2 installation and an upgrade to IBM Tivoli Monitoring V6.2

With emphasis on performing the following:
1. Upgrade a OMEGAMON 350 or 360 environment to IBM Tivoli Monitoring V6.2. If you currently use Candle Management Workstation (CMW) in your OMEGAMON monitoring environment, you are migrated to IBM Tivoli Monitoring V6.2 automatically when you migrate the rest of your environment. However, the installed Candle Management Workstation (CMW) continues to function after the migration, although it is not officially part of IBM Tivoli Monitoring V6.2 and no new function has been added


10. Given that the Warehouse Proxy and Summarization and Pruning agents are installed, drop the database, remove the data source and user, and run the platform specific method so that the Warehouse Proxy and the Summarization and Pruning agents are uninstalled

With emphasis on performing the following:
1. Drop the warehouse database
2. Remove the ODBC/JDBC data source
3. Remove the user “ITMUser” that was created to connect to the DB2 database
4. Use the platform specific method to remove the Warehouse Proxy, Summarization and Pruning agent (if installed)


11. Given ITM V6.2.0 Installation and Setup Guide, run the uninstall program following the prompts, and recycle the event server so that the IBM Enterprise Console event synchronization is uninstalled

With emphasis on performing the following:
1. Run the following uninstall program and follow the prompts:

On Windows: \TME\TEC\OM_TEC\_uninst\uninstaller.exe
On UNIX: /TME/TEC/OM_TEC/_uninst/uninstaller.binwhere is the $BINDIR directory on the event server.
2. Stop and restart the event server for the changes to take effect

Section 4 - Configuration

1. Given the product documentation, appropriate authority and access to ITM V5.x and ITM V6.2 infrastructure, configure and distribute the 5.x endpoint agent so that the interoperatibility is configured and functioning properly

With emphasis on performing the following:
1. Install and configure the ITM V5.x endpoint agent to the required endpoint(s)
2. Demonstrate the ability to configure the DataSeeding and data collection for endpoint
3. Demonstrate the ability to enable historical configuration through TEP
4. Demonstrate the ability to verify and view endpoint data through TEP


2. Given an existing Tivoli Distributed Monitoring 3.7 environment, product documentation, product software and access to the infrastructure, TMR servers and endpoints, examine the Tivoli TMR using Tivoli CLI commands and the Tivoli Desktop GUI so that a list of “to be converted” Tivoli Distributed Monitoring 3.7 monitoring probes are obtained

With emphasis on performing the following:
1. Demonstrate the ability to assess the DM V3.7 environment for a migration to ITM V6.2


3. Given an existing ITM V5.1 monitoring environment, appropriate access to the ITM V6.2 infrastructure, TMR, gateways, endpoints, product documentation, and product software, utilize the upgrade toolkit to assess and analyze the environment so that ITM V5.x endpoints can be migrated properly

With emphasis on performing the following:
1. Demonstrate the ability to scan the TMR using the GUI or the CLI
2. Demonstrate the ability to analyze results to determine the servers to be migrated
3. Demonstrate the ability to migrate endpoints, profiles, profile managers per customer requirements


4. Given an existing DM V3.7 monitoring environment, appropriate access to the ITM V6.2 infrastructure, TMR, gateways, endpoints, product documentation, product software, utilize the upgrade toolkit to assess and analyze the environment so that DM V3.7 endpoints can be migrated properly

With emphasis on performing the following:
1. Demonstrate the ability to utilize assessed results for migration planning
2. Demonstrate the ability to upgrade and migrate endpoints
3. Demonstrate the ability to migrate profiles and profile managers
4. Demonstrate the ability to utilize TEP and verify endpoint migration


5. Given a properly configured ITM V6.1 monitoring environment, appropriate access to the ITM V6.1 infrastructure, product documentation, and product software, upgrade the ITM V6.1 environment to ITM V6.2 so that customer requirements are met

With emphasis on performing the following:
1. Back up ITM V6.1 infrastructure
2. Verify ITM V6.1 infrastructure meets minimum requirements of ITM V6.2
3. Shutdown all Infrastructure Components that will be upgraded
4. Upgrade and configure Infrastructure components in the correct order
5. Verify agent servers meet minimum requirements
6. Upgrade agent using CLI
7. Verify agent upgrade through TEP or CLI


6. Given product documentation, product software, appropriate access and authority to ITM V6.2 infrastructure and servers to be monitored, effectively implement custom monitoring solutions using the Universal Agent so that customer monitoring requirements can be met

With emphasis on performing the following:
1. Determine which custom agent creation tool should be used to achieve the objective
2. Describe the appropriate application and proper use of the data providers included with the Universal Agent
3. Demonstrate how the Universal Agent (UA) can be effectively implemented to address a given business requirement


7. Given the agent builder toolkit, ITM V6.2 environment, appropriate access, authority and product documentation, install and configure the agent builder toolkit and develop the agent so that custom agents can be deployed

With emphasis on performing the following:
1. Determine which custom agent creation tool should be used to achieve the objective
2. Demonstrate the ability to install and configure the Agent Builder toolkit
3. Demonstrate the ability to create an agent using the appropriate data monitoring types, plug-ins, or agent extensions
4. Demonstrate the ability to test and debug an agent
5. Demonstrate the ability to modify and remove an agent
6. Demonstrate the ability to package and deploy the agent


8. Given an installed ITM 6.2 infrastructure, configure the security feature so that only authorized individuals will be validated on TEP

With emphasis on performing the following:
1. Enabling security on the hub monitoring server
2. Generate user account via LDAP or TEMS (or ensure that one exists)
3. Generate TEP user account that matches LDAP or TEMS user ID
4. Validate that authentication occurs via TEMS or LDAP


9. Given ITM V6.2 Command reference Guide, define the tacmd and the itmcmd commands so that a clear understanding of their uses are known

With emphasis on performing the following:
1. Define the tacmd command
2. Define the itmcmd command


10. Given an ITM V6.2 Installation and Setup Guide, define the configuration tasks of Manage Tivoli Enterprise Monitoring Services so that a clear understanding of its uses is known

With emphasis on performing the following:
1. The “Change the configuration of the monitoring server” is used for identifying the communication protocols for the monitoring server
2. The “configure agents and other monitoring components” is used for identifying the communication protocols for the monitoring agents
3. The “start and stop components” is used for starting, stopping, and recycling the IBM Tivoli Monitoring components
4. The “configure security” is used for controlling who has access to the Tivoli Enterprise Portal through the use of user IDs and Passwords as well as enabling security for the hub monitoring server
5. The “Add application support to the monitoring server” is used to add application support to the monitoring server
6. The “Manage IBM Tivoli Monitoring log files” is used to view trace log files for the IBM Tivoli Monitoring components and edit the level of trace information that is collected


11. Given the customer’s environment, install and configure the Universal Agent so that the data provider can connect to applications and provide custom monitoring solutions

With emphasis on performing the following:
1. Install the Universal Agent
2. Configure the data providers for the Universal Agent
3. Start the Universal Agent and verify that the data providers are connecting to applications

Section 5 - Performance Tuning and Problem Determination

1. Given product documentation and access to the ITM V5.x and ITM V6.2 infrastructure, troubleshoot issues with integrated ITM V5.x endpoints utilizing the logs so that endpoint agent issues can be resolved

With emphasis on performing the following:
1. Determine if ITM V5.x endpoint agent is started
2. Demonstrate the ability to identify and review logs for error messages
3. Demonstrate the ability to increase appropriate trace logging for additional information
4. Analyze logs to determine root cause


2. Given the Managed Systems have a status other than ONLINE, review logs or status on TEMS to determine cause of problem so that corrective action can be taken and agent is successfully connected to TEMS

With emphasis on performing the following:
1. Validate if agent is started
2. Recycle agent
3. Validate configuration of agent to TEMS
4. Review agent logs
5. Set the appropriate trace level for the agent and recycle the agent if required
6. Identify and analyze error messages or inconsistencies in the logs
7. Correct the error or modify configuration parameters using MTEMS or CLI
8. Restart the agent


3. Given clients unable to connect to TEPS or log on to the TEP, determine the root cause of the problem by reviewing TEPS and TEMS configuration and logs so that connectivity is restored

With emphasis on performing the following:
1. Determine if TEPS is running
2. Determine if TEMS is running
3. Review configuration of TEPS to TEMS
4. Set the appropriate trace level for TEMS or TEPS and recycle
5. Review network connectivity issues (firewall, logs, DNS, IP ports, multiple network cards)
6. Review ITM V6.2 logs
7. Modify TEPS configuration parameters where necessary
8. Verify log on to TEP


4. Given clients unable to log on to TEP via browser, Web Start client or desktop, determine root cause of logon problem by reviewing TEP, TEPS, and TEMS configuration and logs so that connectivity is restored

With emphasis on performing the following:
1. Determine if TEPS is running and can communicate with the database
2. Determine if TEMS is running
3. Review configuration of TEP client
4. Set the appropriate trace level
5. Review logs for network connectivity and security issues
6. Review ITM V6.2 logs
7. Modify TEP, TEPS, and TEMS configuration parameters where necessary
8. Verify log on to TEP


5. Given an authorized user is unable to log on to TEP, determine cause of the problem by analyzing messages in ITM V6.2 logs and validate user accounts so that the users can successfully log on to TEP

With emphasis on performing the following:
1. Ensure users are defined in TEPS
2. If security is enabled, ensure user IDs (local TEMS account, domain or LDAP account) are valid in TEMS
3. Have system administrator validate user account exist on the TEMS server
4. Analyze messages to determine other possible causes in the logs


6. Given no historical data older than 24 hours (default) is displayed on TEP, verify that the warehouse DB exists, summarization and pruning agent is configured correctly and warehouse proxy agent is running so that historical data is correctly displayed

With emphasis on performing the following:
1. Verify that the warehouse database exists
2. Check if warehouse proxy agent is running
3. Check if there is data in paired files (e.g., WTLOGCLDSK & WTLOGCLDSK.HDR)
4. Check whether you can connect to the data warehouse through the CandleNet Warehouse data source
5. Use the Historical Configuration panel to ensure that historical data collection (HDC) is enabled to collect data
6. Verify that configuration for the particular attribute group is correctly set and collection started
7. Ensure summarization and pruning agent is properly configured


7. Given that data is not being summarized and pruned according to the parameters set, ensure summarization and pruning agent is running and configured appropriately and the database is running so that the data is being summarized and pruned

With emphasis on performing the following:
1. Check if summarization and pruning (S&P) agent is running
2. Ensure S&P agent configuration is correct
3. Analyze if there is any warehouse database problem (e.g., table does not exist )
4. Review log files
5. Recycle the S&P agent if necessary


8. Given users unable to log on to TEPS, open workspaces or no data in workspaces, ensure TEPS is running, verify TEPS tables exist, and ODBC/JDBC entry is valid so that connectivity is restored and users are able to log in

With emphasis on performing the following:
1. Verify TEPS is running and verify configuration of TEPS
2. Verify valid ODBC/JDBC entry for TEPS
3. Verify tables in TEPS database exist (e.g., table names with KFW-prefix)
4. Analyze messages in log files


9. Given high CPU overhead at the agent or the TEMS and an excessive number of active situations, ensure that situations are reused where appropriate, only enable those that are active so that situations will execute efficiently and reduce overhead on TEMS

With emphasis on performing the following:
1. Use same situations across similar/same systems (do not duplicate)
2. Stop situations that are not used or relevant
3. Organize the situations for efficiency
4. Use same sampling interval for situations using same attributes
5. Optimize use of sampling intervals for different types of data
6. Minimize the use of action-taking and display items so that the situations can be “duper” eligible


10. Given a slow running workspace, avoid on-demand sampling, filter at the query source, or be as specific as possible to minimize result rows for display so that overhead to TEPS can be reduced

With emphasis on performing the following:
1. Avoid auto refresh unless necessary
2. Avoid having multiple workspaces with auto refresh open at the same time
3. Create queries to return only data required for your view or workspace
4. Use same query for different views on the same workspace to potentially reduce the overhead


11. Given ITM V6.2 Administrator’s Guide, define and configure the Tivoli Enterprise Monitoring Web Service and its uses so that a clear understanding of the uses is known

With emphasis on performing the following:
1. Define hub server and configure server
2. Define uses for Tivoli Enterprise Monitoring web services

Section 6 - Administration

1. Given the customer monitoring requirements, log on to TEP, open the situation editor to create and manage situations so that the events are raised to the event console at appropriate severity level

With emphasis on performing the following:
1. View a list of situations running on this managed system, the same types of managed systems, or on the enterprise
2. View the definition of a situation
3. Create a new situation or edit a situation
4. Delete a situation
5. Start or stop a situation
6. Distribute a situation to a managed system or managed system list
7. Associate a situation with the current Navigator item
8. Use embedded situations in your situation formula
9. Create correlated situations across multiple types of managed situation


2. Given the product documentation and appropriate access and integrated event servers, configure TEPS so that events from ITM V6.2, TEC and NetCool OMNIbus are viewable in the Common Event Console

With emphasis on performing the following:
1. Configure the common event connectors in TEPS
2. Validate the events in the TEP Common Event Console


3. Given the ITM V6.2 infrastructure components are installed, select queries, filters, and styles to create a customized workspace in order to visualize ITM V6.2 monitoring data

With emphasis on performing the following:
1. Create workspace so items can be viewed as per customer requirements


4. Given customer monitoring requirements, use Situation Editor from a managed system in the Navigator view to modify existing situations so that when thresholds are met, situation events will be opened

With emphasis on performing the following:
1. Utilize Situation Editor to modify situations to meet customer requirements


5. Given customer monitoring requirements, use Situation Editor to create new situations so that when thresholds are met, situation events will be opened

With emphasis on performing the following:
1. Utilize Situation Editor to create situations to meet customer requirements


6. Given the IBM Tivoli Monitoring V6.2 documentation, describe the relationship between attributes and attribute groups to show an understanding of attributes and attribute groups

With emphasis on performing the following:
1. An attribute is a parameter that gets collected by the agent
2. Attribute groups are collections of logically grouped attributes that belong to a portion of a resource to be monitored


7. Given the IBM Tivoli Monitoring V6.2 documentation and appropriate access and authority to the ITM V6.2 infrastructure, demonstrate the ability to back up and recover key ITM V6.2 configuration files and databases so that business continuity can be maintained or migrations can be performed

With emphasis on performing the following:
1. Describe the utilities included with ITM V6.2 that can be used to back up and recover the ITM V6.2 environment
2. Describe what components, databases, and files in the ITM V6.2 infrastructure need to be backed up
3. Demonstrate the ability to back up the appropriate files to successfully restore the TEMS
4. Demonstrate the ability to back up the appropriate files and databases to successfully restore the TEPS