Netcool Wireless Admin Guide

Netcool Performance Manager for Wireless
Version 9.1.2
Administration Guide
Note Before using this information and the product it supports, read the information in Notices and Trademarks on page 171.
This edition applies to version 9.1.2 of Tivoli Netcool Performance Manager for Wireless and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces 0000-0000-00. Copyright International Business Machines Corporation, 2008. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
1 About This Documentation . . . . . . . . . . . . Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Skills and Knowledge . . . . . . . . . . . . . . Document Conventions . . . . . . . . . . . . . . . . . . . . Blank pages . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Structure . . . . . . . . . . . . . . . . . . . . . . . User Publications . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Online Help . . . . . . . . . . . . . . . . Viewing the Publications in PDF . . . . . . . . . . 1 1 1 1 2 3 3 4 4
Tivoli Netcool Performance Manager for Wireless Architecture Overview . . . . . . . . 5 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Listing current software versions . . . . . . . . . . 5 Server Layer . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Client Layer . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Tivoli Netcool Performance Manager for Wireless Server Architecture - The Core Framework . . . . 8 Technology Packs . . . . . . . . . . . . . . . . . . . . . . 8 Extraction, Transformation and Loading (ETL) Data Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Tivoli Netcool Performance Manager for Wireless Application Framework . . . . . . . . . . 9 Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Client Operation Functions . . . . . . . . . . . . . . . 11 Server Operation Functions . . . . . . . . . . . . . . . . 13 Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Install Summary . . . . . . . . . . . . . . . . . Datasource setup . . . . . . . . . . . . . . . . . . . . . . . . LDAP - Directory Server setup . . . . . . . . . . . . . Crontab setup . . . . . . . . . . . . . . . . . . . . . . . . . . Virtuo User setup . . . . . . . . . . . . . . . . . . . . . Root User Setup . . . . . . . . . . . . . . . . . . . . . . Additional entries and scripts . . . . . . . . . . . . SAP setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP configuration . . . . . . . . . . . . . . . . . . . . Starting and Stopping Tivoli Netcool Performance Manager for Wireless . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Oracle Database . . . . . . . . . . . . . Stopping the Oracle Database . . . . . . . . . . . . Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Directory Server . . . . . . . . . . . . Stopping the Directory Server . . . . . . . . . . . 15 15 16 16 16 17 17 18 18 19 19 23 23 24 24 24 24 24 24
Process Monitor . . . . . . . . . . . . . . . . . . . . . . . . . 24 Starting the Process Monitor . . . . . . . . . . . . . 24 Stopping the Process Monitor . . . . . . . . . . . . 25 Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . 25 Starting the Process Manager . . . . . . . . . . . . 25 Stopping the Process Manager . . . . . . . . . . . . 25 Tivoli Netcool Performance Manager for Wireless 25 Starting Tivoli Netcool Performance Manager for Wireless . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Stopping Tivoli Netcool Performance Manager for Wireless . . . . . . . . . . . . . . . . . . . . . . . . . . 26 NetworkAssure Complete startup and shutdown 26 NetworkAssure Complete Startup . . . . . . . . . 26 Tivoli Netcool Performance Manager for Wireless Complete Shut down . . . . . . . . . . . . . . . . 27 5 Tivoli Netcool Performance Manager for Wireless Application Administration . . . 29 User Administration . . . . . . . . . . . . . . . . . . . . . . 30 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 User Administration Basics . . . . . . . . . . . . . . . . 31 Tivoli Netcool Performance Manager for Wireless Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 User Management . . . . . . . . . . . . . . . . . . . . . . . 36 Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . 36 Editing Users . . . . . . . . . . . . . . . . . . . . . . . . . 37 Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . 37 Creating and Deleting Groups . . . . . . . . . . . . 38 Adding and Removing Users to/from Groups 39 Assigning and de-assigning Users to/from a Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Role Management . . . . . . . . . . . . . . . . . . . . . . . 40 Creating and Deleting Roles . . . . . . . . . . . . . 40 Assigning/De-assigning Privileges to a Role 41 User Administration Command Line Tool . . . . . 42 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Listing Users . . . . . . . . . . . . . . . . . . . . . . . . . 43 Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . 43 Modifying a Users password . . . . . . . . . . . . 44 Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . 44 Tivoli Netcool Performance Manager for Wireless Operations Tasks . . . . . . . . . . . 45 Daily Loader Operations Tasks . . . . . . . . . . . . . 45 Checking Loader Status . . . . . . . . . . . . . . . . . 45 Checking for bad files . . . . . . . . . . . . . . . . . . 46 Loader Housekeeping . . . . . . . . . . . . . . . . . . . . . 49 Disk Space Usage . . . . . . . . . . . . . . . . . . . . . 49 Checking TFP_SHM_MIN_SIZE. . . . . . . . . . . . 49
iii
Copyright IBM Corp. 2008
TFP_NC_STABILITY . . . . . . . . . . . . . . . . . . . . 51 7 Datasource, Agent and KPI Cache Administration . . . . . . . . . . . . . . . . . . . . . 53 Datasource Administration . . . . . . . . . . . . . . . . 54 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Listing Datasources . . . . . . . . . . . . . . . . . . . . 55 Activating a Datasource . . . . . . . . . . . . . . . . 55 Deactivating a Datasource . . . . . . . . . . . . . . 55 Agent Maintenance . . . . . . . . . . . . . . . . . . . . . . 56 Overview of Agent Activities . . . . . . . . . . . . 56 Agent activities and log files . . . . . . . . . . . . . 58 agent_admin Command Line Tool . . . . . . . . 58 KPI Cache Management . . . . . . . . . . . . . . . . . . 65 Exporting User Defined Calculations . . . . . . 65 Importing User Defined Calculations . . . . . . 65 Synchronize internal computation engine KPI cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 System Maintenance . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Administration . . . . . . . . . . . . . . . . . . Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling System Maintenance . . . . . . . . . Listing the Status of All Scheduled Jobs . . . Administrative Options for schedule_admin Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting on the Server Status . . . . . . . . . . . . . Database Check . . . . . . . . . . . . . . . . . . . . . . . Listener Check . . . . . . . . . . . . . . . . . . . . . . . Directory Server Check . . . . . . . . . . . . . . . . . SAPMON Check . . . . . . . . . . . . . . . . . . . . . . Tivoli Netcool Performance Manager for Wireless Check . . . . . . . . . . . . . . . . . . . . . . . Log Files Check . . . . . . . . . . . . . . . . . . . . . . Database Monitoring . . . . . . . . . . . . . . . . . . . Unix System Monitoring . . . . . . . . . . . . . . . . CPU Sanity Check . . . . . . . . . . . . . . . . . . . . Managing the Oracle Database . . . . . . . . . . . . . Starting and Stopping the Oracle Database . Types of Oracle Backups . . . . . . . . . . . . . . . Completing an Online Backup . . . . . . . . . . . Completing an Offline Backup . . . . . . . . . . . Exporting Oracle Data . . . . . . . . . . . . . . . . . Importing Oracle Data . . . . . . . . . . . . . . . . . Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving Redo Logs . . . . . . . . . . . . . . . . . . Performing Hardware Diagnostics . . . . . . . . Restoring Data From Backups . . . . . . . . . . . Database Space Management . . . . . . . . . . . . . . Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Oracle Tablespaces . . . . . . . . . . 69 69 70 70 71 72 72 73 75 75 75 75 76 76 76 77 77 78 79 79 80 82 83 83 84 85 86 88 88 89 89 89
Increasing Tablespace Size . . . . . . . . . . . . . . 91 Recover from a Full Tablespace . . . . . . . . . . 92 Partition Maintenance . . . . . . . . . . . . . . . . . . . . 93 Partition Maintenance Jobs . . . . . . . . . . . . . . 93 Partition Maintenance Command Line Tool . 93 Adding Partitions . . . . . . . . . . . . . . . . . . . . . . 96 Deleting Partitions . . . . . . . . . . . . . . . . . . . . . 96 Pinning Partitions . . . . . . . . . . . . . . . . . . . . . 97 Unpinning Partitions . . . . . . . . . . . . . . . . . . . 97 Exporting Partitions . . . . . . . . . . . . . . . . . . . . 97 Importing Partitions . . . . . . . . . . . . . . . . . . . . 98 Showing Parameters . . . . . . . . . . . . . . . . . . . 98 Listing Parameters . . . . . . . . . . . . . . . . . . . . . 98 Updating Parameters . . . . . . . . . . . . . . . . . . . 98 Listing Partitions . . . . . . . . . . . . . . . . . . . . . . 99 List Pinned Partitions . . . . . . . . . . . . . . . . . . 99 List Sessions . . . . . . . . . . . . . . . . . . . . . . . . . 99 Update Sessions . . . . . . . . . . . . . . . . . . . . . . . 99 List Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Show Logs . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Show Errors . . . . . . . . . . . . . . . . . . . . . . . . . 100 Show Status . . . . . . . . . . . . . . . . . . . . . . . . . 100 Managing Disk Space Usage . . . . . . . . . . . . . . 101 Monitoring the Oracle Storage Directories . 101 Monitoring the $WMCROOT/logs Directories . 101 Monitoring the $WMCROOT/var/loader/spool Directories . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Reporting the Size of the File systems . . . . 102 Backing up the File System . . . . . . . . . . . . . . . 103 Working with Log Files . . . . . . . . . . . . . . . . . . 104 Information about Log Files . . . . . . . . . . . . 104 Removing Log Files . . . . . . . . . . . . . . . . . . 106 Archiving Log Files . . . . . . . . . . . . . . . . . . . 106 9 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Importing and Exporting User Documents and Report Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Importing definitions, templates, schedules and folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Exporting definitions, templates and schedules 111 Importing report results . . . . . . . . . . . . . . . . 112 Exporting report results . . . . . . . . . . . . . . . . 114 Time Zone Support for Reporting . . . . . . . . . . 115 About Daylight Saving Time Rules . . . . . . 115 About Time Zone Regions . . . . . . . . . . . . . 118 Holiday Maintenance . . . . . . . . . . . . . . . . . . . . 122 List holidays . . . . . . . . . . . . . . . . . . . . . . . . 122 Add holidays . . . . . . . . . . . . . . . . . . . . . . . . 123 Delete holidays . . . . . . . . . . . . . . . . . . . . . . 123
iv
Tivoli Netcool Performance Manager for Wireless: Administration Guide
Data Availability . . . . . . . . . . . . . . . . . . . . . . . 124 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 10 LCM Administration . . . . . . . . . . . . . . . . 127 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Loader Configuration . . . . . . . . . . . . . . . . . 128 Loader Datasource . . . . . . . . . . . . . . . . . . . 128 NC Relations . . . . . . . . . . . . . . . . . . . . . . . . 128 Data availability . . . . . . . . . . . . . . . . . . . . . 128 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Listing information for Datasources and Loader Configurations . . . . . . . . . . . . . . . . . . . . . . . . . 131 Listing Loader Datasources . . . . . . . . . . . . 131 Listing Loader Configurations . . . . . . . . . . 131 Listing Datasources and Loader Configurations 132 Load Datasources, Loader Configurations, NC Relations and Data Availability . . . . . . . . . . . . 132 Loading a Datasource from XML . . . . . . . . 132 Loading a custom Datasource from XML . 133 Loading a Loader Configuration from XML 133 Loading NC Relations from XML . . . . . . . 133 Loading Data Availability from XML . . . . 134 Merging of Data Availability blocks from XML 134 Unload Datasources, Loader Configurations and NC Relations. . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Unloading a Datasource to XML . . . . . . . . 134 Unloading a custom Datasource to XML . . 135 Unloading a Loader Configuration to XML 135 Unloading NC Relations to XML . . . . . . . . 135 Unloading Data Availability to XML . . . . . 136 Delete Datasources, Loader Configurations and NC Relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Deleting a Loader Configuration . . . . . . . . 137 Deleting NC Relations . . . . . . . . . . . . . . . . 137 Re-reading a Datasource . . . . . . . . . . . . . . . 138 11 SBH Administration . . . . . . . . . . . . . . . . 139 Usage for Stored Busy Hour CLI . . . . . . . . . . . 139 Import Stored Busy Hour definition(s) . . . . 139 Export Stored Busy Hour definition(s) or values 140 List SBH definitions . . . . . . . . . . . . . . . . . . 140 Execute SBH definition(s) . . . . . . . . . . . . . 141 Delete SBH definition(s) . . . . . . . . . . . . . . . 141 Enable/Disable calculation of Late Data for all Busy Hour definitions . . . . . . . . . . . . . . . . . 141 12 Alarm Administration . . . . . . . . . . . . . . 143 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Document contexts . . . . . . . . . . . . . . . . . . . 144 Alarm Template XML Documents . . . . . . . 144
Version Numbering . . . . . . . . . . . . . . . . . . . 144 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Manage Document Contexts . . . . . . . . . . . . . . . 145 Creating a Document Context . . . . . . . . . . . 146 Removing a Document Context . . . . . . . . . 146 List Alarm Templates . . . . . . . . . . . . . . . . . . . . 148 Load an Alarm Template. . . . . . . . . . . . . . . . . . 148 Drop an Alarm Template . . . . . . . . . . . . . . . . . 149 Unload an Alarm Template to a File . . . . . . . . 149 13 The Summarizer and Summary Administration . . . . . . . . . . . . . . . . . . . . 151 Summarizer . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Switching ON/OFF the summary process . . 152 Summary Log file . . . . . . . . . . . . . . . . . . . . 152 Start day of week . . . . . . . . . . . . . . . . . . . . . 154 Summary grace period . . . . . . . . . . . . . . . . . 154 Summarizing Old Loaded Data . . . . . . . . . . 155 summary_admin CLI . . . . . . . . . . . . . . . . . . . . 155 Provisioning a summary . . . . . . . . . . . . . . . 155 Deleting a summary definition . . . . . . . . . . 157 Running a provisioned summary . . . . . . . . . 157 Changing the number of instances . . . . . . . . 158 Exporting summary metadata . . . . . . . . . . . 158 Listing summary definitions . . . . . . . . . . . . 159 14 Technology pack administration tools . 161 The techpack_admin tool . . . . . . . . . . . . . . . . . 161 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Applying a technology pack . . . . . . . . . . . . . . . 162 Exporting lists of dependencies. . . . . . . . . . . . . 162 Patching a technology pack . . . . . . . . . . . . . . . 163 Listing technology pack modules . . . . . . . . . . . 163 Uninstalling a technology pack, and loaders. . . 163 Standard technology pack . . . . . . . . . . . . . . 163 Loader configurations . . . . . . . . . . . . . . . . . 164 Dependent technology packs . . . . . . . . . . . . 164 Displaying help . . . . . . . . . . . . . . . . . . . . . . . . . 165 The techpack_custom tool. . . . . . . . . . . . . . . . . 165 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Option -a . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Option -s . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Appendix A: Problem Resolution and Errors . . . . . . . . . . . . . . . . . . . . 167 Appendix B: Notices and Trademarks . . . . 171
vi
About This Documentation
The Administration Guide provides instructions and general information on how to maintain and support Tivoli Netcool Performance Manager for Wireless. This guide was last updated February 8, 2008 8:17 pm.
1.1
Audience
This guide is intended for experienced system administrators, database administrators or other professionals who are responsible for maintaining a Tivoli Netcool Performance Manager for Wireless installation.
1.2
Required Skills and Knowledge

Oracle database software UNIX basics (such as file structures, text editing, and permissions) A UNIX-based text editor, such as vi or emacs. UNIX system administration.
This guide assumes you are familiar with the following:
This guide also assumes that you are familiar with your companys network and with procedures for configuring, monitoring, and solving problems on your network.
1.3
Document Conventions
Table 1:
Format Examples
This document uses the typographical conventions shown in the following table:
General Document Conventions
Description
ALL UPPERCASE
GPS NULL MYWEBSERVER
Acronyms, device names, logical operators, registry keys, and some data structures.
Table 1:
Format Examples
General Document Conventions (Continued)

Description
Underscore
See Document Conventions
For links within a document or to the Internet. Note that TOC and index links are not underscored. Color of text is determined by browser settings. Heading text for Notes, and Warnings. Any text that appears on the GUI.
Bold SMALL CAPS
Note: The busy hour determiner is... The STORED SQL dialog box... ...click VIEW... In the main GUI window, select the FILE menu, point to NEW, and then select TRAFFIC TEMPLATE. A busy hour is... A web server must be installed... See the User Guide
./wminstall $ cd /cdrom/cdrom0 /xml/dict http://java.sun.com/products/ addmsc.sh Type OK to continue. [root] # pkginfo | grep -i perl system Perl5 On-Line Manual Pages system Perl 5.005_03 (POD Documentation) system Perl 5.005_03 # cd <oracle_setup>
Italic
New terms, emphasis, and book titles.
Monospace
Code text, command line text, paths, scripts, and file names. Text written in the body of a paragraph that the user is expected to enter. For contrast in a code example to show lines the user is expected to enter.
Monospace Bold
<Mono-
space italics>
[square bracket] log-archiver.sh [-i][-w][-t]
Used in code examples: command-line variables that you replace with a real name or value. These are always marked with arrow brackets. Used in code examples: indicates options.
Note: Command prompts. The following shell command prompts can be seen throughout this document: # (hash): displayed if the user is logged in as user root. $ (dollar): displayed if the user is logged in as either the virtuo or oracle user.
1.3.1
Blank pages
Blank pages are used at the end of chapters to ensure the following chapter begins on an odd numbered page. These pages are intentionally blank. If the guide is printed double-sided and bound, each chapter will begin on a right-hand page.
1.4
Document Structure
Table 2:
Chapter
This document is organized in to the following chapters and appendices:

Document Structure
Description
Tivoli Netcool Performance Manager for Architecture overview. Wireless Architecture Overview Setup Tasks Starting and Stopping Tivoli Netcool Performance Manager for Wireless Tasks accomplished as part of the installation of Tivoli Netcool Performance Manager for Wireless. Starting and stopping Tivoli Netcool Performance Manager for Wireless, and Tivoli Netcool Performance Manager for Wireless processes.
Tivoli Netcool Performance Manager for Maintaining users, roles and privileges. Wireless Application Administration Tivoli Netcool Performance Manager for Daily loader operations tasks. Wireless Operations Tasks Datasource, Agent and KPI Cache Administration System Maintenance Datasource and agent administration. Scheduling maintenance, server status, maintaining tablespaces, partitions, disk spaces usage, file system backup and log files. Importing and exporting report definitions, time zone administration and holiday administration. Loader Configuration Manager Administration. Alarm administration tool.
Tools LCM Administration Alarm Administration
The Summarizer and Summary Adminis- The Summarizer component, and data summarization process. tration Technology pack administration tools Problem Resolution and Errors Technology pack administration. Problem resolution.
1.5
User Publications
Tivoli Netcool Performance Manager for Wireless software provides the following user publications in HTML or Adobe Portable Document Format (PDF) formats.
Table 3:
Document
Tivoli Netcool Performance Manager for Wireless User Documentation

Description
Installation Guide Upgrade Guide
Instructions for installing and configuring the Tivoli Netcool Performance Manager for Wireless software. Instructions for upgrading Tivoli Netcool Performance Manager for Wireless software.
About This Documentation 3
Table 3:
Document
Tivoli Netcool Performance Manager for Wireless User Documentation (Continued)

Description
Administration Guide User Guide
Provides instructions and general information on how to maintain and support Tivoli Netcool Performance Manager for Wireless. Provides conceptual information and procedures for using Tivoli Netcool Performance Manager for Wireless software for performance, trending analysis and performance alarms. Provides information and procedures for using Tivoli Netcool Performance Manager for Wireless software for performance, trending analysis and performance alarms.
Online Help
1.5.1
Viewing the Online Help
You can view Online Help for the Tivoli Netcool Performance Manager for Wireless Web client. Using the Tivoli Netcool Performance Manager for Wireless user interface, you can select HELP tabs or the HELP links for context-sensitive Help.
1.5.2
Viewing the Publications in PDF
To open a PDF file you need Adobe Acrobat Reader. If you do not have Adobe Acrobat Reader you can download a copy free of charge from the Adobe Web site. For more details about Acrobat Reader, see the Adobe Web site http://www.adobe.com/ .
2
2.1
Tivoli Netcool Performance Manager for Wireless Architecture Overview

Introduction
The Tivoli Netcool Performance Manager for Wireless system is comprised of the Tivoli Netcool Performance Manager for Wireless Server and a Client layer. The Client layer is a web-based user interface to the Tivoli Netcool Performance Manager for Wireless Server. The Tivoli Netcool Performance Manager for Wireless Server is used to connect a Tivoli Netcool Performance Manager for Wireless user to the datasource. The Tivoli Netcool Performance Manager for Wireless Server manages the core framework which is the basis of the Tivoli Netcool Performance Manager for Wireless product. Tivoli Netcool Performance Manager for Wireless provides important metrics which are essential in helping manage network infrastructure. Tivoli Netcool Performance Manager for Wireless supports the following: Network Quality Management Reporting key performance indicators (KPIs). Performance Optimization Monitoring daily and hourly performances. Isolating, analyzing and resolving problems affecting service.
2.1.1
Listing current software versions
It is possible to list the current software versions for installed Tivoli Netcool Performance Manager for Wireless software. To list currently installed software versions, as user virtuo:
sw_version
Example output:
-------------------------Installed Virtuo software: -------------------------Modules: vallent-vt-common, Virtuo, NA9.1.1.12.03
vallent-vt-jre, Virtuo, NA9.1.1.12.03 vallent-vt-ant, Virtuo, NA9.1.1.12.03 vallent-vt-java-libs, Virtuo, NA9.1.1.12.03 vallent-vt-as-core, Virtuo, NA9.1.1.12.03 vallent-vt-core, Virtuo, NA9.1.1.12.03 vallent-vt-ds-conf, Virtuo, NA9.1.1.12.03 vallent-vt-db-install, Virtuo, NA9.1.1.12.03 vallent-vt-db-conf, Virtuo, NA9.1.1.12.03 vallent-vt-tao, Virtuo, NA9.1.1.12.03 vallent-vt-xerces, Virtuo, NA9.1.1.12.03 vallent-vt-alarms, Virtuo, NA9.1.1.12.03 Gateways: vallent-vt-gway-ascii-gateway, ascii-gateway, 3.3.0.1 vallent-vt-gway-csv-gateway, csv-gateway, 3.3.0.2 vallent-vt-gway-ericsson-mgw-r4.1-xml, ericsson-mgw-r4.1-xml, 3.3.0.2 vallent-vt-gway-gateway-framework, gateway-framework, 3.3.0.5 vallent-vt-gway-xml-3gpp, xml-3gpp, 3.3.0.1 Techpacks: vallent-vt-Neutral_CDMA_BSS_NSS_GOM, Virtuo, 1.0 vallent-vt-Neutral_Core_GOM, Virtuo, 1.0 vallent-vt-Neutral_GPRS_BSS_GOM, Virtuo, 1.0 vallent-vt-Neutral_GPRS_UMTS_CN_GOM, Virtuo, 1.0 vallent-vt-Neutral_GSM_BSS_NSS_GOM, Virtuo, 1.0 vallent-vt-Neutral_UMTS_UTRAN_GOM, Virtuo, 1.0
2.1.2
Server Layer
Depending on the Server(s) configuration during installation, subsystems of the Server architecture may be deployed across several Servers. For example, the database and loading activities may reside on the Database Server, whilst the mediation and the remainder of the application framework may be on another Server. The NetworkAssure Server consists of the following subsystems: Mediation services. See Gateways and the Data Administration Tool on page 9. NetworkAssure Application framework. See Tivoli Netcool Performance Manager for Wireless Application Framework on page 9. Platform Management Services. See Platform Management Services on page 10. User management services. See User Management Services on page 11. Database services. See Database Services on page 11.
Figure 1:
Tivoli Netcool Performance Manager for Wireless Server
2.1.3
Client Layer
The client access layer is a subsystem of the JBoss Server. It is the web/HTML page Server that provides the static and dynamic content for the web-based client user interface. This web-based user interface is used for creating and running performance reports based on data collected in a datasource.
Tivoli Netcool Performance Manager for Wireless Architecture Overview 7
2.2
Tivoli Netcool Performance Manager for Wireless Server Architecture - The Core Framework
The core framework or core product, forms the basis of performance management. The core product includes software modules essential to the basic functioning of the Tivoli Netcool Performance Manager for Wireless performance management solution. The following diagram shows a simplified view of the core framework.
Figure 2: NetworkAssure - The Core Framework
2.2.1
Technology Packs
Technology packs are software layers that represent a particular type of technology. Technology packs allows the core framework to be applied to any underlying network technology. They are plug-and-play modules that enable the management of a specific network technology or service. The following is a list of example technology packs: GSM GPRS CDMA UMTS EVDO IP There is no tight integration between core functionality and technology packs. Technology packs can be added, upgraded and removed independently.
2.2.2
Extraction, Transformation and Loading (ETL) Data Layer
Gateways and the Data Administration Tool Gateways and the data administration tool are used to transfer, parse and manipulate incoming performance data received from network elements, converting the data into a common loader format. The main output of this process is the production of a .lif file for loading into the database. Gateways prepare the data for performance reporting, enabling high performance data loading. Loaders Loaders manage the loading of data into the Oracle database. Tivoli Netcool Performance Manager for Wireless functions with a diverse range of network technologies and therefore a wide range of network element types. Data from these diverse sources is applied in a range of formats. Before the data can be loaded into the Oracle database it must be reformatted into a standard format that the loader processes recognizes. On a Tivoli Netcool Performance Manager for Wireless system there may be a number of loaders running for a number of technologies. The loader process runs constantly taking data from the loader spool directories and loading it into the performance database. Loader Configuration Manager The loader configuration manager provides a service to ensure the correct loaders are used to populate the database for any given managed element file. The loader configuration manager is simply a mapping tool to ensure that during installation all relevant technology pack and loader xml files are used to accurately populate the following tables in the database: lc_relations - which defines the necessary network hierarchical relationships. lc_loadmaps - which defines the load mapping of blocks of data for a specific ruleset to tables in the database. lc_ruleset - which uniquely characterizes a set of data for a particular technology and vendor, and associates this with the actual spool directory that the associated data can be retrieved from. These tables are used to configure and associate the loaders with the applicable database tables and vendor-technology files, for accurate population of the database. Figure 1 illustrates the flow of data.
2.2.3
Tivoli Netcool Performance Manager for Wireless Application Framework
The Tivoli Netcool Performance Manager for Wireless application framework operates on a layer between the NetworkAssure database and the Tivoli Netcool Performance Manager for Wireless web client. The application framework components: Input data in the database. Retrieve and cache data from the database upon user request. Serve pages to the web client interface for use by the user. Manage schedules and services to maintain the database. Manage schedules and services related to user report generation.
2.2.4
Summaries
Tivoli Netcool Performance Manager for Wireless supports the following functionality: Processing of summaries can be switched on and off. If summaries are switched on they will run if they are switched off they will not run. A Summary log file is written to the appserver log file directory in $WMCROOT/logs/as/default and the name of the log file is as-summary.log. The log file contains the following information: Details on whether the summary process is switched on or off. The start time for the summary process. Details on summaries that have run in the past including how many rows were processed by the summary. The end time for the summary process. The start day of the week can be set. The start day of the week can vary depending on the geographical location. The summary process allows you to set the start day of the week to the day the user requires. The summarizer will summarize old loaded data automatically. When the summarizer process is started it detects whether old loaded data is loaded into the system. Data is defined as old loaded data if it is older than 1 day. If the old loaded data has already being summarized then it will be re-summarized and the old summary data is deleted and the new summary data is populated in the summary table. If the old loaded data is older than 1 week or 1 month it will cause weekly and monthly summaries to be re-calculated respectively.
2.2.5
Services
Platform Management Services The platform management services are comprised of several process utilities that work together to set up, control and monitor the NetworkAssure application Server. These tools are installed on the NetworkAssure Server and run from a Korn shell. sapmon - This is the parent utility process to the application server process. It is responsible for the startup and control of the NetworkAssure application framework. sapmgr The process framework manager that registers all NetworkAssure processes including the application server and the loaders. sap The utility used to display the status. It is also used to start and stop the registered processes. Business Services The business services are the core of the Tivoli Netcool Performance Manager for Wireless application. These services provide application access and maintenance capabilities. The following is a list of the business services: Application server - The application Server consists of the JBoss application Server used by Tivoli Netcool Performance Manager for Wireless to communicate with an LDAP Server and the datasource to generate reports.
10 Tivoli Netcool Performance Manager for Wireless: Administration Guide
Agent framework and agents - The agent framework provides agents that gather information about the datasource and the information necessary to define a report. Dynamic SQL Generator - The SQL generator creates queries to collect the performance data per the report definition. User Management Services User management is supported by an LDAP Server and a dedicated user management Web-based interface. The LDAP Server provides the framework for implementation of roles, groups and users for Tivoli Netcool Performance Manager for Wireless through a single sign-on authentication. Database Services The Tivoli Netcool Performance Manager for Wireless web client accesses data stored in the database on the applicable Tivoli Netcool Performance Manager for Wireless database Server. Data is stored in an Oracle Relational Database Management System (RDBMS), version 10g. This data includes: Performance measurements Configuration information Database-utilization information from the infrastructure equipment. For example: The data loading formula and report definitions. Timetables used for scheduling reports, summarizing data, archiving data and performing automated management tasks. Configuration data for the NetworkAssure application.
2.3
Client Operation Functions
Administrators use the web-based Client user interface to complete and monitor the following: User Management Adding and deleting users. Modifying user access to the database. Modifying data within the application. Alarm Management Defining alarm templates and definitions to provide alarm events to users. Reporting Creating new reports. Interactive data access - Viewing charts or raw data directly in the browser interface. Charting - Viewing time-series charts by entities or fields
Drill-down - Viewing rolled-up data at a high level in the hierarchy and examining details lower in the hierarchy when it is required. Add charts to the workspace with the content created from saved reports. Easily includes configuration and performance data in the same report. It can create and visualize end-to-end KPIs called User Defined Computations (UDCs). Exporting data, for example, data in CSV or Excel sheets for further analysis. Monitoring report jobs and tasks running on the Server. Downloading report results. Scheduling reports to run on a custom schedule. Supporting flexible time zone capabilities. Report Vault The report vault provides hierarchical structure which can be user defined for storing report output.It supports the following: A single report repository for easy access to corporate reports. If users have the appropriate permissions they can publish reports in the vault. Report directories which are easy to create and navigate. Report Grouping by any attribute of the entities. The ones mainly used are market, region, technology and time periods. Defining standard corporate reports Report Types The following is a list of report types supported by Tivoli Netcool Performance Manager for Wireless: Comprehensive - which details granular data such as hourly results. It also details aggregated totals. Busy hour - Provides the greatest value for a performance metric over a defined period of time. For example: The busiest hour of the day, week or month Ranking - Display the top n or bottom n values only for a data set. For example: The network element performing the best for any performance measurement. The network element performing the worst for any performance measurement. N-High Busy Hour Reports - Highlights a range of the busiest hours or the busiest days Filtered N-High Busy Hour Reports - allows the user to filter N-High busy hour data according to the values of specific variables.
12
2.4
Server Operation Functions
Command line tools and UNIX commands are used to complete the following tasks on the application Server. Monitoring application processes - sap Starting and stopping NetworkAssure - sapmon, sapmgr, sap Maintaining schedules - schedule_admin Monitoring and maintaining database partitions - schedule_admin, part_admin Monitoring agent framework (jboss) activities - review logs, agent_admin Monitoring the health of the server and its subsystems - various unix commands Configuring parameters for user use - holiday_admin, user_admin, tz_admin, alarm_admin
14
3
3.1
Setup Tasks
This chapter describes a number of tasks that will have been performed as part of the installation of Tivoli Netcool Performance Manager for Wireless. You do not need to perform these tasks again, they are described for information purposes.
Overview
Software install summary Datasources LDAP setup Crontab setup SAP
Setup tasks include:
15
3.2
Software Install Summary
The Tivoli Netcool Performance Manager for Wireless architecture is typically made up of four components, each with specific functions: The Application Component consists of the Tivoli Netcool Performance Manager for Wireless software which is used to run a Tivoli Netcool Performance Manager for Wireless framework The Gateway Component deals with the processing of data which is downloaded from datasources The Database Component consists of an Oracle Database which Tivoli Netcool Performance Manager for Wireless uses to store data The Client PC is used to run the Tivoli Netcool Performance Manager for Wireless GUI. Components can be installed on a single server or distributed over several machines. For example, a single server could be used for the Application, Gateway and Database Components, or these three components could be split over three servers. The installation of Tivoli Netcool Performance Manager for Wireless includes a number of tasks. The following table lists the main installation tasks. Table 4: Tivoli Netcool Performance Manager for Wireless Installation
Task Description
User and Group Accounts Creation Tivoli Netcool Performance Manager for Wireless Software Installation Tivoli Netcool Performance Manager for Wireless Gateway Installation Tivoli Netcool Performance Manager for Wireless Technology Pack Installation Cronjob Installation
User and group accounts creation. Installing Virtuo and required third party products. Deploying gateway packages. Installing technology packs. Installing cronjobs.
Configuring and Starting Tivoli Netcool Per- Configuring and starting Virtuo. formance Manager for Wireless
3.3
Datasource setup
Datasources provide Tivoli Netcool Performance Manager for Wireless with the necessary performance data for reports. Datasources are typically servers that contain entity and performance data information. For more information on Datasources see Datasource, Agent and KPI Cache Administration on page 53.
3.4
LDAP - Directory Server setup
The LDAP server is a third-party application that is used as a directory service to manage users, roles, and privileges.
The LDAP server is installed as a pre-requisite to the installation of Tivoli Netcool Performance Manager for Wireless. For information on starting and stopping the LDAP server see Directory Server on page 24. The LDAP server needs to be started to allow users to login through the Tivoli Netcool Performance Manager for Wireless GUI. Tivoli Netcool Performance Manager for Wireless users, privileges, roles and groups can be altered/ created through the GUI. See Tivoli Netcool Performance Manager for Wireless Application Administration on page 29.
3.5
Crontab setup
The crontab setup is installed and set up as part of the main Tivoli Netcool Performance Manager for Wireless installation. The crontab is installed using the following script:
/appl/virtuo/admin/common/install/scripts/cron_install
Note: See the Tivoli Netcool Performance Manager for Wireless Installation Guide for more information on installing Cron. The installation sets up the virtuo and root user scheduled Cron tasks. There are two different Cron setups installed for the two different users: virtuo user cron setup root user cron setup The installation uses the following two crontab files to setup the virtuo and root user crontab list.
$WMCROOT/admin/common/cron/core_root_crontab $WMCROOT/admin/common/cron/core_virtuo_crontab
3.5.1
Virtuo User setup
The following is a sample default crontab list for a Tivoli Netcool Performance Manager for Wireless basic installation. As user virtuo:
crontab -l 0 1 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 31 /data/trace_archive1 \*.log.\* 0 1 * * * /appl/virtuo/admin/common/cron/cron_script -a -d 0 /data/trace_log1 \*.log.\* /data/trace_archive1 0 3 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /appl/virtuo/tomcat/ logs vt\*.log
Setup Tasks 17
0 0 * * * /appl/virtuo/admin/common/cron/cron_script -c -d 512 /appl/virtuo/logs/ loader virtuo_loader.log 30 0 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/logs/ loader/CHOPPED virtuo_loader.log-\* 0 2 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/var/ loader/bad PDO_\* 10 2 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/var/ loader/dat PDO_\* 20 2 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/var/ loader/log PDO_\*.log
3.5.2
Root User Setup
The following is a sample default crontab list for a Tivoli Netcool Performance Manager for Wireless basic installation. Note: Some environments will have additional entries. As user root:
crontab -l 0 23 * * * /appl/virtuo/admin/oracle/cron/roll_listener_log 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /var/cron log.\* 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /var/cron olog.\* 0 23 * * * /appl/virtuo/admin/common/cron/roll_cron_log 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /appl/oracle/product/9.2.0/network/log listener.log.\* 0 10,16,23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 1 /oradump/vtdb vtdb_arch_\* 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /appl/virtuo/ds/ slapd-`/usr/bin/hostname`/logs access.\* 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /appl/virtuo/ds/ slapd-`/usr/bin/hostname`/logs errors.\*
3.5.3
Additional entries and scripts
The following script is also available:

0 2 * * * /appl/virtuo/admin/common/cron/archive_loader_data -wmcr /appl/virtuo
This scripts archives .lif data files (files produced by the gateways and processed by the loaders in large volumes). Crontab entries can be added if more scripts are written or more log files are generated. Cron entries are added by editing the cron list using crontab -e The following files are the generated cron files - these are the files that are changed using crontab -e for root and virtuo users:
18
/var/spool/cron/crontabs/virtuo /var/spool/cron/crontabs/root
3.6
SAP setup
SAP is a process management utility consisting of a process manager and monitor. The Process Monitor manages the restart ability of Tivoli Netcool Performance Manager for Wireless. The Process Manager registers all the Tivoli Netcool Performance Manager for Wireless processes. SAP scripts are installed under $WMCROOT/bin as part of the core installation. The SAP manager and framework is started using the following commands, as user root:
svcadm enable sapmon-na svcadm enable sapmgr-na
For more information on starting and stopping SAP utilities see Process Monitor on page 24 and Process Manager on page 25. Tivoli Netcool Performance Manager for Wireless processes are started using the following command:
svcadm enable sap-na
Individual processes can be started using:

svcadm enable <process_name>-na
Information on processes can be displayed using:

sap disp
or sap disp -l (verbose output) Producing the following example output:

NAME as loadcdmanortelevdor3 STATE STARTED stopped SINCE Sep 15, 2006 -
3.6.1
SAP configuration
The NetworkAssure processes are automatically configured in SAP following core installation. The SAP tool uses property files to start the application server and configured loaders. These files are stored in the following locations
$WMCROOT/conf/processes/*.properties
The following is a sample application server property file:

# # application server # com.comnitel.process.as.exec=@{WMCROOT}/bin/run_as com.comnitel.process.as.params=
Setup Tasks 19
com.comnitel.process.as.group=asgroup com.comnitel.process.as.start.pmgtprovider=false com.comnitel.process.as.host=${WMCHOST} com.comnitel.process.as.start.sequence=1
Table 5:
Variables
Application Server Property File - Variable Descriptions

Description
com.comnitel.process.as.exec=@{WMCROOT}/bin/ run_as com.comnitel.process.as.params= com.comnitel.process.as.group=asgroup
Describes the command that is executed when the user executes sap start. The space separated command line arguments for the process. The variable is optional. Describes the group of processes that this process belongs to. As well as using sap start <process name>, it is possible to start a group by using sap start <group name>. The variable is optional.
com.comnitel.proDefines whether or not the process make callbacks cess.as.start.pmgtprovider=false to inform the framework of its init states. The vari-
able is optional and defaults to true.

com.comnitel.process.as.host=${WMCHOST} com.comnitel.process.as.start.sequence=1
Defines the name of the Server that this process is executed on. Defines the order in which processes are started. The numbers must be sequential. If more than one process is given the same sequence number the user will not know which process started first. This also applies to the default value of 0. If two processes are allowed to use the default value of 0 the user will not know which process started first. The variable is optional.
The following is a sample loader property file:

com.comnitel.process.loadcdmanortelevdor3.exec=\@{WMCROOT}/bin/run_loader com.comnitel.process.loadcdmanortelevdor3.params=cdmanortelevdor3 com.comnitel.process.loadcdmanortelevdor3.group=loadcdmanortelevdor3 com.comnitel.process.loadcdmanortelevdor3.host=\${WMCHOST} com.comnitel.process.loadcdmanortelevdor3.start.pmgtprovider=false com.comnitel.process.loadcdmanortelevdor3.start.sequence=101 com.comnitel.process.loadcdmanortelevdor3.start.timeout=30000
20
Table 6:
Variables
Loader Property File - Variable Descriptions

Description
com.comnitel.proDescribes the command that is executed when the cess.loadcdmanortelevdor3.exec=\ users starts the loader cdmanortelevdor3. @{WMCROOT}/bin/run_loader com.comnitel.proThe name of the loader is cdmanortelevdor3. cess.loadcdmanortelevdor3.params =cdmanortelevdor3 com.comnitel.proThe group of processes to which the loader belongs. cess.loadcdmanortelevdor3.group= loadcdmanortelevdor3 com.comnitel.proDefines the name of the Server that this process is cess.loadcdmanortelevdor3.host=\ executed on. ${WMCHOST} com.comnitel.proDefines whether or not the process make callbacks cess.loadcdmanortelevdor3.start. to inform the framework of its init states. The varipmgtprovider=false able is optional and defaults to true. com.comnitel.proDefines the order in which processes are started. . cess.loadcdmanortelevdor3.start. The actual numbers do not have to be sequential. If sequence=101 more than one process is given the same sequence
number the user will not know which process started first. The default value is 0 and this variable is optional.
com.comnitel.proDefines the timeout period i.e. length of time to wait cess.loadcdmanortelevdor3.start. to restart the loader if the loader fails to start. timeout=30000
Manual configuration of processes through SAP is not necessary.
Setup Tasks 21
22
4
4.1
Starting and Stopping Tivoli Netcool Performance Manager for Wireless
This chapter describes starting and stopping the NetworkAssure system.
Overview
Several applications must be running before the Tivoli Netcool Performance Manager for Wireless application can be started properly, these include: Oracle Database (LDAP) Directory Server (SAP) Process Monitor (SAP) Process Manager Once all these applications are running, Tivoli Netcool Performance Manager for Wireless can be started. All the processes are automatically started upon bootup. Bootup should take place as part of the installation of Tivoli Netcool Performance Manager for Wireless, see the Tivoli Netcool Performance Manager for Wireless Installation Guide for more information. For instructions on the complete startup and shutdown of Tivoli Netcool Performance Manager for Wireless and Tivoli Netcool Performance Manager for Wireless processes see NetworkAssure Complete startup and shutdown on page 26. Note: A number of status checks can be performed on Tivoli Netcool Performance Manager for Wireless applications and processes, see Reporting on the Server Status on page 75.
23
4.2
Oracle Database
Note: For additional details on manually starting and stopping Oracle using SQL*Plus and the oracle user see Starting and Stopping the Oracle Database on page 79.
4.2.1
Starting the Oracle Database
To start the Oracle Database: 1. Execute the following command as user root:
svcadm enable database-na
4.2.2
Stopping the Oracle Database
To stop the Oracle Database: Execute the following command as user root:
svcadm disable database-na
4.3
4.3.1
Directory Server
Starting the Directory Server
To start the LDAP Server: Execute the following command as user root:
svcadm enable ldap-na
4.3.2
Stopping the Directory Server
To stop the LDAP Server: Execute the following command as user root:
svcadm disable ldap-na
4.4
Process Monitor
The Process Monitor manages the restart ability of the application. Note: Distributed systems only. In a distributed environment the Process Monitor is only started on the Server containing the Application component.
4.4.1
Starting the Process Monitor
To start the Process Monitor: 1. Execute the following command as user root:
svcadm enable sapmon-na
4.4.2
Stopping the Process Monitor
To stop the Process Monitor: 1. Execute the following command as user root:
svcadm disable sapmon-na
4.5
Process Manager
The Process Manager registers all the Tivoli Netcool Performance Manager for Wireless processes. Note: Distributed systems only. In a distributed environment the Process Manager is only started on the Server containing the Application component.
4.5.1
Starting the Process Manager
To start the Process Manager, complete the following: 1. Execute the following command as user root:
svcadm enable sapmgr-na
4.5.2
Stopping the Process Manager
To stop the Process Manager, complete the following:

Execute
the following command as user root:
svcadm disable sapmgr-na
This command does not stop processes.
4.6
Tivoli Netcool Performance Manager for Wireless
Tivoli Netcool Performance Manager for Wireless is started and stopped using the sap command. The sap command starts and stops all registered processes. For instructions on the complete startup and shutdown of Tivoli Netcool Performance Manager for Wireless and Tivoli Netcool Performance Manager for Wireless processes, see NetworkAssure Complete startup and shutdown on page 26.
4.6.1
Starting Tivoli Netcool Performance Manager for Wireless
To start the Tivoli Netcool Performance Manager for Wireless application: 1. Execute the following command as user root:
It may take a few minutes to start all the processes.

Starting and Stopping Tivoli Netcool Performance Manager for Wireless 25
You can check the loader logs for startup issues:

$WMCROOT/logs/loader/
Log information from the application server is written to:

$WMCROOT/logs/as/
4.6.2
Stopping Tivoli Netcool Performance Manager for Wireless
To stop the Tivoli Netcool Performance Manager for Wireless application: 1. Execute the following command as user root:
svcadm disable sap-na
4.7
4.7.1
NetworkAssure Complete startup and shutdown

NetworkAssure Complete Startup
The following procedure starts the Oracle Database, the Directory Server, the Process Monitor, the Process Manager, and all Tivoli Netcool Performance Manager for Wireless processes. Note: If you do not need to start up the Oracle database or the Directory server ignore instructions relating to starting the Oracle database and Directory server.
Note: It is possible to start up all Tivoli Netcool Performance Manager for Wireless applications, the LDAP server and the database using a single command: svcadm enable database-na ldap-na sapmon-na sapmgr-na sap-na
Oracle Database Start the Oracle Database: 1. Execute the following command as user root on the Tivoli Netcool Performance Manager for Wireless Server(s):
svcadm enable database-na
Directory Server Start the Directory Server: 1. Execute the following command as user root on the Tivoli Netcool Performance Manager for Wireless Server(s):
svcadm enable ldap-na
26
Tivoli Netcool Performance Manager for Wireless Important: Distributed systems only. In a distributed system, this section should be performed only on the server hosting the Application component. 1. Execute the following commands to ensure SAP process management is running, and start the remaining Tivoli Netcool Performance Manager for Wireless processes.
svcadm enable sapmon-na svcadm enable sapmgr-na svcadm enable sap-na
It may take a few minutes to start all the processes. You can check the loader logs for startup issues:
$WMCROOT/logs/loader/
Log information from the application server is written to:

$WMCROOT/logs/as/
4.7.2
Tivoli Netcool Performance Manager for Wireless Complete Shut down
The following procedure shuts down Tivoli Netcool Performance Manager for Wireless, all processes, the Process Manager, the Process Monitor, the Directory Server and Oracle. Note: If you do not need to shut down the Oracle database or the Directory server ignore instructions relating to shutting down the Oracle database and Directory server.
Note: It is possible to shut down all Tivoli Netcool Performance Manager for Wireless applications, the LDAP server and the database using a single command: svcadm disable sap-na sapmgr-na sapmonna ldap-na database-na
NetworkAssure Important: Distributed systems only. In a distributed system, this section should be performed only on the server hosting the Application component. Shut down the system as follows: 1. Execute the following commands on the Tivoli Netcool Performance Manager for Wireless Server(s):
svcadm disable sapmon-na svcadm disable sapmgr-na svcadm disable sap-na
Starting and Stopping Tivoli Netcool Performance Manager for Wireless 27
Directory Server Shut down the Directory Server: 1. Execute the following commands on the Tivoli Netcool Performance Manager for Wireless Server(s) as user root:
svcadm disable ldap-na
Oracle Database Shut down the Oracle Database: 1. Execute the following commands on the Tivoli Netcool Performance Manager for Wireless Server(s) as user root:
svcadm disable database-na
28
Tivoli Netcool Performance Manager for Wireless Application Administration
This chapter describes Tivoli Netcool Performance Manager for Wireless application administration. Application administration This includes: user administration and access to the Tivoli Netcool Performance Manager for Wireless application.
29
5.1 5.2
User Administration Overview
The Tivoli Netcool Performance Manager for Wireless User Administration tool allows you to configure a wide range of ways for users to access Tivoli Netcool Performance Manager for Wireless using: users groups roles privileges
30
5.3
User Administration Basics
The Tivoli Netcool Performance Manager for Wireless User Administration tool is accessed from the Tivoli Netcool Performance Manager for Wireless GUI using the TOOLS tab, by selecting USER ADMINISTRATION from the drop-down list box.
Figure 3: User Administration
5.3.1
Tivoli Netcool Performance Manager for Wireless Users
Tivoli Netcool Performance Manager for Wireless users are those users in the LDAP repository that have been configured to use the Tivoli Netcool Performance Manager for Wireless application.
5.3.2
Groups
Groups are collections of users. Permission to access user documents such as reports is given to groups. Users can belong to more than one group. Tivoli Netcool Performance Manager for Wireless software includes a number of predefined groups, shown in the following table, which cannot be edited. You can also create your own groups.
Table 7:
Name Description
Predefined Groups
Admin Everybody
Used to group administrators together. A group that automatically contains all of the users defined by the system.
Tivoli Netcool Performance Manager for Wireless Application Administration 31
5.3.3
Roles
Roles are collections of privileges. Roles can contain other roles. Roles are assigned to users, not to groups. Tivoli Netcool Performance Manager for Wireless software includes a number of predefined roles, shown in the following table, which cannot be edited. You can also create your own roles. The total set of privileges that a user has is determined by the roles assigned to that user, and the privileges associated with those roles. You can view the privileges associated with a role. See Assigning/De-assigning Privileges to a Role on page 41 for information on how to determine the privileges in a role.
Table 8:
Name Description
Predefined Roles
Basic Web User
A limited user who can only read standard report definitions, read schedule definitions, read Vault documents, show users from Everybody group, show folders from Everybody group, access the Alarm Viewer. A typical user who has all the privileges of a Basic Web User and who can edit/ delete standard report definitions, run standard reports, edit/schedule definitions, has a personal documents area, read/edit MyFavorites pages, view UDC definitions. An advanced user who has all the privileges of a Normal Web User and who can also publish and edit Vault documents, view and edit UDCs, access the Alarm Exporter and Alarm Manager, Import and Export data with the Admin tool. The top-level administrator having all available privileges. System administrators have full control over Tivoli Netcool Performance Manager for Wireless software.
Normal Web User
Power Web User
System Administrator
5.3.4
Privileges
Privileges are a list of tasks and features available for users. Privileges are grouped into roles, which are then applied to a particular user. The following table describes the privileges available on the Tivoli Netcool Performance Manager for Wireless system.
Table 9: Privilege Descriptions
Privilege Applies To Description
Admin: Edit Datasource definitions
Administration software
Allows the user to perform actions associated with agents and agent activities. Allows the user to edit users, groups, and roles.
Admin: edit users and user Administration data software, Web Client Allow access to Alarm Exporter Allow access to Alarm Manager Allow access to Alarm Viewer Web Client Web Client Web Client
Allows the user to create and modify alarm targets. Allows the user to activate and deactivate alarms, and to modify alarm definitions. Allows the user to view and acknowledge alarms.
32

Configure Jboss Create entity and field mappings (equivalencies) Edit Agent settings Edit/delete any existing reports Edit/delete any existing folders or documents
Administration software Administration software Administration software Web client Web client
Allows the user to configure Jboss. Allows the user to model entity and field equivalencies. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to modify properties and perform actions associated with agents and agent activities. Allows the user to modify all report results, regardless of the assigned permissions. Allows the user to modify all saved documents, regardless of the assigned permissions. Allows the user to create/edit/delete a remote UDC owned by the current user. Allows the user to open and edit enterprise report definitions. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to schedule reports to be run. Allows the user to open and edit local report definitions. Allows the user to enter information about an entity instance using the Entity Data Editor. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to edit holiday definitions using the Holiday Administration tool. Allows the user to create, edit, and delete customized pages in the Web client. Allows the user to create/edit/delete any remote UDC owned by any user. Allows the user to use the export tool. Allows the user to use the import tool. Allows the user to manage the auto downloading of scheduled reports that exist on remote servers. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to promote a UDC. Allows the user to organize folders and save documents to the vault page, assuming they have the appropriate file permissions.
Edit any remote UDC defi- Administration nitions software Edit/delete enterprise report definitions Edit/delete schedule definitions Edit/delete standard Web report definitions Edit entity data Web client
Web client Web client Administration software Administration software Web client Administration software Administration software Administration software Web client
Edit Holidays Edit MyFavorite pages Edit remote UDC definitions Export Data with the Admin Tool Import Data with the Admin Tool Manage AutoDownload entries Promote UDCs
Administration software
Publish and edit Vault doc- Web client uments

Read enterprise report def- Web client initions Read MyFavorite pages Read reports from remote servers Read schedule definitions Read standard Web report definitions Read Vault documents Web client Web client
Allows the user to read enterprise report definitions. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to view customized pages in the Web client. Allows the user to see remote server report status from the Monitor tab. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to view report schedules. Allows the user to view local report definitions. Allows the user to browse through documents that have been published to the vault page. Allows the user to rename a remote user-defined calculation (UDC). Allows the user to run reports residing on a remote server. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to run enterprise reports. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to run report definitions. This privilege implies read and edit privileges. Allows the user to see documents in a folder in which the user does not have read or write permissions. If this privilege is not granted, the user can only see folders available to the group(s) they belong to. Allows the user to see all users, including those in groups the user does not belong to. If this privilege is not granted, the user can only see other users in the group(s) they belong to. Allows the user to organize folders in a private area and save documents there. Allows the user to view agent properties and agent activities, but not modify any associated properties or perform any associated actions. Allows user to view data availability. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to view agent properties and agent activities, but not perform any actions. Allows the user to browse through documents on remote servers.
Web client Web client Web client
Rename remote UDC defi- Administration nitions software Run classic reports on remote servers Web client
Run enterprise report defi- Web client nitions Run standard Web reports Show folders from Everybody group Web client Web client
Show users from Everybody group
Web client
User has a Personal Docu- Web client ments area View Agent settings Administration software Web client Administration software
View data availability View Datasource definitions
View documents on remote Web client servers
34

View enterprise data avail- Web client ability. View entity and field map- Administration pings (equivalencies) software View entity data Administration software Administration software Administration software Administration software
Allows the user to view enterprise data availability. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to view entity equivalencies, but not edit them. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. Allows the user to view entity information in the Entity Data Editor, but not edit them. This privilege does not apply to Tivoli Netcool Performance Manager for Wireless. View promoted user-defined-calculations (UDCs). Allows the user to view the definition for a remote user-defined calculation (UDC). Allows the user to view users, groups, and roles, but not edit them.
View promoted UDCs View remote UDC definitions View users and user data
5.4
User Management
User Management covers the tasks of adding and maintaining users and groups, and associating users with roles.
Figure 4: User Management
5.4.1
Adding Users
You must have the appropriate privileges to add a user. The Add operation adds the user to the LDAP repository and to the database, creating both inet_user (anonymous user) and user entries. A user is added by default to the Everybody group, and assigned the Normal Web User role. To add a user: 1. In the MANAGE USERS tab, click the VIRTUO USERS tab. 2. Click the ADD USER button. The ADD USER dialog is displayed.
36
Figure 5:
Adding a user
3. Enter the users details in the appropriate fields. 4. Click OK. The user is listed in the LIST OF USERS.
5.4.2
Editing Users
You must have the appropriate privileges to edit a user. To edit a user: 1. In the MANAGE USERS tab, click the VIRTUO USERS tab. 2. Select the user from the LIST OF USERS. 3. Click the EDIT USER button. 4. Edit the users details as required. You cannot alter a users login ID. 5. Click OK.
5.4.3
Deleting Users
Deleting a Tivoli Netcool Performance Manager for Wireless user removes the user from the server. You must have the appropriate privileges to delete a user. The following users cannot be deleted: useradm, virtuo and sysadm. To delete a user: 1. In the MANAGE USERS tab, click the VIRTUO USERS tab. 2. Select the user from the LIST OF USERS. Tip: Select more than one user using the Shift and Ctrl keys. 3. Click the DELETE SELECTED USER(S) button.
A message is displayed asking you to confirm the deletion. 4. Click YES.
5.4.4
Creating and Deleting Groups
Groups are primarily used by Tivoli Netcool Performance Manager for Wireless users to determine who can access their reports. You must have the appropriate privileges to create or delete a group. You cannot delete the system predefined groups: everybody and admin. To create a group: 1. In the MANAGE USERS tab, click the USERS BY GROUP tab. 2. Click the ADD USER GROUP button. The ADD GROUP dialog is displayed.
Figure 6: Adding user groups
3. Enter a name for the group. 4. Click OK. The group is listed in the LIST OF AVAILABLE USER GROUPS. To delete a group: 1. In the MANAGE USERS tab, click the USERS BY GROUP tab. 2. Select the group you want to delete. Tip: Select more than one group using the Shift and Ctrl keys. You cannot delete a group that has one or more users associated with it. 3. Click the DELETE SELECTED USER GROUP(S) button. A message is displayed asking you to confirm the deletion. 4. Click YES.
38
5.4.5
Adding and Removing Users to/from Groups
Adding users to groups is an easy way to allow users access to certain folders and reports. You must have the appropriate privileges to add a user to a group. To add/remove a user to a group: 1. In the MANAGE USERS tab, click the USERS BY GROUP tab. 2. Select the group that you want to add/remove users to/from, in the LIST OF AVAILABLE USER GROUPS. 3. Add/Remove users as required. Users are added by dragging the user from the AVAILABLE USERS box to the ASSOCIATED USERS box. Users are removed by dragging the user from the ASSOCIATED USERS box to the AVAILABLE USERS box. Tip: Select more than one user using the Shift and Ctrl keys.
5.4.6
Assigning and de-assigning Users to/from a Role
Assigning users to a role allows you to determine how they interact with Tivoli Netcool Performance Manager for Wireless software. You can restrict access to folders and systems, or you can grant special privileges to certain classes of users. You must have the appropriate privilege to assign users to a role. To assign/de-assign users to a role: 1. In the MANAGE USERS tab, click the USERS BY ROLE tab. 2. Select the role that you want to assign/de-assign users to/from, in the LIST OF AVAILABLE ROLES. 3. Assign/de-assign users as required. Users are assigned by dragging the user from the AVAILABLE USERS box to the ASSOCIATED USERS box.
USERS
Users are de-assigned by dragging the user from the ASSOCIATED USERS box to the AVAILABLE box. Tip: Select more than one user using the Shift and Ctrl keys.
5.5
Role Management
Role Management covers the tasks necessary for the setting up and maintaining of roles.
5.5.1
Creating and Deleting Roles
Creating a role allows you to group custom privileges that can then be assigned to users. You must have the appropriate privileges to create or delete a role. You cannot delete the system predefined roles: basic web user, normal web user, power web user and system administrator. To create a role: 1. Click the MANAGE ROLES tab. 2. Click the ADD ROLE button. The ADD ROLE dialog is displayed.
Figure 7: Adding roles
3. Enter details for the role. 4. Click OK. The role is listed in the LIST OF AVAILABLE ROLES. To delete a role: 1. Click the MANAGE ROLES tab. 2. Select the role you want to delete. Tip: Select more than one role using the Shift and Ctrl keys. You cannot delete a role that has one or more users associated with it. 3. Click the DELETE SELECTED ROLE(S) button. A message is displayed asking you to confirm the deletion. 4. Click YES.
40
5.5.2
Assigning/De-assigning Privileges to a Role
Assigning privileges to a role allows you to group the privileges you want to assign to users. Creating roles is convenient when several people share common privileges. See Privileges on page 32 for information on access rights for different privileges. You must have the appropriate privileges to assign privileges to a role. To assign/de-assign privileges to a role: 1. Click the MANAGE ROLES tab. 2. Select the role that you want to assign/de-assign privileges to/from, in the LIST OF AVAILABLE ROLES. 3. Assign/De-assign privileges as required.
ROLE
Privileges are assigned by dragging the privilege from the PRIVILEGES AVAILABLE FOR SELECTED box to the PRIVILEGES ASSOCIATED WITH SELECTED ROLE box.
Privileges are de-assigned by dragging the privilege from the PRIVILEGES ASSOCIATED WITH SELECTED ROLE box to the PRIVILEGES AVAILABLE FOR SELECTED ROLE box. Tip: Select more than one privilege using the Shift and Ctrl keys.
5.6
User Administration Command Line Tool
The user_admin tool provide a means of creating and deleting Tivoli Netcool Performance Manager for Wireless users as well as upgrading user passwords. This tool is intended to support bulk provisioning of users. It can be used in parallel with the User Administration GUI. This tool cannot be used off-line. It requires a virtuo administration login to the server hosting the Tivoli Netcool Performance Manager for Wireless application.
5.6.1
Usage
-u <admin_user> -p <admin_password> -listusers simple -u <admin_user> -p <admin_password> -listusers detail -u <admin_user> -p <admin_password> -listroles -u <admin_user> -p <admin_password> -add -f <firstname> -ln <lastname> -uid <user_id> -up <user_password> -rf <role_filename> [-e <email_addr>] -u <admin_user> -p <admin_password> -modify -uid <user_id> -up <new_user_password> -u <admin_user> -p <admin_password> -delete -uid <user_id>
user_admin [-asconf conf_name] parameters
Table 10:
Option
-u -p -listusers simple -listusers detail -listroles -add -f <firstname> -ln <lastname> -uid <user_id> up <user_password> -rf <role_filename> [-e <email_addr>]
Options for user_admin Script

Description
Administration user name. Administration password. List user identifiers only. List all user details for all users. List roles. Add user.
<firstname> is the users first name <lastname> is the users last name <user_id> is the users login ID <user_password> is the users password <role_filename> is the name of the role file, a role file
specifies a number of roles <email_addr> is the users email address, an email address is optional.
-modify -uid <user_id> -up <new_user_password> -delete -uid <user_id>
Modify user. <user_id> is the users login ID. <new_user_password> is the users new password. Delete user. <user_id> is the users login ID.
42
5.6.2
Listing Users
The List operations are threefold. The two user listings consist of the user identifiers only, and the detailed listing of all user details. The role listing consists of listing all roles in the system. To list user ids:
user_admin -u <admin_user> -p <admin_password> -listusers simple user_admin -u <admin_user> -p <admin_password> -listusers detail user_admin -u <admin_user> -p <admin_password> -listroles
where:
<admin_user> is the administrators login ID <admin_password> is the administrators login
password
5.6.3
Adding Users
The Add operation adds a user to LDAP and to the database, creating both inet_user and user entries. A user is added by default to the Everybody group in LDAP. A user is assigned to the roles specified in the role file. A user is assigned to all datasources in the system. To add a user:
user_admin -u <admin_user> -p <admin_password> -add -f <firstname> -ln <lastname> uid <user_id> -up <user_password> -rf <role_filename> [-e <email_addr>]
where:
<admin_user> is the administrators login ID <admin_password> is the administrators login password <firstname> is the users first name <lastname> is the users last name <user_id> is the users login ID <user_password> is the users password <role_filename> is the name of the role file, a role file specifies a number <email_addr> is the users email address, an email address is optional
of roles
Role Files A role file specifies a number of roles. A user is added to the Normal Web User role by default. Each role file is a text file with a role per line. The role name is the name of the role in LDAP, and not the user friendly role name as specified in the user interface. When adding a user, incorrect roles will be ignored and a warning message will be displayed. The user will be added to correctly named roles only. If all roles in the role file are incorrect, the user will still be added to the Normal Web User role. Example of a Role File:
WebUserNormal WebUserPower
5.6.4
Modifying a Users password
The Modify operation allows a user password to be modified. The following users may not be modified: useradm, virtuo and sysadm. To modify a user:
user_admin -u <admin_user> -p <admin_password> -modify -uid <user_id> -up <new_user_password>
where:
<admin_user> is the administrators login ID <admin_password> is the administrators login password <user_id> is the users login ID <new_user_password> is the users new password
5.6.5
Deleting Users
The Delete operation removes a user completely from the system. This includes all references to the user in the database and in LDAP. The following users may not be deleted: useradm, virtuo and sysadm. To delete a user:
user_admin -u <admin_user> -p <admin_password> -delete -uid <user_id>
where:
<admin_user> is the administrators login ID <admin_password> is the administrators login password <user_id> is the user login ID of the user to delete
44
Tivoli Netcool Performance Manager for Wireless Operations Tasks
This chapter describes a number of operations tasks and housekeeping activities that are essential for the operation of Tivoli Netcool Performance Manager for Wireless. These include: Daily Loader Operations Tasks Loader Housekeeping Although not regular tasks, the following are also described: Checking TFP_SHM_MIN_SIZE TFP_NC_STABILITY
6.1
Daily Loader Operations Tasks
In a Tivoli Netcool Performance Manager for Wireless system there may be a number of loaders running for a number of technologies. The loader process runs constantly taking data from the loader spool directories and loading it into the performance database. The loader process is critical to the functioning of Tivoli Netcool Performance Manager for Wireless. The following should be done on a daily basis: Check Loader status Check for bad files.
6.1.1
Checking Loader Status
To check the status of the loaders, complete the following as user virtuo: 1. Execute the command:
sap disp
Output will be displayed listing the loaders that are started and loaders that are stopped. For example:
[virtuo]sap disp NAME as loadericssongsmbssneutral
STATE STARTED STARTED
SINCE Mar 14, 2007 Mar 14, 2007

45
loadericssongsmbss loadnokiagsmbssneutral loadnokiagsmbss loadmotorolagsmbss loadmotorolagsmbssneutral loadmotorolaumtsutran loadericssonumtsutran
STARTED STARTED STARTED stopped stopped stopped stopped
Mar 14, 2007 Mar 14, 2007 Mar 14, 2007 -
2. Ensure the loaders are started correctly. A process should exist for each loader configured and running:
ps -ef | grep na_loader
The loader process looks like the following. The ruleset ID is different for each loader type:
$WMCROOT/bin/na_loader -foreground -ruleset 10003
3. If the loaders have not started correctly, check the loader logs for startup issues. Loader log files are stored in the $WMCROOT/logs/loader directory.
6.1.2
Checking for bad files
The following directories should be checked for large amounts of bad files: $WMCROOT/var/loader/spool/<loadername>/<rulesetid>/bad $WMCROOT/var/loader/bad If there is a large number of bad files in either of these directories the loader log files should be checked. Loader log files are stored in the $WMCROOT/logs/loader directory. There is a properties file for each loader configured in the $WMCROOT/conf/loader directory. The following is an example output from a loader log file.:
Thu Mar 8 16:45:41 2007 MAP AUDIT (19480): FILE_PROCESSING_SUCCESSFULLY_6: "File <MSC_2-#-P_NBSC_RES_ACCESS-#-BSS4.20060217.07.45.1-2-1.lif> has been processed. Blocks loaded: <30>. Loading started: <Thu Mar 8 16:45:41 2007> and finished: <Thu Mar 8 16:45:41 2007> . Elapsed Time: <0> second(s). Performance alarm messages generated: <0>, data loaded events generated: <0>." Thu Mar 8 16:45:41 2007 PDO INFO (19480): PDO_LOAD_SUCCESS_PDO_FILE: "Successfully loaded PDO file <PDO_DAAylaadM> into table <vnl_cell_access_tab>. Return Code is <SUCCESS> , Return message is <>. " Thu Mar 8 16:45:41 2007 PDO AUDIT (19480): PDO_LOAD_FILES_TIME: " The Elapsed time for loading the PDO files is <0> seconds. " Thu Mar 8 16:45:41 2007 ISI AUDIT (19480): ISI_MSG_OPEN_FOUND_IS: "The input source file </appl/virtuo/var/loader/spool/nokiagsmbssneutral1/10000/> <MSC_2-#P_NBSC_RES_ACCESS-#-BSS4.20060217.09.15.1-2-1.lif> was opened" Thu Mar 8 16:45:41 2007 CACHE INFO (19480): CACHE_FILE_STATS_PRT1: "===============Cache statistics for current file===============" Thu Mar 8 16:45:41 2007 CACHE INFO (19480): CACHE_FILE_STATS_PRT2_2: "Rows inserted <30>, rows flushed <30>" Thu Mar 8 16:45:41 2007 CACHE INFO (19480): CACHE_FILE_STATS_PRT3_6: "Rows flushed due to cache full <0> <0.000000%>,due to max time reached <0> <0.000000%> , all other <30> <100.000000%>"
Thu Mar 8 16:45:41 2007 CACHE INFO (19480): CACHE_FILE_STATS_PRT4_2: "Cache hit percentage <0.000000%>, Cache miss percentage <100.000000%>." Thu Mar 8 16:45:41 2007 ISI AUDIT (19480): ISI_MSG_CLOSE_IS: "The input source file </appl/virtuo/var/loader/spool/nokiagsmbssneutral1/10000/MSC_2-#-P_NBSC_ RES_ACCESS-#-BSS4.20060217.09.15.1-2-1.lif> was closed and moved to </appl/virtuo/ var/loader/spool/nokiagsmbssneutral1/10000/good/MSC_2-#-P_NBSC_RES_ACCESS-#BSS4.20060217.09.15.1-2-1.lif>."
If the loader is sending lif files to the bad directory a number of SQL error messages may be generated. The example below shows some of these errors in a loader log file.
Wed Feb 28 12:21:43 2007 PDO INFO (20274): PDO_LOAD_FILE_WITH_ERROR: "Some rows were not loaded when loading PDO file <PDO_DAArVaqMN> into table <vnl_cell_tch_tab>. Return Code is <FAILURE> , Return message is <ORA01400: cannot insert NULL into("VIRTUO"."WML_TABLE_LOAD_HISTORY"."FROM_INTERVAL")>. "
The Oracle oerr ora command can be used to provide additional information about the problem. For example:
oerr ora 1400 01400, 00000, "cannot insert NULL into (%s)"
In some cases lif files may go to the bad directory and there may be very little information in the error logs to track the problem. In such cases the log level can be set to a higher level to produce logs with more information. Note: It is advisable to only to run the loader at log level 0 (debug) for short periods of time because the logs generated can be very large. Log level 1 (info) is the normal logging requirement.
Changing the Loader Log Level To change the loader log level of any loader while it is running, complete the following as user virtuo: 1. Find the process identifier of the loader you want to change by executing the command:
ps-ef | grep na_loader
2. Change the log level of the required loader by executing the command:
kill -USR1 <process_id>
where <process_id> is the identifier of the loader you want to change the log level for. This command increments the log level by one level. For example from 0 to 1. To change the log level from 1 to 0 the command must be issued six times. There are seven logging levels, and after the last level the next level cycles back to 0.
Tivoli Netcool Performance Manager for Wireless Operations Tasks 47
Note: You can also set the loader log level in the run_loader script which is located in the $WMCROOT/bin directory. At the end of this script you will see the following line:
exec $WMCROOT/bin/na_loader -foreground -loglevel 1 -ruleset $RULESET_ID
Change the -loglevel to the log level you need, see Table 11 for a list of the log levels. Start the loaders, execute the following command for each loader that needs to be started:
sap start <loadername>
Log Levels The following table lists the seven logging levels.
Table 11:
Logging Level Description
Logging Levels
0 = Debug 1 = Info 2 = Warning 3 = Error 4 = Fatal 5 = Audit
This level indicates low level messages that can be used to analyze component processing data. This level indicates activity in the system at certain points in the operation, such as starting up or shutting down. This indicates non-fatal errors and can point to performance problems This indicates errors that can be recovered from. This will be true for almost all error handling. This indicates an error has occurred with such severity, that the application could not exit cleanly This level indicates the message contains important information regarding the operation and maintenance of the loader. The use of this level will be limited to information that is contract sensitive. Audit information may include the time loader configuration changes were made, when licenses were updated and additional contract details For NOLOGGING logging.
DEBUG Level Logging - Impacts on Performance Log levels can be set for various parts of the system. Log level 0 (debug) prints the most messages to the server logs. Log level 0 can adversely impact performance. This is especially true if the Meta Service log level is set to 0. In normal operation the log level for all of the subsystems should be set to 1 (info).
48
6.2
Loader Housekeeping
Disk space usage
The following housekeeping task should be done on a daily basis:
6.2.1
Disk Space Usage
LIF files are constantly being parsed, loaded and moved to either good or bad directories. If a problem occurs LIF files may be parsed but not loaded. This may cause the $WMCROOT/var/loader/spool/ <loadername> filesystem to fill up, preventing any new files from being created.
loader/spool/<loadername>
After LIF files are processed they should be removed from the system, otherwise the $WMCROOT/var/ filesystem may fill up.
1. To check filesystem allocation and usage (in particular for /spool), execute the following command as user virtuo:
$df -k
6.3
Checking TFP_SHM_MIN_SIZE
Note: This is not a daily procedure, it is usually only performed once when the system is being configured. The environment variable TFP_SHM_MIN_SIZE specifies the minimum size for the shared memory segment used to store Network Configuration (nc) data for the loaders. Generally, it only needs to be used if you wish to set the Network Configuration shared memory size to be greater than the 50 megabytes (52428800). If the variable is set to lower than 5 megabytes (5242880) then it is ignored and the shared memory size is set to 50 megabytes. Calculating the Value for TFP_SHM_MIN_SIZE Complete the following as user virtuo: To calculate a value for TFP_SHM_MIN_SIZE, complete the following: 1. Load one complete interval of data into the system. This process should fully populate all the Network Configuration (nc) tables for the entire system. Unless re-parenting takes place or new Network Configuration data is loaded then the Network Configuration memory size should not grow beyond this point. 2. Stop the loaders by executing the following command for each loader process:
sap stop <loadername>
3. If it is set, unset the TFP_SHM_MIN_SIZE environment variable in the $WMCROOT/conf/loader/ default.properties file.
4.
Restart one loader, and allow it to work for approximately one minute. Execute the following command to restart one loader:
The loader will allocate the correct amount of memory required for the Network Configuration data. 5. Execute the following command to show the amount of memory in use:
ipcs A
The example below shows the output of ipcs A when the loader is running.
IPC status from <running system> as of Fri Mar T ID KEY MODE STIME MODE ATIME DTIME OWNER RTIME OWNER CTIME virtuo QNUM QBYTES LSPID LRPID Message Queues: T ID SEGSZ m m T OTIME Semaphores: s s 28 25 0xa6000000 --ra-ra---default oracle oinstall oracle oinstall 504 default 0x10a246a0 --ra-r----virtuo virtuo virtuo virtuo 2 10:50:06 10:44:31 14:11:37 14:02:31 30 27 1392517120 ID CTIME CPID KEY LPID GROUP CREATOR CGROUP NATTCH PROJECT virtuo default 63 default CGROUP NSEMS 2 ISMATTCH virtuo virtuo 0 63 GROUP CREATOR 9 14:11:38 GMT 2007 GROUP CTIME CREATOR CGROUP CBYTES PROJECT
Shared Memory: 0xa6000000 --rw-rw---0xad36186c --rw-r----3758 KEY MODE PROJECT 314572800 21505 21590 10:45:06 no-entry 10:44:31 oracle oinstall OWNER 3747 14:11:31 14:11:34 14:02:30
oracle oinstall
The value in bold is the size of the Network Configuration shared memory segment. This value, plus 20%, should be used for TFP_SHM_MIN_SIZE for all loaders. The increase of 20% is to safeguard against the possibility of Network Configuration data growing in size and causing problems in connecting to Network Configuration shared memory. Refer to the Potential Shared Memory Errors on page 167. Increasing the Value for TFP_SHM_MIN_SIZE Complete the following as user virtuo: 1. Stop the loader started in Step 4 above by executing the command:
2. Execute the following command to ensure all loaders are stopped:

sap disp
There should be no loader processes returned. 3. Set the TFP_SHM_MIN_SIZE environment variable in the $WMCROOT/conf/loader/ default.properties file to the required value. 4. Restart the loaders by executing the following command for each loader process:
All the alarm activation and deactivation should be working again.

6.4
TFP_NC_STABILITY
Flapping, otherwise known as oscillating Network Configuration data, occurs when LIF files are loaded which have slightly different Network Configuration parentage information for the same node id. This scenario may occur if two loaders are loading from different data sources and, for some reason, there are differences in the Network Configuration data uploaded from the different data sources. The stability period is the time during which it is permissible for re-parenting of an access key to take place. The default value of 2 hours i.e. 7200 seconds is set for TFP_NC_STABILITY.
52
Datasource, Agent and KPI Cache Administration

Datasource Administration. See Datasource Administration on page 54. Agent Maintenance. See Agent Maintenance on page 56. KPI Cache Management. See KPI Cache Management on page 65.
This chapter describes the following:
53
7.1
Datasource Administration
Datasources provide Tivoli Netcool Performance Manager for Wireless with the necessary performance data for reports. A Datasource is typically a server that contains entity and performance data information. After a software installation users and datasources need to be created. Users and datasources are created as part of the installation process. Note: See the Tivoli Netcool Performance Manager for Wireless Installation Guide, for more information on the installation process. The following command is used to create default users and datasources after installation:
sys_init -u <admin_user> -p <admin_pass> -h <host>
Alternatively, use a web browser and execute the following: 1. Insert the following in a web browser:
http://<hostname>:8080/sysinit
where <hostname> is the hostname for the machine. 2. Log in with the administration userid <admin_user> and the administration password <admin_pass>. After completion of the initialization of the default users, users are maintained using GUI User Administration tool. See User Management on page 36. Datasources are maintained by the ds_admin script. The ds_admin script can perform the following task: Display existing datasources. See Listing Datasources on page 55. The ds_admin script is located in:
$WMCROOT/bin
The ds_admin script can be executed from any directory as user virtuo.
7.1.1
Usage
ds_admin [-asconf conf_name] parameters - List Data Sources: -u user -p password -list - Activate Data Source: -u user -p password -activate dsname - Deactivate Data Source: -u user -p password -deactivate dsname
Note: The -asconf option will be used for multiple instances of the application server. It is reserved for use or removal of future implementations of the Tivoli Netcool Performance Manager for Wireless product.
54
7.1.2
Listing Datasources
ds_admin -u <user> -p <password> -list
1. Execute the ds_admin script using the following syntax: The parameters to be included with the ds_admin script to list datasources are described in Table 12.
Table 12:
Option
-u <user> -p <password>
Parameters for Listing Datasources
Description
Username. Password.
For Example: The following command is sample list output.

[hostname:virtuo] ds_admin -u <user> -p <password> -list Name tralee Host tralee Active true tralee Enterprise true true true false Local JDBC
jdbc:oracle:thin:@tralee:1521:vtdb false jdbc:oracle:thin:@tralee:1521:vtdb
tralee-rs
7.1.3
Activating a Datasource
Note: The -activate option is used during the installation of the Tivoli Netcool Performance Manager for Wireless product. This option is currently reserved for use only by an application installation administrator.
7.1.4
Deactivating a Datasource
Note: The -deactivate option is reserved for future use or removal of future implementations of the Tivoli Netcool Performance Manager for Wireless product.
Datasource, Agent and KPI Cache Administration 55
7.2
Agent Maintenance
When Tivoli Netcool Performance Manager for Wireless is installed, the scheduler process is configured to run certain standard administrative jobs/activities on a regular schedule. The administrative jobs/ activities are maintained and monitored by two command line tools: schedule_admin
agent_admin
Refer to Schedule Administration on page 70 for more information on the schedule_admin tool. The agent_admin tool is used to monitor and manage agent activities executed by the agent framework. These agent activities usually relate to supporting Tivoli Netcool Performance Manager for Wireless activities such as creating summaries, synchronizing the LDAP database and cleaning up agent/file activities.
7.2.1
Overview of Agent Activities
Agents collect information from datasources and perform maintenance on the Tivoli Netcool Performance Manager for Wireless product. It is the responsibility of the agents to collect information from the datasources to: Populate a set of tables (data dictionary) which defines the entities and fields available from the datasource. Keep the source system database information synchronized with the local web tables. Once the information is populated a user can run a report via the web using the information to query the datasource via a dynamic SQL query. The query results are then available to the user via a web browser. The types of tasks the agents perform fall into four categories: Database Procedural Sweeper Summary Table 13 below describes the agent activities currently running for a typical Tivoli Netcool Performance Manager for Wireless installation. Note: Some of the agent activites in Table 13 are marked reserved. This indicates the agent activity is reserved for use or removal of future implementations of the Tivoli Netcool Performance Manager for Wireless product. Do not stop these activities from running as it may result in system consequences.These jobs have minimal impact on your system resources.
56
Table 13:
Agent Activities Label
Agent Types and Descriptions

Description
Procedure
Agent Activity Cleanup Temporary Report and Schedule Cleanup Datasource cleanup. Unused file deletion.
The procedure agent runs every hour to remove old agent activity information. The procedure agent runs first on initial use of the administration software. The procedure agent runs every hour to remove temporary reports and schedules. The procedure agent runs first on initial use of the administration software. This procedure agent runs daily and cleans up deleted datasources (reserved). The sweeper agent runs every 20 minutes to remove report results that are no longer active from the database and the file system. A consequence of this agent is the removal of report results from the Monitor tab. The LDAP synchronization agent updates the database with information about the configured datasource, changes to the datasource properties may occur if another Tivoli Netcool Performance Manager for Wireless Server uses the same datasource. The LDAP agent also runs periodically usually every two hours to ensure the Tivoli Netcool Performance Manager for Wireless Server and LDAP Server are synchronized. Updates mapping of rehomed instances (reserved). The instance data agent gathers information from the remote datasource that is used to track the network elements that are available for reports. The information is stored in tables maintained by the instance schema agent The instance data agent runs automatically if the instance schema agent adds a new table or column. The instance data agent also runs periodically usually every two hours to update the information on the Tivoli Netcool Performance Manager for Wireless Server. (reserved).
Procedure
Procedure Sweeper
LDAP Synchronization
LDAP Synchronization
Procedure Instance Data
Update Mapping of Rehomed Instances. System Retrieve Entity Data
Data Dictionary
Data Dictionary Import
The data dictionary agent maintains the field and entity information on the Tivoli Netcool Performance Manager for Wireless server. The information includes the following: Version information for the datasource. List of available entities. List of available fields. Data dictionary runs once when a new datasource is added to the system. This agent also runs periodically usually every 2 hours to ensure the Tivoli Netcool Performance Manager for Wireless server is up to date. In an effort to avoid database errors, only one data dictionary agent is active at 1 time (reserved).
Agent Activities
Label
Description
Summary
Summary Computations
Tivoli Netcool Performance Manager for Wireless is configured to provide summary computations for all traffic counters gathered from a managed network element. The role of this agent is to assess if summaries need to be completed and to populate the database with the computed summaries. This agent runs every two hours and assesses what summaries are ready for creation. The Summary Computation agent ensures daily, weekly and monthly summary computations are performed.
7.2.2
Agent activities and log files
Each of the agent activities produces an entry into the as-server.log file that details the activity, run time of the activity and status of the activity. The log file rolls over by size and then by date so you may notice that there are multiple log files each day. The log files are located in:
$WMCROOT/logs/as/default
7.2.3
agent_admin Command Line Tool
The agent_admin tool is used to monitor and manage agent activities executed by the agent framework. These agent activities typically relate to supporting NetworkAssure activities such as creating summaries, synchronizing the LDAP database and cleaning up agent/file activities. The agent_admin script can perform the following tasks: Display current activities. See Listing Current Activities on page 59. Listing past activities. See Listing Past Activities on page 61. Display activity logs. See Activity Logs on page 63. Running activites. See Running Activities on page 63. Cancelling activities. See Cancelling Activities on page 63. The agent_admin script is located in:
$WMCROOT/bin
This tool can be executed from any directory as user virtuo. Usage
agent_admin [-asconf conf_name] parameters - Current activities: -u user -p password -list current - Past activities: -u user -p password -list past - Activity log: -u user -p password -logs id run_id - Run activity: -u user -p password -run id - Cancel activity: -u user -p password -cancel id
58
Note: The -asconf option will be used for multiple instances of the application server. It is reserved for future implementations of the Tivoli Netcool Performance Manager for Wireless product.
Listing Current Activities Current activities are agent activities that have not been completed, which includes activities which are running and activities which are waiting to run. Complete the following to display the list of current activities running for a Tivoli Netcool Performance Manager for Wireless installation. 1. Execute the agent_admin script using the following syntax:
agent_admin -u <user> -p <password> -list current
The parameters to be included with the agent_admin script to list current activities are described in Table 14.
Table 14:
Option
-u <user> -p <password> -list current
Parameters for Listing Current Activities
Description
Username. Password. Lists current activities.
For Example: The following command is sample list output of current activities.
[hostname:virtuo] agent_admin -u <user> -p <password> -list current ID Run Type Data End PROCEDURE null null null INSTANCE null null null null null SWEEPER tralee PROCEDURE Data Source State Cancel Entity Active Label N null 2006-10-02 17:25 Agent activity cleanup Start End
Data Start 1 :00 4 null 2 :00 12 51 null 570 null 97 null 48
Attempt Retry tralee null 1 tralee null
SCHEDULED 1 N 1 N N null N
SCHEDULED
2006-10-04 12:34:00 Unused file deletion N null 2006-10-04 12:55 Temporary report N System 2006-10Retrieve
SCHEDULED
and schedule cleanup tralee-rs null tralee null SCHEDULED 1 N N 1 04 12:59:00 entity data 5 :00 13 85 null 44 LDAP_SYNC null SCHEDULED null 2006-10-04 13:04 N N null 2006-102006-09-13 14:34:16 tralee-rs
Ldap synchronization DICTIONARY SCHEDULED
04 13:51:00 14 :00 8 :00 3 :00 45 null 4 null 4 null
null null null
null null null
null null tralee null tralee null
null 1 1
1 N N
N N null N null N null
null
Data dictionary import
SUMMARY tralee-rs PROCEDURE
SCHEDULED SCHEDULED
2006-10-04 14:03 Summary computations 2006-10-04 14:55 Update Mapping o 2006-10-05 02:00 Datasource clean=up
f Rehomed Instances. PROCEDURE null null SCHEDULED 1 N
Current Activity Properties Table 15 describes the information available for each current activity. This information is useful when analyzing a list of current activities.
Table 15:
Property Description
Current Activity Properties
ID Run Type Datasource State Cancel
The unique ID of the agent activity, type and label. The Run ID of the unique agent activity type currently running. See Table 13 for a description of agent types. The datasource affected by the activity. Shows whether the activity is running or in the queue. Determines whether the activity was cancelled. If an activity was cancelled it is shown on the current list until the activity ends on the server. The next time an activity is expected to run. Date and time when the activity started (if available). The time a failed activity ended. The start time of gathering traffic data from a datasource. The end time of gathering traffic data from a datasource. The number of times a failed activity is retried. Shows whether the activity has previously failed. The entity of the datasource affected by the activity. See Table 13, for agent activity labels and descriptions.
Active Start End Data Start Data End Attempt Retry Entity Label
Note: The ID property uniquely identifies an agent activity based on a combination of the agent label and type.
60
Listing Past Activities A past activity can be one of the following agent activities: Completed Failed Cancelled The number of days of past activities displayed depends on the setup of data retention and partitions during installation. It provides all past agent activities based on the install setting of the length of time to retain the Enterprise agent retention setting. Complete the following to list past activities: 1. Execute the agent_admin script using the following syntax:
agent_admin -u <user> -p <password> -list past
The parameters to be included with the agent_admin script to list past activities are described in Table 16.
Table 16:
Option
-u <user> -p <password> -list past
Parameters for Listing Past Activities
Description
Username. Password. Lists past activites.
For Example: The following command is sample list output of past activities.
[hostname:virtuo] agent_admin -u <user> -p <password> -list past
ID Type Data source state Cancel Active Start End Entity Label Message 5 12 1 2 5 1 14 271 136 271 271 270 270 133 LDAP_SYNC null System null null null null null INSTANCE PROCEDURE PROCEDURE LDAP_SYNC PROCEDURE tralee COMPLETED FAILED 2006-11-14 18:15:09 null 2006-11-14 17:42:09 Entity System not found. 2006-11-14 17:33:09 null 2006-11-14 17:30:09 null 2006-11-14 17:15:29 null 2006-11-14 16:33:09 null 2006-11-14 16:31:09 null 2006-11-14 18:15:10 2006-11-14 17:42:11 2006-11-14 17:33:09 2006-11-14 17:30:10 2006-11-14 17:15:30 2006-11-14 16:33:10 2006-11-14 16:31:09 Ldap synchronization tralee-rs tralee tralee tralee tralee Retrieve entity data COMPLETED COMPLETED COMPLETED COMPLETED COMPLETED Agent activity cleanup
Temporary report and schedule cleanup Ldap synchronization Agent activity cleanup Summary computations
SUMMARY tralee-rs
2 13
270 136
PROCEDURE null null DICTIONARY
tralee
COMPLETED FAILED
2006-11-14 16:30:09 null 2006-11-14 16:26:19 No entity data exists fo 2006-11-14 16:15:19 null 2006-11-14 15:42:29 Entity System not found. 2006-11-14 15:33:19 null 2006-11-14 15:30:19 null 2006-11-14 15:15:09 null 2006-11-14 14:33:29 null 2006-11-14 14:31:29 null
2006-11-14 16:30:10 2006-11-14 16:26:20 r datasource tralee-rs. 5 12 1 2 5 1 14 269 135 269 269 268 268 132
Temporary report and schedule cleanup tralee-rs Data dictionary import tralee COMPLETED FAILED
LDAP_SYNC null System null null null null null INSTANCE PROCEDURE PROCEDURE LDAP_SYNC PROCEDURE
2006-11-14 16:15:20 2006-11-14 15:42:31 2006-11-14 15:33:20 2006-11-14 15:30:20 2006-11-14 15:15:10 2006-11-14 14:33:29 2006-11-14 14:31:29
Ldap synchronization tralee-rs tralee tralee tralee tralee Retrieve entity data COMPLETED COMPLETED COMPLETED COMPLETED COMPLETED Agent activity cleanup
Temporary report and schedule cleanup Ldap synchronization Agent activity cleanup Summary computations
SUMMARY tralee-rs
Past Activity Properties Table 17 describes the information available for each past activity. This information is useful when analyzing a list of past activities.
Table 17:
Property Description
Past Activity Properties
ID Type Datasource State Cancel Active Start End Entity Label Message
The unique ID of the agent activity, type and label. See Table 13 for a description of agent types. The datasource affected by the activity. Shows whether the activity completed or failed. Determines whether the activity was cancelled. The next time an activity is expected to run. Date and time when the activity started (if available). The time the activity ended. The network entity of interest for the specific activity. See Table 13, for agent activity labels and descriptions. Displays server messages related to the activity. Messages are typically received for failed activities.
62
Activity Logs The agent activity log contains a complete view of all the agent activities, which includes current and past agent activities. The agent_admin script allows you to view an activity for a specific run of an agent type. 1. Execute the agent_admin script using the following syntax:
agent_admin -u <user> -p <password> -logs <id> <run_id>
The parameters to be included with the agent_admin script to display activity logs are described in Table 18.
Table 18:
Option
-u <user> -p <password> -logs <id> <run_id>
Parameters for Listing Activity Logs
Description
Username. Password. Lists activity logs, for the agent activity type id and the agent activity run_id.
Note: You can use the -list current option to determine the agent activity type.
Running Activities 1. Execute the agent_admin script using the following syntax:
agent_admin -u <user> -p <password> -run <id>
The parameters to be included with the agent_admin script to run an activity are described in Table 19.
Table 19:
Option
-u <user> -p <password> -run <id>
Parameters for Running Activities
Description
Username. Password. Runs the activity, the id is the identity of agent activity type to run.
Note: You can use the -list current option to determine the agent activity type.
Cancelling Activities You should stop a current activity if the activity continues to fail and is not expected to succeed. Cancelling an activity will only cancel the current activity. It will not stop the agent from performing future scheduled activities.
Caution: Stopping an agent activity may stop an important aspect of the data acquisition process or server maintenance. 1. Execute the agent_admin script using the following syntax:
agent_admin -u <user> -p <password> -cancel <id>
The parameters to be included with the agent_admin script to cancel an activity are described in Table 20.
Table 20:
Option
-u <user> -p <password> -cancel <id>
Parameters for Cancelling an Activity
Description
The administration user name. The administration password. Cancels the activity, the id is the identity of activity to cancel.
Note: You can use the -list current option to determine the agent activity type.ex
64
7.3
KPI Cache Management
The kpicache_admin tool can be used to export/import UDCs from/into the Tivoli Netcool Performance Manager for Wireless system in a format compatible with previous releases. In particular, it applies to UDCs that are not attached to a report or template, as is the case in previous releases. When used to export UDCs, it exports all UDCs in the system. The kpicache_admin tool is also for internal synchronization processes and for debugging. Note: The -asconf option will be used for multiple instances of the application server. It is reserved for use or removal in future implementations of the Tivoli Netcool Performance Manager for Wireless product.
7.3.1
Exporting User Defined Calculations
To export UDCs: 1. Execute the kpicache_admin script using the following syntax:
kpicache_admin -u <user> -p <password> -d <filename> <dsname>
The parameters to be included with kpicache_admin script for dumping the UDC are described in Table 21. Example:
kpicache_admin -u sysadm -p Sysadm01 -d /tmp/UDC_export.xml crosshavenz2-rs
This will result in all provisioned UDCs being exported to a file.

Table 21:
Option
-u <user> -p <password> -d <filename> <dsname>
Parameters for Dumping the UDC

Description
Username. Password. Dumps the file <filename> for the datasource <dsname> . The path to where the file is exported must be specified or the script must be executed where the file is located. The name of the server must be used when specifying the <dsname>, and not the IP address.
7.3.2
Importing User Defined Calculations

kpicache_admin -u <user> -p <password> -l <filename> <dsname>
1. Execute the kpicache_admin script using the following syntax: The parameters to be included with kpicache_admin script for loading the UDC dump are described in Table 22. Example
kpicache_admin -u sysadm -p Sysadm01 -l /tmp/UDC_import.xml crosshavenz2-rs
Table 22:
Option
-u <user> -p <password> -l <filename> <dsname>
Parameters for Loading the UDC

Description
Username. Password. Loads the file <filename> for the datasource <dsname> . The path to where the file is located must be specified or the script must be executed where the file is located. The name of the server must be used when specifying the <dsname>, and not the IP address.
7.3.3
Synchronize internal computation engine KPI cache
After importing UDCs, the user must re-build the internal computation engine KPI cache via the kpicache_admin synchronisation option. Complete the following procedure to synchronize the cache: 1. Execute the kpicache_admin script using the following syntax:
kpicache_admin -u <user> -p <password> <dsname>
The parameters to be included with the kpicache_admin script for synchronizing the KPI cache are described in Table 23. Example:
kpicache_admin -u sysadm -p Sysadm01 crosshavenz2-rs
The parameters to be included with kpicache_admin script for synchronizing the KPI cache are described in Table 23.
Table 23:
Option
-u <user> -p <password> <dsname>
Parameters for Synchronizing KPI Cache
Description
Username. Password. Name of the datasource to be synchronized.
The UDCs will not be visible to the user via the UI until the GUI cache has also being re-built using the DICTIONARY service. This can be manually achieved using the agent_admin CLI tool. Example:
agent_admin -u sysadm -p Sysadm01 -list current | grep DICTIONARY agent_admin -u sysadm -p Sysadm01 -run 8
66
In this example '8' is the job id of the DICTIONARY service. The DICTIONARY service is also scheduled to run every two hours. Note: Re-synchronisation of the KPI cache for a datasource option is for internal use to ensure the datasource synchronisation process occurs correctly and allows for debugging. It does not perform any cache function, it only synchronizes current datasource tables. To update tables so the UDCs are visible to the user from the GUI, the dictionary synchronisation process should be executed by schedule or manually using agent_admin script.
68
8
8.1
System Maintenance
Overview
Maintenance of the Tivoli Netcool Performance Manager for Wireless system includes using scripts, processes, and programs that enable the Tivoli Netcool Performance Manager for Wireless server to run at optimal performance levels. System maintenance tasks include the following tasks: Scheduling System Maintenance. Refer to Scheduling System Maintenance on page 72. Reporting on the current Server Status. Refer to Reporting on the Server Status on page 75. Managing the Oracle Database. Refer to Managing the Oracle Database on page 79. Maintaining Tablespaces. Refer to Database Space Management on page 89. Partition Maintenance. Refer to Partition Maintenance on page 93. Managing Disk Space Usage. Refer to Managing Disk Space Usage on page 101. Backing up the File System. Refer to Backing up the File System on page 103. Working with Log Files. Refer to Working with Log Files on page 104.
69
8.2
Schedule Administration
The scheduler process is configured to run certain standard administrative jobs on scheduled dates and times. You can change the date and time a job is run. The administrative jobs and activities are maintained and monitored by two command line tools: schedule_admin
agent_admin
Refer to agent_admin Command Line Tool on page 58 for more information on the agent_admin tool. To ensure reliable handling of data access and storage, NetworkAssure uses several maintenance jobs and agent activities. The jobs invoked by the system perform the following functions: Maintain database partition, creation and cleanup. Perform job task cleanup. Synchronize information between various subsystems and tables. Perform summary computations. The schedule_admin tool is used to monitor and manage the jobs relating to core NetworkAssure activities such as partitioning the database and miscellaneous task/job cleanup chores.
8.2.1
Scheduled Jobs
Caution: These schedule jobs: aggregator, file_missing, scenario_activation, bhupdate, smupdate, bh_clean, bh_summary currently have no functional impact on Tivoli Netcool Performance Manager for Wireless. Do not stop these jobs from running as it may result in system consequences. These jobs have minimal impact on your system resources. Table 24 below provides a description of the current scheduled jobs controlled by the schedule_admin tool. These jobs are currently in use.
Table 24:
Job
misc_clean
Scheduled Job Descriptions.

Description
Category
Cleanup Partition Maintenance
Task-status, active-task, active-job, schedule, pm-schedule logs are purged every two hours. Purges loaded traffic data and partitions that are older than a specified number of days. The number of days specified is set by the Tivoli Netcool Performance Manager for Wireless Server administrator during installation. Compresses data on the disk. Compressing a disk reorganizes daily data and reclaims as much as 40% of the disk. It also improves query time by 25% to 70%. Creates new daily future partitions to store data.
pm_daily
70
Job
pm_weekly
Category
Description
Partition Maintenance
Purges summary data and busy hour partitions that are older than the date specified in Tivoli Netcool Performance Manager for Wireless during installation for summary and busy hour determinations. Compresses data on the disk. Compressing a disk reorganizes daily data and reclaims as much as 40% of the disk. It also improves query time by 25% to 70%. Creates new weekly partitions to store data. The default scheduled time for the pm_weekly job to run is 20:00:00. Purges summary and busy hour data and partitions that are older than the date specified in Tivoli Netcool Performance Manager for Wireless during installation for summary and busy hour determinations. Creates new monthly partitions to store data related to date-time scope and holiday definitions. Compresses data on the disk. Compressing a disk reorganizes daily data and reclaims as much as 40% of the disk. It also improves query time by 25% to 70%. The default scheduled time for the pm_monthly job to run is 20:01:00. Removes handled-events from the database that are older than a the 30-day retention period on a daily basis. Default scheduled time is 22:00:00. Report group file purge and log files cleanup occurs three times per hour. Cleans up loader activities. It drops orphaned processes associated with the loaders that may still be running.
pm_monthly
event_clean
Cleanup
rgfp
Cleanup Cleanup
drop_orphaned_ext ernal
The schedule_admin script is used to schedule all administrative tasks. It is located in:
$WMCROOT/bin
The schedule_admin script can be executed from any directory as user virtuo.
8.2.2
Usage
schedule_admin [-dbconf conf_name] parameters - List job types: -list types - List all jobs: -list all - List set job type cleanup times: -list cleanup - List jobs to be executed: -list next - Change job type limit: -limit job_type max - Enable job type: -enable job_type - Disable job type: -disable job_type - Set job type cleanup period: -setcleanup job_type period
System Maintenance 71
- period expressed in minutes - Schedule a job: -schedule job_name date time - date format: yyyymmdd - time format: hhmm - Schedule a job immediately: -schedule job_name immediate - Turn off a job: -schedule job_name off
Note: The -dbconf option is reserved for future use or removal in future implementations of the Tivoli Netcool Performance Manager for Wireless product. The list of administrative options for the schedule_admin script are described in Administrative Options for schedule_admin Script on page 73.
8.2.3
Scheduling System Maintenance
Schedule administration tasks by executing the following command using the required syntax:
schedule_admin -schedule <job_name> <administrative option>
For Example: The command below schedules the job pm_daily to run at 11:30 on the 27/08/2007.
schedule_admin -schedule pm_daily 20070827 11:30
8.2.4
Listing the Status of All Scheduled Jobs
The following command lists the status of all scheduled jobs in the system:
schedule_admin -list all
Example output:
JOB FAILURE |==============================================================================| | Job | | Last Run | Time | Failed | Time | Duration | | HH:MM:SS |
|=======================|=====================|=====================|==========| |==============================================================================| JOB SUCCESS |==============================================================================| | Job | | misc_clean | bh_clean | pm_daily | pm_weekly | Last Run | Time | Completed | Time | Duration | | HH:MM:SS |
|=======================|=====================|=====================|==========| | 2006/09/01 16:00:13 | 2006/09/01 16:00:15 | 00:00:02 | | 2006/09/01 17:00:12 | 2006/09/01 17:00:13 | 00:00:01 | | 2006/09/01 10:13:46 | 2006/09/01 10:14:28 | 00:00:42 | | 2006/09/01 10:13:16 | 2006/09/01 10:13:22 | 00:00:06 |
72
| pm_monthly | event_clean
| 2006/08/25 20:02:39 | 2006/08/25 20:05:25 | 00:02:46 | | 2006/09/01 10:15:59 | 2006/09/01 10:16:00 | 00:00:01 |
|==============================================================================| JOBS RUNNING |========================================================| | Job | | Last Run | Time | Duration | | HH:MM:SS |
|=======================|=====================|==========| | drop_orphaned_external| 2006/09/01 17:00:40 | 48:44:00 | |========================================================| NEXT RUN JOBS |=============================================| | Job | | bh_summary | pm_weekly | rgfp | bh_clean | pm_monthly | pm_daily | scenario_activation | misc_clean | event_clean | Next Run | Time | job not scheduled | job not scheduled | job not scheduled | job not scheduled | job not scheduled | job not scheduled | job not scheduled | job not scheduled | job not scheduled | | | | | | | | | | | |
|=======================|=====================|
| drop_orphaned_external| job not scheduled
|=============================================|
8.2.5
Administrative Options for schedule_admin Script

Table 25:
Option
-list types -list all
Administrative Options for schedule_admin Script

Description
Lists the available job types. Lists the status of all the scheduled jobs on the Tivoli Netcool Performance Manager for Wireless platform. Job names are: misc_clean pm_monthly pm_daily event_clean rgfp drop_orphaned_external
-list cleanup
Lists set job type cleanup times.
Option
-list next -limit <job_type> [max] -enable <job_type> -disable <job_type> -setcleanup <job_type> <period> -schedule <job_name> <date> <time> -schedule <job_name> immediate -schedule <job_name> off -schedule <job_name> on
Description
Lists jobs to be executed. Changes the job type limit. Enables a particular job type. Disables a particular job type. Set a cleanup period for a set job type. The period must be entered in minutes. Schedule a particular job. Date must be entered in YYYYMMDD format and time must be entered in the HHMM. Schedule a particular job to run at the current time. Turn off a job. Turn on a job.
74
8.3
Reporting on the Server Status
Some healthchecks can be performed on the Tivoli Netcool Performance Manager for Wireless platform to verify it is stable. If the Tivoli Netcool Performance Manager for Wireless server is rebooted the following process checks can be performed to check all processes started successfully: Database check. See Database Check on page 75. Listener check. See Listener Check on page 75. Directory server check. See Directory Server Check on page 75. SAPMON check. See SAPMON Check on page 76. Tivoli Netcool Performance Manager for Wireless check. See Tivoli Netcool Performance Manager for Wireless Check on page 76. Log Files check. See Log Files Check on page 76. Database Monitoring. See Database Monitoring on page 77. System Monitoring. See Unix System Monitoring on page 77. Quick CPU Sanity check. See CPU Sanity Check on page 78.
8.3.1
Database Check
Important: In a distributed system this check should only be performed on the server hosting the Database component. 1. As user root execute the following:
ps -ef | grep ora_*
8.3.2
Listener Check
ps -ef | grep tns
1. As user root execute the following: The $ORACLE_HOME/bin/tnslsnr LISTENER -inherit process should be returned.
8.3.3
Directory Server Check
Important: In a distributed system this check should only be performed on the server hosting the Application component. 1. As user root execute the following:
ps -ef | grep slapd
The slapd process should be returned. 2. As user root execute the following:
ps -ef | grep admin-serv
Three admin-serv processes should be returned.

8.3.4
SAPMON Check
Important: In a distributed system this check should only be performed on the servers hosting the Application and Gateway components. 1. As user root execute the following:
/usr/ucb/ps -auwwx | grep -w sapmon | grep -v grep
One process should be returned.
8.3.5
Tivoli Netcool Performance Manager for Wireless Check
Important: In a distributed system this check should only be performed on the server hosting the Application component. The Tivoli Netcool Performance Manager for Wireless framework processes are started automatically when the server is rebooted. 1. As user virtuo execute the following to check the Tivoli Netcool Performance Manager for Wireless processes:
sap disp -l
A sample of the output is shown below. [hostname:virtuo] sap disp

NAME as loadcdmanortelevdor3 STATE STARTED stopped SINCE Sep 15, 2006 -
2. Execute the following command to display the number of loaders started. This should correspond with the loaders started in Step 1 above.
ps -ef | grep na_loader | grep -vw grep | wc -l
3. Ensure there are no exceptions in the processes log files.

environment/default.properties
The location of the processes log files is set by the WMCLOGDIR variable in the $WMCROOT/conf/ file. These log files are usually located in $WMCROOT/logs.
8.3.6
Log Files Check
The majority of the Tivoli Netcool Performance Manager for Wireless server log files are stored in $WMCROOT/logs. The main log files to check after restarting any of the processes are:
$WMCROOT/logs/as/default/* $WMCROOT/logs/loader/*
76
8.3.7
Database Monitoring
Note: The following checks should be completed by an Oracle Database Administrator. The following are some quick status checks that can be completed. 1. Alert Log Monitoring - Check the $ORACLE_BASE/admin/vtdb/bdump/alert_vtdb.log file for oracle errors or warnings. 2. Oracle processes trace files - Check the $ORACLE_BASE/admin/vtdb/bdump/*.trc files. 3. Oracle listener status - Check the $ORACLE_BASE/product/9.2.0/network/log/listener.log file. 4. Creation logs - Check the $ORACLE_BASE/admin/vtdb/create/*.log files after the database is created. 5. System Global Area (SGA) Memory Monitoring. Execute the following command to provide free memory information for the main pools in the Oracle SGA:
export ORACLE_SID=vtdb; echo "select * from v\$sgastat;"|sqlplus virtuo/Virtuo01| grep "free memory"
For information on tablespaces, see Database Space Management on page 89.
8.3.8
Unix System Monitoring
The UNIX command sar can be used to show an overview of system resource utilization. For Example: sar 5 5
[hostname:virtuo]sar 5 5 SunOS tralee 5.9 Generic_118558-20 sun4u 14:48:56 14:49:01 14:49:06 14:49:11 14:49:16 14:49:21 Average %usr 80 75 53 50 50 62 %sys 3 2 0 2 0 2 %wio 4 1 3 3 2 3 %idle 13 22 44 45 47 34 09/2
Four columns relate to system activity: %usr displays the percentage of user-assigned CPU activity. %sys displays the percentage of system-assigned CPU activity. %wio displays the percentage of idle time waiting for I/O operations to complete. %idle displays the percentage of time the system is available to process work.
The sar command can be used with two parameters: The first is the number of seconds delay between snapshots. The second is the number of iterations. The above example runs the command 5 times, every 5 seconds. At the end of the iterations, an average figure is given for the time period measured. This allows for the smoothing of any peaks and troughs in system activity. The vmstat command can be executed to check the memory status. Check the clockthread scan rate which is column 12 of the "vmstat" output to see if the system is having difficulty with memory. The swap -s command is also useful. It lists both the memory used and the amount of memory available for future use. For Example:
swap -s total: 2212352k bytes allocated + 582864k reserved = 2795216k used, 2915712k available
8.3.9
CPU Sanity Check

echo "`psrinfo | wc -l` Processors available.\n\n`psrinfo -v`"
1. Execute the following command on the Sun operating system to complete a quick processor check: Sample output is shown below:
2 Processors available. Status of virtual processor 0 as of: 10/04/2006 14:32:20 on-line since 07/17/2006 13:18:17. The sparcv9 processor operates at 1503 MHz, and has a sparcv9 floating point processor. Status of virtual processor 1 as of: 10/04/2006 14:32:20 on-line since 07/17/2006 13:18:17. The sparcv9 processor operates at 1503 MHz, and has a sparcv9 floating point processor.
78
8.4
Managing the Oracle Database

Starting up and Shutting Down the Oracle Database. See Starting and Stopping the Oracle Database on page 79. Types of Oracle Backups. See Types of Oracle Backups on page 80. Completing and Online Backup. See Completing an Online Backup on page 82. Completing and Offline Backup. See Completing an Offline Backup on page 83. Exporting Oracle Data. See Exporting Oracle Data on page 83. Importing Oracle Data. See Importing Oracle Data on page 84. Redo Logs. See Redo Logs on page 85. Performing Hardware Diagnostics. See Performing Hardware Diagnostics on page 88. Restoring Data from Backups. See Restoring Data From Backups on page 88.
The following sections describe in detail the following database management functions:
8.4.1
Starting and Stopping the Oracle Database
By default when the Tivoli Netcool Performance Manager for Wireless server is started or shut down, the system is automatically configured to start and shutdown the Oracle database. Disabling Automatic Startup and Shutdown of the Oracle Database To disable the automatic settings and allow manual startup and shutdown of the Oracle database complete the following: 1. Log in as oracle, the UNIX user for the Oracle database. 2. Open the /var/opt/oracle/oratab file. Database entries in the oratab file appear in the following format:
ORACLE_SID:ORACLE_HOME:{Y|N} Y signifies
that you want the system configured so that the database is automatically started upon system bootup and automatically shutdown when the system is shutdown. that you want to manually startup and shutdown the database.
N signifies
3. Find the entries for all the databases that you want to change. They are identified by the sid in the first field. Change the last field for each entry to N. Example:
vtdb:/appl/oracle/product/9.2.0:N
where /appl/oracle/product/9.2.0:N is the $ORACLE_HOME variable. Usually you should only have one entry for the SID vtdb. Manually Shutting Down the Oracle Database 1. As user virtuo display the processes currently running:
sap disp
2. Stop all SAP processes:

svcadm disable sap-na
3. Monitor the process status and wait for all processes to stop.
sap disp
4. Switch to the UNIX user for the Oracle database:

su - oracle
5. Start SQL*Plus, and connect to the database as the DBA administrator:

$ export ORACLE_SID=vtdb $ sqlplus /nolog SQL> connect / as sysdba
6. Shut down the database and exit:

SQL> shutdown immediate SQL> exit
Manually Starting the Oracle Database 1. Switch to the UNIX user for the Oracle database:
su - oracle

3. Start the database:

SQL> startup SQL> exit
4. Switch to UNIX user virtuo. 5. Start all SAP processes:

6. Monitor the process status and wait for all processes to start.
sap disp
8.4.2
Types of Oracle Backups
Database backup is an important process initiated and carried out on the Tivoli Netcool Performance Manager for Wireless platform on a regular basis. Data is constantly being read from and written to the Oracle database. You need to take special precautions to archive the data correctly. Important! Backup the Oracle database regularly. Backups of the database should be taken more often than backups of the Tivoli Netcool Performance Manager for Wireless system. Oracle software offers three methods for backing up the data server: offline
online exporting and importing of data With an offline backup, you shut down the database before archiving data. Before you can determine which method is appropriate for your installation, you need to consider several factors: Size of available auxiliary storage. Cost of auxiliary storage required by the backup scheme. Level of server availability to users during backup. Ease of data restoration. For any of these backup modes, the auxiliary storage should be large enough to hold the backup image without operator intervention. For complete information about performing online and offline backups, see your Oracle documentation. A brief description of the three types of backups is described below. Online Backup When you request an online backup (also called a hot backup), Oracle software begins writing changed blocks to the redo logs, and stops only when you finish copying files and take the tablespace out of backup mode. Online backup mode has the following advantages: The database remains available to users and data loading at all times. You do not need to back up the entire database all at once. This backup mode allows the quickest and most flexible recovery. Offline Backup Offline backup takes down the whole database and backs it up. During this time, data cannot be loaded and users cannot query the database. Offline backups have the following advantages and disadvantages: A complete backup is simple because nothing is running on the system. Restore time is usually not as fast as in online mode. Restoring from an offline backup is not as flexible as restoring from online backups. Exporting and Importing Data Oracle software provides another method of backing up your data, by using the exp (export) command. Export makes a copy of data and data structures in an operating system file. You can use the file created by exp to move data to another instance of the Oracle database, or to move data from one tablespace into another. If you export data from the database, you can import all or part of it again at a later time. For example, you may wish to take another look at data from a particular day or week after it has been archived. You can restore historical data from archives using Oracle softwares imp (import) feature, without overwriting other data in your database.
Log on to the Tivoli Netcool Performance Manager for Wireless server as user virtuo to use export and import. Make sure the path includes the $LD_LIBRARY, $ORACLE_HOME, and $ORACLE_BASE directories. For complete information on using export and import, see your Oracle documentation.
8.4.3
Completing an Online Backup
If you plan to use the online (hot) method of backing up your database, you can choose to back up a different set of data files each night; you do not need to back up all the data files at once. The hot backup method uses the alter tablespace command to toggle a tablespace between read-only and read-write mode. Caution: The database needs to have Archive Log Mode turned on in order for this procedure to work. For instructions on how to turn on Archive Log Mode, consult your Oracle documentation for more information. Complete the following steps to backup the database while Oracle is running: 1. Switch to the UNIX user for the Oracle database:
su - oracle

3. Begin the backup procedure and exit:

SQL> alter tablespace <tbsname> begin backup; SQL> exit
where <tbsname> is the tablespace name. 4. Back up the files for the <tbsname> tablespace, using operating system commands. 5. Restart SQL*Plus, and connect to the database as the DBA administrator. 6. Enter the following commands:
SQL> alter tablespace <tbsname> end backup;
7. Repeat steps Step 3 through to Step 6 for each tablespace in the database. 8. After you have backed up all files, enter the following commands and exit:
SQL> alter system switch logfile; SQL> exit
Note: Be sure to keep archived redo logs that date back to the oldest archived data file in the backup cycle.
82
8.4.4
Completing an Offline Backup
When you perform an offline (cold) backup, you back up the entire database at once. Consequently, when you need to restore data, you need to restore the entire database in order to recover a part of it. Complete the following steps to shutdown Oracle and backup the database: 1. Login to the Tivoli Netcool Performance Manager for Wireless server as user virtuo. 2. Shut down all processes and queues using the following command:
sap stop all
3. Login as oracle, the UNIX user for the Oracle database. 4. Stop Oracle software, using the method recommended in the Oracle documentation. 5. Back up all the data files, redo log files, and control files using your preferred backup system. For a summary of various backup options, see Backing up the File System on page 103. 6. When the data files are backed up, restart the Oracle software while logged on as user oracle (UNIX user for the Oracle database). 7. Login as virtuo and restart all processes and queues using the following command:
sap start all
8.4.5
Exporting Oracle Data
The export command expects you to specify values for certain parameters, offering you the flexibility to export only certain parts of a database rather than backing up the entire file system. Complete the following steps to run the export utility: 1. Login to the Tivoli Netcool Performance Manager for Wireless server as user virtuo. 2. Check to ensure the path includes the $LD_LIBRARY, $ORACLE_HOME, and $ORACLE_BASE directories. 3. To run export interactively execute:
exp
You can also specify the parameters at the command line. For Example:
exp buffer=10240 file=expdata0617.dmp
4. For a list of keywords, their description and default values, execute:

exp help=y
If you run export with no parameters, Oracle software prompts you for the information provided in Table 26 below: For more detailed information on how to export and import data, see the Oracle Utilities Guide.
Table 26:
Parameter
Username Enter array fetch buffer size Export file Entire database, users, or tables Export table data
Export Parameters
Description
The user name and password of the person running the export. The size of memory to use while writing data to the export file. Typical values are between 10240 and 10485760. The name of the file to write to. The default is expdat.dmp. Allow you to specify names of table owners, or certain tables, to export only a part of the database. Oracle softwares export command by default only writes SQL statements to create objects. This option allows you to export the data as well. Allows you to specify whether the create table statements written to the export file should include initial extent size. Oracle softwares default is compressed=Yes we recommend you set this value to No. Allows you to specify the name of a table or partition to export.
Compress extents
Table or partition to export
8.4.6
Importing Oracle Data
The import command expects you to specify values for certain parameters, offering you the flexibility to import only certain parts of a database rather than the entire file system. Complete the following steps to run the import utility: 1. Login to the Tivoli Netcool Performance Manager for Wireless server as user virtuo. 2. Check to ensure the path includes the $LD_LIBRARY, $ORACLE_HOME, and $ORACLE_BASE directories. 3. To run import interactively execute:
imp
You can also specify the parameters at the command line. For Example:
imp userid=user1/passwd file=expdata0617.dmp
4. For a list of keywords, their description and default values, execute:

imp help=y
If you run import with no parameters, Oracle software prompts you for the information provided in Table 27 below. For more detailed information on how to export and import data, see the Oracle Utilities Guide.
84
Table 27:
Parameter
Username Import file Enter insert buffer size
Import Parameters
Description
The user name and password of the person running export. The name of the import file. The size of memory to use as a work area. The minimum is 4096. Typical values are between 10240 and 10485760. Entering yes displays the list of SQL statements written to the import file. Allows you to replace or preserve existing tables. Allows you to specify whether or not to run grant statements (user privileges) after importing an object. Allows you to import data, or simply create objects. Allows you to import only certain parts of an export file.
List contents of import file only Ignore create error due to objective existence Import grants
Import table data Import entire export file
Troubleshooting Export and Import The three most common errors when using export and import are: Oracle database not available - this error means the database is not open. The Oracle database must be running to use export and import. Only a DBA can import a file exported by another DBA. This error results if a user with no Oracle DBA permissions tries to open an import file. You must be a DBA to do full database export. This error results if you start a full database export without Oracle DBA permissions.
8.4.7
Redo Logs
Oracle software creates log files called redo logs, each of which contain a sequential log of actions applied to the database. These redo logs accumulate daily and contain up-to-the-minute details on database operations. By default, the Tivoli Netcool Performance Manager for Wireless server installs the Oracle database in archive log mode. Although archive log mode requires more disk space for daily operations, it provides point-in-time recovery in case of data loss. You can restore data from the last online backup, then restore data from all archive logs since that date to return your database to its most current state. Note: Archive logs can take up large quantities of disk space if you do not regularly back them up. If you set up a backup schedule with only one or two full backups per week, you need to check the archive logs if you are not backing them up regularly.
8.4.8
Archiving Redo Logs
ARCHIVELOG Mode Each database should have ARCHIVELOG mode enabled. This allows the redo logs to be archived instead of being overwritten. Store the archive logs in a separate place to the rest of the database files and ensure that they are periodically backed up. The archive logs can be used if and when a restore of the database is required to restore the database to the point in time when the database went down. This section describes how to check if the database is in ARCHIVELOG mode and how to enable and disable ARCHIVELOG mode. Checking ARCHIVELOG Mode Status To check ARCHIVELOG mode status, complete the following: 1. Log in as user oracle and execute the following commands:
$ export ORACLE_SID=<MYDB>
where <MYDB> is the name of the database

$ sqlplus /nolog SQL> connect / as sysdba
2. To check the ARCHIVELOG mode status, execute the following SQL command:
SQL> archive log list;
If the database is in ARCHIVELOG mode the following output is returned:

Database log mode Automatic archival Archive Mode Enabled
If the database is not in ARCHIVELOG mode the following is returned:

Database log mode Automatic archival No Archive Mode Disabled
Updating ARCHIVELOG Settings Update the log destination where the archive log files are stored from the default to a location which has sufficient space to store the archive logs. The recommended location is /oradump/<MYDB>. Ensure the log destination exists prior to setting it. Create the directory as user oracle if it does not already exist. Update the target archive location by completing the following: 1. Log in as user oracle and execute the following commands:

2. To change the archive log destination, execute the following SQL command:
SQL> alter system set log_archive_dest='/oradump/<MYDB>' scope=both;
86
Enabling ARCHIVELOG Mode To enable ARCHIVELOG mode status, complete the following: 1. Log in as user oracle and execute the following commands:

2. To enable ARCHIVELOG mode status, execute the following SQL commands:

SQL> Shutdown SQL> Startup mount SQL> Alter database archivelog; SQL> alter database open;
SQL> archive log list; Database log mode Automatic archival Archive destination Oldest online log sequence Next log sequence to archive Current log sequence Archive Mode Enabled /oradump/<MYDB> 7 7 9
The database is now in ARCHIVELOG mode. Disabling ARCHIVELOG Mode To disable ARCHIVELOG mode status, complete the following: 1. Log in as user oracle and execute the following commands:

2. To enable ARCHIVELOG mode status, execute the following SQL commands:

SQL> Shutdown SQL> Startup mount SQL> Alter database noarchivelog; SQL> alter database open;
SQL> archive log list; Database log mode Automatic archival Archive destination Oldest online log sequence No Archive Mode Disabled /oradump/<MYDB> 7
Current log sequence
The database is now in NOARCHIVELOG mode.
8.4.9
Performing Hardware Diagnostics
It is generally a good idea to run diagnostic checks on your hardware before restoring data, if you encounter a problem such as a corrupt database. Other database errors can surface when you restore a missing or corrupt file. For Example: When mounting a database, Oracle software stops when it encounters the first error, even though more than one error might exist. If you perform hardware diagnostics before restoring the missing file, you might find other corrupt databases as well.
8.4.10
Restoring Data From Backups
How you restore data depends on the procedures you used to back it up, as well as what you need to restore. For complete information on data restoration procedures, please see your Oracle documentation.
88
8.5
Database Space Management

$WMCROOT/bin
The dbspace_admin tool allows you to monitor and extend the database file set. It is located in:
The dbspace_admin script can be executed from any directory as user virtuo.
8.5.1
Usage
dbspace_admin [-dbconf conf_name] -stats -addfile <tablespace> <path> <size_in_mb> -modifyfile <path> <size_in_mb>
Note: The -dbconf option is reserved for future use or removal in future implementations of the Tivoli Netcool Performance Manager for Wireless product. The sections below detail how to complete the following: Monitor Oracle Tablespaces. See Monitoring Oracle Tablespaces on page 89. Increase tablespace size. See Increasing Tablespace Size on page 91 .
8.5.2
Monitoring Oracle Tablespaces
Oracle tablespaces should be monitored regularly to ensure enough space is available for new data to load. To monitor free space in the tablespaces complete the following: 1. Execute the dbspace_admin script using the following syntax:
dbspace_admin -stats
The -stats option to is described in Table 28.

Table 28:
Option
-stats
dbspace_admin Option for Monitoring Tablespaces

Description
Provides the following tablespace statistics: Tablespace Name Id Size Percentage of free space available Oracle data files associated with each tablespace.
For Example:
dbspace_admin -stats tablespace enterprise enterprise01.dbf id 8 size 300 free% 98.83 file_name /oradata02/vtdb/
system traffic_jumbo traffic_jumbo01.dbf traffic_jumbo traffic_jumbo2.dbf traffic_jumboplus traffic_jumboplus01.dbf traffic_jumboplus traffic_jumboplus2.dbf traffic_jumboplus traffic_jumboplus3.dbf traffic_jumboplus traffic_jumboplus4.dbf traffic_jumboplus traffic_jumboplus5.dbf traffic_jumboplus traffic_jumboplus6.dbf traffic_jumboplus traffic_jumboplus7.dbf traffic_jumboplus traffic_jumboplus8.dbf traffic_large traffic_large01.dbf traffic_large traffic_large2.dbf traffic_large traffic_large3.dbf traffic_large traffic_large4.dbf traffic_large traffic_large5.dbf traffic_large traffic_large6.dbf traffic_large traffic_large7.dbf traffic_large traffic_large8.dbf traffic_medium traffic_medium01.dbf traffic_medium traffic_medium2.dbf traffic_medium traffic_medium3.dbf traffic_medium traffic_medium4.dbf traffic_medium traffic_medium5.dbf traffic_small traffic_small01.dbf
1 6 25 7 26 27 28 29 30 31 32 5 18 19 20 21 22 23 24 4 14 15 16 17 3
350 2048 2048 2048 2048 2048 2048 2048 2048 2048 1024 2048 2048 2048 2048 2048 2048 2048 1024 2048 2048 2048 2048 2048 2048
48.16 79.2 92.68 99.8 89.84 99.8 99.8 99.8 99.8 99.8 99.61 99.99 95.17 99.99 99.99 99.99 99.99 99.99 99.98 99.88 99.98 99.98 99.98 99.1 99.99
/oradata01/vtdb/system01.dbf /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata04/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata03/vtdb/ /oradata02/vtdb/ /oradata02/vtdb/ /oradata02/vtdb/ /oradata02/vtdb/ /oradata02/vtdb/ /oradata04/vtdb/
90
traffic_small traffic_small2.dbf undotbs wm_client wm_client01.dbf wm_flexpm wm_flexpm01.dbf wm_queues wm_queues01.dbf wm_sa tablespace enterprise system traffic_jumbo traffic_jumboplus traffic_large traffic_medium traffic_small undotbs wm_client wm_flexpm wm_queues wm_sa 2
13
2048 2048
98.51 97.34
/oradata04/vtdb/
/oradata01/vtdb/undotbs01.dbf /oradata02/vtdb/ /oradata02/vtdb/ /oradata02/vtdb/ /oradata02/vtdb/wm_sa01.dbf free 296.5 168.56 3520 15124 used 3.5 181.44 576 236 100.75
9 10 11 12 total 300 350 4096 15360 15360 10240 4096 2048 1024 6144 256 256
1024 6144 256 256 over -
67.68 87.92 95.61 94.34 free% 98.83 48.16 85.94 98.46 99.34 99.78 99.25 97.34 67.68 87.92 95.61 94.34
15259.25 10217.5 22.5 4065.38 30.63 1993.63 54.38 693 5402 244.75 241.5 331 742 11.25 14.5
8.5.3
Increasing Tablespace Size
If the following setups have been performed appropriately on the Tivoli Netcool Performance Manager for Wireless platform it should not be necessary to increase tablespace sizes: Tablespaces setup - undertaken during initial deployment of the Tivoli Netcool Performance Manager for Wireless database. Partitions setup - to effectively remove or archive data if it is not required. Note: Only experienced Oracle Database Administrators should change tablespace sizes. You might need to increase tablespace size under the following circumstances: If you anticipate loading large amounts of data. If current tablespace usage cannot hold the anticipated load. If you encounter Oracle error messages indicating that certain tablespaces are out of space. To increase the size of a tablespace use one of the following two options: addfile which adds new database files or increases the size by the amount specified in megabytes.
modifyfile which increases the size of the existing database files to the size specified in megagbytes Add a Database File Complete the following to add a database file: 1. Execute the dbspace_admin script using the following syntax:
dbspace_admin -addfile <tablespace> <path> <size_in_mb>
The parameters used with the -addfile option are described in Table 29.
Table 29:
Option
<tablespace> <path> <size_in_mb>
Parameters of Adding a Tablespace
Description
The name of the tablespace. The path to the database file. The size in megabytes you wish to increase the current tablespace by.
For Example:
dbspace_admin -addfile traffic_jumbo /oradata03/vtdb/ 1024
This will increase the size of the current traffic_jumbo tablespace by 1024 Mb. Modifying a Database File Complete the following to modify a database file: 1. Execute the dbspace_admin script using the following syntax:
dbspace_admin -modifyfile <path> <size_in_mb>
The parameters used with the -modifyfile option are described in Table 30.
Table 30:
Option
<path> <size_in_mb>
Parameters for Modifying a Datafile
Description
The path to the database file. Increases the existing database file to the size specified in megabytes.
8.5.4
Recover from a Full Tablespace
Note: The -recoverfulltbs option is reserved for future use or removal in future implementations of the Tivoli Netcool Performance Manager for Wireless product. If a full tablespace issue occurs please contact your Vallent customer support representative to resolve the problem.
92
8.6
Partition maintenance is a system maintenance job which is responsible for the creation, deletion and optimization of date range partitioned tables. It enables a seamless process of creating, deleting, moving and analyzing partitions without impacting the performance of the system. Tivoli Netcool Performance Manager for Wireless uses partitioned, index organized tables (IOTs) for storing traffic data. This ensures that large data tables are stored in a structured format, with the aim of minimizing the usage of space and optimizing the performance of report generation. The partition maintenance job deals with the adding of partitions, to ensure that sufficient partitions exist in the future, and with the purging of old data from the system. The adding and deleting of data is based on configurable data retention settings within the partition maintenance process. As well as creating and deleting data, the partition maintenance process helps optimize the database performance by: analyzing tables and gathering partition level statistics. moving data in IOT partitions to compress and optimize the data
8.6.1
Partition Maintenance Jobs
The partition maintenance process is automated through several jobs that are scheduled to run automatically. These jobs are used to automatically create partitions for future dates and also to remove partitions where old unwanted data is stored. The scheduler automatically sets partition maintenance to run at a specified time nightly. The partition maintenance jobs that are executed are described in Table 24. To change the default time when partition maintenance jobs are executed refer to Schedule Administration on page 70.
8.6.2
Partition Maintenance Command Line Tool
Partition maintenance uses a command line tool, called part_admin, to allow users to manually run partition maintenance tasks and update partition maintenance settings. The part_admin script is located at the following location and can be executed from any directory as user virtuo:
$WMCROOT/bin/part_admin
Partition Maintenance CLI parameters The scope of the partition maintenance CLI can be limited by the following parameters:
[-type] [-subtype] [-tabtype] [-sdate] [-edate] [-filter] [-param] [-value]
Partition maintenance CLI parameters are described in the following table:
Table 31:
Parameter
-type -subtype
Partition maintenance CLI parameters
Description
Type of table, examples include TECHPACK, ENTITY and TABLE. Subtype associated with a specific type. Subtypes are associated with the main types, examples include: TECHPACK For example, "Neutral GSM Core", "Ericsson GSM BSS
R10"
ENTITY: TABLE
-tabtype -filter
For example, "CELL", "MSC", "OSI_Channel" For example, "traffic", "softalarm", "sSUMDaily"
Table type, examples include "traffic", "softalarm", "sSUMDaily" Filter the output by table name, examples include
"ERI_BSC_TBF_GSL_TAB" "ERI_%_TAB"
-sdate -edate -param
Start time, sdate format: yyyymmddhh24. End time, edate format: yyyymmddhh24. Parameter for updating partition maintenance parameters, examples include data_retention, tablespace_name Value for update partition maintenance parameters and settings.
-value
Partition Maintenance CLI Tasks The following table lists tasks that can be completed using the part_admin tool:
Table 32:
Option
-listtypes
Partition maintenance CLI parameters
Description
The scope of partition maintenance tasks can be limited by type. The -listtypes option can be used to list the available types on the system. Valid types are TECHPACK, ENTITY and TABLE. Subtypes are associated with the main types, examples include: TECHPACK For example, "Neutral GSM Core", "Ericsson GSM BSS R10" ENTITY: For example, "CELL", "MSC", "OSI_Channel" TABLE For example, "traffic", "softalarm", "sSUMDaily" Scope can be limited using [-type]
-add
Add partitions. Scope can be limited using:

[-type] [-subtype] [-tabtype] [-filter] [-sdate] [-edate]
-delete
Delete partitions. Scope can be limited using:

94
Option
-pin
Description
Pin partitions into the database to allow them to be maintained outside of the defined data retention periods. Scope can be limited using:
-unpin
Unpin partitions from the database to allow them to be dropped from the system when they are outside of the defined data retention periods. Scope can be limited using:
-export
Export partition data from the database. Scope can be limited using:
[-tname] <TABLE_NAME> [-sdate] <DATE> [-edate] <DATE>
or,
[-pname] <TABLE_NAME>:<PART_NAME> -import
Import data into the database which has been previously exported using the part_admin tool. Scope can be limited using:
[-pname] <TABLE_NAME>:<PART_NAME>
-showparams -listparams
Display all configurable partition maintenance parameters. Display all parameters settings. Scope can be limited using:
[-type] [-subtype] [-tabtype]
-updateparams
Update specific partition maintenance settings. Scope can be limited using:

[-type] [-subtype] [-tabtype] [-filter] [-param] [-value]
-updatesessions
Update the number of configurable parallel partition maintenance sessions. Scope can be limited using:
[-value]
-listspace -logs
Display the current space settings per tablespace. Display the partition maintenance logs per job id. Scope can be limited using:
[-id]
-errors -status -help
Display the partition maintenance error logs per job id. Display the status of the active partition maintenance job. Display help.
8.6.3
Adding Partitions
Adding a partition adds a partition to an individual table or a group of tables. Partitions are generally added to a partition to allow backloading of data into a table or if specific data was being added to a particular table. Adding partitions outside of the retention period will also pin them into the database. The syntax of the add partitions option is as follows:
part_admin -add [-type] [-subtype] [-tabtype] [-filter] -sdate -edate
The following example will add partitions to all traffic tables in the Neutral GSM Core technology packs from the 1st January 2007 to the 10th January 2007:
part_admin -add -type TECHPACK -subtype "Neutral GSM Core" -tabtype "traffic" sdate 2007010100 -edate 2007011000
The following example will add partitions to the table ERI_BSC_TBF_GSL_TAB from the 1st January 2007 to the 10th January 2007:
part_admin -add -filter "ERI_BSC_TBF_GSL_TAB" -sdate 2007010100 -edate 2007011000
Backloading data When you backload old data, you must ensure partitions exist for the time period that you are backloading for. If these partitions do not exist then you must add the partitions before commencing backloading. Existing partitions can be shown using the following command:
part_admin -listpart [-type] [-subtype] [-tabtype] [-filter]
Partitions are created based on the retention settings defined in the vmm/default.properties file and in the PART_TABLES table. The following command will show the current retention settings on the system:
part_admin -listparams [-type] [-subtype] [-tabtype] [-filter]
where:
DATA RETENTION PAST RETENTION
is the number of partitions which will be kept in the past. is the minimum number of partitions which are automatically created in the past. is the minimum number of partitions which are automatically create in the
FUTURE RETENTION
future. If the necessary partitions do not exist for the data being backloaded, then run the part_admin -add command to add the necessary partitions. This will ensure that the data is loaded correctly and will be managed correctly by partition maintenance.
8.6.4
Deleting Partitions
Deleting a partition drops a partition from an individual table or a group of tables. The syntax of the deleting partitions option is as follows:
96
part_admin -delete [-type] [-subtype] [-tabtype] [-filter] -sdate -edate
The following example will delete partitions from all daily summary tables of entity type X25 from the 1st January 2007 to the 10th January 2007:
part_admin -delete -type ENTITY -subtype "X25" -tabtype "sSUMDaily" -sdate 2007010100 -edate 2007011000
The following example will delete partitions from all tables with a name like %_DSM from the 1st January 2007 to the 10th January 2007:
part_admin -delete -filter "%_DSM" -sdate 2007010100 -edate 2007011000
Important: Deleting partitions on a regular basis is not usually required. Scheduled partition maintenance jobs usually control this task. If you need to delete partitions using this procedure ensure you are deleting the correct partitions to prevent loss of a large amount of important data.
8.6.5
Pinning Partitions
Partitions are pinned into the database to allow them to be maintained outside the defined data retention periods. The syntax of the pinning partitions option is as follows:
part_admin -pin [-type] [-subtype] [-tabtype] [-filter] -sdate -edate
The following example will pin partitions from all softalarm tables of entity type X25 from the 1st January 2007 to the 10th January 2007:
part_admin -pin -type TABLE -subtype "softalarm" -sdate 2007010100 -edate 2007011000
8.6.6
Unpinning Partitions
Partitions are unpinned from a database to allow them to be dropped when they are outside the defined data retention periods. The syntax of the pinning partitions option is as follows:
part_admin -unpin [-type] [-subtype] [-tabtype] [-filter] -sdate -edate
The following example will unpin partitions from all softalarm tables from the 1st January 2007 to the 10th January 2007:
part_admin -unpin -type TABLE -subtype "softalarm" -sdate 2007010100 -edate 2007011000
8.6.7
Exporting Partitions
Partitions can be exported to allow them to be maintained outside of the database. Partitions can be exported for a particular date range or for a particular partition. The syntax of the exporting partitions options are as follows:
part_admin -export [-tname] <TABLE_NAME> [-sdate] <DATE> [-edate] <DATE>
or,
part_admin -export [-pname] <TABLE_NAME>:<PART_NAME>
The following example will export partitions in table ERI_BSC_TBF_GSL_TAB from the 1st January 2007 to the 10th January 2007:
part_admin -export -tname ERI_BSC_TBF_GSL_DSM -sdate 2007010100 -edate 2007011000
The following example will export the partition P2007011000 in table ERI_BSC_TBF_GSL_TAB:
part_admin -export -pname ERI_BSC_TBF_GSL_DSM:P2007011000
8.6.8
Importing Partitions
Partitions which have been exported through the part_admin CLI can be re-imported using the import option. The syntax of the exporting partitions option is as follows:
part_admin -import [-pname] <TAB_NAME>:<PART_NAME>
The following example will import the partition P2007011000 in table ERI_BSC_TBF_GSL_DSM:
part_admin -import -pname ERI_BSC_TBF_GSL_DSM:P2007011000
8.6.9
Showing Parameters
The show parameters option allows the user to see all the configurable partition maintenance parameters. The syntax of the show parameters option is as follows:
part_admin -showparams
8.6.10
Listing Parameters
The list parameters option allows the user to view the current parameter settings, limited by type/subtype/table type or table name (filter). The syntax of the list partitions option is as follows:
part_admin -listparams [-type] [-subtype] [-tabtype]
8.6.11
Updating Parameters
The update parameters option allows the user to update the current parameter setting. The user can update the retention periods, the partitioning period, tablespace etc.
98
Important: The impact of these changes on the system should be considered before implementation. The updates to a parameters setting can be limited by type/subtype/table type or table name. The syntax of the update parameters option is as follows:
part_admin -updateparams [-type] [-subtype] [-tabtype] [-param] [-value]
The following example will update the data_retention to 90 days for all softalarm tables:
part_admin -updateparams -type TABLE -subtype "softalarm" -param data_retention value 90
8.6.12
Listing Partitions
Partitions can be listed by table name to allow the user to see what partitions currently exist on the system. The list can be limited by type/subtype/table type/table name or time period. The syntax of the list partitions option is as follows:
part_admin -listpart [-type] [-subtype] [-tabtype] [-filter] [-sdate] [-edate]
8.6.13
List Pinned Partitions
Pinned partitions can be listed by table name to allow the user to see what partitions are currently pinned on the system. The list can be limited by type/subtype/table type or table name. The syntax of the list pinned partitions option is as follows:
part_admin -listpart [-type] [-subtype] [-tabtype] [-filter]
8.6.14
List Sessions
The list sessions option allows the user to view the current number of configurable parallel partition maintenance sessions. The syntax of the lists sessions option is as follows:
part_admin -listsessions
8.6.15
Update Sessions
The update sessions option allows the user to update the number of configurable parallel partition maintenance sessions. The number of parallel partition maintenance sessions is the number of parallel, slave sessions which can run to create partitions. Important: The number of sessions is dependent on the of CPUs on a system and the impact of changing this setting should be considered before implementation.
The syntax of the update sessions option is as follows:

part_admin -updatesessions -value
8.6.16
List Spaces
The list space option allows the user to view the current space settings per tablespace. The syntax of the list space option is as follows:
part_admin -listspace
8.6.17
Show Logs
The logs option allows the user to view the partition maintenance logs. The syntax of the logs option is as follows:
part_admin -log [-id xxx/latest]
The -log option will give a summary of all partition maintenance logs by log id along with a start time, end time and total duration. The -log -id xxx option will give detailed logs of all tasks that ran for a particular log. The -log -id latest option will give detailed logs of all tasks that ran for the latest logs.
8.6.18
Show Errors
The errors option allows the user to view the partition maintenance error logs. This will show all errors that have occurred in partition maintenance in the last 30 days, ordered by time. The syntax of the logs option is as follows:
part_admin -errors
8.6.19
Show Status
The status option allows the user to view the current status of the active partition maintenance job. The syntax of the update partitions option is as follows:
part_admin -status
100
8.7
Managing Disk Space Usage

Ensure enough disk space is available for the requirements of the database. Ensure enough disk space is available for the software installation. Archiving for log files is setup.
Before attempting to manage disk space, you must meet the following requirements:
Whenever disk utilization is near 100%, the Tivoli Netcool Performance Manager for Wireless processes may be blocked. It is important to monitor disk space and remove old files because recovery from a disk overflow might require rebooting the system. You should conduct regular checks on the amount of disk space available in order to ensure that: Oracle is running at peak performance. Server processes continue to run. Data continues to load. The main files to monitor for disk space usage are: Data files Log files Tablespace files All other files should be a static file size.
8.7.1
Monitoring the Oracle Storage Directories
1. Execute the following command as user virtuo to report the total disk space usage in the oracle storage directories:
du -ks /ora*
Example output is shown below.

4730154 /oradata01 18675938 17844018 24129314 2 393458 393458 /oradata02 /oradata03 /oradata04
/oradump /oralogs1 /oralogs2
2. Execute the following command as user virtuo to report the available capacity in the oracle storage directories:
df -k /ora*
8.7.2
Monitoring the $WMCROOT/logs Directories
1. Execute the following command as user virtuo to report on the disk space usage in each of the $WMCROOT/log directories:
du -k $WMCROOT/logs

53 33 18 29 1564 1565 41094 41095 9679 2 1 4066 911 57452 /appl/virtuo/logs/sapmgr /appl/virtuo/logs/sapmon /appl/virtuo/logs/sap_cli /appl/virtuo/logs/conf_read /appl/virtuo/logs/web/default /appl/virtuo/logs/web /appl/virtuo/logs/as/default /appl/virtuo/logs/as /appl/virtuo/logs/vmm /appl/virtuo/logs/sapmgr_cli /appl/virtuo/logs/loader/CHOPPED /appl/virtuo/logs/loader /appl/virtuo/logs/gways /appl/virtuo/logs
8.7.3
Monitoring the $WMCROOT/var/loader/spool Directories
1. Execute the following command as user virtuo to report the total disk space usage in the $WMCROOT/var/loader/spool directories:
du -ks /$WMCROOT/var/loader/spool

367832 /appl/virtuo/var/loader/spool
8.7.4
Reporting the Size of the File systems
The following command reports on the size of the filesystems and the space in use: 1. Execute the following command as user virtuo:
df -k /ora* $WMCROOT

Filesystem /dev/dsk/c0t2d0s0 /dev/dsk/c0t2d0s1 /dev/dsk/c0t3d0s0 /dev/dsk/c0t3d0s1 /dev/dsk/c0t2d0s3 /dev/dsk/c0t0d0s6 /dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s0 kbytes used avail capacity 19% 74% 70% 95% 1% 4% 4% 64% Mounted on /oradata01 /oradata02 /oradata03 /oradata04 /oradump /oralogs1 /oralogs2 /appl 25822151 4755778 20808152 25822151 18701562 6862368 25822151 17869642 7694288 25822151 24154938 1408992 10327372 10327372 10327372 10258 10213841 403714 9820385 403714 9820385
15493995 9810710 5528346
102
8.8
Backing up the File System
The Tivoli Netcool Performance Manager for Wireless backup scripts are installed as part of the Tivoli Netcool Performance Manager for Wireless core install. The backup_install and virtuo_backup scripts are located in:
$WMCROOT/admin/common/install/scripts
To run the backup install execute the following as user root:

1. $WMCROOT/admin/common/install/scripts/backup_install -wmcr wmcroot
2. Execute the backup script:

$WMCROOT/admin/common/install/scripts/virtuo_backup <options>
The options to be included with the virtuo_backup script are described in Table 33 below.
Table 33:
Option
<-f>
Backup Options for virtuo_backup Script
Description
Performs a full backup. The full backup is setup to run at 3am on every Sunday. Performs an incremental backup. The incremental backup is set to ran at 5am Monday to Saturday each week. Specify the device with the -d option. The default device is /dev/ rmt/0n. To change the default device use the -d option with the new device.
<-i>
<-d> [device]
8.9
Working with Log Files
Server log files can be useful when troubleshooting; however, accumulations of log files can unnecessarily take up disk space. This section gives an overview of the types of log files stored on the Tivoli Netcool Performance Manager for Wireless platform and describes utilities available for archiving them. Note: Log files are helpful when you need to contact your technical support representative. The cron is setup as part of the Tivoli Netcool Performance Manager for Wireless installation. There are two different cron setups installed: Virtuo user cron. Root user cron. The cron install uses the following two crontab files to setup the virtuo and root user:
$WMCROOT/admin/common/cron/core_root_crontrab $WMCROOT/admin/common/cron/core_virtuo_crontrab
The output below is a sample of the root user cron entries:

[hostname:root] crontab -l 0 23 * * * /appl/virtuo/admin/oracle/cron/roll_listener_log 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 0 23 * * * /appl/virtuo/admin/common/cron/roll_cron_log 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d uct/9.2.0/network/log listener.log.\* 0 10,16,23 * * * /appl/virtuo/admin/common/cron/cron_script vtdb_arch_\* 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d slapd-`/usr/bin/hostname`/logs access.\* 0 23 * * * /appl/virtuo/admin/common/cron/cron_script -r -d slapd-`/usr/bin/hostname`/logs errors.\*
2 /var/cron log.\* 2 /var/cron olog.\* 2 /appl/oracle/prod-r -d 1 /oradump/vtdb 2 /appl/virtuo/ds/ 2 /appl/virtuo/ds/
Note: The Removing Log Files, Archiving Log Files. The archive_loader_data script is used to archive .lif files.These are files produced by the gateways and processed by the loaders in large volumes. The archive_loader_data script is located in:
[hostname:virtuo] $WMCROOT/admin/common/cron
8.9.1
Information about Log Files
Tivoli Netcool Performance Manager for Wireless can perform the following functions on log files: Remove old log files. See Removing Log Files on page 106.
104
Archive old log files.See Archiving Log Files on page 106. The cron_script script is used to perform the functions described above. It is located in:
[hostname:virtuo] /$WMCROOT/admin/common/cron
For help when using the cron_script script, execute the following:
./cron_script -help
Tivoli Netcool Performance Manager for Wireless saves the following types of logs on the server: Appserver logs VMM tool - Technology Pack Activation logs SAP Manager logs Loader logs Configuration logs Install logs Web access logs Directory server logs Flex logs Oracle logs - These logs should be internally handled by Oracle. Below is a list of some Appserver logs:
./as/default/as-boot.log ./as/default/as-agent.log ./as/default/as-report.log ./as/default/as-splash-report.log ./as/default/as-splash-chart.log ./as/default/as-sentry.log ./as/default/as-loader.log ./as/default/as-server.log
The cron entries below are setup for the following log files within the Tivoli Netcool Performance Manager for Wireless installation. Tivoli Netcool Performance Manager for Wireless supports the removal, rollover and archiving of the files below:
[hostname:virtuo]crontab -l 0 1 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 31 /data/trace_archive1 \*.log.\* 0 1 * * * /appl/virtuo/admin/common/cron/cron_script -a -d 0 /data/trace_log1 \*.log.\* /data/trace_archive1 0 3 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 2 /appl/virtuo/tomcat/ logs vt\*.log 0 0 * * * /appl/virtuo/admin/common/cron/cron_script -c -d 512 /appl/virtuo/logs/ loader virtuo_loader.log 30 0 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/logs/ loader/CHOPPED virtuo_loader.log-\*
0 2 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/var/ loader/bad PDO_\* 10 2 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/var/ loader/dat PDO_\* 20 2 * * * /appl/virtuo/admin/common/cron/cron_script -r -d 5 /appl/virtuo/var/ loader/log PDO_\*.log
8.9.2
Removing Log Files
Complete the following steps as user virtuo to remove a log file: 1. Move to the directory where the cron_script is located:
cd /$WMCROOT/admin/common/cron
2. Execute the following command:

./cron_script -r -d <dirname> <filename>
The parameters to be included with the -r option to remove old log files are described in Table 34.
Table 34:
Option
<-d> (optional)
Parameters for Removing Log Files
Description
The -d option is optional. Use the next argument to specify the age of the file in days. The directory the log files are currently stored in. The filename of the file you want to remove.
<dirname> <filename>
Note: Multiple files can be removed at the same time using the (*) wildcard. For example:
***/appl/virtuo/admin/common/cron/cron_script -r -d 31 /data/ trace_archive1\*.log\*
8.9.3
Archiving Log Files
Complete the following steps as user virtuo to archive a log file: 1. Move to the directory where the cron_script is located:
cd /$WMCROOT/admin/common/cron
2. Execute the following command:

cron_script -a -d <dirname> <filename> <archive_dir>
The parameters to be included with the -a option to remove old log files are described in Table 35.
106
Table 35:
Option
<-d> (optional)
Parameters for Archiving Log Files
Description
The -d option is optional. Use the next argument to specify the age of the file in days. The directory the log files are currently stored in. The filename of the file you want to remove. The directory to archive the files to.
<dirname> <filename> <archive_dir>
Note: Multiple files can be archived at the same time using the (*) wildcard. For Example:
***/appl/virtuo/admin/common/cron/cron_script -a -d 0 /data/trace_log1\*.log.\* / data/trace_archive1
108
9
9.1
Tools
This chapter covers a number of additional tools available to administer and support the Tivoli Netcool Performance Manager for Wireless software.
Overview
Importing Report definitions Time Zone Support for Reporting Holiday Maintenance Data Availability
This chapter covers the following:
109
9.2
Importing and Exporting User Documents and Report Results
The report_impexp tool provides functionality for importing and exporting the following user documents: report definitions report templates report schedules report results Note: Caution is required when transferring exported files to and from a MicrosoftTM WindowsTM computer. Some Windows text editors automatically insert carriage returns in the file. You can remove the carriage returns by using the unix2dos program on a Solaris computer. The report_impexp tool is located in:
$WMCROOT/bin
The report_impexp tool can be executed from any directory as user virtuo. For help when using the report_impexp script, execute the following:
report_impexp -h [1|2|3|4]
where 1 = help for importing artifacts 2 = help for exporting artifacts 3 = help for importing report results 4 = help for exporting report results
9.2.1
Importing definitions, templates, schedules and folders
The import operation imports all user documents from an import file or directory to a destination directory. usage
report_impexp -i -u <user_id> -p <password> -f <file|dir> [-l <server_directory>] -dup <failonerror|overwrite|ignore>
options The options and parameters to be used with the report_impexp tool for importing report definitions, templates, schedules and folders are described in the following table.
110
Table 36:
Option
-i -u <user> -p <password> -f <file|dir>
Options for report_impexp tool - import user documents

Description
Initiates the import process. The username of the user invoking the import tool. The users password. Name of xml file from which to import users documents. Can be a reference to a file or a folder. If a reference to a folder is given then a recursive search is carried out for all files with an .xml extension. Each file is then imported.
-l <server_directory>
Optional. Destination on server that is the root location for imported documents. This must be a valid user folder location. For example:
/Users/sysadm /Users/peter/folder1 /Users/mary/backup/daily
If the -l option is not used then the location and associations are taken from the imported document(s).
-dup [failonerror|overwrit e|ignore]
Import process behavior. This option is specified with one of the following three parameters:
failonerror - fail when an existing document with the same
name is found overwrite - overwrite when existing documents with the same names are found ignore - ignore documents that already exist
Examples
report_impexp -i -u sysadm -p syspwd -f import.xml -l /Users/mark -dup ignore report_impexp -i -u sysadm -p syspwd -f import.xml -dup ignore
9.2.2
Exporting definitions, templates and schedules
The export operation exports all specified user documents to an output file. usage
report_impexp -e -c <a|d|t|s> -u <user_id> -p <password> -m <pattern_match> -f <file> -l <server_directory> [-r <true|false]
options The options and parameters to be used with the report_impexp tool for exporting report definitions, templates, schedules and folders are described in the following table.
Tools 111
Table 37:
Option
-e -c
Options for report_impexp tool - export user documents

Description
Initiates the export process. Content or type of object to export. This option is specified by one of the following parameters:
a - all of the types below d - report definitions t - report templates s - report schedules The all definitions and template selections will include any dependent folders.
-u <user> -p <password> -m <pattern_match>
The username of the user invoking the export tool. The users password. Pattern matches for user documents using standard wildcards. Quotes must be placed around the wildcards. For example, for all report definitions use "*". File to export documents to. This must be an xml file. Location on server to export the file to. The user should have permission to read the document contents of the selected location. Must be a valid user folder location.
-f <file> -l <server_directory>
-r
Optional. Recursive search (sub-directories) of source root location for other files that match the search pattern specified by the -m option. The -r option is specified by one of the following parameters:
true false
Examples
-e -c all -u sysadm -p syspwd -m "*" -f export.xml -l /Users/mccarthe -r true
9.2.3
Importing report results
Note: Report results don't contain any result data, they contain meta data about the location of the results file. These are stored locally on the application server where the request was initiated in a directory called WMCROOT/var/rg/spool/. To provide the data it is important for the user to externally manage the copying and pasting of the results files. The reason for this external handling of result data, is that the size of the results file can be large. The import operation imports report results from an import file or directory to a destination directory.
112
usage
report_impexp -i -c <r> -u <user_id> -p <password> -f <file|dir> [-l <server_directory>] -dup <failonerror|overwrite|ignore>
options The options and parameters to be used with the report_impexp tool for importing report results are described in the following table.
Table 38:
Option
-i -c <r>
Options for report_impexp - import report results

Description
Initiates the import process. Content or type of object to import. This option uses the following parameter:
r - report results
-u <user> -p <password> -f <file|dir>
The username of the user invoking the import tool. The users password. The file or directory to import. This option is specified by one of the following parameters:
file - the file to import. dir - the directory of files to import.
This must be a valid user folder location. For example:

/Users/sysadm /Users/peter/folder1 /Users/mary/backup/daily
If the -l option is not used then the location and associations are taken from the imported document(s).
-l <server_directory> -dup [failonerror|overwri te|ignore]
Destination on server that is the root location for imported documents. Import process behavior. Note: While this option must be set, it is not used on the server side. Because no relationship is maintained on the server side between report results and definitions, the server can load multiple copies. This option is specified with one of the following three parameters:
failonerror - fail when an existing report with the same name is
found
overwrite - overwrite when existing files with the same names are
found
ignore - ignore files that already exist
Examples
report_impexp -i -c results -u sysadm -p Syspwd -f /appl/virtuo/tmp/ exportResults.xml -l /Users/sysadm -dup ignore
Tools 113
9.2.4
Exporting report results
The export operation exports report results to an output file. usage

report_impexp -e -c <r> -u <user_id> -p <password> -m <pattern_match> -f <file> l <server_directory> [-r]
options The options and parameters to be used with the report_impexp tool for exporting report results are described in the following table.
Table 39:
Option
-e -c
Options for report_impexp tool - export report results

Description
Initiates the export process. Content or type of object to export. This option uses the following parameter:
r - report results
-u <user> -p <password> -m <pattern_match>
The username of the user invoking the export tool. The users password. Pattern matches for document names using standard wildcards. Quotes must be placed around the wildcards. For example, for all report results use "*". The file to export documents to. This option is specified the following parameter:
file - the file to export to.
-f <file>
-l <location> -r
Destination on server that is the root location for imported documents. Optional. Recursive search (sub-directories) of source root location for other files that match the search pattern specified by the -m option. The -r option is specified by one of the following parameters:
true false
Note: If the report results are not on the file system where the report_impexp tool is being used then the report result content will not appear in the exported dataset.
Examples
report_impexp -e -c results -u sysadm -p Syspwd -m 'Report_27*' -f exportResults.xml -l /Users/sysadm -r true
114
9.3
Time Zone Support for Reporting
The report scheduler offers users the option of running reports according to a different timezone than the one where the server is located. A number of timezone regions and Daylight Saving Time (DST) rules are already defined in the Tivoli Netcool Performance Manager for Wireless software. It is possible to define additional timezone regions and DST rules. The administrator can: Set up Daylight Saving Time (DST) rules Define timezone regions, and assign DST rules to them if required The following sections explain: About Daylight Saving Time Rules About Time Zone Regions
9.3.1
About Daylight Saving Time Rules
A DST rule defines the boundaries (starting and ending point) and the amount of DST savings, in minutes. A DST boundary is a date time reference. A single DST rule can be referenced by more than one timezone region. You can define several different types of rules. Usually the entries follow a day-of-the-week-in-month form, for example, "first Sunday in April." You can also define a rule by specifying any of the following forms: Exact day of the month The day of the week occurring on or after an exact day of the month The day of the week occurring on or before an exact day of the month The interface assigns numeric values to the days of the week. Sunday is defined as 1, Monday is defined as 2, and so on. The following table shows an example of a DST rule for Seattle. It defines daylight saving time as starting the first Sunday in April at 2:00 a.m., and ending the last Sunday in October at 2:00 a.m.
Table 40: Example of DST rule for the Seattle region
example
attribute
Starting
Month Day day of Week Time
April first Sunday 2:00 AM
Tools 115
Table 40:
Example of DST rule for the Seattle region

example
attribute
Ending
Month Day day of week Time
October last Sunday 2:00 AM 60 Minutes
Savings
Savings
DST Rule ID Each DST rule has an ID. When a new DST rule is created, the Tivoli Netcool Performance Manager for Wireless software automatically assigns a number to the rule, and displays it after the rule is created. The identifier is always an integer, and cannot be changed. You can list DST rules and their IDs, see List DST rules. Use the tz_admin script to manage rules for timezone regions. This script allows you to perform the following tasks: Create a DST rule List DST rules Delete a DST rule Create a DST rule To create a DST rule:
tz_admin -adddstr start <start_format> end <end_format> mins
where <start_format> and <end_format> can take any of the following forms: after MM dayofweek DD HH:mm before MM dayofweek DD HH:mm first MM dayofweek DD HH:mm last MM dayofweek DD HH:mm exact MMDD HH:mm and where:
Table 41:
attribute description
DST rule
after before first last
First (1=Sun, ...) on or after Last (1=Sun, ...)or before First (1=Sun, ...) Last (1=Sun, ...)
116
Table 41:
attribute description
DST rule
exact dayofweek D M H mm mins
Exact day, specify month (MM) and day (DD) For example, 0415 represents April 15. The numerical values for Sunday to Saturday (1 to 7) Day of the month DD Month, 01-12 Hours 00-24 Minutes 0-60 Minutes of DST time: 1 to 1440.
For example the DST for Europe/London is:

tz_admin -addstr start last 03 dayofweek 01 01:00 end last 10 dayofweek 01 01:00 mins 60
which translates as: start on the last Sunday in March at 01:00, end on the last Sunday in October at 01:00, with 60 minutes of DST. List DST rules To list a DST rule:
tz_admin -listdstr <dst_rule_id>
where:
Table 42:
Option
dst_rule_id
Options for listing a timezone region
Description
DST Rule ID
To list all DST rules:

tz_admin -listdstr all
Delete a DST rule To delete a DST rule:

tz_admin -deletedstr <dst_rule_id>
where:
Table 43:
Option
dst_rule_id
Description
DST Rule ID
Tools 117
9.3.2
About Time Zone Regions
A timezone region is different from a timezone. In the Mountain timezone of the United States, for example, the state of Arizona does not observe Daylight Saving Time, whereas the majority of the rest of the timezone does. The administrator defines timezone regions, which the user can then select when scheduling reports. The following are the default regions available at installation time; you can add others at any time: America/Anchorage America/Buenos Aires America/Caracas America/Chicago America/Denver America/Honolulu America/Indianapolis America/Lima Peru America/Mexico City America/New York America/Noronha America/Phoenix America/Puerto Rico America/San Francisco America/Santiago America/Sao Paulo America/Seattle Asia/Bangkok Asia/Calcutta Asia/Dubai Asia/Hong Kong Asia/Jerusalem Asia/Riyadh Asia/Tokyo Australia/Adelaide Australia/Brisbane Australia/Perth Australia/Sydney Europe/Athens Europe/Berlin
118
Europe/Brussels Europe/Helsinki Europe/London Europe/Madrid Europe/Moscow Europe/Paris Europe/Rome Europe/Vienna Europe/Warsaw Europe/Zurich Greenwich Mean Time Pacific/Auckland Use the tz_admin script to manage timezone regions. This script allows you to perform the following tasks: Create a timezone region List timezone regions Change the timezone region Delete a timezone region Assign a timezone region a DST rule Create a timezone region You can set the current time zone region for your computer as well as define new regions to fit your business needs. You create a timezone region by providing a name, GMT offset in minutes, and optionally assigning a DST rule to it. To create a timezone region:
tz_admin -addtzr <timezone_name> <gmt_offset> [<dst_rule_id>]
where:
Table 44:
Option
Options for creating a timezone region
Description
timezone_name Name of the timezone region (64 characters maximum) gmt_offset dst_rule_id
GMT offset in minutes (-720 to 720). Longitudes west of GMT are negative, and longitudes east of GMT are positive. DST Rule ID
Tools 119
List timezone regions To display the current timezone region:

tz_admin -listcurtzr
To list all timezone regions:

tz_admin -listtzr all
To list a specific timezone region:

tz_admin -listtzr <timezone_name>
where:
Table 45:
Option
timezone_name
Description
Name of the timezone region (64 characters maximum)
Change the timezone region You can change the current timezone region. Warning! Existing schedules that deliver reports based on timezone regions could be impacted when you change the region on a computer. The schedules are based on the number of hours difference between two computers and are not linked dynamically to a regions name. When you change a timezone region for a computer, the hour relationship will not change. To change the current timezone:
tz_admin -addcurtzr <timezone_name>
where:
Table 46:
Option
Description
timezone_name Name of the timezone region (64 characters maximum)
Delete a timezone region To delete a timezone region:

tz_admin -deletetzr <timezone_name>
where:
Table 47:
Option
Description
timezone_name Name of the timezone region (64 characters maximum)
120
Assign a timezone region a DST rule To assign a timezone region a DST rule:
tz_admin -linktzr <timezone_name> <dst_rule_id>
where:
Table 48:
Option
Description
timezone_name Name of the timezone region (64 characters maximum) dst_rule_id
DST Rule ID
Tools 121
9.4
Holiday Maintenance
Holidays are definable dates you can include in or exclude from reports. Including or excluding holidays can provide for more accurate data depending on the monitoring that is conducted. For example, a weekly report that monitors common traffic patterns can become skewed if it includes data from a holiday with abnormal traffic. Conversely, you might want to create a report that only includes data from holidays. The holiday_admin tools provides the means to list and alter the holiday definitions of NetworkAssure. This tool cannot be used off-line. It requires a virtuo administrative login. This tool is available on windows as holiday_admin.js. It can be invoked either directly from the command line or by choosing either the cscript or wscript command processor. Using holiday_admin you can: list holidays add holidays delete holidays Parameters for holiday_admin are as follows:
Table 49:
Option
-u -p -list -add <date>
Description
Administrators user name. Administrators password. Lists all holidays. Adds a holiday, the date is specified as MMDDYY. For example, 041506 represents April 15. You can add more then one date by separating each date with a space, for example 041506 041606 041506 represents April 15. You can remove more then one date by separating each date with a space, for example 041506 041606
-remove <date> Deletes a holiday, the date is specified as MMDDYY. For example,
9.4.1
List holidays
To list current holidays:

holiday_admin -u <admin_user> -p <admin_password> -list
where:
<admin_user>
is the administrators login ID is the administrators login password
<admin_password>
122
9.4.2
Add holidays
To add a holiday:
holiday_admin -u <admin_user> -p <admin_password> -add <date> <date>
where:
<admin_user>
<admin_password>
<date> is the date of the holiday to be added, specified as MMDDYYYY or MM/DD/YYYY. For example using the MMDDYYYY format, 04152006 represents April 15 2006. You can remove more then one date by separating each date with a space, for example 04152006 04162006
9.4.3
Delete holidays
To delete a holiday:
holiday_admin -u <admin_user> -p <admin_password> -remove <date> <date>
where:
<admin_user>
<admin_password>
<date> is the date of the holiday to be deleted, specified as MMDDYYYY or MM/DD/YYYY. For example using the MMDDYYYY format, 04152006 represents April 15 2006. You can remove more then one date by separating each date with a space, for example 04152006 04162006
Tools 123
9.5
Data Availability
The data_availability tool outputs the hourly or daily percentage data availability for a specific counter (KPI) in a table. The data_availability script is located in:
$WMCROOT/bin
9.5.1
Usage
data_availability_admin -type <type_name> -element <network_element> -day <date> counter <counter_name> -table_name <table_name> [-csv]
For example:
data-availability_admin -type hourly -element 1-1-1 -day 01/15/07 -counter TOTSESSSETUPBLK -table_name nor_rncis856perf_tab
Example output:
DO_RNC_ID 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 DAY 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 01/15/07 HOUR 0 1 2 3 4 5 6 7 8 9 10 11 Data Available (%) 100 100 100 100 100 100 100 100 100 100 50 100 TOTSESSSETUPBLK 9 3 1 0 2 0 5 13 16 39 32 20
................................................................... ...................................................................
The parameters must be presented in the following sequence -type -element -day -counter -table_name -csv [optional] If the parameters are not provided to the data_availability_admin script in this sequence then an error will be returned when the script is run.
124
Parameters for data_availability_admin are as follows:

Table 50:
Parameter
-type -element -day -counter
Parameters for Data Availability
Description
Calculate availability by hour or daily total period. The valid values for this parameter are hourly or daily. The network element to be verified. The element specified must be in the table or an error will be returned. The day for which the report is required, using one of the following formats: MM/DD/YYYY or MM/DD/YY Used to identify the technology, network element column name used for data availability calculation. If the counter does not exist in the table then an error will be returned. The name of the table used for data availability calculation. If the table does not exist then an error will be returned. This is an optional parameter, if its set then the script will output the report in comma delimited format. If the parameter is not set the script will output the report in normal format.
-table_name -csv
Tools 125
126
10
LCM Administration
The lcm_admin (Loader Configuration Manager Administration ) tool enables Datasources, Loader Configurations and NC Relations to be loaded from XML files into the administration database, and unloaded from the administration database to XML files. This tool also enables the addition, updating and deletion of Loader Datasources, Loader Configurations and NC Relations. This chapter covers the following: Overview List information for Datasources and Loader Configurations Load Datasources, Loader Configurations and NC Relations Unload Datasources, Loader Configurations and NC Relations Delete Datasources, Loader Configurations and NC Relations Load, merge, and unload data availability blocks from xml files
127
10.1
10.1.1
Overview
Loader Configuration
A Loader Configuration is a full set of information that describes how an individual loader is configured to run. It contains a Datasource ID to link it to a particular Datasource.
10.1.2
Loader Datasource
A Loader Datasource contains a set of mappings from input data to database tables. A Datasource is uniquely identified through its Datasource name, Datasource version, Technology Pack name and Technology Pack version.
10.1.3
NC Relations
Each NC Relations entry provides a relationship between the network configuration data used by a network element, with generated performance data. For example, a relations entry can show a relationship between an NC cell table which contains information on the location of a network element in the network, and a cell traffic table which is a performance table that contains performance data generated by the network element.
10.1.4
Data availability
If a technology pack is provided with Data Availability definitions, these definitions are contained in an .xml file. This file contains information about the technology pack, and a list of blocks of data that are loaded for that technology pack.
10.1.5
Usage
Usage for lcm_admin:

{ -h | -help | --help | -v | -version | --version } | { -listdatasources | -listloaderconfigs | -list } | { -load <xml_file> } | { -loadcustom <datasource_xml_file> } | { -merge <data_availability_xml_file> Adds data availability blocks to any already loaded. } | { -unload [<datasource_xml_unload_dump_file>] -datasource <datasource_name>
128
-dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version> [-type <Vendor | Neutral | Custom>] Type must be specified if using merged loadmaps -unload [<loaderconfig_xml_unload_dump_file>] -loaderconfig <loaderconfig_name> -unload [<relations_xml_unload_dump_file>] -relations [-nctable <nc_table>] [-sourcetable <source_table>] -unload [<dataavailability_xml_file>] -dataavailability -techpack <techpack_name> -tpversion <techpack_version> -unloadcustom [<datasource_xml_unloadcustom_dump_file>] -datasource <datasource_name> -dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version> [-type <Vendor | Neutral | Custom>] Type must be specified if using merged loadmaps } | { -delete <datasource_xml_file> | -datasource <datasource_name> -dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version> You cannot delete a datasource that is associated with a loader configuration. -delete <loaderconfig_xml_file> | -loaderconfig <loaderconfig_name> Deleting a loader configuration also deletes the datasource related to it. -delete <relations_xml_file> | -relations -nctable <nc_table> [-sourcetable <source_table>] If the nctable does not have a source table please pass -sourcetable followed by "*" } | { -reread -datasource <datasource_name> -dsversion <datasource_version> } NOTE: If a command is given with a name option, but the name parameter contains spaces, then double-quotes should be used, for example,
LCM Administration 129
lcm_admin -delete -datasource Nokia T13 -dsversion 2.0 -techpack GPRS CN -tpversion 1.0
The options for the lcm_admin script are described in Table 51.
Table 51:
Option
-listdatasources
lcm_admin options
Description
Lists a summary of all Datasources in the administration database. Lists a summary of all Loader Configurations in the administration database. Lists a summary of all Loader Configurations and all Datasources in the administration database. Loads a Loader Datasource into the administration database from an XML file <xml_file>. Load all files in the loadmaps dir. Load data availability blocks for a technology pack.
-listloaderconfigs
-list
-load <xml_file>
-loadcustom <datasource_xml_file>
Loads a custom Loader Datasource into the administration database from an XML file <datasource_xml_file>. Adds data availability blocks to any already loaded. Unloads a Datasource by specifying either an XML file, or the Datasources identifying parameters.
-merge <data_availability_xml_file>
-unload [<datasource_xml_file>]| -datasource <datasource_name> -dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version> -unload [<loaderconfig_xml_file>] -loaderconfig <loaderconfig_name>
Unloads a Loader Configuration by specifying either an XML file, or the Loader Configurations name. Unloads a data availability xml file by specifying an XML file, technology pack and technology pack version.
-unload [<dataavailability_xml_file>] -dataavailability -techpack <techpack_name> -tpversion <techpack_version>
130
Option
-unloadcustom [<datasource_xml_file>]| -datasource <datasource_name> -dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version> -delete <datasource_xml_file> -datasource <datasource_name> -dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version> -delete <loaderconfig_xml_file> -loaderconfig <loaderconfig_name>
Description
Unloads a custom Datasource by specifying either an XML file, or the Datasources identifying parameters.
Deletes a Datasource by specifying either an XML file, or the Datasources identifying parameters.
Deletes a Loader Configuration by specifying either an XML file, or the Loader Configurations name. Deletes NC Relations entry(s) by specifying either an XML file, or a combination of the NC Relations entry(s) NC table and source table. Rereads a Datasource.
-delete [<relations_xml_file>] -relations [-nctable <nc_table>] [-sourcetable <source_table>] -reread -datasource <datasource_name> dsversion <datasource_version>
10.2
10.2.1
Listing information for Datasources and Loader Configurations

Listing Loader Datasources
The -listdatasources option, displays a summary of all Loader Datasources in the database, in the following format:
Teckpack Name Ericsson GSM BSS Nokia GSM BSS Version 1.0 1.0 DataSource Name Ericsson BSS Nokia BSS Version R10 OSS3.1 ED3 Technology GSM GSM Vendor Ericsson Nokia -------------------------------------------------------------------------
The list is sorted in ascending alphabetical order by Technology Pack name, then by ascending Technology Pack version, then in ascending alphabetical order by Datasource name and ascending Datasource version. To list Datasources, as user virtuo:
lcm_admin -listdatasources
10.2.2
Listing Loader Configurations
The -listloaderconfigs option displays a summary of all Loader Configurations, in the following format:
DataSource Name DataSource Version Type Loader Configuration Name Ruleset Id
----------------------------------------------------------------------------------------Ericsson BSS Ericsson BSS Nokia BSS Nokia BSS R10 R10 OSS3.1 ED3 OSS3.1 ED3 Neutral Vendor Vendor Neutral Ericsson BSS Neutral R10 loader Ericsson BSS Neutral R10 loader Nokia BSS OSS3.1 ED3 loader Nokia BSS OSS3.1 ED3 loader 10000 10001 10002 10003
The list is sorted in ascending alphabetical order by Datasource name, then by ascending Datasource version, then in ascending alphabetical order by Loader Configuration name and ascending rulesetid. To list Loader Configurations, as user virtuo:
lcm_admin -listloaderconfigs
10.2.3
Listing Datasources and Loader Configurations
The -list option, displays a summary of all Loader Configurations and Datasources, in the following format:
Loader Configuration Information DataSource Name Ericsson IOG20 Nokia T13 DataSource Version V2.0 V1.0 Loader Configuration Name GSM Loader GPRS Loader RulesetId 1001 1002
-------------------------------------------------------------------------------
Data Source Information Techpack Name GPRS CN GSM Version 1.0 2.0 DataSource Name Nokia T13 Ericsson IOG20 Version 1.0 2.0
-------------------------------------------------------------------------------
The Datasource list is sorted in ascending alphabetical order by Technology Pack name, then by ascending Technology Pack version, then in ascending alphabetical order by Datasource name and ascending Datasource version. The Loader Configuration list is sorted in ascending alphabetical order by Datasource name, then by ascending Datasource version, then in ascending alphabetical order by Loader Configuration name and ascending rulesetid. To list Datasources and Loader Configurations, as user virtuo:
lcm_admin -list
10.3
10.3.1
Load Datasources, Loader Configurations, NC Relations and Data Availability

Loading a Datasource from XML
The -load option is used to create a new Datasource or update an existing Datasource from a specified Loader Datasource XML file.
132
If the Datasource specified in the XML file already exists, then this Datasource is updated with the configuration in the loaded XML file. If the Datasource does not exist an attempt is made to create a new Datasource in the database. To load a Datasource, as user virtuo:
lcm_admin -load <xml_file>
10.3.2
Loading a custom Datasource from XML
The -loadcustom option is used to create a new custom Datasource or update an existing custom Datasource from a specified Loader Datasource XML file. If the Datasource specified in the XML file already exists, then this Datasource is updated with the configuration in the loaded XML file. If the Datasource does not exist an attempt is made to create a new Datasource in the database. To load a custom Datasource, as user virtuo:
lcm_admin -loadcustom <datasource_xml_file>
10.3.3
Loading a Loader Configuration from XML
The -load option is used to create or update a Loader Configuration in the database from a specified Loader Configuration XML file. If the Loader Configuration specified in the XML file already exists, then this Loader Configuration is updated with the configuration in the loaded XML file. If the Loader Configuration does not exit then a new Loader Configuration is created. To load a Loader Configuration, as user virtuo:
lcm_admin -load <loaderconfig_xml_file>
10.3.4
Loading NC Relations from XML
The load option is used to create or update an NC Relations entry or set of NC Relations entries in the database from a specified NC Relations XML file. If the NC Relations specified in the XML file already exist, then this NC Relations entry(s) is updated with the configuration in the loaded XML file. If the NC Relations specified in the XML file do not exist then an attempt is made to create a new NC Relations entry(s) in the database. Note: If an attempt to load a new set of NC Relations is made, and any of these relations already exist in the database, then none of the NC Relations will be entered into the database. If an attempt is made to update a set of NC Relations entries in the database and any of the NC Relations entries do not exist in the database then none of the NC Relations entries are updated. To load NC Relations, as user virtuo:
lcm_admin -load <relations_xml_file>
10.3.5
Loading Data Availability from XML
The -load option is used to load data availability for a technology pack. If a technology pack is provided with Data Availability definitions, these definitions are contained in an .xml file. This file contains information about the technology pack, and a list of blocks of data that are loaded for that technology pack. If the value of the block is set to true, i.e. <block name="ATMUSAGE">true</block>, then after the file is loaded the loader will start producing Data Availability (DA) statistics every time it loads a block of ATMUSAGE data. Note: This file is supposed to be user-customized: blocks can be switched on or off by the user. It is important to realize that blocks which are tracked take approximately twice as long to load as blocks that are not. Only high-level entities (MSC, BSC, ...) should be tracked, but not low-level entities (TRX, ...). To load data availability for a technology pack:
lcm_admin -load <data_availability.xml>
For example:
lcm_admin -load dataavailability_umts_siemens_utran_umr050_1.0.0.0.xml
10.3.6
Merging of Data Availability blocks from XML
The -merge option is used to add data availability blocks to any already loaded. The -load option overwrites any previously loaded blocks and enables the loader to start producing DA statistics for the blocks in the file passed to it. The -merge option will add any blocks not already having DA statistics loaded to the list of existing blocks, to produce DA statistics. To load data availability for a technology pack:
lcm_admin -merge <data_availability_xml_file>
10.4
10.4.1
Unload Datasources, Loader Configurations and NC Relations

Unloading a Datasource to XML
The -unload option is used to save a Loader Datasource to an XML file in its original format so that it can be modified and saved back to the database using the -load command. All Datasource parameters must be specified (apart from the XML file name) to unload a Datasource, including Datasource name, Datasource version, the Technology Pack name and the Technology Pack version. To unload a Datasource, as user virtuo:
lcm_admin -unload [<datasource_xml_file>] -datasource <datasource_name> -dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version>
where: is the name of the file to be created. The file can be created with a relative or absolute file path. If a relative path is specified, it is relative to the current working
[<datasource_xml_file>]
directory. Any existing file using the same file name shall be overwritten. If the optional parameter [<datasource_xml_file>] is omitted then file naming will use a standard output.
10.4.2
Unloading a custom Datasource to XML
The -unloadcustom option is used to save a custom Loader Datasource to an XML file in its original format so that it can be modified and saved back to the database using the -loadcustom command. All Datasource parameters must be specified (apart from the XML file name) to unload a Datasource, including Datasource name, Datasource version, the Technology Pack name and the Technology Pack version. To unload a custom Datasource, as user virtuo:
lcm_admin -unloadcustom [<datasource_xml_file>] -datasource <datasource_name> dsversion <datasource_version> -techpack <techpack_name> -tpversion <techpack_version>
where:
[<datasource_xml_file>] is the name of the file to be created. The file can be created with a relative or absolute file path. If a relative path is specified, it is relative to the current working directory. Any existing file using the same file name shall be overwritten. If the optional parameter [<datasource_xml_file>] is omitted then file naming will use a standard output.
10.4.3
Unloading a Loader Configuration to XML
The -unload option is used to save a Loader Configuration to an XML file in its original format so that it can be modified and saved back to the database using the -load command. To unload a custom Loader Configuration, as user virtuo:
lcm_admin -unload [<loaderconfig_xml_file>] -loaderconfig <loaderconfig _name>
where:
[<loaderconfig_xml_file>] is the name of the file to be created. The file can be created with a relative or absolute file path. If a relative path is specified, it is relative to the current working directory. Any existing file using the same file name shall be overwritten. If the optional parameter [<loaderconfig_xml_file>] is omitted then file naming will use a standard output.
10.4.4
Unloading NC Relations to XML
The unload option is used to save an NC Relation entry(s) in its original format to an XML file so that it can be modified and saved back to the database using the load command. The [<relations_xml_file>] parameter is optional. It is used to specify the name of the file to be created. The file can be created with a relative or absolute file path. If a relative path is specified, it is relative to the current working directory. Any existing file using the same file name shall be overwritten. If the optional parameter [<relations_xml_file>] is omitted then file naming will use a standard output. A combination of NC table and Source table can be used to retrieve NC Relations entries.
If the sourcetable option is not specified:

lcm_admin -unload [<relations_xml_file>] -relations -nctable <nc_tablename>
then all NC relations entries in the lc_relations table with the specified NC table name will be unloaded. To unload any NC Relations entry for a specified NC table and Source table the following command is used:
lcm_admin -unload [<relations_xml_file>] -relations -nctable <nc_tablename> sourcetable <source_tablename>
To unload any NC Relations entry that has a specified NC table and a blank Source table the following command is used:
lcm_admin -unload [<relations_xml_file>] -relations -nctable <nc_tablename> sourcetable " "
10.4.5
Unloading Data Availability to XML
The -unload option is used to unload a data availability file for a technology pack, in its original format so that the file can be modified and saved back to the database using the -load command. All parameters must be specified to unload the file including the Technology Pack name and the Technology Pack version. To unload a data availability xml file, as user virtuo:
lcm_admin -unload [<dataavailability_xml_file>] -dataavailability -techpack <techpack_name> -tpversion <techpack_version>
where:
<dataavailability_xml_file> is the name of the file to be created. The file can be created with a relative or absolute file path. If a relative path is specified, it is relative to the current working directory. Any existing file using the same file name shall be overwritten. If the optional parameter [<dataavailability_xml_file>] is omitted then file naming will use a standard output.
10.5
Delete Datasources, Loader Configurations and NC Relations
The -delete option is used to delete a Datasource. You can not delete a Datasource that is associated with a Loader Configuration. A Datasource can be deleted using two methods: by specifying the Datasource name, Datasource version, Technology Pack name and Technology Pack version of the Datasource to be deleted. by specifying a Datasource XML file which will be parsed to obtain the Datasource name, Datasource version, Technology pack name and Technology Pack version of the Datasource to be deleted. To delete a Datasource by specifying Datasource parameters:
136
lcm_admin -delete -datasource <datasource_name> -dsversion <datasource_version> techpack <techpack_name> -tpversion <techpack_version>
To delete a Datasource by specifying a Datasource XML file:

lcm_admin -delete <datasource_xml_file>
10.5.1
Deleting a Loader Configuration
The -delete option is used to delete a Loader Configuration. The Datasource associated with that Loader Configuration is not deleted. A Loader Configuration can be deleted using two methods: by specifying the Loader Configuration name. by specifying a Loader Configuration XML file which will be parsed to obtain the Loader Configuration name. To delete a Loader Configuration by specifying the Loader Configuration name:
lcm_admin -delete -loaderconfig <loaderconfig_name>
To delete a Loader Configuration by specifying a Loader Configuration XML file:

lcm_admin -delete <loaderconfig_xml_file>
10.5.2
Deleting NC Relations
The -delete option is used to delete an NC Relations entry. An NC Relations entry can be deleted using two methods: by specifying a combination of the NC Relations NC table and Source table. by specifying an NC Relations XML file which will be parsed to obtain the NC Relations to be deleted. To delete any NC relations entry that has an NC table and a specified Source table the following command is used:
lcm_admin -delete -relations -nctable <nc_tablename> -sourcetable <source_tablename>
This will delete any NC Relations entry with the specified nctable and sourcetable combination. To delete any NC Relations entry that has an NC table and a blank Source table the following command is used:
lcm_admin -delete -relations -nctable <nc_tablename> -sourcetable " "
To delete a set of NC Relations entries by specifying an NC Relations XML file the following command is used:
lcm_admin -delete -relations <relations_xml_file>
This will attempt to delete all NC Relations entries from the database that are specified in the NC Relations XML file. If an NC Relations entry specified in the NC Relations XML file does not exist in
the database an error will be logged, and the lcm_admin tool will continue to delete the remaining NC Relations entries specified in the NC Relations XML file.
10.5.3
Re-reading a Datasource
The -reread option is used to force a loader to reread its configuration, to apply changes made to a loaders configuration. To reread a Datasource:
-reread -datasource <datasource_name> -dsversion <datasource_version>
138
11
SBH Administration
In Tivoli Netcool Performance Manager for Wireless, the Busy Hour feature provides a way of calculating the busiest hour of the day for a performance metric. It reflects the peak demands on the network, for that metric, for each day. The sbh_admin (Stored Busy Hour Administration) tool enables you to: Import SBH definitions Export SBH definitions or values List SBH definitions Execute SBH definitions Delete SBH definitions Turn on/off late data recalculation
11.1
11.1.1
Usage for Stored Busy Hour CLI

Import Stored Busy Hour definition(s)
-f -p -m Import the Stored Busy Hour Definition from <file>. Import all busy hour definitions stored in <directory>. All files with an .xml suffix will be imported. mode overwrite If the definition already exists, update it. ignore fail If the definition already exists, do not update it and do not fail the import. If the definition already exists, fail the import. sbh_admin -i (-f <file> | -p <directory>) -m (overwrite|ignore|fail)
Examples:
sbh_admin -i -f SBH1.xml -m overwrite
Import the Busy Hour defined in SBH1.xml, overwriting the definition if it already exists.
sbh_admin -i -p indir -m overwrite
If two files exist in indir (SBH1.xml SBH2.xml).The definitions in SBH1.xml and SBH2.xml will be imported.
139
11.1.2
Export Stored Busy Hour definition(s) or values
sbh_admin -e -n <name> -t (definition|value) (-f <file> | -p <directory>) -scope <scope> -start <startDate> -end <endDate> -n -t -f Specify the <name> of the Busy Hour to export. Wildcards are possible using the % character Export the definition or the value. Export the Stored Busy hour Definition(s) to <file>. Note, it is possible to export more than one definition to a single file. Export all busy hour definitions that match <name> to <directory>. The file names will be the name of the SBH. Export either daily, weekly or monthly values. Only applicable when exporting values Export values that were calculated between <startDate> and <endDate> Export values that were calculated between <startDate> and <endDate> The dates must be in the format dd/MM/yy If these options are omitted the latest values will be calculated.
-p -scope -start -end
Examples:
sbh_admin -e -n SBH1 -t definition -f SBH1.xml
Export the definition of SBH1 to the file SBH1.xml.

sbh_admin -e -n SBH% -t definition -p outdir
Export all definitions that match SBH% to the directory outdir. If two definitions exist (SBH1 SBH2), the files outdir/SBH1.xml and outdir/SBH2.xml will be created.
sbh_admin -e -n SBH1 -t value -f SBH1.xml -scope daily -start 12/02/07 -end 15/02/07
Export the daily values of SBH1 calculated between 12/2/07 and 15/02/7 to the file SBH1.xml
11.1.3
List SBH definitions

-n Specify the <name> of the Busy Hour to list. Wildcards are possible using the % character. If this option is omitted then all definitions will be listed. Print detailed information on the definition: If this option is omitted then only the name and enabled/disabled will be printed. Print the information to a <file>. If omitted the information will be printed to the screen.
sbh_admin -l (-n name) (-detail) (-f <file>)
-detail
-f
Example:
sbh_admin -l -n SBH1 -detail -f SBH1.xml
Print detailed information on SBH1 to the file SBH1.xml.
140
11.1.4
Execute SBH definition(s)

-n -f -start -end Specify the <name> of the Busy Hour(s) to execute. Wildcards are possible using the % character Print the results of the execution to <file>. If this option is omitted then the results will be printed to the screen Execute calculations between <startDate> and <endDate> Execute calculations between <startDate> and <endDate> The dates must be in the format dd/MM/yy If these options are omitted the latest values will be calculated.
sbh_admin -r -n <name> -f <file> -start <startDate> -end <endDate>
Example:
sbh_admin -r -n SBH1
Execute the Stored Busy Hour definition SBH1.
11.1.5
Delete SBH definition(s)

-n Specify the <name> of the Busy Hour(s) to delete. Wildcards are possible using the % character
sbh_admin -d -n <name>
Example:
sbh_admin -d -n SBH1
Delete the Stored Busy Hour definition SBH1.
11.1.6
Enable/Disable calculation of Late Data for all Busy Hour definitions

-ld Late data calculation may be enabled/disabled on a per Busy Hour basis by setting the calculate-late-data attribute. enable/disable: The calculate-late-data attribute in all definitions is ignored. individual: The calculation or not of late data is specified by the definition itself.
sbh_admin -ld <enable|disable|individual>
Example:
sbh_admin -ld enable
Enable the calculation of Late Data for all Busy Hour definitions. Note: The application server must be restarted in order for the changes made by using sbh_admin -ld <enable|disable|individual> to take effect.
SBH Administration 141
142
12
Alarm Administration
The alarm_admin tool enables Alarm Template xml files to be loaded into the database, unloaded to a file, updated or deleted. The Alarm Manager application requires that Alarm Templates be present in the database in order for alarm definitions to be created; alarm definitions are based on Alarm Templates. It is also possible to create Alarm Templates in the Alarm Manager application. Before an Alarm Template can be created, it must have a context. For more information on the Alarm Manager see the NetworkAssure User Guide and Online help. This chapter covers the following: Overview List an Alarm Template Load an Alarm Template Drop an Alarm Template Unload an Alarm Template Manage contexts
143
12.1
12.1.1
Overview
Document contexts
All Alarm Templates (and alarm definitions) are organized into a tree-like hierarchical structure consisting of document contexts. A context is a particular node in the tree, for example: +GSM LAYER +----- GSM ALARM TEMPLATE LAYER 1 +---------------------------- CONGESTION ALARMS All the elements shown above are nodes, the top-level node GSM Layer is referred to as the root node. The same document context tree is used to logically organize Alarm Templates and Alarm Definitions. Note: Before an Alarm Template can be created, it must have a context.
12.1.2
Alarm Template XML Documents
All Alarm Templates created are identified uniquely by a context name, an alarm name and a version ID. These fields are represented by xml tags in Alarm Template documents. The <AlarmContext> tag specifies the full context path which the document should be assigned to e.g. "GSM.GSM Layer 1". The <AlarmName> tag specifies the name of the alarm which corresponds to the X.733 Specific Problem field e.g. "btsCongestion". The <VersionID> tag specifies the numerical version of the Alarm Template xml document, for example "1.0", "1.1", "1.2" and so on. All Alarm Template xml documents loaded into the database must conform to the Alarm Template DTD.
12.1.3
Version Numbering
Alarm Template xml documents must contain a version number that must contain a fractional part represented as a whole number. For example, 1.0, 2.0 and 3.0 are all valid version numbers whereas 1.1 is not. This is to keep the versioning scheme in line with Alarm Definitions which use the same version numbering system.
12.1.4
Usage
Usage for alarm_admin:
144
{ -h | -help | --help | } | { -load <alarm_template_xml_file> | -drop -context <context> -name <name> -version <version> | -unload -context <context> -name <name> -version <version> -file <file> | -list | -createcontext <document_context_path> | -removecontext <document_context_path> [-r]
} The options for the alarm_admin script are described in Table 52.
Table 52:
Option
-list -load <alarm_template_xml_file>
alarm_admin options
Description
Shows a summary of all loaded Alarm Templates. Relative or absolute file path and name of the Alarm Template xml file to load. If a relative path is given, it must be relative to the current working directory. Requires the context, template name and version. Requires the context, template name, version and file. Must be a one or more path element names separated by "." e.g. "IP Layer.IP Layer 1". Must be a one or more path element names separated by "." e.g. "IP Layer.IP Layer 1".
-drop -context <context> -name <name> -version <version> -unload -context <context> name <name> -version <version> -file <file> -createcontext <document_context_path> -removecontext <document_context_path> [-r]
12.2
Manage Document Contexts
The -createcontext option is used to create a new document context path where each node in the given path will be created as necessary. The -removecontext option is used to remove either a single node of a context path, or the context path node and all its child nodes recursively (using the optional -r qualifier). Because document contexts are created automatically as needed when loading Alarm Templates into the database, this option should not be needed very often. However, document contexts may need to be set up to provide a particular tree structure, even though some nodes in the tree may not yet contain Alarm Templates.
Alarm Administration 145
12.2.1
Creating a Document Context
The -createcontext option, creates all nodes in the document context path specified. For example:
metrica_alarmtemplateadmin.ksh -createcontext One.Two.Three
Creates the nodes: One One.Two One.Two.Three Nodes are created on an as required basis, so that any nodes in the context path that currently exist are effectively ignored.
12.2.2
Removing a Document Context
The -removecontext option, removes one or more context nodes in the given context path. This function may be needed for maintenance when certain context paths are not referred to by any Alarm Templates and are therefore no longer needed. Removing a Single Context Node It is not possible to remove a context node that has children, so for a given context path only a childless node can be removed. For example, given that the context path One.Two.Three.Four.Five:
alarm_admin -removecontext One.Two.Three.Four.Five
will remove the last node (Five). Removing a Context Subtree To remove a complete context subtree for a given context path, you use the -removecontext option together with the -r flag. This will remove the node represented by the given context path and all of its children, its children's children and so on recursively down the context tree. For example:
alarm_admin -removecontext -r Two.Three.Four.Five
will remove the nodes: Two.Three.Four.Five Two.Three.Four Two.Three Two resulting in only node remaining: One
It is not possible to remove the specified document context path when there are Alarm Templates or Alarm Definitions that are stored under that context node or any of its children. This is true when removing a single context and also a complete context subtree. In the latter case the specified context cannot be removed if it, or any of its child context nodes, contains any Alarm Templates. Note: Alarm Definitions are organized in the same document context hierarchy as Alarm Templates.
12.3
List Alarm Templates
The -list option displays a list of all Alarm Templates in the database. To list all Alarm Templates:
alarm_admin -list
The following is a -list output example:

Alarm Template Summary [IP Tech Layer.IP Tech Layer 1.Congestion Alarms.btsCongestion] Version 3.0 Version 2.0 Version 1.0 [IP Tech Layer.IP Tech Layer 1.Dropped Call Alarms.tchAvailability] Version 1.0 Version 1.1
12.4
Load an Alarm Template
The -load option loads the specified xml file to create a new version of an Alarm Template or to update an existing Alarm Template. If the template specified in the xml file (identified by Context Name, Alarm Name and Version ID) already exists, it is replaced. Otherwise a new template entry is created. The following actions are performed when using this option: 1. The specified file is searched for according to the relative or absolute file path specified. If a relative path is specified, it is relative to the current working directory. If the file does not exist an error is displayed and the program will exit. 2. If a DTD document is specified in the XML file (with the statement <!DOCTYPE AlarmTemplate SYSTEM "<path>/AlarmTemplate.dtd">), the xml file is loaded and parsed and validated against the DTD. If all steps have completed successfully the xml document is ready to be loaded into the database. 3. The Alarm Template document is created (if it does not already exist) or updated. To load an Alarm Template:
alarm_admin -load <alarm_template_xml_file>
148
12.5
Drop an Alarm Template
The -drop option drops an Alarm Template. The Alarm Template to be dropped is specified by Alarm ID, Version ID and document context. The dropped Alarm Template is removed from the database. To drop an Alarm Template:
alarm_admin -drop -context <context> -name <name> -version <version>
12.6
Unload an Alarm Template to a File
The -unload option is used to copy an xml definition of an Alarm Template to a file. The Alarm Template to be copied is specified by Alarm ID, Version ID and document context. Any existing file data is overwritten. To unload an Alarm Template:
alarm_admin -unload -context <context> -name <name> -version <version> -file <file>
150
13
The Summarizer and Summary Administration
The Summarizer is a component of Tivoli Netcool Performance Manager for Wireless. Within Tivoli Netcool Performance Manager for Wireless, certain graphs and reports are used over and over again, and many of these will be based on whole days, weeks or even a month's worth of data. Traffic data aggregated over predefined time intervals (day, week, month) is stored for later use in reports as normal counters or KPIs. The data for this subset of reports and graphs is called summary data and the process of collecting this data is called summarization. The summarization process is run once a day. The summary_admin tool is used for creating, deleting, running, and exporting summary definitions, as well as setting the number of summary engine instances that can run concurrently. This chapter describes the following: The Summarizer Switching on and off the summary process Summary log file Start day of week Summarizing old loaded data summary_admin tool create a summary using parameters create a summary using an .xml file deleting a summary definition running a provisioned summary changing the number of instances exporting summary metadata listing summary definitions
151
13.1
Summarizer
Tivoli Netcool Performance Manager for Wireless supports the following functionality for the Summarizer and the summarization process: Processing of summaries can be switched on and off. If summaries are switched on they will run if they are switched off they will not run. A Summary log file is written to the appserver log file directory in $WMCROOT/logs/as/ default. This is a log for summaries ran via the scheduler. The start day of the week can be set. The start day of the week can vary depending on the geographical location. The summary process allows you to set the start day of the week to the day the user requires. The summarizer will summarize old loaded data automatically. When the summarizer process is started it detects whether old loaded data is loaded into the system. Data is defined as old loaded data if it is older than 1 day. If the old loaded data has already being summarized then it will be re-summarized and the old summary data is deleted and the new summary data is populated in the summary table. If the old loaded data is older than 1 week or 1 month it will cause weekly and monthly summaries to be re-calculated respectively.
13.1.1
Switching ON/OFF the summary process
Switching ON/OFF the summaries is done by setting a value in the wm_system_values_v view. The agent_admin tool runs the summary process but the summary process detects wether it is to process summaries or exit. See Agent Maintenance on page 56, for information on the agent_admin tool. Processing of summaries can be switched ON/OFF by setting the ProcessSummary value in the wm_system_values_v view to either true or false. To view what the ProcessSummary value is set to, logon to sqlplus, and run the following sql statement.
SELECT * FROM wm_system_values_v WHERE name = 'ProcessSummary';
If the value is set to true, summaries will be run, if set to false summaries will not be run. To change the value for ProcessSummary run the following SQL statement.
UPDATE wm_system_values_v set value = 'TRUE' WHERE name = 'ProcessSummary'; Commit;
13.1.2
Summary Log file
A Summary log file is written to the appserver log file directory in $WMCROOT/logs/as/ default. This is a log for summaries ran via the scheduler, the name of the log file is assummary.log.
152
Note: The log file for summaries ran via the summary_admin CLI tool is located in: $WMCROOT/logs/ summariser/summariser-server.log. The information contained in the log file depends on the DEBUG level set for the application. Information can include: Details on whether the summary process is switched on or off. The start time for the summary process. Details on summaries that have run in the past including how many rows were processed by the summary. The end time for the summary process. Below is an example of information contained in the as-summary.log file
10:09:17,431 INFO switched on. [summary.NewDataHandler] (Thread-123) Summary execution is
10:09:17,529 INFO [summary.NewDataHandler] (Thread-123) Summary engine execution has started at Thu Feb 15 10:09:17 GMT 2007 10:09:29,436 INFO [summary.SummaryQueryBuilder] (Thread-123) 0 rows were stored in table VNL_CELL_SDCCH_DSM for dates between Tue Feb 13 00:00:00 GMT 2007 and Wed Feb 14 23:59:59 GMT 2007 10:09:37,595 INFO [summary.SummaryQueryBuilder] (Thread-123) 100 rows were stored in table VNL_CELL_HO_CAUSE_DSM for dates between Tue Feb 13 00:00:00 GMT 2007 and Wed Feb 14 23:59:59 GMT 2007 10:10:11,326 INFO [summary.SummaryQueryBuilder] (Thread-123) 200 rows were stored in table VNL_CELL_HANDVR_RSLT_DSM for dates between Tue Feb 13 00:00:00 GMT 2007 and Wed etc .. 10:32:28,194 INFO [summary.NewDataHandler] (Thread-39) Summary engine execution has completed at Thu Feb 13 11:32:28 GMT 2007
Information for summaries can also be found in the summary_history table:

describe summary_history; Name Null Type ------------------------------ ----------------------------------------------------------------------SUMMARY_HISTORY_ID SUMMARY_ID SUMMARY_INTERVAL FIRST_AVAIL NOT NULL NOT NULL NUMBER NUMBER CHAR(1) DATE
The Summarizer and Summary Administration 153
LAST_AVAIL LAST_RUN_START LAST_RUN_END LAST_RUN_RESULT LAST_RUN_TEXT LAST_SUCCESSFUL_RUN
DATE DATE DATE NUMBER(6) VARCHAR2(200) DATE
13.1.3
Start day of week
The start day of the week can vary depending on where in the world you are located, the summary process allows you to set what day of the week the user wants to use as the start of the week. To view what the start day of the week is set to logon to sqlplus and run the following SQL statement:
SELECT * FROM wm_system_values_v WHERE name = 'StartOfWeek';
The following list details what value determines what day of the week. SUNDAY MONDAY TUESDAY THURSDAY FRIDAY SATURDAY 7 1 2 4 5 6
WEDNESDAY 3
The start of the week should be set when the system is installed and should not be altered afterwards, to set the value for StartOfWeek issue the following command via SQLPLUS ,
UPDATE wm_system_values_v SET value = COMMIT; '1' WHERE name = 'StartOfWeek';
13.1.4
Summary grace period
The summary service is normally scheduled to run every night, so when the day has finished (rolled over) the service will wait a certain amount of time (the 'grace period') before running all the summaries. This is to give the system time to collect all the necessary data from its data feeds. For example, if the summary service is scheduled to run a midnight (00:00), it would actually run at 02:00, if the grace is set to 2. This value can be found in:
/appl/virtuo/conf/summaryservice/default.properties
and can be changed by setting the attribute:

com.vallent.pm.summaryservice.core.engine.
The default is 2. The values supported are 0 to 23.

13.1.5
Summarizing Old Loaded Data
The summarizer will re-summarize or summarize old loaded data automatically. When the summarizer process is started it detects if old loaded data is loaded onto the system. Data is determined to be old loaded data if it's older than 1 day old. If the old loaded data has already being summarized then it will be re-summarized and the old summary data is deleted and the new summary data is populated in the summary table. If the old loaded data is older than 1 week or 1 month it will cause weekly and monthly summaries to be re-calculated respectively.
13.2
summary_admin CLI
The summary_admin CLI tool is a ksh shell script which resides in the $WMCROOT/bin directory, and which is used primarily to run one-off summaries. This tool is used for creating, listing provisioned, deleting, running, and exporting summary definitions, as well as setting the number of summary engine instances that can run concurrently.
13.2.1
Provisioning a summary
The create options allow the user to create a summary definition in one of two ways: using parameters using an xml file Only simple summary definitions can be created using the parameters option, whereas both simple and complex definitions can be created using the xml option. Note: Both options are mutually exclusive.
Creating a summary using parameters

Usage: summary_admin -c -source <source_table> ( [-ir] [-sir] [-fr] [-ts] [-ignoreaggr <yes|no>] ) -c source <source_table_name> Mandatory switch used to create a summary. Mandatory source table upon which the summary is based.
[-ir] <daily|weekly|monthly>Optional interval of summary to create: daily, weekly, or monthly. If none are specified then all three are created. [-sir] <daily|raw> [-fr] < DD-MM-YYYY> [-ts] <tablespace name> [-ignoreaggr <yes|no>] Optional interval of existing source summary table Optional date the summary is to run from. Optional existing tablespace in which the summary will be created. Ignore the average of average check.
Note: The ir option is used to identify the type of summary to create, while the sir option is used to identify the type of summary that will be used as a source for the summary creation. By default, the source (-sir) is raw performance tables.
Note: The sir option is to be used in cases where the user wants to create a summary based on an existing summary, i.e. create a weekly or monthly summary based on a daily summary. The sir and ir options are used in conjunction.
Note: The use of the ir option does not require the use of the sir option, as this option defaults to raw.
Note: It is not permissible to create a monthly summary based on a weekly summary.
Creating a summary using an xml file

Usage: summary_admin -c f <filename> [-ignoreaggr <yes|no>] -c -f <filename> Mandatory switch used to create a summary. Mandatory filename of the xml file used to provision the summary path included.
[-ignoreaggr <yes|no>] Ignore the average of average check.
Note: The following is an example of how to provision a summary using an xml file:
summary_admin c f /appl/virtuo/import/filename.xml
Note: By default summary definition provisioning during technology pack installation is switched off. If summary definition provisioning during technology pack installation is required then the following property must be set to true:
vallent.vmm.techpack.provision.summaries
This property is found in:

/appl/virtuo/conf/vmm/default.properties
See the Tivoli Netcool Performance Manager for Wireless Installation Guide for information on technology pack installation and provisioning summary definitions.
156
13.2.2
Deleting a summary definition

-delete <summary_name> Mandatory name of the summary to delete.
Usage: summary_admin delete <summary_name> [-ir] [-ir <daily|weekly|monthly>]Optional interval of the summary to delete. If none are specified then all three are deleted.
Note: If the optional interval switch is omitted, then all three summaries (daily, weekly, monthly) will be deleted from the system.
13.2.3
Running a provisioned summary

-r <summary_name> [-ir] <daily|weekly|monthly> [-er] <end date DD-MM-YYYY> Mandatory switch used to run a summary. Summary name must be provided The interval of the summary. The end date the summary will run to.
Usage: summary_admin -r <summary_name> [-ir] [-fr] [-er]
[-fr] <start date DD-MM-YYYY> The start date the summary will run from.
Note: If the user omits the optional start and end dates then the default response of the summary service is:
summary_admin r nok_trx_rx_quality ir daily
The summary engine will execute the most recently rolled over day, i.e. yesterday
summary_admin r nok_trx_rx_quality ir weekly
The summary engine will execute the most recently rolled over week, i.e. last week
summary_admin r nok_trx_rx_quality ir monthly
The summary engine will execute the most recently rolled over month, i.e. last month
Note: If the user omits the optional interval switch (-ir) and the start (-fr) and end dates (-er), then the default response of the summary service is to execute the daily, weekly, and monthly summaries of the specified summary. The time periods used in this scenario are the ones described in the note above.
Note: If the user wants to run a particular summary for a particular time period then all switch options must be used: interval, start date, and end date. However, if the user wants to run the daily, weekly, and monthly summaries for a particular summary definition they can omit the ir (interval required) option, and specify the start (-fr) and end (-er) dates. If the fr option is used, the er option must also be used. You can not use one without the other.
Note: If the user chooses to run a weekly summary and inadvertently chooses start and end dates that span two weeks, e.g. assuming todays date as 10-Sept-07 and fr = 9-AUG-07 er = 16-AUG-07, the default action of the summary service will be to run two summaries, one for the full week containing the start date (5-AUG-07 to 11-AUG-07), and another for the full week containing the end date (12-AUG07 to 18-AUG-07). The same would apply for the monthly option.
Note: A summary will run even if the data set is incomplete. That is, if todays date is 23-Aug-07 and the start of the week is Sunday the 19-Aug-07, and the user runs:
summary_admin r ir weekly fr 19-08-2007 er 23-08-2007
then the summary will still run even though the week has not rolled over and the data set is incomplete for the week. A date cannot in the future cannot be specified, and will return an error.
13.2.4
Changing the number of instances

-set -n -v Mandatory switch used to set summary parameters. The name of the parameter, e.g. noin (number of summary instances) The value of the parameter.
Usage: summary_admin set n v
To change the number of summary engine instances that can run concurrently use:
summary_admin set n noin v 3
13.2.5
Exporting summary metadata

-e [<summary_name>] Mandatory export switch. If no summary name is specified then all summaries are exported. Optional temporal type. Mandatory xml filename into which the meta data is exported.
Usage: summary_admin -e [ summary_name | -t | -ir ] -f <filename>
-t <user|standard|techpack> Optional creational type. -ir <daily|weekly|monthly> -f <filename>
Note: For example: To export all the nok_trx_rx_quality metadata i.e. daily, weekly, monthly:
summary_admin e nok_trx_rx_quality f /appl/virtuo/export/nok_trx_rx_quality.xml
Note: To export the metadata of all daily provisioned summaries:

summary_admin e -ir daily f /appl/virtuo/export/daily_summaries.xml
The summary definition xml contains the xml for daily, weekly, and monthly summaries. When exporting 'daily' alone, the daily xml data is not extracted from the summary definition xml, the whole xml is
exported. In this way, the daily part of the export command relates to the summary history. The example above would export all the provisioned summaries and would include summary history information related to daily summaries.
Note: To export the metadata of all provisioned summaries:

summary_admin e f /appl/virtuo/export/all_summaries.xml
To export the metadata of all standard provisioned summaries:

summary_admin e t standard -f /appl/virtuo/export/all_summaries.xml
Note: If the summary name is specified after the e option, then the user cannot use either the t or ir option. The following is not valid:
summary_admin -e vnl_cell_tch -ir daily -f /tmp/vnl_cell_tch_export.xml
or
summary_admin -e vnl_cell_tch t standard -f /tmp/vnl_cell_tch_export.xml
Note: If summaries are provisioned during technology pack installation they can be exported them using the creational type techpack.
13.2.6
-l
Listing summary definitions

List all the summary definitions, their run history and status, provisioned by the system. List the specified summary definition, its run history and status.
Usage: summary_admin l [summary_name]
-l <summary_name>
160
14
14.1
14.1.1
-a -e
Technology pack administration tools

The techpack_admin tool
The techpack_admin tool applies standard technology packs to a Tivoli Netcool Performance Manager for Wireless system. This tool is found in $WMCROOT/bin.
Usage
apply new technology pack modules dependencies -d <DirName> -n <TechPackName> export UDCs and reports that are dependent on a technology pack the directory where the files will be exported to the name of the technology pack in "" quotes the directory where the technology pack files to be patched are the name of the technology pack to be patched in "" quotes the version of the technology pack to be patched
Usage: techpack_admin -parameters
-p
patch an already installed technology pack -d <DirName> -n <TechPackName> -v <Version>
-l
list technology pack modules installed uninstalled audit [-n TechPackName] optional, the name of the technology pack in "" quotes for use with audit
-u
uninstall a named technology pack module or a named loader techpack -n <TechPackName> loader -L <Loadername> the name of the Loader configuration you wish to remove in "" quotes. Can be found by running by running: the name of the technology pack in "" quotes
lcm_admin -listloaderconfigs -S <SAPLoadername> the name of the loader as it appears in SAP in "" quotes. Can be found by running: sap disp When Trying to remove a loader that has multiple instances configured the original sap name as created when the techpack was applied should be passed as the -S option. Any files manually created by the user to
161
support multiple loaders must be manually deleted by the user. -h help
Note: Before running the techpack_admin tool ensure that the as process is running by executing the command sap disp as The as process should be at a status of STARTED If it is not started execute sap
start as
14.2
Applying a technology pack
The -a option applies technology pack modules to a Tivoli Netcool Performance Manager for Wireless system. The technology pack modules to apply are read from the $WCMROOT/admin/techpacks/ new_techpacks file. The new_techpacks file is created automatically by the installation of technology pack modules on the Tivoli Netcool Performance Manager for Wireless system. Technology pack modules are installed in
$WMCROOT/admin/techpacks
This file lists each technology pack and version of a technology pack to be applied. An example of a new_techpacks file is: Neutral_GSM_BSS_NSS_GOM 1.0 Neutral_GSM_Core 1.0 Ericsson_GSM_BSS_R10 1.0 The technology packs are applied in the order in which they appear in the new_techpacks file. If all technology packs are applied successfully the new_techpacks file will be deleted. If the application of any technology pack fails the techpack_admin tool will cease application of any further technology packs and will rollback the DML application of any previous technology packs that have been successfully applied.
14.3
Exporting lists of dependencies
The -e option is used to export lists in .csv format of all UDCs, reports and report templates that are dependent on a technology pack. This information is useful when uninstalling a technology pack. For example:
techpack_admin -e dependencies -d <DirName> -n "Nokia GSM BSS NetAct OSS3.1 ED3"
where <DirName> is the directory to write the .csv files to. In this example, all dependent UDCs, reports and report templates, will be listed in the files Nokia_GSM_BSS_udcs.csv and Nokia_GSM_BSS_reports.csv in the directory specified in the -d option.
14.4
Patching a technology pack
The -p option is used to apply a patch to an existing technology pack. For example:
techpack_admin -p -d <DirName> -n <TechPackName> -v <Version>
where:
<DirName> is the root directory under which the technology pack patches are located. For example using $WMCROOT/admin/techpacks/<techpack_dir> applies the patch from the directory $WMCROOT/admin/techpacks/<techpack_dir>/<version>/patches/metalayer. <TechPackName> <Version>
is the name of the technology pack to be patched in quotes.
is the version number of the technology pack to be patched.
techpack_admin -p -d $WMCROOT/admin/techpacks/Nokia GSM BSS -n "Nokia GSM BSS NetAct OSS" -v 3.1
14.5
Listing technology pack modules

installed - provides a list of technology packs applied to the system, UDCs, and all data related to the applied technology packs. uninstalled
The -l option lists the technology pack modules which are:
- provides a list of technology packs that have been uninstalled from the system.
- returns an audit log with information on a technology pack including information on any customizations and entities that were customized. Technology pack name is optional and must be in quotes.
audit [-n TechPackName]
For example:
techpack_admin -audit -n "Nokia GSM BSS NetAct OSS3.1 ED3"
14.6
14.6.1
Uninstalling a technology pack, and loaders

Standard technology pack
a technology pack. Technology pack modules are installed in $WMCROOT/
The -u option uninstalls admin/techpacks.
To uninstall a technology pack as user virtuo, execute the following command: 1. List the technology packs that are installed on the system:
techpack_admin -l installed
Make sure the technology pack you are going to uninstall has no dependencies. All dependent technology packs must be uninstalled beforehand. See Dependent technology packs on page 164, for information on dependent technology packs. 2. Uninstall the technology pack:
Technology pack administration tools 163
techpack_admin -u -n <TechPackName>
For example:
techpack_admin -u -n "Ericsson UMTS UTRAN R3.0"
3. You will be asked to confirm the uninstallation. The uninstall may take several minutes, do not interrupt the uninstall.
14.6.2
Loader configurations
To uninstall loaders for a technology pack: 1. Execute the following command:

techpack_admin -u loader -L <Loadername>
or:
techpack_admin -u loader -L <Loadername> -S <SAPLoadername>
where:
<Loadername>
is the name of the loader is the name of the loader in SAP
<SAPLoadername>
14.6.3
Dependent technology packs
A number of technology packs define top-level concepts that are not specific to any equipment vendor implementation. For example, concepts like 'Wireless CELL' or 'Access Point'. These technology packs are GOM (Global object model) technology packs, and they are used by other dependent technology packs. You cannot delete a technology pack used by another technology pack. You can use the techpack_admin -l installed command to display dependencies between technology packs. The following example output illustrates this:
[moduleInventory] TechPack: [moduleInventory] Module: [moduleInventory] Release: [moduleInventory] Technology: [moduleInventory] Subsystem: [moduleInventory] Vendor: [moduleInventory] Installed: [moduleInventory] Requires: [moduleInventory] [moduleInventory] [moduleInventory] [moduleInventory] UMTS (1.0.20) Ericsson UMTS UTRAN R3.0 (1.0) UMTS RAN Ericsson (ERI) 6 Mar 2007 16:57:41 Neutral GSM BSS/NSS GOM (1.0) Neutral GPRS BSS GOM (1.0) Neutral UMTS UTRAN GOM (1.0) Neutral GPRS/UMTS CN GOM (1.0) Neutral Core GOM (1.0)
In the example above you cannot uninstall Neutral GSM BSS/NSS GOM without first uninstalling Ericsson UMTS UTRAN R3.0.
164
14.7
Displaying help
The -h option displays the usage of the tool.
14.8
The techpack_custom tool
The techpack_custom tool is used to apply a customized technology pack.
14.8.1
Usage
Usage: techpack_custom -parameters -a apply new technology pack modules -s sign new technology pack modules -f <FileName> the full path of the file to be signed -h help
14.8.2
Option -a
The -a option installs a customized technology pack to a Tivoli Netcool Performance Manager for Wireless system. Note: If the techpack being customized is already installed, then it needs to be first uninstalled. Using techpack_admin -u -n <techpackname>. To install a customized technology pack:
teckpack_custom -a
14.8.3
Option -s
The -s option is used to "sign" the customized technology pack. To sign a customized technology pack:
techpack_custom -s -f <filename>
Technology pack administration tools 165
166
Appendix A :Problem Resolution and Errors

A.1
A.1.1
Tivoli Netcool Performance Manager for Wireless Problem Resolution

Potential Shared Memory Errors
Scenario 1: Problem - Failed to Attach to Network Configuration shared_memory Block The loader log file may display the following error:
Failed to attach to network configuration shared_memory block."
This error may occur for the following reason: When a loader starts, it creates a shared memory segment for Network Configuration data. If data is available in the input source directory, it starts to load. If a second loader subsequently starts against the same database and therefore the same shared memory segment, it is possible that it will calculate a different size for the segment i.e. if new/modified Network Configuration data has been loaded by the first loader. If the second loader calculates a different segment size, it can not attach to the existing Network Configuration shared memory segment. It fails to attach and gives the error above.
Scenario 1: Resolution - Failed to Attach to Network Configuration shared_memory Block Complete the following as user virtuo: 1. Run one loader by executing the command:
2. Get the shared memory size by checking the size of the TFP_SHM_MIN_SIZE environment variable in the $WMCROOT/conf/loader/default.properties file. 3. Stop the loader by executing the command:
4. Set the TFP_SHM_MIN_SIZE environment variable in the $WMCROOT/conf/loader/ default.properties file in bytes to a value greater than the required segment size. 5. Restart all the loaders by executing the following command for each loader process:
167
Scenario 2: Problem - Failed to Attach to Network Configuration shared_memory Block This error may occur for the following reasons: Multiple rulesets are configured, some with alarms on and some with alarms off. The user needs to simultaneously run one loader using a ruleset with alarms off, and one loader using a ruleset with alarms on against the same database. The user starts off a loader using the alarms off ruleset first and then a loader using the alarms on ruleset. The error occurs when the second loader is initiated. Scenario 2: Resolution - Failed to Attach to Network Configuration shared_memory Block Always start the loader using the alarms on ruleset first
A.1.2
Running Multiple Performance Manager Instances on the Same Server
If there are multiple Performance Manager instances on the same server then the names used for each performance database should be different, otherwise each loader will try to attach to the same shared memory setting.
A.1.3
Problem
Duplicate lc_relations Entries
Because there is no unique index on the lc_relations table, it is possible to create duplicate entries in this table. If this reoccurs on an ongoing basis, the number of records in this table can grow exponentially. This in turn can result in slow loader startup. Resolution This can be avoided by deleting the duplicate entries from the table. The following query can be used to identify duplicate entries:
select source_tabname, nc_tabname, access_key, master_tabname, count(*) from lc_relations group by source_tabname, nc_tabname, access_key, master_tabname having count(*) > 1
A.1.4
Alarm Stability Evaluation
If a KPI is oscillating between two thresholds, for example, warning and critical, no alarm gets raised if the stability period is greater that one reporting period. For Example:
Stability % = 75 % Stability Time = 60 mins. (4 * 15min. Lifs) Input source file 1 evaluates alarm to Warning state. Input source file 2 evaluates alarm to Minor state.
168
Input source file 3 evaluates alarm to Critical state. Input source file 4 evaluates alarm to Warning state.
The current loader functionality is that the alarm has not been stable for the required percentage (75%) during the stability time (60 minutes). The alarm warning state evaluates to 50 % stability during the 60 minute period so no alarm is raised. The alarm is not stable for the required percentage of time. In fact, an alarm should be raised at major level since the warning predicate evaluates to true during the entire stability period i.e. the alarm state should change to the lowest level that has persisted for the stability period. The alarm state has been at least warning for the required stability percentage during the 60 minute period.
A.1.5
Problem
Thread pool exhausted
Thread pool exhausted, consider increasing jacorb.poa.thread_pool_max. This problem may be encountered if the alarm service thread pool gets exhausted when many loaders simultaneously generate alarms. Solution Increase the jacorb.poa.thread_pool_max propertys value. The default value is 8. The property is found in the following properties file:
/appl/virtuo/conf/corba/jacorb-default.properties
A higher value needs to be specified if this error is encountered. As an approximation the value should equal the number of loaders used to generate alarms, plus 2.
A.2
A.2.1
Errors
Install Errors
SQLFatalErrorException: ORA-28000: the account is locked

cfgtoollogs/emca/vtdb/
This error is expected to appear in log files under /appl/oracle/product/10.2.0/db_1/ during application setup and can be safely ignored.
Problem Resolution and Errors 169
170
Appendix B: Notices and Trademarks

B.1 Notices
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication.
171
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 5300 Cork Airport Business Park Kinsale Road Cork, Ireland. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
172
B.2
Trademarks
IBM, the IBM logo, Tivoli and Netcool are registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
Notices and Trademarks 173
174
Index
A
activate datasource . . . . . . . . . . . . . . . . . . . .55 add database file . . . . . . . . . . . . . . . . . . .92 partition . . . . . . . . . . . . . . . . . . . . . .96 add_datafiles.sh . . . . . . . . . . . . . . . . . . .91 adding users . . . . . . . . . . . . . . . . . . . . . . . .36 Admin group . . . . . . . . . . . . . . . . . . . . .31 agent activities . . . . . . . . . . . . . . . . . . . . .56 activities log files . . . . . . . . . . . . . . .63 activity properties . . . . . . . . . . . . . . .60 activity properties, past . . . . . . . . . . .62 administration . . . . . . . . . . . . . . . . .56 cancel activity . . . . . . . . . . . . . . . . .63 list activities . . . . . . . . . . . . . . . . . . .59 list activities, past . . . . . . . . . . . . . . .61 log files . . . . . . . . . . . . . . . . . . . . . .58 run activity . . . . . . . . . . . . . . . . . . . .63 types . . . . . . . . . . . . . . . . . . . . . . . .57 agent_admin see agent agent_admin tool . . . . . . . . . . . . . . .58, 70 see also agent alarm administration . . . . . . . . . . . . . . . .144 context . . . . . . . . . . . . . . . . . . . . . .146 template . . . . . . . . . . . . . . . . . . . . .144 template version . . . . . . . . . . . . . . .144 template, drop . . . . . . . . . . . . . . . .149 template, list . . . . . . . . . . . . . . . . . .148 template, load . . . . . . . . . . . . . . . . .148 template, unload . . . . . . . . . . . . . . .149 alarm_admin tool see alarm application framework . . . . . . . . . . . . . . .9 application server property file . . . . . . . . . . . . . . . . . . .20 architecture client layer . . . . . . . . . . . . . . . . . . . . .7 core framework . . . . . . . . . . . . . . . . .8 data layer . . . . . . . . . . . . . . . . . . . . . .9 server layer . . . . . . . . . . . . . . . . . . . .6
technology packs . . . . . . . . . . . . . . . . 8 archive redo logs . . . . . . . . . . . . . . . . . . . . . 86 archive logs . . . . . . . . . . . . . . . . . . . . . . 85 archiving log files . . . . . . . . . . . . . . . . 106
B
backup database . . . . . . . . . . . . . . . . . . . . . 80 database, import/export . . . . 81, 83, 84 database, offline . . . . . . . . . . . . 81, 83 database, online . . . . . . . . . . . . . 81, 82 file system . . . . . . . . . . . . . . . . . . 103 backups offline . . . . . . . . . . . . . . . . . . . . . . . 83 Oracle commands . . . . . . . . . . . . . . 81 redo logs . . . . . . . . . . . . . . . . . . . . . 86 business services . . . . . . . . . . . . . . . . . . 10
C
cancel agent activity . . . . . . . . . . . . . . . . . . 63 check cpu . . . . . . . . . . . . . . . . . . . . . . . . . 78 Checking . . . . . . . . . . . . . . . . . . . . . . . 45 client layer . . . . . . . . . . . . . . . . . . . . . . . . . 7 operation functions . . . . . . . . . . . . . 11 cold backups . . . . . . . . . . . . . . . . . . . . . 83 commands lar . . . . . . . . . . . . . . . . . . . . . . . . . 106 configuring archive logging . . . . . . . . . . . . . . . . 86 context alarm . . . . . . . . . . . . . . . . . . . . . . 146 corrupt database checking for . . . . . . . . . . . . . . . . . . 88 cpu check . . . . . . . . . . . . . . . . . . . . . . . 78 creating groups . . . . . . . . . . . . . . . . . . . . . . 38 roles . . . . . . . . . . . . . . . . . . . . . . . . 40 crontab setup . . . . . . . . . . . . . . . . . . . . . . . . 17
D
data backing up . . . . . . . . . . . . . . . . . . . 81
175
summarize old . . . . . . . . . . . .154, 155 data layer core framework . . . . . . . . . . . . . . . . .9 database add file . . . . . . . . . . . . . . . . . . . . . .92 backing up . . . . . . . . . . . . . . . . . . . .83 backup . . . . . . . . . . . . . . . . . . . . . . .80 backup, import/export . . . . . .81, 83, 84 backup, offline . . . . . . . . . . . . . .81, 83 backup, online . . . . . . . . . . . . . .81, 82 check . . . . . . . . . . . . . . . . . . . . .75, 77 disable automatic startup/shutdown . .79 export . . . . . . . . . . . . . . . . . . . .81, 83 import . . . . . . . . . . . . . . . . . . . . . . .84 manage . . . . . . . . . . . . . . . . . . . . . .79 modify file . . . . . . . . . . . . . . . . . . . .92 monitor . . . . . . . . . . . . . . . . . . . . . .77 restoring from backup . . . . . . . . . . . .88 space management . . . . . . . . . . . . . .89 start . . . . . . . . . . . . . . . . . . . . . .24, 79 start, manual . . . . . . . . . . . . . . . . . . .80 status . . . . . . . . . . . . . . . . . . . . . . . .75 stop . . . . . . . . . . . . . . . . . . . . . .24, 79 stop, manual . . . . . . . . . . . . . . . . . . .79 datasource activate . . . . . . . . . . . . . . . . . . . . . .55 administration . . . . . . . . . . . . . . . . .54 deactivate . . . . . . . . . . . . . . . . . . . . .55 delete . . . . . . . . . . . . . . . . . . . . . . .137 list . . . . . . . . . . . . . . . . . .55, 131, 132 load from xml . . . . . . . . . . . . .132, 133 loader configuration . . . . . . . . . . . .128 setup . . . . . . . . . . . . . . . . . . . . . . . .16 unload from xml . . . . . . .134, 135, 136 day of week summarizer . . . . . . . . . . . . . . . . . .154 Daylight Saving Time rules . . . . . . . . . . . . . . . . . . . . . . .115 daylight savings time rule . . . . . . . . . . .115 dbspace management . . . . . . . . . . . . . . . . . . .89 dbspace admin tool See tablespace deactivate datasource . . . . . . . . . . . . . . . . . . . .55 delete groups . . . . . . . . . . . . . . . . . . . . . . .38
partition . . . . . . . . . . . . . . . . . . . . . 96 roles . . . . . . . . . . . . . . . . . . . . . . . . 40 users . . . . . . . . . . . . . . . . . . . . . . . . 37 directory server see LDAP disk space usage . . . . . . . . . . . . . . . . . . . 49, 101 documentation font usage . . . . . . . . . . . . . . . . . . . . . 1 structure . . . . . . . . . . . . . . . . . . . . . . 3 typographical conventions . . . . . . . . . 1 user . . . . . . . . . . . . . . . . . . . . . . . . . 3 viewing PDF . . . . . . . . . . . . . . . . . . . 4 viewing Web Help . . . . . . . . . . . . . . . 4 drop_orphaned_external . . . . . . . . . . . . . 71 ds_admin tool see datasource DST rules . . . . . . . . . . . . . . . . . . . . . . 115 identifier . . . . . . . . . . . . . . . . . . . . 116
E
errors partition maintenance . . . . . . . . . . 100 event_clean . . . . . . . . . . . . . . . . . . . . . . 71 Everybody group . . . . . . . . . . . . . . . . . . 31 exp . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 export . . . . . . . . . . . . . . . . . . . . . . . . . . 81 database . . . . . . . . . . . . . . . . . . 81, 83 partition . . . . . . . . . . . . . . . . . . . . . 97 UDC . . . . . . . . . . . . . . . . . . . . . . . . 65
F
file system backup . . . . . . . . . . . . . . . . . . . . . 103 size of . . . . . . . . . . . . . . . . . . . . . . 102 font usage documentation . . . . . . . . . . . . . . . . . . 1
G
groups . . . . . . . . . . . . . . . . . . . . . . . . . associating with a user . . . . . . . . . . . creating . . . . . . . . . . . . . . . . . . . . . . delete . . . . . . . . . . . . . . . . . . . . . . .
31 39 38 38
H
hardware performing diagnostic checks . . . . . . 88 healthcheck . . . . . . . . . . . . . . . . . . . . . . 75
176
holiday add . . . . . . . . . . . . . . . . . . . . . . . .123 dates maintenance . . . . . . . . . . . . .122 delete . . . . . . . . . . . . . . . . . . . . . . .123 list dates . . . . . . . . . . . . . . . . . . . . .122 holiday_admin tool see holiday
I
imp . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 import . . . . . . . . . . . . . . . . . . . . . . . . . .81 database . . . . . . . . . . . . . . . . . . . . . .84 partition . . . . . . . . . . . . . . . . . . . . . .98 UDC . . . . . . . . . . . . . . . . . . . . . . . .65 increasing tablespace size . . . . . . . . . . . .91 init.ora . . . . . . . . . . . . . . . . . . . . . . . . . .86
J
job drop_orphaned_external . . . . . . . . . .71 event_clean . . . . . . . . . . . . . . . . . . .71 pm_daily . . . . . . . . . . . . . . . . . . . . .70 pm_monthly . . . . . . . . . . . . . . . . . . .71 pm_weekly . . . . . . . . . . . . . . . . . . .71 rgfp . . . . . . . . . . . . . . . . . . . . . . . . .71 schedule . . . . . . . . . . . . . . . . . . . . . .70
K
kpi cache administration . . . . . . . . . . . . . . . . .65 synchronize . . . . . . . . . . . . . . . .65, 66 kpicache_admin tool . . . . . . . . . . . . . . . .65 see also kpi cache
L
lar . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 lcm_admin tool see loader configuration LDAP . . . . . . . . . . . . . . . . . . . . . . . . . .31 check . . . . . . . . . . . . . . . . . . . . . . . .75 setup . . . . . . . . . . . . . . . . . . . . . . . .16 start . . . . . . . . . . . . . . . . . . . . . . . . .24 status . . . . . . . . . . . . . . . . . . . . . . . .75 stop . . . . . . . . . . . . . . . . . . . . . . . . .24 list agent activities . . . . . . . . . . . . . . . . .59 agent activities, past . . . . . . . . . . . . .61 datasource . . . . . . . . . . . .55, 131, 132
loader configuration . . . . . . . . 131, 132 partition . . . . . . . . . . . . . . . . . . . . . 99 pinned partition . . . . . . . . . . . . . . . . 99 scheduled jobs . . . . . . . . . . . . . . . . . 72 sessions, partition maintenance . . . . . 99 spaces, partition maintenance . . . . . 100 listener check . . . . . . . . . . . . . . . . . . . . . . . 75 status . . . . . . . . . . . . . . . . . . . . . . . 75 load datasource from xml . . . . . . . 132, 133 loader configuration from xml 133, 134 nc relations from xml . . . . . . . . . . . 133 loader check bad files . . . . . . . . . . . . . . . . 46 check status . . . . . . . . . . . . . . . . . . . 45 configuration manager . . . . . . . . 9, 128 core framework . . . . . . . . . . . . . . . . . 9 disk space usage . . . . . . . . . . . . . . . 49 log level, change . . . . . . . . . . . . . . . 47 operations tasks . . . . . . . . . . . . . . . . 45 property file . . . . . . . . . . . . . . . . . . 20 loader configuration . . . . . . . . . . . . . . . 128 list . . . . . . . . . . . . . . . . . . . . 131, 132 load from xml . . . . . . . . . . . . 133, 134 unload from xml . . . . . . . . . . . . . . 135 log files . . . . . . . . . . . . . . . . . . . . . 76, 104 agent activities . . . . . . . . . . . . . 58, 63 archiving . . . . . . . . . . . . . . . . . . . . 106 check . . . . . . . . . . . . . . . . . . . . . . . 76 summary . . . . . . . . . . . . . . . . . . . . 152 log-archiver.sh . . . . . . . . . . . . . . . . . . 106 logs archive . . . . . . . . . . . . . . . . . . . . . . 85 loader, change level . . . . . . . . . . . . . 47 partition maintenance . . . . . . . . . . . 100 redo . . . . . . . . . . . . . . . . . . . . . . . . 85
M
maintaining tablespaces . . . . . . . . . . . . . . . . . . . 89 misc_clean . . . . . . . . . . . . . . . . . . . . . . 70 modify database file . . . . . . . . . . . . . . . . . . 92
N
nc relations . . . . . . . . . . . . . . . . . . . . . 128 delete . . . . . . . . . . . . . . . . . . . . . . 137
177
load from xml . . . . . . . . . . . . . . . . .133 unload from xml . . . . . . . . . . . . . . .135 NetworkAssure application framework . . . . . . . . . . . .9 architecture . . . . . . . . . . . . . . . . . . . .5 check . . . . . . . . . . . . . . . . . . . . . . . .76 core framework . . . . . . . . . . . . . . . . .8 install summary . . . . . . . . . . . . . . . .16 resource use . . . . . . . . . . . . . . . . . . .77 start . . . . . . . . . . . . . . . . . . .23, 25, 26 status . . . . . . . . . . . . . . . . . . . . . . . .76 stop . . . . . . . . . . . . . . . . . . .23, 25, 26 system maintenance . . . . . . . . . . . . .69
O
offline backup . . . . . . . . . . . . . . . . . . . .81, 83 offline backups . . . . . . . . . . . . . . . . . . . .83 online backup . . . . . . . . . . . . . . . . . . . .81, 82 Overview . . . . . . . . . . . . . . . . . . . . . . . .15
P
parameters partition maintenance . . . . . . . . . . . .98 partition add . . . . . . . . . . . . . . . . . . . . . . . . .96 delete . . . . . . . . . . . . . . . . . . . . . . . .96 errors . . . . . . . . . . . . . . . . . . . . . . .100 export . . . . . . . . . . . . . . . . . . . . . . .97 import . . . . . . . . . . . . . . . . . . . . . . .98 list . . . . . . . . . . . . . . . . . . . . . . . . . .99 list pinned . . . . . . . . . . . . . . . . . . . .99 logs . . . . . . . . . . . . . . . . . . . . . . . .100 pin . . . . . . . . . . . . . . . . . . . . . . . . . .97 sessions, list . . . . . . . . . . . . . . . . . . .99 sessions, update . . . . . . . . . . . . . . . .99 spaces, list . . . . . . . . . . . . . . . . . . .100 status . . . . . . . . . . . . . . . . . . . . . . .100 partition maintenance . . . . . . . . . . . . . . .93 add partition . . . . . . . . . . . . . . . . . . .96 delete partition . . . . . . . . . . . . . . . . .96 errors . . . . . . . . . . . . . . . . . . . . . . .100 export partition . . . . . . . . . . . . . . . . .97 import partition . . . . . . . . . . . . . . . .98 list partition . . . . . . . . . . . . . . . . . . .99 list pinned partition . . . . . . . . . . . . . .99 logs . . . . . . . . . . . . . . . . . . . . . . . .100
178
parameters . . . . . . . . . . . . . . . . . . . 98 pin partition . . . . . . . . . . . . . . . . . . 97 sessions, list . . . . . . . . . . . . . . . . . . 99 sessions, update . . . . . . . . . . . . . . . . 99 spaces, list . . . . . . . . . . . . . . . . . . 100 status . . . . . . . . . . . . . . . . . . . . . . 100 PDF format . . . . . . . . . . . . . . . . . . . . . . . 4 pin partition . . . . . . . . . . . . . . . . . . . . . 97 pm_daily . . . . . . . . . . . . . . . . . . . . . . . 70 pm_monthly . . . . . . . . . . . . . . . . . . . . . 71 pm_weekly . . . . . . . . . . . . . . . . . . . . . . 71 privileges . . . . . . . . . . . . . . . . . . . . . . . 32 about . . . . . . . . . . . . . . . . . . . . . . . 32 assigning to roles . . . . . . . . . . . . . . . 41 process scheduler . . . . . . . . . . . . . . . . . . . . 70 process manager. See sapmgr process monitor. See sapmon processor check . . . . . . . . . . . . . . . . . . . . . . . 78 properties agent activities . . . . . . . . . . . . . . . . 60 agent activities, past . . . . . . . . . . . . 62 property file application server . . . . . . . . . . . . . . 20 loader . . . . . . . . . . . . . . . . . . . . . . . 20 publications user . . . . . . . . . . . . . . . . . . . . . . . . . 3
R
redo logs . . . . . . . . . . . . . . . . . . . . . . . . 85 archive . . . . . . . . . . . . . . . . . . . . . . 86 archiving . . . . . . . . . . . . . . . . . . . . 86 log files redo . . . . . . . . . . . . . . . . . . . . . 85 report time zones . . . . . . . . . . . . . . . . . . . 115 restoring databases . . . . . . . . . . . . . . . . . . . . 88 missing files . . . . . . . . . . . . . . . . . . 88 rgfp . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 roles . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 assigning privileges to . . . . . . . . . . . 41 assigning users to . . . . . . . . . . . . . . 39 creating . . . . . . . . . . . . . . . . . . . . . . 40 delete . . . . . . . . . . . . . . . . . . . . . . . 40 managing . . . . . . . . . . . . . . . . . . . . 40
run agent activity . . . . . . . . . . . . . . . . . .63
S
SAP setup . . . . . . . . . . . . . . . . . . . . . . . .19 sapmgr start . . . . . . . . . . . . . . . . . . . . . . . . .25 stop . . . . . . . . . . . . . . . . . . . . . . . . .25 sapmon check . . . . . . . . . . . . . . . . . . . . . . . .76 start . . . . . . . . . . . . . . . . . . . . . . . . .24 status . . . . . . . . . . . . . . . . . . . . . . . .76 stop . . . . . . . . . . . . . . . . . . . . . . . . .24 schedule list jobs . . . . . . . . . . . . . . . . . . . . . .72 maintenance . . . . . . . . . . . . . . . . . . .72 schedule_admin tool . . . . . . . . . . . . .56, 70 scheduler options . . . . . . . . . . . . . . . . . . . . . . .73 process . . . . . . . . . . . . . . . . . . . . . .70 See also schedule server layer . . . . . . . . . . . . . . . . . . . . . . . . .6 operation functions . . . . . . . . . . . . . .13 status reports for . . . . . . . . . . . . . . . .75 services business . . . . . . . . . . . . . . . . . . . . . .10 database . . . . . . . . . . . . . . . . . . . . . .11 platform management . . . . . . . . . . . .10 user management . . . . . . . . . . . . . . .11 session partition maintenance . . . . . . . . . . . .99 sessions partition maintenance . . . . . . . . . . . .99 setup crontab . . . . . . . . . . . . . . . . . . . . . .17 datasource . . . . . . . . . . . . . . . . . . . .16 LDAP . . . . . . . . . . . . . . . . . . . . . . .16 root user . . . . . . . . . . . . . . . . . . . . . .18 SAP . . . . . . . . . . . . . . . . . . . . . . . . .19 tasks . . . . . . . . . . . . . . . . . . . . . . . .15 virtuo user . . . . . . . . . . . . . . . . . . . .17 spaces partition maintenance . . . . . . . . . . .100 start database . . . . . . . . . . . . . . . . . . .24, 79 database, manual . . . . . . . . . . . . . . .80
LDAP . . . . . . . . . . . . . . . . . . . . . . . 24 NetworkAssure . . . . . . . . . . 23, 25, 26 sapmgr . . . . . . . . . . . . . . . . . . . . . . 25 sapmon . . . . . . . . . . . . . . . . . . . . . . 24 status cpu . . . . . . . . . . . . . . . . . . . . . . . . . 78 database . . . . . . . . . . . . . . . . . . 75, 77 LDAP . . . . . . . . . . . . . . . . . . . . . . . 75 listener . . . . . . . . . . . . . . . . . . . . . . 75 loader . . . . . . . . . . . . . . . . . . . . . . . 45 NetworkAssure . . . . . . . . . . . . . . . . 76 partition maintenance . . . . . . . . . . . 100 sapmon . . . . . . . . . . . . . . . . . . . . . . 76 status of server . . . . . . . . . . . . . . . . . . . 75 stop database . . . . . . . . . . . . . . . . . . 24, 79 database, manual . . . . . . . . . . . . . . . 79 LDAP . . . . . . . . . . . . . . . . . . . . . . . 24 NetworkAssure . . . . . . . . . . 23, 25, 26 sapmgr . . . . . . . . . . . . . . . . . . . . . . 25 sapmon . . . . . . . . . . . . . . . . . . . . . . 24 summaries . . . . . . . . . . . . . . . . . . . . . . . 10 summarizer . . . . . . . . . . . . . . . . . . . . . 151 day of week . . . . . . . . . . . . . . . . . . 154 old data . . . . . . . . . . . . . . . . . 154, 155 start day of week . . . . . . . . . . . . . . 154 switch on/off . . . . . . . . . . . . . . . . . 152 summary log file . . . . . . . . . . . . . . . . . . . . . 152 switch summarizer on/off . . . . . . . . . . . . . 152 synchronize kpi cache . . . . . . . . . . . . . . . . . 65, 66
T
tablespace increase . . . . . . . . . . . . . . . . . . 91, 92 monitor . . . . . . . . . . . . . . . . . . . . . . 89 recover . . . . . . . . . . . . . . . . . . . . . . 92 tablespaces increasing size of . . . . . . . . . . . . . . . 91 maintaining . . . . . . . . . . . . . . . . . . . 89 technology packs core framework . . . . . . . . . . . . . . . . . 8 template alarm . . . . . . . . . . . . . . . . . . . . . . 144 drop, alarm . . . . . . . . . . . . . . . . . . 149 list, alarm . . . . . . . . . . . . . . . . . . . 148
179
load, alarm . . . . . . . . . . . . . . . . . . .148 unload, alarm . . . . . . . . . . . . . . . . .149 version, alarm . . . . . . . . . . . . . . . . .144 TFP_NC_STABILITY . . . . . . . . . . . . . .51 TFP_SHM_MIN_SIZE . . . . . . . . . . . . . .49 time zone regions . . . . . . . . . . . . . . . . .118 DST rules . . . . . . . . . . . . . . . . . . . .115 time zones DST . . . . . . . . . . . . . . . . . . . . . . . .115 typographical conventions . . . . . . . . . . . . .1 tz_admin tool see time zones
U
UDC export . . . . . . . . . . . . . . . . . . . . . . .65 import . . . . . . . . . . . . . . . . . . . . . . .65 unix system monitoring . . . . . . . . . . . . . .77 unload datasource from xml . . . .134, 135, 136 loader configuration from xml . . . . .135 nc relations from xml . . . . . . . . . . .135 update sessions, partition maintenance . . . . .99 user setup root . . . . . . . . . . . . . . . . . . . . .18 setup virtuo . . . . . . . . . . . . . . . . . . .17 user management . . . . . . . . . . . . . . . . . .36 user publications . . . . . . . . . . . . . . . . . . . .3 UserEdit privilege . . . . . . . . . . . .38, 39, 40 users adding . . . . . . . . . . . . . . . . . . . . . . .36 delete . . . . . . . . . . . . . . . . . . . . . . . .37 permissions . . . . . . . . . . . . . . . . . . .31 roles associated with . . . . . . . . . . . . .39 Web client . . . . . . . . . . . . . . . . . . . .31
W
Web client users . . . . . . . . . . . . . . . . . . .31 Web Help format . . . . . . . . . . . . . . . . . . .4
180
IBM
Copyright IBM Corporation 2008 International Business Machines Corporation 5300 Cork Airport Business Park Kinsale Road Cork, Ireland. Printed in the Republic of Ireland All Rights Reserved IBM, IBM logo, Tivoli, and Netcool are trademarks of International Business Machines Corporation in the United States, other countries or both. Other company, product and service names may be trademarks or service marks of others
181

Netcool Wireless Admin Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Netcool Wireless Admin Guide

Transféré par

Droits d'auteur :

Formats disponibles

Netcool Performance Manager for Wireless

Copyright IBM Corp. 2008

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Copyright IBM Corp. 2008

Tivoli Netcool Performance Manager for Wireless: Administration Guide

About This Documentation

Required Skills and Knowledge

This guide assumes you are familiar with the following:

GPS NULL MYWEBSERVER

Copyright IBM Corp. 2008

General Document Conventions (Continued)

See Document Conventions

Bold SMALL CAPS

New terms, emphasis, and book titles.

Tivoli Netcool Performance Manager for Wireless: Administration Guide

This document is organized in to the following chapters and appendices:

Tools LCM Administration Alarm Administration

Tivoli Netcool Performance Manager for Wireless User Documentation

Installation Guide Upgrade Guide

About This Documentation 3

Tivoli Netcool Performance Manager for Wireless User Documentation (Continued)

Administration Guide User Guide

Viewing the Online Help

Viewing the Publications in PDF

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Tivoli Netcool Performance Manager for Wireless Architecture Overview

Listing current software versions

Copyright IBM Corp. 2008

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Tivoli Netcool Performance Manager for Wireless Server

Tivoli Netcool Performance Manager for Wireless Architecture Overview 7

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Extraction, Transformation and Loading (ETL) Data Layer

Tivoli Netcool Performance Manager for Wireless Application Framework

Tivoli Netcool Performance Manager for Wireless Architecture Overview 9

Client Operation Functions

Tivoli Netcool Performance Manager for Wireless Architecture Overview 11

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Server Operation Functions

Tivoli Netcool Performance Manager for Wireless Architecture Overview 13

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Setup tasks include:

Copyright IBM Corp. 2008

Software Install Summary

LDAP - Directory Server setup

Virtuo User setup

Root User Setup

Additional entries and scripts

The following script is also available:

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Individual processes can be started using:

Information on processes can be displayed using:

or sap disp -l (verbose output) Producing the following example output:

The following is a sample application server property file:

com.comnitel.process.as.group=asgroup com.comnitel.process.as.start.pmgtprovider=false com.comnitel.process.as.host=${WMCHOST} com.comnitel.process.as.start.sequence=1

Application Server Property File - Variable Descriptions

com.comnitel.process.as.exec=@{WMCROOT}/bin/ run_as com.comnitel.process.as.params= com.comnitel.process.as.group=asgroup

able is optional and defaults to true.

The following is a sample loader property file:

Tivoli Netcool Performance Manager for Wireless: Administration Guide

Loader Property File - Variable Descriptions

Manual configuration of processes through SAP is not necessary.

Tivoli Netcool Performance Manager for Wireless: Administration Guide