NSM Slmo

Unicenter Service Level
Management
User Guide
3.0
This documentation and related computer software program (hereinafter referred to as the Documentation) is for
the end users informational purposes only and is subject to change or withdrawal by Computer Associates
International, Inc. (CA) at any time.
This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without
the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright
laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for
their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only
authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the
license for the software are permitted to have access to such copies.
This right to print copies is limited to the period during which the license for the product remains in full force and
effect. Should the license terminate for any reason, it shall be the users responsibility to return to CA the reproduced
copies or to certify to CA that same have been destroyed.
To the extent permitted by applicable law, CA provides this documentation 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 this documentation, 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 product referenced in this documentation and this documentation is governed by the end users
applicable license agreement.
The manufacturer of this documentation is Computer Associates International, Inc.
Provided with Restricted Rights as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or
DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.
2002 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Contents
Chapter 1: Introducing Unicenter SLM

Audience .....................................................................................
Features ......................................................................................
Architecture ..................................................................................
Console ..................................................................................
Collectors ................................................................................
Report Repository .........................................................................
Database .................................................................................
Conventions ..................................................................................
1-1
1-2
1-3
1-4
1-5
1-6
1-6
1-7
Chapter 2: Planning Your Installation

Disk Allocation ...............................................................................
Disk Space ...................................................................................
Data Collection ...........................................................................
Transaction Log ...........................................................................
Maximum Shared Memory ....................................................................
Host Name Resolution ........................................................................
Host Name Validation .........................................................................
Unicenter Components ........................................................................
Installation Path ..............................................................................
2-1
2-2
2-2
2-3
2-3
2-4
2-4
2-5
2-5
Contents
iii
Chapter 3: Configuring the Environment

Locating the Configuration Files ................................................................ 3-1
Verifying Port Numbers........................................................................ 3-2
Changing Port Numbers for Services ........................................................ 3-2
Changing Port Numbers for the Console ..................................................... 3-3
Changing Port Numbers for the Collector .................................................... 3-4
Installing the Java Runtime Environment (JRE) ................................................... 3-4
Configuring the Java Plug-in ................................................................ 3-6
Configuring the javapath ................................................................... 3-7
Synchronizing the JDBC Password .............................................................. 3-8
Adding the pcmtocsv.exe Path .................................................................. 3-8
Defining User Passwords ....................................................................... 3-8
Configuring CAM/CAFT Permissions ........................................................... 3-9
Upgrading Unicenter SLM .................................................................... 3-10
Removing the Database ................................................................... 3-10
Upgrading SLM Console .................................................................. 3-11
Upgrading Collectors ..................................................................... 3-14
Upgrading Custom Metrics ................................................................ 3-15
Removing Unicenter SLM ..................................................................... 3-16
Chapter 4: Using Collectors

Starting the Collector .......................................................................... 4-2
Understanding Collector Processes .............................................................. 4-2
Defining Single Data Collections ................................................................ 4-3
Restarting the Collector .................................................................... 4-4
Modifying Data Collections ................................................................. 4-4
Importing Objects from Unicenter Common Object Repository..................................... 4-4
Installing the Unicenter SLM CORE Gateway................................................. 4-5
Importing Unicenter Objects ................................................................ 4-6
Reloading the Common Object Repository ................................................... 4-8
Understanding Severity and Propagated Severity Collection ................................... 4-8
Importing Performance Cubes ................................................................. 4-10
Configuring Unicenter SLM for Performance Cubes .......................................... 4-10
Configuring Unicenter Performance Management for Data Collection ......................... 4-11
Importing Unicenter Advanced Network Option Data ........................................... 4-12
Configuring Unicenter SLM for Network Data............................................... 4-12
Processing Network Data .................................................................. 4-13
iv
Unicenter Service Level Management User Guide
Importing Unicenter Management for Web Servers Response Data ............................... 4-13
Configuring Unicenter SLM for WRM Data ................................................. 4-14
Processing WRM Data .................................................................... 4-15
Testing the WRM Import.................................................................. 4-15
Importing External Data ...................................................................... 4-16
Import File Requirements ................................................................. 4-17
Preparing Your Data...................................................................... 4-19
Creating an Import Metric Template ....................................................... 4-19
Activating an Import Metric Template...................................................... 4-20
Testing an Import Metric Template ........................................................ 4-21
Deleting an Import Metric Template ....................................................... 4-22
Chapter 5: Using Reports

Understanding the Report Server ............................................................... 5-1
Understanding Reports ........................................................................ 5-2
Creating Reports Interactively .............................................................. 5-3
Creating Reports Automatically ............................................................ 5-3
Using Reports............................................................................. 5-6
Understanding Report Groups ................................................................. 5-6
Report Group Hierarchy ................................................................... 5-7
Creating Report Groups ................................................................... 5-8
Adding Data Collections to Report Groups .................................................. 5-9
Using Report Groups ...................................................................... 5-9
Deleting Report Groups ................................................................... 5-10
Listing Report Group ..................................................................... 5-10
Exporting Reports and Publishing Links ....................................................... 5-11
Configuring the Web Server ............................................................... 5-11
Exporting Reports ........................................................................ 5-12
Publishing Report Links .................................................................. 5-14
Controlling Report Content ............................................................... 5-15
Maintaining the Report Repository ............................................................ 5-16
Deleting Temporary Reports .............................................................. 5-16
Saving Reports to the Report Repository .................................................... 5-17
Deleting Reports ......................................................................... 5-17
Contents
Chapter 6: Using the Interface

Propagating Status Colors ...................................................................... 6-2
Refreshing Status Trees ........................................................................ 6-2
Controlling Access to the User Interface ......................................................... 6-3
Using the Metric Charter ....................................................................... 6-4
Using Parameters .......................................................................... 6-4
Using Load Graph ......................................................................... 6-5
Changing the Display ...................................................................... 6-5
Chapter 7: Using Metrics

Understanding Metrics......................................................................... 7-2
Folder Metrics ............................................................................. 7-2
Data Collection Metrics..................................................................... 7-2
Adding Metric Definitions...................................................................... 7-2
Example: Adding a Gauge Metric ........................................................... 7-3
Example: Calculating Available Memory ..................................................... 7-5
Example: Monitoring Bandwidth Use ........................................................ 7-7
Platform Specific Metrics ...................................................................... 7-10
Activating Platform Specific Metrics ........................................................ 7-11
Additional Metric Files ........................................................................ 7-12
Chapter 8: Understanding the Database

Understanding Data Storage .................................................................... 8-2
Collector Storage .......................................................................... 8-2
Console Storage ........................................................................... 8-3
Understanding Data Reduction ................................................................. 8-4
Customizing Data Reduction Policy ......................................................... 8-5
Maintaining the Database ...................................................................... 8-6
Understanding the cron Job ................................................................. 8-6
Reading Database Error Messages ........................................................... 8-6
Improving Database Performance ........................................................... 8-7
Recovering an Inconsistent Database ........................................................ 8-9
Checkpointing the Database ............................................................... 8-10
vi
Chapter 9: Using Traps and Logs

Using Unicenter Event Console.................................................................
Generated SNMP Traps ....................................................................
Using Message Records and Actions ........................................................
Integrating SNMP Trap Messages ...........................................................
Logging ......................................................................................
Maintaining Console Log Files..............................................................
Changing Logging ........................................................................
Adding Logging ..........................................................................
Checking Email Messages......................................................................
9-1
9-2
9-4
9-5
9-6
9-6
9-7
9-8
9-9
Appendix A: Database Tables

Metric Definition Tables ....................................................................... A-1
metric_field_values ........................................................................ A-1
metric_fields .............................................................................. A-2
metric_menues ............................................................................ A-3
metric_reports ............................................................................ A-3
metrics ................................................................................... A-4
Data Collections Tables ........................................................................ A-5
collected_data ............................................................................ A-5
copy_index ............................................................................... A-5
data_collect_attrs .......................................................................... A-6
data_collections ........................................................................... A-6
import_rules .............................................................................. A-6
System Configuration Tables ................................................................... A-7
smm_module_defs ........................................................................ A-7
smm_module_values ...................................................................... A-7
smm_modules ............................................................................ A-8
smm_sub_systems ........................................................................ A-8
smm_systems ............................................................................. A-9
snmp_config .............................................................................. A-9
Contents
vii
Report Tables ............................................................................... A-10

business_hours .......................................................................... A-10
default_business_hours .................................................................. A-10
export_reports ........................................................................... A-11
profile_defs ............................................................................. A-11
profile_values ........................................................................... A-12
profiles ................................................................................. A-12
report_commands ....................................................................... A-12
report_done ............................................................................. A-13
report_group ............................................................................ A-13
report_group_goals ...................................................................... A-14
report_group_members .................................................................. A-14
report_group_parents .................................................................... A-14
report_identifier ......................................................................... A-15
report_index ............................................................................ A-15
report_options........................................................................... A-16
report_time ............................................................................. A-16
service_goals ............................................................................ A-17
service_goalvalues ....................................................................... A-17
service_incident_victims ................................................................. A-18
service_incidents ........................................................................ A-18
Appendix B: Command Reference

createDb ..................................................................................... B-1
deleteData ................................................................................... B-2
deleteDataCollection .......................................................................... B-2
deleteMetrics................................................................................. B-3
dropDb ...................................................................................... B-3
installData ................................................................................... B-4
lsMetrics ..................................................................................... B-4
lsReportGroups .............................................................................. B-8
mkIndex ..................................................................................... B-8
runReport ................................................................................... B-8
showDcid.................................................................................... B-9
slmCopyBatchReports ........................................................................ B-9
slmLoadColl ................................................................................ B-10
slmLoadGroup .............................................................................. B-11
smmBuild .................................................................................. B-12
smmCheck .................................................................................. B-13
smmCollect ................................................................................. B-14
viii
smmdbd .................................................................................... B-15

smmDataImport ............................................................................. B-16
smmReduceData ............................................................................. B-18
smmReportIndex ............................................................................ B-19
smmReportd ................................................................................ B-19
smmReporter ................................................................................ B-19
smmSetup ................................................................................... B-21
smmdb_maintenance ......................................................................... B-21
smmstart .................................................................................... B-22
smmstop .................................................................................... B-22
Appendix C: Metric Syntax

Metric Definitions ............................................................................. C-1
Service Goal Definitions ................................................................... C-1
Folder Properties .......................................................................... C-2
Data Collection Properties ................................................................. C-2
Mandatory Metric Properties ................................................................... C-6
Mandatory Metric Fields for pathagent and appagent ......................................... C-7
Mandatory Metric Fields for snmpCollect.................................................... C-7
Definitions of Available Metrics ................................................................ C-8
cai_cpuUtil: Windows NT Server CPU Utilization ............................................ C-8
cai_cpuUxUtil: UNIX Server CPU Utilization ............................................... C-10
cai_fileSysUsed: Percentage File System Space Used on a Volume ............................. C-11
cai_memoryUtil: NT Server Memory Utilization............................................. C-12
cai_memoryUxUtil: UNIX Server Memory Utilization ....................................... C-14
cai_ntAvailService: Windows NT Service Availability ....................................... C-15
cai_swapUxUtil: UNIX Server Swap Utilization ............................................. C-16
CA_MSEXCHANGE_DataBase_Status: MS Exchange Database Status ........................ C-17
CA_MSEXCHANGE_DISK_Status: MS Exchange Disk Status ................................ C-19
CA_MSEXCHANGE_MTA_Queue_Status: MS Exchange MTA Current Queue Status .......... C-20
CA_MSEXCHANGE_MTA_Receive_Queue_Status: MS Exchange MTA Receive Queue Status .. C-21
CA_MSEXCHANGE_MTA_Send_Queue_Status: MS Exchange MTA Send Queue Status ....... C-23
CA_NT4_cpu_Current_Processor_Util: Windows NT 4.0 Current CPU Utilization .............. C-24
CA_NT4_cpu_Total_Processors_Util: Windows NT 4.0 Total CPU Utilization .................. C-25
CA_NT4_MEMORY_Current_Paging_memory: Windows NT 4.0 Current Used Paging Memory C-26
CA_NT4_MEMORY_Current_Physical_memory : Windows NT 4.0 Current Used Physical
Memory ................................................................................. C-28
CA_NT4_MEMORY_Current_Virtual_memory: Windows NT 4.0 Current Used Virtual Memory C-29
CA_NT4_NETWORK_Input_Packets_Status: Windows NT 4.0 Status of Received Packets ...... C-31
CA_NT4_NETWORK_Output_Packets_Status: Windows NT 4.0 Status of Sent Packets ......... C-32
Contents
ix
CA_NT4_SERVICES_Service_Availability: Windows NT 4.0 Service Availability ..............

CA_PathDoctor: Import CA PathDoctor Ping Data ..........................................
CA_perfAgent: Import CA Performance Agent Data ........................................
CA_SAP_R3_GENERAL_Items: SAP R/3 Maintenance Items ................................
CA_SAP_R3_GENERAL_Status: SAP R/3 Status ...........................................
CA_SAP_R3_Number_Dump_Daily: Number of SAP R/3 Short Dumps Today ................
CA_SAP_R3_Process_Status: Status of SAP R/3 Work Process ...............................
CA_SAP_R3_Status_Dump_Daily: Status of SAP R/3 Short Dumps Today ....................
CA_SAP_R3_UPDATES_Cancelled_Count: Number of SAP R/3 cancelled updates ............
CA_SAP_R3_UPDATES_Cancelled_Status: SAP R/3 Status of Cancelled Updates .............
CA_SAP_R3_UPDATES_Pending_Count: Number of SAP R/3 Pending Updates ..............
CA_SAP_R3_UPDATES_Pending_Status: SAP R/3 Status of Pending Updates ................
CA_W2K_cpu_Current_Processor_Util: Windows 2000 Current CPU Utilization...............
CA_W2K_cpu_Total_Processors_Util: Windows 2000 Total CPU Utilization ...................
CA_W2K_LOGICAL_VOLUMES_File_Fragmentation: Windows 2000 File Fragmentation on a
Volume .................................................................................
CA_W2K_LOGICAL_VOLUMES_fileSysUsed: Windows 2000 File System Space Used on a
Volume .................................................................................
CA_W2K_MEMORY_Current_Paging_memory: Windows 2000 Current Used Paging Memory .
CA_W2K_MEMORY_Current_Physical_memory: Windows 2000 Current Used Physical
Memory ................................................................................
CA_W2K_MEMORY_Current_Virtual_memory: Windows 2000 Current Used Virtual Memory .
CA_W2K_NETWORK_Input_Packets_Status: Windows 2000 Status of Received Packets .......
CA_W2K_NETWORK_Output_Packets_Status: Windows 2000 Status of Sent Packets ..........
CA_W2K_SERVICES_Service_Availability: Windows 2000 Service Availability ................
cisco_cpu5: Cisco Device CPU Utilization ..................................................
dns: DNS Server Response Time and Availability ...........................................
fr-util: Bandwidth Utilization Measured on a Frame Relay DLCI .............................
ftp: FTP Throughput and Availability ......................................................
ftp-ping: FTP Server Response Time and Availability........................................
hpux-fileSysUsed: Percent File System Space Used on a HP-UX MIB System ..................
hr_fileSysUsed: Percent File System Space Used on the Host MIB System .....................
hr_systemNumUsers: Number of Users on a Host MIB System ...............................
http: HTTP Server Response Time and Availability .........................................
if-cisco-qdrop: Number of Queue Drops on a Interface ......................................
if-discards: Number of Discards Per Sample on an Interface..................................
if-discardsPs: Number of Discards Per Second on an Interface ................................
if-errors: Number of Errors Per Sample on an Interface ......................................
if-errorsPs: Number of Errors Per Second on an Interface ....................................
if-octets: Number of Octets Per Sample on an Interface ......................................
if-octetsPs: Number of Octets Per Second on an Interface ....................................
if-packets: Number of Packets Per Sample on an Interface ...................................
C-33
C-35
C-36
C-37
C-38
C-39
C-41
C-42
C-43
C-45
C-46
C-47
C-49
C-50
C-51
C-52
C-54
C-55
C-56
C-58
C-59
C-60
C-62
C-63
C-65
C-67
C-68
C-70
C-71
C-72
C-74
C-75
C-77
C-78
C-80
C-81
C-83
C-85
C-86
if-packetsPs: Number of Packets Per Second on an Interface .................................. C-88

if-util: Interface Bandwidth Utilization ..................................................... C-89
imap: IMAP Mail Server Response Time and Availability .................................... C-91
ipnet: IP Network Delay and Availability ................................................... C-92
ldap: LDAP Server Response Time and Availability ......................................... C-94
nfs: NFS Server Response Time and Availability ............................................ C-95
nfs_cp: NFS Mounted File Copy ........................................................... C-97
nfs_find: NFS Mounted Directory Search Time .............................................. C-98
nis: NIS Service Response Time and Availability ........................................... C-100
nntp: NNTP Server Response Time and Availability ........................................ C-101
ntp: NTP Server Response Time and Availability ........................................... C-103
pop3: POP Server Response Time and Availability ......................................... C-104
propagated_sev: TNG Propagated Severity Property ....................................... C-106
rmon-util: Port/LAN Utilization Measured on a RMON Probe .............................. C-108
severity: TNG Severity Property .......................................................... C-109
smb: SMB Service Response Time and Availability ......................................... C-112
smtp: SMTP Server Response Time and Availability ........................................ C-114
tcp_echo: TCP ECHO Response Time and Availability ...................................... C-115
wins: WINS (NetBIOS) Name Service Response Time and Availability ....................... C-117
Appendix D: Advantage Ingres Tips and Tricks

Installing Advantage Ingres Manually .......................................................... D-1
Installing Advantage Ingres on UNIX ....................................................... D-1
Installing Advantage Ingres on Windows .................................................... D-4
Creating the Database ..................................................................... D-4
Verifying the Installation ................................................................... D-5
Moving the Transaction Log ................................................................... D-5
Changing the Host Name ...................................................................... D-7
Operating System Configuration............................................................ D-7
Unicenter SLM Configuration .............................................................. D-7
Creating a Backup ............................................................................ D-8
Backing Up the Database ................................................................... D-8
Recovering Backed Up Data ................................................................ D-9
Contents
xi
Chapter
Introducing Unicenter SLM

Unicenter Service Level Management (SLM) is a comprehensive service
monitoring and web-based reporting solution that helps both administrators and
business managers understand and manage predefined service goals across all
IT resources. Unicenter SLM lets network and system management personnel
measure and produce service level reports and statistics for resources available
across the IT infrastructure.
Unicenter SLM can monitor Service Level Agreement (SLA) and performance
reporting of eBusiness infrastructure by administrators or service providers as
well as establishing performance baselines as a basis for service goals. In
addition, Unicenter SLM can generate web-based historical reports on provided
services in relation to predefined service goals and monitor delivered services
from an end user's perspective.
Audience
This guide contains information for system administrators and other technical
personnel who want to configure and use Unicenter SLM.
This guide assumes you are familiar with the operating system on which
Unicenter SLM is installed and the database in use. This guide also assumes you
have technical knowledge of the areas in which you plan to collect data.
11
Features
Features
Unicenter SLM provides the following features and benefits:
12
Provides efficient production and distribution of service level reports

through the use of web servers, allowing the creation of reports from
anywhere on the network using a standard web browser.
Provides access to all administration tasks and operational status monitoring
through a web interface.
Provides flexible presentation of data in reports, including tables and bar or
line graphs.
Presents results relative to previously defined service goals and as deviation
reports that include only results that exceed previously defined service
goals.
Collects data from a wide range of services and instrumentations.
Sends SNMP traps to the management system (when configured). For
example, Unicenter SLM can be configured to send alarms based on
availability measurements for web servers, DNS servers, and SMTP servers.
Exports service level reports to another (external) web server, accessible to
users or customers, with customizable information levels.
Defines service incidents, identifying periods during which data is invalid
for specific collections.
Displays and correlates any combination of metrics in two or three
dimensions.
Architecture
Architecture
Unicenter SLM has a distributed architecture that includes the following
components:
Console
Collectors
Report Repository
Database
The following illustration shows a console and two collectors. The report
repository and database are running on the console system.
13
Architecture
Console
The console configures data collections and report groups, produces reports, and
monitors current status. The console contains the configuration database as well
as providing the following functionality:
Produces service level reports.
Configures and maintains data collections.
Displays collected system status.
Defines and modifies data collections, report groups, report properties, batch
report productions and service incidents.
Restarts and stops collectors.
Displays the status of data collections and Unicenter SLM systems.
Runs and displays reports.
Maintains the report repository.
Note: The console also operates as a collector and can perform data collections.
If the console performs no data collections, it will still run the smmCollect
daemon. This process is responsible for receiving and installing collected data
from remote collector systems.
User Interface
The Unicenter SLM user interface is accessible from any web browser with a
network connection to the console. This interface can be accessed through TCP
port 6668.
Web Server
You can control access to the user interface by configuring access control on the
Unicenter SLM web server. By default, access requires a user name and
password (default slmo and slmo respectively).
Static reports stored in the report repository do not have access control. For more
information on controlling access, see the chapter Planning Your Installation in
this guide.
14
Architecture
Daemon Processes
The daemon processes on a console system include the following:
Database engine (Advantage Ingres or MS SQL)
Data collector (smmCollect)
Data loader (smmdbd)
Report server (smmReportd)
Web server (mhttpd)
Optionally, a standard web server (httpd)
Important! These daemons start at boot time and must be running for the Unicenter
SLM system to operate properly.
Collectors
The Unicenter SLM collector collects and measures data from a wide variety of
sources. This data is regularly uploaded to the console system for reporting.
Note: The only daemon process on a Unicenter SLM collector system is
smmCollect.
Available data collectors include the following:
snmpCollect
The snmpCollect collector gathers data using any SNMP MIB variable or
combination of variables. This collector can use advanced expressions prior to
data logging.
pathagent
The pathagent collector measures IP network delay and availability. This
collector sends SNMP traps for state changes to the management console.
appagent
The appagent collector measures system and service response time and
availability. This collector sends SNMP traps for state changes to the
management console and can measure a wide range of services such as FTP,
HTTP, DNS, SMTP, NTTP, POP3, TCP echo, NFS, and so on.
15
Architecture
coreimport
The coreimport collector imports objects from a Unicenter Common Object
Repository (CORE) and collects properties from these objects.
import
The import collector imports configuration data, log files, or externally collected
data from files. This collector supports transparent import of collected data from
the following sources:
Unicenter Performance Management performance cubes
Unicenter Advanced Network Option data
Unicenter Management for Web Servers response data
ASCII data files supported by the Import Wizard
Report Repository
The report repository stores and organizes all produced reports. Installed with
the Unicenter SLM console, the report repository contains reports, as HTML
documents, organized into categories by group, period, and type. You can access
reports through both the Unicenter SLM web server (on port 6668) and a
standard web server (on port 80).
Note: To control access to reports on a standard web server, the server must be
installed and configured separately to provide users with read-only access to
report documents.
Database
The database stores and maintains all configuration information and collected
data. The database is based on either the Ingres database or Microsoft SQL server
product. For more information on database tables, see the appendix Database
Tables.
16
Conventions
Conventions
This guide uses the following standard conventions to consistently communicate
ideas.
Case-Sensitivity
All class, command, directive, environment parameter, function, and property

names mentioned in this guide are case-sensitive. The names must be spelled
exactly as shown. System command and environment variable names may be
case-sensitive, depending on the requirements of your operating system.
Cross-References
References to information in other guides, or in other sections within this guide,

use the following form:
Convention
Usage
Guide_Name guide
Indicates the name of another guide.
"Chapter_Name"
Indicates the name of a chapter in this or another guide.
The following example uses these conventions:

For more information on installation, see the appendix "Installing SLM" in
the Getting Started.
Syntax
Syntax and user input use the following form:
Convention
Usage
Italic
Indicates a variable name or placeholder for which you

must supply an actual value.
[ ]
Indicates optional operands.
The following example uses these conventions:

wvgethosts -o hosts[-c class][-r repositoryName][ -u user ][-p password]
In this example, wvgethosts must be entered exactly as shown. The variables

hosts, class, repositoryName, user and password must be replaced with a specific
value. The operands -c, -r, -u, and -p are not required for this command to
function.
17
Conventions
Operating System
This guide documents Unicenter Service Level Management for all available
platforms. The following labels indicate differences that depend on the
operating system:
Windows
Information is specific to Windows. The term Windows refers to the Microsoft

Windows operating system, including Windows NT 4.0, Windows 2000, and
Windows Professional. Unless specifically designated, Windows refers to any
Microsoft Windows operating system supported by Unicenter SLM.
UNIX
Information is specific to UNIX. The term UNIX refers to the Linux, Solaris, and
HP-UX operating systems.
The symbol indicates the end of the operating system-specific text.
Database
Microsoft SQL
Advantage Ingres
This guide documents Unicenter Service Level Management for all supported
databases. The following labels indicate differences that depend on the
database:
Information is specific to Microsoft SQL Server. The term SQL refers to the
Microsoft SQL Server database, including 7.0 with SP3 on Windows systems
and 2000 on Windows 2000 systems.
Information is specific to Advantage Ingres version 2.6.
The symbol indicates the end of the database-specific text.
Default Directories
18
This guide uses the following designations for default installation directories:
Directory Designation
Definition
SLM_Install_Path
Identifies the directory in which you

installed Unicenter SLM, such as
C:\slm or /opt/ca/slmo.
DB_Install_Path
Identifies the directory in which you

installed Advantage Ingres or
Microsoft SQL Server.
Chapter
Planning Your Installation

Before installing Unicenter SLM, you must consider what resources are required
for your data collection.
Disk Allocation
Over time, your report volume can grow unwieldy and stop data collections. To
prevent this situation and ensure the security of data collections, create at least
two disk partitions or volumes within the default paths for Unicenter SLM and
Advantage Ingres or Microsoft SQL as follows:
Partition
Size
Description
DB_Install_Path
2/3 of allocated Identifies the path to the Ingres or

size for SLM
Microsoft SQL DBMS installation. This
partition contains all configurations and
collected data.
SLM_Install_Path 1/3 of allocated Identifies the directory in which you

size of SLM
installed SLM, such as C:\slm or
/opt/ca/slmo. This partition contains
subdirectories for programs, libraries,
configuration files, and the Unicenter SLM
report repository.
Note: Collectors do not produce reports and do not require this disk
organization.
21
Disk Space
Disk Space
Important! Insufficient disk space can lead to serious errors in your Unicenter SLM
installation.
The following table shows the minimum disk space requirements for each
installation type:
Type of Installation
Disk Space Requirement
Minimum console
5 GB
Collector
300 MB
To ensure adequate disk space, assume that your installation may be expanded
at a later time. Additional considerations for disk space requirements include
the following:
Amount of data collected
Frequency of data collections
Storage time for collected data
Collected data reduction policy
Number of reports created
Frequency of report creation
Use of graphics in reports
Storage time for reports
Tip: The most important factors in estimating the required disk space are the
number of data collections and the polling frequency.
Data Collection
To estimate initial disk space requirements for your data collection, multiply the
number of samples collected each month by 200. This number indicates the
number of bytes the collection will occupy at the end of a month.
For example, your collector gathers data every ten minutes, creating 144 samples
every day or 4320 samples in a month. This data collection will occupy 843 KB
after the first month.
22
Maximum Shared Memory
Transaction Log
Advantage Ingres
By default, the transaction log size is set to 400 MB. You can change this default
during installation or at any time later using the Advantage Ingres
Configuration Manager (vcbf). For more information on this interface, see the
Advantage Ingres System Administration Guide.
Tip: To optimize performance, put the transaction log on a separate disk

drive from the Unicenter SLM database. For more information, see the
Advantage Ingres System Administration Guide.
Maximum Shared Memory

UNIX
Unicenter SLM requires the maximum shared memory segment size to be at

least 100 MB.
Note: The procedure to check and modify this property must be performed as
user root and is platform specific.
To check and modify this property on the Linux platform, follow these steps:
1.
To check the current value, enter the following command:

cat /proc/sys/kernel/shmmax
2.
To modify the value, use the following command:

echo new_value /proc/sys/kernel/shmmax
where new_value identifies the value for the maximum shared memory.
For example:
echo 100000000 > /proc/sys/kernel/shmmax
23
Host Name Resolution
Host Name Resolution

The Unicenter SLM host name must be resolvable by web browser clients even
when you specify the IP address in the URL. If the web client fails to look up the
IP address of the host name, the Java applets will not load correctly.
Unless the console host name is defined and available from the DNS name
service, you must add the correct IP address and host name for the console
system to the local hosts file. For more information on configuring this file, see
your operating system help system.
Host Name Validation

Unicenter SLM requires a fixed host name. Before installation, verify the
following:
The local host name is fixed.

You cannot use dynamic IP address allocation features for IP addresses and
host name assignments.
The local host name resolves to a valid IP address.

To verify this resolution, enter the command:
ping hostname
where hostname identifies the name of the local host.

This command must be able to look up the local IP address (not the loop
back address 172.172.172.1) successfully.
The hostname command returns the host name without the domain.
To verify this return, enter the following command:
hostname
Examples of valid returns include the following:

slm-server
serverA
Examples of invalid returns include the following:

slm-server.acme.com
serverA.abc.org
Advantage Ingres
24
The local host name must contain valid characters, as required by domain
name servers. Valid characters include alphanumeric characters and
hyphens (-).
Unicenter Components
Unicenter Components
Before installation, stop all agent technology components running on the
Unicenter SLM console. To verify if any agent technology components are
running, enter the following command:
awservices status
If any agent technology components are running, enter the following command
to stop the components:
awservices stop
Once the Unicenter SLM system is installed, enter the following command to
start the agent technology components:
awservices start
Installation Path
During installation you are prompted for the installation path for both Unicenter
SLM and Advantage Ingres. Use the following directories:
SLM: /opt/ca/slm
UNIX
Ingres: /opt/ca/ingresii
After installation, the path /usr/local/smm is created as a symbolic link to the

Unicenter SLM installation directory, unless you have chosen to install in this
directory. This path is required by the SLM installation and must not be
removed.
SLM: C:\SLM
Windows
Ingres: C:\IngresII
25
Chapter
Configuring the Environment

Before you begin using Unicenter SLM, you may need to perform some basic
configuration tasks to ensure an error-free operation.
Locating the Configuration Files

The following configuration files control the initial content of the database as
well as the way client programs can access the database:
smm.cfg
smmdb.cfg.template
These files are located in the following directory:

SLM_Install_Path/etc/
Each time you update these files, you must run the following command:
smmSetup
For more information on this command, see the appendix Command

Reference in this guide.
Tip: The smmdb.cfg.template file contains TCL (Tool Command Language)

array definitions.
31
Verifying Port Numbers

Unicenter SLM requires the following TCP port numbers be available on the
target system:
Port Number
Component Accessing Port
Console or Collector
6667
Collectors (smmCollect)
Console and collector
6668
Web server
Console only
6669
Report daemon (smmReportd)
Console only
6670
Data loader (smmdbd)
Console only
Note: If you must change port numbers, the installation script may fail when
starting the associated daemon process. To correct the problem, start the
daemon process manually after the port numbers are defined correctly.
Changing Port Numbers for Services

To modify the smmCollect, smmReportd, or smmdbd port number, follow these
steps:
1.
From the console system, select SLM Systems, SLM Console, Data Collect
Server, Configuration.
2.
Select and modify the desired port number.
3.
Save your changes.
4.
Open the smm.cfg file in a text editor and change the corresponding port
number.
5.
Close the file and save your changes.
6.
Enter the following command:

smmSetup
7.
Stop and restart the desired process. For example, to start and restart the
smmCollect process, enter the following commands:
smmCollect sd
smmCollect
32
To update the Windows Registry, follow these steps:

Windows
1.
From Start, Settings, Control Panel, open Services.
2.
Select and stop the desired service.
3.
From Start, Run, enter Regedit.
4.
Locate the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5.
From the desired process, open the ImagePath parameter and change the last
number to the new port number.
6.
Close the Registry and save your changes.
7.
Restart the service.
Changing Port Numbers for the Console

To modify the web server or console port number, follow these steps:
1.
Open the smm.cfg file in a text editor.
2.
Locate the console section and change the port parameter to the new port
number. This section appears as follows:
[console]
name = $hostname$
ip = 172.24.74.120
port = 6668
3.
Locate the reportd section and change the preurl parameter for all reports
created on the console. This section appears as follows:
[reportd]
port = 6669
preurl = http://$hostname$:6668
4.
5.

smmSetup
6.
Open the httpd.conf file in a text editor and change the port parameter to the
new port number. This file is located in the following directory:
SLM_Install_Path/mhttpd/conf/
7.
Enter the following commands to stop and start the management server:
/etc/rc.d/init.d/mhttpd stop
/etc/rc.d/init.d/mhttpd start
33
Installing the Java Runtime Environment (JRE)
8.
Update the value for the preUrl attribute in the smm_modules table in the
Unicenter SLM database (smmdb).
9.
Enter the following commands to stop and restart the SLM report server:
smmReportd sd
smmReportd
Changing Port Numbers for the Collector

To modify the collector port number, follow these steps:
1.
2.
Locate the collector section and change the port parameter to the new port
number. This section appears as follows:
[collector]
port = 6667
3.
4.

smmSetup

The Unicenter SLM console and all other machines that require administrator
access to Unicenter SLM require Java Runtime Environment (JRE) version 1.3.0
or later.
Tip: Machines that need to access Unicenter SLM but do not need
administrator privileges require only the Java Plug-in to read reports. The
Java Plug-in can be dynamically downloaded when prompted using Internet
Explorer. However, using Netscape, the Java Plug-in must be manually
downloaded and installed from Sun Microsystems. If you have installed the
JRE, you do not need to install the Java Plug-in separately.
The latest version of Java Runtime Environment and Java Plug-in can be
downloaded from the following locations:
http://java.sun.com/
Unicenter SLM CD-ROM in the Jre directory
Note: The Unicenter SLM CD-ROM contains the Linux and Windows version
1.3.1_01 of JRE. For all other operating systems, see http://java.sun.com.
34
To install the JRE on Windows, follow these steps:

Windows
1.
Open the Unicenter SLM Product Explorer from the CD_ROM.
2.
Select Java Runtime Environment 1.3.
3.
Click Install and follow the wizard instructions.
To install the JRE on Linux, follow these steps:

UNIX
1.
Login as smm.
2.
Copy the following file to SLM_Install_Path:

jre/j2re-1_3_1_01-linux.bin
3.

SLM_Install_Path/j2re-1_3_1_01-linux.bin
This script installs the JRE in the following directory:

SLM_Install_Path/jre1.3.1_01
4.
Open the .bash_profile file in a text editor and edit the PATH environment
variable for smm by adding the following directory:
SLM_Install_Path/jre1.3.1_01/bin
35
Configuring the Java Plug-in

UNIX
To use a web browser to view the Unicenter SLM console, you must install and
configure the Java Plug-in. To configure the Java Plug-in for Netscape, follow
these steps:
1.
Enter the following commands to uninstall the previous installation of the

Java Plug-in, if applicable:
rm -fr ~/.netscape/java
rm ~/.netscape/plugins/javaplugin.so
2.
Take the following action, depending on your browser:

Browser
Action
Netscape Set NPX_PLUGIN_PATH environment variable in the

4.0
.bash_profile file to the following:
SLM_Install_Path/jre1.3.1_01/plugin/i386/ns4
Netscape Change to the following directory:

6.0
Netscape_Install_Path/plugins
where Netscape_Install_Path is the installation directory for
Netscape.
Login as user root and make a symbolic link as follows:
SLM_Install_Path/jre1.3.1_01/plugin/i386/ns600/libjavaplugin_oji.
so libjavaplugin_oji.so
Note: If you are not logging in as user smm to launch the console, you need
to modify the .bash_profile file for the user you are using to launch the
console.
36
3.
Start or restart your Netscape browser.
4.
Close and restart your Netscape browser again. Restarting the browser a
second time prevents a Netscape error.
Configuring the javapath

UNIX
You must configure the smm.cfg file to contain the full path to the Java
program. To configure this file, follow these steps:
1.
2.
Set the javapath parameter as follows:

javapath = SLM_Install_Path/jre1.3.1_01/bin/.
Note: The last / is required.

3.
Close the file and save changes:
4.

smmSetup
Tip: If you have problems executing the java program on Linux RedHat 7.1,
enter the following commands as user root:
cp /bin/cut /usr/bin/
cp /usr/lib/libstdc++-libc6.2-2.so.3 /usr/lib/libstdc++-libc6.1-1.so.2
37
Synchronizing the JDBC Password
Synchronizing the JDBC Password

To connect to the Unicenter SLM database using JDBC, you must use a user and
password specified in the smm.cfg file. To specify or verify this password, locate
the following lines in smm.cfg:
# smmdb connect params
user = smm
password = smm
Assign the password as follows:

System and Database
Convention
UNIX
Use the same password as the system user smm.
Windows with Advantage

Ingres
Use the same password as the system user smm.
Windows with Microsoft SQL Use the same password as the database user
smm.
Important! If you change the system or database user smm, you must reflect this change
in the smm.cfg file. If you do not follow this convention, the Unicenter SLM user
interface will not load properly.
Adding the pcmtocsv.exe Path

Windows
The pcmtocsv.exe utility converts Unicenter Performance Management

performance cubes to comma-separated (CSV) format. To use this utility, you
must manually add the directory path to this program to the PATH
environment variable.
Normally, pcmtocsv.exe is installed in the following directory:
\CA_APPSW
Defining User Passwords

UNIX
You must define a password for the user accounts smm and ingres. To define
this password, enter the following command as user root:
passwd smm
You will be prompted for the password for smm twice. Repeat this procedure
for the ingres user.
38
Configuring CAM/CAFT Permissions
Configuring CAM/CAFT Permissions

UNIX
Unicenter SLM uses the CAM/CAFT service to transfer files to remote systems.
If the CAM/CAFT service is installed before Unicenter SLM, the smm user may
have insufficient permissions on transferred files. To verify and edit
permissions for the CAM/CAFT program, follow these steps:
1.
Navigate to the installation path for the CAFT program.
2.
Enter the following command to check the owner and permission of the
CAFT program:
ls -l $CAFTPATH/bin/caft
For installations with correct permissions, the following line appears:

-rwsr-xr-x 1 smm bin $CAFTPATH/bin/caft
3.
If your installation does not have correct permissions, log in as user root and
set the following environment variable:
CAFTPATH=`cat /etc/catngcampath`
export CAFTPATH
4.
Enter the following command to stop the CAFT program:

$CAMPATH/bin/caftabrt
5.
Enter the following commands to change the owner and permissions on the
CAFT program:
chown smm $CAMPATH/bin/caft
chmod 4755 $CAMPATH/bin/caft
6.
Enter the following commands to change the owner and permissions on the
CAFT log directory:
chmod 777 $CAMPATH/ftlogs
rm -f $CAMPATH/ftlogs/*
7.
Enter the following command to ensure that all files and directories below
the directory SLM_Install_Path/smm/incoming/CA_perfAgent are writable
by the smm user:
chown R smm:users SLM_Install_Path/smm/incoming
39
Upgrading Unicenter SLM

Note: Upgrading from SLMO 1.0 to Unicenter SLM 3.0 is not supported. You
must first upgrade from SLMO 1.0 to SLM 2.0.
The procedure to upgrade SLM 2.0 to 3.0 differs depending on the platform in
use (UNIX and Windows), the database in use (Ingres or MS SQL) and the type
of Unicenter SLM installation (console or collector).
Important! We recommend creating a backup of your installation before upgrading your
system.
Removing the Database

Upgrading from SLM 2.0 to Unicenter SLM 3.0 requires a complete SLM 2.0
installation. You cannot upgrade the SLM 2.0 database only. If you have only the
database, you must manually remove the database and then install Unicenter
SLM 3.0. To remove existing databases, follow these steps:
Advantage Ingres

destroydb smmd
Microsoft SQL
310
Using the SQL Enterprise Manager, delete the smmdb database.
Upgrading SLM Console

Before upgrading your Unicenter SLM console, back up your current installation.
If you have customized your installation, make copies of the following files:
SLM_Install_Path/etc/modules
SLM_Install_Path/gifs/logo.gif
SLM_Install_Path/mhttpd/conf/*
To upgrade your Unicenter SLM console on UNIX, follow these steps:

UNIX
1.
Enter the following commands to back up your crontab definitions:

crontab -l | tee /tmp/SLMO-1.0/cron
2.
Log in as smm and enter the following command:

crontab /dev/null
3.
Enter the following commands to stop services:

smmCollect sd
smmReportd sd
4.
Enter the following command to ensure that these processes are not running:
ps auxw
If these processes are still running, stop the processes with the following
command:
kill 9
5.
Log in as root and enter the following command to stop the Unicenter SLM
web server:
directory/mhttpd stop
where directory is /etc/rc.d/init.d on Linux.

6.
Enter the following command to ensure that processes containing mhttpd

are not running.
ps auxw
If these processes are still running, stop the processes with the following
command:
kill 9
7.
Ensure the Advantage Ingres database is running.
8.
Run the install script as in a regular installation. For more information on

installing Unicenter SLM 3.0, see the Getting Started guide.
Answer yes to the questions, "OK to upgrade SLM?" and "OK to use existing
SLM database?"
9.
Restore your customized files to the appropriate directories.
311
Windows and
Microsoft SQL
To upgrade your Unicenter SLM console on Windows with Microsoft SQL,

follow these steps:
1.
Log in as administrator.
2.
Stop the following services:

SLM Cron Scheduler
SLM smmCollect
SLM smmReportd
Apache
3.
Make sure that the Microsoft SQL server is running.
4.
Enter the following commands:

cd CD_ROM_Drive\windows\
tclsh SLM3.0PreUpgrade.tcl
Note: This command copies the report repository to a backup directory. The
backup directory must be located on a disk volume with sufficient free disk
space to hold all files in the SLM_Install_Path/reports directory.
5.
Navigate to the Windows Add/Remove Programs dialog.
6.
Select SLM and click Add/Remove.
WARNING! Answer No when asked about deleting the database.

7.
Install Unicenter SLM 3.0. For more information on installing Unicenter SLM
3.0, see the Getting Started guide.
8.
Reboot the system when completed.
9.
10. Enter the following commands:

tclsh SLM3.0PostUpgrade.tcl
This command restores the SLM 2.0 report repository in the Unicenter SLM
3.0 report repository.
312
Windows and
Advantage Ingres
To upgrade your Unicenter SLM console on Windows with Advantage Ingres,

follow these steps:
1.
2.

SLM Cron Scheduler
SLM smmCollect
SLM smmReportd
Apache
3.
Make sure that Advantage Ingres is running.
4.
Log in as ingres.
5.

tclsh SLM3.0PreUpgrade.tcl
Note: This command copies the report repository to a backup directory. The
backup directory must be located on a disk volume with sufficient free disk
space to hold all files in the SLM_Install_Path/reports directory.
6.
7.
8.
Reboot the system when completed.
9.
Log in as ingres.
10. Stop Ingres using the Services utility. Using the ingstop command is not
sufficient.
11. Install Unicenter SLM 3.0. For more information on installing Unicenter SLM
Note: Answer "Yes to all" when asked to overwrite existing files during the
Advantage Ingres installation.
12. Reboot the system when completed.
13. Log in as ingres.
14. Stop the following services:
SLM Cron Scheduler
SLM smmCollect
SLM smmReportd
SLM smmdbd
Apache

destroydb smmdb
createdb smmdb
313
16. Change to the backup Ingres directory and issue the following commands:
sql smmdb -usmm <copy.in.smm
smmBuild -all
sysmod smmdb

tclsh SLM3.0PostUpgrade.tcl
This command restores the SLM 2.0 report repository in the Unicenter SLM
3.0 report repository.
Upgrading Collectors
To upgrade your UNIX collectors, follow these steps:
UNIX
1.
Log in as smm.
2.
Disable crontab definitions by entering the following command:

crontab /dev/null
Note: If you have customized definitions, make a copy of the crontab.

3.

smmCollect sd
4.
Enter the following command to ensure that this process is not running.
ps
If the process is still running, stop the process with the following command:
kill 9
5.
Answer yes to the question "OK to upgrade SLM?"
To upgrade your Windows collectors, follow these steps:

Windows
314
1.
2.
3.
Upgrading Custom Metrics

Unicenter SLM 3.0 introduces a new metric attribute, parent, to organize metrics
into folders in the SLM status tree. Custom metrics created with SLM 2.0 must be
updated to use the parent attribute. Any metrics without a parent attribute are
placed into a folder in the metric tree called Unplaced metrics.
To update custom metrics to include the parent attribute, follow these steps:
1.
In a text editor, open the file containing the metric definition.
2.
Add the following line to the metric:

parent
MyFolder
where MyFolder identifies an existing metric folder.

The following example adds the if-octetsPS metric to the Network_interface
folder:
if-octetsPs {
parent
Network_interface
class
link
agent
snmpCollect
label
Link
description
{Number of octets per second on an interface}
class_scope
link
metric_scope
if-octets
metric_reports {
real
{{Interface octets per second} octets/sec interfaceoctets-per-second}
sum
{{Interface octets sum} }
}
metric_fields {
agenthost
{{Agent host} {hidden} {} {default_common} {\$agent}}
startnode
{{Target host} {entry} {} {required} {}}
endnode
{{Neighbour host} {hidden} {} {optional} {none}}
description
{{Label} {entry} {} {optional} {}}
interval
{{Interval (min)} {select} {1 5 10 15 20 30 60}
{default_common} {10}}
community
{{SNMP community} {entry} {} {default_common} {default}}
mib
{{MIB expression} {hidden} {} {default}
{ifPs,ifInOctets,ifOutOctets}}
mibType
{{MIB type} {hidden} {} {default} {EXPRESSION}}
mibFile
{{MIB file} {hidden} {} {default} {IF-MIB-V1SMI.my}}
instance
{{MIB instance} {entry} {} {required} {}}
instancekey
{{MIB instance key} {hidden} {} {default}
{ifDescr,ifAlias}}
linktype
{{Link type} {select} {simplex duplex} {default}
{duplex}}
statusChanged
{{Status changed} {hidden} {} {default} {0}}
adminStatus
{{Suspended} {check} {0 1} {default} {0}}
status
{{Status} {hidden} {} {default} {0000ff}}
selectionName
{{Selection name} {hidden} {} {required} {Undefined}}
dataDir
{{Data directory} {hidden} {} {default}
{\$SMM/databases/collect}}
dataDb
{{Data database} {hidden} {} {default_common}
{default}}
deviceType
{{Device type} {hidden} {} {default} {router}}
vendorName
{{Vendor name} {hidden} {} {default} {any}}
}
}
315
Removing Unicenter SLM
Removing Unicenter SLM

To remove Unicenter SLM on UNIX, follow these steps:
UNIX
1.
Log in as user root.
2.
Check for logged in users by entering the following command:

w
Ensure that no ingres or smm users are logged in.

3.

~smm/bin/uninstall
To remove Unicenter SLM on Windows, follow these steps:

Windows
316
1.
2.
Select SLM and click Add/Remove. This process removes Unicenter SLM,
but not Advantage Ingres, Microsoft SQL, CAM or the Java Runtime
Environment.
Chapter
Using Collectors
The Unicenter SLM collectors (also called agents) collect and measure data from
a wide variety of sources in your installation. This data is regularly uploaded to
the console system for reporting.
In Unicenter SLM, data collections can be defined using one of the following
methods:
Method
Description
Define single data collections
Using the console interface and the address of

the object on which you want to collect data.
This method can be time consuming and is not
recommended if many data collections need to
be defined.
Import data from Unicenter

NSM
Using the console interface and objects existing

in the Unicenter Common Object Repository.
Import Unicenter Performance

Management performance
cubes
Using the console interface and Unicenter

Performance Management performance cubes.
This method provides automatic creation of
data collections and metrics.
Import Unicenter Advanced

Network Option data
Using the console interface and Unicenter

Advanced Network Option data. This method
provides automatic creation of data collections
and metrics.
Import Unicenter Management Using the console interface and Unicenter

for Web Servers response data Management for Web Servers response data.
This method provides automatic creation of
data collections and metrics.
Import external data
Using the Unicenter SLM External Data Import

Wizard to create new import methods to
import data from ASCII files. This method lets
you use existing data for reporting and
monitoring.
Using Collectors
41
Starting the Collector
Starting the Collector

After the installation procedure, you must enter the following command to
manually start the Unicenter SLM data collector daemon:
smmCollect
Alternately, you can restart the collector system.

The smmCollect process automatically defines the collector system in the
database. If this process fails, you can define the new collector system manually
at the console. To define the collector system manually, follow these steps:
1.
From the Unicenter SLM console, right-click SLM Systems in the status tree.
2.
Select Add System from the pop-up menu.
3.
Enter Agent Name (host name) and Agent Description of the new system.
4.
Click Save.
5.
Reload the SLM status tree. The new system appears in the status list.
Understanding Collector Processes

The installed collector goes through the following steps when started:
A connection to the database is created to download the specifications on all

data collections.
Downloaded data collection specifications are written to the following cache
file:
SLM_Install_Path/etc/collections
This file is used as a backup configuration if the database is unavailable at a

later start or restart.
For each data collection specification, a data collection instance is created in

the collector program responsible for that collection.
After each data collection is activated, the smmCollect process enters an
event loop, where the data collections are controlled by timer and response
events.
A timer event signals that a specific data collection should be performed. A
response event signals that a response to an issued data collection has
arrived. The event loop also listens for control events - commands from the
console system, such as a request for a restart.
42
Defining Single Data Collections
The collector stores data for each data collection in a separate file. Using this
method, the collector system does not depend on the console system until a
restart or stop command is received. If the collector is running on the console
system, data is stored directly into the database.
At regular intervals, collected data is uploaded to the console system using
CAM/CAFT (CA messaging and transfer service).
The smmCheck program runs every 15 minutes from the cron utility to check
the status of each data collection and important system resources and report
the findings to the database. This program keeps the smmCollect process
running. If the smmCollect process has exited or stopped, this program is
started.
Defining Single Data Collections

To configure a single data collection, follow these steps:
1.
From the left-hand console panel, expand the Status Tree structure under the
agent system for which you wish to perform the data collection.
2.
Expand the Metrics branch and choose the data collection type you wish to
use.
3.
Click New Data Collection in the right-hand frame.

A configuration form appears, with a set of parameters to be specified. The
content of the configuration form is metric-specific, but some parameters are
always present, such as interval, label, and others. For a description of the
metric, click Help.
4.
Complete the form and click Save Data Collection. The new data collection
will be defined and inserted into the database. A list of defined report groups
appears.
Note: If any parameters are unspecified, the save operation fails. For SNMP
parameters, Unicenter SLM helps find an SNMP instance value for tabular
SNMP variables. If this value is not specified and the metric for this data
collection has an instancekey defined, Unicenter SLM presents the list of
SNMP MIB values.
5.
To add the new data collection instance to a report group, select the desired
groups and click Add Data Collection to Groups. Alternately, click Clear to
save your data collection without adding it to a group.
Note: This process only saves the definition of the new data collection in the
database. The collector performing the data collection must be reloaded
before data collection begins.
Using Collectors
43
Importing Objects from Unicenter Common Object Repository
Restarting the Collector

Restarting the data collector (smmCollect) interferes with any current data
collections. We recommend defining all data collection definitions at once and
then perform a restart that reloads all definitions.
To restart the data collector at a particular agent, follow these steps:
1.
From the left-hand console panel, expand the SLM Systems structure and
click the Unicenter SLM system host name.
2.
Click Restart.
Note: Depending on the number of data collections the data collector must load
and the quality of the network connection between the system running the data
collector and the database, a restart may take some time.
Modifying Data Collections

To modify a data collection, follow these steps:
1.
From the left-hand console panel, expand the Status Tree structure under the
agent system for which you wish to perform the data collection.
2.
Click on Metrics and select the metric type you wish to modify.
3.
Select the desired data collection in the right-hand frame. A configuration

form appears.
4.
From this dialog, edit fields for this data collection and click Save. You can
also perform the following actions from this dialog:
Click Test to test this data collection.
Click Delete to delete this data collection.
Click Report to create a report for this data collection.
Importing Objects from Unicenter Common Object

Repository
Importing objects from Unicenter Common Object Repository requires that the
Unicenter SLM CORE Gateway be installed on the Common Object Repository
server. This component uses libraries from the Software Development Kit in
Unicenter to extract data from the Common Object Repository. The Common
Object Repository database can use Advantage Ingres, MS SQL, or any other
database Unicenter supports, as long as SDK library functions can be used to
extract data.
44
Installing the Unicenter SLM CORE Gateway

The Unicenter SLM CORE Gateway server is included with Unicenter SLM in the
following directory:
CD_ROM\coregw
To install the gateway, locate the following file:

TNGWVserver-os-x.x
where:
os Identifies the operating system.
x.x Identifies the version number.
To install TNGWVserver on UNIX, follow these steps:
UNIX
1.
Copy the TNGWVserver-os-x.x.tar file to the directory in which you want

to install the application.
2.
Enter the following command to un-tar the TNGWVserver-os-x.x.tar file:

tar xvf TNGWVserver-os-x.x.tar
This action creates a TNGWVserver directory.

3.
Enter the following command with a port number as a parameter, as follows:

TNGWVserver 7000
Choose a port number larger than 1024 that is not used by any other
applications. After entering this command, TNGWserver runs in the
background until stopped.
To stop TNGWserver, follow these steps:
1.

ps auxw | grep TNGWVserver
The PID of the TNGWVserver is listed.

2.

kill 9 TNGWVserver_PID
Tip: To remove TNGWVserver from your system, stop TNGWserver and

delete the TNGWVserver directory.
Using Collectors
45
To install TNGWVserver on Windows, follow these steps:

Windows
1.
Run TNGWVserver-win-x.x.exe. The installation wizard for TNGWVserver

appears.
2.
Follow the wizard steps to install TNGWVserver. During installation, you

are prompted for the installation path and TCP port number of
TNGWVserver. Select a port not in use by another application.
TNGWVserver is installed as a Windows service, SLM TNGWVserver, and

started automatically after installation. This service can be started and stopped
like all other services through the Services menu in the Control Panel on
Windows.
Tip: Pausing the TNGWVserver service is not supported.
If you need to change the port number the TNGWVserver is using, you must
remove and then reinstall TNGWVserver. TNGWVserver can be removed by rerunning TNGWVserver-os-x.x.exe or choosing Add/Remove Programs from the
Control Panel.
Importing Unicenter Objects

Note: The following characters are not supported by Unicenter SLM used in the
Unicenter Common Object Repository username or password:
$ [ ] \ " '
To import objects from a Unicenter Common Object Repository, follow these

steps:
1.
From the SLM Status Tree drop-down list, select Unicenter Repositories.
Note: You must have the Show Tree View option selected.
46
2.
Right-click on Unicenter Repositories and select Add Repository.
3.
In the Add Repository dialog, enter the host name or IP address of the
system containing the Common Object Repository, the port number for the
Unicenter SLM CORE Gateway, and the name of the Unicenter Common
Object Repository.
4.
Click OK. After a while, a new entry in the Unicenter Repositories tree
structure appears.
5.
Expand the new Unicenter CORE instance to list the CORE class groups and
classes provided by this CORE. Each class in the tree contains a list of metrics
this class supports. The types of metrics are based on device and vendor
type.
Some metrics are supported for all device and vendor types and others are
specific to a particular vendor. For example, the class SysAgtNT (under class
group Agent) supports all metrics specific to an NT system agent (for
example, cai_cpuUtil, cai_fileSysUsed, and memoryUtil) and also all metrics
for all devices and vendors (such as ipnet).
6.
Click the metric under the class you wish to import. On the right-hand side,
all objects in this class that exist in the Common Object Repository appear, as
well as certain options you can apply to the imported objects. These options
vary depending on the type of metric chosen. A report group called
Unicenter CORe is created, if it does not already exist. Unless you change
this report group, all objects are stored to this group.
7.
Modify any desired options. Common modifications include the following:
By default, the console collects data from the objects imported. You can
choose another collector by selecting its name from the Agent host select
list.
Test connections can be cleared if you do not want to test the connection
to the objects before importing them. This action can be used if you do
not have access to the objects currently because objects that cannot be
accessed will not be imported. The test is based on the metric type you
have selected.
Restart collector can be deselected if you do not want to restart the
collector after importing objects. If you clear this option, the collector
will have to be restarted manually.
8.
Check each object you wish to import. Alternately, use the action list and
select Check all to select all objects.
9.
Depending on the metric type, the action list contains Explore Instances or
Save selection.
If your list has Save selection, click Save selection.

If your list has Explore Instances, click Explore Instances. Click the
instances you want to start collecting data on and choose Save in the
action list.
Tip: Each time a metric is selected in the Unicenter Repositories tree

structure, Unicenter SLM retrieves the objects that apply to the selected
metric. Therefore, you do not have to reload the Unicenter Repositories tree
every time a new object is added to the Common Object Repository.
Using Collectors
47
Reloading the Common Object Repository

You must reload the Common Object Repository instance in the Unicenter
Repositories tree if you have added, modified or removed any managed object
classes in the Unicenter Common Object Repository.
To reload a Unicenter Common Object Repository instance, follow these steps:
1.
Right-click the Unicenter Common Object Repository instance label.
2.
Select Delete from the drop-down menu.
3.
Reload the Common Object Repository.
Understanding Severity and Propagated Severity Collection

The Unicenter Severity and Propagated Severity metrics collect the severity
property of selected Common Object Repository objects. The collector
(smmCollect) calls a collector (coreimport) every time Unicenter severity data is
collected. Coreimport issues only one call to TNGWVserver for every interval.
For example, if you have 10 objects collecting Unicenter severity data every
minute, coreimport gets data for all objects once every minute - not 10 times
during a minute.
Important! Do not set the collect interval to every minute unless you must. If you
experience slow response times from the Common Object Repository or Unicenter SLM,
you may have set too many Unicenter Propagated Severity collections.
48
Propagated Severity Threshold

The Propagated Severity Threshold, defined when you define a Unicenter
Propagated Severity object, specifies the threshold value for availability and
downtime incidents which will trigger events. If you set this value to MAJOR,
propagated severity values of CRITICAL, DOWN, INSERVICE, REMOVE, and
FUTURE are calculated as unavailability/downtime incidents. These values are
based on the following list:
Severity
Value
NORMAL
UNKNOWN
WARNING
MINOR
MAJOR
CRITICAL
DOWN
INSERVICE
REMOVE
FUTURE
Property Value Collection

The coreimport agent can collect on any property of an object in the Common
Object Repository with the following restrictions:
The property must have the same threshold name/value pairs as defined in
the propagated severity threshold.
The property must be accessible to the Unicenter SDK.
Only availability, downtime, and delay reports can be generated on the
collected data.
Note: You must define a new metric if you wish to collect on other properties.
Using Collectors
49
Importing Performance Cubes

The Unicenter Performance Management uses agents to collect performance data
from a variety of systems and database resources. These agents can send the
collected data in packets called cubes to the Unicenter SLM Console for
reporting. When this data is received, an import agent starts an application
(pcmtocsv) that converts the cubes into CSV files. The import agent reads and
converts the CSV files to a format that Unicenter SLM can understand. Unicenter
SLM can then generate service level reports based on the data from Unicenter
Performance Management.
Configuring Unicenter SLM for Performance Cubes

To prepare your Unicenter SLM installation to receive performance cubes, follow
these steps:
1.
From Status Tree, SLM Console, Metrics, select External Data Import.
2.
Click CA Performance Cube data import. From this dialog, you can modify
the following values:
Option
Definition
Scan interval Specifies how often the collect daemon checks for the arrival
of new files below the CA_perfAgent directory.
Backup
Specifies the full path to a directory where imported

performance cubes are stored.
Separator
Specifies which separator to use when importing performance

cubes. Unicenter SLM needs to convert the cube to a CSV file.
Depending on your system settings, the conversion may use
the semicolon as a separator in CSV files.
Import filter
Specifies one or more metric names and corresponding metric

data to be included during import.
A performance cube organizes data into resource types and
resource subtypes. When imported into Unicenter SLM, these
identifiers are concatenated to create a unique metric name.
For example a resource type of System and resource subtype
of Processor Queue Length creates a metric name of
System_Processor_Queue_Length.
A metric name may be fully specified or partial. The value .*
imports everything in the cube. The value Processor_ System_
imports any data assigned a metric name containing
Processor_ or System_.
3.
410
Make the desired modifications and click Save.
4.
On the left-hand side of the console, click the SLM Console label.
5.
Click Restart.
Note: After restart the collect daemon will search for the arrival of new files
below the CA_perfAgent directory. Any file that does not conform to the
Performance Cube layout will be rejected.
Configuring Unicenter Performance Management for Data Collection

To prepare your Unicenter Performance Management installation to export
performance cubes, follow these steps:
Note: Because the New Recipient Machine list is extracted from the current
Unicenter Common Object Repository, the Unicenter SLM console must be
discovered prior to this procedure.
1.
Select Programs, Unicenter, Performance Management, Performance

Configuration from the Start menu.
2.
Select Profile, Data Management, Daily Cubes, Full Daily Cube, Delivery
Machines. The right-hand frame lists all defined recipients for the profile.
3.
From the Cube menu, select the SLM Console as the Performance
Management recipient.
4.
Click Add Recipient Machine.
5.
From the pop-up menu, select the recipient machine that corresponds to the
console.
6.
Enter the following command to check if the CAM session is running

between the console and any host with the Performance Agent installed:
camping {hostname | IP_address}
7.
Use the camstat utility on the console to display the number of messages sent
and received from any Performance Agent host delivering cubes to the
console.
8.
Verify that the application queue CAIFTRANS is in the CON (connected)

state.
Note: The CAM/CAFT protocol runs, by default, on UDP port 4104. You may
require this information when specific protocol filtering is implemented through
a firewall solution.
Using Collectors
411
Importing Unicenter Advanced Network Option Data
Importing Unicenter Advanced Network Option Data

SuperPing, part of the Unicenter Advanced Network Option, determines
availability, round-trip response, and trace route information for selected
networked systems.
To use this data with Unicenter SLM, the collected files must be transferred from
the manager to the Unicenter SLM console system for input to the import facility.
Tip: Currently a separate service must be set up to move these files

automatically, such as CAM/CAFT or FTP.
Configuring Unicenter SLM for Network Data

Prior to importing Unicenter Advanced Network Option data files, follow these
steps:
1.
Create the following directory:

SLM_Install_Path/incoming/CA_ping
2.
Create subdirectories for each SuperPing manager system. These

subdirectories must have the same name as the manager system. For
example, SLM_Install_Path/incoming/CA_ping/ntsrv01 is the full path to
the directory for Ping/SuperPing files from the manager ntsrv01.
Note: The subdirectories let you identify the manager for the data
collections. In addition, the subdirectories ensure unique names for
uploaded data, eliminating the risk of one manager overwriting a file from
another.
3.
4.
Select CA SuperPing. From this dialog, you can modify the following values:
Option
Definition
of new files below the CA_ping directory.
Backup
412
Specifies the full path to a directory where imported

SuperPing files are stored.
5.
6.
On the left-hand side of the console, click SLM Console label.
7.
Click Restart.
Importing Unicenter Management for Web Servers Response Data
Processing Network Data

Unicenter SLM stores on the console system with the following filename:
TAG_DDMMYYYY.log
where
TAG
Specifies PING or SUPERPING.
DDMMYYYY
Identifies the day, month, and year respectively.
Unicenter SLM extracts the following columns from ping and SuperPing data
files:
Column
Ping or SuperPing
Use
Current time
Both
Calculates the sample time for each

record in the file.
Target name
Ping
Labels each data collection.
Path
SuperPing
Labels each data collection with the

SuperPing manager name from the
import directory.
Status
Both
Identifies if the ping timed out. If Status

is critical, an unavailability event is
entered into the database. Otherwise, a
response time value is logged.
Response time
Both
Identifies how long, in seconds, before

the target system responds.
Importing Unicenter Management for Web Servers Response

Data
Web Response Monitor (WRM), part of the Unicenter Management for Web
Servers, tracks and logs availability, response time, and throughput for
monitored web addresses (URLs). This collected data can be imported into
Unicenter SLM and used in service level reports.
Unicenter SLM can import regular and scripted WRM log files. Scripted WRM
log files contain one or more web transactions executed as a set and a summary
entry. Unicenter SLM creates a separate metric instance for the summary entry
where the response time is the sum of the response times in the set and the
throughput is calculated based on the total transferred bytes and the response
time.
Using Collectors
413
Configuring Unicenter SLM for WRM Data

Prior to importing WRM response data files, follow these steps:
1.
Open the modules configuration file in a text editor. This file is located in
the following directory:
SLM_Install_Path/etc/
2.
Ensure that this file contains the following definition:

source SLM_Install_Path/WMO.cfg
3.
If you update the modules file, enter the following command:

smmBuild all
When this command has completed, reload the SLM status tree.
4.
5.
Select WMO WEB response monitor. From this dialog, you can modify the
following fields:
Option
Definition
of new files below the CA_wmo directory.
Backup
Specifies the full path to a directory where imported WRM

data files are stored.
6.
7.
On the left-hand side of the console, click SLM Console label.
8.
Click Restart.
Tip: The WRM data files must be transferred from the WRM manager to the
console system for input to the import facility. This process could be
automated using CAM/CAFT, FTP, or using a file sharing mechanism like
Samba or NFS.
414
Processing WRM Data

Unicenter SLM stores on the console system with the following file name:
hostname/MMDDYYYY[anything]
where:
hostname
Specifies hostname of the WRM probe system.
MMDDYYYY
Identifies the month, day, and year respectively.
Note: To successfully import data, Unicenter SLM needs a valid timestamp
containing date and time for each data collection and information about
where the data was sampled.
Two metric types are associated with WRM data for response time and
throughput respectively:
CA_wmo_HTTPResponse
CA_wmo_HTTPThroughput
The response time metric also maintains availability status. These metrics are
automatically created the first time data is imported.
Tip: WRM data can only be imported at the Unicenter SLM console system.
All WRM metric instances (data collections) are visible in the Metric tree
under the Console.
Testing the WRM Import

To test your new import, follow these steps:
1.
Enable debugging of the import function by un-commenting the following

entry in the smm.cfg file:
IMPORT_LOG = $SMM/var/log/import_remote_data.log
2.

smmSetup
smmCollect sd
smmCollect
3.
Copy a sample WRM log file into the import wizard into the defined import
directory:
SLM_Install_Path/CA_wmo
Using Collectors
415
Importing External Data
Within one minute, the collector job will collect the file, removing it from the
import directory. If a backup directory is specified, a copy of the file appears in
that directory.
Since logging is enabled, the import function logs activity as it processes the
import file. The following example shows a typical output:
01/17/02 11:38:24 d:/slmo/incoming/CA_wmo/stale/01102002.log ready for import
01/17/02 11:38:24: WMO_response_import: Scanning
d:/slmo/incoming/CA_wmo/stale/01102002.log ...
01/17/02 11:38:24: WMO_response_import: Read 112 records
01/17/02 11:38:25: Importing d:/slmo/databases/tmp/01102002.log ...
01/17/02 11:38:26: Created new metric CA_wmo_HTTPResponse
01/17/02 11:38:26: Created new data collect instance (228) for
CA_wmo_HTTPResponse
01/17/02 11:38:27: Created new metric CA_wmo_HTTPThroughput
CA_wmo_HTTPResponse
01/17/02 11:38:28: Created new data collect instance (231)
forCA_wmo_HTTPThroughput
....
CA_wmo_HTTPResponse
01/17/02 11:38:32: 01/17/02 11:38:32:
Loading file
d:/slmo/databases/tmp/696736313/smmdb into smmdb...
01/17/02 11:38:34: 01/17/02 11:38:34
Loaded
d:/slmo/databases/tmp/696736313/smmdb successfully into smmdb
01/17/02 11:38:34: WMO_response_import completed
When the file is imported, the newly created metric types will be available under
the Import metric you created for this import. Clicking any of the metric types
lists the metric instances created for that type.

The Unicenter SLM External Data Import Wizard lets you teach the system how
to load and interpret external data files. Any files complying with the
requirements that contain timestamped collected or measured data suitable for
reporting in Unicenter SLM can be imported. Possible imports include
application log files, system log files or log files from other measurement and
data collecting tools and utilities.
Through the wizard you create an import metric template based on the layout in
a sample ASCII data file. This template is activated to monitor a specific input
directory for the arrival of ASCII files with the same layout as the one run
through the wizard. When new files arrive, the content is automatically imported
into the database.
416
Import File Requirements

Files to be imported must conform to the following requirements to be used with
the wizard:
Formatted as plain ASCII data.
Can be modeled as records (rows) and columns where:
New line character indicates the end of a record.
Common character separates all columns.
All records have the same column layout.
Each record contains at least two columns: a value and a timestamp.

The SLM Import mechanism can parse and convert any standard date or
time string, including standard time zone mnemonics. If the string does not
contain a time zone mnemonic, the local time zone is assumed.
Each record in a column has a common data classification. The wizard lets
you assign a set of report properties that are applicable to all records in a
column. For example, a value column containing sampled data for User,
System and Total CPU utilization is valid since they relate to a common
report type (CPU utilization). However, a value column containing data for
CPU utilization and File system space used is not valid since these are not
related to a common report type.
All records associated with a particular data set are sorted by the sample
time.
Records or global information specify the following information:
-
Information that uniquely identifies the type of sampled data. The

wizard uses this information to define a metric type that describes this
data.
Information that uniquely identifies each instance out of many in a data

set. The wizard uses this information to create a metric instance.
Note: Global information is information derived from the file name of the
imported file. For example, the date part of a timestamp and the source of
the sampled data might be derived from the import file name
20011001.hostname.
Using Collectors
417
Valid Import Examples

Example 1
The following file meets the minimum requirements for data import. The first
column specifies a timestamp and the second column specifies a sampled value:
09:00, 345.00
09:10, 323.00
09:20, 378.00
The import file name must specify additional information. In this example, the
date part for the sample time and a target or instance to identify this data set
must be specified. The file name layout could be as follows:
YYYYMMDD.hostname
where:
YYYYMMDD
Specifies year, month and day respectively.
hostname
Specifies the target system.
Example 2
The following file uses the comma as a column separator, contains a timestamp
column and two value columns (memory and swap utilization), along with
other information that helps to identify the type of data and their instances.
a.domain.com,UNIX SAR,MEMORY,09/07/2001 02:10:00 AM,94.41,4.19
Example 3
The following file uses a semicolon as a column separator. The fourth and last
column contain the sample time (as UNIX epoch time) and a system up time
value (in hundredths of a second) since last boot, along with other information
that helps to identify the type of data and their instances.
a.domain.com; mib-2; sysUpTime; 988801200; 593876288.00
b.domain.com; mib-2; sysUpTime; 988802100; 593966272.00
c.domain.com; mib-2; sysUpTime; 988803000; 594056256.00
Example 4
The following file uses the comma as a column separator, contains a timestamp
column and six value columns, along with other information that helps to
identify the type of data and their instances.
1000305570,a.domain.com,NAMED,NSTATS, 20851, 22, 1275, 101, 4, 68
418
Preparing Your Data

Before using the wizard, you must analyze and prepare your data. To ensure an
error-free import, follow these steps:
1.
Determine the file naming convention and file name separator character for
the ASCII data files to be imported.
2.
Identify and verify the column content of data for compliance with the
requirements.
3.
Copy a sample data file into the following directory on the console system:
SLM_Install_Path/incoming/import
Creating an Import Metric Template

To create an import metric template with the wizard, follow these steps:
1.
From the status tree, SLM Systems, SLM Console system, Metrics, right-click
External Data Import.
Note: Only collector systems support external data import.
2.
Follow the instructions provided by the wizard.
Tip: To modify an import metric template, follow the same steps as when
creating a new import metric template except you must specify the name of
the import metric template you want to modify in the wizard instead of a
new name. Answer yes when prompted if the existing definition is to be
replaced.
Using Collectors
419
Activating an Import Metric Template

After you have created a new import metric template, you must activate it to
start importing data. To activate this template, follow these steps:
1.
From the status tree, SLM Systems, SLM Console system, Metrics, External
Data Import, select the template you wish to activate. You may need to
reload the status tree to make it visible. The Import metric template
activation form appears. This form lets you perform the following actions:
Modify the default import directory. This directory indicates where files
must be stored to be imported into Unicenter SLM.
Modify the import filter. The import filter limits the type of data to
import. The type of data is identified by metric name. For example, if
you specified DNS as the import filter for your data, only DNS records
are imported. The import filter can be specified as a regular expression.
The wildcard value .* imports everything.
Modify the default source backup directory. This definition copies the
original import files into the assigned directory. The value undefined
deletes the import file after it is read.
2.
Click Save. The Activated import metric template appears.
3.
On the left-hand side of the console, expand the status tree and click the SLM
Console label.
4.
Click Restart.
When the collector reads the definition for the new import metric from the
database, the collector creates a separate job for this task. This job creates the
Import directory, if it is not already created, and monitors that directory for
incoming files. When a file arrives its content is parsed as defined by the wizard.
Tip: The data import facility requires that files be stored into their respective
import directories accessible locally by the console system. This process
could be automated by scripts or by defining the import directory as a share
available from remote systems that generate data.
420
Testing an Import Metric Template

To test your new template, follow these steps:
1.
Enable debugging of the import function by un-commenting the following

entry in the smm.cfg file:
IMPORT_LOG = $SMM/var/log/import_remote_data.log
2.

smmSetup
smmCollect sd
smmCollect
3.
Copy the file you loaded into the wizard into the defined import directory,
located in the following directory:
SLM_Install_Path/incoming/import
Within one minute, the collector job will collect the file, removing it from the
import directory. If a backup directory is specified, a copy of the file appears in
that directory.
Since logging is enabled, the import function logs activity as it processes the
import file. The following example shows a typical output:
12/20/01 13:51:02 /usr/local/smm/incoming/_ImportMetric_test/20010411.log ready
for import
12/20/01 13:51:02:
slmImport: Scanning
/usr/local/smm/incoming/_ImportMetric_test/20010411.log ...
12/20/01 13:51:02:
slmImport: Created new metric test_HTTP
12/20/01 13:51:02:
slmImport: Created new metric instance 587
fortest_HTTP:nwosgxab:https://banking.wellsfargo.com::
12/20/01 13:51:02:
slmImport: Created new metric test_HTTP_tput
12/20/01 13:51:03:
slmImport: Created new metric instance 588
fortest_HTTP_tput:nwosgxab:https://banking.wellsfargo.com::
12/20/01 13:51:03:
slmImport: Created new metric instance 589 for
test_HTTP:nwosgxab:www.cai.com/cgi-bin/AT-caisearch.cgi::....
12/20/01 13:51:04:
slmImport: Created new metric instance 598 for
test_HTTP_tput:nwosgxab:www.cai.com::
12/20/01 13:51:04:
Loading file
/usr/local/smm/databases/tmp/800828172/default into default...
12/20/01 13:51:05:
Loaded /usr/local/smm/databases/tmp/800828172/default
successfully into default
12/20/01 13:51:05:
slmImport completed
When the file is imported, the newly created metric types will be available under
the Import metric you created for this import. Clicking any of the metric types
will list the metric instances created for that type.
Using Collectors
421
Deleting an Import Metric Template

When you delete the import metric from the status tree, you delete the import
metric instance (the activated metric), the import metric definition (rules) and
any metric definitions and instances created as a result of the import metric.
To delete an import metric, follow these steps:
1.
Expand the status tree and find the import metric folder in the External Data
Import folder.
2.
Click the import metric label to display the configuration form.
3.
Click Delete.
Alternately, you can use the deleteMetrics command. For more information on
this command, see the appendix Command Reference in this guide.
422
Chapter
Using Reports
Unicenter SLM lets you create reports to view and distribute your monitored
data. These reports contain computed values for measured or collected data,
presented as tables and charts. Results are from within defined business hours or
24 hours, 7 days a week, and are presented in relation to predefined service
goals. Reports can include the following information:
Response time, availability, and outages for networks, systems, and services
Resource utilization in WAN and LAN
CPU and disk storage utilization
Error statistics for communication interfaces, processes, or services
Unicenter SLM relies on the report server to run reports.
Understanding the Report Server

The report server runs reports at scheduled intervals, using the smmReportd
process. This process activates report programs to run specific reports. The
report server goes through the following steps when started:
A connection to the database is created to read all existing report definitions.
A sorted job list is generated based on the execution time for each report.
The smmReportd process enters an event loop in which the report executions
are controlled by timer events.
Note: A timer event signals that a specific report execution should be
performed, or that the database should be read for new or modified report
definitions.
The event loop listens for commands from the console system, such as a
request for a restart.
Using Reports
51
Understanding Reports
The report server uses the following report programs:

Program
Description
runReport
Accepts a job ID for a specific report job. This process gathers

all options for the specified report from the database and then
calls smmReporter with these options.
This process also formats any output from smmReporter and
tells smmReportd to generate mail to specific notification
addresses.
smmReporter
Starts the program smm with all the options it receives from
runReport. This process also generates the report tree
structure and checks for any values exceeding thresholds in
the report.
smm
Generates the report.
Reports consist of the following sections:
Document
Contents
Result document
Contains the reported information from your monitored

systems.
Message document
Contains messages produced while creating the report,

including the definition of business hours for all targets,
periods with missing data for each data collection
included in the report, service incidents for each data
collection instance, host name lookup failures, and so on.
Unicenter SLM formats all reports as HTML documents.
You can create these reports as follows:
52
Interactively, through the web
Batch, running reports automatically at regular intervals
Creating Reports Interactively

To create reports interactively, follow these steps:
1.
From the drop-down list in the left-hand panel, select Report Groups. The
Report Group tree appears in the left-hand panel.
2.
Expand the Report Group tree to show the report groups.
3.
Right-click a report group. The pop-up menu appears.
4.
Choose Reporting, Make Reports. The Make reports page (for report groups)
appears in the right-hand panel. From this dialog, you can modify the report
values. For a detailed description of these values, see your online help
system.
5.
Complete the page and click Run!.
Unicenter SLM stores reports created interactively in a temporary area on the

console system.
Tip: If you select Make Reports from a predefined report group, you can only
produce reports based on the data collections in that group.
Creating Reports Automatically

Batch reports are predefined report commands that run automatically at regular
intervals. Using batch reports, you can schedule Unicenter SLM to produce a set
of reports every night for the previous day or a set of reports for the past week
each night between Sunday and Monday or other periods.
Batch reports are stored in the report repository and accessible to any user with
access to your console system.
Tip: To customize access to your reports, you must configure the web server.
Batch reports are created by the smmReportd process. You can produce batch
reports using the following methods:
GUI
Command line
Report Wizard
For more information on the Report Wizard, see the online help.
Using Reports
53
Changing smmReportd Defaults

The smmReportd process can run up to nine reports simultaneously. By default,
this process can run three reports simultaneously. To change this value, follow
these steps:
1.
From the SLM Systems tree, select Report Server, Configuration.
2.
Change the number of concurrent report processes from the drop-down list.
3.
Restart smmReportd.
Tip: Depending on the number of reports and the amount of data in each
report, all reports may not be done in the selected report period. Distribute
the report production evenly throughout the day to prevent overloading the
system. For example, instead of creating all reports at 01:00, create some at
02:00, 03:00, and so on.
Creating Batch Reports from the GUI

To set up batch report from the GUI, follow these steps:
1.
2.
3.
4.
Select Reporting, Make Reports. The Make reports page (for report groups)
appears in the right-hand panel.
5.
Complete the page based on the following rules:
54
You may only select a predefined report period. Do not select January to
December because this period is covered by other report periods.
Similarly, do not select the report periods Last hour or This hour because
these report periods are covered by the Today report period.
Because batch reports cannot be defined on single data collections you
cannot use the List function and set the report to run in batch.
6.
Click Save. The Store report command page appears.
7.
Complete the page and click OK.
Running Batch Reports from the Command Line

You can run the following types of batch reports from the command line:
Reports based on the last period defined in the report
Reports based on a specified time period
To set up a batch report based on the last period defined, enter the following
command:
SLM_Install_Path/bin/runReport job_id
where job_id is the job identification number. You can determine this number by
viewing the scheduled batch reports list. For more information on viewing batch
reports, see the online help.
The batch report job, identified by the job ID, specifies the report period. This
report period can be overruled as in the following command:
SLM_Install_Path/bin/runReport job_id timeframe
where
job_id
Identifies the job identification number. You can determine this number by
viewing the scheduled batch reports list. For more information on viewing
batch reports, see the online help.
timeframe
Identifies the report period. This parameter can have the following formats.
Time Period
Format
Example
Daily
Day of the week by name
Monday
Weekly
Week_week number
Week_01
Monthly
Month name_Year
January_2002
Quarterly
Q quarter number_Year
Q1_2002
Yearly
Year
2002
Using Reports
55
Understanding Report Groups
Using Reports
For detailed instructions on using reports, see the following topics in the online
help:
Viewing and Modifying Report History
Starting the Report Wizard
Displaying the Report View
Viewing and Modifying Today's Report Queue
Viewing and Modifying Scheduled Batch Reports

Report groups are objects used to group data collections together for reporting.
Groups include the definition of business hours and service level goals.
Context
Description
Business hours
Specifies the start and stop of each day of the week.

When running reports, the user has the option to
include only data collected within the business hours or
all data.
Service level goal

definitions
Specifies service goals for each metric type associated

with the data collections assigned to the report group.
Deviation reports report only results that violate the
service level goals, and regular reports mark results
that violate goals by color (red).
Note: Each service goal definition is associated with a
specific metric type such as IP network delay. If you
require different service goals for the same data
collection type, you must create a report group for each
goal.
56
Report Group Hierarchy

Report groups can be arranged into a hierarchy of groups, using the parent-child
inheritance structure, familiar in object-oriented programming.
For example, the group South_Region may contain the child groups Bandwidth,
Routers, and Novell_Servers. The child group Routers may be the parent of the
child group CPU_Utilization. The child group Novell_Servers may be the parent
of the child groups CPU_Utilization, Disk_Utilization, Operation, and
Active_Users.
You can create a report for any of these groups.

Adding and removing data collections in a report group, does not affect the
configuration of data collections. If you remove a data collection from a group,
you remove only the reference to the specific data collection from the report
group, not the actual data collection.
Using Reports
57
Creating Report Groups

To create a new report group, follow these steps:
1.
2.
Right-click Report Groups. The pop-up menu appears.
3.
Select Add Group. The New Group dialog appears.
4.
Enter the name of the group and click OK.

Note: You cannot use the following characters in the group name: curly
brackets ({ }), bar (|), or single quote ().
5.
6.
7.
Right-click the new report group. The pop-up menu appears.
8.
Select Description. In the right-hand panel, the report group Description

page appears. From this dialog, you can modify the following fields:
Option
Definition
Description
Specifies a description of the group. If defined, this

description is used in the title of reports for the group. If not,
the group name is used.
Business
hours
Defines business hours for each day.
Service goal
Defines service goal values for the data collections in the

group. Initially you can only specify service goals for the type
of data collections assigned to the group.
To specify any service goals, independent of any data
collections in the report group, click All Service Goals.
9.
Modify the report group description and click Save.
Once you have created your report group, you must add data collections for
reporting.
58
Adding Data Collections to Report Groups

To add data collections to a report group, follow these steps:
1.
2.
3.
4.
Select Content. In the right-hand panel, the report group Content page
appears.
5.
Optionally enter Agent, Metric name, and Description filters. Use filter when
you have many data collections. For example a filter of %cpu% in the Metric
name entry field limits the list to display data collections with metric names
containing the word cpu.
6.
Click Filter. Data collections appear in the All available data collections
column.
7.
Select the data collections and click Add. The selected data collections appear
in the Data Collections in Report_Group column.
Using Report Groups

For detailed instructions on using report groups, see the following topics in the
online help:
Viewing Report Group Information
Renaming Report Groups
Copying Report Groups
Configuring Data Collections
Removing Report Group Data Collections
Modifying Report Group Descriptions
Using Reports
59
Deleting Report Groups

Important! You cannot delete a report group with children. You must remove the
children from the report group and then delete the report group.
To delete a report group without children, follow these steps:
1.
2.
3.
4.
Select Delete. The Delete Report Group dialog appears. Optionally select the
Move reports to SLM_Install_Path/reports/tmp/removed check box.
Important! Reports stored in SLM_Install_Path/reports/tmp/removed are deleted if the

Delete Temp. Reports function is run. If you do not want to lose these reports, move them
to a safe place immediately or save the reports to the Unicenter SLM Report Repository.
5.
Click Yes.
Listing Report Group

You can list report groups by group ID, by directory, or you can list all report
groups currently defined. To list all report groups, enter the following
command:
lsReportGroups
Group ID
You can locate the report group ID for a report group name in the report group
description. To view the report group description, follow these steps:
1.
2.
3.
4.
Select Description. In the right-hand panel, the report group Description

page appears. The report group ID appears within the description.
To list report groups by group IDs, enter the following command:

lsReportGroups group-id [..]
510
Exporting Reports and Publishing Links
Directory
UNIX
To look up all file names and directories in the current directory, enter the
following command:
lsReportGroups *

You can export a report to an external web server using ftp or you can publish
the report link to a Unicenter Management Portal.
Note: When you publish a link, the actual report is not exported, only the URL.
However, you may not be able to access this link if the Unicenter Management
Portal is on one side of a firewall and the Unicenter SLM console is on the other
side.
Configuring the Web Server

To configure the remote web server to accept reports, follow these steps:
1.
Verify the following:
2.
Unicenter SLM Console has FTP access to the remote web server.
FTP user can create directories and files in the remote web server
directory.
Copy the following files from the Unicenter SLM Console to the web server:
Source Files
Destination Directories
SLM_Install_Path/reports/report.css
SLM_Install_Path/reports/smm.css
SLM_Install_Path/reports/std.css
Web_Server_Home/smm
SLM_Install_Path/gifs/header.gif
SLM_Install_Path/gifs/bhbar.gif
SLM_Install_Path/gifs/bhbar1.gif
SLM_Install_Path/gifs/line.gif
Web_Server_Home/smm/gifs/
SLM_Install_Path/html/java/statusTree.jar
Web_Server_Home/java/
where Web_Server_Home is the root directory of the remote web server.

Note: Perform this operation once for each web server you wish to export
reports to, not every time you export a report.
Using Reports
511
Exporting Reports
Unicenter SLM supports export using File Transfer Protocol (FTP) to transfer
report documents to a remote web server. The export specification must be
defined as an FTP URL for the remote server as follows:
ftp://user:password@server/directory
Examples:
ftp://slm:slm@external.acme.com/slm/
ftp://external.acme.com/slm/
The directory path is relative to the remote FTP user account. If the directory
path does not exist, Unicenter SLM creates the path.
UNIX
The user name and password, including the colon (:) and at-sign (@) characters,
are optional. If unspecified, the user and password for the remote server must
be specified in the following file:
SLM_Install_Path/.netrc
To specify a user name and password for FTP, follow these steps:
1.
In a text editor, open the following file:

SLM_Install_Path/.netrc
2.
Append a line with the following information for each remote FTP server:
machine hostname login username password password
where:
hostname
Identifies the host name for the remote FTP server.
username
Identifies the user name to use to log into this server.
password
Identifies the password to use to log into this server.
Example:
machine rptsrv login slmo password slmo
512
Export Example
You want to export reports to external.acme.com in directory slm relative to the
login directory of the FTP account. A directory called html is the root of
external.acme.com web server.
1.
After configuring the web server, ensure the slm directory is accessible from
the html directory on the web server.
2.
3.
4.
5.
6.
7.
Enter the following command in the Export this report to field:

ftp://external.acme.com/slm/
8.
Complete the page and click OK.
You can now access the exported report through the following URL:
http://external.acme.com/slm/category/group_id_path/index.html
where category and group_id_path for the report are the same as the console.
Export Tips
Unresolved Links
If you are exporting one or more, but not all, reports for a group, you may
experience unresolved links from the Report Repository tree. This error is
caused by the index.html file for this group file that references all reports
created on the console. You cannot manually edit this file, because it is
overwritten every time reports are exported for this group.
To avoid this issue, create another group on the console containing only the
reports you wish to export.
Using Reports
513
Entering the
Complete Path
To avoid having to type the complete path to an index file on the remote server,
create a parent group for all the groups for which you wish to export reports.
For example, you have two groups called Net and Servers. The parent group for
these groups is called CustomerA.
CustomerA/Net/index.html
CustomerA/Servers/index.html
You can create a report for CustomerA, export this report at least as often, and at
the same time, as the reports in the Net and Servers groups are exported.
CustomerA can now access http://remote_web_server/CustomerA/index.html,
and can see the reports in both Net and Servers groups from this index file.
Publishing Report Links

To publish report links, follow these steps:
1.
2.
3.
4.
5.
6.
Specify the Publish link to field. This field must be defined as a URL for the
Unicenter Management Portal as follows:
http://user:password@portal/category
Example:
http://admin:admin@portal:8080/Enterprise Management/SLA/
514
Controlling Report Content

Prior to export, you can control what reports are available on the external web
server. A report containing results in compliance with predefined service goals
can be exported automatically while a report with noncompliant results does not
get exported. An email about the noncompliant situation can be sent to the
Unicenter SLM administrator who can then verify the report results, correct
errors, or adjust the conditions for the report production, and then manually
rerun and export the report.
To control report content, follow these steps:
1.
2.
3.
4.
5.
6.
In the Do not export if report violates column, check the options that apply:
Option
Description
Availability
results
Indicates data violates service goals for availability.
Performance
results
Indicates data violates service goals for items other than

availability such as response time, utilization, and so on.
Missing data
Indicates the report is missing data.
Using Reports
515
Maintaining the Report Repository

Temporary reports can be moved to the report repository to ensure important
data is not deleted. The size of the report repository grows over time and must
be cleaned to limit its disk space usage and the number of entries in report index
reference files.
Deleting Temporary Reports

When report commands are run from the web user interface, reports are created
in a temporary area at the console system. You must clean this area at regular
intervals to free up disk space.
To delete temporary reports, follow these steps:
1.
From the drop-down list in the left-hand panel, select Report Repository. The
Report Repository tree appears in the left-hand panel.
2.
Right-click Report Repository. The pop-up menu appears.
3.
Choose Delete Temp. Reports. The reports in the temporary reports directory
are deleted.
Note: This action may interfere with any users presently creating or reading
reports in this area.
UNIX
To clean this temporary area regularly, add the following command to the user
smm crontab at the console system:
15 3 * * * find /usr/local/smm/reports/tmp -mtime +1 \
-exec rm -f {} \; > /dev/null 2>&
This command removes all files older than one day from the temporary area at
03:15 each night.
516
Saving Reports to the Report Repository

To prevent important reports saved in the temporary area from being deleted
you must save them to the report repository. To save reports to the report
repository, follow these steps:
1.
2.
Right-click Report Repository. The pop-up menu appears.
3.
Select Save Last Report.

Note: The Save Last Report procedure can only be applied to the last created
report.
4.
Follow the instructions on the page to complete the fields and click Apply.
Deleting Reports
To delete reports from the Report Repository, follow these steps:
1.
2.
Expand the Report Repository tree to any level and right-click a node. The
pop-up menu appears.
3.
Choose Delete Reports. The Delete reports from report repository page
Note: The reports displayed in the right-hand panel depend on the node you
right-clicked. For example, if you right-click on Week_20, all reports
generated in week 20 appear. If you right-click on a specific report, only that
report appears.
4.
Optionally filter the reports that appear.
5.
In the Action column, select the check box for each report you want to delete.
6.
From the Action drop-down menu, select Delete. A delete confirmation

dialog appears.
7.
Confirm the deletion.

Note: Batch reports tied to the deleted reports are not deleted, only the
report itself is deleted.
Using Reports
517
Chapter
Using the Interface

The Unicenter SLM user interface is web-based. All functions, administrative
tasks, and operative status are available from a web browser with access to the
console system. Unicenter SLM requires the web browser Internet Explorer 5.5
SP1 (or higher) or Netscape Navigator version 4 (or higher) as well as Java
Runtime Environment version 1.3 (or higher).
To ensure correct refresh of the current frame, follow these steps:
1.
From MS Internet Explorer, select the Tools, Internet Options.
2.
From the General tab, click Settings in Temporary Internet files.
3.
Select the Every visit to the page option and save your settings.
To access the Unicenter SLM user interface, access the following URL:
http://SLM_Console:6668
where SLM_Console is the host name or IP address of your console system.

You will be asked for a user name and password when you access the Unicenter
SLM interface. By default, both values are slmo.
Note: When using the host name for accessing the SLM Console, ensure the host
name is defined as an entry in your DNS solution or in the local host file. Do not
use localhost as the host name entry when running locally on the console.
For detailed instructions on using the user interface, see the online help.
Using the Interface
61
Propagating Status Colors
Propagating Status Colors

By default, Unicenter SLM does not propagate the status colors upwards in the
trees. To propagate the status colors for the SLM Systems tree, Report Groups
tree, or Report Repository tree, follow these steps:
1.
From the drop-down list in the left-hand panel, select a tree. The tree appears
in the left-hand panel.
2.
Right-click the top level on the tree, which is the tree's name. Alternately,
ensure that the left-hand panel has the mouse focus, and press Ctrl+R. The
pop-up menu appears.
3.
Select Propagate Status. The pop-up menu displays a check next to the
Propagate Status menu item. You must propagate the status for each tree
individually.
To turn propagation on permanently, edit the propagation property in the

smmrc.env file.
Tip: To display the status color definitions for the SLM Systems tree and
Report Groups tree that appear in the left-hand panel, at the bottom of the
right-hand frame, click the Show Legends Link.
Refreshing Status Trees

Because the color status in the SLM Systems tree, Report Groups tree, and Report
Repository tree, do not update automatically, you must manually refresh these
trees. To refresh the trees, follow these steps:
62
1.
In the left-hand panel, right-click in an empty space (a space not on the tree).
The pop-up menu appears.
2.
Select Reload Applet. The tree refreshes.
Controlling Access to the User Interface
Controlling Access to the User Interface

The web server at the console maintains access control and authorization for
different parts of Unicenter SLM through the web user interface.
A default access control scheme is configured during installation. This scheme
requires a user name and password to access functions other than static reports.
This access control is configured in the following Apache configuration file:
SLM_Install_Path/mhttpd/conf/httpd.conf
The following module defines the authorization:

<Directory "SLMHOME/cgi">
AllowOverride None
Options None
Order allow,deny
Allow from all
AuthName "Unicenter SLM Administrator"
AuthType Basic
AuthUserFile SLMHOME/mhttpd/conf/.htpasswd
AuthGroupFile SLMHOME/mhttpd/conf/.htgroup
require group admin
</Directory>
This definition requires that the user log in with a user in the admin group. The
AuthGroupFile identifies a file that defines the group admin. Default content of
this file is as follows:
admin: smm
This definition defines the group admin, containing the user smm. As such, smm
is the only user that can log in. The passwords for users are defined in the file
identified by AuthUserFile. This file must be maintained by the following
command:
SLM_Install_Path/mhttpd/bin/htpasswd
To create a new user/password file, enter the following command and follow the
prompts:
SLM_Install_Path/mhttpd/bin/htpasswd c SLMHOME/mhttpd/conf/.htpasswd smm
To add a new user to this password file, enter the following command and
follow the prompts:
SLM_Install_Path/mhttpd/bin/htpasswd SLMHOME/mhttpd/conf/.htpasswd guest
For more information, see your Apache documentation.
Using the Interface
63
Using the Metric Charter

The metric charter is a visualization and analyzing tool for any Unicenter SLM
metric. The metric charter provides a way of comparing and analyzing metric
values. You can load multiple data collections into the same 3D/2D scenario for
value comparison in any time scope. The scenario can be viewed in many settings
and edited by parameters in the menu pad.
To launch the metric charter, click the chart icon ( ) from a report or a metric
instance list. The metric charter menu pad appears.
Note: The metric charter graphs individual data collections independent of any
report groups and associated service goals. Service goal threshold lines are not
present in the metric charter.
The menu pad contains two menu buttons: Parameters and Load Graph.
Using Parameters
From the parameters menu, you can manipulate the appearance of the graph as
well as revealing trends.
The following examples list some ways in which you can change the way the
graph looks:
Use the Width slider for manipulating the thickness of the graph (only
available in the 3D view).
Use the Opaque slider to adjust the transparency of the graphs.
Use the Border slider to change the border thickness of each individual
graphs.
To reveal trends, you can use regression to indicate relationships of displayed

values.
64
Using Load Graph

From Load Graph, you can enable and disable the data collections displayed in
your graph. You can also enter individual parameters for each chart. To access
these parameters, click P.
To add more metrics into the metric charter, follow these steps:
1.
Click Add. The Add metric instances menu appears in the menu pad.
2.
Select how you wish to filter your data collections. You can filter by metric,
label, or agent.
3.
Enter the text to use in your filter. A list of metric types, agents, or labels
matching the filter string appears.
4.
Select a set of these entries. The list at the bottom shows data collections
matching the previous selections.
5.
Click Ok to add your selections.
Changing the Display

You can manipulate the graphs within the scene of the metric charter using the
following options:
Rotation
You can rotate graphs by clicking and dragging the mouse in the graph area,
in 3 D mode.
Time sliders
You can alter the time scope of the viewed portion of the graph by dragging
the sliders below the graphs.
Value reader
You can change the value reader - a transparent plane (or line) that crosses
the graph. If labels are enabled, the value of each graph at this point is shown
at the end of the label strings behind the graphs. Point to the value reader,
then click and drag to modify its position.
Using the Interface
65
Chapter
Using Metrics
Unicenter SLM contains a common description for data collections, called a
metric definition. Each data collection belongs to a specific metric definition,
which defines the following attribute types:
Collect
Identifies parameters and methods to configure a data collection instance to

measure, collect, or import the raw data provided by the metric type.
For example, a metric definition for CPU utilization on a specific system type has
attributes for the host name for the agent performing the data collection, the host
name of the target system, the collection method (for example, SNMP), the
parameters needed by the collection method (SNMP MIB variable, for example),
the sampling interval, and so on.
Report
Identifies parameters and methods to use when utilizing this metric type in
report production. These include the computing functions and context and label
information to use.
For example, a metric definition for CPU utilization on any system has attributes
for the label to use for the data collection instance in reports, the possible
computations to use on the collected data to produce results (such as average
CPU utilization and maximum CPU utilization), the presentation method (line or
bar graph), and so on.
Using Metrics
71
Understanding Metrics
Understanding Metrics
Metric definitions appear in the metrics section of the following file:
SLM_Install_Path/etc/smmdb.cfg.template
Note: Metrics can also be defined in separate files and loaded with a reference in
the SLM_Install_Path/etc/modules file.
Unicenter SLM uses the two types of metric definitions: folder metrics and data
collection metrics.
Folder Metrics
Folder metrics organize metrics into a tree structure. A folder metric may have
associated properties and methods to enable import of external data, but does
not have its own associated collected data. If the folder metric is used to enable
and control external data import, additional metric field properties are available.
Data Collection Metrics

Data collection metrics specify properties and methods for a particular data
collection, including how collected data arrive into a system and how this data
can be used in reports.
Adding Metric Definitions

Important! When adding new metric definitions to Unicenter SLM, create separate files
outside the smmdb.cfg.template file to prevent your definitions from being overwritten
when receiving patches or upgrades.
Metric definitions are defined in an ASCII file and loaded into the database.
Many metric definitions are defined in the
SLM_Install_Path/etc/smmdb.cfg.template file. Others are defined in separate
files in the SLM_Install_Path/etc directory.
To create a new metric, follow these steps:
1.
Copy a metric definition that is similar to your new metric from

SLM_Install_Path/etc/smmdb.cfg.template into the file
SLM_Install_Path/etc/myMetric.cfg.
where myMetric is the name of the file that will contain your custom metric.
2.
Add the following entry to the SLM_Install_Path/etc/modules file:

source /usr/local/smm/etc/myMetric.cfg
72
3.
Modify the copied metric to suit your new metric.
4.
If necessary, modify your service goals.
5.
Enter the following command to load the new metric definition into the
database:
smmBuild all
For detailed descriptions of metric syntax, see the appendix Metric Syntax in
this guide.
Tip: If you need to remove a metric definition from the database, use the
deleteMetrics command. For more information, see the appendix
Command Reference in this guide.
Example: Adding a Gauge Metric

In this example, you will create a new metric that collects and reports the
temperature of air flow into a Cisco router. Some Cisco routers support a part of
a Cisco MIB that maintains variables for the temperature measured at different
places in the router. The SNMP MIB variable for our new metric is defined in the
MIB file cisco.mib with the label envTestPt1Measure, and has the following
definition:
envTestPt1Measure OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Current value of test point 1. Typically a
temperature in centigrade."
::= { lsystem 79 }
Note: Because MIB variable reports a temperature that may vary, you can treat
this variable as a gauge even if the MIB defines it as an integer.
From the MIB you can see that this is a non-tabular MIB variable that requires
the instance value of 0.
To create the metric definitions, follow these steps:
1.
Copy cisco_cpu5 metric definition from

2.

source $SMM/etc/myMetrics.cfg
Using Metrics
73
3.
Modify the copied metric as follows:

Parameter
Change
metric name
Change to cisco_temperatureIn.
description
Change to Cisco Temperature Gauge.
metric_scope
Change to temperature.
metric_reports
Change to Temperature.
mib
Change to envTestPt1Measure.
instancekey
The resulting metric definition appears as follows:

array set metrics {
cisco_temperatureIn {
parent
Cisco_devices
class
node
agent
snmpCollect
label
{Cisco router}
description {Airflow temperature into the Cisco router}
class_scope node
metric_scope temperature
metric_reports {
real {{Temperature} °C inbound-temperature}
}
metric_fields {
agenthost
startnode
{{Target node} {entry} {} {required} {}}
description
interval {{Interval} {select} {1 5 10 15 20 30 60} {default_common} {10}}
community
mib
{{MIB variable} {hidden} {} {default} {envTestPt1Measure }}
mibType
{{MIB type} {hidden} {} {default} {GAUGE}}
mibFile
{{} {hidden} {} {default} {cisco.mib}}
instance
{{MIB instance} {hidden} {} {default} {0}}
instancekey {{MIB instance key} {hidden} {} {default}
{envTestPt1Measure}}
statusChanged
adminStatus
status
selectionName
dataDir {{Data dir} {hidden} {} {default} {\$SMM/databases/collect}}
dataDb
{{Data database} {hidden} {} {default_common} {default}}
deviceType
{{Device type} {hidden} {} {default} {router}}
vendorName
{{Vendor name} {hidden} {} {default} {cisco}}
}
}
}
4.
Change the following definition in the SLM_Install_Path/etc/myMetric.cfg

file:
array set service_goals {
inbound-temperature {{Inbound temperature (°C)} {entry} {} {35} {2}}
}
74
This change defines a default service goal for temperature as 35 degrees

Celsius. An average temperature above this goal will violate the service goal.
5.
database:
smmBuild all
When this command completes, reload your status tree, and the new metric
appears in the metric list. The new metric is available in the Cisco devices folder.
Example: Calculating Available Memory

In this example, you will create a new metric that collects and reports the
percentage of available memory on a Windows 2000 server using the Windows
2000 system agent MIB.
The SNMP MIB variables for our metric are defined in the MIB file caiW2kOs.txt
as follows:
w2kStatusMemPhysTotal OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"&<caiW2kOs.470>The total size of the physical memory
on the system (in kilobytes)."
::= { w2kStatusMemGroup 11 }
w2kStatusMemPhysValue OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"&<caiW2kOs.471>The size of the currently used
physical memory (in kilobytes)."
::= { w2kStatusMemGroup 12 }
From the MIB we see that this is a non-tabular MIB variable that needs the
instance value of 0.
1.
Copy cai_memoryUxUtil metric definition from

2.

Using Metrics
75
3.

Parameter
Change
metric name
Change to cai_memoryW2kFree.
parent
Change to CA_W2K_MEMORY.
label
Change to W2K Test.
description
Change to W2K Test.
metric_reports
Change to Free memory.
mib
Change to
pstAvailable,w2kStatusMemPhysValue,w2kStatusMemPh
ysTotal.
instancekey
vendorName
Change to CA.

array set metrics {
cai_memoryW2kFree {
parent
CA_W2K_MEMORY
class
node
agent
snmpCollect
label
{Windows 2000 server}
description
{Windows 2000 server available memory}
class_scope
node
metric_scope
memory
metric_reports {
real
{{Free memory} % free-memory}
}
metric_fields {
agenthost
startnode
{{Target node} {entry} {} {required} {}}
description
interval
{{Interval (min)} {select} {1 5 10 15 20 30 60} \
community
mib
{{MIB variable} {hidden} {} {default} \
{pstAvailable,w2kStatusMemPhysValue,w2kStatusMemPhysTotal}}
mibType
mibFile
{{MIB file} {hidden} {} {default} {caiW2kOs.txt}}
instance
{{MIB instance} {hidden} {} {default} {0}}
port
{{SNMP agent port} {entry} {} {default_common} {6665}}
instancekey
{{MIB instance key} {hidden} {} {default} \
{w2kStatusMemPhysValue}}
statusChanged
adminStatus
status
selectionName
dataDir
{{Data directory} {hidden} {} {default}
dataDb
deviceType
{{Device type} {hidden} {} {default} {agent}}
vendorName
{{Vendor name} {hidden} {} {default} {caiw2kos}}
}
}
}
76
4.
Change the following definition in the SLM_Install_Path/etc/myMetric.cfg

file:
free-memory {{Free memory (%)} {entry} {} {5} {3}}
}
This change defines a default service goal for free memory as 5 percent. An
average free memory below this goal will violate the service goal.
5.
database:
smmBuild all
appears in the metric list.
Example: Monitoring Bandwidth Use

In this example you will create a new metric that collects and reports the port
bandwidth use on a Xylan ATM switch. The Xylan switch maintains a set of MIB
variables to count the number of ATM cells transferred across its ATM ports.
These MIB variables are defined in the XYLAN-CSM-MIB stored in the xylancsm.mib file. To load this MIB, you must load the XYLAN-BASE-MIB stored in
the xylan.mib file. The MIB variables of interest are defined as follows:
xylnatmInterfaceStatPortIndex
OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The port number in this slot"
::= { xylnatmInterfaceStatEntry 2}
xylnatmInterfaceStatRxCells
OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of Received Cells at this interface
(OC3, OC12, ATM25...)"
xylnatmInterfaceStatTxCells
OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of transmitted cells at this interface"
Using Metrics
77
The first MIB variable will be used as a value for the instancekey in the new
metric to ease selecting a specific port for a metric instance. The table identifies
the switch ports on the ATM switch. The last two MIB variables are counters for
received and transmitted ATM cells across each ATM port.
No MIB variable exists in the Xylan MIB that identifies the ATM port speed, so
this has to be determined and entered manually by the user when creating a
metric instance. To represent this variable, use the metric attribute exprConstant.
Because port speed is expressed in bits/second and the MIB counters count ATM
cells of size 53 bytes (octets), the value assigned to the exprConstant must be
calculated as follows:
exprConstant = speed / 53

1.
Copy fr-util metric definition from

2.

3.
78

Parameter
Change
metric name
Change to xylan_utilAtmPort.
parent
Change to Xylan_devices.
label
Change to Xylan test.
description
Change to Xylan test.
mib
Change to
ifUtil,xylnatmInterfaceStatTxCells,xylnatmInterfaceStatRxC
ells.
instancekey
Change to xylnatmInterfaceStatPortIndex.
exprConstant
Change to empty. This action requires the user to manually

specify a value computed as described by the label (Port
speed (bps) / 53).

array set metrics {
xylan_utilAtmPort {
parent
Xylan_devices
class
link
agent
snmpCollect
label
{ATM port}
description {Bandwidth utilization measured on an Xylan ATM port}
class_scope link
metric_scope util
metric_reports {
real
{{Bandwidth utilization} % util-bandwidth}
}
metric_fields {
agenthost
startnode
{{Target host} {entry} {} {required} {}}
endnode
{{Neighbour host} {hidden} {} {optional} {none}}
description
interval
{{Interval (min)} {select} {1 5 10 15 20 30 60} \
community
mib
{{MIB expression} {hidden} {} {default} \
{ifUtil,xylnatmInterfaceStatTxCells,xylnatmInterfaceStatRxCells}}
mibType
mibFile {{MIB file} {hidden} {} {default} {xylan.mib, xylan-csm.mib}}
instance
{{MIB instance} {entry} {} {required} {}}
exprConstant
{{Port speed (bps) / 53} {entry} {} {default_common} {}}
instancekey
{{MIB instance key} {hidden} {} {default} \
{xylnatmInterfaceStatPortIndex}}
linktype
{{Link type} {hidden} {} {default} {duplex}}
statusChanged
adminStatus
status
selectionName
dataDir
{{Data directory} {hidden} {} {default} \
dataDb
deviceType
{{Device type} {hidden} {} {default} {switch}}
vendorName
{{Vendor name} {hidden} {} {default} {xylan}}
}
}
}
4.
Add the following folder metric definition inside the array set metrics:
Xylan_devices {
parent
class
description
}
.
folder
{Xylan devices}
This definition adds a new metric folder labeled Xylan devices in the Metrics
root branch.
5.
database:
smmBuild all
appears in the metric list.
Using Metrics
79
Platform Specific Metrics

UNIX
Platform specific metrics are metrics that can only be collected by a collector
running on a specific platform.
The following collector metrics are bundled with Unicenter SLM, but not enabled
by default:
ldap
Measures the availability and response time for the LDAP directory service
provided by the target node from the collector. This metric queries the LDAP
server and records the response time for the query. If no response is received
within a time-out period, the service is assumed unavailable.
This metric requires the ldapsearch command to be available on the collector
system. For more information on this command, see http://www.openldap.org.
nfs_cp
Measures the response time and availability of a NFS mounted from the
collector system to a disk system at the remote node. This metric copies a
specified file on the target host to the collector system. If the operation does not
complete within a time-out period, the service is assumed unavailable.
This metric requires that the file systems are already mounted. For more
information, see your UNIX command manual.
nfs_find
Measures the search time and availability of a NFS mounted from the collector
system to a disk system at the remote node. This metric searches for all files in
and below a specified directory at the mounted file system. If the operation
does not complete within a time-out period, the service is assumed unavailable.
This metric requires that the file systems are already mounted. For more
information, see your UNIX command manual.
nis
Measures the response time and availability of the NIS service. This metric
queries a specific key from the local NIS service available to the collector
system. If the operation does not complete within a time-out period, the service
is assumed unavailable.
This metric requires the ypmatch command to be available on the collector
system. For more information on this command, see your UNIX command
manual.
710
smb
Measures the response time and availability of a SMB service (compatible with
the LanManager protocol) from the collector system to a disk system at the
target node. This metric copies a specified file on the target host to the collector
system. If the operation does not complete within a time-out period, the service
This metric requires the smbclient command to be available on the collector
system. For more information on this command, see http://www.samba.org.
wins
This metric measures the response time and availability of the NetBIOS name
service provided by the target node. This metric queries a specific name from
the service. If the operation does not complete within a time-out period, the
service is assumed unavailable.
This metric requires the nmblookup command to be available on the collector
system. For more information on this command, see http://www.samba.org.
Activating Platform Specific Metrics

To activate these platform specific metrics in the user interface, follow these
steps:
1.
Add the following line to the SLM_Install_Path/etc/modules file:

source SLM_Install_Path/etc/SLM_UNIX_Collector.cfg
2.

smmBuild all
Note: These metrics will be available in the Metric branch of a Windows system.
Any operations that involve the collector on such systems will fail with these
metrics.
Using Metrics
711
Additional Metric Files
Additional Metric Files

In addition to the SLM_Install_Path/etc/smmdb.cfg.template, the following
metrics files are shipped with Unicenter SLM and enabled by default:
File
Metric
PerfAgent.cfg
Contains definitions to import performance cubes.
SuperPing.cfg
Contains definitions to import SuperPing data.
WMO.cfg
Contains definitions to import response time and

availability data from Unicenter Management for Web
Servers.
MetricHierarchy.cfg
Contains definitions for the metric tree hierarchy.
w2k.cfg
Contains SNMP based metric definitions for systems

supporting the Unicenter agent for Windows 2000.
sap4.cfg

supporting the Unicenter agent for SAP.
ntr.cfg

supporting the Unicenter agent for Windows NT 4.0.
exchange.cfg

supporting the Unicenter agent for Microsoft Exchange.
The following metric files are also shipped with Unicenter SLM but not enabled:
File
Metric
HP-UX.cfg

supporting the HP HP-UX MIB.
HostMib.cfg

supporting the Host Resource MIB (RFC1514).
SLM_UNIX_Collector Contains metric definitions for collectors running on

.cfg
UNIX.
712
Chapter
Understanding the Database

The Unicenter SLM database stores and maintains configuration data as well as
collected data. This database uses the following aspects to describe and maintain
this information:
Database Group
Description
Metrics
Defines the type and properties of data that can be

collected, measured, and used.
Report group
Defines how data is organized and grouped and the context

to apply for reporting.
Collected data
Defines the organization of raw or reduced data upon

which calculations and reporting are based.
81
Understanding Data Storage

Collected data is stored differently on collector and console systems.
Collector Storage
On remote collector systems, each data collection is stored to a separate data
collection file, identified by its data collection ID (dcid), located in the following
directory:
SLM_Install_Path/databases/collect
These are plain ASCII files, with each line containing a sampled value in five
comma-separated columns:
Column
Description
Data collection ID (dcid)
Identifies the unique ID for the data collection. This

name is the same as the file name.
Sample time
Identifies the UNIX epoch time the data was

measured/sampled.
Sample interval
Identifies the sampling interval for this data

collection, in seconds.
Qualifier
Identifies a specific instance for data collections with

multiple sampled values.
Value
Identifies the measured/sampled value.
This file content might appears as follows:

123,
123,
123,
123,
123,
958897234,
958897294,
958897354,
958897414,
958897474,
60,
60,
60,
60,
60,
0,
0,
0,
0,
0,
4.0
5.0
4.0
4.0
4.0
Unicenter SLM uploads these files to the console system and loads them into the
database. After upload, the old content is removed from the collector system.
82
Console Storage
In the database, collected data is stored in rows in the collected_data database
table. This table has the following columns:
Column
Type
Nulls Defaults
dcid
Integer no
no
Identifies the data collection ID for the

data collection. This unique ID is used
for all references.
sampletime
Integer no
no
Identifies the UNIX epoch time for the

sample time.
sampleperiod Integer no
no
Identifies the sample period, in

seconds.
qualifier
no
Identifies the qualifier integer used for

data collections containing multiple
sets of data. For example, data
collection on a full duplex network
interface has a separate set of data for
in- and out-bound, labeled with the
qualifiers 1 and 2.
Integer no
Description
This field is normally empty or

contains the value 0 when unused.
samples
Integer yes
null
Identifies the number of samples on

which this entry is based.
If the data has not been reduced, this
field is empty.
avgval
Float
yes
null
Identifies the sampled value or

calculated average value if the data has
been reduced
minval
Float
yes
null
Identifies the minimum data value in

the reduced set.
field is empty.
maxval
Float
yes
null
Identifies the maximum data value in

the reduced set.
field is empty.
stddev
Float
yes
null
Reserved for future use.
83
Understanding Data Reduction

Unicenter SLM reduces collected data as the data ages, using the following
defaults:
Data Reduction Time
Type of Reduction
30 days
Data within each hour is combined.
90 days
Data within each four hour segment is combined.
365 days
Data for each day is combined.
For example, after 30 days, six samples gathered during one hour are reduced to
one sample. Similarly, after 90 days, the reduced four samples representing four
hours are reduced to one sample.
Tip: Unicenter SLM includes a maintenance script that cleans the database
for optimal speed. This script is installed as a separate cron (batch) job that is
run each night. This script also executes the data reduction procedure. To
run successfully, the maintenance script requires temporary disk space in the
work area of the database. We recommend a minimum of 1 GB of free disk
space available on the database disk partition.
During data reduction, the average, maximum, and minimum are calculated, and
the number of raw samples in a reduced data sample is calculated. In its raw
form, only the sampled value is stored. Collected data describing incidents and
service availability is not reduced but is maintained in its original form.
Note: During data reduction, Unicenter SLM does not release acquired disk
space to the file system. That is, the database continues to occupy the same
amount of disk space before and after data reduction. Data reduction allows the
database to maintain a given amount of disk space so that Unicenter SLM does
not need to acquire more space from the file system.
You can customize this data reduction policy to reflect your companys data
maintenance policies.
84
Customizing Data Reduction Policy

Data reduction policy is specified in the datareduction section of the smm.cfg
file. This policy identifies multiple levels of reduction. Each level defines how
data is reduced and the age of the data this reduction is applied to. The age of the
data is limited by the next level specification. Up to nine levels may be defined.
To customize how frequently data reductions occur at your installation, follow
these steps:
1.
2.
Locate the datareduction section and change the data reduce parameters to
the desired reduction period. This section appears as follows:
[datareduction]
DATA_REDUCE_LEVEL_1 = 30:60
Each definition contains the age of the collected data at which to begin the
reduction, in days, and the reduction size, in minutes. The previous example
shows the following levels of data reduction:
Level
Description
Specifies that collected data older than 30 days and younger than 90
days (start of level 2) is reduced to 60-minute samples.
Specifies that collected data older than 90 days and younger than
365 days (start of level 3) is reduced to 240-minute (4-hour) samples.
Specifies that collected data older than 365 days is reduced to

1440-minute (1 day) samples.
3.
4.

smmSetup
Note: To disable one or more data reduction levels, comment the entry with a
pound sign (#) at the start of the line.
85
Maintaining the Database

You must maintain your database to optimize speed and response time.
Database maintenance tasks are implemented through a cron-scheduled script
(smmdb_maintenance) in the SLM_Install_Path/bin directory.
For more information on how to tune and maintain an Advantage Ingres
database, see the Advantage Ingres Database Administration Guide.
For more information on how to tune and maintain a Microsoft SQL Server
database, see the Microsoft SQL Server documentation.
Understanding the cron Job

The cron utility is configured to check the system and data collection status at
specific intervals. By default, this check is performed once every 15 minutes by
the program smmCheck, on every Unicenter SLM system.
On an SLM console system, the cron definition also runs the database
maintenance program, smmdb_maintenance, each night. This program executes
data reduction.
Note: For Advantage Ingres, cron also tunes the database for optimal
performance.
Reading Database Error Messages

Advantage Ingres
If the database becomes corrupt, you may receive error messages stating the
database is inconsistent. Database corruption can be caused by a number of
factors, including power interruption.
Some error messages appear in the output of cron scheduled jobs. If the
smmdb_maintenance script encounters errors, this error is written to the mail
recipient of the cron.
86
Modify Table Errors

Errors related to modify jobs are written to the mail recipient and to the
following log file:
SLM_Install_Path/var/log/smmdb_maintenance.log
Look for errors with the following format:

Failed to modify table
where table is collected_data, data_collections or data_collect_attrs.

Open Database Errors
The following message is a common entry in the mail output or log file:
Sysmoding database 'smmdb' . . .
E_US0014 Database not available at this time.
o The database may be marked inoperable. This can occur if
CREATEDB failed.
o An exclusive database lock may be held by another session.
o The database may be open by an exclusive (/SOLE) DBMS server.
(Thu Dec 20 23:05:25 2001)
Sysmod of database 'smmdb' abnormally terminated.
The message indicates that the command sysmod smmdb was not executed,
since the database is open. If checkpointing of the database is set up, ensure that
the job that executes the checkpoint does this prior to the checkpoint.
Improving Database Performance

Advantage Ingres
To run the maintenance utilities to improve the overall performance of the

reporting execution speed, follow these steps:
1.
UNIX
Shut down all database activity:

crontab > cron.txt
crontab /dev/null
smmCollect sd
smmReportd sd
smmdbd sd
Windows
SLM Cron Scheduler
SLM xmmCollect
SLM smmdbd
SLM smmreportd
87
2.
Enter the following commands to connect to the Unicenter SLM database

through the terminal monitor:
sql l smmdb
modify collected_data to merge\g
commit\g
modify data_collect_attrs to merge\g
commit\g
modify data_collections to merge\g
commit\g
\q
Note: If an exclusive database connection is not achieved, stop the remaining

processes by looking through the output of the ps ef command. Use the kill
pid# command to stop processes still connected to the database.
3.
UNIX
Restart the collector, report, and database daemons:

crontab > cron.txt
crontab /dev/null
smmCollect sd
smmReportd sd
smmdbd sd
Windows
88
Start the following services:
SLM Cron Scheduler
SLM xmmCollect
SLM smmdbd
SLM smmreportd
Recovering an Inconsistent Database

Advantage Ingres
If the database becomes corrupt, you may receive error messages stating the
database is inconsistent. Database corruption can be caused by a number of
factors, including power interruption.
If the database becomes inconsistent, try to recover the database by following
these steps:
1.
Inspect the Advantage Ingres error log (II_SYSTEM/ingres/files/errlog.log

), at the end, for informational errors.
For example, if the log says that the smmdb database or the system catalog
database (iidbdb) is inconsistent, you can mark the database as consistent.
To mark a database consistent, enter the following command as user ingres:
verifydb oruninteractive sdbname db_name oforce_consistent
where db_name identifies the database to be marked consistent.

Important! Removing the inconsistency flag does not repair the database but does
provide access to it.
2.
Enter the following command as user smm to establish database connection

using the terminal monitor:
sql smmdb
If this process works, you have access to the database. If this process does not
work, you must restore your database from your last backup.
3.
Enter the following command to exit the terminal monitor:

\q
4.
Enter the following command as user smm to unload the database:

mkdir backup
cd backup
copydb smmdb
sql smmdb < copy.out
5.
Enter the following command to destroy the smmdb:

destroydb smmd
6.
Enter the following command to recreate the smmdb:

createdb smmdb
7.
Enter the following command to load the backup:

sql smmdb < copy.in
8.
Enter the following command to update the system catalogs:

sysmod smmdb
89
If any of these steps fail, consult the error log. If the error log does not reveal the
issue, you must restore your database from your last backup. For more
information on restoring an Advantage Ingres database from a backup, see the
Advantage Ingres Database Administration Guide.
Checkpointing the Database

Advantage Ingres
To enable checkpointing of the smmdb database, add the following line to the
crontab for user ingres:
30 1 * * * $II_SYSTEM/ingres/bin/ckpdb d usmm smmdb.
This line enables a checkpoint 01:30 every night, and deletes previous
checkpoints.
If a database error occurs, stop all Unicenter SLM processes and enter the
following command to restore the last checkpoint.
rollforwarddb smmdb
810
Chapter
Using Traps and Logs

Unicenter SLM can log events to the Unicenter Event Console as well as
providing local logs for troubleshooting.
Using Unicenter Event Console

The console and collector systems are able to produce SNMP specific traps. These
traps can be registered by any SNMP trap daemon running on a manager host
and integrated with Unicenter Event Console using Message Records and
associated Message Actions.
To determine which host is running the necessary Enterprise Management
components, enter the following command:
catrapd
Enterprise Management starts and stops catrapd if catrapd was activated during
installation. When catrapd is activated on a node where a network manager is
active, catrapd automatically detects and interfaces with the manager provided.
Any received trap is unpacked and sent to the Event Management console log,
where it is recorded. At the console log, the trap is also available for subsequent
automatic mapping, interpretation, and action processing as defined by your
Event Management policies.
91
Generated SNMP Traps

In addition to the standard Unicenter SLM traps, the smmCollect sub-agents,
pathagent and appagent, and the report daemon, generate predefined messages
as SNMP traps and deliver this information to a specific trap recipient.
Note: If the smmCollect or smmReportd process has stopped, no SNMP traps
are sent.
Unicenter SLM generates the following SNMP traps. All of these traps use the
OID 1.3.6.1.4.1.791.2.10.2.55.
snmpPathUp
snmpPathUp indicates that the specified data collector is Up. The original
message format follows:
%CATD_I_060, SNMPTRAP: -c public 791 10.119.74.118 nwosgxab
1.3.6.1.4.1.791.2.10.2.55.1.0
.iso.org.dod.internet.private.enterprises.791.2.10.2.55.1.0
1.3.6.1.4.1.791.2.10.2.55.2.0
1.3.6.1.4.1.791.2.10.2.55.3.0
ipnet@10.119.74.14 is up as seen from nwosgxab
6 1 00:00:09 3 OID:
VALUE: 424 OID:
VALUE: 3 OID:
VALUE:
snmpPathDown
snmpPathDown indicates that the specified data collector is Down. The original
%CATD_I_060, SNMPTRAP: -c public 791 10.119.74.118 nwosgxab
1.3.6.1.4.1.791.2.10.2.55.1.0
1.3.6.1.4.1.791.2.10.2.55.2.0
1.3.6.1.4.1.791.2.10.2.55.3.0
http@www.freia.no is down as seen from nwosgxab
6 2 01:18:46 3 OID:
VALUE: 247 OID:
VALUE: 3 OID:
VALUE:
slmoSLAviolate
When a threshold, predefined as a Service Goal, has exceeded, a warning
message is sent by the current console, to the SNMP trap recipient. The original
%CATD_I_060, SNMPTRAP: -c public 791 10.119.74.118 nwosgxab 6 10 00:00:09 1 OID:
1.3.6.1.4.1.791.2.10.2.55.3.0
.iso.org.dod.internet.private.enterprises.791.2.10.2.55.3.0 VALUE: UNICENTER_Core
Objects: IP network delay : Thursday : 35% missing data : UNICENTER_Core
Objects: IP network delay : Thursday : 35% performance threshold exceeded :
"http://nwosgxab:6668/smm/internal/2/Thursday/1661082654.html"
92
slmoMissingData
When a collector system performs measurements against a data collection and
the console discovers that data are missing within a specific period, a warning
message is sent as an SNMP trap, by the current console. The original message
format follows:
1.3.6.1.4.1.791.2.10.2.55.3.0
.iso.org.dod.internet.private.enterprises.791.2.10.2.55.3.0 VALUE: UNICENTER_Core
Objects: IP network availability : Wednesday : Missing data :
http://nwosgxab:6668/smm/internal/2/Wednesday/1491305784.html
slmoNoData
When a collector system performs measurements against a data collection and
the console discovers that data are missing for the entire reporting period, a
warning message is sent as an SNMP trap, by the current console. The original
1.3.6.1.4.1.791.2.10.2.55.3.0
.iso.org.dod.internet.private.enterprises.791.2.10.2.55.3.0 VALUE: BKK Prod:
Availability based on UNICENTER Propagated severity prop : Thursday : No data in
report : "http://nwosgxab:6668/smm/internal/19/20/27/Thursday/1948002217.html"
slmoMsgError
When a configuration failure for a specific metric is discovered a warning
message is sent by the current collector as an SNMP trap. The original message
format follows:
1.3.6.1.4.1.791.2.10.2.55.3.0
.iso.org.dod.internet.private.enterprises.791.2.10.2.55.3.0 VALUE: 447
10.119.74.0 Permission denied
slmoMsgCritical
When the report daemon has registered a failure, a warning message will be sent
by the current collector system as an SNMP trap. The original message format
follows:
1.3.6.1.4.1.791.2.10.2.55.3.0
.iso.org.dod.internet.private.enterprises.791.2.10.2.55.3.0 VALUE: smmReportd:
initReportList failed to connect to SMM db: Connection refused
93
Using Message Records and Actions

To implement message records and actions on the current Event Manager host
running Event Management Console and catrapd, follow these steps:
1.
Copy the following files from the em directory on the Unicenter SLM CDROM to the Event Management Console host:
File
Description
snmpPathUp.utl
Specification file for all SNMP traps

with status up.
snmpPathDown.utl

with status down.
slmoSLAviolate.utl

with status warning.
slmoMissingData.utl

with missing data for the specified
report period.
slmoNoData.utl

with no data for the entire report
period.
slmoMsgError.utl

with configuration failure.
slmoMsgCritical.utl

with SLM processes stopped.
Note: The provided files are stored in the cautil format and can be shown
with a text editor like Notepad.
2.
Enter the following command to import the files into the DSB database:
cautil f
specification_file
Note: The cautil f command has to be executed for each specification file.
3.
Enter the following command to activate the changes in the Enterprise

Management Database:
oprcmd opreload
94
4.
Log in to the current Console or Collector system.
5.
From the Status Tree Frame on the SLM system, select SLM Systems, SLM
system host name, Data Collect Server, Configuration.
6.
Enter the IP address or host name of the SNMP trap recipient in the field
Network Management System. If specifying more than one NMS, separate
with blank spaces.
Note: If you need to make any changes to this default installation, you can edit
the specification files or use the graphical interface. To start the GUI, enter the
following command:
caugui msgrecord
Integrating SNMP Trap Messages

When Unicenter SLM sends a trap to the Unicenter Event Management Event
Console, the original message string appears in the Log Messages area. You can
configure this interface to display details about the report associated with the
current trap when you right-click on the current message and select User action
from the menu for the following SNMP trap messages:
SlmoSLAviolate
Service Goal in report exceeded
SlmoMissingData
Missing data in the report
SlmoNoData
No data for the entire reporting period
To configure Event Management to display these details, follow these steps:
1.
Create a directory named C:\SLMO-Events on the Unicenter Event

Management Event Console where you intend to receive and display all
SNMP traps generated by SLM.
2.
Copy the following files from the em directory on the Unicenter SLM CDROM to the previous created directory on the Event Console:
emlog1.exe
emslmo.bat
3.
Define the CAI_MSG_EXIT environment variable to be emslmo.bat.

Ensure the emslmo.bat file matches your environment, editing the file if
necessary. Specify the entire path where the executable file for your browser
application is stored in the environment variable %path%.
95
Logging
Logging
The smmCollect, smmReportd and smmdbd daemons log messages to the
following files:
SLM_Install_Path/var/log/smmCollect.log
SLM_Install_Path/var/smmReportd.log
SLM_Install_Path/var/log/smmdbd.log
Logging is enabled by default. These log files are maintained automatically, but
you may need to check the size of these files from time to time, and, perhaps,
truncate them.
In addition, the following processes log data to the corresponding log files.
These files must be maintained manually.
Process
Log File
appagent
appagent.log
data import
import_remote_data.log
export of reports
export.log
core import facility
coreimport.log
Maintaining Console Log Files

The console system runs at least one web server. The web servers log activities
and write any errors detected to log files located in the following directory:
SLM_Install_Path/mhttpd/logs
Unless these files are maintained from time to time, they may grow out of
control.
UNIX
To reset the log files, enter the following commands:

cat /dev/null > access.log
cat /dev/null > errors.log
96
Logging
Changing Logging
To change logging for your Unicenter SLM installation, follow these steps:
1.
2.
Locate the environment section and change the logging parameters, as

appropriate, to the desired reduction period. This section appears as follows:
[environment]
II_SYSTEM = /opt/ca/ingresii
SMM = /opt/ca/slm
localhostname = $hostname$
# Logging
IMPORT_LOG = /usr/local/smm/var/log/import_remote_data.log
EXPORT_LOG = /usr/local/smm/var/log/export.log
DBMAINTENANCE_LOG = $SMM/var/log/smmdb_maintenance.log
#APPAGENT_LOG = $SMM/var/log/appagent.log
#COREIMPORT_LOG = $SMM/var/log/coreimport.log
#SMM_http_APPAGENT_LOG = $SMM/var/log/http.log
#SOAP_LOG = $SMM/var/log/soap.log
# Status tree view/propagation
STATUSTREEVIEW = on
SLMSYSTEMSPROPAGATION = off
REPORTGROUPPROPAGATION = off
REPORTREPOSITORYPROPAGATION = off
3.
4.

smmSetup
Note: To disable one or more logging entries, comment the entry with a pound
sign (#) at the start of the line.
97
Logging
Adding Logging
To enable logging in individual modules in smmCollect, follow these steps:
1.
2.
Locate the environment section and add log specifications to the section. Log
specifications are defined as follows:
log_name = file_name
where file_name is the name of the log file and log_name is one of the
following:
Log Name
Description
IMPORT_LOG
Enables logging of imported data.
EXPORT_LOG
Enables logging of report export to remote

servers.
DBMAINTENANCE_LOG
Enables logging of smmdb_maintenance

operation.
SOAP_LOG
Enables logging of all SOAP based queries to

the console system.
COREIMPORT_LOG
Enables logging of coreimport operation.
APPAGENT_LOG
Enables more detailed logging of service

based metrics. These include dns, ftp, ftpping, http, imap, nfs, nntp, ntp, pop3, smtp
and tcp_echo.
SMM_metric_APPAGENT_
LOG
Enables more detailed logging of a specific

service based metric to a separate log file. For
example, the following command enables
logging of any http metric instance to
log1.txt:
SMM_http_APPAGENT_LOG = log1.txt
3.
4.

smmSetup
98
Checking Email Messages
Checking Email Messages

UNIX
Some of the tasks in Unicenter SLM are performed from cron. When a cron job
or smmReportd produces output on a UNIX system, it is mailed to the local
smm user. You must check the smm mail accounts at every Unicenter SLM
system regularly to detect any errors or invalid configurations.
We recommend forwarding mail from these accounts to a common mail account,
such as the Unicenter SLM system administrators mailbox.
99
Appendix
Database Tables
The database consists of 32 tables, which can be divided into the following
groups:
Group
Description
Metric definition
Contains data on the metric definition.
Data collection
Consists of five tables that link to the metric group by

metric_name. The data_collections table holds the value
dcid, which identifies relations into this table group.
System configuration
Configures the system and operates the data collector.
Report
Describes the aspects covering the report configuration,

production, and history.
The database contains no views and no stored procedures.
Metric Definition Tables

The database includes the following metric definition tables:
metric_field_values
The metric_field_values table stores metric field values for a metric field
identified by field_name and belonging to metric_name. Typically, this table
contains possible values for a field.
Column Name
Type
Length
Nulls
Defaults
Seq
metric_name
varchar
100
no
no
field_name
varchar
50
no
no
value
varchar
50
no
no
Database Tables
A1
metric_fields
The metric_fields table stores attributes for a metric field identified by
field_name and belonging to metric_name. The label and description fields
contain a short and long description of the field. The type field identifies the type
of user interface element to use for this attribute. For example, entry for a
regular input entry or select for a selection list.
A2
Column Name
Type
Length
Nulls
Defaults
Seq
field_name
varchar
50
no
no
metric_name
varchar
100
no
no
label
varchar
100
yes
null
tooltip
varchar
50
yes
null
description
varchar
255
yes
null
tab_order
integer
yes
null
type
varchar
20
no
no
property
varchar
20
yes
null
required
integer
yes
null
editable
integer
yes
null
hidden
integer
yes
null
defaultval
varchar
255
yes
null
minval
varchar
255
yes
null
maxval
varchar
255
yes
null
metric_menues
The metric_menues table stores and identifies metric menu configuration
information. This identification is relevant for the GUI of a metric.
Column Name
Type
Length
Nulls
Defaults
Seq
metric_name
varchar
100
no
no
menu_id
varchar
100
no
no
menu_label
varchar
100
no
no
taborder
varchar
10
yes
no
trig
varchar
50
no
null
type
varchar
50
no
no
action
varchar
255
no
no
metric_reports
The metric_reports table stores definitions for report types with attributes for the
name, the metric_name to which it applies, the report function, and a goal id and
unit.
Column Name
Type
Length
Nulls
Defaults
Seq
report_name
varchar
255
no
no
metric_name
varchar
100
no
no
report_function
varchar
50
no
no
goal_name
varchar
100
yes
null
unit
varchar
50
yes
null
Database Tables
A3
metrics
The metrics table stores available metric types in the database.
Note: Every metric must have a unique name.
A4
Column Name
Type
Length
Nulls
Defaults
Seq
metric_name
varchar
100
no
no
parent
varchar
100
no
null
class
varchar
50
yes
null
alias
varchar
50
yes
null
agent
varchar
30
yes
null
label
varchar
100
yes
null
description
varchar
255
yes
null
class_scope
varchar
50
yes
null
metric_scope
varchar
100
yes
null
metric_help
varchar
1250
yes
null
created
integer
yes
null
created_by
varchar
50
yes
null
last_modified
integer
yes
null
last_modified_by
varchar
50
yes
null
Data Collections Tables

The database includes the following data collections tables:
collected_data
The collected_data table stores collected data for the data collection identified by
dcid.
Column Name
Type
Length
Nulls
Defaults
Seq
dcid
integer
no
no
sampletime
integer
no
no
sampleperiod
integer
no
no
qualifier
integer
no
no
samples
integer
yes
null
avgval
float
yes
null
minval
float
yes
null
maxval
float
yes
null
stddev
float
yes
null
copy_index
The copy_index table contains table names of the temporary imported data.
Column Name
Type
Length
Nulls
Defaults
Seq
copy_table
varchar
50
no
no
inserted
integer
yes
no
Database Tables
A5
data_collect_attrs
The data_collect_attrs table stores specific attribute values for the data collection
identified by dcid.
Column Name
Type
Length
Nulls
Defaults
Seq
dcid
integer
no
no
metric_name
varchar
100
no
no
attr_name
varchar
50
no
no
value
varchar
255
yes
null
data_collections
The data_collections table stores common attribute values for the data collection
identified by dcid.
Column Name
Type
Length
Nulls
Defaults
Seq
dcid
integer
no
no
metric_name
varchar
100
no
no
created
integer
yes
null
created_by
varchar
50
yes
null
last_modified
integer
yes
null
last_modified_by
varchar
50
yes
null
import_rules
The import_rules table stores import rules.
A6
Column Name
Type
Length
Nulls
Defaults
Seq
rule_name
varchar
100
no
no
import_rule
long
varchar
no
no
System Configuration Tables

The database includes the following system configuration tables:
smm_module_defs
The smm_module_defs table stores and defines possible system or application
specific parameters. The table smm_module identifies the system or
application, while attr_name identifies the specific parameter name.
Column Name
Type
Length
Nulls
Defaults
Seq
smm_module
varchar
50
no
no
attr_name
varchar
50
no
no
taborder
integer
yes
null
type
varchar
50
no
no
value
varchar
255
no
no
label
varchar
255
no
no
help
varchar
255
no
no
smm_module_values
The smm_module_values table stores and identifies possible values for specific
parameters.
Column Name
Type
Length
Nulls
Defaults
Seq
smm_module
varchar
50
no
no
attr_name
varchar
50
no
no
value
varchar
255
no
no
Database Tables
A7
smm_modules
The smm_modules table stores values to system or application specific
parameters.
Column Name
Type
Length
Nulls
Defaults
Seq
system_name
varchar
50
no
no
smm_module
varchar
50
no
no
attr_name
varchar
50
no
no
value
varchar
255
no
no
smm_sub_systems
The smm_sub_systems table stores status information for specific subsystems for
each system. Subsystem information can be disk, connection, process, and
system.
A8
Column Name
Type
Length
Nulls
Defaults
Seq
sub_system_name
varchar
100
no
no
system_name
varchar
100
no
no
description
varchar
255
yes
null
status
varchar
255
yes
null
statuspage
varchar
1023
yes
null
created
integer
yes
null
created_by
varchar
50
yes
null
last_modified
integer
yes
null
last_modified_by
varchar
50
yes
null
smm_systems
The smm_systems table stores and identifies systems.
Column Name
Type
Length
Nulls
Defaults
Seq
system_name
varchar
100
no
no
description
varchar
255
yes
null
created
integer
yes
null
created_by
varchar
50
yes
null
last_modified
integer
yes
null
last_modified_by
varchar
50
yes
null
snmp_config
The snmp_config table stores and identifies SNMP configuration information for
a specific target system.
Column Name
Type
Length
Nulls
Defaults
Seq
Target
varchar
50
no
no
community
varchar
50
no
no
retries
integer
no
no
timeout
integer
no
no
netmask
varchar
20
yes
null
Database Tables
A9
Report Tables
Report Tables
The database includes the following report tables:
business_hours
The business_hours table stores the business hours for each day of the week for a
report group identified by group_id.
Column Name
Type
Length
Nulls
Defaults
Seq
group_id
integer
no
no
day_name
varchar
15
no
no
start_time
integer
no
yes
end_time
integer
no
yes
created
integer
yes
null
created_by
varchar
255
yes
null
default_business_hours
The default_business_hours table stores default values for business hours for
each day of the week.
A10
Column Name
Type
Length
Nulls
Defaults
Seq
day_name
varchar
50
no
no
start_time
integer
no
no
end_time
integer
no
no
created
integer
yes
null
created_by
varchar
255
yes
null
Report Tables
export_reports
The export_reports table stores export specifications for a report job identified by
job_id.
Column Name
Type
Length
Nulls
Defaults
Seq
job_id
integer
no
no
name
varchar
50
no
no
value
varchar
255
no
no
profile_defs
The profile_defs table stores the available report profile attributes identified by
profile name, section, and attribute name. The type field identifies a user
interface element type that the user interface for this parameter will use.
Column Name
Type
Length
Nulls
Defaults
Seq
profile_name
varchar
50
no
no
section
varchar
50
no
no
attr_name
varchar
50
no
no
taborder
integer
yes
null
type
varchar
50
no
no
value
varchar
255
no
no
label
varchar
255
no
no
help
varchar
255
yes
null
Database Tables
A11
Report Tables
profile_values
The profile_values table defines possible values for a particular profile attribute.
Column Name
Type
Length
Nulls
Defaults
Seq
profile_name
varchar
50
no
no
section
varchar
50
no
no
attr_name
varchar
50
no
no
value
varchar
50
no
no
profiles
The profiles table stores report profile values for specific report profile attributes
identified by profile_name, section, and attr_name.
Column Name
Type
Length
Nulls
Defaults
Seq
profile_name
varchar
50
no
no
section
varchar
50
no
no
attr_name
varchar
50
no
no
value
varchar
255
no
no
report_commands
The report_commands table stores common specifications for a batch report. The
tables report_identifier and report_options store additional data.
A12
Column Name
Type
Length
Nulls
Defaults
Seq
job_id
integer
no
no
command
varchar
50
yes
null
report_title
varchar
255
no
no
class_scope
varchar
yes
null
metric_scope
varchar
100
yes
null
Report Tables
report_done
The report_done table contains the batch report log identifying the batch report
(job_id), its start and end time, the report period, and the URL to the report.
Column Name
Type
Length
Nulls
Defaults
Seq
job_id
integer
no
no
start_time
integer
yes
null
end_time
integer
yes
null
report_period
varchar
30
yes
null
error
varchar
50
yes
null
link
varchar
100
yes
null
report_group
The report_group table stores definitions for report groups identified by their
unique group_id. The tables report_group_members, report_group_parents, and
report_group_goals store additional data.
Column Name
Type
Length
Nulls
Defaults
Seq
group_id
integer
no
no
group_name
varchar
50
no
no
description
varchar
255
yes
null
created
integer
yes
null
created_by
varchar
50
yes
null
last_modified
integer
yes
null
last_modified_by
varchar
50
yes
null
Database Tables
A13
Report Tables
report_group_goals
The report_group_goals table stores the service goals associated with metric
instances assigned to report groups identified by group_id.
Column Name
Type
Length
Nulls
Defaults
Seq
group_id
integer
no
no
goal_name
varchar
100
no
no
value
varchar
255
yes
null
report_group_members
The report_group_members table stores and identifies the content of report
groups identified by group_id and dcid.
Column Name
Type
Length
Nulls
Defaults
Seq
group_id
integer
no
no
dcid
integer
no
no
report_group_parents
The report_group_parents table stores and identifies the parent report group for
report groups. If a report group has no parents, parent_id equals group_id.
A14
Column Name
Type
Length
Nulls
Defaults
Seq
group_id
integer
no
no
parent_id
integer
no
no
Report Tables
report_identifier
The report_identifier table stores and identifies the target report group or the
individual data collection assigned to a batch report job.
Column Name
Type
Length
Nulls
Defaults
Seq
job_id
integer
yes
null
dcid
integer
yes
-1
group_id
integer
yes
null
report_index
The report_index table keeps a history of all reports and their place in the report
repository.
Column Name
Type
Length
Nulls
Defaults
Seq
report_index
integer
no
null
group_id
integer
no
null
category
varchar
20
yes
null
cmd_id
varchar
50
yes
null
report_period
varchar
50
yes
null
report_title
varchar
255
yes
null
job_id
integer
yes
null
period_type
varchar
20
yes
null
url
varchar
20
yes
null
created
integer
yes
null
last_modified
integer
yes
null
status
varchar
20
yes
null
Database Tables
A15
Report Tables
report_options
The report_options table stores report options assigned to a batch report job.
Column Name
Type
Length
Nulls
Defaults
Seq
job_id
integer
no
no
name
varchar
50
no
no
value
varchar
50
no
no
report_time
The report_time table stores and identifies the time when individual batch
reports should be run. The time string is expressed as a UNIX cron value,
specifying five values, which identify minute, hour, day of month, month, and
day of week.
A16
Column Name
Type
Length
Nulls
Defaults
Seq
job_id
integer
no
no
time
varchar
20
no
no
period
varchar
10
no
no
period_type
varchar
no
no
Report Tables
service_goals
The service_goals table stores and defines service goals associated with service
goal labels (goal_name). A metric_reports definition identifies the value of the
goal_name field.
Column Name
Type
Length
Nulls
Defaults
Seq
goal_name
varchar
100
no
no
label
varchar
100
yes
null
tooltip
varchar
50
yes
null
description
varchar
255
yes
null
tab_order
integer
yes
null
type
varchar
20
no
no
required
integer
yes
null
editable
integer
yes
null
hidden
integer
yes
null
defaultval
varchar
255
yes
null
minval
varchar
255
yes
null
maxval
varchar
255
yes
null
report_function
varchar
50
yes
null
service_goalvalues
The service_goalvalues table stores and identifies possible values for service
goals identified by goal_name.
Column Name
Type
Length
Nulls
Defaults
Seq
goal_name
varchar
100
no
no
value
varchar
50
no
no
Database Tables
A17
Report Tables
service_incident_victims
The service_incident_victims table stores and identifies the data collections
assigned to a service incident (siid). The data collections are referenced by dcid.
Column Name
Type
Length
Nulls
Defaults
Seq
siid
integer
no
no
dcid
integer
no
no
service_incidents
The service_incidents table stores and defines service incidents identified by a
unique service incident id (siid). The incident is bounded in time by its
start_time and stop_time and is assigned a specific category. Category classifies
the incident as either provider responsible or not.
A18
Column Name
Type
Length
Nulls
Defaults
Seq
siid
integer
no
no
description
varchar
255
no
no
start_time
integer
no
stop_time
integer
no
created
integer
yes
null
created_by
varchar
50
yes
null
last_modified
integer
yes
null
last_modified_by
varchar
50
yes
null
category
varchar
10
yes
null
Appendix
Command Reference
createDb
The createDb command creates the database tables.
Advantage Ingres
You must run the Advantage Ingres utility createdb to create the database prior
to running the createDb command.
createDb reads its configuration from SLM_Install_Path/etc/smmrc.env and
SLM_Install_Path/etc/smmdb.cfg.
The following tasks are executed on Advantage Ingres and MS SQL:
Database
Action
Advantage Ingres
Creates the database tables.
MS SQL
Creates the database, the ODBC entry for the database,

and the database tables.
Ensures that AUTO_SHRINK is enabled.
Syntax
createDb
Command Reference
B1
deleteData
deleteData
The deleteData command deletes all records associated with dcid from the
database table collected_data. deleteData does not delete the definition of the
data collection.
Syntax
deleteData dcid [dcid .]
Options
groupID
Specifies the data collection ID.
deleteDataCollection
The deleteDataCollection command deletes all records associated with dcid from
the following database tables:
data_collections
data_collect_attrs
collected_data
report_identifier
deleteDataCollection deletes the data collection definition and all associated

data.
Syntax
deleteDataCollection dcid [dcid .]
Options
dcid
B2
deleteMetrics
deleteMetrics
The deleteMetrics command deletes one or more metrics and any instances of
this metric and associated collected data from the following database tables:
data_collections
data_collect_attrs
collected_data
metrics
metric_fields
metric_field_values
metric_reports
deleteMetrics deletes the metrics from the database and deletes any instances
and associated data from the system.
Syntax
deleteMetrics key
Options
key Specifies a metric name or part of a metric name along with SQL pattern
matching characters.
Example
To delete any metric starting with IP-, enter the following command:
deleteMetrics IP-%
dropDb
The dropDb command destroys the database.
MS SQL
This comman removes the ODBC entry.
Syntax
dropDb
Command Reference
B3
installData
installData
The installData command provides a way to install remotely collected data on
command. The installData command uploads this data into SLM_Install_Path.
Syntax
installData d
Options
-d Enables debug information.
lsMetrics
The lsMetrics command lists defined metrics and metric instances in the
database.
Syntax
lsMetrics [-a] [-l | -L] metric_name ...
Options
-a Shows metric attributes and default values.

-1 Lists metric instances for the selected metrics.
-L Lists metric instances and their attributes for the selected metrics.
metric_name
Identifies the metrics to use with this command.
Note: Without any options, lsMetrics lists all defined metric names.
Example 1
To list all metric attributes and default values for the ipnet metric, enter the
following command:
# lsMetrics a ipnet
The following list appears:

ipnet
---------------------------------------------------Common attributes:
--------------------------------------------------agent
: pathagent
class
: path
class_scope
: path
description
: IP network delay and availability
metric_scope
: ipnet
parent
: IP_Network
Report attributes:
--------------------------------------------------report_name
: IP network availability
report_function
: availability
goal_name
: ip-network-availability
unit
: %
goal_label
: IP network availability (%)
goal_value
: 99.5
orientation
: 2
report_name
: IP network delay
B4
lsMetrics
report_function
: real
goal_name
: ip-network-delay
unit
: msec
goal_label
: IP network delay (msec)
goal_value
: 200
orientation
: 2
report_name
: IP network downtime
report_function
: downtime
goal_name
: ip-network-downtime
unit
: incidents
goal_label
: IP network downtime (min)
goal_value
: 0
orientation
: 0
Collect attributes:
--------------------------------------------------adminStatus
: 0
agenthost
: $agent
checkAll
: False
checkUptime
: False
dataDb
: default
dataDir
: $SMM/databases/collect
description
:
deviceType
: any
endnode
:
importance
: Warning
interval
: 10
logAddress
: Undefined
pktsize
: 64
selectionName
: Undefined
startnode
: $agent
status
: 0000ff
statusChanged
: 0
vendorName
: any
Import attributes:
---------------------------------------------------
Example 2
To list specific details for import metrics, enter the following command:
lsMetrics a _ImportMetric_Keynote

_ImportMetric_Keynote
---------------------------------------------------Common attributes:
--------------------------------------------------agent
: createImport
class
: folder
class_scope
: none
description
: Keynote Data Import
metric_scope
: none
parent
: Import
Report attributes:
--------------------------------------------------Collect attributes:
--------------------------------------------------adminStatus
: 0
agenthost
: $agent
backup
: $SMM/import/_ImportMetric_Keynote
dataDir
handler
: slmImport
importFilter
: .*
importRule
: _ImportMetric_Keynote_0
_ImportMetric_Keynote_1
interval
: 1
Command Reference
B5
lsMetrics
package
: SLM_import
selectionName
: Undefined
source
: $SMM/incoming/_ImportMetric_Keynote
status
: 00ff00
statusChanged
: 0
Import attributes:
--------------------------------------------------Import rule '_ImportMetric_Keynote_0':
fileSeparator
:
commentIndicatorStart
:
commentIndicatorEnd
:
fieldSeparator
: |
metricName
: keynote_total
metricLabel
: keynote_total
class
: path
metricReports
: real {{Service response time} {msec}
service_response_time 2000 2} availability {{Service availability} {%}
service_availability 99.5 2} downtime {{Service downtime} {incidents}
service_downtime 0 0}
selectionName
: {keynote_total}:$agent:{$column(0) }:{}
metricInstanceLabel
: {keynote_total}:$agent:{$column(0) }:{}
target
: $column(0)
sampleTime
: $column(1)
sampleValue
: $column(2)
valueMethod
: Service availability & response time
data
Import rule '_ImportMetric_Keynote_1':
fileSeparator
:
commentIndicatorStart
:
commentIndicatorEnd
:
fieldSeparator
: |
metricName
: keynote_dns
metricLabel
: keynote_dns
class
: path
metricReports
: real {{Service response time} {msec}
service_response_time 2000 2}
selectionName
: {keynote_dns}:$agent:{$column(0) }:{}
metricInstanceLabel
: {keynote_dns}:$agent:{$column(0) }:{}
target
: $column(0)
sampleTime
: $column(1)
sampleValue
: $column(4)
valueMethod
: Service performance data
B6
lsMetrics
Example 3
To list all metric instances based on the metric ipnet, enter the following
command:
# lsMetrics l ipnet
Note: Unicenter SLM lists each instance with its data collection ID (dcid).
ipnet
Instances: 2 643 644 646 647
Example 4
To list the details of all metric instances based on the ipnet metric, enter the
following command:
# lsMetrics L ipnet

ipnet
Instances:
--------------------------------------------------2
adminStatus
: 0
agenthost
: nwosgp0q
agentname
: pathagent
checkAll
: False
checkUptime
: False
class
: path
dataDb
: default
dataDir
description
: ipnet: nwosgp0q -> 130.119.16.17
deviceType
: any
endnode
: 130.119.16.17
importance
: Warning
interval
: 10
logAddress
: Undefined
pktsize
: 64
save_data_collection
: Save
selectionName
: Undefined
startnode
: nwosgp0q
status
: 00ff00
statusChanged
: 0
vendorName
: any
--------------------------------------------------643
adminStatus
: 0
agenthost
: nwosgxab
Command Reference
B7
lsReportGroups
lsReportGroups
The lsReportGroups command lists the group ID and name for one or more
report groups.
Syntax
lsReportGroups groupID ...
Options
groupID
Specifies the report group ID.
mkIndex
The mkIndex command builds and updates the libraries. You must run this
command whenever new library commands are added or moved in the
SLM_Install_Path/lib/smm directory structure.
Syntax
mkIndex
runReport
The runReport command builds a report command specification associated with
the jobId from the database. To execute this command specification, use the
smmReporter command, which produces the report, inserts it into the report
repository, and, if configured, exports the report to a remote server.
Syntax
RunReport jobID
Options
jobID
Specifies the job ID of a scheduled command specification previously
entered into the database.
B8
showDcid
showDcid
The showDcid command displays the metric name and label for one or more
data collections.
Syntax
showDcid dcid [dcid ]
Options
dcid
slmCopyBatchReports
The slmCopyBatchReports command copies a batch report setup assigned to one
report group to another.
Syntax
slmCopyBatchReports sourceID targetID [targetID, ]
Options
sourceID
Specifies the source report group ID from which to copy the batch report
setup.
targetID
Specifies the target report group IDs to which the copied batch report setup
is applied.
Command Reference
B9
slmLoadColl
slmLoadColl
The slmLoadCollcommand creates and updates data collections from a specified
input file.
Syntax
slmLoadColl [-h] [-d] [-t] [-l log] file [file ...]
Options
-h Show shelp and exit.

-d Enables debug information.
-t
Runs in test mode; no database updates.
-l log
Specifies that debug information should be written to a log file, specified by
log.
file
Specifies the input file containing required metric instance attributes. Each
line describes one data collection, containing name/value pairs for metric
attributes. You must include attributes that do not have a default value
specified in the metric definition. You can specify the value reportGroup
with a report group name (full path) to automatically add the data collection
to an existing report group.
If the attribute selectionName is specified, the program checks if the data
collection already exists in the database. If collection exists, the data
collection is updated with the specified metric attributes.
If no selectionName attribute is specified, an attribute is defined based on
the following metric attributes joined by a colon (:).
metric_name
agenthost
startnode
endnode
If available, the following attributes are also used:
instance
url
query
If these attributes are not sufficient to uniquely identify a metric instance,

you should compose and supply an explicit selectionName.
B10
slmLoadGroup
slmLoadGroup
The slmLoadGroup command creates and updates report groups from a
specified input file.
Syntax
slmLoadGroup [-h] [-d] [-t] [-l log] file [file ...]
Options
-h Shows help and exit

-d
Enables debug info
-t
Runs in test mode; no database updates
-l log
Specifies that debug information should be written to a log file, specified by
log.
file
Specifies an input file, containing required report group instance attributes.
Each line describes one report group, containing name/value pairs for report
group attributes. The following examples show possible input file content:
group_name Network description {This is the Network group} monday_start 00:00
monday_end 24:00 tuesday_start 00:00 tuesday_end 24:00 wednesday_start 00:00
wednesday_end 24:00 thursday_start 00:00 thursday_end 24:00 friday_start 00:00
friday_end 24:00 saturday_start 00:00 saturday_end 24:00 sunday_start 00:00
sunday_end 24:00
group_name /Network/West description {This is the West group} monday_start
00:00 monday_end 24:00 tuesday_start 00:00 tuesday_end 24:00 wednesday_start
00:00 wednesday_end 24:00 thursday_start 00:00 thursday_end 24:00 friday_start
00:00 friday_end 24:00 saturday_start 00:00 saturday_end 24:00 sunday_start
00:00 sunday_end 24:00
Command Reference
B11
smmBuild
smmBuild
The smmBuild command reads and parses the database model configuration file
smmdb.cfg and loads this information into the database.
Note: You should run the smmSetup command before you run smmBuild.
Syntax
smmBuild -all | -metrics [metric_name ]| -reports | -business_hours | \

-service_goals -systems | -smmconfig configuration_file]
Options
-all Build everything (metrics, reports, business_hours, service_goals, systems).

-metrics [metric_name]
Build all metrics or the specified metrics.
-reports
Build report functions.
-business_hours
Build default business hours.
-service_goals
Build default service goals.
-systems
Build SMM systems.
-smmconfig configuration_file
Build the configuration file.
Note: You must run smmBuild with an option.
B12
smmCheck
smmCheck
The smmCheck command identifies the local system resource status and the
status of each data collection exercised on the local system. The smmCheck
command loads this information into the database, which in turn is displayed in
the user interface. The smmCheck command is normally run from cron every 15
minutes.
The smmCheck command identifies the following local system resources:
System load
Disk utilization
Running processes
Syntax
smmCheck [-d]
Options
-d Displays the findings.

Note: Without an option, the smmCheck command runs without any output.
Command Reference
B13
smmCollect
smmCollect
The smmCollect command collects, measures, and imports multiple types of
data. The collector supports the following types:
SNMP data collection
ICMP data collection
Service measurements and testing
Unicenter TNG Common Object Repository data collection
Import of CA Performance Cubes
Import of CA SuperPing data
Import of CA WMO response data
Syntax
smmCollect [-d| -D ][-shutdown |-sd]
Options
-d Causes the collector to run in the foreground and writes some logging
output.
-D Causes the collector to run in the foreground and writes more logging
output.
-shutdown (-sd)
Shuts down a currently running smmCollect daemon.
Notes:
B14
1.
You can enable logging in individual sub-agents/modules in smmCollect by

adding log specifications in the SLM_Install_Path/etc/smm.cfg file in the
environment section.
2.
Without an option, smmCollect runs in the background as a daemon process

(or service on Windows) and writes logging information to the file
SLM_Install_Path/var/log/smmCollect.log.
smmdbd
smmdbd
The smmdbd command loads the data from the import facility. The import
facility stores the data in temporary tables named smmdb_random_number. The
table copy_index contains a list of these tables. The smmdbd service polls the
copy_index table and copies the content of the temporary tables into permanent
storage in the collected_data table.
Syntax
smmdbd [-d | -D ][-shutdown |-sd]
Options
-d (-D)
Causes smmdbd to run in the foreground and writes some logging output.
-shutdown (-sd)
Shuts down a currently running smmdbd daemon.
Note: Without an option, smmdbd runs as a background daemon process and
logs its actions to SLM_Install_Path/var/log/smmdbd.log.
Command Reference
B15
smmDataImport
smmDataImport
The smmDataImport command reads and parses ASCII files containing collected
or measured data into the database. Each record must contain data associated
with a single sampled value. The file can contain multiple data collection
instances, as long as it is possible to uniquely identify each.
The program arguments control how a file is read and parsed. To successfully
import, you must provide the following information:
Field
Description
Sample Time
Identifies the time and date Unicenter SLM

performed the data collection.
Sample Interval (optional)
Identifies the sampling interval for a data collection

instance. This interval can be static, dynamic, or
nonexistent.
Data Collection ID
Identifies a unique ID or method to apply to find or

define a unique id for each data collection.
Sampled Value
Identifies the sampled value.
Syntax
smmDataImport h|-help|-d|-rs char|-fs char|-st p1,p2,|-sp p1,p2,|-s1 sec|-q

p1|-Q qualifier|-if dcid|-im method|-is p1,p2,| -v p1,p2,|-vo method|-mn
metric_name|-ms p1,p2,|-mm method|-ma attr_name_value attr_name_value
Options
-h | -help
Displays help message.
-d Enables debug.
-rs char
Identifies a record separator (default \n (newline)).
-fs char
Identifies a field separator (default (space)).
-st p1,p2,
Identifies a position for the sample time column. If sampleTime is an
integer, Unicenter SLM interprets it as a UNIX time. Otherwise Unicenter
SLM evaluates it as a valid date/time format as accepted by the TCL clock
command.
-sp p1,p2,
Identifies a position of the sample period (interval) column.
B16
smmDataImport
-s1 sec
Identifies the number of seconds for the upper limit on a rate of change to
compute the sample period based on two consecutive samples. If you do not
specify sl instead of sp, Unicenter SLM dynamically calculates the sample
time between consecutive samples.
-q p1
Identifies the position of the qualifier column.
-Q qualifier
Identifies the fixed qualifier to use with all data.
-if dcid
Sets the data collection ID. Unicenter SLM assigns this fixed data collection
ID to all records in the file.
Note: You can only specify one option from if, -im, and is.
-im method
Identifies the TCL parse method that extracts the data collection ID from the
file name. Unicenter SLM assigns this data collection ID to all records in the
file.
-is p1,p2,
Identifies the columns used as selection name. Unicenter SLM uses selection
name to lookup a possible existing data collection ID from the database. If
no ids match, Unicenter SLM creates a new data collection with this selection
name. You must select this option when the input file contains multiple data
collection instances.
-v p1,p2,
Identifies the column position for the sampled value.
-vo method
Identifies the TCL parse method to override the sampled value. You can
use this option when there are conditions where the sampled value should
be substituted. For example, if the data contains a status column and the
value in this column defines whether the sample value is valid, the method
must return the value to use.
-mn metric_name
Identifies the metric name to use for all data collection in the file. The file
can only contain a single data collection instance.
-ms p1,p2,
Identifies the column to use to compose a metric name for data collections in
the file. The file can contain multiple data collection instances.
Command Reference
B17
smmReduceData
-mm method
Identifies the TCL procedure to complete the array metric with necessary
attributes base on the syntax and semantics of the file name or record fields.
You use this method to dynamically define new metrics.
-ma attr_name_value attr_name_value
Defines values for metric attributes when creating new data collection
instances. The value can be absolute or can define a TCL method to extract
specific fields from a data collection record. For example, the following
command assigns the value of field 1 to the attr_name startnode and 10 to
the attr_name interval.
-ma 'startnode {[lindex $record 1]} interval 10'
All arguments are optional. If you specify no arguments, Unicenter SLM

assumes the following:
Record separator: Newline ("\n").
Field separator: Space (" ").
The input filename contains the data collection ID (dcid).
Column 1 contains sample time as UNIX time.
Column 2 contains sample period as seconds.
Column 3 contains an integer as a qualifier value.
Column 4 contains a value (float or integer).
smmReduceData
The smmReduceData command removes all data collections marked for
deletion, removing the data collection instance and any collected data associated
with this instance. The smmReduceData command also reduces the
collected_data table according to a predefined policy. This policy specifies what
data and how to reduce that data.
Note: Typically, you run smmReduceData from the smmdb_maintenance
program. For more information, see the command smmdb_maintenance.
Syntax
smmReduceData [-d]
Options
-d Displays information about the data to be reduced.

Note: Without this option, smmReduceData runs without any output.
B18
smmReportIndex
smmReportIndex
The smmReportIndex command builds the report index files in the report
repository based on information stored and maintained in the database.
Syntax
smmReportIndex
smmReportd
The report daemon schedules and runs reports in the background as instructed.
Syntax
smmReportd [-d| -D][-shutdown |-sd]
Options
-d Causes smmReportd to run in the foreground and writes some logging

output.
-D Causes smmReportd to run in the foreground and writes more logging
output.
-shutdown (-sd)
Shuts down a currently running smmdbd daemon.
Note: Without an option, smmReportd runs as a background daemon process
writes logging information to SLM_Install_Path/var/log/smmdbd.log.
smmReporter
The smmReporter command creates reports and updates the report index
maintained in the database. You typically run this command to create reports in
batch, but also to rerun an existing report. The smmReporter also exports reports
to remote web servers. Quality control is provided in this process, which detects
if a report violates predefined service goals or is missing data. If this is true, you
can suppress a report export.
Syntax
smmReporter [-d] [-j jobID] [-t "report_title"] -s class_scope -S metric_scope

[-H "report_header"][-r report_path][-p period][-P profile]c command| -C groupID
Options
-d Report runs on demand. Using d does not run the report, but it removes
the existing report and updates the report_index table.
- j jobID
The job id references report options stored in the database.
-t report_title
Provides the report title enclosed in quotes.
Command Reference
B19
smmReporter
-s class_scope
Limits which data collections to include in the report. Valid values are node,
link, and path. This parameter is mandatory.
-S metric_scope
Limits which data collections to include in the report. Valid values are any
word. This parameter is mandatory.
Note: To be of value, this parameter should contain part of or a complete
metric name for the metric name of the data collections to be included in the
report.
-H "report_header"
Specifies the text to use for the report heading.
-r report_path
Specifies the full path to the report category to use when storing the report
into the report repository. If you do not specify this parameter, Unicenter
SLM uses defaultCategory.
- p period
Specifies the report period, which defines the start and stop date for
Unicenter SLM to include collected data in the report.
-P profile
Specifies which report profile to use when creating the report. A report
profile contains runtime options for the report engine.
-c command
Specifies the report function and options to use when creating a report.
Unicenter SLM passes the content of the command argument to the report
engine. This parameter is mandatory.
- C groupID
Specifies the report group ID to use when creating the report.
B20
smmSetup
smmSetup
The smmSetup command reads two configuration files
(SLM_Install_Path/etc/smm.cfg and SLM_Install_Path/etc/smmdb.cfg.template)
and creates localized versions in SLM_Install_Path/etc/smmrc.env and
SLM_Install_Path/etc/smmdb.cfg respectively.
This command formats the content of smm.cfg into a runtime version of this file
in the smmrc.env file and SLM_Install_Path/html/java/smmrc.env. The
command overwrites the content of the smmrc.env files.
You must run the smmSetup command each time you modify
SLM_Install_Path/etc/smm.cfg and SLM_Install_Path/etc/smmdb.cfg.template.
This command formats the content of smm.cfg into a runtime version of this file
in the smmrc.env file and SLM_Install_Path/html/java/smmrc.env. The
command overwrites the content of the smmrc.env files.
Syntax
smmSetup
smmdb_maintenance
The smmdb_maintenance command is a database maintenance script that calls
the smmReduceData program to clean up and reduce collected data.
Advantage Ingres
This script also runs commands to de-fragment the database, release unused
space, and optimize Advantage Ingres database performance. Some parts of the
Advantage Ingres maintenance process require exclusive access to the database.
During this period the smmCollect and smmReportd daemons are shut down
and later restarted.
By default the smmdb_maintenance script runs each night from the cron utility.
Syntax
smmdb_maintenance
Command Reference
B21
smmstart
smmstart
The smmstart command starts the Unicenter SLM services (smmCollect,
SmmReportd, and smmdbd).
smmstart
Syntax
smmstop
The smmstop command stops the Unicenter SLM services (smmCollect,
smmReportd, and smmdbd).
Syntax
B22
smmstop
Appendix
Metric Syntax
Unicenter SLM metrics must define the following set of properties:
Property
Definition
Common attributes
Identifies common attributes for any metric.
Collect attributes
Identifies attributes and methods to configure a data

collect instance to measure, collect, or import the raw
data provided by the metric type.
Report attributes
Identifies attributes and methods to use when utilizing a

metric instance in a report process.
Metric Definitions
The metric definition must be wrapped inside the following statement in the
ASCII file:
array set metrics {
<your metric definition>
}
Service Goal Definitions

When you define a new metric you must create the definition of the new metric
and possibly the definition of a new service goal. A new service goal definition is
needed if none of the existing service goal definitions are applicable.
Your new service goal definition must be wrapped inside the following
statement in your ASCII file:
your new service goal
}
Multiple metrics and service goals can be defined inside these wrappers.
Metric Syntax
C1
Metric Definitions
Folder Properties
Each folder metric definition must identify the following properties:
Property
Description
metric name
Identifies a unique name assigned to the metric.
parent
Identifies the parent folder name where this folder metric

should be available in the status tree. The value . specifies
that the metric should be present at the root level in the
metric list. Any other value must reference an existing
metric folder.
class
Identifies the type of metric definition. The value for this

property is folder.
description
Identifies a descriptive label, used in the user interface.
Data Collection Properties

Each data collection metric definition must identify the following properties:
metric name
Identifies a unique name assigned to the metric.
parent
Identifies the folder name where this metric should be available in the status
tree. The value . specifies that the metric should be present at the root level in
the metric list. Any other value must reference an existing metric folder.
class
Identifies the type of metric definition. Valid values for this property include
the following:
link
Used for data collections associated with network interfaces, such as
collecting bandwidth utilization on a network interface.
node
Used for data collections where a single node is involved, with no specific
relation to other systems such as measuring CPU utilization or number of
users logged in on a server.
path
Used for data collections performing service response time and availability
measurements that include both a target system and a reference system such
as measuring web service response time and availability from a specific
server.
C2
Metric Definitions
agent
Identifies a collect program to perform the data collection. Valid values for this
property include the following:
snmpCollect
Used for any SNMP data collection.
pathagent
Used for IP network delay and availability data collection.
appagent
Used for system/service response time, and availability data collection.
coreimport
Used for data collections based on a Unicenter Common Object Repository
database.
createImport
Used for external data import.
smmImport
Used for imported data collections.
label
Identifies a general context label, used for data collections based on this metric
in reports.
description
Identifies a descriptive label, used in the user interface.
class_scope
Identifies how to filter metrics that may be included in report types defined for
this metric, based on class. Valid values include link, node, path, or none. None
specifies that no filtering is assigned.
metric_scope
Identifies how to filter the metrics that may be included in report types defined
for this metric, based on metric name. Valid values include none, part of the
name, or the complete metric name. None specifies that no filtering is assigned.
Metric Syntax
C3
Metric Definitions
metric_reports
Defines report types for the metric. Valid values include a name and a value
definition as follows:
name
Identifies a specific report function, real, availability, or downtime.
value
Identifies the report type label, report type unit, and report type service goal
tag. Multiword values must be enclosed inside curly brackets ({ }).
Note: Report type service goal tag associates the report type with a service goal
definition in the service_goals table.
The following example defines three report types based on the report functions
availability, real, and downtime. The report labels include IP network
availability, IP network delay, and IP network down time. The units to be
used by the report types are %, msec, and incidents. The service goal tags
are listed in the last fields.
metric_reports {
availability {{IP network availability} % ip-network-availability}
real
{{IP network delay} msec ip-network-delay}
downtime {{IP network down time} incidents ip-network-downtime}
}
Note: If another metric definition defines a report type with exactly the same
label, but with a different class and metric scope, two identical labels are listed in
the report type list in the user interface, but with different context.
Metric Fields
Metric fields (or attributes) consist of an attribute name and a multipart value
definition. The attribute name must be unique within the metric definition. The
agent program specifies attribute names, as they are used and referenced within
the agent program.
Some attributes can be assigned default values, referenced as a variable,
including the variable agent. This variable is replaced with the collect system
host name when an instance of this metric is created.
Note: These variables must be escaped when assigned using \$agent.
The multipart value assigns a possible default value to an attribute and, at the
same time, specifies the configuration dialog in the user interface. The value in a
metric attribute definition always consists of five elements. Any element
containing multiple words must be enclosed in curly brackets ({}).
C4
Metric Definitions
Metric Fields
Metric fields include the following parts:
User interface label
Identifies the label used in the configuration dialog in the user interface.
User interface type
Identifies the type of input/select field where a value can be specified for this
attribute. Valid types include hidden, entry, select, radio, and check. Hidden
types are not seen in the user interface and are suitable for attributes with a
predefined and constant value.
List of possible values
When the user interface type is select, this field lists possible values for the list.
If not used, this field value is curly brackets ({}).
Property
Specifies the degree of importance of the metric field. This field can be used to
decide whether this metric field has to be specified or not. This field is typically
used when many data collections are imported and some fields can be applied
to many data collections, but others need to be specified individually.
Valid values for this field include the following:
default
Specifies a default value is specified and used, but only for one data
collection.
default_common
Specifies a default value is specified and can be used for more than one data
collection of the metric type.
required
Specifies that no default value is specified or default value is set to
undefined.
required_common
Specifies that no default value is specified or default value is set to undefined
for more than one data collection.
optional
Indicates this value is optional.
optional_common
Indicates this value is optional, and can be modified for more than one data
collection.
Default value
Specifies the default value of the metric.
Metric Syntax
C5
Mandatory Metric Properties

agenthost
Identifies the host name of the agent system. Default value is \$agent.
startnode
This attribute currently has different meanings for link, node, and path class
metrics. For link and node class metrics, this identifies the host name of the
target system for the data collection. For these metrics, there is no default value
for this attribute. For path class metrics, this identifies a reference system,
where the data collection/service measurement is performed. Default value is
\$agent. This property is not required for folder metrics.
description
Assigns a label for the data collection, to be used in reports.
interval
Identifies the sampling interval for the data collection. If the sampling interval
is irrelevant, the value 0 (null) must be assigned as a default value.
adminStatus
Defines the administrative status of the data collection. The user maintains this
status. Default value is normal.
status
Identifies the operational status of the data collection, which is maintained by

the collector. Initial (default) value is Undefined (value 0000ff).
dataDir
Defines the full path for the directory on which data collect files are stored
when collected on a remote SLM system. Default value is
$SMM/databases/collect (where $SMM equals the SLM install path
(SLM_Install_Path)).
dataDb
Defines the database vnode name, where the collected data is to be stored.
Currently only the value default is supported, which means that data will be
stored in the database running at the console. This property is not required for
folder metrics.
deviceType
Defines a particular device type associated with this metric. This attribute is
used for grouping related metrics. This property is not required for folder
metrics.
Valid values include the following:
unknown
No device type.
any
Applies to any type of device.
Any words that identify a particular device type this metric should be associated
with. Examples include router, host, and probe, and so on.
C6
vendorName
Define a particular vendor name associated with this metric. This attribute is
used for grouping related metrics. This property is not required for folder
metrics.
Valid values include the following:
unknown
No vendor name.
any
Applies to any vendor name.
Any words that identify a particular vendor name this metric should be
associated with. Examples include cai, cisco, linux, and so on.
selectionName
Defines a string that may be used by external programs or import programs to

reference and identify a data collection. This property is not required for folder
metrics.
Mandatory Metric Fields for pathagent and appagent

endnode
Identifies the host name of the target system. There is no default value for this
attribute.
Mandatory Metric Fields for snmpCollect

mibType
Defines a particular SNMP MIB type. Possible values are GAUGE, INTEGER,
COUNTER, and EXPRESSION. The first three are used for single value SNMP
MIB data collections, while the last is used with SNMP data collections
involving multiple SNMP MIB variables. GAUGE type MIB data collections
store the measured value, while the COUNTER and INTEGER type MIB data
collections store a rate of change value. For EXPRESSION type MIB data
collection, a collect method contains the rules for calculating and storing
collected data.
mibFile
Defines a list of MIB files to be loaded to resolve SNMP MIB variable labels and
types when creating an instance of this metric.
Metric Syntax
C7
Definitions of Available Metrics
mib
Defines an SNMP MIB variable for GAUGE, INTEGER, and COUNTER type
MIB data collections, or a list of values for EXPRESSION type MIB data
collections. The list must contain the name of a collect method as the first
element, followed by a list of SNMP MIB variables expected by the collect
method. An SNMP MIB variable can be specified as an Object Identifier (OID)
or by its label name. The latter requires that the label names be unique and that
the SNMP MIB defining the labels be loaded.
instance
Defines a particular SNMP MIB instance of the defined SNMP MIB variables.
An SNMP MIB instance value is always required.
instancekey
Defines a list of SNMP MIB variables that can be probed when testing the data
collection, and, at the same time, be used to help select and identify a correct
instance value.

The following sections describe metrics available with Unicenter SLM.
cai_cpuUtil: Windows NT Server CPU Utilization

This metric measures CPU utilization on a Windows NT Server running SNMP.
The target server must be running Unicenter agent for Window NT.
Operations
This metric has the following operations:

Save
Saves a new or modified import specification. The save operation only
updates the Unicenter SLM database. The collector performing the import
must be explicitly notified by a restart. To restart the collector from the
status tree, select the associated Unicenter SLM system and click Restart.
Test
Tests a data collection. The test specification is sent from the Unicenter SLM
console system to the collector system, which performs the test and returns
the results. The test queries the MIB variable ntStatusCPUTotal (Current total
utilization on the processor).
C8
Delete
Deletes an existing import job. This operation removes this metric instance
definition and any reference to it in the Unicenter SLM database. This
operation does not remove any collected data associated with imported data
collections. The collector performing the import job must be explicitly
notified by a restart, otherwise it continues importing data. To restart the
collector from the status tree, select the associated Unicenter SLM system and
click Restart. This operation is only available in modify mode.
Report
Accesses the Unicenter SLM interactive report interface for this data
collection. This operation is only available in modify mode.
Clear
Resets the configuration dialog.
Parameters
This metric has the following configurable parameters:

Target node
Identifies the host name or IP address of the target server. The user must
enter this parameter.
Label
Identifies a textual label for this data collection. Default value is cai_cpuUtil:
target node
Interval
Identifies the sampling interval for this data collection in minutes.
SNMP community
Identifies the SNMP community name used to query the SNMP agent at the
target node. The value default is the default SNMP community. The default
SNMP community name value is set in the configuration dialog accessible
from the Unicenter SLM menu Configuration, SNMP Configuration. Any
other value than default is used directly in SNMP queries to the target host.
SNMP agent port
Identifies the port number used by the remote agent.
Suspended
Suspends the import job until the next start of the Unicenter SLM collector
system.
Metric Syntax
C9
cai_cpuUxUtil: UNIX Server CPU Utilization

This metric measures CPU utilization on a UNIX Server running SNMP. The
target node must be running a UNIX agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is
cai_cpuUxUtil: target node
Interval
C10
SNMP community
SNMP agent port
Suspended
system.
cai_fileSysUsed: Percentage File System Space Used on a Volume

This metric measures percentage space used on a disk volume on a Windows NT
server. The target server must be running Unicenter agent for Window NT.
Operations

Save
If the MIB instance is undefined, this metric tries to query the table identified
by ntStatusFSDriveLabel that, if successful, lists available volume names and
associated MIB instance values. From this list you can select the MIB instance
to be collected. This is the easiest way to define this type of data collection,
unless you already know the MIB instance value.
Test
the results. The test queries the MIB variable ntStatusFSDriveLabel (The
drive label of the file system).
Delete
Metric Syntax
C11
Report
Click the Report to access the Unicenter SLM interactive report interface for
this data collection. This operation is only available in modify mode.
Clear
Parameters

Target node
Label
cai_fileSysUsed: target node
Interval
MIB Instance
Identifies a specific disk volume on the server.
SNMP agent port
Suspended
system.
cai_memoryUtil: NT Server Memory Utilization

This metric measures Windows NT server memory utilization using SNMP. The
target server must be running Unicenter agent for Window NT.
Operations

Save
C12
Test
the results. The test queries the MIB variable ntStatusMemLoad (Current
Memory Load, defined as a percentage).
Delete
Report
Clear
Parameters

Target node
Label
cai_memoryUtil: target node
Interval
SNMP community
SNMP agent port
Suspended
system.
Metric Syntax
C13
cai_memoryUxUtil: UNIX Server Memory Utilization

This metric measures UNIX server memory utilization using SNMP. The target
node must be running a UNIX agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
cai_memoryUxUtil: target node
Interval
C14
SNMP community
SNMP agent port
Suspended
system.
cai_ntAvailService: Windows NT Service Availability

This metric reports service availability for services running on a Windows NT
server. The target node must be running a Unicenter 2.x Windows NT System
agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters
Metric Syntax
C15
Target node
Label
cai_ntAvailService: target node
Interval
SNMP community
SNMP agent port
Suspended
system.
cai_swapUxUtil: UNIX Server Swap Utilization

This metric measures UNIX server swap utilization using SNMP. The target
node must be running a UNIX agent.
Operations

Save
Test
the results.
Delete
C16
Report
Clear
Parameters

Target node
Label
cai_swapUxUtil: target node
Interval
SNMP community
SNMP agent port
Suspended
system.
CA_MSEXCHANGE_DataBase_Status: MS Exchange Database Status

This metric reports the current database status on a MS Exchange server. The
target node must be running an Exchange agent.
Operations

Save
Test
the results.
Metric Syntax
C17
Delete
Report
Clear
Parameters

Target node
Label
CA_MSEXCHANGE_DataBase_Status: target node
Tip: Replace unknown with the current File System Queue Name by editing
the Label field, after you click Save. By doing so, every metric instance is
differentiated with a unique File Queue Name.
Interval
SNMP community
Suspended
system.
C18
CA_MSEXCHANGE_DISK_Status: MS Exchange Disk Status

This metric reports the current disk status on a MS Exchange server. The target
node must be running an Exchange agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_MSEXCHANGE_DISK_Status: target node
Tip: Replace unknown with the current Drive Name by editing the Label
field, after you click Save. By doing so, every metric instance will be
differentiated with a unique Drive/Disk Name.
Metric Syntax
C19
Interval
SNMP community
Suspended
system.
CA_MSEXCHANGE_MTA_Queue_Status: MS Exchange MTA Current Queue Status

This metric reports the current MTA queue status on a MS Exchange server. The
target node must be running an Exchange agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C20
Parameters

Target node
Label
CA_MSEXCHANGE_MTA_Queue_Status: target node
Tip: Replace unknown with the current MTA Queue Name by editing the
Label field, after you click Save. By doing so, every metric instance will be
differentiated with a unique Queue Name.
Interval
SNMP community
Suspended
system.
CA_MSEXCHANGE_MTA_Receive_Queue_Status: MS Exchange MTA Receive

Queue Status
This metric reports the current MTA receive queue status on a MS Exchange
server. The target node must be running an Exchange agent.
Operations

Save
Test
the results.
Metric Syntax
C21
Delete
Report
Clear
Parameters

Target node
Label
CA_MSEXCHANGE_MTA_Receive_Queue_Status: target node
Interval
SNMP community
Suspended
system.
C22
CA_MSEXCHANGE_MTA_Send_Queue_Status: MS Exchange MTA Send Queue

Status
This metric reports the current MTA send queue status on a MS Exchange server.
The target node must be running an Exchange agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_MSEXCHANGE_MTA_Send_Queue_Status: target node
Metric Syntax
C23
Interval
SNMP community
Suspended
system.
CA_NT4_cpu_Current_Processor_Util: Windows NT 4.0 Current CPU Utilization

This metric reports the current processor utilization as percentage value. The
target node must be running a Windows NT 4.0 System agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C24
Parameters

Target node
Label
CA_NT4_cpu_Current_Processor_Util: target node
Interval
SNMP community
Suspended
system.
CA_NT4_cpu_Total_Processors_Util: Windows NT 4.0 Total CPU Utilization

This metric reports the current total utilization of all processors as percentage
value. The target node must be running a Windows NT 4.0 System agent.
Operations

Save
Test
the results.
Delete
Metric Syntax
C25
Report
Clear
Parameters

Target node
Label
CA_NT4_cpu_Total_Processors_Util: target node
Interval
SNMP community
Suspended
system.
CA_NT4_MEMORY_Current_Paging_memory: Windows NT 4.0 Current Used

Paging Memory
This metric reports the size of the currently committed paging memory as
percentage value. The target node must be running a Windows NT 4.0 System
agent.
Operations

Save
C26
Test
the results.
Tip: The value returned by the Test procedure is the size of the currently
used paging memory in kilobytes. However the computed value stored in
the database and displayed in the reports is a percentage value, using Total
Paging Memory as a reference.
Delete
Report
Clear
Parameters

Target node
Label
CA_NT4_MEMORY_Current_Paging_memory: target node
Interval
SNMP community
Suspended
system.
Metric Syntax
C27
CA_NT4_MEMORY_Current_Physical_memory : Windows NT 4.0 Current Used

Physical Memory
This metric reports the size of the currently committed physical memory as
agent.
Operations

Save
Test
the results.
used physical memory in kilobytes. However the computed value stored in
Delete
Report
Clear
Parameters

Target node
C28
Label
CA_NT4_MEMORY_Current_Physical_memory: target node
Interval
SNMP community
Suspended
system.
CA_NT4_MEMORY_Current_Virtual_memory: Windows NT 4.0 Current Used Virtual

Memory
This metric reports the size of the currently committed virtual memory as
agent.
Operations

Save
Test
the results.
used virtual memory in kilobytes. However the computed value stored in
Metric Syntax
C29
Delete
Report
Clear
Parameters

Target node
Label
CA_NT4_MEMORY_Current_Virtual_memory: target node
Interval
SNMP community
Suspended
system.
C30
CA_NT4_NETWORK_Input_Packets_Status: Windows NT 4.0 Status of Received

Packets
This metric reports the current status of the received packets rate as determined
by the thresholds. The target node must be running a Windows NT 4.0 System
agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_NT4_NETWORK_Input_Packets_Status: target node
Interval
Metric Syntax
C31
SNMP community
Suspended
system.
CA_NT4_NETWORK_Output_Packets_Status: Windows NT 4.0 Status of Sent Packets

This metric reports the current status of the sent packets rate as determined by
the thresholds. The target node must be running a Windows NT 4.0 System
agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C32
Parameters

Target node
Label
CA_NT4_NETWORK_Output_Packets_Status: target node
Interval
SNMP community
Suspended
system.
CA_NT4_SERVICES_Service_Availability: Windows NT 4.0 Service Availability

This metric reports the service availability for services running on a Windows
NT 4.0 host. The target node must be running a Windows NT 4.0 System agent.
Operations

Save
Tip: You can populate the nt4StatusSrvcName table with available Windows
services using the Windows NT 4.0 System Agent View. For more
information, see the agent view online help system.
Test
the results.
Metric Syntax
C33
Delete
Report
Clear
Parameters

Target node
Label
CA_NT4_SERVICES_Service_Availability: target node
Tip: Replace the label entry unknown with the current Windows service
name to differentiate every metric instance with a unique service name.
Interval
SNMP community
Suspended
system.
C34
CA_PathDoctor: Import CA PathDoctor Ping Data

This metric initiates an import of CA PathDoctor ping data. This metric creates
an import job at the Unicenter SLM system to receive input data files from the
PathDoctor manager system. This metric does not have its own collected data or
any report capabilities. This metric uses the following directory for import:
SLM_Install_Path/incoming/CA_ping
Each PathDoctor manager must have a separate sub-directory in this directory,

and each is regularly scanned by the import job.
Operations

Save
Delete
Clear
Parameters

Scan interval
Identifies the interval at which the import job looks for new data to import.
Backup
Defines a directory where unmodified imported files are stored.
Suspended
system.
Metric Syntax
C35
CA_perfAgent: Import CA Performance Agent Data

This metric initiates an import of performance agent data. This metric creates an
import job at the Unicenter SLM system to receive performance cube data files,
converted to comma separated value (CSV) format. This metric does not have its
own collected data or any report capabilities. This metric uses the following
directory for import:
SLM_Install_Path/incoming/CA_perfAgent
Operations

Save
Delete
Clear
Parameters

Scan interval
Identifies the interval at which the import job looks for new data to import.
CSV Separator
Identifies the separator for the CSV files that are imported. Some Excel
versions use ; as a separator when converting from XLS to CSV.
Backup
Defines a directory where unmodified imported files are stored.
Suspended
system.
C36
CA_SAP_R3_GENERAL_Items: SAP R/3 Maintenance Items

This metric reports the total number of SAP R/3 maintenance items. The target
node must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_SAP_R3_GENERAL_Items: target node
Interval
Metric Syntax
C37
SNMP community
Suspended
system.
CA_SAP_R3_GENERAL_Status: SAP R/3 Status

This metric reports the service availability for current SAP R/3 systems. The
target node must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C38
Parameters

Target node
Label
CA_SAP_R3_GENERAL_Status: target node
Tip: Add the Instance name after the label entry InstanceName with the
current SAP agent instance to differentiate every metric instance with a
unique instance name.
Interval
SNMP community
Suspended
system.
CA_SAP_R3_Number_Dump_Daily: Number of SAP R/3 Short Dumps Today

This metric reports the number of SAP R/3 short dumps today. The target node
must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Metric Syntax
C39
Delete
Report
Clear
Parameters

Target node
Label
CA_SAP_R3_Number_Dump_Daily: target node
Interval
SNMP community
Suspended
system.
C40
CA_SAP_R3_Process_Status: Status of SAP R/3 Work Process

This metric reports the status of SAP R/3 work process. The target node must be
running a SAP R/3 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_SAP_R3_Process_Status: target node
Tip: Add the Instance name after the label entry Process Number to
differentiate every metric instance with a unique process number.
Interval
Metric Syntax
C41
SNMP community
Suspended
system.
CA_SAP_R3_Status_Dump_Daily: Status of SAP R/3 Short Dumps Today

This metric reports the status of SAP R/3 short dumps today. The target node
must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C42
Parameters

Target node
Label
CA_SAP_R3_Status_Dump_Daily: target node
Interval
SNMP community
Suspended
system.
CA_SAP_R3_UPDATES_Cancelled_Count: Number of SAP R/3 cancelled updates

This metric reports the number of SAP R/3 cancelled updates within poll
interval. The target node must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Tip: The poll interval is specified by the SAP R/3 agent configuration. For
more information about poll intervals, see Working with Agents.
Metric Syntax
C43
Delete
Report
Clear
Parameters

Target node
Label
CA_SAP_R3_UPDATES_Cancelled_Count: target node
Interval
SNMP community
Suspended
system.
C44
CA_SAP_R3_UPDATES_Cancelled_Status: SAP R/3 Status of Cancelled Updates

This metric reports the status of cancelled updates within poll interval. The target
node must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_SAP_R3_UPDATES_Cancelled_Status: target node
Interval
Metric Syntax
C45
SNMP community
Suspended
system.
CA_SAP_R3_UPDATES_Pending_Count: Number of SAP R/3 Pending Updates

This metric reports the number of SAP R/3 pending updates within poll interval.
The target node must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C46
Parameters

Target node
Label
CA_SAP_R3_UPDATES_Pending_Count: target node
Interval
SNMP community
Suspended
system.
CA_SAP_R3_UPDATES_Pending_Status: SAP R/3 Status of Pending Updates

This metric reports the status of SAP R/3 pending updates within poll interval.
The target node must be running a SAP R/3 agent.
Operations

Save
Test
the results.
Metric Syntax
C47
Delete
Report
Clear
Parameters

Target node
Label
CA_SAP_R3_UPDATES_Pending_Status: target node
Interval
SNMP community
Suspended
system.
C48
CA_W2K_cpu_Current_Processor_Util: Windows 2000 Current CPU Utilization

This metric reports the current processor utilization as a percentage. The target
node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_W2K_cpu_Current_Processor_Util: target node
Interval
Metric Syntax
C49
SNMP community
Suspended
system.
CA_W2K_cpu_Total_Processors_Util: Windows 2000 Total CPU Utilization

This metric reports the current total utilization of all processors as a percentage.
The target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
C50
Parameters

Target node
Label
CA_W2K_cpu_Total_Processor_Util: target node
Interval
SNMP community
Suspended
system.
CA_W2K_LOGICAL_VOLUMES_File_Fragmentation: Windows 2000 File

Fragmentation on a Volume
This metric reports the current file fragmentation on a volume as a percentage.
The target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Metric Syntax
C51
Delete
Report
Clear
Parameters

Target node
Label
CA_W2K_LOGICAL_VOLUMES_File_Fragmentation: target node
Interval
SNMP community
Suspended
system.
CA_W2K_LOGICAL_VOLUMES_fileSysUsed: Windows 2000 File System Space Used

on a Volume
This metric reports the current file system space used on a volume as a
percentage. The target node must be running a Windows 2000 agent.
C52
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_W2K_LOGICAL_VOLUMES_fileSysUsed: target node
Interval
SNMP community
Suspended
system.
Metric Syntax
C53
CA_W2K_MEMORY_Current_Paging_memory: Windows 2000 Current Used Paging

Memory
This metric reports the size of the currently committed paging memory as a
percentage. The target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
C54
Label
CA_W2K_MEMORY_Current_Paging_memory: target node
Interval
SNMP community
Suspended
system.
CA_W2K_MEMORY_Current_Physical_memory: Windows 2000 Current Used

Physical Memory
This metric reports the size of the currently committed physical memory. The
target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Metric Syntax
C55
Delete
Report
Clear
Parameters

Target node
Label
CA_W2K_MEMORY_Current_Physical_memory: target node
Interval
SNMP community
Suspended
system.
CA_W2K_MEMORY_Current_Virtual_memory: Windows 2000 Current Used Virtual

Memory
This metric reports the size of the currently committed virtual memory. The
target node must be running a Windows 2000 agent.
C56
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
CA_W2K_MEMORY_Current_Virtual_memory: target node
Interval
Metric Syntax
C57
SNMP community
Suspended
system.
CA_W2K_NETWORK_Input_Packets_Status: Windows 2000 Status of Received

Packets
This metric reports the current status of the received packets rate as determined
by the thresholds. The target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters
C58
Target node
Label
CA_W2K_NETWORK_Input_Packets_Status: target node
Interval
SNMP community
Suspended
system.
CA_W2K_NETWORK_Output_Packets_Status: Windows 2000 Status of Sent Packets

This metric reports the current status of the sent packets rate as determined by
the thresholds. The target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
Delete
Metric Syntax
C59
Report
Clear
Parameters

Target node
Label
CA_W2K_NETWORK_Output_Packets_Status: target node
Interval
SNMP community
Suspended
system.
CA_W2K_SERVICES_Service_Availability: Windows 2000 Service Availability

This metric reports the service availability for services running on a Windows
2000 host. The target node must be running a Windows 2000 agent.
Operations

Save
Test
the results.
C60
Tip: You can populate the w2kStatusSrvcName table with available

Windows services using the Windows 2000 System Agent View. For more
information, see the agent view online help system.
Delete
Report
Clear
Parameters

Target node
Label
CA_W2K_SERVICES_Service_Availability: target node
Tip: Replace the label entry unknown with the current Windows service
name to differentiate every metric instance with a unique service name.
Interval
SNMP community
Suspended
system.
Metric Syntax
C61
cisco_cpu5: Cisco Device CPU Utilization

This metric measures Cisco 5 minute exponentially decayed moving average of
the CPU busy percentage. The target node must be running a Unicenter Cisco
agent.
Operations

Save
Test
the results. The test queries the MIB variable avgBusy5 (5 minute
exponentially-decayed moving average of the CPU busy percentage).
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is cisco_cpu5:
target node
C62
Interval
SNMP community
Suspended
system.
dns: DNS Server Response Time and Availability

This metric measures DNS service response time and availability by querying a
target DNS name server.
Operations

Save
Test
the results. The test requires that the target host, query type, and query are
specified.
Delete
Report
Clear
Metric Syntax
C63
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is dns: target
node.
Interval
Query type
Identifies a specific query type to request based on the Query value.
address
Address lookup; Query is host name or IP address
hinfo
Query for host information; Query is host name or IP address
mx Query for mail exchange information; Query is domain name
name
Query IP address; Query is IP address
soa Query for SOA (Zone of Authority); Query is domain name, host name
or IP address
Query
Identifies the value to be queried.
Importance
Identifies a classification of the importance of this data collection as defined
on the Unicenter Service Level Management system. This information is only
carried in SNMP trap messages which are generated when the operational
status for this data collection change from up to down and from down to up.
The destination for the SNMP trap messages is specified by the Network
Management System parameter in the Collect system, System, Agent
configuration dialog. How the information is used depends on the SNMP
trap receiver.
Suspended
system.
C64
fr-util: Bandwidth Utilization Measured on a Frame Relay DLCI

This metric measures bandwidth utilization measured on a Frame Relay DLC.
Operations

Save
If the MIB instance is undefined, this metric tries to query the SNMP table
identified by frCircuitDlci, which if successful, lists available frame relay
circuits identified by their associated MIB instance values. The MIB instance
value includes two numbers; the first identifies the interface and the second
identifies the virtual circuit number (VC) for the frame circuit. Normally this
is identical to the VC number used by the frame relay network provider.
From this list you can select the MIB instance to be collected.
Test
console system to the collector system that performs the test and returns the
results. The test queries the specified MIB instance from the frCircuitDlci
table.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is fr-util: target
node.
Metric Syntax
C65
Interval
SNMP community
MIB instance
Identifies a specific frame relay circuit at the target node.
Speed
Defines the frame relay speed in bits/second. The frame relay circuit speed is
required to calculate bandwidth utilization on the circuit. Because you
cannot query the router using SNMP for the frame relay circuit speed, the
user must provide this information. You can either supply the CIR value or
the modem speed value. If you specify CIR speed, you may measure more
than 100% utilization.
Suspended
system.
C66
ftp: FTP Throughput and Availability

This metric measures FTP file transfer throughput and FTP service availability.
The target node must be running a FTP server.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is ftp: target
node.
Method
Identifies the direction of the file transfers; put uploads local file to the target
host as remote file, while get retrieves remote file from the target host as
local file. In a put operation the local file must exist at the Unicenter SLM
collector system. In a get operation the remote file must exist at the target
host.
Metric Syntax
C67
Interval
Timeout
Identifies the number of seconds to wait for this measurement/operation to
complete. If this timeout period is exceeded, the service is recorded as
unavailable.
Importance
Identifies the classification of the importance of this data collection as
defined on the Unicenter SLM system. This information is only carried in
SNMP trap messages which are generated when the operational status for
this data collection change from up to down and from down to up. The
destination for the SNMP trap messages is specified by the Network
trap receiver.
FTP user name
Identifies the user name defined at the target host.
FTP password
Identifies the password assigned to the user name at the target host.
Remote file
Identifies the remote file to be retrieved (get) or replaced (put) at the target
node. Use a full path name.
Local file
Identifies the local file to be uploaded (put) or replaced (get) at the Unicenter
Service Level Management collect system. Use a full path name.
Suspended
system.
ftp-ping: FTP Server Response Time and Availability

This metric measures FTP service availability and response time based on
connecting to the target FTP server. No file transfer is performed. The target
node must be running a FTP server.
Operations

Save
C68
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is ftp-ping:
target node.
Method
Identifies the direction of the file transfers; put uploads local file to the target
host as remote file, while get retrieves remote file from the target host as
local file. In a put operation the local file must exist at the Unicenter SLM
collector system. In a get operation the remote file must exist at the target
host.
Interval
Timeout
unavailable.
Metric Syntax
C69
Importance
trap receiver.
Suspended
system.
hpux-fileSysUsed: Percent File System Space Used on a HP-UX MIB System

This metric measures file system space used on an HP-UX system. The target
node must be running a SNMP agent supporting the HP-UX MIB.
Operations

Save
If the MIB instance is undefined, this metric tries to query the SNMP table
identified by fileSystemName in the HP-UX MIB, which if successful, lists
available disk partitions identified by their associated MIB instance values.
From this list you can select the MIB instance to be collected.
Test
results. The test queries the specified instance in the fileSystemName table.
Delete
Report
C70
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is hpuxfileSysUsed: target node.
Interval
SNMP community
MIB instance
Suspended
system.
hr_fileSysUsed: Percent File System Space Used on the Host MIB System
This metric measures percentage space used on a disk volume on a system. The
target node must be running an SNMP agent supporting the host MIB.
Operations

Save
Test
the results.
Metric Syntax
C71
Delete
Report
Clear
Parameters

Target node
Label
hr_fileSysUsed: target node
Interval
SNMP community
MIB instance
Identifies a specific disk volume at the target node.
Suspended
system.
hr_systemNumUsers: Number of Users on a Host MIB System

This metric measures the number of logged in users on a system supporting the
host MIB.
C72
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
hr_systemNumUsers: target node
Interval
SNMP community
Suspended
system.
Metric Syntax
C73
http: HTTP Server Response Time and Availability

This metric measures web server response time and availability based on
requesting a specific web page from the server. The target node must be running
a web server.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is http: target
node.
Interval
C74
Importance
Identifies a classification of the importance of this data collection as defined
on the Unicenter Service Level Management system. This information is only
carried in SNMP trap messages which are generated when the operational
status for this data collection change from up to down and from down to up.
The destination for the SNMP trap messages is specified by the Network
trap receiver.
URL
Identifies the web page to request from the target node. The URL must only
include the part following the host name and port number specification in a
fully specified URL.
Port
Identifies the port number to use to access the web server.
Proxy server
Identifies the proxy server to use to access the web server. If no proxy server
is needed this parameter must be set to none.
Suspended
system.
if-cisco-qdrop: Number of Queue Drops on a Interface

This metric measures the number of queue drops on an interface of a Cisco
router. The target router must be running a SNMP agent supporting Cisco
private MIBs.
Operations

Save
If the MIB instance is undefined, this metric tries to query the SNMP tables
identified by ifDescr and ifAlias, which if successful, lists available interfaces
identified by their associated MIB instance values. From this list you can
select the MIB instance to be collected.
Test
results. The test operation queries the specified MIB instance from the
ifDescr and ifAlias tables.
Metric Syntax
C75
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-ciscoqdrop: target node.
Interval
SNMP community
MIB instance
Link type
Identifies the type of interface the MIB instance identifies. A duplex interface
has a separate in and outbound channel, while a simplex interface shares a
common channel for in and outbound traffic. The user must enter this
parameter.
Suspended
system.
C76
if-discards: Number of Discards Per Sample on an Interface

This metric measures the number of discards per sample period on an interface.
The target router must be running an SNMP agent supporting MIB-2
Operations

Save
Test
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-discards:
target node.
Interval
Metric Syntax
C77
SNMP community
MIB instance
Link type
has a separate in and outbound channel, while a simplex interface share a
parameter.
Suspended
system.
if-discardsPs: Number of Discards Per Second on an Interface

This metric measures the number of discards per second on an interface. The
target router must be running an SNMP agent supporting MIB-2.
Operations

Save
Test
C78
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-discards:
target node.
Interval
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
Metric Syntax
C79
if-errors: Number of Errors Per Sample on an Interface

This metric measures the number of errors per sample period on an interface.
The target router must be running a SNMP agent supporting MIB-2.
Operations

Save
Test
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-errors:
target node.
Interval
C80
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
if-errorsPs: Number of Errors Per Second on an Interface

This metric measures the number of errors per second on an interface. The target
router must be running an SNMP agent supporting MIB-2.
Metric Syntax
C81
Operations

Save
Test
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-errors:
target node.
Interval
C82
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
if-octets: Number of Octets Per Sample on an Interface

This metric measures the number of octets (bytes) per sample period sent and
received on an interface. The target router must be running a SNMP agent
supporting MIB-2.
Operations

Save
Test
Metric Syntax
C83
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-octets:
target node.
Interval
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
C84
if-octetsPs: Number of Octets Per Second on an Interface

This metric measures the number of octets (bytes) sent and received per second
on an interface. The target router must be running a SNMP agent supporting
MIB-2.
Operations

Save
Test
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-octets:
target node.
Metric Syntax
C85
Interval
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
if-packets: Number of Packets Per Sample on an Interface

This metric measures the number of packets per sample period sent and received
on an interface. The target router must be running a SNMP agent supporting
MIB-2.
Operations

Save
Test
C86
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-packets:
target node.
Interval
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
Metric Syntax
C87
if-packetsPs: Number of Packets Per Second on an Interface

This metric measures the number of packets sent and received per second on an
interface. The target router must be running a SNMP agent supporting MIB-2.
Operations

Save
Test
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-packets:
target node.
Interval
C88
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
if-util: Interface Bandwidth Utilization

This metric measures interface bandwidth utilization. The target node must be
running a SNMP agent supporting MIB-2. Bandwidth utilization is calculated
based on the amount of transferred data during a sample period and the
interface speed. The interface speed is learned using SNMP from the MIB
variable ifSpeed for the associated MIB instance. This variable must report the
proper interface speed to archive correct results.
Operations

Save
Test
Metric Syntax
C89
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is if-util: target
node
Interval
SNMP community
MIB instance
Link type
parameter.
Suspended
system.
C90
imap: IMAP Mail Server Response Time and Availability

This metric measures the response time and availability of the Internet Message
Access Protocol (IMAP ) mail client service at the target node. The measure is
based on connecting to the IMAP service at the target node and recording the
response time. If no response is received within a timeout period, the service is
assumed unavailable.
Operations

Save
Test
the results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is imap: target
node
Interval
Metric Syntax
C91
Timeout
unavailable.
Importance
trap receiver.
Suspended
system.
ipnet: IP Network Delay and Availability

This metric uses the ICMP protocol to measure roundtrip time between the
Unicenter SLM collect system and a target IP node, like regular ping. When no
response is received within a timeout interval the target host is assumed to be
unavailable, otherwise a response time value (in milliseconds) is recorded.
Operations

Save
Test
results.
Delete
C92
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is ipnet: target
node
Interval
Packet size
Identifies the size of user data (pay load) in the ICMP packet.
Importance
defined on the Unicenter Service Level Management system. This
information is only carried in SNMP trap messages which are generated
when the operational status for this data collection changes from up to down
and from down to up. The destination for the SNMP trap messages is
specified by the Network Management System parameter in the Collect
system, System, Agent configuration dialog. How the information is used
depends on the SNMP trap receiver.
Check System Uptime
Checks the system uptime at the target node after an operational status
change from down to up is measured. The measured outage is then limited
to the system uptime value. The resulting effect of this method is that the
local target node uptime is measured, neglecting any network outages
between the Unicenter SLM collector system and the target node.
Suspended
system.
Metric Syntax
C93
ldap: LDAP Server Response Time and Availability

This metric measures the availability and response time for the LDAP directory
service available from the target node. This metric is (currently) only available
from Linux based Unicenter Service Level Management collector systems, and
require the ldapsearch command. The measure is based on querying the LDAP
server and recording the response time for the query. If no response is received
within a timeout period, the service is assumed unavailable.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is ldap: target
node
Interval
C94
Timeout
complete. If this timeout period is exceeded the service is recorded as
unavailable.
Query
Defines the query to send to the LDAP server.
Expected response
Defines a text string that is included in a successful query.
Importance
when the operational status for this data collection change from up to down
Suspended
system.
nfs: NFS Server Response Time and Availability

This metric measures the response time and availability of the NFS (Networked
File System) on the target node. The measure queries the RPC portmap server on
the target node to check if the NFS service is available and recording the
response time. If no response is received within a timeout period, the service is
assumed unavailable.
Operations

Save
Test
results.
Metric Syntax
C95
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is nfs: target
node
Interval
Timeout
unavailable.
Importance
Suspended
system.
C96
nfs_cp: NFS Mounted File Copy

This metric measures the response time and availability of a NFS (Network File
System) mounted from the Unicenter SLM collector system to a disk system at
the remote node. The measure is based on copying a specified file at the target
host to the Unicenter SLM collector system. If the operation does not complete
within a timeout period the service is assumed to be unavailable. The metric
requires the file system are already mounted.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is nfs_cp:
target node
Interval
Metric Syntax
C97
Local file
Identifies where to copy the remote file to at the Unicenter Service Level
Management collect system.
Timeout
unavailable.
Importance
Suspended
system.
nfs_find: NFS Mounted Directory Search Time

This metric measures the search time and availability of a NFS (Network File
System) mounted from the Unicenter SLM collect system to a disk system at the
remote node. The measure is based on searching for all files in and below a
specified directory at the mounted file system. If the operation does not complete
within a timeout period the service is assumed to be unavailable. The metric
requires the file system to already be mounted.
Operations

Save
Test
results.
C98
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is nfs_find:
target node
Interval
Mount directory
Identifies the mounted directory at the target node to be searched.
Timeout
unavailable.
Importance
Suspended
system.
Metric Syntax
C99
nis: NIS Service Response Time and Availability

This metric measures the response time and availability of the NIS service. The
measure is based on querying a specific key from the local NIS service available
to the Unicenter SLM collector system. If the operation does not complete within
a timeout period the service is assumed to be unavailable.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Lookup key
Identifies a key to lookup in the NIS service.
Label
Identifies a textual label for this data collection. Default value is nis: target
node
Interval
Timeout
unavailable.
C100
Importance
Suspended
system.
nntp: NNTP Server Response Time and Availability

This metric measures the response time and availability of the NNTP (Network
News Transfer Protocol) service. The measure is based on connecting to the
NNTP service at the target node, and issuing the specified command. If the
expected response isn't returned within a timeout period, the service is assumed
to be unavailable.
Operations

Save
Test
results.
Delete
Report
Clear
Metric Syntax
C101
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is nntp: target
node
Interval
Timeout
unavailable.
Command
Defines the NTTP command to send to the target node. Any valid NTTP
protocol command may be specified.
Expected response
Defines a text string that is included in a successful query.
Importance
Suspended
system.
C102
ntp: NTP Server Response Time and Availability

This metric measures the response time and availability of the NTP (Network
Time Protocol) service. This metric is (currently) only available from Linux based
Unicenter SLM collector systems, and requires the ntpdate command. The
measure is based on querying the NTP service at the target node and recording
the response time. If no response is received within a timeout period, the service
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is ntp: target
node
Interval
Metric Syntax
C103
Timeout
unavailable.
Importance
Suspended
system.
pop3: POP Server Response Time and Availability

This metric measures the response time and availability of the POP (Post Office
Protocol) service at the target node. The measure is based on connection to the
POP3 service at the target node and recording the response time. If no response
is received within a timeout period, the service is assumed unavailable.
Operations

Save
Test
results.
Delete
C104
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is pop3: target
node
Interval
Timeout
unavailable.
Importance
Suspended
system.
Metric Syntax
C105
propagated_sev: TNG Propagated Severity Property

This metric measures availability based on the Unicenter propagated severity
property of a Business Process View or an object. If you want to measure the
actual severity of an object, you should use the severity metric. The Unicenter
hosting the Common Object Repository must be running a server application
called TNGWVserver.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
propagated_sev: target node
Interval
C106
TNG Host Address

Identifies the host name or IP address of the machine running the
TNGWVserver application. The user must enter this parameter.
TNGWVserver Port
Identifies the port number the TNGWVserver is using to accept connections.
The user must enter this parameter.
TNG Repository Name
Identifies the name of the Common Object Repository. The user must enter
this parameter.
Severity Threshold
Identifies the propagated severity value you wish to use as the threshold
value for availability measurements. By default this value is set to NORMAL.
All other propagated severity values are calculated as downtime incidents. If
you set this value to MAJOR, propagated severity values of CRITICAL,
DOWN, INSERVICE, REMOVE and FUTURE are calculated as downtime
incidents, based on the following list:
NORMAL = 0
UNKNOWN = 1
WARNING = 2
MINOR = 3
MAJOR = 4
CRITICAL = 5
DOWN = 6
INSERVICE = 7
REMOVE = 8
FUTURE = 9
Importance
Suspended
system.
Metric Syntax
C107
rmon-util: Port/LAN Utilization Measured on a RMON Probe

This metric measures the bandwidth utilization on a specific switch port or LAN
segment monitored by a RMON probe. Bandwidth utilization is calculated based
on the amount of transferred data during a sample period and the specified
LAN/Port speed.
Operations

Save
identified by etherStatsDataSource, which if successful, lists available
segments/ports identified by their associated MIB instance values. From this
list you can select the MIB instance to be collected.
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is rmon-util:
target node
C108
Interval
SNMP community
Speed
Defines the media speed in bits/second.
MIB instance
Link type
has a separate in and outbound channel, while a simplex interface shares a
parameter.
Suspended
system.
severity: TNG Severity Property

This metric measures availability based on the Unicenter severity property of a
Business Process View or an object. If you want to measure propagated severity
you should use the propagated_sev metric. The Unicenter installation hosting the
Common Object Repository must be running a server application called
TNGWVserver.
Operations

Save
Test
results.
Metric Syntax
C109
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is severity:
target node
Interval
TNG Host Address
Identifies the host name or IP address of the machine running the
TNGWVserver application. The user must enter this parameter.
TNGWVserver Port
Identifies the port number the TNGWVserver is using to accept connections.
The user must enter this parameter.
TNG Repository Name
Identifies the name of the Common Object Repository. The user must enter
this parameter.
C110
Severity Threshold
Identifies the propagated severity value you wish to use as the threshold
value for availability measurements. By default this value is set to NORMAL.
All other propagated severity values are calculated as downtime incidents. If
you set this value to MAJOR, propagated severity values of CRITICAL,
DOWN, INSERVICE, REMOVE and FUTURE are calculated as downtime
incidents, based on the following list:
NORMAL = 0
UNKNOWN = 1
WARNING = 2
MINOR = 3
MAJOR = 4
CRITICAL = 5
DOWN = 6
INSERVICE = 7
REMOVE = 8
FUTURE = 9
Importance
Suspended
system.
Metric Syntax
C111
smb: SMB Service Response Time and Availability

This metric measures the response time and availability of a SMB service that is
compatible with the LanManager protocol from the Unicenter SLM collector
system to a disk system at the target node. The measure is based on copying a
specified file at the target host to the Unicenter Service Level Management collect
system. If the operation does not complete within a timeout period the service is
assumed to be unavailable. This metric is only available from Linux based
Unicenter SLM collector systems, and requires the smbclient command.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is smb: target
node
Interval
C112
Domain name
Identifies the work group or domain for access to the LanManager service
from the target node.
Share name
Identifies the share name which is exported by the LanManager service from
the target node and contain the remote file.
User
Identifies the user name defined at the target host.
Password
Identifies the password assigned to the user name at the target host.
Remote file
Identifies the remote file to be retrieved from the target node.
Local file
Identifies the local file to be replaced at the Unicenter Service Level
Management collect system. Use a full path name.
Timeout
unavailable.
Importance
Suspended
system.
Metric Syntax
C113
smtp: SMTP Server Response Time and Availability

This metric measures SMTP (Simple Mail Transfer Protocol) server response time
and availability based on connecting to the target SMTP server. If no response is
received within a timeout period, the service is assumed unavailable.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is smtp: target
node
Interval
Timeout
unavailable.
C114
Command
Identifies the SMTP command to send to the target node. Any valid SMTP
protocol commands may be specified.
Expected response
Identifies the text string that is included in a successful query.
Importance
Suspended
system.
tcp_echo: TCP ECHO Response Time and Availability

This metric measures server response time and availability based on connecting
to the TCP echo port at the target node, and requesting an echo of a text string. If
no response is received within a timeout period, the service is assumed
unavailable.
Operations

Save
Test
results.
Delete
Metric Syntax
C115
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is tcp_echo:
target node
Interval
Data size
Identifies the length of the text string to be echoed by the target node.
Timeout
unavailable.
Importance
Suspended
system.
C116
wins: WINS (NetBIOS) Name Service Response Time and Availability

This metric measures the response time and availability of the NetBIOS name
service provided by the target node. The measure is based on querying a specific
name from the service. If the operation does not complete within a timeout
period, the service is assumed to be unavailable. This metric is only available
from Unicenter SLM collector systems with the SAMBA software installed with
the nmblookup command.
Operations

Save
Test
results.
Delete
Report
Clear
Parameters

Target node
Label
Identifies a textual label for this data collection. Default value is wins: target
node
Name to query
Identifies the NetBIOS name to query.
Metric Syntax
C117
Interval
Timeout
unavailable.
Importance
Suspended
system.
C118
Appendix
Advantage Ingres Tips and Tricks

The following sections provide some tips and tricks for using Advantage Ingres
with Unicenter SLM.
Installing Advantage Ingres Manually

If you cannot successfully install Unicenter SLM with Advantage Ingres, you
must perform a manual install.
Note: Advantage Ingres depends on specific environment variables. The most
important variable is the II_SYSTEM variable that defines the installation root for
Ingres. The II_SYSTEM setting for Unicenter SLM is as follows:
II_SYSTEM=/opt/ca/ingresii
Installing Advantage Ingres on UNIX

UNIX
As user root
To manually install Advantage Ingres on UNIX, follow these steps:

1.
Enter the following command to define II_SYSTEM to /opt/ca/ingresii:

II_SYSTEM=/opt/ca/ingresii
export II_SYSTEM
2.
Enter the following command to remove the old ingres user :

userdel r ingres
3.
Enter the following command to create the ingres user with home directory
set to $II_SYSTEM:
useradd d $II_SYSTEM m ingres
4.
Enter the following command to specify a password for user ingres with the
command:
passwd ingres
(default password for user ingres for SLM is ingres)
5.
Enter the following command to ensure that the directory $II_SYSTEM is

readable for everyone with the command:
chmod a+r $II_SYSTEM
D1
As user ingres
6.
Enter the following command to create a directory called ingres, and update
the .profile file:
cd
mkdir ingres
vi .profile, and add :
II_SYSTEM=/opt/ca/ingres
export II_SYSTEM
PATH=$PATH:$HOME/ingres/bin:$HOME/ingres/utility
export PATH
7.
Enter the following command to set permission 755 for this directory:
chmod 755 ingres
8.
Enter the following command to change to the ingres directory:

cd ingres
9.
Enter the following command to set umask 0:

umask 0
10. Enter the following command to unpack the install directory from the Ingres
distribution media:
tar xf /tmp/ingres/ingres.tar install
As user root
11. Enter the following command to install the Ingres License:

cd II_SYSTEM/ingres
./install/mklicense
As user ingres
12. Enter the following command to start the install program:

II_EMBED_INSTALL=ON
export II_EMBED_INSTALL
./install/ingbuild
You will be prompted for the correct terminal settings.

13. Specify vt100fx for Linux or vt100f for Solaris and HP-UX. The install
program (ingbuild) presents a list of all Ingres modules in the package.
14. Select the following modules for a console installation:
DBMS ( Ingres Intelligent DBMS )
JDBC (Ingres JDBC Server )
tm ( Terminal monitors )
15. Execute install after the correct modules are selected. The installation
program guides you through the installation.
The installation program prompts you for optional partitions for backup
logs. Respond with the II_SYSTEM setting for all such questions. The default
for the transaction log size is 400 Mb. We recommend using a size between
400 1 GB, depending on the amount of data collections.
D2
Configuring User Access

To configure user access, follow these steps:
As user ingres
1.

TERM=vt100fx (Linux) or TERM=vt100f (others)
Export TERM
accessdb
2.
Select User.
3.
Select Create.
4.
Define user name as smm.
5.
Ensure that the Create database is y.
6.
Save and exit.
7.
Enter the following commands (substitute your local host name for
LOCALHOSTNAME):
iisetres
iisetres
iisetres
iisetres
iisetres
iisetres
iisetres
iisetres
iisetres
As user root
8.
ii.LOCALHOSTNAME.dbms."*".default_page_size 4096
ii.LOCALHOSTNAME.dbms."*".max_tuple_length 4016
ii.LOCALHOSTNAME.dbms."*".qef_qep_mem 25600
ii.LOCALHOSTNAME.dbms."*".qef_sort_mem 204800
ii.LOCALHOSTNAME.dbms."*".rule_depth 200
ii.LOCALHOSTNAME.dbms."*".default_journaling OFF
ii.LOCALHOSTNAME.dbms."*".dmf_hash_size 1024
ii.LOCALHOSTNAME.dbms."*".dmf_tbl_cache_size 50
ii.LOCALHOSTNAME.dbms.private."*".cache.p4k_status ON
Enter the following command to set up password validation for the JDBC
Server:
cd II_SYSTEM/ingres/bin
./mkvalidpw
9.
Enter the following command to restart Advantage Ingres:

ingstop && ingstart
D3
Installing Advantage Ingres on Windows

Windows
To manually install Advantage Ingres on UNIX, follow these steps:

1.
Locate the ingres.rsp file in the Advantage Ingres distribution.
2.
Open this file in a text editor and ensure that the following code is in place:
Ingres DBMS Server=TRUE
JDBC Driver=TRUE
JDBC Server=TRUE
Ingres Querying and Reporting Tools=TRUE
logfilesize="400"
Note: The II_SYSTEM defines the installation root. Update this in

SLM_Install_Path/etc/smm.cfg.
3.
Create a system account for user ingres, and make ingres a member of the
Administrators Group.
4.
Log in as user ingres
5.
Enter the following command in the directory where the Advantage Ingres
distribution is unpacked:
install /embed /r ingres.rsp
6.
Repeat step 4 and 5 from the Unix installation.

Note: Ignore the TERM variable on Windows.
7.
Reboot the machine.
Creating the Database

You must now create and initialize the database and tables. All Unicenter SLM
program and configuration files should have been installed during the failed
installation.
As user smm
1.
Enter the following command to create the database:

createdb smmdb
2.
Enter the following command to create the tables:

createDb
UNIX
cd SLMHOME\bin
createDb
Windows
3.
Edit and localize smm.cfg as the chapter Configuring the Environment in

this guide.
Note: The host entry in the databases section must contain only the host
name without the domain part.
D4
Moving the Transaction Log
4.

smmSetup
If this command fails, ping the host name. If the ping fails, add the host name
to /etc/hosts.
5.
Enter the following command to build the tables and configuration:

smmBuild all
6.
From the directory SLM_Install_Path/lib/smm and enter the following

command:
./mkIndex
Verifying the Installation

Unicenter SLM should be now be installed. To check your installation, enter the
following command to start the collector daemon processes in debug mode:
smmCollect d

UNIX
The default size of the transaction log is 400 MB. Moving this log to another
disk volume can reclaim this space and improve performance, if the disk
controller is capable of multiple writes.
To move the transaction log, follow these steps.
1.
Enter the following command as user smm to shut down the collector, report
daemon and data loader daemon:
smmCollect sd && smmReportd sd && smmdbd sd
2.
Enter the following command as user ingres to stop Ingres:

ingstop
3.
Enter the following command start cbf:

TERM=vt100fx cbf
4.
From the transaction log entry, choose destroy.
5.
Exit cbf.
D5
6.
Create the new target directory for the new transaction log:, such as
II_LOG_FILE/ingres/log. The new directory must have the subdirectories
ingres/log. The file permissions must be 0755 for all the directories.
For example, if the new directory is /opt/ii, enter the following commands:
mkdir /opt/ii
chmod 0755 /opt/ii
cd /opt/ii
mkdir p ingres/log
chmod R 0755 ingres/log
7.
Enter the following command to set the II_LOG_FILE environment variable:

ingsetenv II_LOG_FILE=/opt/ii
8.
Start cbf.
9.
From the transaction log entry, choose create. The new path should be listed.
10. Enter the size.

11. Exit cbf and start Advantage Ingres.
12. Enter the following command as user smm to start the collector, report
daemon and the data loader daemon:
smmCollect && smmReportd && smmdbd
Windows
Note: The Advantage Ingres DBMS must be stopped prior to changing the
transaction log location. You can do this through the Service Manager.
To move the transaction log, follow these steps:
D6
1.
Open Ingres Visual Manager .
2.
Right mouse click the Primary Transaction Logentry.
3.
Select the present transaction log, and select Destroy.
4.
After confirming the deletion, select Create.
5.
On the resulting screen, select add, and enter the path to the new location.
6.
Select OK, and the new location is installed.
7.
Restart Ingres through the Component Services.
Changing the Host Name
Changing the Host Name

To change the host name on a console system, you must perform the following
configurations:
Operating system configuration
Unicenter SLM configuration
Operating System Configuration

To change the host name on the system, follow these steps:
UNIX

su
hostname <new hostname>
vi /etc/hosts
# change old hostname to new
Windows
Change the host name from Control Panel, Network, Identification, Change.
Unicenter SLM Configuration

To configure Unicenter SLM, following these steps.
UNIX
Note: On the Unix platform, the following tasks must be done as user smm.
1.
Edit smm.cfg. Replace all occurrences of the old host name with the new host
name and replace all occurrences of the old IP address with the new IP
address.
2.

smmSetup
smmBuild -config
3.
If this system is collecting data, the attribute agenthost with the value
old_hostname needs to be updated with the value new_hostname for each data
collection.
To do this, enter the following command to start the Advantage Ingres
terminal monitor:
sql smmdb
Enter the following SQL commands:

update data_collect_attrs set value=new hostname
commit\g
D7
Creating a Backup
Creating a Backup
No backup is initialized when Unicenter SLM is installed. The following
elements need to be included in a backup of the Unicenter SLM Console:
Unicenter SLM database
Unicenter SLM report repository
Unicenter SLMconfiguration files
No regular backup of a Unicenter SLM collect system is needed.

Use regular file backup methods to back up the report repository and
configuration files from the following directories:
SLMHOME/reports
SLMHOME/etc
Backing Up the Database

To backup the Unicenter SLM database, use the checkpoint method. This
method is a full backup of the Advantage Ingres database. A journal is an
incremental backup since the last checkpoint or journal.
Unicenter SLM installs all tables with journaling enabled from the first
checkpoint. Therefore, journaling takes effect after the first invocation of a
checkpoint.
To perform a checkpoint of the database, use the following command:
ckpdb smmdb
This command can be run while the database is online. You can use the
following arguments with this command:
-d smmdb
Deletes the previous checkpoint.
-j smmdb
Disables journaling.
+j smmdb
Enables journaling.
-d +j smmdb
Enables journaling, and delete previous checkpoint.
-m /dev/rmt8 smmdb
Writes the backup to /dev/rmt8. Any previous data will be lost.
D8
Creating a Backup
To see the status of checkpoints and journals, use the following command:
infodb
A checkpoint creates a file with extension .ckp located in the following directory:
DB_Install_Path/ingres/ckp/default/smmdb
We recommend executing the following command before backing up your

Unicenter SLM database:
sysmod smmdb
Recovering Backed Up Data

UNIX
To recover backed up data, follow these steps:

1.
Enter the following commands to stop any running Unicenter SLM server
daemons:
crontab > cron.txt
crontab /dev/null
smmCollect sd
smmReportd sd
smmdbd sd
/etc/rc.d/init.d/mhttpd stop.
2.
To recover from a checkpoint file, enter the following command:

rollforwarddb smmdb
To recover from a checkpoint at a tape drive, enter the following command:

rollforwarddb smmdb -m /dev/[tape device]
For an in-depth description of the rollforwarddb command, see the Advantage

Ingres Database Administrator Guide.
To reinstall the crontab entry and start up the Unicenter SLM server daemons,
enter the following commands:
crontab cron.txt
smmCollect
smmReportd
smmdbd
Windows
To recover backed up data, use Ingres Visual DBA.
D9
Index
CA_NT4_MEMORY_Current_Paging_memory
metric, C-26
CA_NT4_MEMORY_Current_Physical_memory
metric, C-28
access
controlling for the interface, 6-3
CA_NT4_MEMORY_Current_Virtual_memory
metric, C-29
appagent collector, 1-5
CA_NT4_NETWORK_Input_Packets_Status metric,
C-31
architecture, 1-3
audience, 1-1
CA_NT4_NETWORK_Output_Packets_Status metric,
C-32
CA_NT4_SERVICES_Service_Availability metric,
C-33
CA_PathDoctor metric, C-35
backup, D-8
CA_perfAgent metric, C-36
batch reports
command line, 5-5
GUI, 5-4
overview, 5-3
smmReportd, 5-4
CA_SAP_R3_GENERAL_Items metric, C-37
C
CA_MSEXCHANGE_DataBase_Status metric, C-17
CA_MSEXCHANGE_DISK_Status metric, C-19
CA_SAP_R3_GENERAL_Status metric, C-38

CA_SAP_R3_Number_Dump_Daily metric, C-39
CA_SAP_R3_Process_Status metric, C-41
CA_SAP_R3_Status_Dump_Daily metric, C-42
CA_SAP_R3_UPDATES_Cancelled_Count metric,
C-43
CA_SAP_R3_UPDATES_Cancelled_Status metric,
C-45
CA_MSEXCHANGE_MTA_Queue_Status metric,
C-20
CA_SAP_R3_UPDATES_Pending_Count metric, C-46
CA_MSEXCHANGE_MTA_Receive_Queue_Status
metric, C-21
CA_W2K_cpu_Current_Processor_Util metric, C-49
CA_MSEXCHANGE_MTA_Send_Queue_Status
metric, C-23
CA_NT4_cpu_Current_Processor_Util metric, C-24
CA_NT4_cpu_Current_Total_Processors_Util metric,
C-25
CA_SAP_R3_UPDATES_Pending_Status metric, C-47
CA_W2K_cpu_Total_Processor_Util metric, C-50

CA_W2K_LOGICAL_VOLUMES_File_Fragmentation
metric, C-51
CA_W2K_LOGICAL_VOLUMES_fileSysUsed metric,
C-52
Index1
CA_W2K_MEMORY_Current_Paging_memory
metric, C-54
CA_W2K_MEMORY_Current_Physical_memory
metric, C-55
CA_W2K_MEMORY_Current_Virtual_memory
metric, C-56
CA_W2K_NETWORK_Input_Packets_Status metric,
C-58
CA_W2K_NETWORK_Output_Packets_Status
metric, C-59
CA_W2K_SERVICES_Service_Availability metric,
C-60
cai_cpuUtil metric, C-8
cai_cpuUxUtil metric, C-10
cai_fileSysUsed metric, C-11
cai_memoryUtil metric, C-12
cai_memoryUxUtil metric, C-14
cai_ntAvailService metric, C-15
cai_swapUxUtil metric, C-16
CAM/CAFT password, 3-9
catrapd, 9-1
checking email, 9-9
checkpoint the database, 8-10
cisco_cpu5 metric, C-62
collect interval, 4-8
collection size estimates, 2-2
collectors
importing external data, 4-16
importing performance cubes, 4-10
importing SuperPing data, 4-12
importing Unicenter objects, 4-4
importing WRM data, 4-13
modifying, 4-4
overview, 1-5
restarting smmCollect, 4-4
single collections, 4-3
starting, 4-2
storage, 8-2
types, 4-1
understanding, 4-2
upgrading, 3-14
commands
createDb, B-1
deleteData, B-2
deleteDataCollection, B-2
deleteMetrics, B-3
dropDb, B-3
installData, B-4
lsMetrics, B-4
lsReportGroups, B-8
mkIndex, B-8
runReport, B-8
showDcid, B-9
slmCopyBatchReports, B-9
slmLoadColl, B-10
slmLoadGroup, B-11
smmBuild, B-12
smmCheck, B-13
smmCollect, B-14
smmDataImport, B-16
smmdb_maintenance, B-21
smmdbd, B-15
smmReduceData, B-18
smmReportd, B-19
smmReporter, B-19
smmReportIndex, B-19
smmSetup, B-21
smmstart, B-22
smmstop, B-22
Common Object Repository
importing objects, 4-6
propagated severity threshold, 4-9
property value collection, 4-9
reloading objects, 4-8
severity, 4-8
configuration
file location, 3-1
updating, 3-1
configuring Unicenter Performance Management,
4-11
considerations
data collection, 2-2
disk allocation, 2-1
disk space, 2-2
host name, 2-4
installation path, 2-5
maximum shared memory, 2-3
transaction log, 2-3
colors, 6-2
Index2
console
controlling access, 6-3
daemon processes, 1-5
interface, 6-1
metric charter, 6-4
overview, 1-4
status colors, 6-2
storage, 8-3
upgrading UNIX, 3-11
upgrading Windows and Ingres, 3-13
upgrading Windows and SQL, 3-12
user interface, 1-4
web server, 1-4
conventions, 1-7
coreimport collector, 1-6
createDb command, B-1
cron job, 8-6
cross references, 1-7
D
daemon processes, 1-5
data collections
defining single, 4-3
external data, 4-16
modifying single, 4-4
performance cubes, 4-10
size estimates, 2-2
SuperPing, 4-12
Unicenter objects, 4-4
WRM, 4-13
data reduction
configuring policy, 8-5
default policy, 8-4
database
checkpoint, 8-10
collector storage, 8-2
configuring data reduction, 8-5
console storage, 8-3
cron job, 8-6
data reduction, 8-4
designation, 1-8
improving performance, 8-7
maintenance, 8-6
reading error messages, 8-6
recovery, 8-9
removing, 3-10
storage, 8-2
structure, 8-1
database tables
business_hours, A-10
collected_data, A-5
copy_index, A-5
data_collect_attrs, A-6
data_collections, A-6
default_business_hours, A-10
export_reports, A-11
import_rules, A-6
metric_field_values, A-1
metric_fields, A-2
metric_menues, A-3
metric_reports, A-3
metrics, A-4
profile_defs, A-11
profile_values, A-12
profiles, A-12
report_commands, A-12
report_done, A-13
report_group, A-13
report_group_goals, A-14
report_group_members, A-14
report_group_parents, A-14
report_identifier, A-15
report_options, A-16
report_time, A-16
service_goal_values, A-17
service_goals, A-17
service_incident_victims, A-18
service_incidents, A-18
smm_module_defs, A-7
smm_module_values, A-7
smm_modules, A-8
smm_sub_systems, A-8
smm_systems, A-9
snmp_config, A-9
default directories, 1-8
Index3
defining collections, 4-1
deleteData command, B-2

deleteDataCollection command, B-2
GUI
metric charter, 6-4
status colors, 6-2
URL, 6-1
deleteMetrics command, B-3

deleting import metric template, 4-22
directory metrics, 7-2
disk allocation, 2-1
disk space
data collection considerations, 2-2
data reduction policy, 8-4, 8-5
minimum, 2-2
dns metric, C-63
dropDb command, B-3
H
host name
Ingres, D-7
validation, 2-4
verification, 2-4
hpux-fileSysUsed metric, C-70
hr_fileSysUsed metric, C-71
hr_systemNumUsers metric, C-72
email messages, 9-9

error messages
modify table, 8-7
open database, 8-7
Event Console
catrapd, 9-1
integrating, 9-5
message records and actions, 9-4
traps, 9-2
http metric, C-74
I
if-cisco-qdrop metric, C-75
if-discards metric, C-77
if-discardsPs metric, C-78
example
adding a single MIB value, 7-3
adding interface MIB values, 7-7
adding multiple MIB values, 7-5
if-errors metric, C-80
external data
file format, 4-17
import metric template, 4-19
preparing, 4-19
if-octetsPs metric, C-85
if-errorsPs metric, C-81

if-octets metric, C-83
if-packets metric, C-86

if-packetsPs metric, C-88
if-util metric, C-89
imap metric, C-91
features, 1-2
import metric template

activating, 4-20
creating, 4-19
deleting, 4-22
testing, 4-21
import collector, 1-6
fr-util metric, C-65

ftp metric, C-67
ftp-ping metric, C-68
Index4
importing
Common Object Repository, 4-6
external data file format, 4-17
performance cubes, 4-10
SuperPing, 4-12
WRM, 4-14
inconsistent database, 8-9
logging
adding, 9-8
changing, 9-7
maintaining, 9-6
overview, 9-6
Ingres
backup, D-8
host name, D-7
tips, D-1
transaction log, D-5
UNIX installation, D-1
Windows installation, D-4
installation
Ingres on UNIX, D-1
Ingres on Windows, D-4
path, 2-5
stopping agent technology, 2-5
Unicenter SLM CORE Gateway, 4-5
installData command, B-4
interface
metric charter, 6-4
status colors, 6-2
URL, 6-1
ipnet metric, C-92
J
Java Plug-in
configuring, 3-6
Java Path, 3-7
Java Runtime Environment
installing, 3-4
Java path, 3-7
Java Plug-in, 3-6
JDBC password, 3-8
JRE. see Java Runtime Environment
ldap metric, 7-10, C-94

log files, maintenance, 9-6
lsMetrics command, B-4

lsReportGroups command, B-8
M
maintaining
log files, 9-6
maintenance
log files, 9-6
memory
shared requirements, 2-3
metric charter, 6-4
display, 6-5
load graph, 6-5
parameters, 6-4
metrics
activating UNIX-specific, 7-11
adding a single MIB value example, 7-3
adding interface MIB values example, 7-7
adding multiple MIB values example, 7-5
additional files, 7-12
architecture, 7-2
CA_MSEXCHANGE_DataBase_Status, C-17
CA_MSEXCHANGE_DISK_MTA_Queue_Status,
C-20
CA_MSEXCHANGE_DISK_MTA_Receive_Queu
e_Status, C-21
CA_MSEXCHANGE_DISK_MTA_Send_Queue_
Status, C-23
CA_MSEXCHANGE_DISK_Status, C-19
CA_NT4_cpu_Current_Processor_Util, C-24
CA_NT4_cpu_Total_Processors_Util, C-25
CA_NT4_MEMORY_Current_Paging_memory,
C-26
CA_NT4_MEMORY_Current_Physical_memory,
C-28
Index5
CA_NT4_MEMORY_Current_Virtual_memory,
C-29
CA_NT4_NETWORK_Input_Packets_Status,
C-31
CA_NT4_NETWORK_Output_Packets_Status,
C-32
CA_NT4_SERVICES_Service_Availability, C-33
CA_PathDoctor, C-35
CA_perfAgent, C-36
CA_SAP_R3_GENERAL_Items, C-37
CA_SAP_R3_GENERAL_Status, C-38
CA_SAP_R3_Number_Dump_Daily, C-39
CA_SAP_R3_ProcessStatus, C-41
CA_SAP_R3_Status_Dump_Daily, C-42
CA_SAP_R3_UPDATES_Cancelled_Count, C-43
CA_SAP_R3_UPDATES_Cancelled_Status, C-45
CA_SAP_R3_UPDATES_Pending_Count, C-46
CA_SAP_R3_UPDATES_Pending_Status, C-47
CA_W2K_cpu_Current_Processor_Util, C-49
CA_W2K_cpu_Total_Processor_Util, C-50
CA_W2K_LOGICAL_VOLUMES_File_Fragment
ation, C-51
CA_W2K_LOGICAL_VOLUMES_fileSysUsed,
C-52
CA_W2K_MEMORY_Current_Paging_memory,
C-54
CA_W2K_MEMORY_Current_Physical_memory
, C-55
CA_W2K_MEMORY_Current_Virtual_memory,
C-56
CA_W2K_NETWORK_Input_Packets_Status,
C-58
CA_W2K_NETWORK_Output_Packets_Status,
C-59
CA_W2K_SERVICES_Service_Availability, C-60
cai_cpuUtil, C-8
cai_cpuUxUtil, C-10
cai_fileSysUsed, C-11
cai_memoryUtil, C-12
cai_memoryUxUtil, C-14
cai_ntAvailService, C-15
cai_swapUxUtil, C-16
cisco_cpu5, C-62
creating, 7-2
data collection, C-2
dns, C-63
files, 7-2
folder, C-2
fr-util, C-65
ftp, C-67
ftp-ping, C-68
hpux-fileSysUsed, C-70
hr_fileSysUsed, C-71
Index6
hr_systemNumUsers, C-72
http, C-74
if-cisco-qdrop, C-75
if-discards, C-77
if-discardsPs, C-78
if-errors, C-80
if-errorsPs, C-81
if-octets, C-83
if-octetsPs, C-85
if-packets, C-86
if-packetsPs, C-88
if-util, C-89
imap, C-91
ipnet, C-92
ldap, C-94
location, 7-2
mandatory fields, C-6
nfs, C-95
nfs_cp, C-97
nfs_find, C-98
nis, C-100
nntp, C-101
ntp, C-103
overview, 7-1
pop3, C-104
propagated_sev, C-106
rmon-util, C-108
severity, C-109
smb, C-112
smtp, C-114
syntax, C-1
tcp_echo, C-115
UNIX, 7-10
upgrading, 3-15
wins, C-117
mkIndex command, B-8
N
nfs metric, C-95
nfs_cp metric, 7-10, C-97
nfs_find metric, 7-10, C-98
nis metric, 7-10, C-100
nntp metric, C-101
ntp metric, C-103
operating systems conventions, 1-8
reduction
configuring policy, 8-5
default policy, 8-4
P
password
CAM/CAFT, 3-9
ingres, 3-8
JDBC, 3-8
smm, 3-8
path
adding metric files, 7-2
pathagent collector, 1-5
performance cubes
configuring Unicenter Performance
Management, 4-11
importing, 4-10
pop3 metric, C-104
port numbers
changing for collector, 3-4
changing for console, 3-3
changing for services, 3-2
changing for web server, 3-3
required, 3-2
preparing external data, 4-19
processing
SuperPing data, 4-13
WRM data, 4-15
propagated severity
threshold, 4-9
propagated_sev metric, C-106
property
value collection, 4-9
reloading
removing
UNIX, 3-16
Windows, 3-16
report groups
adding data collections, 5-9
creating, 5-8
deleting, 5-10
hierarchy, 5-7
listing, 5-10
overview, 5-6
report repository
deleting reports, 5-17
deleting temporary reports, 5-16
maintaining, 5-16
overview, 1-6
saving reports, 5-17
report server overview, 5-1
reports
configuring web server, 5-11
controlling content, 5-15
creating automatically, 5-3
creating interactively, 5-3
exporting, 5-11, 5-12
exporting tips, 5-13
maintaining, 5-16
overview, 5-1
publishing links, 5-14
report groups, 5-6
report server, 5-1
understanding, 5-2
rmon-util metric, C-108
runReport command, 5-2, B-8
Index7
smmReporter command, 5-2, B-19

smmReportIndex command, B-19
service goals syntax, C-1
smmSetup command, B-21
severity
smmstart command, B-22
severity metric, C-109

shared memory, 2-3
smmstop command, B-22

smtp metric, C-114
showDcid command, B-9
SNMP
traps, 9-2
slmCopyBatchReports command, B-9
snmpCollect collector, 1-5
slmLoadColl command, B-10
snmpPathDown, 9-2
slmLoadGroup command, B-11
snmpPathUp, 9-2
slmoMissingData, 9-3
SuperPing
importing, 4-12
processing data, 4-13
slmoMsgCritical, 9-3
slmoMsgError, 9-3
slmoNoData, 9-3
slmoSLAviolate, 9-2
smb metric, 7-11, C-112
smm command, 5-2
smm.cfg file
collector port number, 3-4
console port number, 3-3
file location, 3-1
JDBC password, 3-8
services port number, 3-2
updating, 3-1
web server port number, 3-3
smmBuild command, B-12
smmCheck command, B-13
smmCollect
restarting, 4-4
smmCollect command, B-14
smmDataImport command, B-16
smmdb.cfg.template file
file location, 3-1
updating, 3-1
syntax
case-sensitivity, 1-7
variables, 1-7
T
tcp_echo metric, C-115
testing
import metric template, 4-21
WRM, 4-15
transaction log
default size, 2-3
Ingres, D-5
traps
message records and actions, 9-4
showing details, 9-5
slmoMissingData, 9-3
slmoMsgCritical, 9-3
slmoMsgError, 9-3
slmoNoData, 9-3
slmoSLAviolate, 9-2
snmpPathDown, 9-2
snmpPathUp, 9-2
Unicenter SLM, 9-2
smmdb_maintenance command, B-21

smmdbd command, B-15
smmReduceData command, B-18
smmReportd command, 5-4, B-19
Index8
U
Unicenter
Event Console, 9-1
Unicenter Performance Management
PATH environment variable, 3-8
Unicenter SLM CORE Gateway
installing for UNIX, 4-5
installing for Windows, 4-6
upgrading
collector, 3-14
considerations, 3-10
metrics, 3-15
removing the database, 3-10
UNIX console, 3-11
Windows and Ingres console, 3-13
Windows and SQL console, 3-12
user interface, 1-4
W
web server, 1-4
configuring for reports, 5-11
wins metric, C-117
WRM
importing, 4-14
processing, 4-15
testing, 4-15
Index9

NSM Slmo

Uploaded by

Document Information

Original Title

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

NSM Slmo

Uploaded by

Copyright:

Available Formats

Unicenter Service Level

2002 Computer Associates International, Inc.

Chapter 1: Introducing Unicenter SLM

Chapter 2: Planning Your Installation

Chapter 3: Configuring the Environment

Chapter 4: Using Collectors

Unicenter Service Level Management User Guide

Chapter 5: Using Reports

Chapter 6: Using the Interface

Chapter 7: Using Metrics

Chapter 8: Understanding the Database

Unicenter Service Level Management User Guide

Chapter 9: Using Traps and Logs

Appendix A: Database Tables

Report Tables ............................................................................... A-10

Appendix B: Command Reference

Unicenter Service Level Management User Guide

smmdbd .................................................................................... B-15

Appendix C: Metric Syntax

CA_NT4_SERVICES_Service_Availability: Windows NT 4.0 Service Availability ..............

Unicenter Service Level Management User Guide

if-packetsPs: Number of Packets Per Second on an Interface .................................. C-88

Appendix D: Advantage Ingres Tips and Tricks

Introducing Unicenter SLM

Introducing Unicenter SLM

Provides efficient production and distribution of service level reports

Unicenter Service Level Management User Guide

Introducing Unicenter SLM

Produces service level reports.

Configures and maintains data collections.

Displays collected system status.

Restarts and stops collectors.

Displays the status of data collections and Unicenter SLM systems.

Runs and displays reports.

Maintains the report repository.

Unicenter Service Level Management User Guide

Database engine (Advantage Ingres or MS SQL)

Data collector (smmCollect)

Data loader (smmdbd)

Report server (smmReportd)

Web server (mhttpd)

Optionally, a standard web server (httpd)

Introducing Unicenter SLM

Unicenter Performance Management performance cubes

Unicenter Advanced Network Option data

Unicenter Management for Web Servers response data

ASCII data files supported by the Import Wizard

Unicenter Service Level Management User Guide

All class, command, directive, environment parameter, function, and property

References to information in other guides, or in other sections within this guide,

Indicates the name of another guide.

Indicates the name of a chapter in this or another guide.

The following example uses these conventions:

Syntax and user input use the following form:

Indicates a variable name or placeholder for which you

Indicates optional operands.

The following example uses these conventions:

In this example, wvgethosts must be entered exactly as shown. The variables

Introducing Unicenter SLM

Information is specific to Windows. The term Windows refers to the Microsoft

Identifies the directory in which you

Identifies the directory in which you

Unicenter Service Level Management User Guide