Sale!

Test C2010-510: IBM Tivoli Monitoring V6.3 Administration

$118.00 $68.00

Product Description

Test information:

Number of questions: 70
Time allowed in minutes: 105
Required passing score: 77%
Languages: English, Japanese

C4040.com provides the latest version of IBM C2010-510 questions and answers, which can make sure you pass the test easily. Besides, before you make a decision, you can practice IBM C2010-510 online test questions here.

Objectives:

Section 1:Configuration

Given installed IBM Tivoli Monitoring (ITM) V6.3 software, use root/administrator login ID to configure Tivoli Enterprise Monitoring Server (TEMS) with correct information so that TEMS is configured.
With emphasis on performing the following tasks:
Use root / administrator login ID.
Run ./itmcmd config -S -t tems_name where tems_name is name of monitoring server for UNIX / Linux or use MTEMS-> TEMS -> Reconfigure on Windows.
Check and correct information regarding TEMS.
Choose type of protocol to use for communication and backup.
Configure KDC_PARTITION, Auditing, and Hot Standby features.
Configure Security Authentication.
Configure forward situation event console.
Configure SOAP server.
Configure self-describing agent capability.
Given installed ITM software and IBM Tivoli Enterprise Portal Server V6.3 (TEPS) is operational, use root/administrator login ID to stop and configure TEPS settings so that TEPS is configured and operational.
With emphasis on performing the following tasks:
Use root / administrator login ID.
Stop TEPS.
Run ./itmcmd config -A cq or use MTEMS-> TEPS-> Configure on Windows.
Configure ITM Connector settings.
Configure the connection between the portal server and the hub monitoring server.
Configure the connection between the portal server and the portal server database.
Configure Tivoli Data Warehouse and connection settings between the portal server and warehouse database.
Start TEPS.
Configure settings to validate users with an LDAP database.
Configure settings to use single sign-on.
Given information on users and details of their workstations, potential crossing of firewalls and the need to access the ITM V6.3 environment through graphical interface clients (Tivoli Enterprise Portal or TEP) , implement steps so that TEP client is successfully configured.
With emphasis on performing the following tasks:
Determine the list of users.
Determine details of workstations: which TEP client to be deployed (full client, browser of Java Webstart).
Determine details of TEPS and TEMS (IP Addresses or Hostnames)
Determine any security software on the workstation (Security blocking software,).
Determine ports to open through any firewall if any needs to be crossed
Verify that the Java Runtime environment installs correctly on the workstation.
Configure the TEP client based on the user requirements.
Verify that user can successfully connect to the ITM V6.3 environment.
Given a requirement to retain historical data, configure the Warehouse Proxy agent so that desired enterprise data can be retained in the Tivoli Data Warehouse.
With emphasis on performing the following tasks:
Obtain connection information to Tivoli Data Warehouse.
Begin warehouse proxy agent configuration from;
the GUI (“MTEMS”)
command line (itmcmd config -A hd)
Input configuration values.
Save and close.
Verify successful connection of agent.
Given installed Tivoli Enterprise Monitoring Agent (TEMA) and an installed OS agent, use the Managed System window features or command line interface so that the configuration of TEMA is completed.
With emphasis on performing the following tasks:
Log in to TEPS with Agent Management permission.
Right-click the Navigator item for the agent to configure or upgrade.
Click Configure to open the Configure Managed System window.
Edit the fields to configure the agent, clicking Next and Back to move among the pages. Any pages besides Agent are specific to the agent type.
Warehouse Proxy: See the “Install and configure communications for the Warehouse Proxy agent” topics under “Setting up data warehousing” in the IBM Tivoli Monitoring Installation and Setup Guide.
Summarization and Pruning Agent: See “Configuring the Summarization and Pruning Agent (JDBC connection)” in the IBM Tivoli Monitoring Installation and Setup Guide.
Performance Analyzer Warehouse Agent: See the IBM Tivoli Monitoring Installation and Setup Guide.
Universal Agent: Specify the Metafile and Script files. These are described in the “New in this release”.
Non-base agents: See your product’s installation guide in the IBM Tivoli Monitoring information center.
On the Agent page, establish the user ID that will be used to maintain the agent:
Windows: Accept the default, Use local system account to use your TEP user ID. You can also select Allow service to interact with desktop to enable remote control. Or select Use this account and fill in the user name and password under which the agent will be controlled.
Non-Windows: Enter the Username under which the agent will run and the Group name.
Click Finish to complete the managed system configuration. If any of the information provided is invalid, you will receive an error message and be returned to the configuration window. Check your entries and edit as appropriate to configure correctly.
Given a company network plan and the ITM V6.3 documentation, determine the exact requirements for the firewall gateway, build the XML files, and configure the agents so that the firewall gateway is configured.
With emphasis on performing the following tasks:
Determine where agents will have to cross firewall to reach their remote Tivoli Enterprise Monitoring Server (RTEMS) or the RTEMS to reach the Hub Tivoli Enterprise Monitoring Server.
Check corporate network security policies if ports can be opened from the less to the more secure zone.
Check if firewall gateway is required to comply with security policies.
Determine which agents in each network zone will function as firewall gateway
Determine if the firewall gateway will be used for TEMS traffic only or also for warehouse traffic.
Build the XML definition files for all gateways.
Set the selected agents variables to point to these XML files.
Configure the agents to connect with their firewall gateway.
Given a HA plan, and requirements, implement the planned actions so that the HA environment is deployed
With emphasis on performing the following tasks:
Implement HUB Hot Standby or Cluster configuration.
Implement spare RTEMSs.
Implement WPA failover parameters so that agents can warehouse to a secondary WPA.
Configure Agents to be able to connect to 2 RTEMSs.
Configure spare TEPS with or without some kind of load balancer and/or cluster configuration.
Implement a plan to quickly replace a failing SPA.
Given an installed Summarization and Pruning Agent (SPA), select options and update required details so that the SPA is configured.
With emphasis on performing the following tasks:
./itmcmd config -A sy or use MTEMS-> SPA -> Reconfigure on GUI
Select TEMS to connect to (protocol and port included).
Select Database Type.
Select Data Sources (JDBC drivers) and enter DB admin credentials.
Test connection.
Enter scheduling details.
Set pruning details.
Select details like worker threads, database compression etc.
Save the configuration and restart the agent.

Section 2:Performance Tuning,Problem Determination and Troubleshooting

Given an IBM Tivoli Enterprise Portal (TEP) client connected to an IBM Tivoli Enterprise Portal Server (TEPS) V6.3, go to the Tivoli Data Warehouse agent configuration workspaces and identify errors that need to be corrected so that the IBM Tivoli Monitoring (ITM) Tivoli Data Warehouse agent environment is functioning properly.
With emphasis on performing the following tasks:
Connect to TEPS by using your preferred TEP client.
Navigate to a Warehouse Proxy agent (WPA) or Summarization and Pruning agent (SPA).
Click the configuration or statistics workspace to view agent data.
Select one of those options you want to check.
Identify configuration or run-time issues.
Review error code for each issue.
Resolve the errors identified.
Verify the configuration and statistics workspaces no longer report issues.
Given logs, identify the types of logs that are used in ITM so that basic troubleshooting information can be gathered.
With emphasis on performing the following tasks:
Identify RAS1 logs and its path for each component.
Identify operational logs and its path for each component.
Identify core files and drwatson dumps.
Identify installation logs.
Given an existing ITM V6.3 environment, a Tivoli Enterprise Monitoring Server (TEMS) exhibiting unexpected behavior, the ITM V6.3 Troubleshooting guide and access to internet search engines, execute required actions so that TEMS V6.3 issues are resolved.
With emphasis on performing the following tasks:
Access ITM V6.3 environment either on GUI or Command Line.Identify abnormal behavior of ITM V6.3. Check log files located under install_dir\logs\hostname_ms-HEXtimestamp-nn.log.
Analyze the log file content and extract clues related to errors/error codes.
Research for solution about identified errors/error codes (ITM Troubleshooting Guide, IBM search).
If recommended, Set trace option according to issue referenced by the Troubleshooting guide or search engines.
Collect trace files, analyze content of Trace files.
Execute relevant recommendations from the Troubleshooting Guide or from results of search engine.
Confirm that TEMS V6.3 issues are resolved and it behaves normally.
Given a TEPS, check processes, logs, and documentation so that analysis or troubleshooting can be completed.
With emphasis on performing the following tasks:
Ensure that all the TEPS processes are running.
Check the TEPS operational and RAS1 logs.
Check eWAS and IHS logs.
Check Documentation and FAQs for common scenarios:Performance impacts of the HTTP and HTTPS protocolsUsers who run the IBM HTTP Server do not have permission to the content directory.tacmdexportWorkspaces or importWorkspaces receives an out of memory errorFailed to log in as sysadmin with portal server LDAP enabled.On AIX systems, newly created users with auto-expire passwords cause installation failures.Linux portal server is unable to FTP catalog/attribute files.TEPS performance is slow.Cannot create a TEPS database.Receive a KFW error when a query is sent to more than 200 managed systems.Non-hub situations are not associated at the TEPS level.Start and stop the Eclipse Help Server.Root password is not accepted during non-root TEPS configuration.Stop or start the eWAS subcomponent of the TEPS.
Check on the IBM support site for the latest fixes or known issues.
Given ITM , the Agent User guide and the need for troubleshooting, set the trace option so that Tivoli Enterprise Monitoring Agent (TEMA) trace files are configured.
With emphasis on performing the following tasks:
Open the Manage Tivoli Enterprise Monitoring Services window.
Right-click the icon of the monitoring agent whose logging you want to modify.
Select Advanced -> Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed.
Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid string.The selections are as follows:
General error tracing. KBB_RAS1=ERROR
Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL)
Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)
Check hostname__program_timestamp-nn.log files located under install_dir\logs path.
Given the pdcollect and cinfo tool perform the start command and review the output so that the pdcollect output will be generated.
With emphasis on performing the following tasks:
When running pdcollect, ensure the following is in the output �Data collection is complete’.
Review the manifest.txt file to ensure the necessary files are there.
Ensure �exit’ is entered when finished.Verify the following commands are used to start pdcollect –
Windows: pdcollect.cmd pdcfilt.exe,
UNIX/Linux: pdcollect,
z/OS: pdcollect.clist
Run cinfo to collect application information, application support levels, running agents.
Review the output and take necessary action.
Given ITM and ITM knowledge, a running checked database, WPA and SPA configured and running, and historical data collection configured and a need for the warehouse to function as required, execute any remedy so that warehouse is troubleshot . (NOTE: Troubleshot is not so much used, but is correct too ).
With emphasis on performing the following tasks:
@Check if the Database is up and running. @Check if the WPA is up and running. @Check if the SPA is up and running. @Check if the historical collection is configured and running.
Set the trace levels according to the Warehouse Guide. @Use the portal client WPA workspaces and views to detect problems.
Given an existing ITM V6.3 environment, the ITM V6.3 Troubleshooting guide and access to internet search engines, execute required remedial actions so that components communication failures are resolved.
With emphasis on performing the following tasks:
Access ITM V6.3 environment either on GUI or Command Line.
Identify ITM V6.3 suspected components communication failures.
Check log files located under install_dir\logs\ for the suspected component.
Analyze the log file content and extract clues related to errors/error codes.
Research for solution about identified errors/error codes (ITM Troubleshooting Guide, IBM search).
If recommended, Set trace option according to issue referenced by the Troubleshooting guide or search engines for the concerned components.
Collect trace files, analyze content of Trace files for the concerned components.
Execute relevant recommendations from the Troubleshooting Guide or from results of search engine.
Confirm that ITM V6.3 components communication issues are resolved.
Given ITM documentation and customer support guidelines, set the components KBB_RAS1 variable either statically or dynamically so that the component is being traced correctly for debugging.
With emphasis on performing the following tasks:
Set the KBB_RAS1 variable by using either the Manage Tivoli Enterprise Monitoring Services console or by modifying the component’s environment or .ini file and recycling the component.
Alternatively, use the components service console via http://TEPSserverHostname:1920 to start tracing dynamically.

Section 3:Administration

Given an IBM Tivoli Enterprise Portal (TEP) client connected to an IBM Tivoli Enterprise Portal Server (TEPS) V6.3, take the required actions so that the custom users can be configured.
With emphasis on performing the following tasks:
Login to TEPS with Agent Management permission
Click on Administer Users opens the Administer Users window.
Create or delete a user.
Adjust the following parameters to meet the user requirements:
Permissions setting will give the user account authorization.
Applications setting will allow the user to see some or all the application types being monitored.
Navigator Views setting will allow user access to the Navigator.
Member Of and Members setting will assign users to a group.
Given a TEP client connected to a TEPS V6.3, create, modify and remove custom workspace so that Workspace is modified according to the requirements.
With emphasis on performing the following tasks:
Connect to TEPS by using your preferential TEP client with Workspace Author Mode permission ID.
Select Workspace Gallery to choose other Workspace already defined.
Open an undefined workspace.
Use Split tool to modify workspace.
Configure the view types and test the result.
Use Save Workspace as to create a new Workspace.
If it is necessary modify the properties, including its name, go to your new workspace created and edit properties.
Use File -> Delete Workspace to delete the Workspace.
Given the installation predefined situations, copy and change the predefined situations so that new, customized situations are created.
With emphasis on performing the following tasks:
Copy the predefined situations to change. (The predefined situations provided with this monitoring agent are not read-only. Do not edit these situations and save over them. Software updates will write over any of the changes that you make to these situations.).
Use the Situation Editor, display the predefined situations or create situations.
Alter the following tabs to create a new situation:
Formula – Condition being tested
Distribution – List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed
Expert Advice – Comments and instructions to be read in the event workspace
Action – Command to be sent to the system
– Until – Duration of the situation
Event Integration Facility – Whether to send a Tivoli Enterprise Console event and event severity
When creating situations, choose from these types of predefined situations:
Automatically installed and activated at startup
Not automatically installed but activated at startup
Automatically installed and not activated at startup
Bottleneck analysis, not activated at startup
Given a running IBM Tivoli Monitoring (ITM) V6.3 environment, the ITM V6.3 Administration guide and requirements for a situation to depend on other situations, use TEP to execute the required steps so that a correlated situation is created.
With emphasis on performing the following tasks:
Click New Situation to open the Create Situation window.@Type a name for the situation in the Name field and, optionally, a description in the Description field.@Select the Correlated Situation from the Type list and click OK.@In the Correlated Situation Selection window, select a situation from the Available Situations list, select the managed system (or managed systems) to correlate from the Available Managed Systems list, then click OK to add the situation to the editor.@Click in a cell below each new column to add == True and complete the expression.@A correlated situation is not complete until it has at least two conditions. If you have more situations to add, click Add Conditions, select the next situation and managed system (or managed systems), click OK, and select inside a cell of each column added.@Adjust any other settings in the Formula tab to complete the formula:#To add event persistence, click Advanced.#To change the sampling interval, click inside the dd (day), hh (hour), mm (minute) or ss (second) field and click the up and down arrows.#To start the situation manually rather than automatically, clear .@When you are finished composing or editing the situation, save your changes and start the situation by clicking Apply to keep the editor open; or by clicking OK to close the Situation editor.
Given an existing ITM V6.3 environment, the ITM V6.3 Administration guide and local requirements to automate activities through workflows, execute required steps so that customized policies can be managed.
With emphasis on performing the following tasks:
Connect to TEPS by using the preferred TEP client with Workspace Author Mode permission ID, View Policy permission ID or Both.
Select Workflow Editor -> New Policy (or copy an existing policy).
Update required details for the policy (like name, description etc..).
The Select a Situation window opens for you to select a situation that, when true or in error, triggers the next activity in the workflow.
Add other activities to the policy as needed.
Draw connecting lines to direct the workflow.
After finish workflow, Validate, Distribute, and Apply policy.
Select Edit Workflow to open and Edit policy as needed.
In case of copy and delete policy use Workflow Editor and select Copy or Delete Policy as needed.
Given a TEP client connected to a TEPS V6.3, take required actions so that links between workspaces are created or modified according to requirements.
With emphasis on performing the following tasks:
Connect to TEP by using an ID with Workspace Author Mode permissions.
Open the source workspace.
Right-click one of the possible link source locations: The highlighted Navigator item for this workspace, An icon in a graphic view, An object in a Tivoli Management Services Infrastructure view, A row in a table view or situation event console view, A data point in a chart view.
Select Link to -> Link Wizard.
To create a new one, Select “Create a new link” and type the name and description.
Select: Dynamic; Absolute; Relative link options.
Select the navigation view of your target link.
Configure setting of selected links options.
Select finish to save the link.
To modify link properties or delete a link, follow the previous steps and select Modify an existing link or Delete one or more existing links.
Given agents and the attribute groups and an appropriate user ID, use the default queries with variables to run a query on Tivoli Enterprise Monitoring Server (TEMS) or a database so that a custom query is created.
With emphasis on performing the following tasks:
Click Queries.
In the title bar of the table or chart view where you would like to apply a new query, click Properties editor -> viewProperties -> Query Click here to assign a query.
Review default queries and variables.
Select the attribute group from the Group list, then the attributes to include from the Item list, and click OK.
Add the same symbol expressions to the specification as those used in the predefined query for this attribute group.
Edit the specification for any changes to meet your requirements.
Query TEMS tables or database.
Assign query to workspace.
Given the agent depot and bundles, populate the depot and deploy the agents so that the agents are deployed from the depot.
With emphasis on performing the following tasks:
Populate the agent depot with installable agent images.
Determine type of agent deployment -using the tacmd createNode from TEMS for OS agents or use the tacmd addSystem from TEMS or TEP Deploy for non-OS agents.
View and change the contents of the agent depot.
Use one agent depot for all the monitoring servers in your monitoring environment.
Deploy an OS agent.
Deploy a non-OS agent.
Deploy a group of agents simultaneously.
Verify that agents are successfully deployed.
Given a TEP client connected to a TEPS V6.3, configure the history data collection windows so that custom history is configured.
With emphasis on performing the following tasks:
Connect to TEPS.
Click on the History Configuration icon.
Configure the History data collection configuration windows according to needs.
Configure the SPA to summarize and prune the historical data to control database growth.
Given an existing ITM V6.3 environment, the ITM V6.3 Administration guide and customer requirements to re-organize TEP views, edit workspaces so that Navigator views are customized.
With emphasis on performing the following tasks:
Log in through TEP, access target Navigator items, Edit the Navigator workspace and save with different name as predefined workspaces cannot be modified or deleted.
Use the tools in the Navigator view toolbar to update the display when managed systems have come online or gone offline, to open another Navigator view, to edit custom Navigator views, and to collapse the view.
Use the Edit Navigator view to open the Navigator editor for creating, deleting, and modifying Navigator views. If the tool is disabled (dimmed), your user ID does not have Modify permission for Custom Navigator Views.
Use the down arrow icon to open a list that you can select a Navigator view from. The views available are those assigned to your user ID. When you select another Navigator view, a tab is added to the bottom of the Navigator so that you can quickly switch among the views by clicking the tab.
Use the Find in the Navigator toolbar to look for a Navigator item by such criteria as managed system name or associated situation name. When the search has completed, any items that match the criteria are listed in the Find results table where you can switch to the default workspace for a found item or open it in a new window.
Use the Apply pending updates tool to update the Navigator tree with the correct status of agents, in response to the count of agents that have been removed from or added to the TEMS. The counter is displayed next to the tool and in the status bar. Refresh is enabled when the Navigator view has been edited, such as a new item has been added, so that you can update the view with the changes. This tool is dimmed when no updates are required.
Use the horizontal and vertical Split icon to split the Navigator horizontally or vertically to create a new workspace view.
Save the new Workspace.
Given a requirement to retain historical data for reporting, configure historical data collection and warehouse tables so that out-of-the-box Tivoli Common Reporting reports can be run successfully.
With emphasis on performing the following tasks:
Set historical collection to populate required data tables in Tivoli Data Warehouse.
Create the Time Dimension table and the Resource Dimension table.
Verify reports are populating with correct data.
Given access to TEMS and the host and port of the event management system, take the required steps so that integration of managed events and event management systems is completed.
With emphasis on performing the following tasks:
Determine Event integration management system is either Tivoli Enterprise Console or Netcool/OMNibus.
Open Manage Tivoli Enterprise Monitoring services.
Right-click the monitoring server and click Reconfigure.
On the configuration options window, select Tivoli® Event Integration Facility.
Click Save and OK.
Complete the following fields on the Event Server: Location and Port Number window and click OK:
Type the host name or IP address for the computer where the EIF probe is installed.
Type the port number on which the probe is listening.
Verify the integration
Given a TEP client connected to a TEPS V6.3, create, update and modify the routine so that a take action executes successfully.
With emphasis on performing the following tasks:
Connect to TEPS by using your preferential TEP client with modify permission for the Action feature.
Define the Navigator item associated with the application on which you want to run the command.
Modify the view if recommended.
Select “Take Action” button, and select CREATE or EDIT.
Define the routine to take.
Save the changes.
Verify the take action executes successfully.
Given a terminal window or command window, use the tacmd, cinfo, itmcmd and pdcollect command line to run administration tasks on the TEMS so that CLI commands are issued.
With emphasis on performing the following tasks:
Execute commands to log in to the TEMS, use help, and log out.
Execute commands to work with bundles and the depot.
Execute commands to deploy remotely.
Execute commands to manage situations.
Execute commands to manage take action commands
Execute commands to manage calendar functions.
Execute commands to manage event destinations.
Execute commands to stop and start components.
Execute commands to check the application support versions.
Given the need to use ITM V6.3 solution with the IBM Tivoli Performance Analyzer (ITPA), and the ITM V6.3 Administration guide, explain main operational features so that the ITPA is described.
With emphasis on performing the following tasks:
Obtain and read the ITPA User’s Guide.
Obtain and read the IBM Tivoli Monitoring V6.3 Administration Guide
Determine ITPA functionality and if it meets customer requirements.
Determine how ITPA is linked to ITM V6.3
Determine how ITPA can benefit an organization with emphasis on trend analysis, predictive analysis, reporting, etc
Determine who ITPA can target and why.

 

Reviews

There are no reviews yet.

Be the first to review “Test C2010-510: IBM Tivoli Monitoring V6.3 Administration”