Test 887: IBM Tivoli Monitoring Express V6.1 Specialist

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 documented.

With emphasis on performing the following steps:
1. Interview customer in order to gather user requirements – systems to be monitored for availability, network topology, applications, hardware/software standards,
2. number of users, administrators, security requirements, budgets, existing systems management tools.


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

With emphasis on performing the following steps:
1. Identify Windows operating system version for infrastructure. (Windows 2003 Server SP1, Windows 2000 Server and Advanced Server).
2. Determine database platform for Tivoli Data Warehouse – DB2 Express, DB2 Enterprise Edition V8.2, or MSSQL.
3. Identify number and type of agents required not to exceed 100 servers per terms and conditions.
4. Determine hardware configure for IBM Tivoli Monitoring Express Management Server.

Section 2: Installing

1. Given the solution design, install IBM Tivoli Monitoring Express V6.1 (ITM Express) and DB2 Express from the Launchpad so that ITM Express is installed.

With emphasis on performing the following steps:
1. From Launchpad, there are the Welcome message, Release Notes, Systems Requirement document, Getting Started Guide, and License Upgrade “launchers” available in addition to product installation.
2. From Launchpad, on installation click the install DB2 Express button. The DB2 Express installer will launch. @Specify a typical installation, the install path, and pick a db2admin password that it will use to create the db2admin account.
3. Specify installation path for ITM Express the Launchpad.
4. Specify and confirm sysadmin password in the Launchpad
5. Specify and confirm DB2 admin ID/password you want to use (that you provided in DB2 Express install).
6. Check/uncheck install Windows OS Agent in the Launchpad
7. Check/uncheck install UNIX Agents for remote deployment in the Launchpad
8. Load license file if not installing as trial code.


2. Given installed ITM Express V6.1 infrastructure components on Windows and database administrator password, uninstall the product using the Windows control panel so that all infrastructure components are uninstalled from Windows.

With emphasis on performing the following steps:
1. From the desktop, click Start -->Settings -->Control Panel (for Windows 2000) or Start -->Control Panel (for Windows 2003).
2. Click Add/Remove Programs.
3. Select IBM Tivoli Monitoring and click Change/Remove. The following window is displayed.
4. Select Remove and click Next. The following window is displayed.
5. Confirm the uninstall and removal for the Tivoli Enterprise Portal Service database.
6. Enter database administrator password.


3. Given a mounted product CD or image, select and install products to the depot via command line so that product packages are available for remote deployment.

With emphasis on performing the following steps:
1. Launch command window and authenticate with tacmd login command.
2. Select or create the install directory.
3. Select to install products to depot via command line.
4. Select install language.
5. Read and accept the product license agreement.
6. Select remote deploy packages and exit.

Section 3: Configuring

1. Given IBM Tivoli Monitoring Express V6.1 (ITM Express) infrastructure components are installed, and a list of User IDs to be created, create users in Tivoli Enterprise Portal (TEP), and define the matching User IDs on the operating system so that users can access TEP after entering a valid User ID and password.

With emphasis on performing the following steps:
1. Enabling security on the monitoring server: In Manage Tivoli Enterprise Monitoring Services, right-click the monitoring server and click Reconfigure.
2. Creating a user on the Tivoli Enterprise Portal: In the Tivoli Enterprise Portal, click Edit -->Administer Users.
3. Type a user ID, user name, and optional description for the user, then “OK” and “OK” to close the window.
4. Define a matching Windows user ID with password to the network domain or to the host where the monitoring server resides.


2. Given the IBM Tivoli Monitoring Installation and Set-up Guide, define the command tacmd so that a clear understanding of its’ uses are known.

With emphasis on performing the following steps:
1. The command tacmd createSit is used to create a new situation.
2. The command tacmd deleteSit is used to delete a situation from the environment.
3. The command tacmd editSit is used to edit a situation.
4. The command tacmd help is used to display the name of all the available CLI commands along with a short description of each command.
5. The command tacmd listSit is used to list the situations on the hub monitoring server and can optionally filter the list for those distributed to a particular managed system or managed system type.
6. The command tacmd login is used to authenticate with the operating system and create a security token necessary for issuing subsequent tacmd commands during the current work session.
7. The command tacmd logout is used to disable the security token created by the command tacmd login.
8. The command tacmd viewDepot is used to display the names of the monitoring agent types available on the monitoring server.
9. The command tacmd viewSit is used to view the definition of a situation in your monitored environment.


3. Given IBM Tivoli Monitoring V6.1 Universal Agent User’s Guide, the data providers available within the Universal Agent have been defined so that the data provider types are known.

With emphasis on performing the following steps:
1. The Universal Agent (UA) data provider API Server enables you to collect data from resources on remote machines where the ITM Express UA API software is supported.
2. The Universal Agent data provider ASFS consolidates four types of data providers into one package which is started as a single thread to save resource usage.
3. The Universal Agent data provider File monitors sequential files such as system or message logs.
4. The Universal Agent data provider HTTP allows the monitoring of Internet URLs for availability and response time.
5. The Universal Agent data provider ODBC allows data collection from ODBC-compliant databases using SQL Select statements and stored procedures.
6. The Universal Agent data provider Post is a TCP/IP socket application with predefined data that enables you to send ad hoc notifications such as messages, alerts, and status.
7. The Universal Agent data provider Script allows data collection from any script or program that sends results to standard output.
8. The Universal Agent data provider SNMP provides the functionality of an SNMP manager, including network discovery, trap monitoring, and MIB data collection.
9. The Universal Agent data provider Socket listens to a TCP/IP socket for data sent using program-to-program communication and enables you to collect data from remote devices or machines for which no ITM Express Agent API support is available.


4. Given IBM Tivoli Monitoring V6.1 Installation and Setup Guide, define the configuration tasks of Manage Tivoli Enterprise Monitoring Web Services so that a clear understanding of the uses is known.

With emphasis on performing the following steps:
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 Express 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 for the 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 Express components and edit the level of trace information that is collected.


5. Given infrastructure components to be installed on Windows, launch Manage Tivoli Enterprise Monitoring Services (MTEMS), reconfigure the Tivoli Enterprise Monitoring Server (TEMS), agents, Tivoli Enterprise Portal Server (TEPS), and Tivoli Enterprise Portal (TEP) so that the components are configured and operational.

With emphasis on performing the following steps:
1. Start Manage Tivoli Monitoring Services by clicking Start -->Programs -->IBM Tivoli Monitoring -->Manage Tivoli Monitoring Services.
2. Change the configuration of the monitoring server.
3. Configure agents and other monitoring components.


6. Given the customer monitoring requirements, log on to TEMS and reconfigure Warehouse Proxy Agent so that the agent is started to store historical data in the data warehouse.

With emphasis on performing the following steps:
1. Ensure connectivity to TEMS.
2. Select protocol (IP.PIPE, IP.UDP, or ...).
3. Verify hostname of TEMS and port number.
4. Select DB platform (DB2 Express, DB2 Enterprise Edition V8.2, MSSQL).
5. Specify DB admin user ID/password (e.g., db2admin).
6. Specify DB user ID/password (e.g., ITMUser).
7. Verify data source name to be ‘CandleNet Warehouse’.
8. Verify data base name.
9. Check ‘Synchronize TEPS warehouse information’.


7. Given the installed IBM Tivoli Universal Agent, edit the environment file for UA, add different data providers to the KUMA_STARTUP_DP environment variable, and start the UA in order to enable the specific data providers required for custom monitoring solutions.

With emphasis on performing the following steps:
1. Select Start -->Programs -->IBM Tivoli Monitoring -->Manage Tivoli Monitoring Services.
2. In the Manage Tivoli Enterprise Monitoring Services window, right-click the IBM Tivoli Universal Agent, then select Advanced --> Edit ENV file from the pop-up menu.
3. In KUMENV add the parameters listed below to the KUMA_STARTUP_DP= statement.
4. Multiple data providers can be added as entries separated by commas.
5. Use the parameter:

ASFS to start the consolidated data provider (APIS, SOCK, FILE, and SCRP).
APIS to start the API Server Data Provider
FILE to start the File Data Provider
HTTP to start the HTTP Data Provider
ODBC to start the ODBC Data Provider
POST to start the Post Data Provider
SCRP to start the Script Data Provider
SNMP to start the SNMP Data Provider
SOCK to start the Socket Data Provider
When done editing, save the file and restart the Universal Agent

Section 4: Troubleshooting

1. Given the status of Managed Systems OFFLINE, review logs or status on Tivoli Enterprise Monitoring Server (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 steps:
1. Validate if agent is started.
2. Recycle agent.
3. Validate configuration of agent to TEMS.
4. Review agent logs in [Installed drive and path]…\IBM\ITM\TMAITM6\logs.
5. Set the KDC_DEBUG trace to “all” 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 Manage Tivoli Enterprise Monitoring Services (MTEMS),.
8. Restart the agent.
9. Verify agent heartbeat configuration.


2. Given clients unable to log on to Tivoli Enterprise Portal Server (TEPS), determine root cause of logon problem by reviewing Tivoli Enterprise Portal (TEP) and TEPS configuration and logs so that connectivity is restored.

With emphasis on performing the following steps:
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 KDC_DEBUG trace to “all”.
5. Review logs for port connectivity and security issues
6. Review ITM V6 logs in [Installed drive and path]…\IBM\ITM \logs
7. Modify TEP configuration parameters where necessary


3. Given an authorized user is unable to log on to TEP, determine cause of the problem by analyzing messages in IBM Tivoli Monitoring Express v6 (ITM Expess) logs and validating user accounts so that the users can successfully log on to TEP.

With emphasis on performing the following steps:
1. Ensure users defined in TEPS.
2. Logon to TEPS with known user account.
3. Click ‘Administer Users’ icon from main menu bar.
4. Validate user account on the list.
5. If security is enabled, ensure user IDs (OS account) are valid in TEMS.
6. Have system administrator validate user account exist on the TEMS server.
7. Analyze messages to determine other possible causes in [Installed drive and path]…\IBM\ITM\TMAITM6\logs.


4. Given no historical data past 24 hours is displayed on TEP, verify that the warehouse DB exists, HDC is correctly configured and started, Warehouse Proxy Agent is running so that historical data is correctly displayed.

With emphasis on performing the following steps:
1. Log on to DB2 Control Center to determine if 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) located in [Installed drive and path]…\IBM\ITM\TMAITM6\logs.
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 configuration for that particular Attribute Group is correctly set and collection started.


5. Given that data is not being summarized and pruned according to the parameters set, ensure Summarization and Pruning (S & P) 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 steps:
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, ).


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

With emphasis on performing the following steps:
1. Use same situations across similar/same systems (do not duplicate).
2. Disable situations that are not used.
3. Optimize the order of conditions 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.


7. 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 steps:
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.

Section 5: Administration

1. Given the customer monitoring requirements, log on to Tivoli Enterprise Portal (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 steps:
View a list of situations running on this managed system, the same types of managed systems, or on the enterprise.
1. View the definition of a situation.
2. Create a new situation or edit a situation.
3. Delete a situation.
4. Start or stop a situation.
5. Distribute a situation to a managed system or managed system list.
6. Associate a situation with the current Navigator item.
7. Use embedded situations in your situation formula.
8. Create correlated situations across multiple types of managed situation.


2. Given the solution design and the configured agent, configure historical data collection for various agent types to collect data so that the historical data can be displayed in workspaces.

With emphasis on performing the following steps:
1. Click ‘History Configuration’ icon (ctrl+H).
2. Select product type (e.g., Windows OS, CCC Logs, …).
3. Select Attribute Group.
4. Select Collection Interval.
5. Select Collection Location.
6. Select Warehouse Interval.


3. Given the solution design and collected historical data, configure summarization and pruning of historical data so that summarized historical data is available.

With emphasis on performing the following steps:
1. Select summarizations desired.
2. Select pruning requirements desired.
3. Click ‘Configure Groups’.
4. Click ‘Start Collection’.
5. Configure Summarization and Pruning Agent.
6. Right-mouse click to bring up context menu.
7. Select protocol (IP.PIPE, IP.UDP, etc…).
8. Verify database information for warehouse and Tivoli Enterprise Portal Server (TEPS).
9. Enter DB user’s password (ITMUser).
10. ‘test database connection’ if desired.
11. Define appropriate summarization and pruning requirements, including schedule.
12. Click ‘Save’ and ‘Close’.
13. Start Summarization and Pruning Agent.
14. View historical data collection.
15. Log on to TEP.
16. Navigate to a historical workspace.
17. Validate report view.
18. Configure time span of historical report view.
19. Click ‘Time Span’ icon to open the dialog.
20. Define desired time span to view the historical data.


4. Given the IBM Tivoli Monitoring Express V6.1 (ITM Express) infrastructure components are installed, select queries, filters, and styles to create a customized workspace in order to visualize ITM Express monitoring data.

With emphasis on performing the following steps:
1. Logon to TEP.
2. Navigate to any managed systems.
3. Expand plus sign to see the detail Attribute Groups for a particular managed system.
4. Click an icon of desired view type (pie chart, bar graph, table, etc…).
5. Click the view area to place the view type.
6. Right-mouse click to select Properties.
7. Click to assign a query.
8. Expand the managed system type to see all Attribute Groups.
9. Expand within Attribute Group to select a query.
10. Click ‘Query Results Source’ tab.
11. Verify appropriate managed system is assigned.
12. Click ‘Filter’ tab to apply desired filters for this query.
13. Click ‘Style’ tab to define desired style of the view.


5. 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 steps:
1. Logon to TEP.
2. Open situation editor from a managed system in the Navigator view.
3. Expand the list of situations tree.
4. Select appropriate existing situation.
5. Verify or modify thresholds.
6. Set sampling interval.
7. Verify ‘Run at startup’ is checked.
8. Click on Distribution tab.
9. Verify managed systems are assigned.
10. Click ‘Expert Advice’ to review the content validity.
11. Modify or define ‘Expert Advice’.
12. Click Action tab.
13. Define appropriate action if desired.
14. Click OK.


6. 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 steps:
1. Log on to TEP.
2. Open situation editor from a navigator item.
3. Click ‘Create new situation’ icon.
4. Name the new situation.
5. Select the appropriate Attribute Group.
6. Select item from Attribute Group.
7. Specify the monitoring thresholds.
8. Click ‘Add attributes’ button if needed.
9. Set sampling interval.
10. Set the State.
11. Verify ‘Run at startup’ is checked.
12. Click on Distribution tab.
13. Verify managed systems are assigned.
14. Click ‘Expert Advice’ to review the content validity.
15. Modify or define ‘Expert Advice’.
16. Click Action tab.
17. Define appropriate action if desired.
18. Specify display item and/or event persistence in the advanced situation settings.
19. Click OK.


7. Given customer requirements, use the command line interfaces to start/stop/recycle the agents on either Windows or UNIX systems, so that the components are restarted.

With emphasis on performing the following steps:
1. Open command prompt on Windows system.
2. Run tacmd login –S
3. Run tacmd restartAgent to recycle the agent.
4. Run tacmd startAgent to start the agent.
5. Run tacmd stopAgent to stop the agent.
6. Open command prompt on UNIX system.
7. Run itmcmd agent to either start or stop the agent.


8. Given user requirements, use Manage Tivoli Enterprise Monitoring Services (MTEMS), to reconfigure/start/stop/recycle an infrastructure component so that components are started, stopped or reconfigured.

With emphasis on performing the following steps:
1. Launch MTEMS.
2. Right-mouse click, select stop/start or recycle.
3. Click ‘Actions’ from main menu and click stop/start or recycle.
4. Click the traffic light icon on the icon menu bar.
5. Right-mouse click to select appropriate options to administer advanced features for a particular infrastructure components.


9. Given the IBM Tivoli Monitoring V6.1 documentation, know the relationship between attributes and Attribute Groups so you have an understanding of attributes and Attribute Groups.

With emphasis on performing the following steps:
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.

Section 6 – Maintaining

1. Given the fix pack software and documentation, install the appropriate fix pack on appropriate systems so that the IBM Tivoli Monitoring Express fix pack has been applied properly.

With emphasis on performing the following steps:
1. Determine requirements for fix pack from fix pack documents.
2. Before attempting to install the fix pack on a production system, when at all possible first attempt on a non-critical system.
3. Request backup of system prior to installation of the fix pack.
4. Install fix pack on the appropriate system.
5. Test fix pack.