EDURV215111SE

Computer Associates
Unicenter NSM
Implementation and Administration Student Workbook URV215
EDURV215111SE
PROPRIETARY AND CONFIDENTIAL INFORMATION These educational materials (hereinafter referred to as the "Materials") are for the end user's educational purposes only and are subject to change or withdrawal by CA at any time. These Materials may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. These Materials are confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THESE MATERIALS "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THESE MATERIALS, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any software or product referenced in the Materials is governed by the end user's applicable license agreement. The manufacturer of these Materials is CA. Provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2006 CA. All rights reserved.
Call CA technical services for any information not covered in this manual or the related publications. In North America, see your CA Product Support Directory for the appropriate telephone number to call for direct support, or you may call 1-800-645-3042 or 631-342-4683 and your call will be returned as soon as possible. Outside North America, contact your local CA technical support center for assistance.
Table of Contents
Introduction
Welcome . . . . . . . . . . . . . . . . . . . . . . . . Target Audience . . . . . . . . . . . . . . . . . . . Learning Path . . . . . . . . . . . . . . . . . . . . . About This Workbook. . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . About This Course . . . . . . . . . . . . . . . . . . Course Length . . . . . . . . . . . . . . . . . . Prerequisite Skills . . . . . . . . . . . . . . . Course Agenda . . . . . . . . . . . . . . . . . Day 1 . . . . . . . . . . . . . . . . . . . . . . . . Day 2 . . . . . . . . . . . . . . . . . . . . . . . . Day 3 . . . . . . . . . . . . . . . . . . . . . . . . Day 4 . . . . . . . . . . . . . . . . . . . . . . . . Day 5 . . . . . . . . . . . . . . . . . . . . . . . . Case Study: Really Big Corporation . . . . . . Service Availability Branding. . . . . . . . . . . Service Availability Strategy . . . . . . . . . . . Classroom Computer Hostnames . . . . . . . Course Objectives . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. x .. x .. x . . xi . xii . xiii . xiii . xiii . xiii . xiii . xiv . xiv . xv . xvi xvii xviii . xx xxiii xxiv
1 Plan a Unicenter NSM Implementation

Analyze the Corporate Environment . . . . . . . . . . . . . . . . . . 1-4 Evaluate Platform and OS Requirements . . . . . . . . . . . . . . . 1-7 Define Unicenter NSM Component Configurations . . . . . . . . 1-8 Define a Fault Tolerant Deployment . . . . . . . . . . . . . . . . . 1-10 Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12
2 Install Unicenter Components

Establish the Required DNS Service Location Record . . . . . 2-3 Install Unicenter NSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
iii
Configure Systems Monitoring
Describe Unicenter NSM Architecture . . . . . . . . . . . . . . . . . 2-26 Explain WorldView . . . . . . . . . . . . . . . . . . . . . . Explain the DSM Manager . . . . . . . . . . . . . . . . . Describe the Role of Agents in Systems Monitoring Describe Enterprise Management . . . . . . . . . . . . . . Describe Unicenter NSM Catalog Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27 2-29 2-30 2-31 2-34
Install the Linux System Agent . . . . . . . . . . . . . . . . . . . . . . 2-36 Verify Active DIA Connections . . . . . . . . . . . . . . . . . . . . . . 2-44 Verify MCC Provider Connections . . . . . . . . . . . . . . . . . . . . 2-46 Identify Management Components in the Catalog Structure Identify Commands to Maintain Catalogs . . . . . . . . . . . . . Access Managed Objects and Properties . . . . . . . . . . . . . . Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 2-49 2-51 2-55
3 Configure Systems Monitoring

Configure OS Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Configure Agents with Agent View, Adaptive Dashboards, or the MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Tune Threshold Values with the Agent Browser . . . . . . . . . . . . . 3-5 Define Windows System Agent . . . . . . . . . . . . . . . . . . . . . . 3-6 Define Watchers and Metrics . . . . . . . . . . . . . . . . . . . . . . 3-12 Define Trap Destinations . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Tune Threshold Values with ADS . . . . . . . . . . . . . . . . . . . . . . 3-22 Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22 Manage Systems with the UCM . . . . . . . . . . . . . . . . . . . . . . . 3-29 Create Base Profiles and Differential Profiles . . . . . . . . . . . 3-29 Distribute Base Profiles and Differential Profiles . . . . . . . . . 3-30 Modify Adaptive Configuration Parameters . . . . . . . . . . . . . . . 3-34 Identify Objects to Monitor . . . . . . . . . . . . . . . . . . . . . . . . 3-36 Run the Adaptive Configuration Service . . . . . . . . . . . . . . . 3-37 Tune Threshold Values of the Linux System Agent to Send Alerts 3-42
iv
Implementation and Administration Student Workbook
Discover System and Network Devices
Optimize the DSM Manager for Systems Monitoring . . . . . 3-51 Describe the DSM Discovery Process . . . . . . Describe DSM Configuration . . . . . . . . . . . . Define the DSM Configuration Tool . . . . . . . . Manage and Configure a DSM Environment The Role of DSM Configuration . . . . . . . . DSM Agent Class Scoping . . . . . . . . . . . . DSM Agent Class Scoping Pane . . . . . . . . DSM Discovery Community Strings . . . . . DSM Polling . . . . . . . . . . . . . . . . . . . . . . DSM Discovery Pollset Values . . . . . . . . . Improving Pollset Efficiency . . . . . . . . . . IP Address Scoping . . . . . . . . . . . . . . . . Setdsmname . . . . . . . . . . . . . . . . . . . . . Identify DSM Commands . . . . . . . . . . . . . . . Monitor the Status of DSM Managed Objects . Launch Node View . . . . . . . . . . . . . . . . . Use the Mini-Tree . . . . . . . . . . . . . . . . . Interpret Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-54 .3-55 .3-55 .3-55 .3-56 .3-56 .3-57 .3-57 .3-58 .3-58 .3-59 .3-59 .3-60 .3-63 .3-64 .3-64 .3-65 .3-65
Apply URM to Custom Unicenter NSM Environments . . . . . 3-67 Define URM Architecture . . . . . . Define URM Components . . . . . . AI . . . . . . . . . . . . . . . . . . . saCORe . . . . . . . . . . . . . . . Define Resource Monitoring . . . . Identify Hardware Requirements Identify Software Requirements . Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-67 .3-68 .3-69 .3-69 .3-70 .3-71 .3-71 .3-78
4 Discover System and Network Devices

Perform Classic Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Describe Advanced Discovery . . . Scope . . . . . . . . . . . . . . . . . . Subnets . . . . . . . . . . . . . . . . SNMP . . . . . . . . . . . . . . . . . . Mode . . . . . . . . . . . . . . . . . . DHCP . . . . . . . . . . . . . . . . . . SAN . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . Timeouts . . . . . . . . . . . . . . . Discovery Monitor . . . . . . . . . Perform Command Line Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 . 4-3 . 4-4 . 4-4 . 4-5 . 4-5 . 4-5 . 4-5 . 4-9 . 4-9 .4-10
Configure Continuous Discovery . . . . . . . . . . . . . . . . . . . . 4-15 Reclassify Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Describe the Relationship Between the MDB and Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20 When a Device Is Not Classified . . . . . . . . . . . . . . . . . . . . .4-21 Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24 v
Optimize Network Visualization
5 Optimize Network Visualization

Navigate the MCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Create Business Process Views . . . . . . . . . . . . . . . . . . . . . . . 5-5 Prioritize Managed Objects by Severity with Billboards . . . 5-10 Prioritize Business Impact of Alerts with BPVM . . . . . . . . . 5-12 Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
6 Automate Response to Events and Alerts

Describe Event Management Architecture . . . . . . . . . . . . . . 6-3 Event Management Daemon (caoprdmn) . . . . . . . . Event Management NT EventLog Reader (caoprlog) Event Management Messages . . . . . . . . . . . . . . . . Administrative GUI (Access Event Console Logs) . . Event Management Database . . . . . . . . . . . . . . . . Decision Support Binary (DSB) . . . . . . . . . . . . . . . Identify Enterprise Management Services . . . . . . . . . . UNIFSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNICNTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define the CAICCI . . . . . . . . . . . . . . . . . . . . . . . . . . CAICCI Communication Ports . . . . . . . . . . . . . . . . Cross-Platform CAICCI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 . 6-5 . 6-6 . 6-8 . 6-9 6-10 6-11 6-11 6-14 6-17 6-18 6-19
Filter Events with Event Console Logs . . . . . . . . . . . . . . . . 6-21 MCC Event Console . . . . . Log Messages Area . . . Console Message Detail Held Messages Area . . Classic Event Console . . . Console Settings . . . . . Buttons . . . . . . . . . . . Filters . . . . . . . . . . . . Timers . . . . . . . . . . . . Miscellaneous Items . . Columns . . . . . . . . . . Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21 6-22 6-22 6-23 6-24 6-24 6-24 6-24 6-25 6-25 6-25 6-25
Respond to Events by Creating Message Records and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31 Optimize Message Records with Wildcards . . . . . . . . . . . . . . . 6-35 Process Significant Events with the AMS . . . . . . . . . . . . . . 6-38
vi
Optimize the MDB
Communicate Event Status with the UNS . . . . . . . . . . . . . 6-47 Describe the UNS Process . . . . . . . . . . . . . . . Describe the Recipient and Provider Registry Consider Email Protocol Issues . . . . . . . . . Perform Troubleshooting . . . . . . . . . . . . . . Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-48 .6-49 .6-51 .6-52 .6-58
7 Optimize the MDB

Define a Single or Multiple MDB Implementation . . . . . . . . 7-3 Single MDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Multiple MDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Identify Ingres Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 Identify Ingres Visual Manager . . . . . . . . . . . . System Summary Icon . . . . . . . . . . . . . . . Identify Visual DBA . . . . . . . . . . . . . . . . . . . . Navigational Tree Structure in Visual DBA . . Database Administration Tools in Visual DBA Visual DBA Workspace . . . . . . . . . . . . . . . Identify Ingres Services and Commands . . . . . Ingres Net Connection Settings . . . . . . . . . Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 . 7-8 .7-10 .7-11 .7-11 .7-12 .7-12 .7-12 .7-13
Secure MDB Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 MDB Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16 MDB Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17 Tune the Ingres Database to MDB Requirements . . . . . . . 7-24 Identify Query Optimizer . . Identify Database Statistics Generate Statistics . . . . Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24 .7-24 .7-25 .7-27
8 Optimize Network Visualization with the UMP

Install the UMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Identify UMP System Requirements . . . . . . . . . . . . . . . . . . . . 8-3 Create Scoreboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
vii
Administer Unicenter Systems Performance
Provide Role-based Access to the UMP . . . . . . . . . . . . . . . . 8-14 Create a Workgroup . . . . . . . . . . . . . . . . . . . . . . Use Subgroups to Create a Workgroup Hierarchy Create a User . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicate a User . . . . . . . . . . . . . . . . . . . . . . . Create a Portal Administrator . . . . . . . . . . . . . . Add Multiple Portal Users . . . . . . . . . . . . . . . . . Import User Information from an LDAP Server . . Import User Information from a CSV File . . . . . . Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14 8-15 8-16 8-18 8-18 8-18 8-19 8-19 8-24
9 Administer Unicenter Systems Performance

Identify Unicenter Systems Performance Architecture Performance Data Grid . . . . . . . . . . . . . . . . . . Performance Domain Server . . . . . . . . . . . . . . . Performance Distribution Server . . . . . . . . . . . . Performance Agent . . . . . . . . . . . . . . . . . . . . . Define Unicenter Systems Performance Applications Performance Scope . . . . . . . . . . . . . . . . . . . . . Performance Trend . . . . . . . . . . . . . . . . . . . . . Performance Reporting . . . . . . . . . . . . . . . . . . Performance Configuration . . . . . . . . . . . . . . . . Data Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 . 9-6 . 9-7 . 9-8 . 9-9 9-10 9-10 9-12 9-13 9-14
Install Unicenter Systems Performance Components . . . . . 9-16 Install Systems Performance Manager . . . . . . . . . . . . . . . . . . 9-16 Install Systems Performance Agent . . . . . . . . . . . . . . . . . . . . 9-19 Configure Unicenter Systems Performance . . . . . . . . . . . . 9-22
Create a New Performance Profile . . . . . . . . . . . . . . . . . . . . . 9-23 Create a Unicenter Systems Performance Report . . . . . . . . 9-27 View Real-time Data with Performance Scope . . . . . . . . . . 9-35 Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
A Assessment Answers
Assessment Answers Module 1 . . . . . . Module 2 . . . . . . Module 3 . . . . . . Module 4 . . . . . . Module 5 . . . . . . Module 6 . . . . . . Module 7 . . . . . . Module 8 . . . . . . Module 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 . A-2 . A-2 . A-3 . A-3 . A-4 . A-4 . A-4 . A-5 . A-5
viii
Introduction
ix
Introduction
Welcome
Slide 1
Target Audience
Welcome to Unicenter NSM: Implementation and Administration training by CA. This course was specifically designed for Systems Administrators and Application Developers. In your jobs, you are responsible for maintaining the integrity of your enterprise. As your employer continues to increase the size and complexity of the business, your Enterprise Management responsibilities are growing exponentially.
Slide 2
Learning Path
This course provides instruction on how to administer Unicenter Network and Systems Management (NSM) through effectively managing discovered resources, monitoring captured events, and controlling the network environment. To learn about additional training solutions designed for your job role or this software product, visit gems.ca.com/Gemsmarketing/CourseFinder.asp Here you will find links to the Course Catalog, Learning Paths, Registration, and Locations/Schedules. Learning Paths will help you determine the best training combination to enhance job performance, learn advanced skills, or become certified.
Notes
Introduction
About This Workbook

Each task in this course is presented using the following instructional events, which follow a specific sequence: Instructional Event Demonstration Description Due to the limitations of a classroom setting, you will not always be able to perform specific tasks. Instead, you will observe the instructor perform these tasks step-by-step so that you can gain a better understanding of how to handle situations pertinent to your needs.
Interactive Demonstration
You will follow along on your student computer as your instructor demonstrates each step in a task. Your instructor will use this opportunity to explain the concepts, the conditions that drive which options should be selected, and other supporting information essential for you to understand the purpose of the task.
Skill Practice
You will practice the task just demonstrated while your instructor provides coaching.
Notes
xi
Introduction
Conventions
The following conventions are used throughout your Student Workbook: Convention Use Bold Italics GUI elements New terms Example Click OK to continue. ...the Name text box. A dialog is a window that appears to collect information from the user. Enter a range from 0 to n, where n equals the number of tapes. Do not erase the backup tapes. See the Unicenter TNG: Getting Started Guide. Refer to the Special Training Manual by IBM. See Administration for more information. At the prompt, type: C:\Program Files\myfolder At the prompt, type: C:\Program Files\folderName To reboot, press CTRL+ALT+DEL.
Variable values Emphasis Titles of books
Quotation Marks Computer Text Computer Text Italics SMALL CAPS
Reference to module titles and headings Commands to be typed (exactly as written) Variables to be replaced by the user with real values Names of keys
Notes
xii
Introduction
Slide 3
About This Course

This course is performance-based training. It was designed to teach only the tasks you will likely perform in 90 to 120 days of completion.
Course Length
5 days
Prerequisite Skills

Slide 4
Working knowledge of Microsoft Windows 2003, Microsoft Windows XP, Microsoft Windows 2000, or Microsoft Windows NT operating systems Knowledge of TCP/IP internetworking theory Solid understanding of IT terminology
Course Agenda Day 1

Module 1: Plan a Unicenter NSM Implementation
Task 1: Analyze the Corporate Environment Task 2: Evaluate Platform and OS Requirements Task 3: Define Unicenter NSM Component Configurations Task 4: Define a Fault Tolerant Deployment
Notes
xiii
Introduction
Module 2: Install Unicenter Components

Task 1: Establish the Required DNS Service Location Record Task 2: Install Unicenter NSM Task 3: Describe Unicenter NSM Architecture Task 4: Install the Linux System Agent Task 5: Verify Active DIA Connections Task 6: Verify MCC Provider Connections
Day 2
Module 3: Configure Systems Monitoring
Task 1: Configure OS Agents Task 2: Optimize the DSM Manager for Systems Monitoring Task 3: Apply URM to Custom Unicenter NSM Environments
Day 3
Module 4: Discover System and Network Devices
Task 1: Perform Classic Discovery Task 2: Configure Continuous Discovery Task 3: Reclassify Objects
Notes
xiv
Introduction
Module 5: Optimize Network Visualization

Task 1: Navigate the MCC Task 2: Create Business Process Views Task 3: Prioritize Managed Objects by Severity with Billboards Task 4: Prioritize Business Impact of Alerts with BPVM
Slide 5
Day 4
Module 6: Automate Response to Events and Alerts
Task 1: Describe Event Management Architecture Task 2: Filter Events with Event Console Logs Task 3: Respond to Events by Creating Message Records and Actions Task 4: Process Significant Events with the AMS Task 5: Communicate Event Status with the UNS
Module 7: Optimize the MDB

Task 1: Define a Single or Multiple MDB Implementation Task 2: Identify Ingres Utilities Task 3: Secure MDB Access Task 4: Tune the Ingres Database to MDB Requirements
Notes
xv
Introduction
Day 5
Module 8: Optimize Network Visualization with the UMP
Task 1: Install the UMP Task 2: Create Scoreboards Task 3: Provide Role-based Access to the UMP
Module 9: Administer Unicenter Systems Performance

Task 1: Identify Unicenter Systems Performance Architecture Task 2: Install Unicenter Systems Performance Components Task 3: Configure Unicenter Systems Performance Task 4: Create a Unicenter Systems Performance Report Task 5: View Real-time Data with Performance Scope
To gain job competency using Unicenter NSM, you will practice these tasks in a business context, and have opportunities to solve problems on your own.
Notes
xvi
Introduction
Slide 6
Case Study: Really Big Corporation

To simulate real-world business conditions, the fictional Really Big Corporation (RBC) will be used. You will be asked to play the role of a key stakeholder in RBC, to facilitate the learning process. The growth of RBC is due to a number of mergers and acquisitions. Today, the conglomerate has business holdings in many diverse markets. Legacy systems and data present numerous challenges to RBC. With offices and subsidiaries scattered worldwide, RBC is continually looking for ways to streamline operations.
Notes
xvii
Introduction
Slide 7
Service Availability Branding

Todays business processes are revenue generators that are highly dependent on the performance and availability of IT services. Degradation and downtime can be costly in many waysincluding lost sales and end user frustration. With so much at stake, IT is under pressure to deliver mission critical IT services in the most cost effective and efficient way possible. CA provides a complete, integrated, and open solution for service availability to help ensure that business processes run efficiently. Also, since the network and systems infrastructure is a critical element in delivering reliable business services, Unicenter NSM helps ensure reliability and efficiency of the systems infrastructure. At the same time, it can be used as a common visualization console for all IT activity. IT is struggling with many issues and wants to be able to:
Implement a solution that reduces the risk of performance degradations and outages and provides the ability to quickly pinpoint, diagnose, and repair problems to restore service quickly. Make the shift from reactive to proactive management to address problems before they impact business. Prioritize problem resolution based on business impact. Deliver superior support to all customers with whom Service Level Agreement (SLA) penalties have been defined. Mitigate any security risks inherent in the IT infrastructure by optimization and control of operations.
Notes
xviii
Introduction
Slide 8
There are four major steps to achieving Service Availability, as outlined in the following table. Management Discipline Step 1: Centralized Event Management Step 2: Mapping IT to Business Processes Solution
Integrated view of infrastructure health Tight integration with CA and third-party event
management solutions they support
IT assets are mapped to the business process Integrated view of events and their
relationships
IT can assess business impact of events
Step 3: Proactive Business Impact Management Step 4: Dynamically Optimized IT Business Agility
Integrated view of events and their
relationships
IT can assess business impact of events Problems are dealt with before they impact the
business and customers
Notes
xix
Introduction
Slide 9
Service Availability Strategy

Unicenter NSM is a family of integrated infrastructure management solutions that provide the following features:

Management delivery for the extended enterprise New modular design Stand-alone deployment and seamless integration End-to-end management that can incorporate solutions for networks, systems, databases, and so on
Integration makes it possible to effectively manage your infrastructure to quickly adapt to the dynamic business challenges facing a company today. Integration can help:

Reduce and manage operational costs. Reduce time to detect problems. Accelerate problem resolution. Reduce service level violations. Increase infrastructure security. Protect existing investments. Make new investments at your own pace. Reduce labor costs and need for experts. Reduce time spent reacting to problems. Reduce cost of maintaining multiple products and tools. Increase understanding of infrastructure and how it supports business processes. Increase use of current technology investments. Surpass business expectations by managing to service levels.
Notes
xx
Introduction
The CA Service Availability Solution provides a comprehensive, integrated, modular solution, as outlined in the following table: Solution Manage Costs Benefits An automated approach maximizes the availability and performance of business-critical services. When a critical business process experiences downtime, service is restored as quickly as possible. The productivity of IT staff is increased and instead of manually gathering, filtering, classifying, and determining the root cause of a problem and forwarding events to the right support staff, they can spend more time supporting new, revenue-generating initiatives. Trouble tickets are correctly assigned more often, problems are found more quickly, and MeanTime-To-Repair (MTTR) is reduced. Downtime is minimized as are all associated costs such as IT productivity, non-performance penalties, and lost business opportunities. IT can proactively respond to a business problem before users are impacted.
Improve Service
Notes
xxi
Introduction
Solution Manage Risk
Benefits Customers and business are protected against attacks and unauthorized access. IT staff is freed from manually responding to audit requests and legal inquiries that can sometimes monopolize time. All incoming events are stored to support current and future compliance requirements. IT services are aligned with business goals by defining enterprise-wide policies and then consistently prioritizing resources, problem resolution, and new product and service development in accordance with those policies. The impact that an incident has on the business is identified and quantified so that remediation can be prioritized and disruption to the business is minimized.
Align IT Investments with Business Needs
Notes
xxii
Introduction
Slide 10
Classroom Computer Hostnames

All CA classroom computer hostnames are named based on the following standard: USxxyyzz US Represents the classroom in a CA office in the United States xx A two-character city designator yy A two-character classroom number designator zz A two-character unique number assigned to each computer in the classroom beginning with 01. There are also two instructor computers: T1 and T2. Some classes use VMware virtual machines running on the student computer. The hostname for these virtual machines is the same as the parent host with the addition of the character V and a single digit that indicates the virtual machine, that is, USxxyyzzV1. The classroom Windows Active Directory domain names are based on the following standard: USxxDOMyy US Represents the classroom in CA office in the United States xx A two-character city designator DOM Indicates this is a domain name yy A two-character classroom number designator The fully qualified domain name of a classroom computer incorporates both of the previous matrixes. For example, the standard USxxyyzz.USxxDOMyy.com would create the following name: usdc0101.USDCDOM01.com
Notes
xxiii
Introduction
Slide 11
Course Objectives
After this course, you will be able to:

Plan a Unicenter NSM Implementation Install Unicenter Components Configure Systems Monitoring Discover System and Network Devices Optimize Network Visualization Automate Response to Events and Alerts Optimize the MDB Optimize Network Visualization with the UMP Administer Unicenter Systems Performance
Slide 12
Notes
xxiv
1
Plan a Unicenter NSM Implementation
1-1

Module Objectives
Slide 1-1
Module Objectives
After this module, you will be able to:

Analyze the Corporate Environment Evaluate Platform and OS Requirements Define Unicenter NSM Component Configurations Define a Fault Tolerant Deployment
Module Overview
Unicenter NSM provides a scalable, flexible, and automated solution to manage your network and systems environment for continuous availability and optimal performance. In response to recent growth and the resulting challenges, implementing Unicenter NSM can provide RBC with a true, cross-platform enterprise management solution. A well thought-out implementation plan is important to a successful production rollout of Unicenter NSM. Unicenter NSM offers network and systems management capabilities. These capabilities provide resource availability and control for the most granular insight into the extended infrastructure. Network and systems management solutions monitor status, event, and configuration information for the following infrastructure:

Linux and Microsoft Windows to OS/390 Frame Relay and TCP/IP networks Clusters and storage area networks (SANs)
Notes
1-2
Plan a Unicenter NSM Implementation Module Overview
Unicenter NSM provides integrated management of industry-standard devices and network protocols. It manages network and application performance across network boundaries, providing a complete picture of end-to-end status and performance. Using flexible architecture, innovative visualization, and intelligence technologies, Unicenter NSM delivers superior scalability and administration in a modular, expandable, easy-to-use design.
Notes
1-3

Task 1: Analyze the Corporate Environment
Slide 1-2

Successful implementation of Unicenter NSM requires a solid understanding of your business environment, processes, and IT infrastructure. You also require a solid understanding of how to apply Unicenter NSM as the solution to these business issues. There are invariably specific and immediate business objectives that Unicenter NSM is expected to address and resolve. It is essential to understand these objectives and your entire corporate business environment prior to implementing Unicenter NSM. Consult with each department to learn their particular business processes and the impact of these processes on the whole organization. Acquiring this level of understanding means documenting and analyzing the corporate computing environment as follows:
Slide 1-3
Document each business objective, its associated applications, and the service levels you expect Unicenter NSM to manage. Examples might include: Network availability - 99.9% Email availability - 99% Website availability - 100%
Determine the business needs that Unicenter NSM is expected to address, for example, identify the following: Devices to be monitored or managed Type of reporting required Type of response required if a monitored object is unreachable or if specific error messages are received Type of security required Type of job processing required
Notes
1-4
Plan a Unicenter NSM Implementation Task 1: Analyze the Corporate Environment
Location of administration Individuals who need administrative capabilities Individuals who need informational-only capabilities and how those capabilities will be provided Individuals who need automatic notification of the status and state of specific objects and how these notifications will occur Individuals responsible for administering the databases
Document the following information for your current hardware and software: Number, type, and location of computers impacted by this implementation (such as user interface clients, managers, and managed devices) or installed with the enterprise management database (MDB) The operating system of those computers including release and maintenance level Major software applications installed on those computers and their corresponding roles for example, mail server Available disk space and processor load on those computers Open issues regarding functionality of computers or software
Document hardware naming conventions. Consider the following network resources: Physical layout, logical aspects such as local area network (LAN) segments, and devices such as servers, printers, and workstations Line speed and the current and planned backbone Load information
Obtain existing network and server performance documentation, if any, and define performance improvement expectations.
Notes
1-5


Obtain network topology maps, if available. Document network addressing and subnetting schemes. Document network protocols, including routing, and routed and bridged protocols. Determine potential LAN or wide area network (WAN) traffic patterns. Document LAN or WAN security, such as firewalls, proxy servers, and community strings. Determine the following operational standards and restrictions: Scheduled downtimes Existing firewalls and which ports are available to open Security restrictions Failover requirements Naming conventions
Research the future evolution of the environment, such as the addition of new computers, a change in network structure, OS changes, and the implementation of other software solutions.
Task Summary
In this task, you learned that analyzing your corporate environment enables you to choose the right component configuration for your platform. This task was accomplished by investigating business objectives, environment, processes, and IT infrastructure. In the next task, you will review the platform and OS requirements for Unicenter NSM.
Notes
1-6
Plan a Unicenter NSM Implementation Task 2: Evaluate Platform and OS Requirements
Slide 1-4
Task 2: Evaluate Platform and OS Requirements

Unicenter NSM r11.x manager components can run on Microsoft Windows or Linux OS. Specific requirements depend on the platform you are using, the Unicenter NSM release, and which components of Unicenter NSM are being deployed. Software applications, other than Unicenter NSM, running on these target computers also impact requirements.
Slide 1-5
Consult the following information sources for hardware and software requirements:

GettingStarted.pdf on install media Readme file on install media Product home page at http://supportconnect.ca.com
Task Summary
The general platform and OS requirements represent a starting point you must consider when planning a Unicenter NSM implementation. In the next task, you will learn what to consider when selecting the component configuration for your environment.
Notes
1-7

Task 3: Define Unicenter NSM Component Configurations
Slide 1-6
Task 3: Define Unicenter NSM Component Configurations

Unicenter NSM comprises several components that can be installed in a centralized or distributed manner. Unicenter NSM functions well in standardized or diverse OS environments. The selection and distribution of Unicenter NSM components for installation directly impacts the specifications for the serverclass hardware you choose. No single design effectively applies to all environments. The environment, requirements of the organization, and policies necessary to deliver the solution impact the final configuration. You also need to consider network speed, network topology, server capability and capacity, and potential for growth when defining the Unicenter NSM component configuration.
Slide 1-7
Slide 1-8
The four essential Unicenter NSM components are:

MDB WorldView and Management Command Center (MCC) Distributed State Machine (DSM) Event Manager
All these components can be installed on one computer. They can also be installed on multiple computers to accommodate a distributed environment. This is the recommended approach in large environments with thousands of managed devices spread across the globe. Your configuration choices will be between a highly centralized and a highly distributed architecture. The MCC is an administrative GUI and typically should not be installed or run on a management node. For additional information, refer to the current version of the Implementation Guide provided in the Documentation folder of the Unicenter NSM product DVD.
Notes
1-8
Plan a Unicenter NSM Implementation Task Summary
Task Summary
In this task, you learned what factors to consider when choosing a Unicenter NSM component configuration. In the next task, you will learn that it is critical to maintain a reliable environment during the implementation process.
Notes
1-9

Task 4: Define a Fault Tolerant Deployment
Slide 1-9
Task 4: Define a Fault Tolerant Deployment

The fault tolerance of a product represents the ability to continue functioning after the loss of a critical component or system. Terms like high availability, failover, and fallback are often used in conjunction with fault tolerance. Failover is the switch from a primary system to a backup system. It is generally reserved for the most critical systems and is configured to perform automatically. Fallback is normally designated as a manual task and is a satisfactory solution for non-critical system restoration. In addition, fallback usually permits enough time to accurately identify the cause of the failure prior to returning the primary system to service.
Slide 1-10
The following graphic is an example of a fault tolerant deployment:
Notes
1-10
Plan a Unicenter NSM Implementation Task 4: Define a Fault Tolerant Deployment
Slide 1-11
The level of tolerance you have for component or system failures dictates the level of fault tolerance you need. Choices range from the standard backup and restore systems to advanced clustering technologies or high availability. Regardless of your choice, the decision requires two basic considerations. First, consider the impact a component or system failure will have on business processes. Second, consider the amount the organization is willing to invest to maintain the health of business processes. When running in High Availability mode and if running on the same node of a cluster, the Enterprise Management Unicenter service and the Ingres Intelligent Database service must be launched by the Cluster Administrator. These two services will then switch together from one node to another during a failover event. In highly available installations, the MDB data files, which include Enterprise Management data, are located on the cluster shared disk instead of under the same high-level directory tree of the Ingres executables. When Enterprise Management and Ingres fail over from one node to the next, the shared disk containing the MDB data files becomes available to the new node. The Enterprise Management and Ingres servers on the new node continue from where they left off on the old node.
Task Summary
In this task, you have learned that fault tolerance represents the level of tolerance required to maintain a reliable environment. You have also become familiar with fault tolerance terminology, such as high availability, failover, and fallback.
Notes
1-11

Assessment
Assessment
1 To successfully implement Unicenter NSM, which three factors do you need to understand? (Choose three.) a b c d e 2 Annual revenue IT infrastructure Employee turnover Business objectives Business environment
Unicenter NSM r11.x manager components can run on which two operating systems? (Choose two.) a b c d Linux Debian Solaris 10 Microsoft Windows
Which two Unicenter NSM managers are essential components in a centralized or distributed design architecture? (Choose two.) a b c d LAN DSM RAID Event Manager
Notes
1-12
Plan a Unicenter NSM Implementation Assessment
When running in High Availability mode and if running on the same node of a cluster, the Enterprise Management Unicenter service and the Ingres Intelligent Database service must be launched by which feature? a b c d MCC Cluster Administrator Ingres Configuration Manager Cluster Configuration Manager
Notes
1-13

Module Summary
Slide 1-12
Module Summary
You should now be able to:

Analyze the Corporate Environment Evaluate Platform and OS Requirements Define Unicenter NSM Component Configurations Define a Fault Tolerant Deployment
When planning a Unicenter NSM implementation, you must analyze the corporate environment. You also have to consider general platform and OS requirements and possible component configurations. In addition, you have to take into account the level of fault tolerance required to maintain a reliable environment. As a result of your planning, you will be able to perform a successful Unicenter NSM implementation for RBC. In the next module, you will install Unicenter NSM components.
Notes
1-14
2
Install Unicenter Components
2-1

Module Objectives
Slide 2-1
Module Objectives

Establish the Required DNS Service Location Record Install Unicenter NSM Describe Unicenter NSM Architecture Install the Linux System Agent Verify Active DIA Connections Verify MCC Provider Connections
Module Overview
Unicenter NSM delivers innovative, secure, and platform-independent management solutions to enable you to confidently deploy single platform or heterogeneous business applications for RBC. Unicenter NSM solutions help you sustain an optimized, on-demand infrastructure, maximizing RBCs IT investment by continuously assessing and self-managing network and systems elements. In this module, you will establish the DNS Service Location Record and then install and configure Unicenter NSM. You will learn about the different Unicenter NSM architectural components and their functions. In addition, you will learn how to install the Linux System Agent. You will also verify active DIA connections and examine the Master KB component. Lastly, you will use the MCC, made possible by the Global Catalog, to maintain information about the availability and location of key Unicenter NSM management components.
Notes
2-2
Install Unicenter Components Task 1: Establish the Required DNS Service Location Record
Slide 2-2
Task 1: Establish the Required DNS Service Location Record

Unicenter NSM management components use the Distributed Intelligence Architecture (DIA) protocol to access information throughout the enterprise. Consumers of DIA accessible management information are:

Slide 2-3
Management Command Center (MCC): Accesses Alerts and Console Logs through DIA Distributed State Machine (DSM): Polls Unicenter NSM r11.x Agents through DIA Unicenter NSM r11.x Agents: Send alerts to the DSM through DIA Unicenter Configuration Management (UCM): Gathers and distributes agent profiles through DIA Advanced Event Correlation (AEC): Distributes AEC policies through DIA Unicenter Management Portal (UMP): Accesses Unicenter NSM Management Component information through DIA Unicenter Adaptive Dashboard Server (ADS): Communicates with agents through DIA
DIA communication depends on the establishment of the DIA grid. The DIA grid consists of one or more zones, each of which contains one or more Unicenter Knowledge Bases (UKB). Zones can be used to logically segment the DIA grid. An example of this might be a Production zone and a Test zone. Resource visibility can be restricted to one zone or the other. The MCC is the only DIA consumer that can communicate across zones. All external interfaces access DIA through the UKB, which is the central source of data for DIA. The UKBs each maintain a copy of the grid. One UKB fills the role of the Master Knowledge Base (MasterKB). All other UKBs communicate with the MasterKB informing it of changes to locally registered DNA and obtaining updates that the MasterKB has received.
Notes
2-3

Demonstration The MasterKB is identified by the presence of a Service Location (SRV) _grid record in the Domain Name Service (DNS). The _grid record identifies the host name of a UKB. A priority is assigned to each _grid record. The active UKB with the highest assigned priority assumes the role of MasterKB. Alternatively, the MasterKB is identified by an entry in the dna.cfg file. DNA is the smallest DIA component needed to cultivate knowledge from a given system. DNA uses genes and cells to build knowledge that can be accessed from an external interface. DNA cells are registered to DNA by installers. For example, if you install Agent Technology, the agent cell will be registered, or if you install WorldView, the WorldView cell will be registered. When DNA first starts, it recognizes that it has not been registered and queries the MasterKB identified by the DNS _grid record or dna.cfg file. The MasterKB allocates the DNA registration to a UKB. The allocation is to the local UKB if present. Otherwise, the MasterKB uses its rule file to assign the node to a zone and an inbuilt rule to allocate the DNA registration to a UKB active within the zone. The MasterKB responds to the query with the name of the allocated UKB and the zone name. DNA then initiates a registration request with the identified UKB. It publishes its registered cell information to its UKB during this registration. After DNA is registered to the UKB, the UKB will synchronize with the MasterKB, and the MasterKB ensures that all UKBs within a zone are synchronized.
Demonstration
Task Purpose: Create SRV records in the DNS. Set up SRV record in the DNS to establish DIA MasterKB location. Note: The following demonstration is performed on the DNS server (T2 computer). View Current _grid SRV Record Properties: 1 2 Click Start and then choose Programs Expand Forward Lookup Zones. Administrative Tools DNS.
Notes
2-4
Install Unicenter Components Demonstration
3 4 5 6 7 8 9
Expand the classroom domain name. Select _tcp. In the right pane, right-click _grid and select Properties. Observe the _grid record values. Click OK to close the _grid Properties window. Right-click _tcp and select Other New Records. In the Resource Record Type dialog, select Service Location (SRV). Click Create Record. Note: If a new _grid record was needed, the fields would be completed using the values observed in step 5.
Identify Method to Create New SRV Record:
10 Click Cancel.
Task Summary
In this task, you discussed the importance of the Distributed Intelligence Architecture (DIA) protocol. You also identified the purpose of the _grid SRV record and identified how to create one.
Notes
2-5

Task 2: Install Unicenter NSM
Slide 2-4
Task 2: Install Unicenter NSM

You can implement Unicenter NSM in a number of ways. You might have a single server with all agents reporting to a central point. Alternatively, you might have a distributed environment with several managers strategically placed throughout the environment. Whatever server architecture you use, understanding its hardware and software requirements can greatly improve your ability to manage the structure. Unicenter NSM must evolve to meet the ever-changing needs of the IT industry. For this reason, it is important to check the most current documentation before starting a new implementation. The following documents are helpful references when starting a Unicenter NSM implementation:
Slide 2-5
The Getting Started Guide is an excellent resource for a detailed overview of the Unicenter NSM architecture. This resource includes specific hardware and software recommendations to consider prior to installation. The Release Summary has detailed information about the new features and enhancements in the current Unicenter NSM release. The Administrators Guide is another valuable resource to assist in the design phase. It provides details about how to manage and maintain your entire infrastructure using Unicenter NSM.
Notes
2-6
Install Unicenter Components Interactive Demonstration
Task Purpose: Confirm existence of DNS _grid Service Location (SRV) record. The Unicenter NSM installation will include Distributed Intelligence Architecture (DIA). DIA registration depends on the availability of a DNS _grid Service Location (SRV) record that identifies the location of the DIA Master Knowledge Base (MasterKB). The host must be logged on to the domain to have access to this record. 1 2 Double-click the Command Prompt shortcut on the desktop. Type whoami and press ENTER. The response should be usxxdomyyzz\administratorzz. If the response indicates the host is logged on to the local machine rather than the domain, log off and log back on to the domain. Type nslookup and press ENTER. Type set type=SRV and press ENTER. Type _grid._tcp and press ENTER. The _grid record should be returned pointing to the usxxyyT1.usxxdomxxyy.com host. If the _grid record is not returned, the installation should be put on hold until the situation is corrected.
3 4 5
Notes
2-7

Task Purpose: Install Unicenter NSM with Ingres MDB. Note: It is highly recommended that you perform a Unicenter NSM installation once or twice in a lab to get acquainted with the installation process prior to a production installation. When you perform a full Unicenter NSM installation, you must begin the installation by inserting the Unicenter Network and Systems Management for Microsoft Windows Install CD. 1 2 3 4 5 6 7 8 9 In Microsoft Windows Explorer, open the following folder: C:\InstallMedia\UNI_NSM_R11\Windows Double-click the setup.exe file. The Unicenter Product Explorer appears. Select Installation Wizard for Unicenter NSM and click Install. The Unicenter NSM Installation Wizard appears. Accept the default option Install any or all Unicenter NSM components and click Next. Scroll to the end of the license agreement, select I accept the terms in the license agreement, and click Next. Type YourName in the Your name field, type YourCompanyName in the Company name field, and click Next. On the Component Selection screen, clear Express Install. Click Unicenter NSM Components twice to clear it. Expand the Ingres folder.
10 Select Ingres Client and Ingres Server. 11 Expand the WorldView folder. 12 Select Administrative Client, WorldView Manager, and WorldView Provider. 13 Expand the Agent Technologies folder.
Notes
2-8
14 Expand the Manager folder. 15 Select Distributed State Machine, Agent Views, and Agent Technologies DSM Provider. 16 Expand the Agent Technology Agents folder. 17 Select Windows System Agent. 18 Expand the Enterprise Management folder. 19 Select Alert Management and Enterprise Management Provider. 20 Select Management Command Center. 21 Expand the Continuous Discovery folder. 22 Select Continuous Discovery Agent and Continuous Discovery Manager. 23 Expand the Notification Services folder. 24 Select Notification Services Client and Notification Services Server. 25 Select Configuration Manager. Note: Web Reports and Dashboards is automatically selected as a result of selecting Configuration Manager. 26 Click Next. 27 On the Component Functionality screen, confirm that Automatically start Enterprise Management services, Automatically start Agent Technologies services, and Automatically start WorldView services are selected. 28 Clear Adaptive Configuration Support for Windows System Agent and Automatically start Continuous Discovery services. 29 Click Next.
Notes
2-9

Interactive Demonstration 30 On the Ingres configuration window, confirm EI as the Ingres Installation code. Note: Take note of the EI code because you will need it for MDB connections. 31 Accept the default user name nsmadmin. 32 Type unicenter in the Password and Confirm password fields. Note: When Check password rules is selected, Unicenter NSM validates the password against Microsoft Windows domain criteria. 33 Click Next. 34 On the Database Selection and Configuration screen, confirm that Enterprise Management Database and WorldView Repository are selected. 35 Click Next. 36 On the Unicenter Administrator Credentials screen, accept the default user name caunint. Note: The default Unicenter NSM Administrator user name, caunint, should not be changed. 37 Clear Use random password. 38 Type unicenter in the Password and Confirm Password fields. Note: Establishing a unique password is mandatory. This account, used by Unicenter NSM, is added to the Windows Administrators Group with the added User Rights of Log on as a service and Act as part of the operating system. 39 Click Next.
Notes
2-10
40 On the Event Server screen, accept the default option This machine will be processing its own Event Management messages. 41 Select Enable automatic trap translation. 42 Click Next. 43 On the Connection Manager screen, click Next. 44 On the Apache Tomcat Configuration Information screen, type unicenter in the Password and Confirm password fields. 45 Click Next. 46 On the Global Catalog screen, accept the default setting The Global Catalog will reside on the local System. 47 Click Next. 48 On the Install Directories screen, click Next. 49 On the Selection Summary screen, click Next. 50 To begin the installation, click Install. 51 Click OK when prompted to close all open windows before continuing.
Task Purpose: Install Microsoft SQL Server 2000. On the following pages, your instructor will conduct a walkthrough of the Microsoft SQL Server 2000 Standard Edition installation. You will need the following information: Information Required CD Key Setup Type Value ____ ____ ____ ____ Custom
Notes
2-11

Interactive Demonstration Information Required Select Components Components Server Components Management Tools Client Connectivity Sub-Components SQL Server Performance Counters Enterprise Manager Query Analyzer Conflict Viewer Service Accounts Authentication Mode Use the Local System account Mixed Mode (Windows Authentication and SQL Server Authentication) sa password is unicenter Collation Settings SQL Collations (Used for compatibility with previous versions of SQL Server) Dictionary order, case-sensitive for use with 1252 Character Set Network Libraries Named Pipes TCP/IP Sockets Port number 1433 Choose Licensing Mode Per Seat 20 Value
Notes
2-12
1 2
From the Windows Explorer, open the C:\InstallMedia\SQL_2000 folder. Double-click Setup.bat. Note: For a typical installation, you would insert the MS SQL Server 2000 CD. The installation program will automatically run. To get to the Microsoft SQL Server Installation Wizard, select SQL Server 2000 Components, and then Install Database Server.
3 4 5 6 7 8 9
Click Continue at the warning screen. At the Welcome screen, click Next. For Computer name, accept the default option, Local Computer. Click Next. For Installation Selection, accept the default option, Create a new instance of SQL Server, or Install Client Tools. Click Next. For User Information, type your name and the company name.
10 Click Next. 11 On the Software License Agreement screen, click Yes. 12 For CD Key, type the 25-digit CD Key provided by the instructor. 13 Click Next. 14 For Installation Definition, accept the default option, Server and Client Tools. 15 Click Next. 16 For Instance Name, accept the default option by leaving Default selected. 17 Click Next. 18 For Setup Type, select Custom.
Notes
2-13

Interactive Demonstration 19 Click Next. 20 Under Select Components, select Server Components. 21 Clear all Sub-Components except for SQL Server and Performance Counters. Verify that SQL Server is selected. 22 Under Components, select Management Tools. 23 Clear the Sub-Components Profiler and DTC Client Support. Verify that Enterprise Manager and Query Analyzer are selected. Conflict Viewer will be selected automatically. 24 Under Components, clear Books Online and Development Tools. Verify that Client Connectivity is selected. 25 Click Next. 26 For the Services Accounts, verify that Use the same account for each service. Auto start SQL Server Service. is selected. 27 Select Use the Local System account. 28 Click Next. 29 For Authentication Mode, select Mixed Mode (Windows Authentication and SQL Server Authentication). 30 Type unicenter for the sa password in the ENTER password and Confirm password fields. 31 Click Next. 32 For Collation Settings, verify that SQL Collations (Used for compatibility with previous versions of SQL Server) is selected. 33 Select Dictionary order, case-sensitive for use with 1252 Character Set. 34 Click Next. 35 For Network Libraries, verify that Named Pipes is selected. 36 Verify that TCP/IP Sockets is selected. This is required for communication through routers.
Notes
2-14
37 Verify that the TCP/IP Socket Port Number is set to 1433. 38 Click Next. 39 Start Copying Files. 40 Click Next. 41 For Choose Licensing Mode, to keep our classroom environment simple, accept the default option Per Seat for. 42 Increase the number of devices to 20. 43 Click Continue. Note: The Microsoft SQL Server Installation Wizard will then install SQL Server according the configuration settings you have specified. 44 To complete the setup, click Finish. Note: The Microsoft SQL Server Installation Wizard will close automatically. 45 Close Windows Explorer.
Task Purpose: Install SQL Service Pack 4 and Verify the Configuration Properties. Using the SQL Service Pack provided by Microsoft, administrators can install the latest patch and verify the installation by using the SQL 2000 Query Analyzer to confirm the installation. 1 2 From Windows Explorer, open the C:\Student\UR215 folder. Double-click sql_sp4_install.bat.
Notes
2-15

Interactive Demonstration 3 4 Verify the Configuration Properties by opening the SQL Query Analyzer. Click Start Programs Microsoft SQL Server Query Analyzer. Connect to your SQL Server. Click the button with the three dots next to the SQL Server field to open the Select Server window, and select your computer name (database) from the list. Click OK to close the Select Server window. Note: Observe the check box Start SQL Server if the server is stopped. The Query Analyzer can also be used to start SQL Server. 6 7 8 9 Verify that SQL Server authentication is selected. Verify that the Login name is sa. Type unicenter in the Password field. Click OK.
10 Query the Master Database. Make sure that the Master Database is selected. You can verify the selection in the drop-down box on the toolbar at the top of the SQL Query Analyzer. 11 Run a Query to check the SQL Collation (Sort Order) has been installed correctly. In the open window, type sp_helpsort. 12 Click Execute Query (green arrow on the toolbar), or press F5 to execute the query. Note: A second window will appear under the first window, showing the results of your query. 13 Verify that Latin1-General, case-sensitive appears in the query results window. 14 To run a query to check the Version (Service Pack) level of this installation of SQL Server, under the first query, type select @@version.
Notes
2-16
15 Click Execute Query (green arrow on the toolbar), or press F5 to execute the query. Note: A third window will appear under the second window, showing the results of your query. 16 Verify that Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) appears in the query results window. 17 Close the SQL Query Analyzer. 18 Do not save the changes, click No To All.
Task Purpose: Install Unicenter NSM with SQL MDB. Note: It is highly recommended that you perform a Unicenter NSM installation once or twice in a lab to get acquainted with the installation process prior to a production installation. When you perform a full Unicenter NSM installation, you must begin the installation by inserting the Unicenter Network and Systems Management for Microsoft Windows Install CD. 1 2 3 4 5 In Microsoft Windows Explorer, open the following folder: C:\InstallMedia\UNI_NSM_R11\Windows Double-click the setup.exe file. The Unicenter Product Installer appears. Select Installation Wizard for Unicenter NSM and click Install. The Unicenter NSM Installation Wizard appears. Accept the default option Install any or all Unicenter NSM components and click Next. Scroll to the end of the license agreement, select I accept the terms in the license agreement, and click Next.
Notes
2-17

Interactive Demonstration 6 7 8 9 Type YourName in the Your name field, type YourCompanyName in the Company name field, and click Next. On the Component Selection screen, clear Express Install. Click Unicenter NSM Components twice to clear it. Select Management Database.
10 Expand the WorldView folder. 11 Select Administrative Client, WorldView Manager, and WorldView Provider. 12 Expand the Agent Technologies folder. 13 Expand the Manager folder. 14 Select Distributed State Machine, Agent Views, and Agent Technologies DSM Provider. 15 Expand the Agent Technology Agents folder. 16 Select Windows System Agent. 17 Expand the Enterprise Management folder. 18 Select Alert Management and Enterprise Management Provider. 19 Select Management Command Center. 20 Expand the Continuous Discovery folder. 21 Select Continuous Discovery Agent and Continuous Discovery Manager. 22 Expand the Notification Services folder. 23 Select Notification Services Client and Notification Services Server. 24 Select Configuration Manager. Note: Web Reports and Dashboards is automatically selected as a result of selecting Configuration Manager.
Notes
2-18
25 Click Next. 26 Click OK to acknowledge absence of _grid record warning. 27 On the Component Functionality screen, confirm that Automatically start Enterprise Management services, Automatically start Agent Technologies services, and Automatically start WorldView services are selected. 28 Clear Adaptive Configuration Support for Windows System Agent and Automatically start Continuous Discovery services. 29 Click Next. 30 On the Management Database (MDB) Setup screen, leave the Database Instance Name field blank. 31 Accept the default user name nsmadmin. 32 Type unicenter in the Password and Confirm password fields. 33 Click Next. 34 On the Database Selection and Configuration screen, clear the Database Instance Name field for both the Enterprise Management Database and the Worldview Repository. 35 Click Next. 36 On the Unicenter Administrator Credentials screen, accept the default user name caunint. Note: The default Unicenter NSM Administrator user name, caunint, should not be changed. 37 Clear Use random password.
Notes
2-19

Interactive Demonstration 38 Type unicenter in the Password and Confirm Password fields. Note: Establishing a unique password is mandatory. This account, used by Unicenter NSM, is added to the Windows Administrators Group with the added policies of Logon as a Service and act as part of the operating system. 39 Click Next. 40 On the Event Server screen, accept the default option This machine will be processing its own Event Management messages. 41 Select Enable automatic trap translation. 42 Click Next. 43 On the Connection Manager screen, click Next. 44 On the Apache Tomcat Configuration Information screen, type unicenter in the Password and Confirm password fields. 45 Click Next. 46 On the Global Catalog screen, accept the default setting The Global Catalog will reside on the local System. 47 Click Next. 48 On the Install Directories screen, click Next. 49 On the Selection Summary screen, click Next. 50 To begin the installation, click Install. 51 Click OK when prompted to close all open windows before continuing. In the following interactive demonstration, you will create an Agent Response file.
Notes
2-20
Task Purpose: Create an Agent Response file. 1 2 Open Virtual Windows 2003 Server 2. To log on to the server, press CTRL+ALT+INSERT and type the following: User Name: administratorzz Password: usxxyyzzcai 3 Change to the folder where the installation media resides. a b For Ingres student environment, navigate to: For MS SQL Server student environment, type: Shared Folders on .host:(Z:)\InstallMedia\UNI_NSM_r11\Windows Shared Folders on .host:(Z:)\InstallMedia\UNI_NSM_r11_1\Windows 4 5 6 Execute the setup.exe file. To start Unicenter Network and Systems Management, click Run. On the Unicenter Product Explorer window, under Unicenter for Windows, verify that Installation Wizard for Unicenter NSM is selected as the default option. Note: Install Status indicates this component is already installed. 7 8 Click Install. On the Unicenter NSM Installation Wizard window, under Setup Options, select Build Unicenter NSM response file for unattended install.
Notes
2-21

Interactive Demonstration 9 Click Browse, and on the Save As window, navigate to C: and type the following file options: File name: nsmagent.rsp Save as Type: Response Files 10 Click Save. 11 Scroll to the end of the license agreement, select I accept the terms of the license agreement, and click Next. 12 On the Company Information window, type the following details: Your name: username Company name: company name 13 Click Next. 14 Review the Upgrade information, select I have read and understand these upgrade ramifications, and click Next. 15 On the Component Selection window, under Configuration choices, clear the Unicenter NSM Components option. 16 Expand Agent Technologies\Agent Technology Agents, select Windows System Agent, and click Next. 17 On the Component Functionality window, clear the Adaptive Configuration Support option. 18 Under Configuration Preferences, verify that Automatically start Agent Technologies services is selected. Click Next. 19 Verify the Install Directories and Drive Utilization Summary information and click Next. 20 Examine the Selection Summary window to review your installation values. Click Next. 21 The Interview Complete window provides verification that the Response File has been successfully created, indicates the file location, and provides details for using this file. Click Done.
Notes
2-22
Response files deploy large numbers of agents to save time and increase efficiency. Next, you will practice deploying an Agent Response file.
Task Purpose: Install scripted installations. To install the script that you have generated, follow these steps: 1 2 Open a Command Prompt window. To change to the drive where the installation media resides, type the following and press ENTER: Z: 3 Change to the folder where the installation media resides: a For Ingres student environment, type: cd Installmedia\UNI_NSM_r11\Windows b 4 For MS SQL Server student environment, type: cd Installmedia\UNI_NSM_r11_1\Windows Execute the setup application specifying the location of the script file. a For Ingres student environment, type: setup -NT="z:\Student\UR215\nsmagent.rsp" CDPATH="z:\Installmedia\UNI_NSM_r11\Windows" b For MS SQL Server student environment, type: setup -NT="z:\Student\UR215\nsmagent.rsp"CDPATH="z:\Installmedia\UNI_NSM_r11_1\Windows" Note: Monitor nsmsetup.exe in the Task Manager. When the process is no longer running, the installation is complete. Restart the server.
Notes
2-23

Verify a Successful Agent Installation

5 6 Type atscm at the command prompt. Verify the following services: aws_orb aws_agtgate aws_sadmin caiWina3 In the following interactive demonstration, you will perform post-installation activities for the classroom environment. Note: Installation must be complete prior to performing these activities.
Task Purpose: Discover the host machine. Perform the following steps on the host server: 1 2 At a command prompt, type cd student\ur215 and press ENTER. Type discover.bat YourServerName and press ENTER.
Skill Practice
Task Purpose: Discover the VMware session. Run the discover.bat file again with the hostname for Virtual Windows 2003 Server 2 as the parameter.
Notes
2-24
Install Unicenter Components Task Summary
Task Summary
In this task, you learned that you can implement Unicenter NSM in a number of ways. You might have a single server with all agents reporting to a central point. Alternatively, you might have a distributed environment with several managers strategically placed throughout the environment. In this task, you first confirmed the existence of DNS _grid Service Location (SRV) record. Then, you proceeded to install Unicenter NSM with Ingres MDB and with SQL MDB. You also created an Agent Response file, installed scripted installations, and discovered a host machine and VMware session.
Notes
2-25

Task 3: Describe Unicenter NSM Architecture
Slide 2-6
Task 3: Describe Unicenter NSM Architecture

Unicenter NSM provides a scalable architecture to design and deploy a complete Enterprise Management solution. The architecture provides dynamic services for:

Visualizing network topology Monitoring the health of network devices Implementing an integrated system management solution
Unicenter NSM provides enhanced control over your distributed computing environment for a proactive approach with day-to-day operations. Because your organization might be global, it can require a scalable architecture with a location-based rollout to establish regional management. The implementation requires its own local administrative staff to establish a system management policy that mandates a proactive response to expedite the resolution for network faults and system outages. Unicenter NSM supports localization for regional implementation, promotes network bandwidth efficiency, and integrates into the global architecture that best suits your IT Infrastructure.
Slide 2-7
The three conceptual layers in Unicenter NSM are:

WorldView Manager Systems Monitoring
You can implement all three layers on one computer. However, depending on their perceived role and location, you would implement these layers across several computers in your environment.
Notes
2-26
Install Unicenter Components Explain WorldView
Slide 2-8
Explain WorldView
The WorldView layer, highlighted in the following graphic, is the repository for the graphical visualization of the enterprise:
Slide 2-9
The WorldView layer consists of three components:

MDB Real World Interface WorldView Application Interface (API)
Notes
2-27

Explain WorldView
MDB
CA product suites are integrated through a common enterprise data repository, the MDB. The MDB provides a unified database schema for management data stored by all mainframe and distributed CA products. Use of the MDB with CA products enables full integration for managing your IT infrastructure. CA products are delivered out-of-the-box with an MDB running on a high-performance Ingres database. You can extend the MDB to include additional IT management data from non-CA software products and tools.
Real World Interface

The Real World Interface consists of the tools used to access the MDB. It enables the user to view and manipulate classes and objects in the MDB. These views can be customized to provide appropriate information for a variety of users. One user can visualize the contents of many repositories while another can visualize the same information from a different perspective. One of the Real World Interface tools is Common Discovery. Common Discovery is the process by which network devices are found and classified and then placed in the MDB as managed objects. Devices are discovered using Classic Discovery or Continuous Discovery. The MCC is another Real World Interface tool that is used to visualize and investigate the contents of the MDB. The MCC Topology view displays the MDBs that you choose to view.
WorldView API
The third component of the WorldView layer is the WorldView API. Most Unicenter NSM components connect to the WorldView tables of the MDB through the WorldView API. The WorldView API component enables you to create and integrate functions with the MDB.
Notes
2-28
Install Unicenter Components Explain the DSM Manager
Slide 2-10
Explain the DSM Manager

The Manager layer is comprised of several components grouped into various categories. Monitoring is one of these categories and contains the agent facilities that monitor and determine the state of the enterprise. Another category is Enterprise Management, which is a collection of integrated managers that control and automate a variety of functions and responses in the enterprise. The DSM is the manager for agent technology. The DSM discovers and maintains the state of all managed objects in the Agent layer. As the manager of Agent Technologies, the DSM determines the state of a managed object. The state of the managed object is represented as Warning, Critical, or Down and it is the responsibility of the DSM to update this information in the MDB. The Manager layer is highlighted in the following graphic:
Slide 2-11
Notes
2-29

Describe the Role of Agents in Systems Monitoring A DSM can manage many objects in the Agent layer. Each DSM can report to only one MDB. The MDB, however, can have multiple DSMs reporting the state of managed objects to it.
Slide 2-12
Describe the Role of Agents in Systems Monitoring

An agent is an application that supports network management. Agents gather information from your enterprise through remote access monitoring and control resources. Agents are located on, or near, managed objects and provide information to a management application, such as Unicenter NSM. To detect abnormal situations and rectify problems, agents:

Monitor network devices and report the status of their environments to their managers. Communicate with managers by sending information about changes in the status of the monitored resource (managers can also poll agents). Are scalable so a number of agents can be applied to one resource.
Notes
2-30
Install Unicenter Components Describe Enterprise Management
The Agent layer is highlighted in the following graphic:

Slide 2-13
Slide 2-14
Describe Enterprise Management

Enterprise Management is a collection of integrated system management functions available through Unicenter NSM. The Manager layer consists of managers that deal with control issues. Using the Manager layer, you can centralize the management of your enterprise. It can be used to implement security, automate storage, schedule jobs, and control events.
Notes
2-31

Describe Enterprise Management The Event Management System (EMS) is the focal point for managing enterprise events from a variety of sources throughout your network. Through the Console Log, you can monitor event activity and immediately respond to events as they occur. By filtering messages that appear on each console, you can retrieve specific information about a particular node, user, or workstation. Components of the EMS include the following:

Console log views enable you to restrict message access to authorized users and user groups. Calendars enable you to establish date and time controls for automated event processing. Message record and action profiles enable you to identify events that are important to your operation and define the special processing that Unicenter NSM performs when encountering these events. Advanced Event Correlation (AEC) enhances your message record and action policy by identifying a set of events that you want to monitor and correlate. It also identifies what actions should be performed if correlation exists or does not exist.
The Alert Management System (AMS) is a tool for organizing and tracking the most important events in an enterprise or a logical segment of an enterprise. It enables you to focus on and manage the highest severity IT events. With AMS, you can:

Specify the situations that create alerts and define alert policies. View and manage alerts in multiple panes of the MCC. Link to the Unicenter Service Desk, which is a customer support application that manages calls and IT assets, tracks problem resolution, and shares corporate knowledge.
Alerts are important or critical events generated by one or more source events in the EMS. You can organize, view, and manipulate alerts in complex ways with the MCC.
Notes
2-32
Install Unicenter Components Describe Enterprise Management
Alert management maintains specialized events processed through message records and actions or AEC policies. Extending and tailoring policies to any environment becomes easy when using a class-based approach. Another commonly implemented Enterprise Management function is Unicenter Job Management. Job managers control job scheduling. Job agents process commands at the direction of job managers. Installing a job agent enables the computer to be part of job process execution. Configure one or more job managers to direct job scheduling; configure one or more job agents across different computers and platforms to execute jobs. Job management can span multiple platforms. Job managers are supported on the following platforms:

MVS UNIX Linux Microsoft Windows
Job agent support is provided through the Unicenter Universal Job Management Agent. It supports the following platforms:

OpenVMS OS/400 UNIX Linux Microsoft Windows
The function of the job agent is to implement and track the status of jobs on the local system; the function of the job manager is to instruct and manage the job agent. Use the ability to schedule and track jobs across multiple platforms to enable flexibility in the architecture. For example, a UNIX job manager can control not only UNIX job agents but also Microsoft Windows job agents.
Notes
2-33

Describe Unicenter NSM Catalog Services
Slide 2-15
Describe Unicenter NSM Catalog Services

The MCC provides an interface for monitoring the enterprise from a single focal point. Implemented in Java, the MCC combines several Unicenter NSM components using plug-ins for ease of infrastructure management. The MCC runs on various platforms, which simplifies its use in a heterogeneous environment. The MCC requires the installation of companion applications and services to operate properly. The prerequisites are the Java 2 Compliant Operating System and Java runtime environment (JRE). When installing the MCC, the Unicenter NSM Installation Wizard performs a check to determine the operating system being used and to validate Java capability. In today's market, generally all operating systems are Java 2 compliant. Prior to installing Unicenter NSM, the Add and Remove Programs utility in the Microsoft Windows Control Panel can also be opened to determine the installation status of prerequisite applications. The Unicenter NSM Installation Wizard automatically performs a JRE installation if the application is not present. To verify the JRE installation, complete a postinstallation check to visually identify the current version of the Java Plug-In listed in the Add and Remove Programs utility. You can access related configuration information through each of the corresponding tabs in the Java Plug-In Control Panel. Open the Java Plug-In Control Panel by double-clicking the Java Plug-In applet in the Microsoft Windows Control Panel.
Notes
2-34
Task Summary
In this task, you examined the components and functions of the Unicenter NSM architecture. Unicenter NSM will enable you to deploy and maintain a complex, secure, and reliable infrastructure that supports business objectives. It will also help ensure the continuous health and performance of your critical infrastructure and controls costs while maintaining or increasing responsiveness to changing business priorities. Its ability to integrate with other solutions in the CA portfolio and share information using a common database provides unparalleled network and systems management. In the next task, you will learn how to install the Linux System Agent.
Notes
2-35

Task 4: Install the Linux System Agent
Slide 2-16
Task 4: Install the Linux System Agent

The Linux System Agent monitors status, event, and configuration information for critical OS parameters, such as CPU utilization, disk space availability, swap file activity, and memory usage. It also monitors important desktop and server OS resources by adhering to user-defined policy. This agent detects profile deviations and, if necessary, escalates events to Unicenter NSM for appropriate action.
Slide 2-17
The Linux System Agent collects information on basic configuration settings. This information is collected once (immediately after the agent is initialized) and includes:

Node name System name OS release OS version Hardware details Boot time Run level (at start of agent)
There are two installation requirements for Unicenter NSM for Linux or UNIX:

The install media must be located in a local DVD drive or a networkmounted DVD drive. The target system must support a Java GUI installation.
Notes
2-36
Task Purpose: Install and manage the Linux System Agent. A Linux server has been added to a previously exclusive Microsoft Windows environment. Administrators have been tasked to monitor the Linux server by installing the Linux System Agent and configure Unicenter NSM to manage the agent.
Perform the following steps on your host: Identify Current Network Configuration
Prior to installing the Linux System Agent, you will need to identify the current classroom network configuration. In a later step, you will identify the IP address of the Linux virtual server. These values will be needed when you update the network configuration to meet the requirements of the Linux System Agent install. 1 2 3 Open a command prompt. Type ipconfig and press ENTER. Note the classroom Subnet Mask and Default Gateway values.
Start the Linux Virtual Machine

4 5 On the desktop, double-click the VMware Workstation icon. Select Red Hat Enterprise Linux 4 and click Power On.
Perform the following steps on the Linux virtual machine: Log on to the Linux Server
6 7 Type root in the Username field and press ENTER. Type password in the Password field and press ENTER.
Notes
2-37

Interactive Demonstration 8 If you receive an Internet address lookup error message, click Log in Anyway.
Identify the Current IP Address

9 Select Applications System Tools Terminal. 10 Execute ifconfig. 11 Note the IP address.
Update the Network Configuration

12 Select Applications System Settings Network. 13 Select the Devices tab. 14 Select the network device and click Edit. 15 Select Statically set IP addresses. 16 Set the Address, Subnet mask, and Default gateway address values using the current network configuration values obtained previously, and click OK. 17 Select the DNS tab. 18 Move the Secondary DNS address to the Tertiary DNS address field. 19 Move the Primary DNS address to the Secondary DNS address field. 20 Type the IP address of the classroom USxxyyT2 in the Primary DNS address field. 21 Type USxxDOMyy.com in the DNS search path field. 22 Select the Hosts tab. 23 Click New. 24 Enter the IP address obtained in step 11 in the Address field. 25 Enter USxxyyzzV3.USxxDOMyy.com in the Hostname field.
Notes
2-38
26 Enter USxxyyzzV3 in the Alias field. 27 Click OK. 28 Select File Save to save the network settings. 29 Click OK to acknowledge system-config-network changes saved message. 30 Close the Network Configuration window.
Perform the following steps on the Instructor T2 Server (instructor only): Create Host and PTR Records in DNS for Linux Hosts
31 Select Start Programs Administrative Tools DNS. 32 Drill down to DNS USxxyyT2 USxxDOMyy.com. Forward Lookup Zones
33 Right-click USxxDOMyy.com and select New Host (A). 34 Type the Linux host name and IP address in the appropriate fields. 35 Select Create associated pointer (PTR) record and Allow any authenticated user. Click Add Host. 36 Repeat steps 28 and 29 until all Linux hosts have been added. 37 Close the dnsmgmt window.
Perform the following steps on the Linux virtual machine: Activate the Updated Network Settings
38 Select Actions Log Out. 39 Select Save current setup and Restart the computer. Click OK. 40 Type root in the Username field and press ENTER.
Notes
2-39

Interactive Demonstration 41 Type password in the Password field and press ENTER.
Test the Updated Network Settings

42 In the terminal window, ping your host server. 43 Type hostname -i and press ENTER. 44 Type nslookup USxxyyzzV3 and press ENTER. Note: The setupNSM process requires that the hostname -i and nslookup <Linux hostname> commands return the same IP Address. 45 Type cd /NSMR11/DVD/Linux and press ENTER. 46 Type ls -lart setupNSM and press ENTER. The command output should be similar to the following: -r-xr-xr-x 1 root sys 4111 Oct 7 2005 setupNSM Note: setupNSM is the file to launch the installation and must have execute (x) permission. If the first part of the command output is not the same as the previous example, you may need to change the file permissions.
Change File Permissions

47 Type chmod 555 setupNSM and press ENTER. 48 Type ls -lart setupNSM and press ENTER. Note: setupNSM now has the execute (x) permission.
Notes
2-40
Install the Linux System Agent

49 Type ./setupNSM and press ENTER. Note: There will be a short delay while the installation initializes, and then the Unicenter NSM Installation dialog will appear. 50 Select Installation Wizard for Unicenter NSM and click Install. 51 Scroll to the bottom of the End User License Agreement and click I agree. 52 Select the Custom install option and click Next. 53 On the Component Selection screen, clear Express Install. 54 Expand the Agent Technologies folder. 55 Select the Linux System Agent and click Next. 56 Accept the default file locations and click Next. 57 At the Update Login Profiles screen, select the Yes option and click Next. 58 At the Start Unicenter NSM After Installation screen, select the Yes option and click Next. 59 At the Start Unicenter NSM During System Restart screen, select the Yes option and click Next. 60 At the Select Agent Common Services Owner screen, confirm that the Owner is root and click Next. 61 At the Enable Adaptive Configuration screen, select the Yes option and click Next. 62 At the Selection Summary screen, click Next. 63 Click Install to start the installation process. 64 At the Installation Complete screen, click OK.
Notes
2-41

Initialize the Installed Environment

65 Select Actions Log Out. 66 Select Save current setup and Restart the computer and click OK. 67 Type root in the Username field and press ENTER. 68 Type password in the Password field and press ENTER.
Verify Successful Installation

69 In the terminal window, type export and press ENTER. Scroll to the top of the returned list and observe the environment settings that the install established. 70 Type awservices list and press ENTER. You should see the following output: RUNNING aws_orb:aws_orb RUNNING aws_agtgate:aws_ agtgate RUNNING aws_sadmin:aws_ sadmin RUNNING aws_baseline:aws_ baseline RUNNING aws_caiUxsA2:aws_ caiUxsA2 71 Select File Close Window to close the terminal window.
Perform the following steps on your host: Discover the Linux Server
72 Type dscvrbe -7 USxxyyzzV3 and press ENTER. 73 Launch the MCC and drill down to the classroom network segment. 74 Verify that the Linux server is classified correctly. 75 Verify that the DSM discovered the Linux System Agent.
Notes
2-42
Task Summary
In this task, you examined the resources that are monitored by the Linux System Agent. You also reviewed the generic procedure for installing the Linux System Agent. The Linux System Agent provides comprehensive monitoring and management of the UNIX or Linux OS environment and is based on a completely redesigned management information base (MIB) and DSM or Agent View policy. The agent monitors a richer set of metrics and implements a series of new features and functionality that improve its usability and flexibility. In the next task, you will verify active DIA connections.
Notes
2-43

Task 5: Verify Active DIA Connections
Slide 2-18
Task 5: Verify Active DIA Connections

DIA provides a unified data transport mechanism for accessing Unicenter NSM through firewalls using a single port. It also provides a standard interface to obtain data from different Unicenter NSM sources. It acts as a generic mechanism, which dynamically deploys the necessary files to facilitate the correct monitoring of a given system. To view this information, components of DIA must be deployed on the computers where these components are located.
Slide 2-19
A Unicenter Knowledge Base (UKB) is the central location for information on the IT infrastructure being monitored. The UKB is responsible for:

Routing requests to the correct locations. Performing proxy and port brokering tasks for nodes located behind firewalls. This supplies a fully abstracted view of all Unicenter NSM data to the end user. Extending the functionality of Unicenter NSM while reducing management points.
A Master Knowledge Base (MasterKB) coordinates and updates changes to all UKBs in the DIA zones. DIA zones are logical entities or groupings of managed hosts within the DIA grid. A MasterKB must be set up prior to other component configurations. Rules set in the MasterKB assign UKBs to DIA zones. During a DNA registration, the MasterKB assigns the DNA node to one of the UKBs in the DIA zone.
Task Purpose: Verify active DIA connections. 1 2 3 Open a command prompt. Type diahosts and press ENTER. The command output displays all UKBs and registered DNA nodes for each UKB. Open the C:\Student\UR215 folder. Execute the diatool.bat file.
Notes
2-44
Provide the credentials of a user that is a member of the local host administrators group: User: administratorzz Password: usxxyyzzcai
5 6
Click Yes to acknowledge the disclaimer. Expand Default. Verify that the Host and Virtual Windows Server 2003 are in the Default Zone Knowledge Base.
Task Summary
In this task, you verified active DIA connections. DIA provides a central location to manage all components and aspects of a network. The Unicenter knowledge base is the central communication and management point for DIA. A MasterKB coordinates and updates changes to all knowledge bases in the zones. For example, if a knowledge base gets a new managed node, the MasterKB notifies other knowledge bases in that zone about the new node. The Unicenter knowledge base zone is assigned by rules set in the MasterKB. In the next task, you will verify MCC provider connections.
Notes
2-45

Task 6: Verify MCC Provider Connections
Slide 2-20
Task 6: Verify MCC Provider Connections

When monitoring an enterprise such as RBC, you will use the MCC, which is made possible by the Global Catalog. In this task, you will discover that the Global Catalog maintains information about the availability and location of key Unicenter NSM management components such as WorldView, MDB, DSMs, and Event. You will find that if additional Unicenter NSM management servers are deployed and point to the Global Catalog, Local Catalogs are deployed on those servers. You will be introduced to the commands used to maintain catalogs. You will also become familiar with managed object properties and how to access them. The MCC provides a central, standardized console for all management tasks. The entire network infrastructure can be visualized, monitored, and configured from this primary Unicenter NSM administration GUI. The Global Catalog installation can be independent or combined with additional Unicenter NSM components. If additional Unicenter NSM management servers are deployed and point to the Global Catalog, then Local Catalogs, or replicas, are deployed on those servers.
Notes
2-46
Install Unicenter Components Identify Management Components in the Catalog Structure
Slide 2-21
Identify Management Components in the Catalog Structure

In the scenario shown in the following graphic, the Global Catalog is located on Server 0. WorldView is installed on Server A. A Local Catalog is created on Server A, and the WorldView local namespace is published to the Global Catalog.
Slide 2-22
Notes
2-47

Identify Management Components in the Catalog Structure A DSM and Event Manager are installed on Server B. A Local Catalog is created on Server B. The DSM and Event Manager local namespaces are published to the Global Catalog, as shown in the following graphic:
Slide 2-23
Notes
2-48
Install Unicenter Components Identify Commands to Maintain Catalogs
Slide 2-24
Identify Commands to Maintain Catalogs

The Unicenter NSM Installation Wizard creates the Global and Local Catalogs during the installation of Unicenter NSM components. However, it might be necessary to rebuild and republish catalogs manually. Catalogs have different types of wrappers that group information. Based on the command being issued, certain wrappers will be created or updated. The SHOWCAT utility displays the contents of a catalog. This command can be run on a Local Catalog or a Global Catalog. SHOWCAT is useful for troubleshooting the catalog when a Unicenter NSM management component does not appear in the MCC. SHOWCAT can also be redirected to an output file: SHOWCAT > CATALOG.TXT
Notes
2-49

Identify Commands to Maintain Catalogs The commands in the following table are executed automatically during the Unicenter NSM installation. They can also be used to create new catalogs manually or to modify existing catalogs. Command CREATECAT Description The CREATECAT command creates a new catalog. This command deletes the existing catalog and builds a new one. When a catalog is first created by CREATECAT, three wrappers are created:

catadmin rmiWrapper SystemAdmin
TNDADDNSP
The TNDADDNSP command is used to take inventory of the Unicenter NSM management components installed on the local computer and create a wrapper for each component. The TNDMASTERCAT command is used to designate the Global Catalog. It creates or updates the MasterCat wrapper and determines if the catalog is a Local Catalog or a Global Catalog. A Global Catalog is defined as the computer in the MasterCat wrapper. When this command is issued, the computer host name or IP Address of the Global Catalog must be specified. TNDMASTERCAT (GlobalCatalog)
TNDMASTERCAT
Notes
2-50
Install Unicenter Components Access Managed Objects and Properties
Command TNDPUBLISH
Description The TNDPUBLISH command updates the Global Catalog with information about Unicenter NSM management components installed on the local computer. Wrappers for these components are created with the TNDADDNSP command. TNDPUBLISH publishes components to the Global Catalog. SYNCHCAT updates the Local Catalog so the MCC can access these components. The TNDUNPUBLISH command removes previously published entries from the Global Catalog. A new Global Catalog is populated using TNDREPUBLISH. This combines the TNDMASTERCAT, TNDPUBLISH, and TNDUNPUBLISH commands into a single command. Type the command and designate the server name of the new Global Catalog. The new Global Catalog will be updated. TNDREPUBLISH (GlobalCatalog)
TNDUNPUBLISH TNDREPUBLISH
Slide 2-25
Access Managed Objects and Properties

Every managed object is derived from the ManagedObject class or a subclass of ManagedObject. You can view the values of a managed object by selecting Properties in the right pane of the MCC. Each of the tabs corresponds to a property group for the class. Each field represents a property. The number of tabs that appear depends on the class definition of the object. The Name and Label of the managed object appear on the Main tab. The label can be changed for existing objects, but the name cannot. When creating a new object, the name and label must be entered. You can edit class- and instancelevel properties for a managed object using the Class Editor in the right pane of the MCC.
Notes
2-51

Access Managed Objects and Properties
Note: See Module Discover System and Network Devices, for examples of adding and editing properties. Tab Main Purpose This contains the Universally Unique Identifier (UUID), Location, Description, Contact, IP Address, Alarmset, Interface Type, Date Installed, and Last Date Modified. This shows the Status, Severity, and Admin Status. Other options are available, such as Hidden, Propagate, Posted, and Acknowledge. This is used to enter comments about a specific managed object. These comments appear by clicking the appropriate 2D Map object. This provides read-only interface information about a managed object. Information on this page is provided by the system and cannot be modified. This displays read-only parent and child information for the managed object. This provides read-only link information for a managed object. This enables a specific image file, such as an icon, to be used for this object, which overrides the class definition.
Status
Comments
Interface
Inclusion Link Images
Notes
2-52
Tab SNMP
Purpose This contains the Pollset, System Object Identifier (MIB), and SNMP get and set community names for this managed object. This is a catch-all page that displays instance-level properties not assigned to a group or tab.
Others
Task Purpose: View the Topology tree structure and validate managed object properties. In this demonstration, you will explore the MCC Topology view, use drill down procedures to view DSM Manager and agent status, and confirm accurate device classification using managed object properties. 1 2 3 Click Start and then choose Programs Computer Associates Unicenter NSM Management Command Center. In the left pane, expand YourServerName. Expand ManagedObjectRoot, select TCP/IP Network, expand each subnet until you reach your local network segment, and select YourServerName. In the right pane, click Explore View of Worldview. The context will change to Explorer View of YourServerName. Select Properties from the view type list and verify the Name, Address, and Class Name properties of the object. In the left pane, right-click YourServerName and choose Drill Down. Right-click YourServerName-Unispace and choose Drill Down. After the managed objects appear, right-click Windows System Agent and choose Actions View Node.
4 5 6 7 8
Notes
2-53

Interactive Demonstration 9 In the Unicenter - Node View dialog, right-click Windows System Agent and choose View Agent. The Agent status appears.
10 Close the Agent View - Summary dialog. 11 Close the Unicenter - Node View dialog.
Task Summary
This task showed you the purpose of Global and Local Catalogs in Unicenter NSM. You were introduced to the commands used to maintain catalogs. You discovered how to access the MCC, drill down to view management components, and view managed object properties.
Notes
2-54
Install Unicenter Components Assessment
Assessment
1 Which consumer of DIA accessible management information gathers and distributes agent profiles through DIA? a b c d 2 MCC DSM UCM Unicenter NSM r11.x Agents
What are two ways by which the Master Knowledge Base is identified? (Choose two.) a b c d e The DNS Locally registered DNA The host name of a UKB An entry in the dna.cfg file The presence of a Service Location _grid record
When applying Collation Settings, the SQL Collations parameter must be changed to what? a b c d No sort order Strict Compatibility Dictionary order, case-sensitive Dictionary order, case-insensitive
Notes
2-55

Assessment 4 In Network Libraries, what should the port be for TCP/IP Sockets? a b c d 5 80 1433 1600 8080
What must be selected during MS SQL Server 2000 installation to help ensure communication through routers? a b c d Named Pipes Banyan Vines TCP/IP Sockets NWLink IPX/SPX
How many conceptual layers comprise the Unicenter NSM architecture? a b c d Two Five Four Three
The Real World Interface consists of tools to access which part of Unicenter NSM? a b c d MDB DSM Agent layer Enterprise Management
Notes
2-56
Which component stores the class definitions and managed objects for Unicenter NSM? a b c d MDB Agent Real World Interface Enterprise Management
Which application supports network management by gathering information from the enterprise through remote access monitoring and control resources? a b c d Agent Ingres Server WorldView Manager Enterprise Management
10 Which layer of the Unicenter NSM architecture can be used to implement security, automate storage, schedule jobs, and control events? a b c d Manager layer WorldView layer Unicenter NSM layer Unicenter NSM Agent layer
Notes
2-57

Assessment 11 What are the two prerequisites required to install the MCC? (Choose two.) a b c d JRE Ingres Client software Windows XP Professional Java 2 Compliant Operating System
12 For which two parameters does the Linux System Agent monitor status, event, and configuration information? (Choose two.) a b c d e Install media Swap file activity User-defined policies Disk space availability Java GUI installations
13 For which three tasks is the UKB responsible? (Choose three.) a b c d e Assigning the DNA node Routing requests to the correct locations Coordinating and updating changes to all UKBs Performing proxy and port brokering tasks for nodes located behind firewalls Extending the functionality of Unicenter NSM while reducing management points
Notes
2-58
14 What coordinates and updates changes to all knowledge bases in the zones? a b c d DIA DNA MasterKB Unicenter knowledge base
15 When additional Unicenter NSM management servers are deployed and point to the Global Catalog, what is deployed on those servers? a b c d Local Catalogs Managed objects SHOWCAT utility Managed object properties
16 Which utility is useful for troubleshooting the catalog when a Unicenter NSM management component does not appear in the MCC? a b c d SHOWCAT CREATECAT TNDPUBLISH TNDMASTERCAT
Notes
2-59

Assessment 17 Which Unicenter NSM component is used to view and modify the values of managed object instance-level properties? a b c d MCC Local Catalogs Global Catalogs SHOWCAT utility
Notes
2-60
Install Unicenter Components Module Summary
Slide 2-26
Module Summary

Establish the Required DNS Service Location Record Install Unicenter NSM Describe Unicenter NSM Architecture Install the Linux System Agent Verify Active DIA Connections Verify MCC Provider Connections
Unicenter NSM solutions help you sustain an optimized, on-demand infrastructure, maximizing RBCs IT investment by continuously assessing and self-managing network and systems elements. In this module, you established the DNS Service Location Record and then performed a Unicenter NSM installation. You also examined the Unicenter NSM architectural components and their functions. In addition, you learned how to install the Linux System Agent. You also verified active DIA connections and, lastly, you examined how to monitor your enterprise with the MCC. In the next module, you will configure systems monitoring.
Notes
2-61

Module Summary
Notes
2-62
3
3-1

Module Objectives
Slide 3-1
Module Objectives

Configure OS Agents Optimize the DSM Manager for Systems Monitoring Apply URM to Custom Unicenter NSM Environments
Module Overview
To facilitate comprehensive and integrated network polling and administration, Unicenter NSM uses Agent Technology to monitor the status of enterprise resources, determine when status changes occur that require attention, and report these status changes to Unicenter Event Management so that corrective action can be automatically initiated. Agent Technology agents monitor and report the status of your resources and applications to their manager, the Distributed State Machine (DSM). The DSM determines if the reported status indicates that a state change has occurred. The DSM reports state changes to Unicenter Event Management. The DSM maintains a managed object representing each monitored resource. The managed object has properties that identify, among other aspects, the last known state and DSM polling requirements for that object. In this module, the processes involved in monitoring system resources will be explained. Several demonstrations will guide you through the steps required to configure OS agents with the Agent Browser, ADS, Unicenter Configuration Manager (UCM), and Adaptive Configuration. You will also be shown how to optimize the DSM Manager for systems monitoring and how to apply Unicenter Remote Monitoring (URM) to Unicenter NSM environments. All these tools will help save time and enable you to monitor the systems at RBC more effectively.
Notes
3-2
Configure Systems Monitoring Task 1: Configure OS Agents
Slide 3-2
Task 1: Configure OS Agents

Agents monitor critical computing resources. Management information is collected on monitored resources and distributed to Unicenter NSM managers that interpret the data and take action based on custom configurations. Monitored resources, such as processor and memory, are referred to as instances of the agent.
Slide 3-3
Agents can be grouped into three categories:

Operating system Database Application
An agent is an application that resides on a managed node, such as a server or workstation. An agent:

Communicates with the manager. Provides a simple and standardized view of monitored data. Does not affect the monitored resources by its presence.
The primary manager to communicate with agents is the DSM. Information that is exchanged between the DSM and agents is classified into two categories:

Poll: requests by the DSM to the agent Trap: unsolicited messages from an agent to the DSM
To communicate with monitored resources, the DSM and agents must share a common protocol and communicate on a common basis by way of the MIB. Each agent has an MIB that contains the attributes of the component for which it is responsible. The manager must have the complete information base of the entire network to perform its task. Therefore, all MIBs that are present on agents must be available on the managing system.
Notes
3-3

Configure Agents with Agent View, Adaptive Dashboards, or the MIB Browser
Slide 3-4
Configure Agents with Agent View, Adaptive Dashboards, or the MIB Browser
Agents residing on managed nodes in the network are typically configured from remote workstations using administrative tools, such as Agent View, Adaptive Dashboards, or the MIB Browser. Agent View and Adaptive Dashboards provide a visually intuitive view of the aggregate statuses of the monitored resources with their sub-statuses, monitoring conditions, and monitoring levels. You can create resource watchers, modify the monitoring conditions of existing watchers, or delete watchers using these tools. In this way, you can customize the agent configuration on a specific server. You can also use this configuration for other, similar servers by importing it as a Base Profile into UCM, and then distributing it as required. The MIB Browser acts on the logical structure of a specified MIB. It does not provide a visually intuitive view of the agent, so it is rarely used as a configuration tool, although it can be. It does enable you to see the actual hierarchical MIB structure which is sometimes useful. Agent configuration changes made using these tools take effect immediately without the need for a restart. This is convenient if you are testing various configurations. If you change the configuration of an agent during runtime with one of these applications, those changes take effect immediately and remain in force until the attribute values are reset. If you stop and restart the agent with no configuration set in use, your runtime changes persist. However, if you start the agent with a configuration set read from the SNMP Administrator Store, changes made online during the agent's last execution are not restored.
Notes
3-4
Configure Systems Monitoring Tune Threshold Values with the Agent Browser
Slide 3-5
Tune Threshold Values with the Agent Browser

OS agents monitor the general health of the operating system for the server on which they are installed. These agents monitor system resources, such as memory, CPUs, files, logical drives, and so on. Examples of OS agents are the Windows 2003 System Agent, the Windows 2000 System Agent, and the UNIX System Agent. Some of the parameters you monitor using OS agents are:

Processes critical to the system. Failed logon attempts. An unexpected rapid growth rate of a file, such as a log file receiving a large number of error messages. Files containing sensitive information.
Agents monitor only those resources they are configured to monitor. By default, OS agents and database agents monitor a small number of resources. Therefore, you will need to configure agents to monitor additional resources. Agent View, also called the Agent Browser, is the primary tool used to configure agents. Agent configuration is commonly referred to as agent instrumentation. Agent View is available for all Unicenter NSM agents and is very intuitive by nature. After you complete a few types of tasks using Agent View, you can often determine how to perform other tasks due to the intuitive design. To launch Agent View, right-click an agent and choose View Agent. Agent View is launched in a context-sensitive fashion. If the View Agent option is selected from a monitored resource group or a monitored instance context menu, Agent View opens displaying only the item selected and any items under it. For specific details about configuring each instance of the Microsoft Windows agents, refer to Understanding Resources Monitoring in the runtime operation guide, Inside Systems Monitoring.
Notes
3-5

Define Windows System Agent
Slide 3-6
Define Windows System Agent

The Windows System Agent monitors the availability and status of Microsoft Windows resources in an enterprise. The Windows System Agent queries a host for data on its system resources, for example, CPU, memory, and logical volumes. This data is compared with thresholds to determine the system status. The following table provides an overview of the monitoring functions: Resource Group CPU Definition CPU watchers indicate the total usage of all CPUs and the utilization of each CPU. They monitor the following metrics:
Load Queue length Loss
Memory
Memory watchers monitor real memory utilization of the following metrics:

Virtual memory Physical memory Paging memory
Notes
3-6
Configure Systems Monitoring Define Windows System Agent
Resource Group Logical Volumes
Definition Logical volume watchers monitor the following metrics:

Size Size Delta Throughput Average queue length Total fragmentation File fragmentation Cluster type Loss of a logical volume
Mounts
A mount in the Microsoft Windows OS is a dedicated directory pointing to a logical volume. Mounts are used to merge several logical volumes into a common namespace. To help ensure the integrity of this namespace, no unexpected changes concerning the mounts must occur. Mount watchers monitor the following metrics:
Targets (logical volumes) Loss of a mount Cluster type
DFS links
Distributed File System (DFS) watchers monitor the number of unavailable targets of a DFS link and the loss of a DFS link. Quota watchers monitor the quota size usage, in percent or KB, and the loss of a quota entry.
Quotas
Notes
3-7

Define Windows System Agent Resource Group Directories Definition Directory watchers monitor a directory with or without including all recursively contained files and subdirectories. A directory watcher monitors the following resources:
Number of entries Size (in percent or KB) Size Delta (in percent or KB, as +, -, or +/-) Timestamp Existence of a directory
Files
File watchers monitor a single file or a set of files (one-to-many watcher) that is defined by a filter condition on the file name, not the path. A file watcher monitors the following resources:
Number of instances Size (in percent or KB) Size Delta (in percent or KB, as +, -, or +/-) Timestamp
Notes
3-8
Resource Group Processes
Definition A process watcher monitors a single process or a set of processes (one-to-many watcher) that is defined by a filter condition on the name, path, and user of the processes. A process watcher monitors the following resources:
Number of instances Memory size CPU usage Number of threads (Miscellaneous Mode) Number of handles (Miscellaneous Mode) Number of children (Miscellaneous Mode) Runtime (Miscellaneous Mode) Restart Cluster type
Services
A service watcher monitors the following metrics:

Configuration change Activeness Existence Cluster type
Notes
3-9

Define Windows System Agent Resource Group Jobs Definition A job is a set of processes that is handled as a process group. A job watcher monitors the following metrics of a job:
Processes Memory size (KB) CPU usage Loss
Sessions
A session watcher monitors the following metrics of a single session or a set of sessions:
Number of instances CPU usage Memory size (KB)
Printers
A printer watcher monitors the following metrics of local printers connected to the system:
Events raised by the Microsoft Windows Printer
Manager
Length of the print queue Loss of a printer
Notes
3-10
Resource Group Network Interfaces
Definition A network interface watcher monitors metrics concerning the received and sent traffic and can detect the loss of an interface, for example, caused by a dropped cable. Network interface watchers are created automatically and cannot be deleted. They monitor the total network interface use across all network interfaces and the individual network interfaces:
In Packets/Out Packets per second In Bytes/Out Bytes per second In Errors/Out Errors per poll Operational status Loss of individual network interfaces
Registry Monitoring
A registry entry is defined by its complete path in the Microsoft Windows registry. A registry entry watcher monitors the following metrics:
Value (data) Any changes in the subtree Existence of a registry entry
Hardware Resources
A hardware resource watcher monitors hardware components by using external scripts or applications. They monitor hardware properties, such as system temperature, power supply status, and fan status.
Notes
3-11

Define Watchers and Metrics
Slide 3-7
Define Watchers and Metrics

Watchers and metrics are essential entities to monitor IT resources. An agent monitors IT resources on the basis of configured watchers. A watcher is the term used for any instance of a monitored resource added to the agent configuration. The agent evaluates the status of a specific resource according to the assigned watcher configuration. Usually, a watcher consists of a set of metrics, or thresholds, which are compared to the detected values of monitored resources. The result of this comparison is the status of the monitored resource according to the metric settings. The status of the watcher is the worst case aggregate of all associated resource statuses. If the aggregate status of a watcher changes, an info-trap is sent to the manager. The info-trap contains information about the monitored resource that caused the status change. Two basic watcher types can be distinguished:
One-to-one watcher: A watcher is mapped to a single resource that will be monitored. Characteristics of the monitored resource are evaluated by appropriate metrics. For example, a file system is monitored by a single watcher and different metrics are used to detect the status of file system characteristics, such as size. One-to-many watcher: A watcher is mapped to a set of resources, or instances, that will be monitored. Common characteristics of these instances are evaluated by appropriate metrics. Unlike the one-to-one watcher, a culprit list is provided to identify those instances that cause a status change of the watcher. For example, processes or files can be monitored by one-to-many watchers.
The evaluation policy defines how metric values, statuses total values, and culprit lists of monitored instances are calculated for one-to-many watchers. A monitored instance appears in a culprit list (IDs) if it violates a threshold condition that is enabled (equal or greater than 0), regardless of the monitoring level settings.
Notes
3-12
Configure Systems Monitoring Define Watchers and Metrics
The culprit list is sorted in descending order for rising thresholds and in ascending order for declining thresholds. The total value of the monitored instance depends on the evaluation policy setting and is set at the creation time of the watcher. Valid evaluation policy values are as follows:
Individual: Each monitored instance is compared individually to the defined thresholds of the metric. The total value is the largest value of all monitored instances. Minimum: The instance with the smallest value of all monitored instances is compared to the defined thresholds of the metric. If a threshold condition is violated, the culprit list consists of instances with the smallest value. The total value is the smallest value of all monitored instances. Maximum: The instance with the largest value of all monitored instances is compared to the defined thresholds of the metric. If a threshold condition is violated, the culprit list consists of instances with the largest value. The total value is the largest value of all monitored instances. Sum: The agent calculates the sum of the values of all monitored instances and compares it to the defined thresholds of the metric. If a threshold condition is violated, the culprit list consists of all monitored instances. The total value is the sum of the values of all monitored instances. Average: The agent calculates the average of the values of all monitored instances and compares this average to the defined thresholds of the metric. If a threshold condition is violated, the culprit list consists of those monitored instances that violate the threshold condition. The total value is the average of the values of all monitored instances.
Notes
3-13

Task Purpose: Monitor resources with the Windows System Agent and customize it to meet specific system requirements.
Monitor the CPU

1 2 3 4 5 6 7 Open the MCC and navigate to YourServerName. Drill down to the Windows System Agent, right-click, and choose Actions View Agent. The Agent View - Summary window opens. Choose View CPUs. The Agent View - CPUs window opens. Click P next to CPU Total. The CPU Total - Dashboard window opens. Click Configure. The Configure CPU Total dialog appears. Change Warning Maximum to 60 and Critical Maximum to 75. Keep the minimum levels at -1. Click OK. Close the CPU Total - Dashboard window.
Monitor Memory
8 9 From the Agent View - CPUs window, choose View Click Properties. Memory.
10 Click Configure. The Configure Memory Watcher dialog appears. 11 Set the Warning threshold to a value substantially less than the amount of physical memory in use. If the amount in use is 85%, change the setting to 10% and click OK. 12 Close the Configure Memory Watcher dialog. 13 From the Agent View - Memory screen, click Change. The Poll Memory Watchers dialog appears. 14 Change the Poll Interval to 30 and the Lag to 1. Click OK. The new settings cause the agent to go into a Warning state.
Notes
3-14
Configure Systems Monitoring Interactive Demonstration
15 Return the Warning threshold percentage to its default.
Monitor Directories
16 From the Agent View - Memory window, choose View 17 Click New. The New Directory Watcher dialog appears. 18 Type Temporary Directory in the Watcher Name field. 19 Type C:\Temp in the Directory Name field. 20 In the Aggregate Lag field, type 1. 21 From the Size/Monitor list, select Do Not Monitor. 22 In the Size Delta field, type 5 for Warning and 10 for Critical. 23 From the Size Delta/Scale list, select Percent +. 24 From the Size Delta/Monitor list, select Both and click OK. 25 Click Change to edit the poll interval. Type 30 and click OK. Note: Poll intervals are customized for each environment. Thirty seconds is often too short for normal circumstances. 26 Click OK. Directories.
Verify the Solution

27 Open Microsoft Windows Explorer. 28 Drill down into the C:\Student\UN277 folder. 29 Select all files, right-click, and choose Copy. 30 Drill down into the C:\Temp folder. 31 In the right pane, right-click and choose Paste.
Notes
3-15

Interactive Demonstration 32 Return to the Agent Browser. Click the P button beside the Watcher Name. The Directory watcher must display Critical status for Size Delta. 33 Click the Reint button. The Directory watcher returns to a Normal state. Note: Size Delta will reinitialize monitoring for growth based on the provided values.
File Watcher
The following steps demonstrate how to use a Regular Expression to monitor multiple files. 34 In Microsoft Windows Explorer, copy the C:\Program Files\CA\Shared Components\CCS\DIA\dia\dna\config folder address. 35 On the Agent View - Summary window, click Files. The Agent View Files window opens. 36 Click Change. The Change File Polling dialog appears. 37 Type 30 in the Poll Interval (Seconds) field and click OK. 38 Click New. The New File Watcher dialog appears. 39 Type Config Files in the Watcher Name field. 40 Paste the C:\Program Files\CA\Shared Components\CCS\DIA\dia\dna\config folder address before .* in the File Name field. Type \ after config. 41 Type 9 in the Instances Minimum and Maximum fields. 42 From the Instances Monitor list, select Down Critical and click OK. 43 Click New. The New File Watcher dialog appears. 44 Type DNA Config in the Watcher Name field. 45 Paste the C:\Program Files\CA\Shared Components\CCS\DIA\dia\dna\config folder address in the File Name field. Type \dna.cfg after config.
Notes
3-16
46 From the Size Monitor list, select Do Not Monitor. 47 From the Size Delta Monitor list, select Do Not Monitor. 48 Type 1 in the Instances Warning Minimum and Maximum fields. 49 From the Time Monitor list, select Down Warning. 50 Click OK. 51 In Microsoft Windows Explorer, open the C:\Program Files\CA\Shared Components\CCS\DIA\dia\dna\config folder. 52 Right-click the dna.cfg file and select Send To NOTEPAD.EXE. 53 In the text editor, scroll to the bottom, type #Comment, and press ENTER. Save your changes and close the dna.cfg file. 54 Create a new text document, name it TEST.TXT, and save it to the C:\Program Files\CA\Shared Components\CCS\DIA\dia\dna\config folder. 55 Return to the Agent View - Files window. Click P to open the DNA Config watcher dashboard. 56 Click Details to view the DNA Config watcher details. The Time Status icon displays a Warning state. 57 Click Reset Time. The Reset File Time Property dialog appears. 58 Click OK. 59 After the time resets, close the File Watcher - Details window. 60 Click P to open the Config Files watcher dashboard. 61 Click Details to view the Config Files watcher details. The Instances Status icon displays a Critical state. The number of files in the directory, 10, now exceeds the minimum and maximum, 9. 62 Close the File Watcher - Details window. 63 Delete the TEST.TXT file.
Notes
3-17

Interactive Demonstration 64 Refresh the Agent View - Files window to observe the file watchers change status.
Monitor Services
65 Select the Services view, and click List. 66 Choose View Available Objects. 67 Find and select the Spooler service, and click Add. The New Service Watcher dialog appears. 68 From the Active list, select Down Critical. 69 Type Print Spooler in the Description field. 70 From the Configuration/Monitor list, select Down Critical. 71 Click OK. 72 Close the Available Services window. 73 Click Change. 74 Type 30 in the Poll Interval field. 75 Click OK.
Verify the Solution

76 At a command prompt, type net stop spooler and press ENTER. 77 Return to the Agent Browser and wait for the next 30 second poll.
Reset the Agent

78 At a command prompt, type net start spooler and press ENTER.
Notes
3-18
Configure Systems Monitoring Skill Practice
Skill Practice
Task Purpose: Tune threshold values of the Windows System Agent to send alerts. 1 2 3 4 5
Slide 3-8
Create a watcher for the Messenger service that will send a Warning alert when the service fails. Implement steps 63 to 73, Monitor Services, in the previous interactive demonstration. Select Messenger instead of Spooler. Select a Warning for Alert status. Use the net stop messenger command to verify correct configuration.
Define Trap Destinations

While discovering the network, Unicenter NSM automatically sets the correct trap destination on the discovered nodes so the traps are automatically sent to the associated manager. There is no need to configure the SNMP Administrator for such standard trap destinations manually, however it can be done if you must meet specific requirements. To modify the default trap destination policy manually, edit the \ProgramFiles\CA\SharedComponents\CCS\AT\Services\CONFIG \AWS_SADMIN\AWS_SADMIN.CFG file. This text file is self-documenting. You can define multiple trap destinations. To put the new policy into effect, stop and restart Agent Technology Services on the node. In the aws_sadmin.cfg file, the trap destination has the following format: SNMP_TRAP [host or ipAddr] | [port]
Notes
3-19

Interactive Demonstration The actual trap destination entry in the configuration file consists of the following information:

Type: identifies the type of entry being specified Host: identifies the network destination for the trap and can be a resolvable host name or an IP address Port: receives the trap at its destination and remains as IP port 162
Task Purpose: Configure agents to send traps to the DSM Manager using the Agent Browser. Note: When the DSM first discovers an agent node, it adds its IP Address to the SNMP Administrator's dynamic trap destination list if one of the five slots is available. When the DSM is colocated on the agent node, it does not need to add its IP Address to the list since the aws_sadmin.cfg file already specifies the required trap destination using the loopback address (127.0.0.1). 1 2 3 4 In the MCC, drill down to your local host and locate the AWsadmin object. Right-click AWsadmin and choose Actions View Agent. From the SNMP Administrator View - Summary window, choose View Trap Destinations. From the SNMP Administrator View - Trap Destinations dialog, type the IP address of your DSM server in the Trap Destination field and click Add. Close the SNMP Administrator View - Trap Destinations dialog.
In the next interactive demonstration, you will configure agents to send traps using the aws_sadmin.cfg file.
Notes
3-20
Task Purpose: Configure trap destinations by editing the aws_sadmin.cfg file.
Open the SNMP Admin Configuration File

1 In Microsoft Windows Explorer, open the C:\Program Files\CA \SharedComponents\CCS\AT\SERVICES\CONFIG\AWS_SADMIN folder. Open the aws_sadmin.cfg file in Notepad.
Update the Trap Destination

3 4 5 In the open file, scroll down until you see the following line: SNMP_TRAP 127.0.0.1|162 # traps to localhost Change the trap destination to YourServerName or the IP address of the DSM server. Save and close the file.
Implement the Changes

6 7 At a command prompt, type awservices stop and press ENTER. Type awservices start and press ENTER.
Notes
3-21

Skill Practice
Skill Practice
Task Purpose: Configure the Microsoft Windows 2003 server VMware session to send traps to the DSM server. 1 2 Use one of the methods detailed in the previous interactive demonstrations. Confirm the traps are reaching the DSM server. If not, configure a correct trap destination.
Hint:
You can confirm the receipt of a trap by forcing a Critical status for an Agent watcher on the VMware session. If the Critical status immediately appears on the Nodeview display of the VMware session host, this indicates that the trap was received.
Slide 3-9
Tune Threshold Values with ADS

ADS create personalized management views of Unicenter NSM components through a web-based interface. This includes customized and preconfigured dashboards for Unicenter NSM agents.
Dashboards
Dashboards are a user-customized, consolidated view of enterprise management information provided by Unicenter NSM products through secure web-based interfaces. A dashboard provides:

A high-level general health view of the enterprise. A diagnostic view of exceptions that occur in the enterprise. An interface to modify the configuration of watchers, which monitor system resources.
Notes
3-22
Configure Systems Monitoring Dashboards
The following types of dashboards are supported: Dashboard Type Normal, or General Health Exception User-defined (Normal or Exception mode) Server (Normal or Exception mode) Description Provides a continuously updated snapshot of the monitored resource Provides information about only what is wrong in the monitored resource Displays the user-selected data groups of the monitored resource Consolidates data from all agents running on a server
Multi-agent and MultiDisplays data from several agents running on host (Normal or Exception several hosts mode) Access dashboards as right-pane data viewers in the MCC if the Web Reports and Dashboards option has been installed. To view dashboards from the MCC, you must enter the host name of the server running Unicenter NSM Dashboards and the port number used by Tomcat on the Connections tab of the Options dialog. After entering this information, a Dashboard viewer will be enabled for a select set of agent and server nodes in the Topology and DSM View trees. When requesting the first dashboard for each session, you must enter the user ID and password for the Tomcat server on which the Web Reports and Dashboards option has been installed.
Notes
3-23

Task Purpose: Log in to ADS. 1 Select Start Programs Computer Associates Unicenter NSM CA Web Server. Under the CA Applications section, click ADS. Type admin in the User Name field. Type unicenter in the Password field. Click Log In.
2 3 4
In the next interactive demonstration, you will build a server dashboard using ADS.
Task Purpose: Build a server dashboard to provide a high-level graphical representation of real-time data from Unicenter NSM agents. 1 2 3 4 5 6 7 8 9 From the Unicenter Adaptive Dashboard Server, expand Dashboards and select Create Server Dashboard. From the DSM Server list, select YourServerName. From the Show Exception Levels list, select Normal. Click Next. Check Select Hosts for the Host server. Click Publish. Type YourServerName_Dashboard in the View Name field. Click Publish. Collapse and expand the Dashboards tree to refresh. Expand Published Server Dashboards and select YourServerName_Dashboard.
Notes
3-24
10 Right-click YourServerName_Dashboard and choose Reload. 11 Scroll down the Dashboard to observe the monitored instances. In the next interactive demonstration, you will customize an existing server dashboard using ADS.
Task Purpose: Customize the exception level in an existing server dashboard. 1 From the Unicenter Adaptive Dashboard Server, expand Published Server Dashboards and select YourServerName_Dashboard. Select Edit Server Dashboard. Select YourServerName_Dashboard in the Published Documents field. Click Edit. From the Show Exception Levels list, select Warning. Click Next. Confirm YourServerName is selected. Click Publish. Verify the publish information and click Publish.
2 3 4 5 6 7 8 9
10 In response to the Are you sure you want to overwrite the existing one? warning, click OK. 11 Select YourServerName_Dashboard to verify changes. 12 Note the changes when a Manage by Exception practice is employed. Note: You can also use the Agent Browser to create a Warning or Critical state on your host. Note the changes in the server dashboard.
Notes
3-25

Interactive Demonstration In the next interactive demonstration, you will create an agent dashboard with ADS.
Task Purpose: Build an agent dashboard to provide a granular-level presentation of real-time data from Unicenter NSM agents. 1 2 3 4 5 6 7 8 9 From the Unicenter Adaptive Dashboard Server, select Create Dashboard. Select Windows System as the Monitoring Class. In the column labeled New, locate the row that corresponds to the Windows System monitoring class. Click the icon. Type Win2k3_Basic in the Definition File Name field. Clear the Set Default definition option. Clear all selections, and then select CPU, Files, and Memory. Click Save. From the DSM Server list, select YourServerName. From the Show Exception Levels list, select Normal.
10 Select Windows System as the Monitoring Class. 11 From the Select Tiles Definition list, select Win2k3_Basic. 12 Click Next. 13 From the Host List, select YourServerName. 14 Click Publish. 15 Type Win2k3_Agent_Dashboard in the View Name field. 16 Click Publish. 17 Expand Published\Agent Dashboards and select Win2k3_Agent_Dashboard.
Notes
3-26
In the next interactive demonstration, you will customize an existing agent dashboard using ADS.
Task Purpose: Customize the resources displayed in an existing agent dashboard. 1 2 3 4 5 6 7 8 9 From the Unicenter Adaptive Dashboard Server, select Edit Dashboard. Select Win2k3_Agent_Dashboard in the Published Documents field. Click Edit. Select Windows System as the Monitoring Class. Click Edit. Select Network Interfaces. Click Save. Confirm Windows System and Win2k3_Basic are selected. Click Next.
10 Confirm YourServerName is selected in the Host List and click Publish. 11 Verify the publish information and click Publish. 12 In response to the Are you sure you want to overwrite the existing one? warning, click OK. 13 Select YourServerName_Dashboard to verify the changes. In the next interactive demonstration, you will change the policy of an agent dashboard with ADS.
Notes
3-27

Task Purpose: Modify the configuration of monitored resources with the agent dashboard. 1 2 From the Unicenter Adaptive Dashboard Server, expand Published\Agent Dashboards and select Win2k3_Agent_Dashboard. Click the Memory drilldown icon. Note: The drilldown icon is the magnifying glass on the Memory title bar. 3 4 5 6 7 From the Memory Watcher window, click Edit. Type 65 in the Physical Memory Warning field and click OK. Click OK. Click Done. Open the Agent Browser for your host to verify the threshold changes.
Skill Practice
Task Purpose: Create an agent dashboard. 1 2 Create an agent dashboard for the Windows System Agent on Virtual Windows 2003 Server 2. Add the following to the dashboard: 3 4 CPU Memory Network interfaces
Use the agent dashboard to add the DIA_DNA service. Edit the agent dashboard to display the DIA_DNA service.
Notes
3-28
Configure Systems Monitoring Manage Systems with the UCM
Slide 3-10
Manage Systems with the UCM

The UCM simplifies management of agent configurations in the enterprise. The UCM focus is configuring servers, not agents. Configuration can be defined independently of any running agents. The UCM supports the management of agent configuration data in the form of Adaptive Configuration Profiles, Base Profiles, and Differential Profiles. These profiles are stored on a UCM server and can easily be distributed to specific systems in your network on demand or by scheduling, using auditing and security.
Create Base Profiles and Differential Profiles

You can classify computers into groups and assign specific Base Profiles to these groups. For example, you can group all the UNIX or Linux servers and Microsoft Windows servers. For each group, create a Base Profile that contains the typical settings for this type of server. To create a Base Profile, import an existing agent configuration from a managed node in your network and modify this configuration in UCM accordingly. Base Profiles and Differential Profiles contain static agent configuration data. After you load it on a computer, the configuration data does not change unless you modify it manually, for example, through Agent View. If you want to deploy different agent configurations in a group, you can define additional Differential Profiles for particular computers, which consider the special characteristics of these computers, for example, Linux, AIX, HP-UX, or Solaris servers. If a Differential Profile and a Base Profile are associated with a Configuration Bundle for the same resource and Delivery Schedule, the differential will be merged with the Base Profile providing a Final Profile that is delivered to the target host. The merging of the Differential Profile is based on the operations defined in it, such as insert, delete, update, and the content of the Base Profile.
Notes
3-29

Distribute Base Profiles and Differential Profiles
Distribute Base Profiles and Differential Profiles

You can distribute your profiles from UCM to the specified systems. The configuration data is directly loaded into the AWS_SADMIN stores of these systems. The agents run with this configuration unless you change their configuration data manually through Agent View or Adaptive Dashboards.
Task Purpose: Access the UCM Web Client. 1 2 3 4 5 6 Click Start and then choose Programs Computer Associates Unicenter NSM CA Web Server. Under the CA Applications section, click ADS. Type admin in the User Name field. Type unicenter in the Password field. Click Log In. UCM prompts for MDB connection details on initial connection. a If you are using NSM r11 with an Ingres MDB: i ii iii iv Type YourServerName in the MDB Host Name field. Type nsmadmin in the MDB User Name field. Type unicenter in the MDB Password field. Type EI7 in the JDBC Port field.
Note: EI represents the instance name of the database assigned during installation.
Notes
3-30
If you are using NSM r11.1 with a Microsoft SQL Server MDB: i ii iii iv v Select SQL Server in the MDB DBMS Type field. Type YourServerName in the MDB Host Name field. Type nsmadmin in the MDB User Name field. Type unicenter in the MDB Password field. Type 1433 in the JDBC Port field.
Note: 1433 represents the default Microsoft SQL Server instance. If a named instance had been used, you can identify the port using the SQL Server Network Utility. In the utility, select the named instance and view the TCP/IP properties. 7 8 Click Save. Click Log In.
In the next interactive demonstration, you will create a group for a server.
Task Purpose: Create a group for the Virtual Windows 2003 Server 2. A server must be a member of a group to be the recipient of a configuration bundle delivery. 1 2 3 4 5 From the UCM, on the Groups tab, click New Group. Type Win2k3 Servers in the Group Name field. Under the Filter Criteria section, accept the Host Label and like filter options and type us in the Filter field. Click Go. The Available Hosts table will populate. Select Virtual Windows 2003 Server 2 from the Available Hosts table and click the arrow to move it to the Selected Hosts table.
Notes
3-31

Interactive Demonstration 6 7 8 Click Save as Child. In the left pane, expand Monitored Resources Model to see your new server group, Win2k3 Servers. Expand Win2k3 Servers to see its hosts.
In the next interactive demonstration, you will create a baseline Microsoft Windows agent configuration for multiple servers.
Task Purpose: Create a standard baseline Microsoft Windows agent configuration that can be distributed to multiple servers. 1 2 3 4 5 6 7 8 9 From the UCM, select the Profiles tab. Expand Monitored Resources Model and select the Base Profiles folder. Click New Profile. Type Win2k3_Base in the Profile Name field. From the Resource Class list, select caiWinA3. Click Next. Under the Filter Criteria section, accept the Host Label and like filter options and type us in the Filter field. Click Go. The Available Hosts table will populate. Select YourServerName from the table and click Finish.
10 Expand Monitored Resources Model\Base Profiles. Confirm the Win2k3_Base Profile was created. Finally, in the next interactive demonstration, you will create and deliver a configuration bundle.
Notes
3-32
Task Purpose: Build and deliver a configuration bundle. 1 2 3 4 5 6 7 8 9 From the Unicenter NSM Configuration Manager, select the Groups tab. Select the Win2k3_Servers group. Click New Configuration Bundle. From the Resource Class list, select caiWinA3. Click Next. If no file packages need to be added, click Next. Type Win in the Base Profile Name field. Click Go. Select the Base Profile you want from the list of available Base Profiles and click Next.
10 If no differential profiles need to be added, click Finish. 11 Select the new configuration bundle. 12 Click Deliver Now. 13 From the Unicenter NSM Configuration Manager, select the Reports tab. 14 Expand Reports Configured Reports and select the Delivery Status Report. Observe the report in the right pane and note the value in the Deliver Status column. 15 Connect to Virtual Windows 2003 Server 2 with ADS or the Agent Browser, and verify delivery of the new configuration. The Virtual Windows 2003 Server 2 must be monitoring the same instances as YourServerName.
Notes
3-33

Modify Adaptive Configuration Parameters
Slide 3-11
Modify Adaptive Configuration Parameters

A fundamental part of the CA strategy for Unicenter NSM is the elimination, wherever possible, of time-intensive manual tasks on the part of customers. Unicenter NSM Adaptive Configuration sets out to address this need. Due to the extensible and modular design, Adaptive Configuration can be used to discover virtually any computer-based object, such as CPUs, memory, disks, databases, files, network components, and so on. Over time, it can also learn about the usage or load placed on that object to determine its baseline. This information can be used to determine measurements and thresholds that health monitoring agents can use to detect unusual conditions. From a business perspective, such a capability is highly desirable. It greatly eases the deployment of agents and alleviates the need for dedicated, highly skilled, and knowledgeable staff to manually configure the agents. Unicenter NSM Adaptive Configuration provides an intelligent and automated configuration solution for Unicenter NSM agents, thus removing the need for human interaction in the initial and ongoing configuration of these agents. Adaptive Configuration uses a process of automated object discovery and measurement to provide an agent with an initial configuration that will exploit the full monitoring capabilities of the agent, without the need for manual user interaction. The Adaptive Configuration service provides two modes of operation:
Self-configuration: This mode of operation provides rapid and automatic configuration of an agent when it is first deployed to its target environment with no other form of predefined configuration. Adaptive Configuration provides default values for the initial agent configuration. This process takes about three minutes. Self-adaptation: This mode of operation provides ongoing refinement and adjustment of an agent's existing configuration. In this mode of operation, the Adaptive Configuration process is one of refinement and an ongoing learning and training exercise conducted over a number of weeks or months.
Notes
3-34
Configure Systems Monitoring Modify Adaptive Configuration Parameters
A policy controls how Adaptive Configuration meets different requirements:

Early detection (poll interval) opposed to monitoring impact on the computer Early recognition of possible alarm situations opposed to risk of false alarm Complete monitoring (number of watchers) opposed to monitoring impact on the computer
For each agent resource group, individual values are defined that map to three generic policy settings:

Small, Few, Short, or Tolerant Standard Large, Many, Long, or Sensitive
In most cases, these settings are mapped to the following values: Agent Resource Group Poll Interval Lag Setting Threshold Setting (Warning) Threshold Setting (Critical) Threshold Setting (Warning Delta) Small, Few, Short, or Tolerant 60 3 85% 96% 20% Standard Large, Many, Long, or Sensitive 300 30 60% 80% 5%
120 10 70% 90% 10%
Notes
3-35

Identify Objects to Monitor Agent Resource Group Threshold Setting (Critical Delta) Small, Few, Short, or Tolerant 40% Standard Large, Many, Long, or Sensitive 10% 100
20% 30
Watcher Selection 4
Identify Objects to Monitor

You can use the self-adaptation mode to perform a systematic search over all instances of specific monitored resources, for example, files and directories. The search process identifies candidates for file watchers (size, modification date) and directory watchers (number of inodes, modification date). For example, the files must have been modified in the last n (default = 10) days. ModifiedWithinLastDays = 10 For the n biggest or last modified files, n watchers are created. The number n is controlled by one of the following policies: WatcherSelection = standard 30 WatcherSelection = few 4 WatcherSelection = many 100
Notes
3-36
Configure Systems Monitoring Run the Adaptive Configuration Service
The thresholds are derived from the standard deviation over the evaluated values. The Unicenter NSM Adaptive Configuration service uses the :AC: character string as the description for watchers that it creates. If a resource group is enabled for Adaptive Configuration, you can switch the self-adaptation mode on or off for an individual watcher by adding or removing the :AC: character string to or from the beginning of a watcher description.
Run the Adaptive Configuration Service

The Adaptive Configuration service starts automatically in the self-configuration mode after a successful installation. After completing the self-configuration mode, it starts the installed agents that support Adaptive Configuration, such as the UNIX System Agent, the Windows System Agent, or the Active Directory Services Agent and continues with the self-adaptation mode.
Notes
3-37

Run the Adaptive Configuration Service The following graphic indicates an overview of the weekly activities of the preconfigured Adaptive Configuration service as delivered with the product:
Slide 3-12
Notes
3-38
Task Purpose: Create an Adaptive Configuration policy that demonstrates how to exclude an agent instance from monitoring and how to include a resource not monitored by an AutoWatcher. 1 2 3 4 5 6 7 8 9 Open the Unicenter NSM Configuration Manager. On the Profiles tab, expand Monitored Resources Model\Adaptive Configurations. Click New Adaptive Configuration. Type DemoConfig in the Profile Name field. From the Resource Class list, select caiWinA3. Click OK. Expand DemoConfig\Agent Settings\Resources\Net\Policy\Policy Parameters. From the ResourceOn list, select no. Click Save.
10 Expand DemoConfig\Agent Settings\Resources\Dir\Policies\Policy Includes. 11 Click Insert. 12 Check Select and type c:\student in the Name field. 13 Click Save. In the next interactive demonstration, you will create a file package to deliver the Adaptive Configuration policy.
Notes
3-39

Task Purpose: Create a file package to deliver the Adaptive Configuration policy. 1 2 3 From the Unicenter NSM Configuration Manager, select the Profiles tab. Expand Monitored Resources Model\Adaptive Configurations\DemoConfig. Note the value ac/DemoConfig/caiWinA3.xml in the Profile location URL field. This value will be needed in step 10. You can save some time if you copy this value to the Windows clipboard. Select the File Packages tab. Click New File Package. Type New_Adaptive_Config in the File Package Name field. From the Resource Class list, select caiWinA3. Type c:\program files\CA\Shared Components\CCS\AT\Agents\config in the Destination Location field. Click Next.
4 5 6 7 8 9
10 Append the value ac/DemoConfig/caiWinA3.xml to the current value in the Destination Location field so that it appears as follows: C:/Program Files/CA/SharedComponents/Tomcat.ccs/4.1.29/ webapps/wiser/configDocs/ac/DemoConfig/caiWinA3.xml 11 Check Select. 12 Click Finish. In the next interactive demonstration, you will deliver an Adaptive Configuration file package.
Notes
3-40
Task Purpose: Deliver an Adaptive Configuration file package. 1 2 3 4 5 6 7 8 9 From the Unicenter NSM Configuration Manager, select the Groups tab. Expand Monitored Resources Model\Win2k3_Servers. Select the applied configuration bundle. Click Edit. Type New in the File Package Name field. Click Go. Move New_Adaptive_Config from the Available File Packages table to the Selected File Packages table. Click Next. To edit the Base Profile, click Next. To accept the Base and Differential Profiles, click Finish.
10 Select the applied configuration bundle and click Deliver Now.
Notes
3-41

Tune Threshold Values of the Linux System Agent to Send Alerts
Slide 3-13
Tune Threshold Values of the Linux System Agent to Send Alerts

The Linux System Agent monitors status, event, and configuration information for critical operating system parameters, such as CPU utilization, disk space availability, swap file activity, and memory usage. It also monitors important desktop and server operating system resources per adherence to user-defined policy. This agent detects profile deviations and, if necessary, escalates events to Unicenter NSM for appropriate action. The Linux System Agent collects information on basic configuration settings. This information is collected once, immediately after the agent is initialized, and includes:

Node name System name Operating system release Operating system version Hardware details Boot time Run level at start of agent
Notes
3-42
Configure Systems Monitoring Tune Threshold Values of the Linux System Agent to Send Alerts
The following table provides an overview of the monitoring functions: Resource Group System Description The following configuration information about the UNIX or Linux OS environment is collected once at the startup time of the agent:
Node name and OS version information Hardware information, such as kernel mode
and boot mode
Boot date and run level Cluster information Number of processors List of configuration parameters with general
configuration details
OS resource parameters
The number of each of the following monitored OS resource parameters can vary on different UNIX platforms:
Open file descriptors Running processes Logged in users or sessions Used message queue IDs Used semaphore IDs Used shared memory IDs
CPU
The agent monitors the total CPU utilization for all CPUs and also for individual CPUs.
Notes
3-43

Tune Threshold Values of the Linux System Agent to Send Alerts Resource Group Load Description The load averages metrics display the number of processes in the run queue averaged over 1, 5, and 15 minutes. As a general rule, when this queue length persistently exceeds two jobs, the computer is not running as efficiently as possible. The agent monitors real memory utilization and dynamic changes of memory size by the following metrics:
Scan rate as an integer value of scans per
Memory
second (if supported by OS) per second
Page Outs rate as an integer value of page outs Memory utilization as an overloaded
percentage of total memory size modified
Size as an indicator if total memory has been
Typically the best indication of a shortage in Physical Memory is provided by the Scan Rate metric. Swap Swap space watchers are created automatically and cannot be deleted. The agent monitors the total swap space use across all swap spaces as well as the following individual swap spaces:
Total used swap space in KB Total swap space in KB Used individual swap spaces in KB Total individual swap spaces in KB
Notes
3-44
Resource Group Quotas
Description A quota consists of two limits, the hard limit and the soft limit. A user is never permitted to exceed the hard limit. A system-wide soft time limit controls the quotas. After the soft limit is reached, the expiration timer starts. If the timer reaches the soft time limit, the user is unable to allocate space until the use has decreased below the soft limit. A quota watcher monitors the following resources:
Disk space (in KB) Number of inodes Expired disk space (soft limit) Expired inodes (soft limit)
Directories
A directory watcher monitors a set of directories for existence, modification, number of entries, growth rate, and size. A recursive policy specifies if the agent additionally monitors subdirectories and their entries.
Notes
3-45

Tune Threshold Values of the Linux System Agent to Send Alerts Resource Group File systems Description A file system watcher monitors the space available on a mounted file system. This can take on two forms:
The amount of file system or partition space
that is used in comparison with the total amount available. stored on the file system or partition.
The number of files, or inodes, that can be
Additionally, the agent monitors the delta space and delta inodes as well as the mount status, cluster status, and loss status of file systems. The UNIX System Agent monitors all metrics on remote file systems across all platforms. Files A file watcher monitors a set of files for existence (instance monitoring), modification, growth rate, and size. An evaluation policy defines how metric values, statuses total values, and culprit lists for file watchers are calculated. Valid values are as follows:
Individual Minimum Maximum Sum Average
Notes
3-46
Resource Group Disks
Description The agent records the amount of disk throughput at a physical disk level and derives the status from this information. Disk watchers monitor the throughput in KB per second. In addition, the agent detects the removal (loss) or addition of disks at runtime. Typical causes of a high rate of disk I/O are incorrect memory or swap configurations, or applications that have data split over two or more disks. The agent monitors a single process or set of processes (one-to-many watcher) defined by a filter condition on the names, paths, arguments, and users of the processes. A process watcher monitors the following resources based on the setting of an evaluation policy:
Number of instances, child processes, and Size of processes in KB (minimum and
Processes
threads (minimum and maximum metrics) maximum metrics)
Short-term and long-term CPU utilization Restart status and cluster status (binary
(extended minimum and maximum metrics) metrics)
Notes
3-47

Tune Threshold Values of the Linux System Agent to Send Alerts Resource Group Print queues Description Print queue watchers monitor the number of jobs in local or remote print queues as well as the status of a printer. If the printer is offline (down status), the agent provides the error information (reason) that caused the down state. Network interface watchers are created automatically and cannot be deleted. The agent monitors the total network interface use across all network interfaces as well as the individual network interfaces and collects the following data:
Input/Output packets per second Received/Sent bytes per second Input/Output errors per second Number of collisions per poll interval Status and loss of individual network interfaces
Network interfaces
Speed-info attribute
IP/host name attribute
Shared memory
The agent monitors the total number of shared memory IDs and individual shared memory IDs. A shared memory ID represents a shared memory segment and a number of processes attached to this segment. The segment size and the number of processes are monitored by the agent.
Notes
3-48
Resource Group Semaphores
Description The agent monitors the total number of semaphore IDs and individual semaphore IDs. A semaphore ID represents a set of semaphores. The number of semaphores in a set is monitored by the agent. The agent monitors the total number of message queue IDs and individual message queue IDs. A message queue ID represents the number of outstanding messages and bytes in the outstanding messages of the associated message queue. The number of messages and bytes are monitored by the agent. The agent provides watchers to monitor hardware properties, such as disk storage, system temperature, power supply, and fan status. These watchers are similarly structured and based on the generic resource monitoring concept. Generic resource monitoring enables you to extend the monitoring capabilities of the agent for very specific purposes by using external scripts or programs.
Message queues
Hardware monitoring
Notes
3-49

Task Summary
Task Summary
In this task, you learned how to tune threshold values of the Microsoft Windows System Agent with the Agent Browser. You also learned how to send traps or alerts to the DSM Manager. You learned how to create a dashboard and how to tune threshold values of the Microsoft Windows System Agent with ADS. You learned how to create a server group and a server profile, and how to build and deliver a configuration bundle with the UCM. You learned how to create and deliver Adaptive Configuration parameters. You also learned how to tune threshold values of the Linux System Agent to send alerts and traps. In the next task, you will optimize the DSM Manager for systems monitoring.
Notes
3-50
Configure Systems Monitoring Task 2: Optimize the DSM Manager for Systems Monitoring
Slide 3-14
Task 2: Optimize the DSM Manager for Systems Monitoring

The DSM Manager layer, shown in the following graphic, provides control of the day-to-day operations of your IT infrastructure. The managing layer is represented by the DSM, which consists of the Distributed State Machine and its supporting components. Each component of this layer plays a key role in systems monitoring. The managing layer can run on Microsoft Windows and UNIX or Linux platforms.
Slide 3-15
Notes
3-51

Task 2: Optimize the DSM Manager for Systems Monitoring The components that make up the managing layer run as processes that can be started and stopped individually or as a group by the Agent Technology Service Control Manager (awservices). The following table briefly describes key components of the DSM Layer: Component Distributed Services Bus (aws_orb) Distributed State Machine (aws_dsm) Purpose Manages communication between all other Agent Technology components on the node Controls the discovery of agents and monitored resources in the enterprise and maintains the status of these resources based on information received from the agents Provides real-time monitoring of the DSM distribution, which includes the following resources:
Connectivity of DSM to MDB Number of nodes, objects, and classes that the
DSM Monitor (dsmmonitor)
DSM is monitoring
DSM effect on system performance and the
effect on system performance by the other services on which the DSM depends
Load balance of messages to and from the DSM Historical data collection
The DSM Monitor accesses the same kind of data, even when DSMs are installed on different operating systems. It uses various data collection methods to effectively monitor a DSM process, its impact on Unicenter NSM, and its impact on the performance of its server.
Notes
3-52
Configure Systems Monitoring Task 2: Optimize the DSM Manager for Systems Monitoring
Component DSM Store (aws_nsm) Object Store (aws_store) Service Control Manager (awservices)
Purpose Contains DSM managed objects that represent agents and the resources they monitor Stores class definitions for the agents and resource classes that DSM manages Starts and stops all Agent Technology components and agents on the node in the correct order Note While this component is running, all other components can be installed, started, stopped, or uninstalled. The Service Control Manager is the only Agent Technology process that is installed as a Microsoft Windows service.
SNMP Gateway (aws_snmp) DIA Gateway (aws_agtgate)
Handles all SNMP communication on behalf of the DSM Routes SNMP requests from DSM to CA Agents through DIA communication Note DIA is the default protocol used for DSM communications with Unicenter NSM r11.x agents. SNMP is used for DSM communications with Unicenter NSM r3.x agents and for other SNMP-enabled network devices.
WorldView Gateway (aws_wvgate)
Manages communications to and from the MDB
Notes
3-53

Describe the DSM Discovery Process
Slide 3-16
Describe the DSM Discovery Process

Each time the DSM Discovery Process starts, the DSM discovers its domain and re-establishes the managed object list in the DSM Store. It starts with a list of nodes and agents retrieved from the MDB through the WorldView Gateway. It communicates with each node. The DSM examines those nodes that reply to determine the status of agents already known to exist on the node and to identify the possible existence of new agents. The following steps illustrate how the DSM discovery process works: 1 2 3 4 5 6 7 The DSM retrieves a list of nodes from the MDB. This is the list of nodes the DSM is assigned to manage and establishes the domain of the DSM. The DSM adds a managed object to the DSM Store to represent each node in its domain. The DSM queries the Object Store for the agents that can be found on each managed object depending on its particular class. The DSM has the SNMP Gateway query the managed objects to see what agents are installed and running. The DSM adds the discovered agents to the DSM Store list of managed objects. The DSM triggers the SNMP Gateway to query each discovered agent to see what resource watchers it has been configured to monitor. The DSM adds the discovered resource watchers to the DSM Store list of managed objects.
Notes
3-54
Configure Systems Monitoring Describe DSM Configuration
Slide 3-17
Describe DSM Configuration

When you first install Unicenter NSM, the default configuration is set assuming that a DSM is located on the MDB server and that this local DSM will monitor all network devices that WorldView discovers. If other DSMs exist, they will have no members assigned to their domains. This is because the default LOCALHOST server is the only DSM defined and all MDB managed objects are in its domain. When the DSM starts, the WorldView Gateway retrieves all managed objects belonging to the DSM domain from the MDB. It is likely that the DSM will reside on a server other than the MDB server. In this case, you will need to update the DSM configuration so it reflects the correct DSM domain configuration. The DSM_Server value must match the hostname of the DSM Server and the IP address range you specify must be valid for the associated DSM.
Slide 3-18
Define the DSM Configuration Tool

You can decrease the work required of your DSMs and make them work more efficiently. To do this, specify only the classes and IP addresses you know reside in your enterprise and fine-tune the pollset values and managed objects that appear in the 2D Map. By customizing the DSM settings, you can decrease the time it takes for a DSM to discover all the resources it must monitor and to reload policy when restarted. Use DSM Configuration utilities to set the scope of your DSMs at install time and to modify, delete, or add new entries while managing your environment. You can locate the DSM Configuration tools in the MCC by selecting Tools in the left pane.
Slide 3-19
Manage and Configure a DSM Environment

DSM Configuration is a tool that enables you to visually configure the extent that your Agent Technology DSMs can manage their domain environment or scope.
Notes
3-55

The Role of DSM Configuration To proactively keep all systems running as smoothly as possible with the least number of problems or downtime, you need an easy way to configure what each DSM is monitoring and how often the DSM communicates with system devices. Settings that used to be contained only in files are now accessible from two interfaces, the MCC under Tools DSM Configuration and the DSM Wizard.
The Role of DSM Configuration

DSM Configuration determines how the DSM policy is implemented. In general, the DSM configuration tools contain information about:

Slide 3-20
What to manage. What to look for. Where to look. When to check. How to display in WorldView what is being managed.
DSM Agent Class Scoping

DSM Agent Class Scoping displays the names of all the agent classes that the DSM manages. By looking at this list, you can easily see all the agent classes that any DSM is responsible for monitoring. This list contains information about what agent classes to monitor and what policy to load. You can decrease the work of your DSMs and, therefore, make them more efficient, when you specify only the agent classes that you know reside in your environment. By configuring each DSM to focus on your specific agent classes, you can decrease the amount of time it takes a DSM to discover its agents and to load policy when the DSM is started. Note: When you introduce a new policy, you must add the agent class name to the list of known agent classes.
Notes
3-56
Configure Systems Monitoring DSM Agent Class Scoping Pane
Configure the agent classes by performing any one of the following tasks:

Add a new agent class for the DSM to monitor. Modify any existing agent class settings. Delete an existing agent class from the list of those being monitored.
DSM Agent Class Scoping Pane

In the DSM Agent Class Scoping pane, check the Managed Status box for the agent classes the DSM must monitor and clear the box for any agent class that the DSM must no longer look for during discovery. Entries with DSM Server set to ANY apply to all DSMs in your enterprise while a specific DSM entry applies only to that specific DSM. If, for some reason, the same agent class indicates ANY and a specific DSM, the specific DSM takes precedence over ANY. In this case, the change would be applied to the specific DSM only. When you make any changes to the existing list, click Notify DSM so the affected DSM refreshes its configuration. There is no requirement to stop and start the DSM.
Slide 3-21
DSM Discovery Community Strings

The DSM Discovery Community Strings pane identifies community strings and port numbers that your DSM uses to discover agents and devices. The community string tells the device whether the DSM has read or write permission for any SNMP get and set requests. If the community string is successful during the discovery phase, it is continually used for that device, unless you modify it. By looking at this list, you can see which community strings and ports your DSM uses or you can configure the DSM to use different community strings and ports to communicate with specific node classes and agent classes. Because community strings are the authentication notification with which the devices and DSM communicate, you need a way to modify these access strings at various intervals, depending on your security requirements.
Notes
3-57

DSM Polling
DSM Polling
The DSM regularly requests information from managed systems regarding the status of monitored resources. These requests take the form of SNMP GetRequests and are called polls because they are repeated requests that occur regularly.
Slide 3-22
DSM Discovery Pollset Values

The DSM Discovery Pollset Values pane displays the poll intervals, the timeouts, and the number of retries that the DSM uses to poll discovered agents and devices. When discovered, the devices are assigned these poll values for use in future communications. After looking at this list, you can quickly see what intervals, time-outs, and retries your DSM uses. By modifying the list of poll intervals, the interval at which the DSM checks all the devices can be customized, based on the type of resource or server being monitored. If the DSM queries all devices too often, the DSM and network are busier than necessary. When you make any changes to the existing table for DSM Discovery Pollset Values, click Notify DSM so any affected DSM refreshes its configuration. The new values will be used for DSM managed objects discovered subsequent to the change. To activate the new values for pre-existing DSM managed objects, they must be rediscovered by the DSM. The easiest way to accomplish this is by restarting the DSM.
Notes
3-58
Configure Systems Monitoring Improving Pollset Efficiency
Improving Pollset Efficiency

You can increase the number of managed objects by increasing the poll interval. However, setting network object polling at intervals greater than 60 minutes is not recommended. The default setting of 5 minutes helps ensure that outages are detected in an average time of 2.5 minutes. Longer poll intervals mean longer delays before outages are detected, although this does not impact agent-detected problems because those problems are reported through agent traps. DSMs poll agents only to help ensure that the agent and the path from the DSM are operational. Infrequent polling of agents is the norm for a Unicenter deployment. The primary concern for DSMs is that all object polls are complete in their elapsed poll cycle and that enough capacity exists to handle a message storm from a failing network. The upper limit is a combination of the capacity of the server, availability of network bandwidth, and speed of the operating system. Large DSMs are memory-intensive and processor-speed dependent.
Slide 3-23
IP Address Scoping
Each DSM has a list of nodes that it manages; this is referred to as the DSM domain. The IP Address Scoping interface enables you to change the range of subnets or hosts that report to a particular DSM. By modifying a DSM list of IP addresses, you can control how many nodes and devices report to each DSM. You can perform the following actions:

Set up an entire subnet to report to a DSM by using wildcards, such as *.*.*.*. Specify a range of addresses in a subnet. Exclude specific IP addresses or address ranges from being monitored.
Notes
3-59

Setdsmname By assigning your DSMs to manage specific IP addresses, you can spread the load of monitoring your enterprise among the number of DSMs you deploy. You can help ensure that each DSM manages those nodes that are near it in the network to reduce the amount of network traffic. The DSM IP Scope table notifies each DSM of what nodes to manage. When the aws_wvgate service starts, it checks the DSM IP Scope table and makes corresponding DSM_Server and DSM Address updates before selecting the monitored objects. While aws_wvgate is running, it listens for WorldView notifications and updates DSM_Server and DSM Address properties for all new objects of managed classes. Also, aws_wvgate dynamically updates MDB objects to reflect any DSM IP Scope changes detected through the DSM Wizard or any DSM configuration scoping change made through the MCC interface.
Slide 3-24
Setdsmname
If you click Notify DSM after modifying the DSM IP Address Scoping pane in the MCC and you have one or more DSMs running, the aws_wvgate service sets the DSM_Server and DSM_Address properties. The setdsmname command (run manually) reads the entries in DSM IP Address Scoping and updates the DSM_Server and DSM_Address Instance Level Properties (ILPs) in the Managed Objects of the MDB. Each DSM, when started, downloads the list of IP addresses that it was configured to manage. Note: You cannot manage the same IP address from multiple DSMs if the DSMs report to the same MDB. An IP address must have only one entry in the DSM IP Scoping table.
Notes
3-60
Task Purpose: Select the systems to be managed by a DSM using IP address ranges. The MCC or DSM Wizard can be used to complete this task. 1 2 3 4 5 6 7 Open the MCC. In the left pane, select Tools from the View type list. Select Tools YourServerName Address Scoping. DSM Configuration DSM IP
Change the DSM Server name from LocalHost to YourServerName. Change the IP Mask from *.*.*.* to the address range used on your server, for example, 138.42.45.*. Click Save Changes. Click Notify DSM.
In the next interactive demonstration, you will select agents to monitor.
Task Purpose: Select the specific agents for the DSM to monitor to improve efficiency and performance. The MCC or DSM Wizard can be used to complete this task. 1 2 3 4 5 At a command prompt, type dsmwiz and press ENTER. The DSM Wizard appears. Click Next. Click Deselect All. Select AWsadmin, caiWinA3, dsmMonitor, IP_Interfaces, and PingIP. Click Save.
Notes
3-61

Interactive Demonstration 6 7 8 9 Click Next. Accept the default setting for Community Strings and click Next. Accept the default settings for polling parameters and click Next. Accept the default settings for DSM class and agent instances and click Next.
10 Accept the default settings for Subnet Selections and click Next. 11 Check Enable New Configuration and click Finish. In the next interactive demonstration, you will customize polling intervals.
Task Purpose: Create a custom pollset for the caiWinA3 agent to be polled every 1,200 seconds. By default, the DSM polls host-managed objects every 600 seconds, or 10 minutes, and IP_Interfaces every 900 seconds, or 15 minutes. These parameters can be customized for longer or shorter intervals based on the network environment. 1 2 3 4 5 6 7 8 Open the MCC. In the left pane, select Tools from the View type list. Select Tools YourServerName Discovery Pollset Values. Click Insert. Change the Agent Class from ANY to caiWinA3. Change the Poll Interval from 600 to 1200. Click Save Changes. Click Notify DSM. DSM Configuration DSM
Notes
3-62
Configure Systems Monitoring Identify DSM Commands
Slide 3-25
Identify DSM Commands

The DSM commands are described in the following table: DSM Command resetdsm resetdsm init Description Overwrites stores by extracting from the original caz archives and then loads the policies under DM Recreates the nsm store and object store, loads the policies under DISTRIB\dsm, and then loads the policies under DM Overwrites stores by extracting from the caz archive and then loads the MIB files under \CONFIG\MIBS and \AGENT\MIBS Recreates the sadmin-store, loads the MIB files under <CRP>\mibs, and then loads the MIB files under \CONFIG\MIBS and \AGENT\MIBS Displays a list and the status of local CA agent watchers according to definitions in atlist.cfg in aws_sadmin directory Displays the status of awservices service only Displays the status of services Displays connection init time Displays in and out traffic Dynamically loads new policies without need to restart aws_dsm
clean_sadmin
clean_sadmin init
atlist
awservices status awservices list orbctrl -E orbctrl -e ldatp -n converter -n
Notes
3-63

Monitor the Status of DSM Managed Objects
Slide 3-26
Monitor the Status of DSM Managed Objects

The DSM discovers agents and monitored resources and represents them as managed objects in the DSM Store. There will be occasions where you need to monitor the status of all DSM managed objects for a particular node. The Node View utility provides you with this capability. The leaves of the Node View tree represent the following managed object types:

The managed node Agents installed and running on the node Resource groups the agent is designed to monitor Instances that the resource group has been configured to manage
The objects that branch from the node represent agents located on the node. Objects branching from each agent represent the resource groups monitored by each agent. Under the resource groups are the individual instances of these resources being monitored.
Launch Node View

Typically, you can launch Node View from the MCC using the View Node context menu option. When the node is identified, right-click the agent on the node and choose View Node. You can also open Node View from the system prompt using the nodeview.exe command. You can invoke Node View using the following syntax: nodeview [-@ servicesHost] [-d debugLevel] [-f logFile] [-target initialTarget] The following syntax is an example of how to invoke this code: nodeview -@ unidsm01 -target uniagt01@unidsm01
Notes
3-64
Configure Systems Monitoring Use the Mini-Tree
The MCC launches Node View in a context-sensitive fashion. If you choose the View Node option from the context menu of a monitored resource group or a monitored instance, Node View opens displaying only the selected item and any items that fall under it. If needed, you can display the entire node object tree by choosing the View Show From Root menu option. Node View displays the overall status of the node, the status of the individual agents, and the status of the resource instances being monitored. When you invoke Node View, a list of managed objects and their status is obtained from the DSM. Status values propagate up through the Node View hierarchy from the monitored instances to the node. The result is that the node reflects the most severe status being reported by any of the child objects.
Use the Mini-Tree

When the Node View object tree is too large, you must scroll through the main window to see all the objects. The mini-tree is a navigational tool that enables you to see all the objects without scrolling. If you click a box in the mini-tree, the main window scrolls to show the corresponding object and its name. To open the mini-tree choose View Show Mini-Tree, or click the Hide/Show MiniTree icon.
Interpret Status
Node View represents the status of managed objects by their color. It also represents the overall status of the node through the propagation of status. At each level of the tree, the most severe status being reported propagates to the next higher level.
Notes
3-65

Interpret Status You can identify the status of an object in Node View using the following information: Color Red Red Orange Yellow Bright Green Dark Green Blue Gray Status Broken Broken Down Warning Repaired Up Unknown Gone DSM Object Status Critical Absent Acknowledged Warning Repaired Up Unknown Gone
Task Summary
In this task, you learned about the key components of the DSM Layer and how the DSM Discovery process works. You learned how to configure the DSM to select systems to be managed and agents to monitor. You also learned how to customize polling intervals plus how to monitor the status of DSM managed objects with Node View. In the next task, you will learn how to apply URM to custom Unicenter NSM environments.
Notes
3-66
Configure Systems Monitoring Task 3: Apply URM to Custom Unicenter NSM Environments
Slide 3-27
Task 3: Apply URM to Custom Unicenter NSM Environments

URM provides a quick-to-deploy remote monitoring solution that is a first step for organizations that have, or are beginning to deploy, enterprise management tools. It enables immediate and simplified monitoring of hosts, workstations, IP-enabled devices, and Microsoft Windows and UNIX resources.
Slide 3-28
Define URM Architecture

URM performs its monitoring function without installing an agent on each monitored resource. In fact, the only required installation is for the Remote Monitoring application itself. Unlike other monitoring tools that depend on data available from a single source, such as SNMP, Remote Monitoring is a crossplatform, multi-layered monitoring tool. URM provides a broad subset of the monitoring capabilities of Agent Technologies.
Notes
3-67

Define URM Components The following graphic illustrates a typical deployment using URM:
Slide 3-29
Slide 3-30
Define URM Components

Remote Monitoring consists of the following major component areas:

Administrative Interface (AI) saCORe Data fetchers XML store
Notes
3-68
Configure Systems Monitoring AI
AI
AI provides you with the interface to discover resources, configure selected resources, and receive updates on the status of monitored resources. AI will initially be Microsoft Windows centric, running only on Microsoft Windows computers. You can launch AI as a stand-alone program or you can launch it in context from Unicenter WorldView or the MCC. In addition, AI will use the data fetcher components to perform the discovery of services, event logs, performance metrics, processes, registry keys, and IP ports. Default monitoring configurations, or templates, are provided to enable you to configure resources quickly. The templates apply to most monitored aspects of a Microsoft Windows resource as well as an IP resource.
saCORe
The Remote Monitoring Agent, saCORe, is the main processing module responsible for doing the work for Remote Monitoring. It polls each monitored resource continuously and determines if an error has occurred. It issues requests to the appropriate data fetchers and examines the returned data for errors. The agent component runs as a service and can be started and stopped from awservices. Because agents are not installed on monitored resources, there are trade-offs between a traditional agent-based approach and the Remote Monitoring approach. Remote Monitoring uses non-intrusive technology at the expense of creating additional network traffic. The advantage of installing an agent on a remote resource is that the agent uses the CPU cycles and memory of the remote computer to determine if an error has occurred. The agent forwards only the errors to the Event Management Console and the WorldView Repository.
Notes
3-69

Define Resource Monitoring However, with Remote Monitoring, the agent gathers the required data, based on your selections, and pulls the data back across the network to the Remote Monitoring computer. The agent uses the memory and CPU of its own computer to determine whether or not an error has occurred. This process can increase the amount of traffic flowing over your network, but it enables the monitored computers to devote their entire resources to servicing your production requests.
Slide 3-31
Define Resource Monitoring

The technology used to communicate with each resource is dependent on the resource type. Remote Monitoring uses technology that is native to each resource type as a means to compensate for having no code installed on the monitored resource. The methodology for each resource type is listed in the following table: Resource Type IP Methodology Remote Monitoring uses the Internet Control Message Protocol (ICMP) libraries to ping addresses and ports. Remote Monitoring uses the Remote Procedure Call (RPC) technology that is native to Microsoft Windows and installed by default to gather data that has been made available through this mechanism. For security, Remote Monitoring uses the credentials under which the Remote Monitoring Agent service is running.
Windows
URM monitors the following resources:

Microsoft Windows Linux AIX
Notes
3-70
Configure Systems Monitoring Identify Hardware Requirements

Slide 3-32
HP-UX Solaris Tru64 Mac OS
Identify Hardware Requirements

You must install the Remote Monitoring Agent on a computer dedicated to running the agent. The CPU needs to be relatively powerful because it is assessing the data for each monitored resource to determine if an error has occurred. Depending on the number of resources, their types and configurations, and the scheduled polling cycles, the CPU of this computer can be very busy polling each server. Due to the techniques used by the Remote Monitoring Agent to remotely monitor resources, there is an inherent limit as to the number of resources a single Agent installation can monitor. The solution is to deploy multiple agents. In a WAN environment, each remote office can have one or more agents, depending on the workload, while a large central office can have several agents. The recommended limit for each agent installation is 200 to 250 IP and Microsoft Windows resources combined. If you are running state-of-the-art hardware, this limit can be higher.
Slide 3-33
Identify Software Requirements

You must install the Remote Monitoring Agent using an administrator account and password that enables it to access each of your remote Microsoft Windows resources. The Agent uses the security definition under which the Remote Monitoring Agent is running to access your remote computers. This is a more secure approach than having you provide accounts and passwords for each monitored server.
Notes
3-71

Identify Software Requirements If you plan to run Remote Monitoring on Microsoft Windows NT or Windows 2000, you must have the appropriate service pack installed. In addition, there are a number of other elements you must review and verify prior to URM installation. Refer to the following table: Component Windows NT 4.0 Windows 2000 Windows 2003 Server Unicenter NSM Requirement Service Pack 6a Service Pack 3 Service Pack 1 Requires Remote Monitoring Administrative Interface installed on a computer that has an installation of Unicenter NSM (admin client or manager) Installed and running Note Check your running services to determine if Unicenter CAICCI is active or use a command prompt to run the ccicntrl status command. WorldView Base Component Event Management Base Component Installed Installed
Unicenter CAICCI
Notes
3-72
Task Purpose: Install Remote Monitoring as an alternative to standard DSM or agent configuration. This solution can be used when rapid deployment is necessary or remote DSM deployment is not feasible. 1 2 3 4 5 6 7 8 9 In Microsoft Windows Explorer, open the C:\InstallMedia\UNI_NSM_r11\Windows folder. Double-click the setup.exe file to open the Unicenter NSM Product Explorer. Expand Unicenter for Windows. Expand Post Installation Utilities. Select Remote Monitoring. Click Install. Click Next to begin the Remote Monitoring Agent setup. Select Custom Setup Type and click Next. Select Agent, Administrative Interface, Tools, and Icons and click Next.
10 Type caunint in the User name field, type unicenter in the Password field, and click Next. 11 Type nsmadmin in the WorldView User name field, type unicenter in the WorldView Password field, and click Next. 12 Click Next to begin the file copy. 13 Select Yes, I want to launch the URM Agent now. 14 Click Finish. Now that you have installed URM, you will configure URM in the next interactive demonstration.
Notes
3-73

Task Purpose: Configure URM to monitor resources. 1 Click Start and then choose Programs Computer Associates Unicenter NSM Remote Monitoring Remote Monitoring AI. Select Windows Discover. Unicenter
2 3 4 5 6
Select the Windows Domain to monitor, select YourServerName, and click OK. Expand URM Agent Windows Resources YourServerName. Right-click YourServerName and select Properties. Change the Poll Interval to 30. Note: 30 seconds is too short an interval for most environments.
7 8 9
In the Modify Windows Resource dialog, select the System Metrics tab. Select Memory (Windows) from the Metric Category list. Select Page Faults Rate and Committed Memory to monitor.
10 From the Metric Category list, select Logical Disks. 11 Select the Detailed Metrics tab. 12 With Logical Disks selected in the Display Parameters list, click Discover. 13 When prompted, click Yes to proceed with the discovery. 14 Select All. 15 Select C:. 16 Select Free Space (%) to monitor. 17 From the Free Space (%) Rule list, select <=.
Notes
3-74
18 Change 25 to 20 in the Free Space (%) Warning field. 19 Select the Services tab. 20 Select Auto-start services. 21 Select the Print Spooler to monitor. 22 Select the System Metrics tab. 23 Select Printers from the Metric Category list. 24 Uncheck Out of Paper Error and Printer Not Ready. 25 Click OK to save this monitoring configuration. 26 Choose Agent Unicenter Options. 27 In the Unicenter Options dialog, verify that the user name is nsmadmin and the password is unicenter. 28 Select All resources (normal to down) to display. 29 Click OK.
Test the Solution

30 Open the MCC. 31 In the left pane, select Business Process Views from the View type list. 32 Expand WorldView and select YourServerName. 33 Select Remote Monitoring. 34 At the command prompt, type net stop spooler and press ENTER. 35 Open URM. 36 Expand URM Agent\Windows Resources\YourServerName\Services and select Print Spooler. 37 Open the MCC.
Notes
3-75

Skill Practice 38 Expand WorldView\YourServerName\Remote Monitoring\URM Agent\Windows Resources\YourServerName and select Print Spooler. 39 Open URM. 40 View the Print Spooler Severity level. 41 At the command prompt, type net start spooler and press ENTER. 42 In URM, click Print Spooler Severity to open the Alarm Details dialog. Review the details and click OK to close the dialog.
Skill Practice
Task Purpose: Configure URM to monitor resources. 1 Use the local administrator account for Virtual Windows 2003 Server 2.
Discover Virtual Windows 2003 Server 2

2 Monitor the following: System Metrics: Processes CPU Usage >= Warning=65 Alarm=75 Memory Usage >= Warning=75 Alarm=85 Services Print Spooler
Configure Service Failure Action

3 4 Expand URM Agent (YourServerName)\Windows Resources\YourServerName\Services. Right-click Print Spooler and select Properties.
Notes
3-76
Configure Systems Monitoring Skill Practice
5 6
From the Action? list, select restart. Click OK.
Verify the Results

7 Stop the Print Spooler service and verify that URM sends an alert and restarts the service automatically.
Task Summary
In this task, you learned about URM architecture, its components, and resource monitoring. You also learned the hardware and software requirements for installing URM. You installed URM and configured it to monitor resources.
Notes
3-77

Assessment
Assessment
1 What is the common basis used by the DSM Manager and Agents to communicate? a b c d 2 MIB CAICCI CATRAPD DSM Store
Which command enables you to stop, start, and check the status of all Agent Technology Services components on the local computer? a b c d awstop awstart awstatus awservices
What defines how metric values, status total values, and culprit lists of monitored instances are calculated for one-to-many watchers? a b c d DSM policy Object Store Callback script Evaluation policy
Notes
3-78
Configure Systems Monitoring Assessment
When does an agent automatically receive a trap destination address? a b c d While discovering the network After running the resetdsm command When the agent browser is launched for the first time When Node View is launched for the first time
What must be created to deliver a Base Profile using Unicenter Configuration Manager? a b c d Group Dashboard Differential Profile Adaptive Configuration
Which DSM Configuration tool defines what agent classes the DSM will look for and what policy it will load? a b c d DSM Agent Class Scoping DSM Discovery Pollset Values DSM Managed Object Scoping DSM Discovery Community Strings
Notes
3-79

Assessment 7 What acts essentially as a password that controls access to agents? a b c d 8 DSB Object Store SNMP Store SNMP Community String
What is a valid IP Mask for configuring DSM IP Address Scoping? a b c d 138.42.45.* 138.42.45.0 142.38.*.120 142.38.56.10*
There are trade-offs between a traditional agent-based approach and the Remote Monitoring approach. What does Remote Monitoring use at the expense of creating additional network traffic? a b c d Traps Reduced network traffic Non-intrusive technology Minimal network bandwidth
Notes
3-80
Configure Systems Monitoring Module Summary
Slide 3-34
Module Summary

Configure OS Agents Optimize the DSM Manager for Systems Monitoring Apply URM to Custom Unicenter NSM Environments
To facilitate comprehensive and integrated network polling and administration, Unicenter NSM uses Agent Technology to monitor the status of enterprise resources, determine when status changes occur that require attention, and report these status changes to Unicenter Event Management so that corrective action can be automatically initiated. Agent Technology agents monitor and report the status of your resources and applications to their manager, the DSM. The DSM determines if the reported status indicates that a state change has occurred and reports state changes to Unicenter Event Management. The DSM also maintains a managed object representing each monitored resource. The managed object has properties that identify, among other aspects, the last known state and DSM polling requirements for that object. In this module, you were shown the processes involved in monitoring system resources. Several demonstrations guided you through the steps required to configure OS agents with the Agent Browser, ADS, UCM, and Adaptive Configuration. You were also shown how to optimize the DSM Manager for systems monitoring and how to apply URM to Unicenter NSM environments. All these tools will help save time and enable you to monitor the systems more effectively. In the next module, you will learn how to discover system and network devices.
Notes
3-81

Module Summary
Notes
3-82
4
4-1

Module Objectives
Slide 4-1
Module Objectives

Perform Classic Discovery Configure Continuous Discovery Reclassify Objects
Module Overview
Common Discovery is the process where devices on the network are found and classified and are then placed in the MDB as managed objects. Common Discovery provides RBC with a shared tool to gather important information about common IT infrastructures. It provides both an on-demand and a continuous, or real-time, mode. It provides discovery services to other CA common services components and updates the CA common database, the MDB, with newly discovered and classified network objects. Common Discovery facilitates this information gathering and stores the information in the MDB for easy access to all applications using the MDB. Discovery services notify subscriber applications of changes in the environment. In this module, you will locate and identify system and network devices using discovery tools. You will perform Classic Discovery and configure Continuous Discovery. Finally, you will examine object properties and reclassify objects.
Notes
4-2
Discover System and Network Devices Task 1: Perform Classic Discovery
Slide 4-2
Task 1: Perform Classic Discovery

There are two types of Common Discovery, Classic and Continuous. Classic Discovery is an on-demand process that enables you to decide which subnets you want to discover and when. You can also configure Classic Discovery to run at regular intervals. This can be used as an alternative to Continuous Discovery and can help ensure that your discovered environment in the MDB is always current. You can start a Classic Discovery from the Discovery GUI, the MCC, the Unicenter Browser Interface, or the command prompt. There are two methods of gathering configuration information before running Classic Discovery:
Slide 4-3
The Discovery Wizard walks you through configuration screens based on your selections. Use the Discovery Wizard to gather information about how you want to execute the discovery process. Advanced Discovery contains a tab format and enables you to configure every screen.
Slide 4-4
Describe Advanced Discovery

Advanced Discovery gathers the same information as the Discovery Wizard but contains eight tabs for quick entry.
Scope
Use this screen to configure the portion of the network in which you want to have the discovery process run.
Notes
4-3

Subnets There are three options:

Discover the entire network: This option will run IP Discovery and SAN Discovery on the local subnet. Discover a subset of the network: This option will run IP Discovery and SAN Discovery on the subnets that you define in the Subnet configuration screen. No IP DiscoveryRefresh SAN Links Only: This option will only run a SAN Discovery.
Subnets
This screen is used to configure the subnets you want discovery to run. To define a subnet, you need to enter the Subnet Address using a 0 to indicate all, the Gateway Address, and the Subnet Mask. The subnet will appear in the Subnet list. A green light means that the subnet will be included when the discovery process is executed. A red light means that a discovery has already been run against that subnet and that it will be excluded when the discovery process is executed. A previously discovered subnet can be included. When you execute the discovery process, the network devices in this subnet will be discovered again.
SNMP
Discovery needs SNMP communication with the network devices to classify them. SNMP uses Community Names to authenticate its communication. The SNMP configuration screen enables you to enter Community Names and Network Masks so that discovery can communicate with the network devices in your enterprise. Community Names are case-sensitive and the Network Mask uses an asterisk (*) to indicate all. To add a new Community Name to the Community Name list, simply enter the Community Name and Network Mask.
Notes
4-4
Discover System and Network Devices Mode
Mode
The Discovery Wizard of the MCC offers two types of discovery mode. These two types are:

Detailed Discovery: This mode uses a Ping Sweep method of sequentially pinging every IP address to discover the devices on a network. Faster Discovery: This mode determines which network devices it will run discovery against using the ARP Cache.
When you first install Unicenter NSM, it is recommended that you run a Detailed Discovery to complete a comprehensive search of your network. Periodically, it is also a good idea to run a Faster Discovery.
DHCP
Classic Discovery has two options that deal with the discovery of network devices whose IP addresses are assigned using Dynamic Host Configuration Protocol (DHCP). To use these options, you must first identify the IP address ranges that are controlled by DHCP. To enter a DHCP range, simply enter a starting IP address and an ending IP address. Defining DHCP IP address ranges does not limit the discovery.
SAN
If you want to run a SAN Discovery only, you must select the Discover SAN Devices Only check box. To run an IP Discovery this check box must be cleared. Adjustments can be made for Timeouts and Retries.
Options
The Options configuration screen will only appear if you are in the Advanced mode of the Discovery Wizard.
Notes
4-5

Options This screen has the following three basic areas of options, with a variety of defaults that can be checked on or off:

Discovery Object Naming IP Address Conflict Resolution
Discovery
The following table outlines the Discovery options: Discovery Options Rediscover Subnets r Description This option takes subnets that are excluded because they were previously discovered and includes them for this discovery. If a subnet was manually set to exclude, then it will not be changed. This option causes discovery to check the registry of the device, FTP port, and Telnet port to classify the device. These checks are only run if the SNMP check fails. This option ensures that only those devices that discovery can communicate with using SNMP will be discovered and added to the MDB as managed objects.
Check Additional Ports
Discover SNMP Devices Only
Notes
4-6
Discover System and Network Devices Options
Discovery Options Delete Old IP Interfaces
r Description This option deletes the old managed object and creates a new one if the device was previously discovered and is discovered again. If not checked, discovery will skip the device and keep the current information on the managed object. This option controls whether the discovery that runs on the subnets is limited to SAN objects. A typical IP Discovery executes, but only SAN devices are added to the MDB. When the discovery of the device is complete, SAN links are determined and SAN Discovery will use the newly discovered SAN objects and those already existing in the MDB to determine the SAN configurations in the subnets.
Run SAN Discovery
Object Naming
The following table outlines the Object Naming options: Object Naming Options Description Use Domain Name Server/Host File Use IP Address instead of sysName Specifies whether the DNS name should be used to name and label the managed object Tells discovery to use the IP address for the name and label of the managed objects
Notes
4-7

Options Object Naming Options Description Label Interfaces with DNS Name Remove Suffix Changes the interface (router) label to the DNS name Enables you to truncate the name of objects based on a list of suffixes; this requires you to enter the suffix you want to remove
IP Address Conflict Resolution

The following table outlines the IP Address Conflict Resolution options: IP Address Conflict Resolution Options Delete Unclassified DHCP Object Description Deletes an unclassified DHCP object from the MDB when a classified object is found by discovery that has the same IP address; the classified object is then added to the MDB Changes the status of an existing classified object in the MDB to IP Address Invalid when another object is found by discovery that has the same IP address
Update Classified DHCP Object
Notes
4-8
Discover System and Network Devices Timeouts
Timeouts
This configuration screen is used to set the Discovery Query Timeout values. These values can greatly affect how successful and how long your discovery takes to run. If set with a higher timeout value, discovery will take longer but devices will have plenty of time to communicate successfully with discovery. If set with a lower timeout value, discovery will run quicker but devices might not get classified or even discovered.
Discovery Monitor
The Discovery Monitor provides a visual display that enables you to track the progress of discovery. The Discovery Monitor is refreshed every five seconds to help ensure an accurate representation of the progress of the discovery process. Besides providing an object count, the Discovery Monitor displays:

Time the discovery process began Number of discovery processes running Current subnet name Current IP address being pinged Messages pertaining to the discovery process
Task Purpose: Discover network devices, operating systems, wireless devices, and network topology with Classic Discovery to provide an accurate map of your IT infrastructure. 1 2 3 4 Open the MCC. Select Topology Expand Tools Tools. YourServerName and select Advanced Discovery.
On the Scope tab, select Discover a subset of the network.
Notes
4-9

Perform Command Line Discovery 5 6 7 8 9 Select the Subnets tab. Type your subnet address in the Subnet Address field. Type your gateway address in the Gateway Address field. Type your subnet mask in the Subnet Mask field. Click Add.
10 Verify the information on the SNMP tab. 11 On the Mode tab, select Detailed Discovery. 12 Click the Options tab. 13 In the Object Naming Options section, select Remove Suffix and type your local domain in the Remove Suffix field, such as USSCDOM01.com. 14 Click Start Discovery. 15 The discovery results will display in the Discovery Monitor while discovery is running and after it has finished.
Slide 4-5
Perform Command Line Discovery

DSCVRBE is an executable command run from the command prompt to perform discovery. One advantage is that you can discover a single device with the -7 parameter. This makes adding a new computer or discovering a single device much quicker. DSCVRBE has multiple switch commands, which correspond to the options provided in the Advanced Discovery interface. An example of the syntax is: dscvrbe -7 (IP Address or Host Name) -R (MDB) Other discovery commands that can be run from the command prompt are:

TNGSRVCS: This opens the Distributed Services GUI used to start and stop the discovery process and access the setup programs. DSCVRNET: This opens the Subnet Management window used to determine on which subnets to run discovery.
Notes
4-10
Discover System and Network Devices Perform Command Line Discovery
DSCVMNTR: This opens the Discovery Monitor, which shows the status of the discovery process. DISCSRV: This activates the Trace Console, which provides a Command Prompt window that monitors discovery activity.
The following table outlines DSCVRBE parameters: DSCVRBE Parameters Repeatedly discover the subnets Do not insert class B network Discovery method (ARPCACHE | PINGSWEEP | FASTARP |FROMDNS) ICMP Ping query timeout value Use DNS name or not Number of SNMP query per community Time to start (also needs -Y) Instance Number If no DNS, use sysName or IP Delete old unclassified DHCP objects Level of Logging New subnet filter For Range [xxx.xxx.xxx.xxxyyy.yyy.yyy.yyy] -A -B -D Values [Default] Yes | [No] Yes | [No] [ARPCACHE]
-E -F -G -H -I -J -K -L -M
millisecond | [400] [Yes] | No [1] | 2 | 3 | 4 | 5 | 6 | 7 | 8 hh:mm | [current time] unique number [sysName] | IP Yes | [No] [0] - 9 [*.*.*.*]
Notes
4-11

Perform Command Line Discovery DSCVRBE Parameters Subnet mask for first subnet Create SNMP device only Number of ICMP pings per object Stop discovery when finished Repository name (Required) Discovery new subnet counter Database update throttle time Attempt other probes for unknown devices Level of console messages SNMP query timeout value Running in DHCP environment Date to start (also needs -H) Update old classified DHCP object Unique string identifying the application Suffix to be removed from device name Use DNS name for interface Rediscover those discovered subnets -N -O -P -Q -R -S -T -U -V -W -X -Y -Z -1 -3 -4 -5 Values [Default] subnet mask | [255.255.255.0] Yes | [No] 1 | 2 | [3] | 4 | 5 [Yes] | No RepositoryName all | number | [0] second | [0] Yes | [No] [Yes] | 1 - 9 millisecond | [800] Yes | [No] mm/dd/yyyy | [current day] Yes | [No] string suffix Yes | [No] Yes | [No]
Notes
4-12
Discover System and Network Devices Perform Command Line Discovery
DSCVRBE Parameters Loopback for CISCO router or no objects Discover only this host Discover only those subnets in filename Refresh routers and the interf Perform crosschecks in Routing table Preferred discovery log filename SAN Discovery option (SAN | NOSAN | SANONLY | SANREFRESH) SAN Proxy ping timeout value SAN Proxy ping retries SAN Proxy query timeout value SAN Proxy query retries Discovery Profiles Threaded Ping ICMP interval -6 -7 -8 -9 -12 -13 -14
Values [Default] [Yes] | No | NoObj a.b.c.d | dnsname filename Yes | [No] Yes | [No] Filename [NOSAN]
-15 -16 -17 -18 -19 -21
millisecond | [1000] [0] | 1 | 2 | 3 millisecond | [10000] [0] | 1 | 2 | 3 Profilename 1 - 255 [50]
Notes
4-13

Task Purpose: Perform Command Line Discovery. 1 2 At a command prompt, type: dscvrbe -7 targetmachine -3.domainname.com -F No -V 9 Press ENTER.
Task Summary
In this task, you examined the two methods for gathering configuration information before running discovery. Using Classic Discovery, you discovered network devices, operating systems, wireless devices, and network topology to provide an accurate map of your IT infrastructure. You examined the parameters and default values of the DSCVRBE command and then used commands to perform Command Line Discovery. In the next task, you will configure Continuous Discovery.
Notes
4-14
Discover System and Network Devices Task 2: Configure Continuous Discovery
Slide 4-6
Task 2: Configure Continuous Discovery

Continuous Discovery is event-driven and ongoing. It employs a manager and agents that continuously scan your network in real-time mode for new devices or changes in IP addresses of existing devices. You can configure Continuous Discovery for optimal load balancing between the discovery agents and the Discovery Manager. If you choose this method of discovery, you must install the Continuous Discovery Agents and the Continuous Discovery Manager.
Slide 4-7
This method serves a multi-tiered architecture, as shown in the following graphic, enabling discovery across the enterprise:
Notes
4-15

Task 2: Configure Continuous Discovery
Slide 4-8
The Continuous Discovery Manager consolidates discovery information with the MDB that is gathered by the Continuous Discovery Agents. When a new device is discovered on the network by an agent, it updates the MDB with this information. The Manager monitors the latest traffic for a device through various mechanisms including:

Monitoring DHCP and network traffic. Scanning the ARP caches of routers. Scanning monitored subnets through various protocols, such as ICMP (ping), SNMP, and HTTP.
Discovery information is submitted to the MDB to be shared among Unicenter NSM components and other CA products. When new devices are discovered, these products can use the MDB DIA cell to receive event notification to define business policy. It is recommended that you run a combination of Classic and Continuous Discovery when you want to discover subnets, rather than running them both concurrently. Because Classic and Continuous Discovery work differently, depending on which options you select for both methods, you need to be aware of the following differences to avoid creating duplicate devices in the MDB:
Classic and Continuous Discovery name devices differently: Classic Discovery supports naming a device using its sysName, the MIBII value for a device that supports SNMP, which is the default if no DNS name is available. SysNames are not supported by Continuous Discovery.
To avoid discovering duplicate devices in Classic Discovery, set the dscvrbe -j option to IP so that the IP address is used if the DNS name cannot be found. Using IP addresses to name discovered devices helps ensure that objects are named using the same method and that no duplicates are created. Set this option only if DNS is not enabled in your environment.
Notes
4-16
Discover System and Network Devices Interactive Demonstration
Note: If you are using the Classic Discovery GUI to run discovery, select Use IP address Instead of sysName.

When you run a full subnet discovery using Classic Discovery, stop the Continuous Discovery services. Continuous Discovery discovers only subnets on which an agent is deployed. To automatically monitor and discover non-agent subnets using Continuous Discovery, perform one of the following: Run the Classic Discovery DSCVRBE command to discover a router and all subnets it supports. Write a script using the dscvrbe -7 option to discover all gateways on the wanted subnets.
For more specific details on configuring Continuous Discovery options, refer to the Administrator Guide.
Task Purpose: Activate the Continuous Discovery agent to perform a ping sweep of a designated subnet. Continuous Discovery is an event-driven, continuous process used to discover dynamic environments. This method serves a multi-tiered architecture, enabling discovery across the enterprise. 1 2 From the MCC, drill down to the subnet discovered in the Command Line Discovery interactive demonstration. Note the single object. Open Windows services and start: 3 CA- Continuous Discovery Agent CA- Continuous Discovery Manager
Return to the MCC. Observe the new subnet populated automatically by the Continuous Discovery engine.
Notes
4-17

Interactive Demonstration 4 Navigate to your server. Drill down to the first object under Unispace. This is the Continuous Discovery Agent. In the right pane, select Properties from the list. Click the RunTime tab. Note the Managed Subnets.
Task Summary
Continuous Discovery is event-driven and ongoing. It continuously scans your network in real-time mode for new devices or changes in IP addresses of existing devices. You can configure Continuous Discovery for optimal load balancing between the Discovery Agents and the Discovery Manager. In this task, you learned that Classic and Continuous Discovery methods name devices differently. As a result, you know how to avoid duplicating services. In the next task, you will reclassify objects.
Notes
4-18
Discover System and Network Devices Task 3: Reclassify Objects
Slide 4-9
Task 3: Reclassify Objects

The behavior and state of the objects are defined by class properties. The two types of properties are described in the following table: Property Type Class-level Description Class-level properties are the same for all objects that belong to a particular class. When a class is defined, properties are declared that determine the state and behavior of objects belonging to that class. For example, class-level properties can define the basic size, color, or look of an icon or model. The value of the class-level property is the same for all objects derived from the class and should not be modified. Instance-level properties define the attributes and relationships for a particular object derived from a class. When a class is instantiated, an object derived from that class is created at run time. The object has class-level properties and instancelevel properties. This is because the values for instance-level properties are almost always unique for every object.
Instance-level
Notes
4-19

Describe the Relationship Between the MDB and Managed Objects
Slide 4-10
Describe the Relationship Between the MDB and Managed Objects

It is tedious to manually locate, categorize, and catalog objects in an IT infrastructure. With Classic Discovery, you can locate managed objects automatically. Classic Discovery enables you to scan the IT infrastructure and locate the objects. You can also extract information about the managed objects and organize them in an easy-to-view format. WorldView objects are held in the MDB. During the Classic Discovery process, the MDB is populated with managed objects, their characteristics, status information, and management methods. A managed object is an entity used to monitor and control IT infrastructure entities. A managed object can represent hardware, software, or Business Process Views. Managed objects have the following characteristics:
Object Methods: These determine the kind of behavior exhibited by the object. For example, an object modeling a satellite might have a method that calculates the position of the satellite displayed on a monitor. Object Properties: These are related to the state of an object. An object usually has a set of possible states determined by its properties.
The MDB class hierarchy shows the relationship between classes. The tree structure begins with a single root class, ManagedObjectRoot, which contains all predefined classes. Classes in TNGRoot contain further subclasses. TNGRoot has only class-level properties and no instance-level properties.
Notes
4-20
Discover System and Network Devices When a Device Is Not Classified
Slide 4-11
The following property inheritance rules are enforced as follows: Rule Class-level inheritance Description The definition of a subclass can override the classlevel property value inherited from its superclass, but not its data type or length.
Instance-level inheritance The definition of a subclass can overwrite a superclass instance-level property default value, but not its data type, length, required flag, or key flag.
Slide 4-12
When a Device Is Not Classified

In the event that a device is not classified, the following checklist and suggested actions can assist you:
The SNMP get community name is incorrect. Action: Use ObjectView to verify. The SNMP agent on the device is not running. Action: Bring up the SNMP agent on the device. There is a conflicting IP address in the system. Action: Remove the conflicting device from the system. The SNMP agent is accepting SNMP traffic from only a particular set of IP addresses. Action: Check the Access Control List found in the SNMP security setup utility of that device. This is normally used as a form of security to enable only the Network Management software, running on particular IPs, to access and change the SNMP information. The actual utility and method for changing security is device-dependent and vendor-supplied.
Notes
4-21

If a particular device was discovered with Continuous Discovery but placed in the UNCLASSIFIED_TCP class, then one of two situations has occurred: No classification rule can be successfully executed for the device. In this case, you should create a new rule or class that enables discovery to correctly identify the device. To add a new rule, edit the classification configuration files located in the Discovery\Config subfolder. If no appropriate class exists for the device, create a new class using the WorldView Class Editor. After the rules and classes are added, reclassify the UNCLASSIFIED_TCP object(s) to the newly created classes or run Classic Discovery again.
Task Purpose: Reclassify an unrecognized device as a Windows_NetServer. Objects in the repository must be recognized in the proper class structure to be managed by the DSM. 1 2 3 4 5 6 7 Open the MCC. In the left pane, expand TCP/IP Network the object you want to reclassify. YourServerName and locate
Right-click the object and choose Reclassify. The Reclassify dialog appears. Scroll down the list until you find the class you want to reclassify as the object. In this case, select Host Windows_NetServer and click OK. Select the object in the left pane to see the reclassification change in the Properties view in the right pane. On the Main tab, select Host from the Alarmset Name list. On the SNMP tab, type Host in the Pollset Name field.
Notes
4-22
Discover System and Network Devices Task Summary
Task Summary
The state and behavior of a managed object is defined by class properties. The two types of class properties are class-level and instance-level. The discovery process enables you to extract class property information about managed objects. Sometimes, objects are not discovered during the discovery process. In this task, you learned how to reclassify an object when it is not discovered.
Notes
4-23

Assessment
Assessment
1 Which type of objects are placed in the MDB as the result of discovering devices on the network? a b c d 2 Classic objects System objects Managed objects Integrated objects
Which command triggers the underlying program when discovery is executed? a b c d DISCSRV DSCVRBE DSCVRNET DSCVMNTR
Which naming convention is supported by Classic Discovery but is not available in Continuous Discovery? a b c d sysNames DNS names SNMP names Fully qualified domain names
Notes
4-24
Discover System and Network Devices Assessment
Which condition can prevent a device from being discovered and classified correctly? a b c d SNMP not started on the DSM Messenger service not started Discovery configured to search for multiple community strings SNMP agent accepting SNMP traffic from only a particular set of IP addresses
Notes
4-25

Module Summary
Slide 4-13
Module Summary

Perform Classic Discovery Configure Continuous Discovery Reclassify Objects
It is tedious and inefficient to manually locate, categorize, and catalog objects in an IT infrastructure, especially for a quickly evolving organization like RBC. With Common Discovery, you can locate managed objects quickly and easily. The two types of Common Discovery are Classic Discovery and Continuous Discovery. Classic Discovery enables you to scan the IT infrastructure and locate managed objects automatically. With Classic Discovery, you can also extract information about the managed objects and organize them in an easyto-view format. Continuous Discovery is event-driven and ongoing. It employs a manager and agents that continuously scan your network in real-time mode for new devices or changes in IP addressing of existing devices. In this module, you performed Classic Discovery, configured Continuous Discovery, and reclassified objects. In the next module, you will optimize network visualization.
Notes
4-26
5
5-1

Module Objectives
Slide 5-1
Module Objectives

Navigate the MCC Create Business Process Views Prioritize Managed Objects by Severity with Billboards Prioritize Business Impact of Alerts with BPVM
Module Overview
CA has performed extensive analysis on user interfaces to determine how various roles in a data center work effectively. The result is a variety of interfaces tailored for specific users. Using this role-based management methodology, you can easily navigate IT complexity using scoped and meaningful visualizations. Unicenter NSM provides system administrators and IT managers with a familiar and intuitive graphical tree structure for the most productive navigation of rolebased administrative tasks. The ability to view elements from an application perspective will help RBC align their network and systems infrastructure with their business priorities. In this module, you will optimize network visualization with the MCC, Business Process Views, billboards, and Business Process View Management (BPVM).
Notes
5-2
Optimize Network Visualization Task 1: Navigate the MCC
Slide 5-2
Task 1: Navigate the MCC

The MCC is the center for visualization, configuration, and monitoring in Unicenter NSM. You can use it to navigate the WorldView 2D Map and Topology tree views, monitor event messages, look into details of Agent Technology, start network and system discovery, and create reports. Integration with WorldView, through icons and Business Process Views, is also crucial for interaction between Unicenter NSM and other applications. The MCC automatically delivers the most valuable data relevant to any asset of interest. You can customize individual views to create an effective and personal working space. The MCC Filter Editor is a GUI editing tool for creating and modifying filters and queries. The view type of the Filter Editor enables you to manage and display filters in the MCC. Using the Filter Editor, you can create, delete, rename, and edit filters. It supports drag-and-drop, copy-and-paste, and delete and rename functions for filters.
Slide 5-3
Task Purpose: Create an emphasis filter to emphasize a subset of objects based on class. 1 2 3 4 5 6 7 Open the MCC. In the left pane, select Filters from the View type list. Right-click WorldView and choose New Filter. Expand WorldView, right-click New Filter_0, and choose Rename. Change the New Filter_0 name to Cisco Switches. In the right pane, select CISCO_SWITCH from the Select Class list. Click Save Changes.
Notes
5-3

Interactive Demonstration 8 9 In the left pane, select Topology from the View type list. Select YourServerName and choose View Switches. Apply Emphasis Cisco
10 Expand TCP/IP Network and drill down to your Cisco Switches. Observe the Filter icon beneath WorldView and confirm that all objects are dimmed except those meeting the filter criteria. In the next interactive demonstration, you will apply an emphasis filter to view Critical objects.
Task Purpose: Apply an existing emphasis filter to view Critical objects only. 1 2 In the MCC, choose View Objects. Apply Emphasis Critical Managed
Drill down to the Windows System Agent. Observe that all objects are dimmed except those meeting the filter criteria.
Task Summary
The MCC is the center for visualization, configuration, and monitoring in Unicenter NSM. The MCC automatically delivers the most valuable data relevant to any asset of interest. You can customize individual views to create an effective and personal working space. In this task, you navigated the Topology tree and 2D Map in the MCC. You also created and applied emphasis filters in the MCC. In the next task, you will create static and dynamic Business Process Views.
Notes
5-4
Optimize Network Visualization Task 2: Create Business Process Views
Slide 5-4
Task 2: Create Business Process Views

A Business Process View is a logical group of managed objects you create based on any criteria you determine, such as geographic location, business process, or security. Business Process View acts as a filter that displays only objects relevant to the management of resources for a specific business requirement. A Business Process View helps you monitor and manage designated segments of your enterprise. Business Process View is the way you can logically group the constituent resources that perform some business critical process, such as accounting or personnel. Business Process View is an effective way to alert you that a key link in a chain of resources is encountering a problem that can impact the business. The contents of a Business Process View can represent anything important to your process execution. You can group these views by geographical locations, organizational structures, applications, resource features, or other similar criteria. The Business Process Views you create are visually represented as separate folders on the 2D Map. A Business Process View is itself a managed object and is stored in the MDB. It is accessible to any user of your 2D Maps. Business Process Views are added to the 2D Map with the Tool Palette. The same adding and modifying procedures that apply to all objects apply to Business Process Views. To monitor the condition and status of objects, you can set triggers and thresholds and intercept messages generated by programs participating in the process. These views can assist you in the early detection and prevention of problems. When a problem does occur, Business Process View provides an immediate, graphical view of the source and severity of the problem.
Slide 5-5
Notes
5-5

Task 2: Create Business Process Views
Slide 5-6
You can create various types of Business Process Views using a variety of methods:
Static Business Process Views are typically defined manually by the user. They are simply a collection of objects that are related in some way. For example, by class, or perhaps by the business process or service they support. Dynamic Business Process Views are populated automatically, based on policy defined for that Business Process View. Two main dynamic Business Process View tools are Dynamic BPV and Dynamic Container Service. They enable you to define policy that results in objects being added and removed automatically; for example, to show all critical Microsoft Windows servers, all unmanaged switches, or all devices in the IP range 172.16.10.100200. Smart Business Process Views (SmartBPVs) are based on communication protocols. These are collections of devices that are communicating on a given port or protocol; for example, an HTML Business Process View, a SQL Business Process View, or a Microsoft Exchange Business Process View. SmartBPV uses packet-sniffing technology from Sonar to detect who is talking to whom using what protocol, and to dynamically update the Business Process Views accordingly. SmartBPV is available on Microsoft Windows only. The Domain Business Process View contains domain objects. Each domain object represents the Agent Technologies DSM component. The WBEM Business Process View is created by the discovery process and contains all the WBEM objects, devices that provide WBEM data, found on your network. The Deployed Objects Business Process View contains the state of the WorldView component and the Enterprise Management components. Vlan Domain View, OSPF Network, and additional Business Process Views, are created by Advanced Network Management. For more information about these Business Process Views, refer to the Advanced Network Management documentation.
The following Business Process Views are created automatically:

Notes
5-6
Optimize Network Visualization Interactive Demonstration
Task Purpose: Create a static Business Process View containing servers from the classroom environment. 1 2 3 4 5 6 7 8 9 Open the MCC. Expand your server and select ManagedObjectRoot. In the right pane, select the 2D Map view type. Click Tool Palette. The Tool palette appears at the right of the screen. Expand Classes\ManagedObject. Click BusinessView. A preview of the tool appears at the bottom of the Tool Palette. Drag the BusinessView preview to the 2D Map and drop it in the ManagedObjectRoot container. Right-click the new BusinessView object and choose Open Viewer Properties. On the Main tab, type Classroom in the Name and Label fields and close the Properties window. Close the Tool Palette.
10 In the left pane, drill down to the segment level of your subnet. 11 In the right pane, select the Explorer view type. 12 Choose View List. 13 While pressing and holding the SHIFT key, select all the objects in your classroom and then right-click and choose Copy. 14 In the left pane, right-click the Classroom Business Process View and choose Paste. In the next interactive demonstration, you will create a dynamic Business Process View.
Notes
5-7

Task Purpose: Create a dynamic Business Process View. 1 2 3 4 5 Open the MCC. At the top level of the Topology hierarchy, expand the WorldView MDB labeled with your host name. In the right pane, select the 2D Map view type. Click Tool Palette. The Tool Palette appears at the right of the screen. Expand Classes\ManagedObject\BusinessView and click DynamicBPV. A preview of the tool appears at the bottom of the Tool Palette. Drag the Dynamic BPV preview to the 2D Map and drop it in the ManagedObjectRoot container. Close the Tool Palette. In the left pane, select Business Process Views from the View type list. At the top level of the Business Process Views hierarchy, expand the WorldView MDB labeled with your server name. Select the New Dynamic BPV that was created.
6 7 8 9
10 In the right pane, close all but one of the viewers. Switch the remaining viewer to the 2D Map view. 11 In the left pane, right-click New Dynamic BPV and choose Add Viewer Properties. 12 In the Properties right pane view, type Critical Windows_NetServers in the Label field. 13 In the right pane, select the Dynamic BPV Editor view. 14 On the Main tab, select Windows_NetServer from the Select Class list. 15 From the Choose Property list, select Propagated Sev. 16 Select Critical from the status list.
Notes
5-8
17 Click Save Changes. 18 In the right pane, select 2D Map from the View type list. 19 Observe the critical Windows_NetServer objects in the 2D Map. Note: If no servers are in the Critical state to populate the Dynamic BPV, create a Critical state on your host server to test the configuration.
Task Summary
A Business Process View helps you monitor and manage designated segments of your enterprise. Business Process Views can assist you in the early detection and prevention of problems. When a problem does occur, the Business Process View provides an immediate, graphical view of the source and severity of the problem. In this task, you examined the purpose and benefits of Business Process Views and created static and dynamic Business Process Views. In the next task, you will create a billboard.
Notes
5-9

Task 3: Prioritize Managed Objects by Severity with Billboards
Slide 5-7
Task 3: Prioritize Managed Objects by Severity with Billboards

Billboard objects enable you to keep up-to-date information about critical objects in view at all times. You can take a quick look at the billboard to see if any of the children of a parent object are critical.
Slide 5-8
By default, billboards are automatically populated with objects in a Critical state. If the Critical status of an object changes to Normal, that object is removed from the billboard. A status that changes from Normal to Critical causes the affected object to appear in the billboard automatically. To create a billboard, click the Tool Palette icon and choose Billboard from the Managed Object tree, then drag it to the 2D Map. The best practice is to place billboards on the segment level. Note: Do not place billboard objects at the Managed Object level.
Task Purpose: Use billboards to readily identify critical objects based on userdefined parameters. 1 2 3 Open the MCC. In the left pane, from the View type list, select Topology. Drill down to the IP_Subnet. In the left pane, expand WorldView\YourServerName\ManagedObjectRoot\TCP/IP Network. Under the classroom IP_Network object, locate and select the classroom IP_Subnet. In the right pane, select the 2D Map view type. Click Tool Palette. The Tool Palette appears at the right of the screen. In the Tool Palette, expand Classes\ManagedObject. Click Billboard. A preview of the tool appears at the bottom of the Tool Palette.
4 5 6
Notes
5-10
7 8 9
Drag the New Billboard preview to the 2D Map and drop it in the IP_Subnet container. In the left pane, expand the segment and scroll down to identify the New Billboard. Right-click New Billboard and choose Add Viewer Properties.
10 On the Main tab, type Critical_Objects_in_Segment in the Name field and Critical Objects in Segment in the Label field and close the Properties view window. 11 Close the Tool Palette. 12 Observe that the Billboard automatically populates with objects from the segments in a Critical state.
Task Summary
Billboard objects keep up-to-date information about critical objects in view at all times. You can take a quick look at the billboard to see if any objects are in a Critical state, and then quickly resolve any issues that you find. In this task, you used billboards to readily identify and manage critical objects. In the next task, you will establish BPVM priorities.
Notes
5-11

Task 4: Prioritize Business Impact of Alerts with BPVM
Slide 5-9
Task 4: Prioritize Business Impact of Alerts with BPVM

BPVM is a component that enables you to create Business Process objects to monitor and control your network. You can use Business Process objects to apply new rules to your system to determine how state propagates from existing WorldView objects, using methods ranging from simple counters to complex correlation rules. BPVM enables you to implement policies to make automated high-level decisions about key resources and set warnings and critical events when problems are detected. BPVM is available on Microsoft Windows only. For example, you can have a Business Process View that includes three web servers. Failure of one web server can be significant, but it might not have an adverse impact on your business operations. Failure of two web servers can have a major business impact, possibly bringing operations to a halt if the two servers remain offline for an extended time period. Using BPVM, you can define a rule that represents the failure of one server as a Warning state and the failure of two servers as a Critical state requiring immediate action. Business Process objects represent a combination of other objects. Each Business Process object is associated with a target object, such as an existing Business Process View. Business Process objects derive their state by applying rules to the associated target. Business Process objects can have any number of rules associated with them. You can use the Business Process View Management Configuration Wizard to configure Business Process objects. Rules determine the Business Process object state. You can configure any number of rules for each Business Process, and you can combine rules to provide sophisticated forms of correlation for the contents, or children, of the target object. Each rule is represented by an object in the MDB, under the associated Business Process, and thus independently influences the propagated process state. Rules report all threshold breaches to a designated Event Console to support automated actions.
Slide 5-10
Notes
5-12
Slide 5-11
BPVM provides several kinds of rules to influence the state of the Business Process from different aspects of the target object and its children as follows:

Child Count Rule State Count Rule Propagation Thresholds Rule Boolean Logic Rule Child Update Rule
Task Purpose: Establish BPVM. Administrative personnel have found static and dynamic Business Process Views highly effective in isolating problems in complex business systems that rely on a heterogeneous hardware and software environment. Any critical object in one Business Process View causes that Business Process View to report as Critical. However, there is a need to define correlation rules that apply to multiple servers in a Business Process View. For example, when more than four web servers report Critical in a Web Server Farm, the entire Web Server Farm has an outage. BPVM will more readily identify system outages that have a business impact.
Establish File Path for BPVM

1 Click Start and then choose Programs Computer Associates Unicenter NSM WorldView Business Process View Management Init File Path. In the Unicenter Business Process View Management Configuration dialog, click Apply. When asked if you want to create the directory now, click Yes.
2 3
Notes
5-13

Create Objects
4 5 6 7 8 Open the MCC. In the left pane, expand WorldView\YourServerName and select ManagedObjectRoot. In the right pane, select the 2D Map view type. Click Tool Palette. The Tool Palette appears at the right of the screen. In the Tool Palette, expand Classes\ManagedObject and click BusinessView. A preview of the tool appears at the bottom of the Tool Palette. Drag the BusinessView preview to the 2D Map and drop it in the ManagedObjectRoot container.
10 In the left pane, expand WorldView\YourServerName\ManagedObjectRoot and select New BusinessView. 11 In the right pane, select the Properties view type. 12 On the Main tab, type Web_Farm in the Name field and Web Farm in the Label field. 13 Select the 2D Map view type. 14 Click Tool Palette. 15 In the Tool Palette, expand Classes\ManagedObject\Host and click Windows_NetServer. A preview of the tool appears at the bottom of the Tool Palette. 16 Drag the Windows_NetServer preview onto the 2D Map and drop it in the Web Farm container. 17 In the left pane, select New Windows_NetServer. 18 In the right pane, select the Properties view type. 19 On the Main tab, type Web_Server_1 in the Name field and Web Server 1 in the Label field.
Notes
5-14
20 Close the Properties view window. 21 Repeat steps 16 to 19 five more times. You will have a total of six new Microsoft Windows NetServers.
Configure BPVM Rules

22 Click Start and then choose Programs Computer Associates Unicenter NSM WorldView Business Process View Management Configuration Wizard. 23 Click Next to begin the configuration. 24 Click Browse to select a repository. 25 In the Unicenter NSM dialog, select your MDB from the list and click OK. a b For an Ingres MDB, the Repository name will be WV_YourServerName. For a Microsoft SQL Server MDB, the Repository name will be YourServerName.
26 Type your nsmadmin username in the User name field. 27 Type unicenter in the Password and Password Confirm fields. 28 Click Test Sign-On. 29 When the successful connection message appears, click OK. 30 Click Next. 31 Select Verbose from the Level list. 32 Select Send Events to Event Management. 33 Select Critical Errors from the Event Level list. 34 Type YourServerName in the Event Management Node field and click Check Status. 35 When the successful contact message appears, click OK.
Notes
5-15

Interactive Demonstration 36 Select Add Local Timestamp. 37 Click Next. 38 Click Add. The Business Process Policy dialog appears. 39 Select BusinessView from the Class list. 40 Click Select. The Select Target Object dialog appears. 41 Select Web_Farm from the list and click OK. 42 Click Add State Count Rule. 43 In the Description field, type: Greater than 4 Critical Web Servers indicates the Business Process has failed 44 Type 3 in the Warning Threshold field and select Warning from the list. 45 Type 4 in the Critical Threshold field and select Warning from the list. 46 Click the button to the right of Label to populate the field. 47 Click OK. 48 Click OK to close the Business Process Policy dialog. 49 Click Next. 50 Click Save. 51 When asked if you want to send the configuration changes to the engine, click Yes.
Test the BPVM Rules

52 From the MCC, in the left pane, select Business Process Views from the View type list. 53 Select the Web Farm Business Process View. 54 In the right pane, select the 2D Map view type. 55 In the left pane, select Web Server 1.
Notes
5-16
56 In the right pane, select Properties from the View type list for Web Server 1. 57 Click the Status tab. 58 Scroll down and click Warning from the Severity list. 59 Repeat steps 55 to 58 for Web Servers 2 to 4. 60 In the left pane, expand Business Processes and select the StateCount Business Process for Web Farm. 61 In the right pane, select 2D Map from the View type list. 62 Confirm that the StateCount[W=3(Wrn)/C=4(Wrn)] icon is red, indicating a severity of Critical. Note: The overall severity for the Web Farm Business Process View is still Warning.
Add a New Rule

63 Click Start and then choose Programs Computer Associates Unicenter NSM WorldView Business Process View Management Configuration Wizard. 64 Click Next. 65 Click Next. 66 Click Next. 67 Select Business Process for Web Farm and click Edit. 68 Click Add and then select Propagation Threshold Rule from the list. 69 Type 2 Critical Web Servers indicates a severity of Critical. 3 Down Web Servers indicates a severity of Down. in the Description field. 70 Type 2 in the Critical field.
Notes
5-17

Interactive Demonstration 71 Type 3 in the Down field. 72 Click the button to the right of the Label field to populate the field. 73 Click OK. 74 Click Add and then select Boolean Logic Rule from the list. 75 Type 1or2 warning=warning - 5and6 down=critical in the Label field. 76 Type If Web Servers 1 OR 2 are Warning this indicates Warning. If Web Servers 5 AND 6 are Down this indicates Critical. in the Description field. 77 Under the Warning section, click Add. 78 Select Windows_NetServer from the Object Class list. 79 Click Select and choose Web Server 1 as the Object Name. 80 Click OK on the Select Target Object window. 81 Select Object is child of Target and meets the following Condition. 82 Select Equal To (==) and Warning from the Propagated Severity list. 83 Click OK on the Logical Conditions Specification window. 84 In the Warning section, click Add again. 85 Add the same logical condition for Web Server 2. 86 In the Warning section, set the AND/OR toggle key to OR. 87 Under the Critical section, click Add. 88 Add a logical condition that Web Server 5 is equal to Down. 89 Add a second Logical condition in the Critical section that Web Server 6 is equal to Down. 90 In the Critical section, set the AND/OR toggle key to AND. 91 Click OK on the Business Process Rule Definition window. 92 Click Add and select Child Update Rule.
Notes
5-18
93 Change the Warning threshold to 120 seconds and the Critical threshold to 180 seconds. 94 Click the button beside the Label field to populate the field. 95 Click OK. 96 Click OK on the Business Process Policy window. 97 Click Next. 98 Click Save. 99 Click Yes to send configuration changes to the engine. 100 From the MCC, open the Web Farm folder. 101 Using Properties, change the severity of Web Servers 4, 5, and 6 to DOWN. 102 Return to the MCC to observe the effect on the icons representing the following three new rules: The Web Farm Business Process View will reflect a Down state. Propagate will reflect a Down status. The Business Process will reflect a Down state.
Task Summary
BPVM is a component that enables you to create Business Process objects to monitor and control your network. BPVM enables you to implement policies to make automated high-level decisions about key resources and set warnings and critical events when problems are detected. In this task, you used BPVM to apply new business rules to a system.
Notes
5-19

Assessment
Assessment
1 What is the center for visualization, configuration, and monitoring in Unicenter NSM? a b c d 2 DSM MCC Unicenter Explorer Business Process View
Which type of Business Process View is manually defined by the user? a b c d Static Smart Visual Dynamic
Which right pane view in the MCC must be displayed to access the Tool Palette? a b c d Explorer 2D Map Class Editor Association Browser
Notes
5-20
Optimize Network Visualization Assessment
Which container in the MCC is automatically populated with objects in a Critical state? a b c d Host Agent Billboard Business Process View
Notes
5-21

Module Summary
Slide 5-12
Module Summary

Navigate the MCC Create Business Process Views Prioritize Managed Objects by Severity with Billboards Prioritize Business Impact of Alerts with BPVM
In this module, you determined that Unicenter NSM displays overview and detailed views of infrastructure elements with a single GUI, the MCC. These visualizations help you identify and understand information relevant to particular operational roles. The ability to view elements from an application perspective helps organizations like RBC align network and system infrastructure with business priorities. Identifying ways to optimize network visualization with Business Process Views, billboards, and BPVM will make your systems monitoring efforts more effective. In the next module, you will identify how to optimize network visualization with the Unicenter Management Portal (UMP).
Notes
5-22
6
Automate Response to Events and Alerts
6-1

Module Objectives
Slide 6-1
Module Objectives

Describe Event Management Architecture Filter Events with Event Console Logs Respond to Events by Creating Message Records and Actions Process Significant Events with the AMS Communicate Event Status with the UNS
Module Overview
Event Management is the focal point for managing enterprise events from a variety of sources throughout RBCs network. With Event Management, you can monitor event activity and immediately respond to events as they occur. You can also filter messages to retrieve specific information about a particular event. Determining a course of action based on when an event occurs can be critical to its proper handling. By defining message record and action profiles, you can identify events that are important to RBCs operations and define the special processing that Unicenter NSM performs when encountering them. Through the MCC interface, Event Management is now more integrated with other components, such as the Alert Management System (AMS), Unicenter Notification Service (UNS), and other Unicenter NSM features. This consolidation enables fewer staff to manage more of the infrastructure. In this module, you will use Event Management components to monitor and consolidate event activity from a variety of sources and to focus on and manage the highest severity events.
Notes
6-2
Automate Response to Events and Alerts Task 1: Describe Event Management Architecture
Slide 6-2
Task 1: Describe Event Management Architecture

The Event Management architecture, shown in the following graphic, is the integration of multiple components. This integration enables instant awareness of status changes and problems. You can manage events throughout your organization with Event Manager components. Use the Console Log to monitor events from various platforms and devices, send messages to other computers for processing, and automate actions for any event that requires special attention.
Slide 6-3
Notes
6-3

Event Management Daemon (caoprdmn)
Event Management Daemon (caoprdmn)

The Event Management Daemon (caoprdmn) process, shown in the following graphic, is the heart of Unicenter NSM Event Management. The caoprdmn process evaluates events, applies policies, and writes messages to the Unicenter NSM Event Console Log. You configure this process to forward messages to other servers and initiate defined actions. The caoprdmn process operates based on policies you create, which are stored in the in-memory Decision Support Binary (DSB).
Slide 6-4
Notes
6-4
Automate Response to Events and Alerts Event Management NT EventLog Reader (caoprlog)
Event Management NT EventLog Reader (caoprlog)

The Event Management NT EventLog Reader (caoprlog) process performs a simple, but critical, function. This process, shown in the following graphic, forwards messages from Microsoft Windows 2000/NT logs and delivers them to the caoprdmn for processing. A single thread is opened by caoprlog to process each of these logs. This service is automatically performed without user intervention.
Slide 6-5
Notes
6-5

Event Management Messages
Event Management Messages

The Unicenter NSM Event Manager captures messages from network and system resources in your IT infrastructure, which can include:

System Events: Events from the caioprlog process, such as licensing and shell incidents SNMP Traps: The Event Management Trap Daemon (catrapd) receives traps sent by SNMP agent enabled devices and delivers them to the Event Management Daemon (caoprdmn) for processing. DSM Messages: State change messages generated by the DSM concerning the condition of an agent CAICCI Events: Notification from other Enterprise Management Managers, including other Event Managers, concerning significant actions or policies they have initiated Direct Interface: Using the CA Write-To-Operator (CAWTO) and CA WriteTo-Operator-Reply (CAWTOR) commands provides a communication interface directly into the caoprdmn
Notes
6-6
Automate Response to Events and Alerts Event Management Messages
Slide 6-6
The Event Management process is shown in the following graphic:
Notes
6-7

Administrative GUI (Access Event Console Logs)
Administrative GUI (Access Event Console Logs)

The Unicenter NSM Event Console is used to view the Unicenter NSM Event Console Log, as shown in the following graphic. Each day, at midnight, a new Console Log is created for that day. All messages written to these daily logs come from the caoprdmn process. By default, the daily logs are never deleted.
Slide 6-7
Notes
6-8
Automate Response to Events and Alerts Event Management Database
Event Management Database

Event Management policy is stored in the MDB as Message Records and Message Record Actions. Event Management loads this policy into the memory resident Decision Support Binary (DSB) when it starts. Accessing the policy in memory, or cache, is more efficient than getting it directly from the MDB every time it is needed. If changes are made to the policy in the MDB, the DSB can be refreshed by running the opreload command or by recycling Event Management.
Slide 6-8
Notes
6-9

Decision Support Binary (DSB)
Decision Support Binary (DSB)

Event Management loads its policy from the MDB into the DSB when it starts and also when the opreload command is executed. If changes are made to the policy in the MDB, the DSB can be refreshed by running the opreload command or by recycling Event Management.
Slide 6-9
Notes
6-10
Automate Response to Events and Alerts Identify Enterprise Management Services
There are two copies of the DSB. One DSB is placed in memory. This in-memory DSB is where Event Management policy is placed for caoprdmn to perform queries against it. These queries are performed at the speed of your server system bus. The other DSB, named caopr.dsb, is stored on the local disk. The default location of caopr.dsb is %CA_TND_HOME%logs. If the MDB is unavailable, the in-memory DSB is loaded from the local disk DSB that was created during the last successful MDB policy load. Note: Unicenter NSM environment variables determine whether or not Event Management will retry the opreload process. CA_OPR_DB_INTERVAL determines the length of time between retries. CA_OPR_DB_RETRIES determines the number of retry attempts. If Event Management is configured so that retries will occur, a DSB will be loaded and active as soon as a DSB or an Event Management database is contacted.
Slide 6-10
Identify Enterprise Management Services

Enterprise Management is a collection of components that provide automation and additional control over your enterprise. Event Management is the component that provides a complete view of ongoing processing. Every running program or user process can use this component. Event Management enables you to identify significant events or monitor for unusual conditions and then automatically take actions the user has defined.
UNIFSTAT
The UNIFSTAT utility displays the status of Enterprise Management functions. There are several parameters that can be used with this command, including the redirect (>) and pipe (|), as well as the following command-specific parameters: unifstat [-h -r -p -v] [-c {component}] [-u {subcomponent}] [-s {node}]
Notes
6-11

UNIFSTAT The command-specific parameters are described in the following table: Parameter -h -v -r -c -u -p -s Description Generates help information Enables verbose mode Generates requisite information Generates component information Generates subcomponent information Generates process information associated with components and subcomponents Retrieves requested information from a specific (remote) server
The asterisk (*) can be used for partial component names. The default setting if no arguments are given (UNIFSTAT command only) is -r -p -c* -u* and it retrieves the status of Enterprise Management functions on the local computer. The following tables list all Enterprise Management components and subcomponents monitored by the UNIFSTAT command. The COM component controls these subcomponents: Subcomponent DIR RTR CAL TRP Description Directory Services Router Services Calendar SNMP Trap Services
Notes
6-12
Automate Response to Events and Alerts UNIFSTAT
Subcomponent ENF EMSRVC MDMGR
Description Event Notification Facility EM Services Router Mobile Device Manager
The OPR component controls these subcomponents: Subcomponent EVTD EVTR WMS SAF Description Event Management Daemon Event Management NT Event Log Reader Event Management Wireless Messaging Store and Forward
The SCH component controls these subcomponents: Subcomponent SCHM SCHA Description Job Server Job Agent
Notes
6-13

UNICNTRL The SEC component controls these subcomponents: Subcomponent SECMAIN SECAUDIT SECLOGON Description Security Main Security Audit Security Logon
UNICNTRL
The UNICNTRL utility command controls Enterprise Management functions. Use this command to start and stop Enterprise Management components. When you use this command, it must be followed by a command and keyword: unicntrl [Command] [Keyword] The commands are described in the following table: Command START STOP PAUSE Description Starts the specified component on the node named in SERVER Stops the specified component on the node named in SERVER Pauses the specified component on the node named in SERVER; this option is available only on Microsoft Windows NT Resumes running the specified component on the node named in SERVER; this option is available only on Microsoft Windows NT
RESUME
Notes
6-14
Automate Response to Events and Alerts UNICNTRL
The keywords are described in the following table: Keyword COM OPR SCH SEC UNI Description Common Unicenter components; this keyword applies to Microsoft Windows only Event Management function Job Management function Security Management function Starts or stops all Unicenter Enterprise Management functions; this keyword applies to Microsoft Windows only Starts or stops all Unicenter Enterprise Management functions; this keyword applies to Microsoft Windows only
ALL
The following options can only be used with Microsoft Windows operating systems: Option SERVER TRACE Description Specifies a remote computer you want to control Shows a trace of the specified component on the remote computer
Notes
6-15

Task Purpose: Customize Event Management security settings. By default, the local administrator is the only account with permission to launch commands from Event Management. Note: The following settings are for classroom use only; they are not suggested or recommended for any production environment. The instructor will explain methods for a more secure environment. These steps are solely for simplifying the learning process in the classroom. 1 2 At the command prompt, type caugui conlog and press ENTER. The EM Console Log opens. Type opreload in the Command field and press ENTER. Note: Complete the following steps only if you get the console message Command execution denied: Not authorized by security. 3 4 5 6 7 8 9 Minimize the EM Console Log. At the command prompt, type caugui settings and press ENTER. The EM Settings dialog appears. On the Event Management tab, scroll down and select Users authorized to issue commands, and type * in the Settings field. When prompted, click Yes to save the settings. Select Check authorized users list for MSGRECORD\MSGACTION database updates and then select YES from the Settings list. When prompted, click Yes to save the settings. Scroll up to identify the entry for Excluded Windows Event Logs. Type Security in the Setting field. Click Yes to confirm the change.
10 Close the EM Settings dialog.
Notes
6-16
Automate Response to Events and Alerts Define the CAICCI
11 At the command prompt, type unicntrl stop opr and press ENTER. 12 Type unicntrl start opr and press ENTER. 13 Return to the EM Console Log. 14 Type opreload in the Command field and press ENTER. 15 Observe whether the opreload command launches successfully.
Slide 6-11
Define the CAICCI

The CA International Common Communications Interface (CAICCI) is a proprietary CA messaging system. CAICCI enables Unicenter NSM components to communicate with CA components on another computer in a computing environment that includes a heterogeneous mix of computers. Therefore, CAICCI provides intra-application, inter-application, and server-to-server communication.

Intra-application communication: CAICCI enables Unicenter NSM components to communicate with each other. Inter-application communication: CAICCI enables Unicenter NSM components to communicate with other CA products. Server-to-server communication: CAICCI enables Unicenter NSM components to communicate with a Unicenter NSM component or any other product executing on another computer. This can include a heterogeneous mix of computers.
Notes
6-17

CAICCI Communication Ports The CAICCI for Microsoft Windows platforms is shown in the following graphic:
Slide 6-12
Slide 6-13
CAICCI Communication Ports

When Enterprise Management components on a Microsoft Windows Server need to communicate with Enterprise Management components on a UNIX Server, the services of the CAICCI remote daemon (ccirmtd) are used. This communication must be performed over the same port. CAICCI uses the default port 1721. An entry is automatically placed into the following file on installation: Microsoft Windows: \Windows\system32\drivers\etc\services UNIX: \etc\services
Notes
6-18
Automate Response to Events and Alerts Cross-Platform CAICCI Configuration
Cross-Platform CAICCI Configuration

CAICCI communication is normally invisible to the user because the installation process discovers the environment and automatically configures any files required during operation. There is no customization required for communication between similar operating systems (Microsoft Windows to Microsoft Windows or UNIX to UNIX). CAICCI customization is required for cross-platform communication. The configuration file on Microsoft Windows (ccirmtd.rc) and on UNIX (ccirmtd.prf) must be configured with the requirements shown in the following graphic:
Slide 6-14
Notes
6-19

Task Summary
Task Summary
Event Management architecture is the integration of multiple components. This integration enables instant awareness of status changes and problems. In this task, you became familiar with Event Management architecture and components and used utility commands to start and stop Event Management services. You also identified how Unicenter NSM components communicate with CA components with CAICCI. In the next task, you will identify ways to view and filter events with Event Console Logs.
Notes
6-20
Automate Response to Events and Alerts Task 2: Filter Events with Event Console Logs
Slide 6-15
Task 2: Filter Events with Event Console Logs

The Event Management component provides a visualization tool for viewing the daily logs known as the Event Console. Unicenter has two administrative tools and, therefore, there are two different, but similar, Event Consoles. Both versions are fully customizable and can be tailored to suit the needs of each individual user.
Slide 6-16
MCC Event Console

To access the Console Logs using the MCC, you select Enterprise Management from the left pane options. When you attempt to access the Enterprise Management components of a particular computer, you are prompted for a user ID and password. This is the user ID and password needed to access the computer. After you have access to the Enterprise Management components on a particular computer, access the Console Logs by expanding the Event Management window, selecting Console Logs, and then selecting Launch Console Logs from the right pane. The Event Console will appear. By default, the MCC version of the Event Console has three key areas. The top window is named the Held Messages area, the middle larger window is named the Log Messages area, and the lower window is a Command area. The Command area can be used to issue commands like the Command Prompt window on your computer. Any entries made are written to the Console Log and automatically processed by the caoprdmn process, which also writes to the Console Log. Using the CAWTO and CAWTOR commands, you can generate messages and events directly. The CAWTO and CAWTOR commands can also be used from a command prompt to generate messages and events.
Notes
6-21

Log Messages Area
Log Messages Area

The Log Messages area displays the daily Console Log. It can also be used to look at previous daily logs.
Columns
The columns in the Console Log have various icons that denote the status of the selected message: The second column (Red Circle) in the Console Log represents severity. The five states available help to identify status information pertaining to a specific message. The third column (Blue Push Pin) indicates if annotations exist. The fourth column (Black Key) displays attributes associated with the message. They provide useful information for certain types of messages.
Console Message Detail

The Console Message Detail dialog appears when you double-click any message.
Message Tab
The Message tab provides a copy of the complete message. Text in the Message field can be selected and copied to create a specific Message Record. Additional detail can be found in the Date/Time and Info areas.
General Tab
The General tab provides other valuable information about the message, such as the Record ID, Node, User that generated the message, Process that initiated the message, and Tag that indicates the operating system involved.
Notes
6-22
Automate Response to Events and Alerts Held Messages Area
Attributes Tab
The Attributes tab displays information about color or Attribute Flags that are indicated in the selected column in the Console Log.
Annotations Tab
An Annotations tab provides an area to note information you want to retain. To create an annotation, select the Annotations tab, click New, and type any information you want retained with the message. A picture of a push pin will appear in the Annotation column next to the message, indicating that there is an annotation attached to the message.
Held Messages Area

The Held Messages area is for messages that require operator intervention. To remove held messages from this area, you issue an acknowledgement or reply. Held messages are automatically placed there by the established Event Management policy. Also, use the CAWTO command with the -k parameter or the CAWTOR command to manually place messages there, using the Command field or command prompt. There are two types of held messages. The first, indicated by the yellow phone in the Attributes field, is a message that requires a reply. The second, indicated by the white check mark, requires an acknowledgement.
Issuing a Reply to a Held Message

To initiate the reply required, you must right-click the corresponding message and choose Reply. The Message Reply window appears. Type the necessary information and click OK (the green check mark). The message is no longer displayed in the Held Messages area. You will see a notification in the Log Messages area, indicating a reply was issued for this specific message.
Notes
6-23

Classic Event Console
Issuing an Acknowledgement to a Held Message

To issue an acknowledgement, right-click the message and choose Acknowledgement. The message is no longer displayed in the Held Messages area. You will see a notification in the Log Messages area, indicating a reply (acknowledgement) was issued for this specific message by the operator who performed the acknowledgement.
Slide 6-17
Classic Event Console

The Classic Event Console enables you to perform almost identical functions as the Console Log but in a slightly different format. There are different choices for the toolbar, some additional custom configuration options, and the Held Messages pane does not display unless messages are present.
Console Settings
The Event Management Console can be configured to provide the optimum operating environment for the user. Configuration settings are saved to a configuration file (.cfg). Every user can have a set of configuration files.
Buttons
You can set sixteen buttons with strings. The strings can be set to run automatically when the command button is clicked or the text can be displayed at the command line. A red indicator appears on command buttons that are automatically activated.
Filters
A filter can be used to focus on important messages. However, you cannot remove information from the log using the filter. The filter can only be used to remove unwanted messages from the console display.
Notes
6-24
Automate Response to Events and Alerts Timers
Timers
Three types of timers can be configured:

The interval, in seconds, between console updates of the log data The interval, in seconds, for the Log Messages window and the Held Messages window to be scrolled to show new messages The on and off periods, in milliseconds, for a message that has a blink attribute
Miscellaneous Items
This is where the default settings for the miscellaneous items are displayed.
Columns
Change the sequence of columns by dragging them to another location. The configuration file does not preserve the order of columns.
Print
Print using the various options shown on the Print tab. Note: View/Read-only versions of the Console Logs are also available in the MCC. Select Console Logs from the Topology menu. Expand the Default Zone and Event Manager server. The logs are available by date.
Notes
6-25

Task Purpose: View events using the MCC Event Console and the Classic Event Console.
View Events with the MCC Event Console

1 2 3 4 5 6 Open the MCC. Select the Enterprise Management view. When prompted, type your Microsoft Windows administrator credentials. Expand YourServerName\Event Management and select Console Logs. In the right pane, click Launch Console Logs. In the Console Log, double-click a message to view it in more detail. The Console Message Detail dialog appears.
View Events with the Classic Event Console

7 8 From a command prompt, type caugui conlog to open the EM Console. Double-click a message to view it in more detail. The EM Console Message dialog appears.
In the next interactive demonstration, you will create a macro button in the Event Console to launch the opreload command.
Task Purpose: Create a macro button in the Event Console to launch the opreload command. 1 2 3 Open the classic EM Console. Choose Options appears. Settings. The EM Console Configuration dialog
On the Buttons tab, select Auto on line 1.
Notes
6-26
Automate Response to Events and Alerts Interactive Demonstration
4 5 6 7 8 9
Type opreload in the Label field. Type opreload in the Command field. Click Save as. Type standard in the File Name field. Click Save. Click OK.
10 Click the opreload button in the Command area. Observe the resulting message in the Log Messages area. In the next interactive demonstration, you will create filters for viewing different types of console messages.
Task Purpose: Create multiple filters for console messages. When operators try to isolate problems from a large number of servers and applications, it involves the time-consuming task of sifting through large numbers of messages on different systems and from long lists of log files. Slower response time results in downtime of critical servers and less productivity. In addition to the Unicenter NSM ability to color-code messages and hold important messages for acknowledgement, the product can be configured to filter out extraneous messages at the GUI level. Operators can select messages related to a particular server, application, process, user, OS type, or other criteria by filtering messages.
Create a Time Filter

1 2 From the EM Console, choose Options Configuration dialog appears. Select the Filters tab. Settings. The EM Console
Notes
6-27

Interactive Demonstration 3 4 5 6 7 8 9 Click New. The Filter dialog appears. From the Field list, select Time. Select Wildcard as the Pattern type. Type 00:02* in the Pattern field. Click OK. To apply the new filter, click Apply. Click OK to close the EM Console Configuration dialog and view filter results in the EM Console Log. Settings. The EM Console Configuration dialog
10 Confirm the console displays only messages between 2:003:00 a.m. 11 Choose Options appears.
12 Select the Filters tab. 13 Select the filter just created. 14 Click Disable all. 15 Click OK.
Create a Node Filter

16 From the EM Console, choose Options Configuration dialog appears. 17 Click New. The Filter dialog appears. 18 From the Field list, select Node. 19 In the Match if setting, accept equals. 20 Type YourNodeName in the Pattern field. 21 Click OK. 22 To apply the new filter, click OK. 23 Confirm the console displays only messages issued from YourServerName. Settings. The EM Console
Notes
6-28
24 Choose Options
Settings.
25 From the EM Console Configuration dialog, select the Filters tab. 26 Select the filter just created. 27 Click Disable all. 28 Click OK.
Create a Filter Based on the Message Field

29 From the EM Console, choose Options Configuration dialog appears. 30 Click New. The Filter dialog appears. 31 From the Field list, select Message. 32 Select Wildcard as the Pattern type. 33 Type *Critical* in the Pattern field. 34 Click OK. 35 To apply the new filter, click OK. 36 View results in the EM Console. Confirm the console displays only messages that indicate a Critical state. 37 Choose Options Settings. 38 From the EM Console Configuration dialog, select the Filters tab. 39 Select the filter just created. 40 Click Disable all. 41 Click OK. Settings. The EM Console
Notes
6-29

Task Summary
Task Summary
The Event Console is a visualization tool for viewing the daily event logs. Unicenter NSM has two distinct, but similar, Event Consoles. One is accessed through the MCC and the other is accessed from a command prompt. Both versions are fully customizable and can be tailored to suit the needs of each individual user. In this task, you have identified how to view and filter events with the MCC Event Console and the Classic Event Console. In the next task, you will determine how to respond to events by creating message records and actions.
Notes
6-30
Automate Response to Events and Alerts Task 3: Respond to Events by Creating Message Records and Actions
Slide 6-18
Task 3: Respond to Events by Creating Message Records and Actions

The Event Console enables you to view a real-time daily log of all events as they occur in the environment; however, the real advantage of Event Management is its ability to take specific actions when a particular event occurs. The real task is to identify which events are significant and decide what actions you want to take when those events occur. Event Management uses message records and actions to provide you with the capability to do this.
Slide 6-19
You can generate message records to identify specific events. When a match between the event and a message record occurs, the actions associated with that message record occur sequentially. The message record token number is the link between the message record and its actions. The Message id field of each message record contains the pattern matched against the event message as it appears in the Console Log. Apply wildcards in this pattern for more generalized matching. When the Event Manager receives events, the caoprdmn process looks for a match by comparing the event message string against the message records. This process is very efficient because the message records are stored in the in-memory DSB. Access message records by selecting the Enterprise Management left pane view, expanding Event Management, and selecting Messages. The Message Record Detail dialog contains the following tabs:
Criteria tab: Apply the Domain/Node, Domain/User, and Device fields to specify that matching only occurs if these conditions originated on the specified node, user, or device. Job Criteria tab: The Job Criteria tab involves Job Management-related information that presents additional granularity for the message record.
Notes
6-31

Task 3: Respond to Events by Creating Message Records and Actions
Configuration tab: The Configuration tab presents several options: Message type: Message type has two values, Message and Command. Message means it matches output strings or events in the Console Log. Command means it matches output strings generated from the Command area in the Event Console by an operator. Wildcard character: Wildcard character has two values, Multiple and Single. Multiple is the character that is employed to represent multiple characters, a word, or multiple words. Single is the character that is employed to represent a single character. Frequency: Frequency denotes the number of consecutive times, or count, that the same event must occur in a specific amount of time, or interval, before the message record is matched by the caoprdmn process. Calendar profile: A user-defined calendar displays the message record when that text is valid. Eval node: When multiple Event Managers share a single Event Management database, this field determines which Event Manager will employ this message record. Search all messages: When cleared, the Event Manager stops after the first match of a message record. When selected, the Event Manager selects all message records that match. Apply regular expression: When selected, the Event Manager employs POSIX-compliant, regular expressions to match this message record to an event. When cleared, the Event Manager employs wildcards.
Notes
6-32
Message active: This option activates and inactivates the message record. Case-sensitive: This option makes all the fields in the message record case-sensitive or case-insensitive. This does not apply to the Message id field, which is always case-sensitive.
Scan tab: The Scan tab specifies the text string of the message to be intercepted as it appears in the Console Log. The From and To fields define what column range is selected for the Start and Stop positions to perform the match.
Task Purpose: Create a Message Record Action (MRA) based on a service failure to be placed in the Held Messages area and color code it blue. System and network administrators are constantly in a reactive mode when dealing with systems events detected by the console. This is due to the lack of automation in the tools being applied. Unicenter NSM provides automated responses to events that require consistent responses. When a problem occurs, Unicenter NSM can, among other actions, automatically notify personnel, run a program, hold a message on the console, update objects in the 2D Map, color code, and execute a command and DLL subroutine. For a single event, any combination of these actions can be taken. 1 2 3 At the command prompt, type caugui conlog and press ENTER. The EM Console opens. Open Microsoft Windows Explorer and launch the batch file, Service_Failure_Trap.bat, located in the C:\Student\UR215 folder. Return to the EM Console and locate the message that results from running the Service_Failure_Trap.bat batch file. The message will indicate the spooler is in a Warning state. To open the EM Console Message dialog, double-click the message. In the Message field, select and then copy the message text.
4 5
Notes
6-33

Interactive Demonstration 6 7 Open the MCC. From the Enterprise Management view, expand YourServerName\Event Management and select Messages. Note: If prompted for authorization credentials, type administrator in the User field and type the password for the local administrator account. 8 9 In the right pane, click New. The Message Record - Detail dialog appears. Paste the message text in the Message id field and click Save.
10 Select the Actions tab. 11 Click New. The Message Record Action - Detail dialog appears. 12 Type * in the Sequence number field. 13 From the Action list, select SENDKEEP. 14 From the Color list, select BLUE. 15 Click OK. The Message Record Action - Detail dialog closes. 16 Click OK. The Message Record - Detail dialog closes. 17 Return to the EM Console. 18 Type opreload in the Command field and press ENTER. 19 Return to Microsoft Windows Explorer and launch the batch file, Service_Failure_Trap.bat, located in the C:\Student\UR215 folder. This will send the Service Failure message to the console and activate your action. 20 Return to the EM Console. Click Refresh to update the console, if necessary. 21 Verify that a blue-colored message appears in the Held Messages and Log Messages panes. 22 Close the EM Console and the MCC.
Notes
6-34
Automate Response to Events and Alerts Optimize Message Records with Wildcards
Slide 6-20
Optimize Message Records with Wildcards

The text string used in the Message id field of your Message Record is what the Event Management Daemon searches for in the DSB to find a match. It must be an exact match unless wildcards are used. Wildcards can be used to identify suitable text strings without having to specify every character. There are two wildcard characters, the word wildcard and the character wildcard. By default, the word wildcard is the asterisk (*), and the character wildcard is the question mark (?). You can replace these characters with other symbols if you want. Rules that determine the evaluation of the text string can be summarized as follows:
The Message id is evaluated against the equivalent portion of the incoming Message. If the Message id consists of five words, it is evaluated against the first five words of the incoming Message. Any additional words of the incoming Message are not considered. With respect to the evaluation process, a word is a character or group of characters bounded by a space on both sides. A word wildcard is bound by spaces and occurs in the middle or at the end of a Message id. It denotes a word of one or more characters in length. A word wildcard appended to a character or group of characters denotes zero or more additional characters. A character wildcard denotes a single character.
Notes
6-35

Task Purpose: Optimize message records with text strings and wildcards. Edit the existing message record using a wildcard that will enable the message to respond to a trap or poll. A second wildcard makes the message recognize and respond to state changes from OK. 1 2 3 4 5 6 7 8 In the EM Console Message dialog, select and copy the Service Failure message text in the Message field and then click OK. Open the MCC. In the right pane, select the message to edit and click Rename. In the Rename dialog, paste the message text in the To field. Change Warning to * and Trap to * in the text string just pasted. Click OK. Return to the EM Console. Type opreload in the Command field and press ENTER. Open Microsoft Windows Explorer and launch the batch file, Service_Failure_Poll_Critical.bat, located in the C:\Student\UR215 folder. Return to the EM Console. A blue-colored message should appear in the Held Messages pane as a result of running the Service_Failure_Poll_Critical.bat batch file.
10 Close the EM Console and the MCC.
Notes
6-36
Automate Response to Events and Alerts Skill Practice
Skill Practice
Task Purpose: Optimize message records with text strings and wildcards. Use wildcards to enable an MRA to respond to a Web Server Failure from a poll or trap with a Warning or Critical state. 1 2 3 4 Use the steps from the previous interactive demonstration. Use C:\Student\UR215\Web Server Fail to send a message to the Event Console. Type Web Server Fail in the Description field. The message record will be used later for an alert. Use a Waitoper action in place of the Sendkeep action.
Task Summary
In this task, you identified how to respond to events by creating message records and actions. You also used text strings and wildcards in message records. The true value of Unicenter NSM is its ability to instantly respond to critical events as they occur in your business environment. In the next task, you will identify how to process significant events with the AMS.
Notes
6-37

Task 4: Process Significant Events with the AMS
Slide 6-21
Task 4: Process Significant Events with the AMS

The AMS is a tool for organizing and tracking the most important events that occur in an enterprise or logical segment of an enterprise. The AMS significantly improves the ability to focus on and manage the highest severity IT-related events in your enterprise.
Slide 6-22
The AMS can:

Specify the situations that create alerts and define alert policies. View and manage alerts in multiple panes of the MCC. Link to Unicenter Service Desk, which is a customer support application that manages calls and IT assets, tracks problem resolution, and shares corporate knowledge.
Alerts are sophisticated messages representing situations that typically require human intervention. They are created using MRAs and AECs. Alerts are functionally similar to held messages, but can be organized in much more intuitive ways. Alerts are stored in the MDB.
Notes
6-38
Automate Response to Events and Alerts Task 4: Process Significant Events with the AMS
Slide 6-23
The following administrative tools are components of the AMS: Administrative Tool Display Attributes Description This tool specifies the appearance of alerts on the MCC. Attributes include foreground and background color, blinking text, reverse video, and so on. This tool runs scripts, executable programs, and commands in response to alerts or manually from the Context menu in the MCC. This tool arranges user actions into submenus for use on the MCC context-sensitive menu. This tool specifies properties that apply to all alerts and configuration settings for all of the AMS. Alert queues facilitate grouping of similar alerts. The AMS organizes alerts by the queues you define and the MCC displays alerts by those queues. Alert classes organize alerts and specify their initial properties.
User Actions
Action Menu Alert Global Definitions Alert Queues
Alert Classes
Alerts should comprise a small subset of events that occur; the AMS is not a replacement for Event Management. Alerts should typically represent only those events that require human intervention or provide information critical to continued normal operations. The fewer the alerts generated, the more easily operations staff can focus on what is important. Each alert consumes more computing resources than other events. By carefully designing your AMS configuration and policy, you can help ensure that you get the most benefit from the AMS.
Notes
6-39

Task Purpose: Create alerts. 1 2 3 4 5 6 7 8 9 Open the MCC. In the left pane, select the Enterprise Management view. Expand Alert Management and select Alert Queues. In the right pane, click New. Type Servers in the Alert Queue Name field. Click OK. In the left pane, select Display Attributes. Double-click the Critical Display Attribute row. To change the foreground color, click select color.
10 Click Yellow and then click OK. 11 To change the background color, click select color. 12 Click Blue and then click OK. 13 Select Bold for the text font style. 14 Click OK. 15 In the left pane, select Alert Classes. 16 In the right pane, click New. 17 On the Main tab, type SERVERS in the Class ID field and Servers in the Class Name field. 18 From the Initial queue list, select Servers. 19 Select the Appearance tab. 20 From the Display Attributes list, select Critical. 21 Click OK.
Notes
6-40
22 In the left pane of the Enterprise Management view, expand Event Management and select Messages. 23 In the right pane, double-click Web Server Fail Message Record. The Message Record - Detail dialog appears. 24 Select the Actions tab. The Message Record Action - Detail dialog appears. 25 Double-click the WAITOPER action. 26 Type Web Server &nodeid Failure in the Text field. 27 From the Action list, select ALERT. 28 From the Alert class id list, select Servers. 29 To close the Message Record Action - Detail dialog, click OK. 30 To close the Message Record - Detail dialog, click OK. 31 In the left pane, select Console Logs. 32 In the right pane, click Launch Console Logs. 33 Type opreload in the Console Log Command field and press ENTER. 34 Return to the MCC and select the Console Logs view. 35 Choose Available Zones Default YourServerName.YourDomain.com and select Last 24 Hours. 36 Click the Lock Icon in the upper right corner. The icon will change from an open lock to a closed lock. Note: When a right pane view is locked for a subject, its relevant content is locked to the subject chosen and the content is refreshed periodically. 37 In the MCC left pane, select Alerts and observe that you see the Alerts view and the locked Console Log view.
Notes
6-41

Interactive Demonstration 38 Choose Available Zones Default YourServerName.YourDomain.com and select the Servers queue. 39 In Microsoft Windows Explorer, open the C:\Student\UR215 folder. 40 Double-click the Web_Server_Fail.bat file. The batch file runs. 41 Return to the Console Logs view and Alerts view in the MCC. Note: There may be a delay before the alert appears in the right pane of the MCC. 42 Close the Console Logs right pane view. In the next interactive demonstration, you will create an escalation policy for alerts.
Task Purpose: Create an escalation policy. 1 2 3 4 5 6 7 8 9 Open the MCC. In the left pane, select the Enterprise Management view. Expand Alert Management and select Alert Queues. In the right pane, click New. The Alert Queue - Detail dialog appears. Type Critical in the Alert queue name field. Click OK. In the left pane, select Display Attributes. In the right pane, click New. The Display Attribute - Detail dialog appears. Type Escalate Critical in the Attribute name field.
10 For Text font style, select Bold. 11 Click Background select color, select Red, and then click OK.
Notes
6-42
12 Click Foreground select color, select Yellow, and then click OK. 13 Click OK. 14 In the left pane, select Alert Classes. 15 In the right pane, click New. The Alert Class - Detail dialog appears. 16 On the Main tab, type CRITICAL in the Class ID field and Critical in the Class Name field. Verify Initial queue is set to Critical. Note: By default, Initial queue is set to Critical due to its alphabetic position in the list of available queues. 17 On the Appearance tab, from the Display attributes list, select Escalate Critical. 18 Click OK. 19 Click Start and then choose Programs Computer Associates Unicenter NSM Enterprise Management Classic. 20 Double-click Windows. 21 Double-click AMS. 22 In the left pane, select Escalation Policy. 23 Click New. The Escalation Policy dialog appears. 24 Type Escalate Critical in the Escalation policy field. 25 On the Escalation Policy tab, click New. The Escalation Policy Editor dialog appears. 26 Select Age in queue (hr:min) and select 1 in the Minute box. 27 Select Critical from the Transfer to queue list. 28 Select Escalate Critical from the Display Attributes list. 29 Click OK to close the Escalation Policy Editor dialog. EM
Notes
6-43

Interactive Demonstration 30 Click OK to close the Escalation Policy - Detail dialog. 31 In the left pane, select Alert Queues. 32 In the left pane, select the Alerts view. 33 In Microsoft Windows Explorer, open the C:/Student/UR215 folder. 34 Double-click the Web_Server_Fail.bat file. 35 In the MCC, select Servers in the left pane. Observe the server alert in the right pane. Note: There may be a delay before the new alert appears in the Servers queue. 36 In the left pane, select Critical. Observe the Critical alert in the right pane. Note: There may be a delay before the new alert is escalated to the Critical queue. In the next interactive demonstration, you will create user actions in the AMS.
Task Purpose: Create user actions. 1 2 3 4 5 6 In the MCC, select User Actions in the left pane of the Enterprise Management view. In the right pane, click New. The User Action - Detail dialog appears. Type Launch Service Desk in the Action field. Type "C:\Program Files\Internet Explorer\iexplore" http:// servername/CAisd/pdmweb.exe in the Command field. Click OK. In the left pane, select Action Menus.
Notes
6-44
7 8 9
In the right pane, click New. The Action Menu - Detail dialog appears. Type Service Desk in the Menu name field. In the Available user actions/menus: table, select Launch Service Desk and click the Add button to move it to the Selected user actions/ menus: table.
10 Click OK. 11 In the left pane, select Alert Queues. 12 In the right pane, select the Critical alert queue from the table. The Alert Queue - Detail dialog appears. 13 Select Service Desk from the Menu list. 14 Click OK. 15 In the left pane, select the Alerts view. Observe the alerts in the right pane. 16 In the MCC, select Critical in the left pane of the Alerts view. 17 In the right pane, select the Critical alert, right-click, and choose My Actions Service Desk Create Ticket. The Execute an Action dialog appears. 18 Click Execute. When prompted, click OK. Note: This action would launch the Service Desk Web Interface in an environment where it existed. This type of action can also be used to launch other web-based management applications. 19 Close the Execute an Action dialog.
Notes
6-45

Task Summary
Task Summary
Using AMS, you can create custom views for console messages that warn about important or critical events. You define which messages are alerts and specify how you want to view them. In this task, you identified how to organize and track the most important events with the AMS. In the next task, you will identify how to communicate event status with the UNS.
Notes
6-46
Automate Response to Events and Alerts Task 5: Communicate Event Status with the UNS
Slide 6-24
Task 5: Communicate Event Status with the UNS

The UNS provides a service that sends wired and wireless messages using various protocols and devices. These messages must get the attention of operators or administrators, wherever they are, to resolve problems or attend to emergencies. The UNS is different from the Wireless Messaging component of Unicenter Event Management. Wireless Messaging enables you to send emails and pages. Notifications can be sent from message actions integrated with the Event Management user interface from the command line or script.
Slide 6-25
The types of protocols available with the UNS are: Protocol Email Description SMTP is used to send one-way and two-way email messages. POP3 is used to receive emails from a mail server. Wireless Communications Transfer Protocol (WCTP) uses XML over HTTP and is designed for sending and receiving messages and binary data between wire-line systems and one-way or twoway wireless devices. Simple Network Paging Protocol (SNPP) is based on TCP/IP and offers one-way and two-way pages. Telocator Alphanumeric Protocol (TAP) sends pages by modem and is the oldest one-way paging protocol. Short Message Service (SMS) is used to send text one-way to cellular phones using HTTP.
Wireless
Page
Short Message
Notes
6-47

Describe the UNS Process Protocol Instant Message Description IBM Lotus Instant Messaging and Web Conferencing, or Sametime Instant Messaging (SIM), is used on Microsoft Windows to send oneway and two-way instant messages. Telephony Application Programming Interface (TAPI) is used on Microsoft Windows to send oneway voice messages that are synthesized from text using the Microsoft Speech Application Programming Interface (SAPI) text-to-speech (TTS) engine. The default speech is set in the Microsoft Windows Control Panel. The messages travel to the recipient by telephone line using a TAPI-compliant telephony device. Third-party programs, customer programs, or scripts can be used to send one-way messages. Scripts and command definitions are stored in the UNSConnections.ini file in the install_path/config directory.
Voice
Script
Slide 6-26
Describe the UNS Process

The UNS keeps track of all notifications that you send. This is especially important for two-way notifications that must be matched with responses. You create a notification message by using one of the following features:

User interface Command line or script Event Console by right-clicking a message Event Management NOTIFY action
Notes
6-48
Automate Response to Events and Alerts Describe the Recipient and Provider Registry
Alert Management escalation Application using the Notification Services client SDK
Then, based on the recipient, provider, or protocol information in the request, the Notification Services Daemon (unotifyd) selects a protocol-specific driver to send the notification. Note: The Notification Services Daemon (unotifyd) runs as a service on Microsoft Windows and as a background process on UNIX and Linux.
Slide 6-27
Describe the Recipient and Provider Registry

The Notification Services recipient and provider registry enables you to type information about recipients, recipient groups, and service providers. It contains recipient addresses, protocols, and connection information so that you need not type everything manually with each notification. You just type the name (alias) for the information you want to use. This saves time and might hide sensitive information. The registry has files that you can edit with a text editor, the Microsoft Windows GUI, or the unsutil command-line utility. Each file contains an explanation of the file contents and includes sample templates to help you define your own recipients and providers. The files are defined in the following table: File uns_provider.ini Definition Defines provider aliases with connection information for the protocols that service providers support Defines recipient aliases and default providers: each recipient has one default provider
uns_recipient.ini
Notes
6-49

Describe the Recipient and Provider Registry File uns_recipient_group.ini uns_recipient_address_link.ini Definition Defines recipient groups Defines recipient addresses for each provider
The Notification Services Daemon commands are defined in the following table: Command unotify Definition This command sends a one- or two-way notification message using the Notification Services Daemon. If a reply or other status is requested, the command waits for the status and displays it when received. If the wait times out, use the uquery command for future queries. This command sends a one-way or two-way notification message on the local node without using the Notification Services Daemon. This command enables you to send notifications when the daemon is not running. However, because the daemon is not running, the notification information is not stored on disk. This command requests the status of one or all notifications from the Notification Services Daemon. For one notification, you can display the current status immediately or wait until a requested status, like a reply, is received.
unotifys
uquery
Notes
6-50
Automate Response to Events and Alerts Consider Email Protocol Issues
Command uquerys
Definition This command requests the status of one notification sent by unotifys on the local node. The Notification Services Daemon is not used so you can use this command when the daemon is not running. This command starts, stops, and queries the status of the Notification Services Daemon. This command encrypts and decrypts a configuration file. Some connection information in the uns_provider.ini file requires a user name and password that you might want to protect. Only Notification Services applications can read an encrypted file. Note Before changing data in an encrypted file, decrypt it. After changing the file, encrypt it again.
Unscntrl Unsconfig
Consider Email Protocol Issues

Some firewall and antivirus software can block ports 25 and 110. The notification appears to timeout. Check with your software provider to find out how to configure the software so the Notification Services Daemon (unotifyd) can access these ports.
Notes
6-51

Perform Troubleshooting Because of site-specific mail server names, user IDs, and passwords, the EMAIL two-way notification is disabled after installation. You must configure POP3 in the MAIL01 section of the UNSDaemon.ini file. Uncomment by removing the semicolon for lines ResponseName=POP3 and ResponsePath=uns_smtp. Also, uncomment and type the configuration information for your mail server at line ResponseConnectionInfo=servername.company.com:110:user:password. Set up a separate mailbox to receive responses to notifications. It is not recommend to use a personal mailbox.
Perform Troubleshooting
You can diagnose errors with SMTP and POP3 using the smtp_session.log and pop3_session.log files in the log directory UNS. Use TELNET host PORT# to verify if ports 25 or 110 are blocked.
Task Purpose: Communicate event status with the UNS.
Configure an Email Account

1 2 3 4 5 6 7 8 9 Click Start and then choose Programs Office Outlook 2003. Microsoft Office Microsoft
Click Cancel to close the Outlook 2003 Startup wizard. Click Yes in response to the confirmation prompt. Choose Tools E-mail Accounts. Select Add a new e-mail account and click Next. Select POP3 and click Next. Type StudentX in the Your Name field, for example, Student2. Type StudentX@YourDomain.com in the E-mail Address field. Type UsxxyyT2 in the Incoming mail server (POP3) field.
Notes
6-52
10 Type UsxxyyT2 in the Outgoing mail server (SMTP) field. 11 Type StudentX@YourDomain.com in the User Name field. 12 Type password in the Password field. 13 Click Test Account Settings. When all tests are successfully completed, click Close. 14 Click Next. 15 To close the E-mail Accounts wizard, click Finish. 16 Click Send/Receive. 17 Click New to create a new mail message. 18 Type StudentX@YourDomain.com in the To field. 19 Type test message in the Subject field. 20 Click Send. 21 Click Send/Receive. 22 In the Navigation pane, under All Mail Folders, select Inbox. 23 Select the test message in the Inbox to view it in the Reading pane.
Configure a Service Provider

24 Click Start and then choose Programs Computer Associates Unicenter Enterprise Management EM Classic. 25 Double-click Windows. 26 Double-click Notification. 27 Double-click Service Provider. The Service Provider Summary dialog appears. 28 Double-click EMAIL in the Service Provider table. The Service Provider - Detail dialog appears. NSM
Notes
6-53

Interactive Demonstration 29 Type UsxxyyT2:25 in the Connection information field. 30 Select Active. 31 Click OK to close the Service Provider - Detail dialog. 32 Close the Service Provider Summary dialog.
Create a Recipient
33 In the EM Classic window, double-click Windows, Notification, and then Recipient. The Recipient Summary dialog appears. 34 Click New. The Recipient - Detail dialog appears. 35 Type StudentX in the Recipient field. 36 Click New. The Recipient provider dialog appears. 37 Type StudentX@YourDomain.com in the Address field. 38 Click OK. 39 When prompted, click Yes to continue. 40 Click OK to close the Recipient - Detail dialog. 41 Close the Recipient Summary dialog.
Test the Notification

42 In the EM Classic window, double-click Windows, Notification, and then Notification. The Notification dialog appears. 43 On the Main tab, click the binoculars icon. The Recipients dialog appears. 44 Double-click StudentX from the Available recipients table. 45 Click OK. 46 Click Verify. The following message appears in the Status field: The recipient is valid for the provider.
Notes
6-54
47 Type nsmalert@YourDomain.com in the Sender field. 48 Type Test Message in the Message field. 49 Click Submit. 50 Click Status. The Notification Status dialog appears. Observe the status of the test message. 51 Close the Notification Status dialog. 52 Close the Notification dialog. 53 Close all remaining EM windows. 54 Open Microsoft Outlook. 55 Click Send/Receive. 56 Select the test message in the Inbox to view it in the Reading pane.
Create a Message Record with Notify Action

57 At the command prompt, type caugui conlog and press ENTER. The EM Console opens. 58 In Microsoft Windows Explorer, open the C:\Student\UR215 folder and double-click the Notification.bat file. 59 Return to the EM Console and double-click the message that resulted from running the batch file. The EM Console Message dialog appears. 60 On the Messages tab, select and copy the message text in the Message field. 61 Close the EM Console Message dialog. 62 Open the MCC. 63 In the left pane, select the Enterprise Management view. 64 Expand YourServerName\Event Management and select Messages. 65 Click New.
Notes
6-55

Interactive Demonstration 66 Paste the message text in the Message id field. 67 Click Save. 68 Select the Actions tab. 69 Click New. 70 On the Action tab, type * in the Sequence number field. 71 Select SENDOPER from the Action list. 72 Select BLUE from the Color list. 73 Click OK. 74 Click New. 75 On the Action tab, type * in the Sequence number field. 76 Select Notify from the Action list. 77 Type -t StudentX -v EMAIL -m "&text" in the Text field. 78 Click OK. 79 Click OK to close the Message Record - Detail dialog. 80 Return to the EM Console. 81 Type opreload in the Command field and press ENTER.
Define a Default SMTP Sender

82 In Microsoft Windows Explorer, open the C:\Program Files\CA\Unicenter NSM\UNS\config folder. 83 Open the UNSDaemon.ini file. 84 85 Choose Edit Next. Find, type [MAIL01] in the Find what field and click Find
In the [MAIL01] protocol driver configuration section, locate From=.
86 Type nsmalert@YourHostDomain.com after the equal sign.
Notes
6-56
87 Choose File
Save and close the file.
88 From your desktop, double-click the Services shortcut. The Services window opens. 89 Right-click CA Notification Services in the Name column and choose Restart.
Test the Notification

90 In Microsoft Windows Explorer, open the C:\Student\UR215 folder. 91 Run the Notification.bat batch file. 92 Open the EM Console. Observe the resulting log message. 93 Open Microsoft Outlook. 94 Click Send/Receive. 95 Open the notification message in the Inbox.
Task Summary
The UNS provides protocols that give you full programmatic control of notification options and policies for resolving situations. In this task, you discovered the various notification services available in the UNS. You also communicated event status with the UNS.
Notes
6-57

Assessment
Assessment
1 Which process evaluates events, applies policies, and writes messages to the Unicenter NSM Event Console Log? a b c d 2 caoprlog opreload caopr.dsb caoprdmn
What is the name of the visualization tool used to view the daily logs? a b c d DSB Event Console Direct Interface Administrative GUI
What can be used to identify text strings without having to specify every character? a b c d Variables Wildcards Message actions Message records
Notes
6-58
Automate Response to Events and Alerts Assessment
Which tool specifies the appearance of alerts on the MCC? a b c d Action Menu Display Attributes Event Management Alert Global Definitions
Which three notification services are available with the UNS? (Choose three.) a b c d e MRA AEC Page Email Instant Message
Notes
6-59

Module Summary
Slide 6-28
Module Summary

Describe Event Management Architecture Filter Events with Event Console Logs Respond to Events by Creating Message Records and Actions Process Significant Events with the AMS Communicate Event Status with the UNS
With Event Management, you can monitor event activity and immediately respond to events as they occur. You can also filter messages to retrieve specific information about a particular event. Determining a course of action based on when an event occurs can be critical to its proper handling. By defining message record and action profiles, you can identify events that are important to RBCs operations and define the automated processing that Unicenter NSM performs when encountering them. Through the MCC interface, you can access Event Management components such as Event Console Logs, the AMS, and the UNS. This consolidation enables fewer staff to manage more of the infrastructure. In this module, you used Event Management components to monitor event activity from a variety of sources and to automate responses to events and alerts. You filtered events with Event Console Logs and responded to events by creating message records and actions. You also processed significant events with the AMS and provided notification services with the UNS. In the next module, you will learn how to optimize the MDB.
Notes
6-60
7
Optimize the MDB
7-1
Optimize the MDB

Module Objectives
Slide 7-1
Module Objectives

Define a Single or Multiple MDB Implementation Identify Ingres Utilities Secure MDB Access Tune the Ingres Database to MDB Requirements
Module Overview
The MDB combines all data from currently distinct disciplinesoperations, storage, security, life cycle, and service managementand provides the foundation necessary to manage and optimize RBCs IT infrastructures. A unified MDB schema means only one database to administer, rather than many. This makes the database and related products easier to manage and less expensive. To optimize the MDB, you need to know how to create, maintain, back up, and recover databases. You also need to define various types of users, authorize user access, and work with different types of database objects. In this module, you will learn about the advantages of the MDB approach. You will identify the Ingres utilities that you can use to effectively manage and administer databases. You will be exposed to the different types of MDB users and learn how to grant different levels of MDB user access. You will also use queries and database statistics to optimize databases.
Notes
7-2
Optimize the MDB Task 1: Define a Single or Multiple MDB Implementation
Slide 7-2
Task 1: Define a Single or Multiple MDB Implementation

The MDB is a single integrated database schema for the management data stored by all CA products, mainframe and distributed. The MDB provides a complete view of the entire IT environment.
Slide 7-3
The primary advantages of the MDB approach are:

Integrated IT management data Integrated database administration
A unified database schema for IT management data provides increased visibility into the underlying IT organization, including storage, performance, hardware, and software information. This visibility improves IT decision-making and helps to reduce costs and increase infrastructure use. Using a unified database schema enables fully-informed decisions about hardware, software, and storage purchases, as well as provisioning, scheduling, data protection, and more. The unified MDB schema enables CA to integrate its products without additional programming effort. Without an MDB, data is stored in multiple locations and schemas making it difficult to integrate and create new features that take advantage of data relationships. A unified MDB schema means only one database to administer, which makes the database and related products easier to manage and less expensive.
Notes
7-3
Optimize the MDB

Task 1: Define a Single or Multiple MDB Implementation
Slide 7-4
The MDB contains complete, consistent, and manageable definitions for all key IT management data. These definitions are shared by CA product solutions right out of the box, and they also can be extended to other products and third-party tools. MDB information supports CA products in the following categories of IT management:

Assets and inventory Storage Security Operations Services Job scheduling Servers and desktops Databases Application life cycle
No two IT organizations have the same deployment requirements. Some organizations must implement multiple MDB instances for reasons of size, legal requirements, organizational structure, or geography. In addition, organizations need to be able to deploy one or more MDBs in IT environments that include non-CA software solutions. There are two basic models for MDB deployment with CA products:

Single MDB for all CA products Multiple MDBs for use with CA product deployments where more than one MDB is required
Notes
7-4
Optimize the MDB Single MDB
Slide 7-5
Single MDB
Deployment in a single global MDB to store data for all products is the simplest to implement. In general, this implementation costs less and is easier to manage. This deployment option is shown in the following graphic:
A single integrated view of the underlying IT infrastructure is available with no additional processing required. In this deployment, administration requirements, including establishing security and data availability, occur once for the single MDB.
Notes
7-5
Optimize the MDB

Multiple MDBs
Slide 7-6
Multiple MDBs
The MDB enables a federated approach that uses multiple databases, or data instances. Supporting multiple MDBs can require additional planning and administration. To gain a single integrated view, data must be retrieved or accessed from multiple data instances as shown in the following graphic:
In this scenario, one or more products access different MDBs.
Notes
7-6
Optimize the MDB Multiple MDBs
Each of the following approaches provides a single integrated view, for reporting purposes, of the underlying IT infrastructure:
Distributed query support, provided by Ingres or from other relational databases, enables a federated approach. With distributed query, multiple MDBs, each with its own management information, are segmented and implemented by function, geography, and organization. Distributed queries enable data from different database, MDBs, to appear as if it were from one database. Replication, available with Ingres or other relational databases and built into some of CA management products directly, enables a federated approach. With replication, each function and geography or organization uses its own MDB for management information. Data from each MDB is replicated to a central database server with an MDB that provides a single, integrated view of the IT infrastructure of the company. In a replicated approach, the central database server might also serve as an MDB supporting one or more CA products.
Task Summary
The MDB approach provides integrated IT management data and database administration. This makes the database and related products easier to manage and less expensive. The two basic models for MDB deployment are single and multiple. Different IT organizations have different deployment requirements. Some organizations must implement multiple MDB instances for reasons of size, legal requirements, organizational structure, or geography. In addition, organizations need to be able to deploy one or more MDBs in IT environments that include non-CA software solutions. In the next task, you will identify Ingres utilities.
Notes
7-7
Optimize the MDB

Task 2: Identify Ingres Utilities
Slide 7-7
Task 2: Identify Ingres Utilities

Ingres provides GUI tools, services, and commands for system management and database administration.
Slide 7-8
Identify Ingres Visual Manager

The Ingres Visual Manager is an integrated GUI tool that provides a global view into your installation. It serves as a system console from which you can manage Ingres components and access other utilities. This utility also captures events that are occurring in the system, not only to alert the system administrator, but also to act as a basis for creating rules that fix the errors. In Ingres Visual Manager, you can easily perform the following functions:

Start and stop the installation. Monitor the status of the installation or individual servers. View and configure system, user, and other types of parameters. View the log files and event statistics for the installation or individual servers. View and define error message alerts. Invoke other visual tools.
System Summary Icon

In Microsoft Windows, the Ingres system summary icon visually informs you of the state of the installation. You can tell immediately if Ingres is running, partially or completely, and whether any problems exist. The icon is located in the notification area of the taskbar.
Notes
7-8
Optimize the MDB Interactive Demonstration
The color of the icon indicates various states, as follows:

Green indicates that instances of all Ingres components have been started based on the chosen startup counts. Dark green indicates that instances of all Ingres components have been started based on the chosen startup counts, and additional instances of some components have also been started manually. Half green and half red indicate that instances of only some components have been started based on the chosen startup counts. Red indicates that no instances of any components have been started.
An exclamation mark appears in the icon if an alert has arrived that the user has not yet acknowledged.
Task Purpose: View system information with the Ingres Visual Manager. 1 2 3 Click Start and then choose Programs Computer Associates Ingres Ingres Visual Manager. Select any of the component configuration sub-branches in the Ingres Visual Manager. In the right pane, click the Status, Logged Events, and Event Statistics tabs to view information for the component you selected.
In Ingres Visual Manager, you can also control how various types of error log messages are handled. You can specify which messages should be discarded, displayed in Ingres Visual Manager, or displayed with a user alert.
Notes
7-9
Optimize the MDB

Task Purpose: Define message categories and notification levels. 1 2 3 4
Slide 7-9
Open Ingres Visual Manager. Choose File Categories and Notification Levels. The Define Message Categories and Notification Levels window opens. Drag a message from the lower pane to the desired state or category branch in one of the upper panes. Depending where you dropped the message, you can define a state, category, or both for the message.
Identify Visual DBA

Visual DBA is an intuitive, GUI-based database tool that enables you to manage servers and other database resources easily. In its flexible, interactive workspace, you can:

Connect to and work with multiple servers. Monitor your system, analyze performance, and perform system management tasks. Access and manipulate your databases and installations visually through powerful database administration utility windows. Create new databases, including distributed databases, for use with Ingres Distributed Option. Install, view, and configure replication objects to be used with Ingres Replicator Option. Create and manage users, groups, profiles, and roles.
Notes
7-10
Optimize the MDB Navigational Tree Structure in Visual DBA
Navigational Tree Structure in Visual DBA

In Visual DBA, tree-like structures are used to delineate virtual node and server information, database objects and their relationships, and performance data in Multiple Document Interface (MDI) windows. For example, the Database Object Manager enables you to select the branch for the appropriate database object and then create, alter, drop, or assign privileges to it. You can even customize the tree structure of this window. You can open and work with multiple databases, servers, or both in multiple windows.
Database Administration Tools in Visual DBA

In addition to the Database Object Manager, Visual DBA has several other tools that can be used to perform an array of database administration tasks required for your installation. For example, the SQL Test window helps you analyze the performance of your SQL queries. The Database Event Trace utility and the Performance Monitor enhance your ability to monitor database events and various types of performance data. For example, you can view and manage servers and sessions, as well as locking and logging systems. You can also manage distributed databases because Visual DBA offers connectivity to remote databases through Ingres Net and Advantage Enterprise Access gateways. Visual DBA provides a host of other complementary tools to complete the database administration environment. These include capabilities to perform many of your routine database maintenance activities, along with system management and performance analysis. In addition, you can use Visual DBA to configure and propagate replication objects and manage your replication activities.
Notes
7-11
Optimize the MDB

Visual DBA Workspace
Visual DBA Workspace

The main areas in the Visual DBA workspace are:

Menu bar Visual DBA toolbar Virtual Nodes toolbar and window Display area for MDI windows Status bar
The workspace can be customized. For example, you can hide the main application toolbar or the Virtual Nodes toolbar and window. The toolbars in all windows are dockable, which means that they can be attached, or docked, to any side of their parent windows by dragging the toolbar to the window border. A toolbar can also be floated in its own window by double-clicking it.
Slide 7-10
Identify Ingres Services and Commands

After Ingres is installed, you will need to use additional services and commands so that users can access and use the new installation.
Ingres Net Connection Settings

For an Ingres Net installation, an Ingres server on a host cannot be accessed until a virtual node (vnode) definition is provided on the client for that host.
Notes
7-12
Optimize the MDB Startup and Shutdown
You must make the following entries for each node:
Virtual Node: This node defines a name that identifies the host. This name is a user-defined connection definition. Note: In replication, this name has to be the same as the server to which you are replicating.
Remote Node: This node defines the name of the workstation as known by the networking protocol. Protocol Node: This node identifies the network protocol used by Ingres Net. Listen Address Node: This node identifies the listen address, which is determined by the installation on the remote node. For a Microsoft Windows server, it is usually II. Contact your database administrator to determine the proper listen address, and whether it supports the required protocol. User Name Node: This node specifies the name of the user recognized by the operating system on the remote node. Password Node: This node specifies the OS password for the specified user on the remote node.
Startup and Shutdown

You can start up and shut down your Ingres installation in the following ways:

Automatically Using Ingres Visual Manager Using Ingres Service Manager
Notes
7-13
Optimize the MDB

Startup and Shutdown

Using the Services Window in Microsoft Windows Using the ingstart and ingstop commands Note: After Ingres is installed with the High Availability option, you must start and stop the Ingres installation only from a Cluster Service Manager.
Automatic Startup and Shutdown

During installation, if you chose to start the Ingres DBMS Server as an automatic service on system startup, Ingres will be shut down when you log off Microsoft Windows. Note: Prior to stopping Ingres, you must stop all Unicenter NSM services.
Task Summary
Ingres provides GUI tools, services, and commands for system management and database administration. In Ingres Visual Manager, you can view and manage information related to an Ingres component, control how various types of error log messages are handled, and specify which messages should be discarded, displayed, or displayed with a user alert. Visual DBA enables you to manage servers and other database resources easily. After Ingres is installed, you will need to use additional services and commands so that users can access and use the new installation. In the next task, you will secure MDB access.
Notes
7-14
Optimize the MDB Task 3: Secure MDB Access
Slide 7-11
Task 3: Secure MDB Access

All CA products share the database objects in the MDB. This provides a consistent data architecture in which management information uses a single standard for access control and administration to help ensure integrity and availability. Enforcement of security rules for access to the MDB is provided by the relational database management system (RDBMS). The MDB contains the database objects for all CA products. Database objects include tables, views, procedures, and rules. Typically, a CA product uses a specific set of database objects to expose information to the user. Those database objects should not be accessible to other products. The MDB security model helps ensure that the user of a CA product can only access the database objects for that product. In other words, a customer using the CA Service Desk product can only access tables used by that product and cannot, for example, access tables for another product. The MDB security model restricts access to the database objects used by a product using underlying RDBMS user groups. A user group is created for each product or for each product application component. Users of a product, or users created for the component of the product, are assigned to a user group. Any number of users can be associated with a user group. Through grouping the database objects used by a particular product and associating database users with a user group, product access is restricted in the data, procedures, and rules. The MDB is created with many user groups already defined. Products specify these groups when they connect to the database. If you choose to use external tools, such as report writers to access MDB data, you can limit table accessibility to users of the report writer by making these user groups a part of the database connection information.
Notes
7-15
Optimize the MDB

MDB Access
Slide 7-12
MDB Access
To connect to an Ingres MDB, you must possess a valid Ingres user ID and also an associated valid user ID on the OS that hosts the Ingres database server. Many of the Ingres user IDs required for CA products to access the MDB are created as part of the MDB installation process. Ingres user IDs are defined without passwords because Ingres authenticates the OS user definition before checking whether the user is defined to Ingres. Some product installations create OS users when the product is installed. In such cases, product installation should prompt the user for the password to use to create the OS user ID. Whenever possible, it should refrain from creating the password automatically, or, if created automatically, it should be a strong password. Note: The Ingres user name, mdbadmin, is the owner of all MDB database objects. This user name must not be an OS user ID. It is recommended that this user name should not be used by any product to access objects in the MDB. There are two types of MDB access:

Groups Users
When a new Ingres user ID is created, that user does not automatically have access to MDB database objects. One method of granting access to a specific group of database objects is to assign a predefined user group. For example, a newly created Ingres user ID can be assigned to a Service Desk user group. This enables that user to access only those database objects permitted to the Service Desk group. This approach limits the exposure of database objects. If an Ingres user ID is created to access database objects for reporting purposes, the new user must be granted access to the appropriate database objects, tables, and views. This is accomplished using Ingres grant statements.
Notes
7-16
Optimize the MDB MDB Users
Slide 7-13
MDB Users
User definitions are required for access to the MDB. For a user to connect to an MDB, that user must possess a valid user ID and also an associated valid user ID on the OS that hosts the database server. There are three types of MDB superusers:
System administrator: Owns the Ingres account Needs OS knowledge Must have system privileges on VMS, but rarely needs root privilege on UNIX Installs and maintains the Ingres installation Has security privilege by default Has privileges in the Ingres environment Can grant security privilege to others Can create databases on behalf of others Is responsible for creating and maintaining databases Can own a database Has privileges in own databases Can own objects Can grant privileges to others
Security administrator:
Database administrator:
Notes
7-17
Optimize the MDB

Interactive Demonstration Ingres users:

Are the end users Use existing databases Can own objects Can grant privileges to others
Task Purpose: Create a user account with administrative permissions to all Unicenter NSM applications, GUIs, and the MDB. 1 2 3 4 5 6 7 8 9 Right-click Ingres [WV] in the notification area of the taskbar. Choose Ingres Visual DBA. In the left pane of the Ingres Visual DBA [WV] window, expand Nodes\YourServerName\Users. Right-click nsmadmin and choose Connect/DOM. In the middle viewing pane, right-click Users and choose Create. The Create User on WV_YourServerName dialog appears. Type uni_administrator in the User Name field. Select uniadmin from the Default Group list. Select mdb from the Access to Non-Granted Databases list. Select External Password. Click OK.
10 Close the Ingres Visual DBA. The confirmation message box appears. 11 Click NO. 12 On your desktop, right-click My Computer and choose Manage. The Computer Management window opens. 13 In the left pane, expand Local Users and Groups.
Notes
7-18
14 Right-click Users and choose New User. The New User dialog appears. 15 Type uni_administrator in the User Name field. 16 Type unicenter in the Password and Confirm password fields. 17 Clear the User must change password at next logon option. 18 Select Password never expires. 19 Click Create and then click Close. 20 In the left pane of the Computer Management window, select Local Users and Groups Groups. 21 In the right pane, right-click TNDUsers and choose Add to Group. 22 The TNDUsers Properties dialog appears. Click Add. 23 The Select Users, Computers, or Groups dialog appears. Click Locations. 24 The Locations dialog appears. Select YourServerName and click OK. 25 Type uni_administrator in the Enter the object names to select field, click Check Names, and then click OK. 26 Click OK to close the TNDUsers Properties dialog. The following steps are only necessary in the classroom environment to test the Unicenter_Administrator account. 27 Open Microsoft Windows Explorer. 28 Open the C:\Documents and Settings\Administratorzz\Start Menu\Programs\Computer Associates\Unicenter\NSM folder. 29 Right-click the Management Command Center shortcut and choose Copy. 30 Open the C:\Documents and Settings\All Users\Desktop folder. 31 Right-click and paste the Management Command Center shortcut. 32 Click Start and then choose Shut Down.
Notes
7-19
Optimize the MDB

Interactive Demonstration 33 Select Log off administratorzz from the list and click OK. 34 Press
CTRL+ALT+DELETE
and when prompted, click OK.
35 Type uni_administrator in the User Name field. 36 Type unicenter in the Password field. 37 Select YourServerName from the Log on to list. 38 Click OK. 39 Double-click the Management Command Center shortcut on the desktop. 40 When prompted, type your administrator credentials and click OK. 41 In the left pane, drill down to any server object in the classroom. 42 Right-click the server object and choose Delete. The object will be deleted. 43 Log off as uni_administrator and log back on as Domain Admin, administratorzz. Now that you have granted administrator access to the MDB, you will grant the MDB read-only user access in the next interactive demonstration.
Task Purpose: Create a user account with read-only permissions to all Unicenter NSM applications, GUIs, and the MDB. 1 2 3 4 5 Right-click Ingres [WV] in the notification area of the taskbar. Choose Ingres Visual DBA. In the left pane of the Ingres Visual DBA [WV] window, expand Nodes\YourServerName\Users. Right-click nsmadmin and choose Connect/DOM. In the middle viewing pane, right-click Users and choose Create. The Create User on WV_YourServerName dialog appears. Type Uni_Operator in the User Name field.
Notes
7-20
6 7 8 9
Select uniuser from the Default Group list. Select mdb in the Access to Non-Granted Databases list. Select External Password. Click OK.
10 Close the Ingres Visual DBA. The confirmation message box appears. 11 Click NO. 12 On your desktop, right-click My Computer and choose Manage. The Computer Management window opens. 13 In the left pane, expand Local Users and Groups. 14 Right-click Users and choose New User. The New User dialog appears. 15 Type Uni_Operator in the User Name field. 16 Type unicenter in the Password and Confirm password fields. 17 Clear the User must change password at next logon option. 18 Select Password never expires. 19 Click Create and then click Close. 20 In the left pane of the Computer Management window, select Local Users and Groups Groups. 21 In the right pane, right-click TNDUsers and choose Add to Group. 22 The TNDUsers Properties dialog appears. Click Add. 23 The Select Users, Computers, or Groups dialog appears. Click Locations. 24 The Locations dialog appears. Select YourServerName and click OK. 25 Type Uni_Operator in the Enter the object names to select field, click Check Names, and then click OK. 26 Click OK to close the TNDUsers Properties dialog.
Notes
7-21
Optimize the MDB

Interactive Demonstration 27 Click the Start menu and then choose Shut Down. 28 Select Log off administratorzz from the list and click OK. 29 Press
CTRL+ALT+DELETE
and when prompted, click OK.
30 Type Uni_Operator in the User Name field. 31 Type unicenter in the Password field. 32 Select YourServerName from the Log on to list. 33 Click OK. 34 Double-click Management Command Center on the desktop. 35 When prompted, type your administrator credentials and click OK. 36 In the left pane, drill down to any server object in the classroom. 37 Right-click the server object and choose Delete. 38 The Confirm Delete message appears. Select Delete child objects (irreversible) and click Yes. Note: The object will not be deleted because the user does not have permission. 39 A Management Command Center message appears advising that you do not have access rights to create, update, or delete objects.
Notes
7-22
Optimize the MDB Task Summary
Task Summary
All CA products share the database objects in the MDB. This provides a consistent data architecture in which management information uses a single standard for access control and administration to help ensure integrity and availability. Enforcement of security rules for access to the MDB is provided by the RDBMS. When a new Ingres user ID is created, that user does not automatically have access to MDB database objects. One method of granting access to a specific group of database objects is to assign a predefined user group. This approach limits the exposure of database objects. In this task, you identified how to administer different user access privileges. In the next task, you will identify how to tune the Ingres database to MDB requirements.
Notes
7-23
Optimize the MDB

Task 4: Tune the Ingres Database to MDB Requirements
Slide 7-14
Task 4: Tune the Ingres Database to MDB Requirements

Good performance requires planning and regular maintenance. Maintaining your databases keeps them in good condition and helps you to quickly identify any problems.
Slide 7-15
Identify Query Optimizer

Ingres uses a query optimizer to develop sophisticated query execution strategies. The query optimizer makes use of basic information, such as row size, number of rows, primary key fields and indexes, and more specific data related information, such as the amount of data duplication in a column. The data related information is available for use by the query optimizer only after statistics have been generated for the database. Without knowing exactly what data you have stored in your table, the query optimizer can only guess what your data looks like.
Slide 7-16
Identify Database Statistics

When you generate statistics for a database, you are optimizing the database, which affects the speed of query processing. More complete and accurate statistics generally result in more efficient query execution strategies, which further result in faster system performance. The extent of the statistics to be generated for a database can be modified by various options, including restricting the tables and columns that are used. Note: Deleting all the rows in a table does not delete the statistics.
Notes
7-24
Optimize the MDB Generate Statistics
Generate Statistics
In Visual DBA, use the Optimize Database dialog to generate statistics for the database that is currently selected in the Database Object Manager window. At the command line, you can accomplish this task with the optimizedb command. For more information, refer to the Command Reference Guide.
Demonstration
Task Purpose: Optimize a database. Note: Optimize Database should not be run for all tables in the database. Consult the database schema for specific table information. 1 2 3 4 5 6 7 Right-click Ingres [WV] in the notification area of the taskbar and choose Ingres Visual DBA. Expand Nodes\WV_YourServerName\Servers and select Ingres. To open the Database Object Manager, click Database Object Manager, which is the first icon on the left. Expand the Databases branch. Select the MDB you want to optimize. Choose Operations dialog appears. Generate Statistics. The Optimize Database
To specify individual tables for which statistics are to be generated, select Specify Tables and click the Tables button. The Specify Tables dialog appears. Note: If Specify Tables is cleared, all tables are chosen for processing.
Select the tables for which statistics are to be generated and click OK.
Notes
7-25
Optimize the MDB

Generate Statistics 9 If you specified one or more tables in the previous step, you can also specify individual columns in a table for processing. Select Specify Columns and click Columns. The Specify Columns dialog appears. Note: If Specify Columns is cleared, all columns of the specified tables are chosen for processing. 10 Select a table from the Table list. 11 Select the columns for which statistics are to be generated and click OK. 12 Complete the dialog according to the information provided in the Optimize Database dialog help topic. 13 To specify the display characteristics for the statistics, click Display. The Display dialog appears. 14 Complete the dialog according to the information provided in the Display dialog help topic. 15 Click OK.
Task Summary
For best performance, an MDB should be optimized to match the data distribution patterns of a product's actual database changes. For this purpose, Ingres provides a query optimizer that uses statistical data about the table columns that are used in queries. When you optimize a database, data distribution statistics are collected that help queries run more quickly and use fewer system resources. Collecting these statistics increases the likelihood of optimal query plans in the future.
Notes
7-26
Optimize the MDB Assessment
Assessment
1 What are the two primary advantages of the MDB approach? (Choose two.) a b c d 2 Multiple data sources Complex visualization tools Integrated IT management data Integrated database administration
What are the two basic models for MDB deployment? (Choose two.) a b c d Secure Single Multiple Integrated
Which Ingres utility serves as a system console from which you can manage Ingres components and access other utilities? a b c d Vnode Visual DBA Ingres Visual Manager System summary icon
Notes
7-27
Optimize the MDB

Assessment 4 What are the three types of MDB superusers? (Choose three.) a b c d e f 5 Ingres user Operations user System administrator Storage administrator Security administrator Database administrator
What makes use of basic information, such as row size, number of rows, primary key fields, and more specific data related information, to optimize a database? a b c d Query optimizer optimizedb command Database Object Manager Optimize Database dialog
Notes
7-28
Optimize the MDB Module Summary
Slide 7-17
Module Summary

Define a Single or Multiple MDB Implementation Identify Ingres Utilities Secure MDB Access Tune the Ingres Database to MDB Requirements
The MDB approach provides integrated IT management data and database administration for organizations like RBC. This makes the database and related products easier to manage and less expensive. Because different IT organizations have different deployment requirements, there are two basic MDB deployment models, single and multiple. Ingres provides GUI tools, services, and commands for system management and database administration. In this module, you used the Ingres Visual Manager to view system information. In every database, it is important to maintain security and access control. You identified the different types of MDB users and how to grant administrative and operator access. Maintaining your databases keeps the databases in good condition and helps you to quickly identify any problems. When you optimize a database, data distribution statistics are collected that help queries run more quickly and use fewer system resources. In the next module, you will optimize network visualization with the UMP.
Notes
7-29
Optimize the MDB

Module Summary
Notes
7-30
8
Optimize Network Visualization with the UMP
8-1

Module Objectives
Slide 8-1
Module Objectives

Install the UMP Create Scoreboards Provide Role-based Access to the UMP
Module Overview
Whether RBC is involved in business-to-business (B2B), business-to-consumer (B2C), or business-to-employee (B2E) initiatives, staying ahead of the competition in the fast-paced business world requires efficiency, flexibility, and speed. Business partners need to perform as if they are part of the same company. Customers expect access to information that enables them to make informed buying choices. Employees need the right information at the right time to make intelligent and timely decisions. They also need the right tools to take action on that information. In this module, you will discover that a portal is a consolidation point that combines information from various sources and presents a single, personalized view to the end user. Portals are used to deliver all types of information to support business processes to individuals. Portals are key components of the new information environment and provide access from virtually anywhere to anyone. You will also become familiar with portal security practices and create high-level, summarized views called scoreboards.
Notes
8-2
Optimize Network Visualization with the UMP Task 1: Install the UMP
Slide 8-2
Task 1: Install the UMP

The UMP provides a personalized web interface with intelligent delivery of information and permits information to be defined by role and user preference. Security and administrative control can be predefined through workplaces that are accessible through the Web. The UMP delivers consolidated status information from multiple sources in a single view and provides visual correlation, filtered event notifications, dynamic web reporting, and a high-level report summary. The UMP is a scalable solution that can be deployed on several servers to provide load balancing; it supports a Clustering Solution, Application Mirroring, Distributed Transactions Services available with Database applications, or Server-to-Server failover for methods of fault tolerance. Client access requires a web browser, a URL, and credentials for access to any deployed UMP Server. In addition, the UMP empowers employees, partners, and customers by providing the dynamic business information they need when they need it. The UMP provides a single vendor solution integrating HTTP and XML specifications using open Java technology. Built on the CleverPath Portal, the UMP can provide access to several resources in your enterprise from a single focal point.
Slide 8-3
Slide 8-4
Identify UMP System Requirements

The UMP uses Java 2 technology. The supported JRE is included with the UMP installation. Server hardware requirements vary depending on the number of users, reports published, and size of reports. A 50-user system requires the following minimum hardware specifications: Microsoft Windows 2000, Microsoft Windows NT, and Microsoft Windows 2003 Server requirements:

500 MHz processor 512 MB dedicated application memory
Notes
8-3

Interactive Demonstration UNIX Server requirements:

300 MHz processor 512 MB dedicated application memory 800 MB disk space for installation; 1 GB additional disk space for content recommended 100 MB database tablespace, with ability to grow as needed
All servers:

The UMP Server supports Intel-based servers running Microsoft Windows as well as Solaris with X-Windows installed and running on the system.
Task Purpose: Install the UMP. Make sure you have a Unicenter knowledge base running and that a managed node is present, both preferably on the local UMP computer. Note: Refer to the Unicenter Management Portal Installation Guide for complete installation information. 1 2 3 4 5 6 7 In Microsoft Windows Explorer, open the C:\InstallMedia\UNI_NSM_rll\Windows folder. Double-click the Setup.exe file. Select Installation Wizard for Unicenter Management Portal. Click Install. Click Next. Scroll to the end of the license agreement and select I accept the terms of the license agreement. Accept the default directory name or click Browse to choose another folder.
Notes
8-4
Optimize Network Visualization with the UMP Interactive Demonstration
8 9
Click Next. To create this directory, click Yes.
10 Verify the Portal Host Name is YourServerName. 11 Verify the Portal Port Number is 8090. 12 Verify the Shutdown Port Number is 8095. 13 Type unicenter in the Password for Portal Admin User and Confirm Password fields. 14 Click Next. 15 Type unicenter as the DB Administrator Password. 16 Verify the Database Name is MDB. 17 Click Next. Note: The UMP Installer will create the database and install the portal. This process will take a few minutes. 18 Click Next to view the installation results. 19 Click Finish. 20 Close Unicenter Product Explorer.
Link Unicenter NSM Management Components to the Portal

21 Open Microsoft Internet Explorer. 22 Choose Tools Internet Options. 23 On the Connections tab, click LAN Settings. 24 Clear Use a proxy server for your LAN and click OK. 25 To close the Internet Options dialog, click OK.
Notes
8-5

Interactive Demonstration 26 Type http://YourServerName:8090 in the Address field and press ENTER. 27 Type admin in the User Name field and unicenter in the Password field. Click Log In. 28 On the Workplace tab, click Task 1. Manage Components. 29 Click Discover. 30 For Alert Manager, Agent (DSM) Manager, Event Manager, and WorldView Manager, select your host as the Default Host Name. 31 Type unicenter in the WorldView Manager Password field. 32 Click Save. 33 Click the Connection link to configure Unicenter Configuration Management. 34 Click New. 35 Type YourServerName in the UCM Configuration Manager Name field. 36 Type unicenter in the Password field. 37 Click OK. 38 To return to the Manage Components screen, in the _UMP Administration Wizard window, click Back. Note: Do not click Back in the Microsoft Internet Explorer window. 39 Verify the status of each newly configured component.
Notes
8-6
Optimize Network Visualization with the UMP Task Summary
Task Summary
The UMP provides role-based, dynamic, and personalized views of management information securely over the Web, which addresses customers needs for rolebased management, management by exception, simplicity of use, and helping to deliver IT as a service. With the UMP, you can provide consolidated status information from multiple sources in a single view, visual correlation between infrastructure management applications, filtered event notifications tailored to roles and responsibilities, dynamic web reporting, and high-level report summary and graphs suited to non-IT users. The UMP is a powerful visualization tool because it provides dynamic business information to users when they need it. In this task, you installed the UMP and managed components after the installation. In the next task, you will create scoreboards.
Notes
8-7

Task 2: Create Scoreboards
Slide 8-5
Task 2: Create Scoreboards

The UMP enables you to create and publish high-level, summarized views called scoreboards. Scoreboards present information from the DSM, Enterprise Management, and the MDB. A variety of scoreboards can be created from many different types and sources of data, such as:
Slide 8-6
Service Level Agreements (SLA): Create an SLA scoreboard if you have Unicenter Service Level Management (SLM) deployed somewhere on your network and you have enabled batch report execution. WV-Business Process Views: Business Process Views can be published and presented in UMP 3.1. After choosing which Business Process View you want to publish in the scoreboard, you are presented with a severity breakdown of all underlying objects. From there, drill deeper to see detailed information as provided by the Topology Browser and Severity Browser. DSM-Agent Map: The Agent Map scoreboards provide the user with status and information about all resources the particular agent is monitoring. Actual value and threshold information is displayed by connecting to the DSM using DIA. DSM-Host Map: The Host Map scoreboards provide a slightly different view from the Agent Map scoreboards. Instead of grouping the view by agents and presenting a breakdown of resource statuses, the Host Map scoreboards present the host type and provide a breakdown of the statuses of all agents on that particular host. For example, to view the statuses of all agents on all Microsoft Windows 2000 computers, use Host Map scoreboards. WV-Agent Status by Agent Type: The Agent Status by Agent Type scoreboard provides a quick view of the number of agents in each severity state grouped by agent type. The scoreboard presents a status breakdown based on the type of agent, showing how many are in Normal, Warning, Critical, and other states.
Notes
8-8
WV-System Status by Host: The System Status by Host scoreboard provides a quick view of the number of hosts in each severity state grouped by host type. The scoreboard presents a status breakdown based on the type of host showing how many are in Normal, Warning, Critical, and other states. DSM-Agent View: The DSM-Agent View scoreboard provides a detailed look at what certain agents are currently monitoring. This is a very in-depth view of actual resources and their current statuses. The DSM-Agent View is similar to the Agent View in Unicenter NSM. In a well-organized GUI, you will be presented with current values and thresholds of all the monitored resources that you have selected.
Task Purpose: Build WorldView scoreboards. Create a Business Process View with a severity breakdown of all underlying objects. 1 2 3 4 5 6 7 Sign in to the Unicenter Management Portal as admin. On the Workplace tab, click Task 2. Create or Modify UMP Portlets. To create a new WV-System Status Scoreboard, click New. Select Normal from the Severity list. Type WV Windows_System Scoreboard in the Title field. Select 2 minutes from the Refresh list. On the Presentation tab, select Windows, Windows2000_Server, and Windows_NetServer from the Available Systems list. Click the Arrow button to move your selections to the Selected Systems list. On the Data Source tab, select your host from the Data Source list. Click Execute.
8 9
10 Verify the settings and click Configure.
Notes
8-9

Interactive Demonstration 11 Click Publish. 12 Click Finish. 13 Select the Knowledge tab. 14 In the left pane, expand Library\Enterprise Management\Unicenter Scoreboards\User Defined Scoreboards and select WV Windows_System Scoreboard. In the next interactive demonstration, you will design a systems monitoring scoreboard in the UMP.
Task Purpose: Design systems monitoring scoreboards. 1 2 3 4 5 6 7 8 9 Sign in to the Unicenter Management Portal as admin. On the Workplace tab, click Task 2. Create or Modify UMP Portlets. Click New to create a new DSM-Server View Dashboard. Type YourServerName in the Host Name Filter field. Click Next. Select the hosts you want to monitor from the Host List. Click Execute. Open the MCC. In the left pane, right-click Windows System Agent and choose Actions View Agent. The Agent View - Summary window opens. Memory and click Properties.
10 Choose View
11 Click Configure. The Windows System Agent - Memory - Dashboard dialog appears. 12 Type 5 in the Physical Memory Warning field. 13 Type 10 in the Physical Memory Critical field.
Notes
8-10
14 Type 1 in the Lag field. 15 Click OK. 16 Close the Windows System Agent - Memory - Dashboard dialog. 17 Click Change. The Poll Memory Watchers dialog appears. 18 Type 30 in the Poll Interval field. 19 Click OK. 20 Observe the Physical Memory Status change. 21 Minimize the Windows System Agent dialog. 22 To return to the Unicenter Management Portal, in the _UMP Administration Wizard window, click Refresh. Note: Do not click Refresh in the Microsoft Internet Explorer window. 23 Click Refresh to renew the dashboard page. 24 Observe the Windows System Memory Dashboard change. 25 Click the Memory drilldown icon. The Windows System Memory Watcher opens. 26 Click Edit. 27 Type 70 in the Physical Memory Warning field. 28 Type 90 in the Physical Memory Critical field. 29 Click OK. 30 Click OK to close the Windows System Memory Watcher window. 31 Click Done to close Windows System Memory Dashboard. 32 Click Refresh to renew the dashboard page. 33 Click Publish.
Notes
8-11

Interactive Demonstration 34 Enter a name in the View Name field. 35 In the _UMP Administration Wizard window, scroll to the bottom. 36 In the Available Channels field, select My Views and move it to Assigned Channels. 37 Click Publish. 38 Select Channels. 39 Expand Channels\My Unicenter Menu\My Views and select the view you have created. In the next interactive demonstration, you will filter events in the UMP.
Task Purpose: Filter events in the UMP. 1 2 3 4 5 6 7 8 9 Sign in to the Unicenter Management Portal. Select the Knowledge tab. Expand Library\Enterprise Management\Unicenter Event Management and select Event Console. On the Messages tab, click Configure. In the Selected FilterGroups section, move CA-System Agents and Network to the Selected list. In the Selected Displayable Properties section, remove User and Annotated from the Selected list. Click Apply. On the Log Messages tab, type MemPhys in the Search for field and click Go. Type Windows_NetServer in the Search for field and click Go.
10 Select Error from the Severity list and click Go.
Notes
8-12
Task Summary
Scoreboards provide summarized views of messages regarding system events that can occur in your IT infrastructure. Individual scoreboards for each resource type show only event messages for resources that are of interest to you. In each scoreboard detail pane, you can further filter event messages by severity. Consolidation of these scoreboards in the UMP centralizes management of different aspects of your infrastructure, helping ensure that important events are acted on in a timely manner. In this task, you created scoreboards and filtered events in the UMP. In the next task, you will provide role-based access to the UMP.
Notes
8-13

Task 3: Provide Role-based Access to the UMP
Slide 8-7
Task 3: Provide Role-based Access to the UMP

UMP security is managed through the creation of users and workgroups. A user is a person who has been identified, through a unique identifier and an associated password, as having access to the portal. A workgroup is a logical grouping of users. A user can belong to more than one workgroup
Slide 8-8
Slide 8-9
Create a Workgroup
By using workgroups to organize users who require access to the same information, the Portal Administrator and subadministrators can reduce redundant distribution of information and applications. The Portal Administrator can also use workgroups to implement security. Not only can permissions be assigned to workgroups, but workgroups can be nested to create a security hierarchy. Carefully designed and implemented workgroup policies and structures in your portal provide an effective layer of security. When the UMP is installed, three workgroups are created automatically:

Admin Template Editor Public
Note: Public does not appear in the list of workgroups, but every user is automatically assigned to it. You can add as many workgroups as necessary using the Manage Workgroups command in Portal Administration.
Notes
8-14
Optimize Network Visualization with the UMP Use Subgroups to Create a Workgroup Hierarchy
The Manage Workgroups form enables you to:

Add a workgroup. Edit the properties of an existing workgroup. View the list of users who are members of a workgroup. Create a subgroup of an existing workgroup. Delete workgroups.
Note: The deletion of a workgroup does not result in the deletion of users who were members of that workgroup.
Use Subgroups to Create a Workgroup Hierarchy

Workgroups can be nested to enable one group to have permissions for all content assigned to another larger workgroup. When creating a workgroup hierarchy using subgroups, it is important to note that:

A subgroup typically has fewer members than its parent group, but access to a wider range of content than its parent group. Members of a subgroup have access to all the content assigned to the parent workgroup, but the reverse is not the case. The hierarchy is not like an organization chart.
Subgroups are created and maintained using the Manage Workgroups command. A subgroup for an existing parent workgroup can be created by editing the properties of the parent workgroup and assigning an existing workgroup as a subgroup. A subgroup for an existing parent workgroup can also be created by selecting the existing workgroup and adding a new workgroup as a subgroup.
Notes
8-15

Task Purpose: Create nested workgroups. 1 2 3 4 5 6
Slide 8-10
Sign in to the Unicenter Management Portal as admin. On the Workplace tab, click Task 6. Manage Workgroups. Click Add. In the Workgroup Name field, type Unicenter Users and click Save. From the Workgroups list, select Unicenter Users and click Add Subgroup. In the Workgroup Name field, type Unicenter Administrators and click Save.
Create a User
The UMP supports three classes of portal users:

Users, who have no administrative access to the portal Subadministrators, who have been granted limited administrative functions to manage templates, a set of users, or workgroups Administrators, who have full access to all administrative functions
Users are created and managed with the Manage Users command in Portal Administration, which enables you to establish user profiles and assign users to workgroups. Note: The only limit to the number of portal users is the limit specified in your software license.
Notes
8-16
Optimize Network Visualization with the UMP Create a User
The Portal Administrator can delegate tasks to four types of subadministrators:
Group Administrator: This subadministrator is able to add, delete, and modify workgroups that are subgroups of the group to which they are assigned. A Group Administrator will be able to access the Portal Administration window from the Profile page, but will only be able to use the Manage Workgroups command. User Administrator: This subadministrator is able to add, delete, and modify users who are members of workgroups to which the User Administrator is assigned. A User Administrator will be able to access the Portal Administration window, but will only be able to use the Manage Users command. Group/User Administrator: This subadministrator has User Administrator and Group Administrator roles and will have access to the Manage Users and Manage Workgroups commands. Template Editor: This subadministrator is able to add, delete, and modify templates. A Template Editor will be able to access Template Administration tools from the Profile page.
The Portal Administrator is responsible for creating meaningful hierarchies and verifying the control of a subadministrator. For example, making a user the User Administrator of the Executives workgroup will give that person the privilege of removing every user in that group. As a result, the Portal Administrator must exercise caution when choosing which users have User and Group Administrator roles. To grant a user rights as a Group Administrator, User Administrator, or Group/ User Administrator for a workgroup, you must edit that users profile, select the workgroup, and assign a Role in Group for that user.
Notes
8-17

Duplicate a User
Duplicate a User
The Portal Administrator can create a new user by duplicating an existing user. The new user will have the same profile settings as the existing one except for the user name and password. One way the Portal Administrator can use this is to create a model user for each workgroup that has the default properties of all users in that group. When a new user needs to be created for a workgroup, the Portal Administrator can duplicate the model user, rather filling in all the user fields manually again.
Create a Portal Administrator

Portal Administrators have full access to all portal content and all of its administrative tools. Portal Administrators are responsible for implementing and maintaining security in the portal. Depending on the size or complexity of the portal, you might want more than one full Portal Administrator. The portal includes by default the single Portal Administrator, admin, but you can add as many additional Portal Administrators as necessary. Note: Select Portal Administrators carefully because they have the same access to the portal as the admin user does, including the ability to delete admin or remove it as a Portal Administrator. To grant a user full rights as a Portal Administrator, add the user to the Admin workgroup.
Add Multiple Portal Users

If user and authentication information already exists on another server, or in a database, you can save time by uploading it all at once to the Portal Server. Note: Only Portal Administrators can add users from these sources.
Notes
8-18
Optimize Network Visualization with the UMP Import User Information from an LDAP Server
Import User Information from an LDAP Server

The Lightweight Directory Access Protocol (LDAP) Properties form is used to import user and authentication properties from an LDAP server. You can specify the parameters for one or more LDAP servers. The import can be scheduled to take place automatically or you can use the Importer tool, accessible from a command prompt, to import user information as needed.
Import User Information from a CSV File

The comma-separated value (CSV) Properties form is used to configure the Portal Server to import user or workgroup information from a CSV file. A CSV file is a portable representation of a database in which each line, or record, contains information about a single user or workgroup with each field separated by a comma. After setting the properties, you must use the Importer tool to import the information.
Task Purpose: Create a user. 1 2 3 4 5 Sign in to the Unicenter Management Portal as admin. On the Workplace tab, click Task 5. Manage Users. Click Add. Type Analyst in the User name field. Type unicenter in the Password and Password Again fields. Note: User names and passwords in the portal are case-sensitive.
Notes
8-19

Interactive Demonstration 6 Scroll to the Groups section and select Unicenter Users from the Available list. Click the Arrow button to move Unicenter Users to the Member of list. Select User Admin from the Role in Group list. Click Save. Confirm that Analyst has been added to the Users list.
7 8 9
10 Log out of Unicenter Management Portal. 11 Type Analyst in the User Name field. 12 Type unicenter in the Password field. 13 Click Log In. 14 Select the Knowledge tab. 15 In the left pane, expand Library\Users. Notice the only user folder displayed is Analyst. 16 Click My Profile. 17 Access the Portal Administration link and confirm that you have access to Manage Users. 18 Close the Portal Administration window. 19 Log out of Unicenter Management Portal. 20 Type admin in the User Name field. 21 Type unicenter in the Password field. 22 Click Log In. 23 Repeat steps 14 and 15. Notice that admin sees all user folders. To observe who owns each folder, in the right pane, click Properties.
Notes
8-20
Optimize Network Visualization with the UMP Skill Practice
Skill Practice
Task Purpose: Create a user. 1 2 3 4 Create a user named Windows_Admin. Make it a member of Unicenter Administrators and grant it the role of Group/User Admin. Verify that Windows_Admin has been added to the Users list. Sign in as Windows_Admin. Access the Portal Administration link to confirm that you have access to the Manage Users and Manage Workgroups subadministrator functions. Sign in as admin. Access the Portal Administration link to confirm that you have access to all administrator functions. Edit the Unicenter Users workgroup and click View Member List.
5 6 7
Task Purpose: Create a new workplace and set it as the default for a group. 1 2 3 4 5 6 7 8 Sign in to the Unicenter Management Portal as Windows_Admin. On the Workplace tab, click Edit Workplaces. Type Windows_Admins in the Name field and click Add. In the Workplaces field, choose Windows_Admins. Click OK. Click Add Content. In the Available Content list, expand Enterprise Management\Unicenter Scoreboards\User Defined Scoreboards. Select WV Windows_System Scoreboard.
Notes
8-21

Interactive Demonstration 9 Click 1 to add WV Windows_System Scoreboard to Column 1.
10 From the Number of Columns list, select 2. 11 In the Available Content list, expand Enterprise Management\Unicenter Reports\Agent Technology\Configured Reports. 12 Select Windows Systems (Warning) Report. 13 Click 2 to add Windows Systems (Warning) Report to Column 2. 14 In Column 1, select 60% from the Width list. 15 Click OK. 16 Log out of Unicenter Management Portal. 17 Sign in as admin. 18 On the Workplace tab, click Task 4. Portal Administration. 19 Click Default Workplace. 20 Type Windows_Admin as the user name for the Unicenter_Administrators workgroup. 21 Click Update Changes. 22 Click Manage Users and then click Add. 23 Type Sysadmin in the Name field and give it a password. 24 Make Sysadmin a member of the Unicenter_Administrators workgroup and click Save. 25 Log out of Unicenter Management Portal. 26 Sign in as Sysadmin and notice that the Windows_Admins workplace has been pushed to Sysadmin as the default workplace.
Notes
8-22
Task Summary
By using workgroups to organize users who require access to the same information, you can reduce redundant distribution of information and applications. Not only can permissions be assigned to workgroups, but workgroups can be nested to create a security hierarchy. Carefully designed and implemented workgroup policies and structures in the UMP provide an effective layer of security. Providing role-based access to the UMP significantly reduces the potential for human error, the cause of most problems, and malicious activity. In this task, you used the Manage Users command in Portal Administration to create and manage users.
Notes
8-23

Assessment
Assessment
1 Which Unicenter NSM component provides a personalized web interface with intelligent delivery of enterprise management information and provides for information to be defined by role and user preference? a b c d 2 MDB DSM UMP Business Process View
Which command provides remote access to a UMP? a b c d www.ump:8090 http://portalserver:8090 http://unicenterNSM/9090 www.portalserver.com/ump
Which type of UMP scoreboard provides a breakdown of the statuses of all agents on a particular host? a b c d DSM-Agent Map DSM- Host Map DSM-Agent View WV-Status by Agent
Notes
8-24
Optimize Network Visualization with the UMP Assessment
Which built-in Portal account is able to add, delete, and modify assigned workgroup users and access the Portal Administration window, but is only able to use the Manage Users command? a b c d Template Editor User Administrator Group Administrator Group User Administrator
Notes
8-25

Module Summary
Slide 8-11
Module Summary

Install the UMP Create Scoreboards Provide Role-based Access to the UMP
Another key visualization feature of Unicenter NSM, the UMP provides personalized views of information specific to the role, interests, and business needs of the end user at RBC. This clear, real-time view of information makes it easy to understand how IT affects a particular business unit or application. It eliminates users from viewing lengthy status reports that do not apply directly to them to find information. The UMP interface helps users to see what their business looks like and to add their own information to make the presentation of the information meaningful to them. In this module, you installed the UMP, created scoreboards to view specific, high-level summary information, and managed access by creating users and workgroups in Portal Administration.
Notes
8-26
9
9-1

Module Objectives
Slide 9-1
Module Objectives

Identify Unicenter Systems Performance Architecture Install Unicenter Systems Performance Components Configure Unicenter Systems Performance Create a Unicenter Systems Performance Report View Real-time Data with Performance Scope
Slide 9-2
Module Overview
Systems Performance provides the means to track current performance issues in the system infrastructure, and assist in long-term planning. Access to historic and real-time performance data assists with problem analysis and capacity planning. You can monitor key parameters that influence system performance and applications, and compare what is actually happening against a set of predefined operational parameters. Use Systems Performance to determine the most efficient use of resources by examining how busy each server is, which servers are overused or underused, when computers are being used, whether usage is increasing or decreasing, and where bottlenecks occur. In this module, you will install the Systems Performance Manager and the Systems Performance Agent. You will examine Systems Performance architecture and components. Then you will use the Systems Performance Configuration application to create Systems Performance profiles. You will also create performance reports with the different Systems Performance applications.
Notes
9-2
Administer Unicenter Systems Performance Task 1: Identify Unicenter Systems Performance Architecture
Slide 9-3
Task 1: Identify Unicenter Systems Performance Architecture

As business operations become more dependent on e-Business, the need grows for tools which enable you to efficiently manage the performance of the servers and devices within your enterprise. To gain control of the critical, distributed, and in many cases disparate systems, you need to be able to understand how these systems are loaded, so that you can obtain the best response times, optimize throughput, and help ensure longterm reliability. What is needed are tools that can analyze and present this data in a meaningful and consistent form, enabling visualization of the performance of the systems and devices, not just for a given point in time, but for days, weeks, months, and even years. To achieve an effective Performance Management strategy, it is important to address two fundamental requirements:

The rapid identification and resolution of unexpected performance problems that can and do occur, day to day, across the enterprise. The ability to perform long term planning, trend analysis, and reporting to help ensure current and future needs are met.
Unicenter NSM Systems Performance is designed to address these two fundamental requirements and provide a comprehensive and holistic solution to the complex challenge of managing the performance and throughput of the many heterogeneous servers, workstations, and devices on which missioncritical e-Business applications depend. The Unicenter Systems Performance architecture supports such a distributed environment by providing high levels of scalability and enabling easy configuration across many computers. Furthermore, because it is often desirable to define logical groupings in the enterprise and manage each of these groups independently, the architecture implements the concept of multiple configuration domains.
Notes
9-3

Task 1: Identify Unicenter Systems Performance Architecture
Slide 9-4
The main Systems Performance architecture components are:

Performance Data Grid Performance Domain Server Performance Distribution Server Performance Agent Performance Applications
The following graphic shows the main components in the Systems Performance architecture:
Slide 9-5
Notes
9-4
Administer Unicenter Systems Performance Performance Data Grid
Systems Performance architecture has two main functions:

Slide 9-6
To provide access to and management of the performance data gathered by the Systems Performance Agents To enable the configuration of the Systems Performance Agents
Performance Data Grid

With each Systems Performance domain capable of supporting up to 100,000 monitored servers and workstations, there is a critical need for a mechanism that provides fast and reliable access to the vast amount of performance data that is gathered. In particular, it is important that the data held in performance cubes across the enterprise:

Can be summarized and stored in the MDB so that you can correlate it with your organizational assets and other management data Is readily accessible to management and analysis applications that need performance data Is reliably marshaled and stored in a highly scalable way, but is centralized enough to support easy data management and recovery Can easily have data management rules applied so that you can age and aggregate the data as it gets older Can be changed into a form that has greater business relevance, such as health indexes, workload-based or application-based metrics, and customized metrics that you create
The Performance Data Grid (PDG), in conjunction with the MDB, provides all these capabilities, besides others. In essence, the PDG provides performance information that covers any time period, at any degree of granularity, for any managed element in your enterprise, such as a device, server, or application.
Notes
9-5

Performance Domain Server The PDG is formed from a network of orthogonal, distributed Performance Distribution Servers that form a grid to service data requests. This grid creates a single image of the performance data for the entire enterprise and grants you seamless access to the data. A notable feature of this design is that you do not need to know where the data you are requesting is physically stored, or which end-point is servicing the request; you simply place a query on the grid and obtain a response.
Performance Data and the MDB

The MDB is unique in the industry today, in that it defines one schema definition for all new and existing CA product tables. To help maximize the business benefits this brings, Systems Performance integrates with the MDB by automatically storing historical performance data in its tables. Historical performance data is modeled within the RDBMS using a STAR schema based design that enables true, relational access to the performance metrics. When employed, this simple schema enables those with little Microsoft SQL Server knowledge to be able to query the data to extract the information they require. To maximize the your out-of-the box experience, summary performance data will be automatically loaded into the MDB as soon as Systems Performance has been installed.
Slide 9-7
Performance Domain Server

The Performance Domain Server acts as a gateway to the PDG and stores all performance configuration policies for an entire domain. The advantage of centralizing the configuration data into one location is to simplify back ups and other disaster recovery procedures. Performance Configuration GUIs are used to review and modify these policies and the Performance Domain Server distributes any configuration changes to the various Performance Distribution Servers for onward distribution to the agents.
Notes
9-6
Administer Unicenter Systems Performance Performance Distribution Server
Multiple clients can simultaneously connect to the Performance Domain Server and engage in configuration operations. You can perform configuration operations from any computer on which the Performance Configuration application is installed. You can even use a single computer to administer multiple domains; however, a client cannot connect to more than one Performance Domain Server at a time. The Performance Domain Server enables the upload of historical performance data into the MDB with data sourced from the PDG. This happens, by default, after the Performance Domain Server has been installed. Although the data is published to the MDB automatically, the content and granularity is configurable. It is therefore essential that the MDB is configured optimally and tuned appropriately. Additionally, the Performance Domain Server enables the publishing of Asset and Configuration information known to the Domain Server into the MDB. The Performance Domain Server is also responsible for providing and enforcing access control to prevent unauthorized users from accessing the data and meta data contained within the PDG.
Slide 9-8
Performance Distribution Server

Performance Distribution Servers request configuration data from the Performance Domain Server and deliver it to the Performance Agents. As this data is centralized at the Domain Server level, Distribution Servers operate without requiring any local persistent information. Therefore, you can install or re-install Distribution Servers without the need to back up and restore the configuration data.
Notes
9-7

Performance Agent A key function of a Distribution Server is to manage performance data for the computers for which it is responsible and maintain this data in its local cube store. Each Distribution Server communicates with the others and has information about the contents of their cube stores. To achieve this, each Distribution Server examines its local cube store and builds up an index of the computers for which it has cubes, the cubes that exist for each computer, and the resource metrics for each cube. The Distribution Server then passes its index to the other servers with which it is registered so that they all contain upto-date information on each other.
Slide 9-9
Performance Agent
Systems Performance uses Performance Agents running on each monitored computer to collect data on a wide range of system and database resources, SAP resources, and SNMP-based resources. To help ensure that the configuration state of any Performance Agent in the Configuration domain is always known, the architecture implements a handshaking mechanism between the Performance Agents and the Distribution and Domain Servers. The Configuration Domain Server always knows the configuration state of agents. The client GUI clearly represents the configuration state by displaying status color keys. The most severe state is propagated upwards, thus letting you expand into the GUI to quickly determine if any computers are in an undesirable configuration state.
Notes
9-8
Administer Unicenter Systems Performance Define Unicenter Systems Performance Applications
There are two types of agents: Type Real-Time Performance Agent (prfAgent) Description This agent is responsible for the real-time, transient collection of performance data, which it supplies to client applications such as Performance Scope. This agent provides facilities for collecting, storing, and managing historical, time-banded data. Where necessary, it can act as a proxy to enable the monitoring of resources from SNMPenabled hosts or devices that cannot support a Performance Agent directly, such as a network router.
Historical Performance Agent (hpaAgent)
Slide 9-10
Define Unicenter Systems Performance Applications

Systems Performance provides graphical applications that you can use to visualize, analyze, report, and configure performance and resource usage data. The Systems Performance components are:

Performance Scope Performance Trend Performance Reporting Performance Configuration Chargeback Data Utilities
Notes
9-9

Performance Scope These applications and utilities enable you to manage performance data using intuitive, platform-independent techniques, so you can administer different operating systems and devices using the same methods and techniques. The Performance Agents support these applications by gathering both real-time and historical performance data from the computers on which they are running.
Slide 9-11
Performance Scope
Performance Scope is used to monitor the current performance of your enterprise and perform real-time analysis of any performance problems or outages that might occur. Performance Scope enables you to pinpoint the scope, effect, duration, and cause of problem events to minimize user impact.
Slide 9-12
Performance Trend
Performance Trend facilitates capacity management by providing historical performance and resource usage data in a spreadsheet, enabling you to display and analyze data with ease. Presenting monitored resource data in various chart styles enables you to observe, at a glance, any trends occurring across your enterprise. With Performance Trend, you can:

Identify heavily loaded servers and devices Observe patterns of activity and use of applications and servers Identify problematic trends Investigate the impact of moving applications and users to other servers Determine the effect of running workload at different times Provide automated graphical reports Provide reports in various formats: HTML, XLS, CSV, and hardcopy
Notes
9-10
Administer Unicenter Systems Performance Performance Trend
Performance Trend is supplied with plug-in macros for averaging and statistical analysis. The following table defines the available macros: Macro Average_PerDay_Or_Machine Description This macro will, for the metric being plotted by the selected Period or Enterprise chart, calculate the average value for each day in a Period Cube, or each computer in an Enterprise Cube, and plot all these values on the same chart with all the days, or computers, on the X axis. This macro is virtually identical to the Average_PerDay_Or_Machine macro, but provides additional functionality by plotting minimum and maximum values for each day, or computer, as well as the average value.
AverageMinMax_PerDay_Or_ Machine
Notes
9-11

Performance Reporting Macro Description
AverageMinMax_PerTimeband This macro essentially collapses all the planes of data in a Period Cube or Enterprise cube into one average day. In the case of a Period Cube, for the metric being plotted, it will take all the individual days and find the average value across all the days for each time band. This effectively provides a report that represents "a typical day in the month of." By generating this chart against a Period Cube containing data from April 1st through April 30th, you can identify the average, minimum, and maximum value at 09:00am, for example, across all the days in the month. This will help find unusual patterns of behavior that are hard to spot when you look at each isolated day. For an Enterprise Cube, it will produce an aggregated view of how all the servers in the Enterprise cube performed over the course of a day. AverageMinMax_PerTimeband This macro is virtually identical to the macro _PlusData AverageMinMax_PerTimeband, but provides additional functionality by adding a data line that shows the original raw date, the original values for each day in the selected Period Cube or computer in the selected Enterprise Cube.
Slide 9-13
Performance Reporting
Performance Reporting presents highly graphical and interactive chart-based or tabular reports of historical performance data, which are available through a standard web browser, such as Microsoft Internet Explorer. You can generate reports dynamically to show any level of detail, from the average performance of a group of servers over an entire year, in one chart, to a detailed analysis of a given application's performance over a specific period in a given day.
Notes
9-12
Administer Unicenter Systems Performance Performance Configuration
Slide 9-14
Performance Configuration
Performance Configuration enables the configuration, distribution, and management of customized Systems Performance policies across the enterprise. You use Performance Configuration to create and apply configuration policies, named profiles, to Performance Agents. After a Performance Agent has received a profile, it knows what performance data to collect, when to collect it, and where to send it. You can easily create complex Systems Performance policies using the highly graphical and intuitive Performance Configuration GUI. You can then drag these policies on computers, devices, or Configuration Groups, resulting in immediate and dynamic reconfiguration of the agents on the selected remote nodes. Systems Performance Configuration policies have the additional benefit of being operating system and device independent. This independence provides a layer of abstraction from the specifics of each platform and enables you to create a single policy that you can deploy to many disparate nodes. This enables you to manage many computers with different operating systems using the same policy. When you initially install Performance Agents, the agents register themselves with their Configuration Domain controller. The agents are then automatically supplied a default profile, helping ensure they are immediately productive outof-the-box.
Notes
9-13

Data Utilities
Slide 9-15
Data Utilities
Systems Performance provides command line utility tools to perform various functions. The following table defines two of these: Utility PDtoDB Description This command line utility:
Supports the export of performance information
from both the PDG and conventional Performance Cubes into an RDBMS database enabling you to precisely tailor which data is exported, all the way down to the resource instance level to be run in the background as part of an automated workload schedule environments
Provides comprehensive data selection options,
Is designed as a console application to enable it
Supports both Windows and Linux
PDtoXML
This command line utility:

Supports the export of performance information
from both the PDG and conventional Performance Cubes into XML format
Provides the same data selection options as
PdtoDB, enabling you to precisely tailor which data is exported, all the way down to the resource instance level to be run in the background as part of an automated workload schedule environments
Is designed as a console application to enable it
Supports both Windows and Linux
Notes
9-14
Administer Unicenter Systems Performance Task Summary
Task Summary
Although the computing facilities in many companies are typically large and diverse, Systems Performance architecture supports such a distributed environment by providing high levels of scalability and enabling easy configuration. In this task, you examined the main components and functions of Systems Performance architecture. In the next task, you will install Systems Performance components.
Notes
9-15

Task 2: Install Unicenter Systems Performance Components
Slide 9-16
Task 2: Install Unicenter Systems Performance Components

Systems Performance monitors the performance of the servers and devices in your enterprise, helping you apply consistent management policies to disparate operating systems. Systems Performance provides historic and real-time information to assist with problem analysis and capacity planning. Also, simplified reports provide immediate value on installation.
Slide 9-17
Install Systems Performance Manager

Systems Performance can be installed on Microsoft Windows, UNIX, and Linux systems. The Systems Performance Linux and UNIX installer:

Is fully integrated with the main NSM installer Uses PIF technologies on UNIX and Linux Additionally uses Linux standard RPM for Linux Installations Supports both interactive and silent installations Is based on MSI as required by the Install Standards Is invoked through Product Explorer or directly from the Setup.exe program Calls out to the CCS installer through a standalone CCSExeinterface executable Supports both interactive and silent installations
The Systems Performance Microsoft Windows installer:

Notes
9-16
Administer Unicenter Systems Performance Interactive Demonstration
Two types of installation modes are available:
Interactive: Standard UI dialogs are displayed with two modes available: Install Mode: Installs Systems Performance components Response File Mode: Is used for generating a response file Note: The Response File Mode is only available on computers that do not already have Systems Performance installed.
Silent: No dialogs are displayed. However, a valid response file is required to confirm acceptance of the CA EULA. There are two modes available: Install Mode: Installs Systems Performance components Upgrade Mode: Performs silent upgrade of components
Task Purpose: Install Systems Performance Manager. 1 2 Open Microsoft Windows Explorer. Launch Unicenter Product Explorer. a For Ingres MDB student environments, open the C:\InstallMedia\UNI_NSM_r11\Windows folder and double-click the setup.exe file. For Microsoft SQL Server MDB student environments, open the C:\InstallMedia\UNI_NSM_r11_1\Windows folder and doubleclick the setup.exe file.
Expand the Unicenter for Windows folder, select Installation Wizard for Unicenter NSM Systems Performance, and click Install. The CA Unicenter Systems Performance Setup Wizard appears. Click Next.
Notes
9-17

Interactive Demonstration 5 6 7 8 9 Scroll to the bottom of the license agreement, select I accept the terms in the license agreement, and click Next. Type your information in the fields provided, accept the default option, Install on this machine, and click Next. Select the Create a Systems Performance Domain/Custom Install setup option and click Next. From the Performance Chargeback list, select This feature will not be available. From the Performance Agent list, select This feature will not be available.
10 Click Next. 11 Accept the default file paths for where to install the product and click Configure MDB. The Edit MDB Configuration Settings dialog appears. 12 Type unicenter in the Password field, and click Validate. 13 After the MDB credentials are successfully validated, click OK. 14 Click Next. 15 Type YourServerName in the Performance Distribution Server field and the Performance Web Reporting field, and click Next. 16 Accept the default Performance Scope options and click Next. 17 Accept the default Performance Trend options and click Next. 18 Click Install. 19 After Performance Manager has successfully installed, click Finish. 20 When prompted to restart your computer, click Yes.
Notes
9-18
Administer Unicenter Systems Performance Install Systems Performance Agent
Prepare Sample Data

After the computer starts, complete the following steps to prepare sample Systems Performance data for later activities in the module. 21 In Microsoft Windows Explorer, navigate to the C:\Student\UR215 folder and execute the updatesampledata.bat file. 22 Right-click the Windows Status Bar and select Task Manager. 23 Select the Processes tab and confirm that capmpde.exe is running. 24 If capmpde.exe is not running, open a command prompt. a b c Type configserver stop and press ENTER. Type configserver start and press ENTER. Examine the Processes tab again and confirm that capmpde.exe is running.
Install Systems Performance Agent

The Systems Performance Agents collect performance data from supported operating systems, applications, and database resources distributed throughout an enterprise. The Systems Performance Agents then provide this data to one or more management nodes, where you can view and analyze it.
Task Purpose: Install Systems Performance Agent. 1 2 3 Click Start and then choose Programs Workstation. VMware VMware
On the Virtual Windows 2003 Server 2 tab, under Commands, click Start this virtual machine. When prompted, press
CTRL+ALT+INSERT
to begin.
Notes
9-19

Interactive Demonstration 4 5 6 7 8 Click OK to close out the password information window. Type administratorzz in the User name field. Type usxxyyzzcai in the Password field. From the Log on to field, select the classroom domain, and click OK. In Microsoft Windows Explorer, expand My Computer Folders on .host. a Shared
For Ingres MDB student environments, open the C:\InstallMedia\UNI_NSM_r11\Windows folder and double-click the setup.exe file. For Microsoft SQL Server MDB student environments, open the C:\InstallMedia\UNI_NSM_r11_1\Windows folder and doubleclick the setup.exe file.
When prompted, click Run.
10 In Unicenter Product Explorer, expand Unicenter for Windows and select Installation Wizard for Unicenter NSM Systems Performance. 11 Click Install. 12 When the Unicenter NSM Systems Performance Setup Wizard appears, click Next. 13 Scroll to the bottom of the license agreement, select I accept the terms in the license agreement, and click Next. 14 Type YourName in the User Name field and YourCompanyName in the Organization field, select Install on this machine, and click Next. 15 Select Install Performance Agents, clear the Express option, and click Next. 16 Accept the default destination install paths and click Next. 17 Accept the default Performance Agent install path, type YourServerName in the DNS host name or IP address of Distribution Server field, and click Next.
Notes
9-20
18 Click Install. 19 Click Finish.
Verify the Performance Agent Installation

20 Click Start and then choose Programs Computer Associates Unicenter NSM Agent Technology Service Control Manager. The Agent Technology Services Manager appears.
Identify the File Location of Performance Cubes

21 In Microsoft Windows Explorer, open the C:\Program Files\CA\Unicenter NSM\PerfData\performance_cubes folder. Note: It will take two or three minutes for the cube files to be created. A folder named computername will contain the .pcm files.
Task Summary
Systems Performance helps you apply consistent management policies to all of the server platforms in your enterprise. The Systems Performance Agent collects performance-related data and provides this data to one or more management applications, where you can view and analyze it. In this task, you installed the Systems Performance components. In the next task, you will configure Systems Performance.
Notes
9-21

Task 3: Configure Unicenter Systems Performance
Slide 9-18
Task 3: Configure Unicenter Systems Performance

The Performance Configuration component enables you to use an intuitive GUI to perform component configuration from a central point of control. All performance configuration information is held in a centralized repository and is automatically distributed to the remote performance components as necessary. With the use of the UI client, connection to Domain Server is available from any workstation.
Slide 9-19
The Performance Configuration component provides two GUI applications that enable you to configure Systems Performance: Performance Configuration Application and Performance Profile Configuration Editor. The consistent use of Wizards to act as a guide for all object creation operations enables ease of use. Both components offer a browser-style GUI and use wizards to perform a variety of creation operations. Component Performance Configuration Application Description Use the main Performance Configuration application GUI to display and organize all devices in the enterprise and to view the profiles that exist for the Performance Agent. Through the main Performance Configuration GUI, you can configure, manage, and distribute performance policies across the enterprise. Use the Profile Configuration Editor to configure the Performance Agent for data collection and management. You access this component from the Profiles Configuration area in the main GUI. Highlighting a profile and selecting Properties opens the Profile Configuration Editor.
Performance Configuration Profile Editor
Notes
9-22
Administer Unicenter Systems Performance Create a New Performance Profile
When you launch Performance Configuration, the main Performance Configuration application window appears, displaying the top-level configuration view for your enterprise. The left panel presents a configurable hierarchical network navigation tree view of the enterprise. It also presents color-coded representations of the configuration status of the Performance Agents, including propagation of worst state upwards. Highlighting a profile and selecting Properties opens the Performance Configuration Profile Editor. You use the Performance Configuration Profile Editor to configure the Performance Agent for data gathering and for managing the data gathering policies throughout the enterprise. After you install a Performance Agent, the agent attempts to register with the Performance Configuration application. When Performance Configuration receives the registration message, Performance Configuration delivers the Default Profile to the Performance Agent. The agent initially uses the Default Profile settings to determine what resources should be monitored and when the data should be collected. By using the Default Profile, the Performance Agent is automatically configured to immediately provide a resource monitoring function. The Default Profile, however, can potentially generate high overhead because by design, the Default Profile collects data for almost all resources. Using the Performance Configuration Profile Editor, you can create, modify, and view a profile. These functions enable you to customize the data gathering properties of the Performance Agent to meet the specific resource monitoring requirements in your organization.
Slide 9-20
Create a New Performance Profile

The Performance Profile Creation Wizard automates the process of creating a new profile. All new profiles are based on an existing profile. Using the Performance Configuration Profile Editor, you can customize configuration by modifying the properties of the profile.
Notes
9-23

Interactive Demonstration You can create and apply a new profile that defines the data gathering and management properties of a selected computer or group. When you create a new profile, you name it and use the Performance Configuration Profile Editor to specify collection details and a selection period. Using this component, you can also select a resource set to be monitored and identify the recipient computer that will collect the data.
Task Purpose: Create and apply a new performance profile. 1 Click Start and then choose Programs Computer Associates Unicenter NSM Systems Performance Performance Configuration. When prompted, select YourServerName from the Select MDB list and click OK. When prompted, select YourDomainServer from the Select Performance Domain Server list and click OK. In the left pane, expand Profiles and select Systems Performance. In the right pane, scroll down and click the Create Profile link. The Performance Profile Create Wizard appears. 6 7 8 9 Type Base in the Name field and click Next. Select Default Profile from the list and click Finish. In the left pane, right-click Data Gathering and choose Modify. The Data Gathering dialog appears. On the Times tab, from the Frequency list, select 5 minutes. The Custom Resource Set Wizard appears. 11 Type Base in the Custom Resource Set Name field and click Next. 10 On the Resources tab, click Add.
2 3 4 5
Notes
9-24
12 From the Full Set list, expand Microsoft Windows Server 2003, Standard Edition, select Processor, and click Add to move the resource to the Custom Set list. Repeat for Memory, LogicalDisk, PhysicalDisk, and Network Interface. 13 Click Finish. 14 Click OK. 15 In the left pane, expand Data Management\Daily Cubes\Full Daily Cube, right-click Delivery Machines, and choose Modify. The Full Daily Cube Properties dialog appears. 16 On the Delivery tab, click Modify. The Recipient Machine Selection dialog appears. 17 Select YourServerName from the Available Machines list, click Add to move it to the Recipient Machines list, and click OK. 18 Click OK. 19 Close the Performance Configuration Profile Editor. 20 In the left pane, expand Machines and Devices and navigate to YourVirtualServer. 21 In the right pane, drag the Base profile to YourVirtualServer in the left pane. 22 When a Unicenter Performance Configuration message appears, click OK. 23 In the left pane, expand Machines and Devices and drill down to YourServerName\Systems Performance. Observe the newly delivered Base profile.
Notes
9-25

Task Summary
Task Summary
Easily accessible and customizable visual information results in faster problem analysis and response. Both the Performance Configuration application and the Performance Configuration Profile Editor offer a browser-style GUI and use wizards to perform a variety of creation operations. In this task, you used both Performance Configuration applications to create and apply a new performance profile. In the next task, you will use Performance Reporting to identify and investigate problems in your enterprise.
Notes
9-26
Administer Unicenter Systems Performance Task 4: Create a Unicenter Systems Performance Report
Slide 9-21
Task 4: Create a Unicenter Systems Performance Report

With Performance Reporting, you can choose to view performance data for several different types of objects, such as selected applications, databases, or servers. You can also generate executive reports, which are high-level summaries of the overall performance and health of the enterprise. In addition, you can schedule reports to run automatically in the future and save the finished reports in PDF or CSV format. Performance Reporting provides powerful analytical capabilities, including baseline generation, threshold breach analysis, statistical and health index reports, and the ability to create composite, virtual metrics. It provides clear, easy to read reports, appropriate for technical, managerial, and executive users. Performance Reporting is integrated with Unicenter NSM Web Reporting Server (WRS) and Portal. It is platform-independent where the client side is browsercontrolled and the server side uses Microsoft Windows and Linux. The capability to use UNIX on the server side is in the planning stages. You can create new reports in three simple steps:

Slide 9-22
Select a computer. Select the metrics on which to report. Select a presentation option.
Task Purpose: Create connections from the Web Reporting Server to Unicenter NSM manager components to enable data collection for reports. 1 2 Select Start Programs Computer Associates Unicenter NSM CA Web Server. Under CA Applications, select WRS.
Notes
9-27

Interactive Demonstration 3 4 5 6 In the left pane of the Unicenter Web Reporting Server dialog, expand Administration and select Managed Components. In the right pane, click Discover. For Agent (DSM) Manager, Event Manager, and WorldView Manager, select your host as the Default Host Name. Type unicenter in the WorldView Manager Password field, and click Save.
In the next interactive demonstration, you will identify and investigate potential problems using Server and Device Reports.
Task Purpose: Identify and investigate potential problems using Server and Device Reports. 1 Expand Unicenter Reports. WRS has reports for many Unicenter NSM components. In this activity, we are focusing on Systems Performance. 2 Expand Systems Performance. At this level, all the report classes are visible, for example Applications and Business Process Views. 3 4 Expand Servers and Devices. Expand Report Templates and CA Configured Reports. Report Templates contain several Report Types, for example Alert Reports and Baseline Reports. These are all configuration wizards that can be used to create your own custom reports. 5 Under CA Configured Reports, expand Windows Servers. These are configured reports provided for default functionality.
Notes
9-28
Under Windows Servers, click on the report Processor Usage for past 4 weeks. This report shows how all the Microsoft Windows Servers in the enterprise have been performing for the past four weeks. You will notice from the chart, the values for the metrics are higher for the following three computers: ESM_MAIL1.ca.com ESM_MAIL2.ca.com ESM_MAIL3.ca.com
In the right pane, scroll down to the Table view and locate the three computers. You will now focus on each of these by individually drilling down into each computer.
Start with the computer ESM_MAIL3.ca.com, click on the arrow link in its row. A new Detail Report window appears showing a finer view of the four week data. Focus only on the metrics Processor, % Processor Time, and _Total, which as its names indicates, is overall processor utilization.
On the chart, click Options, and select only the metrics Processor, % Processor Time, and _Total. Observe that processor utilization is fairly constant across the period.
10 Close the Detail Report window. 11 Repeat the process for the computer ESM_MAIL2.ca.com. Observe that the results are similar with processor utilization fairly constant across the period.
Notes
9-29

Interactive Demonstration 12 Repeat the process for the computer ESM_MAIL1.ca.com. Observe that Processor Utilization started to rise about three days ago. This requires further investigation. 13 In the right pane, scroll down to the Table view and drill down further into the current day. This is where processor utilization marginally peaks. To obtain additional information, the report will need to be re-configured. 14 On the report in focus, in the upper right corner, click Configure. The configuration wizard for a standard report appears. As you are reconfiguring a report, all required fields are pre-filled and pre-selected. 15 The wizard has three tabs: Machine Selection, Metric Selection and Presentation. To continue to focus on the computer ESM_MAIL1.ca.com, click Next. For metric selection, instead of viewing processor metrics, you need to see which processes are running high. 16 Right-click Metric Selection Mode and change the selection from Specific Instances to All Instances, and then click Add Metrics. 17 In the Resource Type field, select Process. 18 From the Subtype selection list, select % Processor Time, and click Done. 19 Click Next. 20 Click Execute. A report appears showing the average processor utilization for individual processes. The report is sorted by process name.
Notes
9-30
21 To change the Table view sort order, click the % Processor Time column name twice. The new sort order appears, descending by % Processor Time. Observe that the EXCHNG32 and STORE processes are high percentage users of processor time. These are Microsoft Exchange processes. Next we will use Application Reports to look further into the problem. 22 Close all report windows leaving open the primary WRS window. Now that you know what is causing the high processor utilization, you can further determine the why by using the Application Reports in the next interactive demonstration.
Notes
9-31

Task Purpose: Identify and investigate potential problems using an Application Performance Report. So far you have only focused on reports in the Severs and Devices report class. Using the problem you have been investigating until now, you will see how reports in the Applications class can help you find the root cause of problem. 1 Choose Unicenter Reports CA Configured Reports. Systems Performance Applications
Recall that when you drilled down from Servers and Devices class reports, you found that Microsoft Exchange processes are causing overall processor utilization to rise significantly for the computer ESM_MAIL1.ca.com. Two Microsoft Exchange reports are provided by default. 2 Select Microsoft Exchange Servers Performance for past 4 weeks. You will see a report with the Exchange Processes EXCHNG32 and STORE, and other critical system metrics Processor, Disk, and Memory. Unlike Servers and Devices reports where computers are selected and then metrics, Application reports are configured so that all computers are automatically added that have the application metrics selected, in this example, Exchange Processes. 3 4 5 In the right pane, scroll down to the Table view. Locate the computer ESM_MAIL1.ca.com and click the arrow link in its row. On the detail report, click Options and remove all selected metrics.
Notes
9-32
One by one, select each metric to view its trend for the four weeks, and then remove it. You can see that for all the metrics, except LogicalDisk, % Disk Time, and _Total, there is a strong trend showing a rise in usage towards the last few days of the four week period. The Application Performance report shows information similar to what is available in the Servers and Devices report area. Application reports can be set up on any application, and all computers that have the application installed will be automatically included in the report. However, you need more information before you can identify the actual problem.
Close all report windows leaving open the primary WRS window.
In the next interactive demonstration, you will use Application Statistic reports to determine the actual problem with the over usage of the computer.
Task Purpose: Identify and investigate potential problems using an Application Statistics Report. 1 Choose Unicenter Reports Systems Performance Applications CA Configured Reports Exchange Servers Statistics for past 4 weeks. In the right pane, scroll down to the Table view. Locate the computer ESM_MAIL1.ca.com and click the arrow link in its row. On the detail report, on the chart, click Options. Microsoft
2 3 4
Notes
9-33

Interactive Demonstration 5 6 In the lower right of the chart, change the chart style from Bars to Lines. Click Options to remove it. Four metrics appear: Number of Connections Number of Messages Delivered / Min Number of Messages Sent / Min Number of Users served by the Exchange Server
For the first three, the trend is the same. The dip every few days is on each weekend. For the last metric, the User Count, note that for the last few days, the number of users served increases by 1,750 from 4,500 to 6,250. Using Systems Performance Reporting, you have found the root cause. The extra number of Exchange users has caused the server processor utilization and memory to rise significantly. Therefore you should plan to increase the power of the server or move the new users to a new Exchange Server.
Task Summary
With Performance Reporting, you use a web interface to extract historical data to determine and investigate problems in your enterprise. By careful analysis of the historical data, you can resolve problems before they happen. This enables the company to understand what resources are being used, how they are used, and to prepare for future growth. In the next task, you will use Performance Scope to view real-time and historic instances in your enterprise.
Notes
9-34
Administer Unicenter Systems Performance Task 5: View Real-time Data with Performance Scope
Slide 9-23
Task 5: View Real-time Data with Performance Scope

Performance Scope uses platform-independent techniques to provide a view of the performance of the servers and devices across the enterprise. This enables you to use the same methods and techniques to visualize and analyze disparate operating systems and devices.
Slide 9-24
Each Performance Scope view seamlessly joins real-time and historical data, so that you can examine the performance of resources now and in the past. It also displays the performance of several different resources. Multiple concurrent views are supported, enabling the monitoring of many computers. You can assign predefined thresholds to resources, causing alarms to be generated and actions to occur when a threshold breach occurs.
Task Purpose: View real-time data with Performance Scope. 1 2 3 4 5 6 7 Click Start and then choose Programs Computer Associates Unicenter NSM Systems Performance Performance Scope. When prompted, from the Select MDB list, select YourServerName and click OK. When prompted, from the Select Performance Domain Server list, select YourDomainServer and click OK. In the left pane, drill down to YourVirtualServerName. Expand Processor and choose % Processor Time. In the right pane, right-click _Total and choose Add Selection to View Add to new Chart View. Observe historical performance data and real-time performance data simultaneously.
Notes
9-35

Interactive Demonstration 8 9 From the toolbar, choose View Historical Chart Settings.
The Historical Performance Data dialog appears. In the Day of View section, select Previous available day. 10 Click OK. In the next interactive demonstration, you will graph multiple metrics with Performance Scope.
Task Purpose: Graph multiple metrics. 1 2 3 4 5 6 From the toolbar in Performance Scope, choose Resources Resource View. Show
In the left pane, choose YourVirtualServerName\Processor\% Privileged Time. In the right pane, right-click _Total and choose Add Selection to View Add to existing Chart View. Repeat steps 3 and 4 for the metrics % Interrupt Time, % Idle Time, and % User Time. From the toolbar, choose Window Chart_View_1 - Chart Performance View. Observe the multiple types of data. To size the Legend box to display all metrics, select View Legend Box. Auto Size
In the next interactive demonstration, you will create multiple graphs with Performance Scope.
Notes
9-36
Task Purpose: Create multiple graphs. 1 2 3 4 5 From the toolbar in Performance Scope, choose Resources Resource View. Show
In the left pane, right-click YourVirtualServerName and choose Create new View Create New Chart View. From the toolbar, choose Resources Show Resource View. In the left pane, choose YourVirtualServerName\PhysicalDisk and select % Disk Read Time. In the right pane, right-click _Total and choose Add Selection to View Add to existing Chart View. The Set Default View dialog appears. Select Chart_View_2 - Chart Performance View and click OK. Repeat steps 4 to 6 for % Disk Time, % Disk Write Time, and % Idle Time. From the toolbar, choose Window Performance View. Select View Chart_View_2 - Chart
6 7 8 9
Auto Size Legend Box. Properties.
10 From the toolbar, choose View
The Chart View Properties dialog appears. 11 Type Disk Usage in the Description field and click OK. 12 From the toolbar, choose Window Performance View. 13 From the toolbar, choose View Chart_View_1 - Chart
Properties.
The Chart View Properties dialog appears. 14 Type CPU Usage in the Description field and click OK.
Notes
9-37

Interactive Demonstration In the next interactive demonstration, you will customize the Performance Scope application.
Task Purpose: Customize the look and feel of Performance Scope. 1 2 3 4 5 6 7 8 9 From the toolbar in Performance Scope, choose View The General Options dialog appears. Click the arrow in the Gallery box, select the fit to curve icon, and click Apply. Click the arrow in the Grid Lines box, select the both icon, and click Apply. Click OK. From the toolbar, choose View 3D Chart Settings. The 3D View Properties dialog appears. Select Full 3D View and click Apply. Change the X Angle to 35, change the Y Angle to 35, and click Apply. Move the 3D Slider all the way to the right and click Apply. Click OK. Chart Background Color Chart. The Color dialog appears. 11 Select a color and click OK. 12 From the toolbar, choose View The Color dialog appears. 13 Select a color and click OK. 14 Select File Save View. The Save View dialog appears. Chart Grid Color. Chart Style.
10 From the toolbar, choose View
Notes
9-38
Administer Unicenter Systems Performance Skill Practice
15 In the Save In field, navigate to C:\Documents and Settings \Administratorzz\Application Data\CA\Unicenter NSM\Scope \MachineViews folder, and click Save. 16 Select File Close View. 17 Repeat the previous four steps to save and close the second view.
Skill Practice
Task Purpose: Create a Performance Scope chart. Create a chart with the following parameters:
Network Interface Bytes/Received Bytes/Sent Bytes/Total Cube Chart Horizontal Grid
Chart Style
Task Summary
Performance Scope enables you to monitor the current performance of the enterprise and perform real-time analysis of any performance problems or outages that may occur. In this task, you used Performance Scope to view realtime data, graph multiple graphics, and create multiple graphs for ease of comparison. The ability to create a custom look of Performance Scope enables ease of use.
Notes
9-39

Assessment
Assessment
1 Which component of Systems Performance architecture enables you to obtain performance information for any time period and at any degree of granularity for a managed element in the enterprise? a b c d 2 Performance Agent Performance Data Grid Performance Domain Server Performance Distribution Server
Which Systems Performance architecture component enables the upload of historical performance data into the MDB with data sources from the PDG? a b c d Performance Agent Performance Applications Performance Domain Server Performance Distribution Server
Which Performance Agent manages historical, time-banded data? a b c d prfAgent OS Agent hpaAgent UNIX Agent
Notes
9-40
Administer Unicenter Systems Performance Assessment
Which component enables the configuration, distribution, and management of customized Systems Performance policies? a b c d Performance Trend Performance Scope Performance Data Grid Performance Configuration
From which three areas can the Systems Performance Agents collect performance data? (Choose three.) a b c d e Applications Operating systems Management nodes Standard UI dialogs Database resources
After you install a Performance Agent, it attempts to register with the Performance Configuration application. When Performance Configuration receives this request, what is delivered back to the Performance Agent? a b c d Default Profile MDB password Performance cube Performance Profile
Notes
9-41

Assessment 7 Which Systems Performance application enables you to create preconfigured and customized performance reports? a b c d 8 Performance Trend Performance Scope Performance Reporting Performance Configuration
Which Systems Performance application enables you to graph a real-time view of data? a b c d Performance Trend Performance Scope Performance Data Grid Performance Configuration
Notes
9-42
Administer Unicenter Systems Performance Module Summary
Slide 9-25
Module Summary

Identify Unicenter Systems Performance Architecture Install Unicenter Systems Performance Components Configure Unicenter Systems Performance Create a Unicenter Systems Performance Report View Real-time Data with Performance Scope
Slide 9-26
Systems Performance monitors the performance of the servers that deliver business-critical IT services using consistent, fact-based management policies that reduce complexity. Systems Performance provides a flexible and extensible architecture that simplifies the management of the numerous systems and devices that make up today's complex infrastructures. Its facilities for collecting, analyzing, and reporting information simplify performance and capacity trend analysis, and increase IT responsiveness to unexpected problems, ensuring higher service levels. In this module, you installed the Systems Performance Manager and the Performance Agent. You examined the main components and functions of Systems Performance architecture. You used the Performance Configuration, Performance Scope, and Performance Reporting applications to create performance profiles and reports.
Notes
9-43

Course Summary
Slide 9-27
Course Summary

Plan a Unicenter NSM Implementation Install Unicenter Components Configure Systems Monitoring Discover System and Network Devices Optimize Network Visualization Automate Response to Events and Alerts Optimize the MDB Optimize Network Visualization with the UMP Administer Unicenter Systems Performance
Slide 9-28
Notes
9-44
A
Assessment Answers
A-1
Assessment Answers
Assessment Answers
Module 1
Question 1: b, d, and e Question 2: a and d Question 3: b and d Question 4: b
Module 2
Question 1: c Question 2: d and e Question 3: c Question 4: b Question 5: c Question 6: d Question 7: a Question 8: a Question 9: a Question 10: a Question 11: a and d Question 12: b and d Question 13: b, d, and e Question 14: c
Notes
A-2
Assessment Answers
Question 15: a Question 16: a Question 17: a
Module 3
Question 1: a Question 2: d Question 3: d Question 4: a Question 5: a Question 6: a Question 7: d Question 8: a Question 9: c
Module 4
Question 1: c Question 2: b Question 3: a Question 4: d
Notes
A-3
Assessment Answers
Module 5
Question 1: b Question 2: a Question 3: b Question 4: c
Module 6
Question 1: d Question 2: b Question 3: b Question 4: b Question 5: c, d, and e
Module 7
Question 1: c and d Question 2: b and c Question 3: c Question 4: c, e, and f Question 5: a
Notes
A-4
Assessment Answers
Module 8
Question 1: c Question 2: b Question 3: b Question 4: b
Module 9
Question 1: b Question 2: c Question 3: c Question 4: d Question 5: a, b, and e Question 6: a Question 7: c Question 8: b
Notes
A-5
Assessment Answers
Notes
A-6

EDURV215111SE

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EDURV215111SE

Uploaded by

Copyright:

Available Formats

Computer Associates

1 Plan a Unicenter NSM Implementation

2 Install Unicenter Components

Configure Systems Monitoring

3 Configure Systems Monitoring

Implementation and Administration Student Workbook

Discover System and Network Devices

4 Discover System and Network Devices

Optimize Network Visualization

5 Optimize Network Visualization

6 Automate Response to Events and Alerts

Implementation and Administration Student Workbook

Optimize the MDB

7 Optimize the MDB

8 Optimize Network Visualization with the UMP

Administer Unicenter Systems Performance

9 Administer Unicenter Systems Performance

Implementation and Administration Student Workbook

Implementation and Administration Student Workbook

About This Workbook

Variable values Emphasis Titles of books

Quotation Marks Computer Text Computer Text Italics SMALL CAPS

Implementation and Administration Student Workbook

About This Course

Course Agenda Day 1

Module 2: Install Unicenter Components

Implementation and Administration Student Workbook

Module 5: Optimize Network Visualization

Module 7: Optimize the MDB

Module 9: Administer Unicenter Systems Performance

Implementation and Administration Student Workbook

Case Study: Really Big Corporation

Service Availability Branding

Implementation and Administration Student Workbook

management solutions they support

IT can assess business impact of events

Integrated view of events and their

business and customers

Service Availability Strategy

Implementation and Administration Student Workbook

Solution Manage Risk

Align IT Investments with Business Needs

Implementation and Administration Student Workbook

Classroom Computer Hostnames

Implementation and Administration Student Workbook

Plan a Unicenter NSM Implementation

Implementation and Administration Student Workbook

Plan a Unicenter NSM Implementation Module Overview

Plan a Unicenter NSM Implementation

Task 1: Analyze the Corporate Environment

Implementation and Administration Student Workbook

Plan a Unicenter NSM Implementation Task 1: Analyze the Corporate Environment

Plan a Unicenter NSM Implementation

Implementation and Administration Student Workbook

Plan a Unicenter NSM Implementation Task 2: Evaluate Platform and OS Requirements

Task 2: Evaluate Platform and OS Requirements

Plan a Unicenter NSM Implementation

Task 3: Define Unicenter NSM Component Configurations

The four essential Unicenter NSM components are:

Implementation and Administration Student Workbook

Plan a Unicenter NSM Implementation Task Summary

Plan a Unicenter NSM Implementation

Task 4: Define a Fault Tolerant Deployment

The following graphic is an example of a fault tolerant deployment: