Tivoli Netcool®/Proviso® 4.4.3 IBM · PDF fileQuestions on the capabilities of non-IBM...

IBMNetcool®/Proviso® 4.4.3Tivoli

Document Revision R2E3

Release Notes

Notices

This information was developed for products and services offered in the U.S.A. IBM® may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information about the products and services currently available in your area. 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 give 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, 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 might 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. 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 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A.

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.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

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 is for planning purposes only. The information herein is subject to change before the products described become available.

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.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming

techniques on various operating systems. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating system for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color illustrations might not appear.

Trademarks

AIX®, DB2®, developerWorks®, eServer, i5/OS®, IBM®, the IBM logo®, IBMLink, iSeries®, Lotus®, Netcool®, Netcool/Proviso®, OMEGAMON®, Passport Advantage®, pSeries®, Rational®, Redbooks®, OS/390®, OS/400®, Tivoli®, the Tivoli logo®, Tivoli Enterprise Console®, WebSphere®, and zSeries® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Intel® is a registered trademark of Intel Corporation or its subsidiaries in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft® and Windows® are registered 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, and service names may be trademarks or service marks of others.

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.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Contents

Contents

Overview of the Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Netcool/Proviso Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Problems and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation and Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Installing Netcool/Proviso from a DVD/CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Case in Deployer Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Default for TARGET_TNS_HOST Property Always Set to PV . . . . . . . . . . . . . . . . . . . . . . . 3Database Remove Fails After Upgrade to Netcool/Proviso FixPack 3 and Oracle10g . . . . . . 3

General Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Indents Not Preserved In Acrobat Reader Cut and Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Special Characters and Command-Line Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Launchpad GUI Requires SHELL Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5New Installations Intending to Use the DataLoad High Availability Manager (HAM) . . . . . . 5Topology Editor Does Not Propagate Different User Credentials on New Hosts . . . . . . . . . 5DataChannel Parameter Keys Are Converted to Uppercase . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Non-default Oracle Data Mount Points Can Be Overwritten . . . . . . . . . . . . . . . . . . . . . . . . . . 6Problem with Uploading DataChannel Parameters for Removed AMGRs . . . . . . . . . . . . . . . 6Moving DataLoad High Availability Manager (HAM) Collectors to New Hosts . . . . . . . . . . . 6Moving UBA Collectors With BLB and QCIF Components . . . . . . . . . . . . . . . . . . . . . . . . . . 6Property Value Fields May Go Blank When Using Reset Default Button . . . . . . . . . . . . . . . . 6Topology Editor Does Not Update ProvisoInfo URL When DataMart Host is Changed . . . 7Request Editor May Not Start When Launched From DataMart GUI. . . . . . . . . . . . . . . . . . . 7Default DataView Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Maximum Collector Identification Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Database Password Mismatch Causes Component to Die. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8SilverStream User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Recommendation for Adding SNMP Collectors to a Minimal Deployment . . . . . . . . . . . . . . 8Splitting DataChannel into Separate Data and Executable Directories. . . . . . . . . . . . . . . . . . . 8

Technology Pack Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Critical Technology Pack Upgrade/Installation Notes -- Your Upgrade/Installation Will Fail if

You Do Not Read This . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Technology Pack Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Netcool/Proviso Upgrade Flags UBA Properties as Custom Properties for Installed UBA

Technology Packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Technology Packs Do Not Support Silent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Installing and Configuring SNMP and UBA Technology Packs Require Different Procedures

12Installation Errors Written to Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Netcool/Proviso Release Notes, Version 4.4.3 v

Contents

BCOL Collectors Require an Additional Environment Variable . . . . . . . . . . . . . . . . . . . . . . . 12Topology Editor JVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Cisco CMW/IPT Path Changes Required Following Netcool/Proviso Upgrade. . . . . . . . . . 13

AIX-Specific Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Oracle Listener Control Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Changes and New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Netcool/Proviso Common Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installing Netcool/Proviso. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installing Technology Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Making Changes to Your Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SNMP Bandwidth Control and Collection Smoothing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Features Available in the FixPack 1 Release of Netcool/Proviso 4.4.3 . . . . . . . . . . . . . . . . . . . . . 18

Upgrade Support from Netcool/Proviso 4.4.1 or 4.4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Supported Upgrade Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Netcool/Proviso High Availability Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19DataView Uses Oracle Client Version 9.2.0.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Features Available in the FixPack 2 Release of Netcool/Proviso 4.4.3 . . . . . . . . . . . . . . . . . . . . . 20Matrix Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Features Available in the FixPack 3 Release of Netcool/Proviso 4.4.3 . . . . . . . . . . . . . . . . . . . . . 20Oracle10g Support (Upgrade Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Red Hat Enterprise Linux 5 Support For SNMP DataLoad Collectors . . . . . . . . . . . . . . . . . 21Topology Editor Enhancements to Simplify Upgrade of UBA Technology Packs . . . . . . . . 22

Other Changes/New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Problems Resolved in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

DataMart Documentation Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Appendix A: Expanded Versioning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Netcool/Proviso Version 4.4.3 Versioning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

vi Netcool/Proviso Release Notes, Version 4.4.3

Release Notes

bility

, 2008

ber 30, 2008

31, 2009

, 2009

Netcool®/Proviso® Version 4.4.3

These release notes (which are intended for internal and customer use) support Netcool/Proviso 4.4.3, and contain the following topics:

Overview of the Release

Note: Beginning with FixPack 1of Netcool/Proviso 4.4.3, the term “Technology Pack” has replaced “Application Pack” in all new or changed material in the Netcool/Proviso documentation set.

Topics Page

Overview of the Release 1

Netcool/Proviso Modules 2

Problems and Limitations 2

Changes and New Features 15

Problems Resolved in this Release 22

Netcool/Proviso Documentation 24

Version FixPack Type of Release Availa

4.4.3 Not applicable

This is a GA release of Netcool/Proviso, and is supported for new installations on Solaris, AIX (not DataView), and Linux (SNMP Collector only) systems.

June 30

4.4.3 - adding support for new features

FixPack 1 Beginning December 30, 2008, Netcool/Proviso 4.4.3 introduces functionality to support Netcool/Proviso upgrade and the DataLoad High Availability Manager. For more information, see Changes and New Features on page 15.

Decem


FixPack 2 Beginning March 31, 2009, Netcool/Proviso 4.4.3 introduces functionality to support Matrix tables.

March


FixPack 3 Beginning July 14, 2009, Netcool/Proviso 4.4.3 introduces functionality to support Oracle10g upgrade, Red Hat Enterprise Linux 5 support for SNMP data collectors, Topology Editor enhancements to simplify upgrade of UBA technology packs. For more information, see Changes and New Features on page 15.

July 14

Netcool/Proviso Release Notes, Version 4.4.3 1

Netcool/Proviso Modules

Netcool/Proviso Version 4.4.3 consists of the following modules:

• Netcool/Proviso Database Version 4.4.3.3R0E3

• Netcool/Proviso DataChannel Version 4.4.3.3-324

• Netcool/Proviso DataLoad Version 4.4.3.3-324

• Netcool/Proviso DataMart Version 4.4.3.3-20090514

• Netcool/Proviso DataView Version 4.4.3.3 build 4433R0E2

Note: Although some of the module version numbers do not include the traditional R2 numbers, they are, in fact, GA versions.

To determine the versions of the Netcool/Proviso modules installed on your system, see the Technical Note entitled Netcool/Proviso Technical Note: Tools for Version Reporting that delivers with the Netcool/Proviso documentation.

Important: For more detailed versioning information, see Appendix A on page 25.

In addition, Version 4.4.3 introduces a new, graphical installation interface made up of the following modules:

• Launchpad

• Topology Editor

• Deployer

• Technology Pack Installer

See the Netcool/Proviso Installation Guide for detailed information about these interfaces. See Netcool/Proviso Common Installer on page 16 for brief descriptions of these interfaces.

Problems and Limitations

This section lists the known limitations in this release of Netcool/Proviso. The topics are as follows:

• Installation and Configuration Problems on page 2

• General Problems on page 4

• Technology Pack Problems on page 11

• AIX-Specific Restrictions on page 15

Installation and Configuration Problems

This section lists the known installation and configuration problems with Netcool/Proviso 4.4.3.

Installing Netcool/Proviso from a DVD/CD

Currently, installing Netcool/Proviso from a DVD/CD is not supported. You must copy the files from the DVD/CD onto your local hard drive before installing.

2 Netcool/Proviso Release Notes, Version 4.4.3

Case in Deployer Commands

All command line deployer commands are case-sensitive and must be submitted as documented in order to function correctly.

For example, the ./deployer.bin -Daction=clean command is used to clean all the installed components on the local system. If you fail to use an uppercase D for the -Daction parameter (for example, ./deployer.bin -daction=clean), the deployer silently ignores the clean option and treats the run as an installation instead of an uninstallation. In this case, when the run is complete, the deployer generates the following error message:

GYMCI9023W There appear to be no differences between the desired topology state and the current state of the Proviso installation.

Default for TARGET_TNS_HOST Property Always Set to PV

The TARGET_TNS_HOST property specifies the TNS name of the Oracle server on the target machine. The default value for this property is PV. If you use a non-default value, you must remember to use the same value in all properties that call for the TNS name. For example, if you set the Oracle TNS name for this property to PROV instead of PV, you must override the default PV value in all properties that call for the TNS name.

Database Remove Fails After Upgrade to Netcool/Proviso FixPack 3 and Oracle10g

This issue relates to the following scenario:

• The user has upgraded to Netcool/Proviso 4.4.3 FixPack 3.

• The user has upgraded to Oracle10g.

• The user wants to remove (uninstall) the database component.

The removal of the database component fails because:

• The deployer is using the old value in ORACLE_HOME that points to /opt/oracle/9.2.0 instead of the new value in ORACLE_HOME that points to /opt/oracle/10.2.0.

• The Topology Editor points to the /opt/oracle/product/9.2.0/jdbc/lib Oracle JDBC driver base installation directory instead of the new directory /opt/oracle/product/10.2.0/jdbc/lib.

You specify the base installation directory of the Oracle JDBC driver during the upgrade to Netcool/Proviso 4.4.3 FixPack 3, specifically when you install and start the Topology Editor. The steps for installing and starting the Topology Editor are described in the Netcool/Proviso Upgrade Guide.

When you get to the step that displays the default location of the base installation directory of the Oracle JDBC driver, specify:

/opt/oracle/product/10.2.0/jdbc/lib

To remove the database component:

Important: Before you remove the database component, you must have previously removed all of the other Netcool/Proviso components. See the Netcool/Proviso Installation Guide for more information on removing and for restrictions associated with removing Netcool/Proviso components.

1. On the Install Topology Editor page in the launchpad, click the Start Topology Editor link.

2. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed.

3. For the topology source, select the option that corresponds to the version of Netcool/Proviso that you are using, then click Next. For example:

From database (v. 443)

4. Verify that all of the fields for the database connection are filled in with the correct values:


— Database hostname — The name of the database host. The default value is localhost.

— Port — The port number used for communication with the database. The default value is 1521.

— Database user — The user name used to access the database. The default value is PV_INSTALL.

— Database password — The password for the database user account. For example, PV.

— SID — The SID for the database. The default value is PV.

If desired, click Save as defaults to save these values for future incremental installations.

5. Click Next.

6. In the Default operating systems for hosts field, specify the correct operating system for your environment. For example:

SOLARIS

7. Click Finish. The upgrade topology is retrieved from the Database and is displayed in the Topology Editor.

8. Click Topology>Save topology as.

9. If you have validated your upgrade topology and are satisfied that it is correct, ignore the displayed warning message and click Ok.

10. Specifiy a name for the topology file, or use the default of topology.xml.

11. Click Ok.

12. Select Topology>Open existing topology to open the topology you just saved.

13. Click Finish. The topology you just saved is displayed in the Topology Editor.

14. For the topology source, click local then use Browse to navigate to the correct directory and file. Once you have selected the file, click OK. The selected file is displayed in the Open Topology window.

15. Change any fields that specify the value 9.2.0 to 10.2.0.

16. Save the edited topology.

17. Run the deployer from /opt/IBM/proviso/deployer (or specify another directory if you installed in a different directory) with the following command:

# ./deployer.bin -Daction=clean

When prompted, specify the saved topology, for example: topology.xml

The above command removes the database component.

General Problems

This section lists the known general problems with Netcool/Proviso 4.4.3.

Indents Not Preserved In Acrobat Reader Cut and Paste

Indents are not preserved when cutting and pasting text in Adobe Acrobat, since this functionality is not provided in the base product.

This pertains to cutting and pasting text from the PDF versions of the user guides.

Note that in many cases, indentations in examples (such as the Oracle listener and tsnname configuration instructions in the Netcool/Proviso Installation Guide), must be preserved in order for the lines to be parsed correctly.


Special Characters and Command-Line Utilities

When using the command line utilities (like resmgr, for example) make sure that you use a backslash (\) to escape characters that are special to the shell and to TCL, especially the following:

• [ ]

• { }

• ‘

• "

• \

• $

Launchpad GUI Requires SHELL Variable

The launchpad GUI requires that the SHELL variable in your environment is set to a valid value (for example, /sbin/sh or /sbin/ksh) before starting the application.

New Installations Intending to Use the DataLoad High Availability Manager (HAM)

If you are setting up a new Netcool/Proviso environment and plan to use a High Availability Manager (HAM) in that environment, perform the following tasks in the following order:

1. Install all collectors.

2. Configure and start the HAM.

3. Install all Technology Packs.

4. Perform the discovery.

Topology Editor Does Not Propagate Different User Credentials on New Hosts

If you add a new host to a topology and specify user credentials that differ from the default of pvuser in the Specify the Host Details panel, your user credentials will not be propagated to Netcool/Proviso components on the new host.

To work around this issue, do the following:

1. Add the new host to the topology with the Specify the Host Details panel, using the default credentials of pvuser.

2. Once the host has been added, select the host in the Physical View.

3. Within the Properties displayed for the selected host object, specify the user credentials you wish to use on that host. Specifying the user credentials directly in the host object will ensure that the property value is inherited correctly by its Netcool/Proviso components.

DataChannel Parameter Keys Are Converted to Uppercase

This issue can affect customers who are upgrading their environment to Netcool/Proviso 4.4.3.

Beginning with Netcool/Proviso 4.4.3, DataChannel parameters reside in the database. When the parameters are placed into the database, all of the DataChannel keys, or the portion of the parameter definition that appears to the left of the equals sign (for example, DC_KEY=value), are converted to uppercase.


As most DataChannel keys are already in uppercase, this issue is unlikely to affect your environment. However, to verify that this issue will not affect your Technology Packs or any external scripts, you should verify your dc.cfg file. If you have any lower-case or mixed-case DataChannel keys, it is recommended that you change these keys to all-uppercase before upgrading your environment to verify that your Netcool/Proviso components work properly.

This issue is known to affect only the Netflow IPFIX Technology Pack, as all other Technology Packs have been tested to verify any problems.

Non-default Oracle Data Mount Points Can Be Overwritten


If your environment uses non-default values for the Oracle data mount points, your site values can be overwritten by the Netcool/Proviso defaults (/raid_2/oradata and raid_3/oradata, by default) when your upgrade topology is loaded into the Topology Editor.

To remedy this issue, verify the O_MOUNTPOINT_1 and O_MOUNTPOINT_2 Database Configuration properties in your topology and input your site’s values, if necessary.

Problem with Uploading DataChannel Parameters for Removed AMGRs


If you have removed a DataChannel machine from your environment, but that machine’s AMGR is still registered with the DataChannel CNS, the DataChannel parameter upload script will attempt to contact the missing AMGR. To remedy this issue, remove the missing AMGR from the DataChannel CMS.

Moving DataLoad High Availability Manager (HAM) Collectors to New Hosts

In a High Availability Manager (HAM) environment with one primary collector and one spare collector (a 1+1 environment), you may encounter a problem if you move either of the collectors to a new host, whereby the moved collector is installed and configured correctly on the new host, but is not removed from the old host.

If the moved collector is still installed on the old host (status shows as Configured) after you complete the move operation, you can remove the collector from the old host with the following command:

deployer.bin -DAction=uninstall -DTarget=DLR -DUsehostname=<NewHostName>

For more information about Deployer commands, see the Deployer CLI Options appendix in the Netcool/Proviso Installation Guide.

Moving UBA Collectors With BLB and QCIF Components

You cannot move UBA collectors that have BLB and QCIF subcomponents. If you want to move this type of UBA collector, you must manually remove it from the old host in the topology and then add it to the new host.

Property Value Fields May Go Blank When Using Reset Default Button

In the Topology Editor, if you select the Value field for a property and click the Reset Default button, all property value fields may go blank.

To work around this issue, click on another field for the property that you wish to change (for example, the Description field) in order to select the row, then click the Reset Default button again.


Topology Editor Does Not Update ProvisoInfo URL When DataMart Host is Changed

The ProvisoInfo URL property value is not updated when you change the DataMart host in the Topology Editor. Although the property value is not editable, you can do the following to update the property with the correct value:

1. In the Topology Editor, select DataMart in the Logical View.

2. Click the Advanced Properties tab.

3. Select the ProvisoInfo URL property.

4. To update the property value, click the Reset Default button in the Topology Editor.

Request Editor May Not Start When Launched From DataMart GUI

If you attempt to launch the Request Editor from within the Configuration tab of the DataMart GUI, the application may sometimes fail to start.

To work around this issue, do the following:

1. On the DataMart host, log in as pvuser.

2. Set and export the DISPLAY variable.

3. Source the DataMart environment using the following command:

$ . /opt/datamart/dataMart.env

4. Change your directory to the DataMart bin directory (/opt/datamart, by default). For example:

$ cd /opt/datamart/bin

5. Start the Request Editor using the following command:

$ ./requestedit

Default DataView Portal

With Netcool/Proviso 4.4.3, the default DataView portal is DVPortal3. When you apply an interim fix or fix pack to a Netcool/Proviso 4.4.3 deployment, the default DataView portal might be overwritten by DVPortal2. If that happens, you can restore DVPortal3 by following the instructions in Netcool/Proviso Technical Note: Changing to the New Skin. You can find this document online at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/ com.ibm.netcool_proviso.doc/tech_notes/NetcoolProvisoTechNote-ChangingToNewSkin.pdf

Maximum Collector Identification Number

In Netcool/Proviso 4.4.3, the maximum collector identification number is 999.

If you installed Netcool/Proviso 4.4.1 using anything other than the 4.4.1 DataLoad and DataChannel installers, you might have numbered collectors at 1000 or higher. Check your system to see if you have any collector numbers (UBA, SNMP, or BCOL) numbered 1000 or higher. You must renumber any such collectors to be numbered in the range 1 to 999 (inclusive).


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_proviso.doc/tech_notes/NetcoolProvisoTechNote-ChangingToNewSkin.pdf

Database Password Mismatch Causes Component to Die

If the passwords for the DataChannel components do not match the database password, they will run silently without doing anything. A misconfigured database user ID and password will not be logged in the walkback file, so be sure to verify these settings.

SilverStream User

The value of the Unix SilverStream user property is taken from the host Unix user property. If the value on the host Unix user property is changed, the value for the Unix SilverStream user property is automatically changed to the new value.

As intended, this “inheritance” will not take place if the Unix SilverStream user property is changed on the Advanced Properties tab of the DataView component. So, it is recommended that you only change the Unix user property on the host so that the new value is propagated correctly.

Recommendation for Adding SNMP Collectors to a Minimal Deployment

If you want to add SNMP collectors following a minimal deployment of Netcool/Proviso, IBM recommends that you install DataLoad on the new host using the same path that you specified on the original host (for example, /opt/proviso/dataload). If the same DataLoad root directory is not specified on the new host, the installation will complete successfully, but the DataLoad components will be split between several directories.

Splitting DataChannel into Separate Data and Executable Directories

You can upgrade or create an environment where the DataChannel is split into separate data and executable directories. For example:

• DataChannel DATA root directory (for example, /opt/datachannelDATA) — The directory that contains the non-administrative DataChannel components.

• DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE) — The directory that contains the administrative DataChannel components.

If you plan to upgrade or create this type of environment, you must perform some additional actions as described in the sections below.

Upgrading an Existing Environment

To upgrade an existing environment that has separate DataChannel DATA and EXECUTABLE directories, do the following:

1. Import your upgrade topology as described in the Netcool/Proviso Upgrade Guide.

2. In the Physical View, for each DataChannel host that does not include a BCOL or UBA component, do the following:

2-a. On the Properties tab, select the DC Root Directory property and change the value from the DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE) to the DataChannel DATA root directory (for example, /opt/datachannelDATA).

2-b. Click the Advanced Properties tab.

2-c. Select the DC conf Directory property and change the value from the DataChannel DATA root directory (for example, /opt/datachannelDATA/conf) to the DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE/conf).


2-d. Select the DataChannel bin Directory property and change the value from the DataChannel DATA root directory (for example, /opt/datachannelDATA/bin) to the DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE/bin).

3. Prepare and deploy your upgrade topology as described in the Netcool/Proviso Upgrade Guide.

4. Perform the tasks described in Configuring Each DataChannel Host Following Upgrade/Installation on page 9.

Creating an Environment with Split DataChannel Data and Executable Directories

To create an environment that has separate DataChannel DATA and EXECUTABLE directories, do the following:

1. Create your topology and add a DataChannel component as described in the Netcool/Proviso Installation Guide.

2. In the Physical View, for each DataChannel host that does not include a BCOL or UBA component, do the following:

2-a. On the Properties tab, select the DC Root Directory property and change the value from the DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE) to the DataChannel DATA root directory (for example, /opt/datachannelDATA).

2-b. Click the Advanced Properties tab.

2-c. Select the DC conf Directory property and change the value from the DataChannel DATA root directory (for example, /opt/datachannelDATA/conf) to the DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE/conf).

2-d. Select the DataChannel bin Directory property and change the value from the DataChannel DATA root directory (for example, /opt/datachannelDATA/bin) to the DataChannel EXECUTABLE root directory (for example, /opt/datachannelEXE/bin).

3. Create and deploy your topology as described in the Netcool/Proviso Installation Guide.

4. Perform the tasks described in Configuring Each DataChannel Host Following Upgrade/Installation on page 9.

Configuring Each DataChannel Host Following Upgrade/Installation

Once you have upgraded or installed your environment as described above, do the following on each DataChannel host:

1. Log onto the host as root.

2. Change the owner of the DataChannel EXECUTABLE root directory to the Netcool/Proviso user, such as pvuser. For example:

chown pvuser:staff /opt/datachannelEXE

3. Switch the session user to the Netcool/Proviso user, such as pvuser. For example:

su - pvuser

4. Change the working directory to the DataChannel DATA root directory

5. Open the dataChannel.env file for editing.

6. Change the DC_PRODUCT_HOME parameter to specify the DataChannel EXECUTABLE root directory. For example:

DC_PRODUCT_HOME=/opt/datachannelEXE

7. Once you have made your edits, write and quit the file.

8. Move the following items from the DataChannel DATA root directory to the DataChannel EXECUTABLE root directory:

mv /opt/datachannelDATA/dataChannel.env /opt/datachannelEXE/dataChannel.env mv /opt/datachannelDATA/bin /opt/datachannelEXE/bin


mv /opt/datachannelDATA/conf /opt/datachannelEXE/conf mv /opt/datachannelDATA/lib /opt/datachannelEXE/lib mv /opt/datachannelDATA/license /opt/datachannelEXE/license

9. Open the crontab file for editing by using the following command:

crontab -e

10. For each DataChannel component listed in the crontab file, change the DataChannel DATA root directory to the DataChannel EXECUTABLE root directory. For example:

Before:

0,5,10,15,20,25,30,35,40,45,50,55 * * * * . /opt/datachannelDATA/dataChannel.env && /opt/datachannelDATA/bin/cnsw > /dev/null 2>&1

After:

# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * . /opt/datachannelEXE/dataChannel.env && /opt/datachannelEXE/bin/cnsw > /dev/null 2>&1

11. Once you have made your edits, write and quit the file.


Technology Pack Problems

The following defects are related to technology packs. For more information, see the Netcool/Proviso Technology Pack Release Notes for your specific technology pack version.

Critical Technology Pack Upgrade/Installation Notes -- Your Upgrade/Installation Will Fail if You Do Not Read This

Alcatel Lucent 5620 SAM Technology Packs Upgrade/Installation

If you are running a version earlier than 4.3-U of the Alcatel-Lucent 5620 SAM Technology Pack and plan to upgrade to Netcool/Proviso 4.4.3, you must upgrade this pack to the 4.3-U or later level before upgrading Netcool/Proviso. If you are installing Netcool/Proviso 4.4.3 into a new environment and plan to install the Alcatel-Lucent 5620 SAM Technology Pack, you must install and run the 4.3-U or later version of this pack.

Netflow IPFIX Technology Packs Upgrade/Installation

If you are running a version earlier than 4.3-V of the Netflow IPFIX Technology Pack and plan to upgrade to Netcool/Proviso 4.4.3, you must upgrade this pack to the 4.3-V level before upgrading Netcool/Proviso. However, you can install and run earlier versions of this pack if you are installing Netcool/Proviso 4.4.3 into a new environment.

Cisco CMTS Technology Pack Upgrade/Installation

If you are running a version earlier than 4.3-V of the Cisco CMTS Technology Pack and plan to upgrade to Netcool/Proviso 4.4.3, the pack will continue to function following the upgrade process, but you will not be able to upgrade the pack to the 4.3-V level. A future release of Netcool/Proviso will support the upgrade of the Cisco CMTS Technology Pack. If you are installing Netcool/Proviso 4.4.3 into a new environment and plan to install the Cisco CMTS Technology Pack, you must install and run the 4.3-V version of this pack.

Nortel CS2000 Technology Pack Upgrade/Installation

If you are running a version earlier than 4.3-T of the Nortel CS2000 Technology Pack and plan to upgrade to Netcool/Proviso 4.4.3, the pack will continue to function following the upgrade process, but you will not be able to upgrade the pack to the 4.3-T, 4.3-U, or 4.3-V level. A future release of Netcool/Proviso will support the upgrade of the Nortel CS2000 Technology Pack. If you are installing Netcool/Proviso 4.4.3 into a new environment and plan to install the Nortel CS2000 Technology Pack, you must install and run the 4.3-V version of this pack.

Cisco CWM, Cisco IP Telephony Technology Pack Installation

If you are running a version earlier than 4.3-V of the Cisco CWM or Cisco IP Telephony Technology Packs and plan to upgrade to Netcool/Proviso 4.4.3, the packs will continue to function following the upgrade process. However, you cannot install and run earlier versions of this pack if you are installing Netcool/Proviso 4.4.3 into a new environment. The Technology Pack 4.3-W release will support installing Cisco CWM and Cisco IP Telephony Technology Packs on Netcool/Proviso 4.4.3.

Technology Pack Requirements

To install Technology Packs successfully, your system must have Java Runtime Environment (JRE) 1.4.2, JVM 1.4.2_17, and several Solaris patches, including the Solaris Patch 112874-45: libc patch. See the Netcool/Proviso Configuration Recommendations for detailed information about the required patches.


Netcool/Proviso Upgrade Flags UBA Properties as Custom Properties for Installed UBA Technology Packs

In general, you do not need to perform any special actions for Technology Packs when you are upgrading your Netcool/Proviso environment. The installed packs will function at the new level of Netcool/Proviso without requiring any technology pack upgrade.

Prior to FixPack 3, if you have UBA technology packs installed in your environment, there is an issue if you choose to upgrade the pack after you have upgraded Netcool/Proviso.

Starting in 4.3-U, UBA technology packs include XML Schema Definition (XSD) files that describe and validate pack-specific properties in the Topology Editor. Unfortunately, prior to FixPack 3, when you upgrade to Netcool/Proviso 4.4.3 no XSDs are assigned to deployed UBA Collectors. The Topology Editor treats pack-specific UBA properties for deployed UBA packs as free form, custom settings. Thus, the Topology Editor cannot provide the appropriate validation of settings as it normally would during a typical pack install. For more information, see Upgrading Technology Packs in the Netcool/Proviso Upgrade Guide.

With FixPack 3, this issue has been corrected. See Topology Editor Enhancements to Simplify Upgrade of UBA Technology Packs on page 22 for more information.

Technology Packs Do Not Support Silent Install

With the exception of installing the MIB II Technology Pack in a Netcool/Proviso Minimal Deployment, technology packs do not support silent install and should be installed using the launchpad.

Installing and Configuring SNMP and UBA Technology Packs Require Different Procedures

Make sure that you read the Netcool/Proviso Installation Guide and the Netcool/Proviso Technology Pack Release Notes before you install and configure a technology pack or add any collectors in your environment. The release notes contain information on whether a specific technology pack is a UBA or SNMP pack. UBA and SNMP packs require you to perform different installation and configuration steps, as each type of pack has unique requirements.

If you do not follow the correct procedure for the type of technology pack you are installing, the installation or configuration will be unsuccessful and will generate errors.

Installation Errors Written to Log File

If an error occurs during a technology pack installation (for example, you specify the wrong SilverStream password), the error is written to the log file but is not shown in the GUI.

BCOL Collectors Require an Additional Environment Variable

If your Netcool/Proviso environment runs a BCOL collector, an issue can arise where the pollinv tool becomes locked. The pollinv tool is used to prevent multiple BCOL inventories from being run concurrently on a given profile, and if it is locked, inventory cannot take place.

To prevent this issue, you must add the PVM_INV_NOORALOCK=1 environment variable to your dataMart.env file by doing the following:

1. On the DataMart host, log in as pvuser.

2. Change your directory to the DataMart home directory (/opt/datamart, by default). For example:


$ cd /opt/datamart

3. Using the text editor of your choice, open the dataMart.env file.

4. Add the following statements anywhere between the else and fi lines of the file:

PVM_INV_NOORALOCK=1 export PVM_INV_NOORALOCK

For example:

5. When you are satisfied with your edits, write and quit the file.

Topology Editor JVM

The Topology Editor uses its own JVM to run. When you install the Topology Editor, this JVM is installed under the Topology Editor installation directory. However, when the Topology Editor extracts the configuration metadata files (XSD files) from a UBA technology pack’s jar file, it issues an external command. This external command inherits all the properties of the shell from which the Topology Editor was started.Therefore, if the Topology Editor is started by a user who has the Java path included in the PATH environment variable, the external command works correctly. Otherwise, the command will fail.

Cisco CMW/IPT Path Changes Required Following Netcool/Proviso Upgrade

If you are running a version earlier than 4.3-V of the Cisco CWM or Cisco IP Telephony Technology Packs and plan to upgrade to Netcool/Proviso 4.4.3, there is an issue where the ODBC driver can produce SQL errors that will affect inventory for these technology packs.

To work around this issue, after completing your Netcool/Proviso upgrade, do the following on each DataChannel host in your environment:

1. Open an xterm session on the DataChannel host.

2. Change your working directory to the DataChannel home directory (/opt/datachannel, by default):

cd /opt/datachannel

3. Using a text editor, open the dataChannel.env file.

3-a. On Solaris systems, search for the LD_LIBRARY_PATH environment variable.

3-b. On AIX systems, search for the LIBPATH environment variable.

4. Add the $DC_PRODUCT_HOME/license path to the LD_LIBRARY_PATH or LIBPATH environment variables. For example:

PVMEnvProductName=DataMart_1

if [ ! -z "$PV_PRODUCT" -a "$PV_PRODUCT" != "$PVMEnvProductName" ]; then

echo "Environment is already set for use by another Proviso product"

else PV_PRODUCT=$PVMEnvProductName

export PV_PRODUCT

PVM_INV_NOORALOCK=1

export PVM_INV_NOORALOCK

PVMHOME=/opt/datamart

.

.

.

fi


4-a. After adding the specified path, the LD_LIBRARY_PATH environment variable on Solaris would look something like this:

LD_LIBRARY_PATH=$DC_PRODUCT_HOME/license:$DC_PRODUCT_HOME/lib:$ORACLE_HOME/lib:$LD_LIBRARY_PATH

4-b. After adding the specified path, the LIBPATH environment variable on AIX would look something like this:

LIBPATH=$DC_PRODUCT_HOME/license:$DC_PRODUCT_HOME/lib:$ORACLE_HOME/lib:$LD_LIBRARY_PATH

5. Write and quit the dataChannel.env file.

6. Load the shell with the DataChannel environment, by sourcing the dataChannel.env file, as follows:

. /opt/datachannel/dataChannel.env

7. Stop the AMGR (Application Manager). To manually stop the AMGR, follow these steps:

7-a. Log in as pvuser on the host computer running the AMGR.

7-b. At a shell prompt run the following command:

'$ ps -edf | grep amgr | grep -v grep'

The above command returns the process ID of the AMGR process.

7-c. Stop the AMGR by killing the process ID returned in the previous step. This process ID is represented by amgr_PID in the following example:

'$ kill -9 amgr_PID'

8. Restart the AMGR. To manually restart the AMGR, follow these steps:

8-a. Log in as pvuser on the host computer running the AMGR.

8-b. At a shell prompt, change to the DataChannel bin subdirectory. For example:

$ cd /opt/datachannel/bin

8-c. Enter the following command at a shell prompt:

./amgrw

9. Bounce (restart) any UBA that runs either the Cisco CMW or Cisco IPT Technology Pack using the following command:

'$ dccmd bounce UBA.<channel_number>.<subchannel_number>’

where:

— channel_number — Replace with the channel number that was configured for this technology pack.

— subchannel_number — Replace with the subchannel (also referred to as the collector) number that was configured for this technology pack.

10. For Cisco CWM only. Bounce (restart) the CWMIF application using the following command:

'$ dccmd bounce CWMIF.<channel_number>.<subchannel_number>’

where:

— channel_number — Replace with the channel number that was configured for this technology pack.

— subchannel_number — Replace with the subchannel (also referred to as the collector) number that was configured for this technology pack.


AIX-Specific Restrictions

Unsupported Features

The following Netcool/Proviso Version 4.4.1 features are not supported on AIX systems in Version 4.4.3:

• Novell exteNd command-line interface (CLI)

The CLI (SilverCmd) is not supported if executed from DataMart systems running on AIX platforms. However, SilverCmd is supported on Version 4.4.3 when executed from the DataView system.

SilverCmd is a convenience feature that allows some actions to take place remotely from the DataView report server (which uses the exteNd application server). These features are available from the DataView server.

• Cisco Call Manager SQL Server connectivity (Data Direct Library requirement)

Future versions of the Cisco Call Manager will be based on Informix rather than the SQL Server, which will remove the need for the Data Direct Libraries to be installed on your system.

Oracle Listener Control Process

On AIX systems, the listener control (lsnrctl) process for Oracle does not start automatically because the inittab file contains the wrong path.

To correct this problem so the process starts automatically, follow these steps:

1. Using a text editor, open the /etc/inittab file.

2. Correct the path by changing /bin/lsnrctl to $ORACLE_HOME/bin/lsnrctl.

3. Save your changes and close the file.

Alternatively, log in as the oracle user and enter the following command:

lsnrctl start

Changes and New Features

This section provides an overview of the new features included in Netcool/Proviso 4.4.3, and is organized as follows:

• Netcool/Proviso Common Installer on page 16

• SNMP Bandwidth Control and Collection Smoothing on page 18

• Features Available in the FixPack 1 Release of Netcool/Proviso 4.4.3 on page 18



• Other Changes/New Features on page 22

Note: Features made available in the FixPack 1 and FixPack 2 releases of Netcool/Proviso 4.4.3 will also be available in the FixPack 3 release of Netcool/Proviso 4.4.3.


Netcool/Proviso Common Installer

The Netcool/Proviso Common Installer is a new component that was introduced to provide a cohesive and easy to use installation and configuration tool that improves consumability for both new and existing Netcool/Proviso customers.

The Common Installer provides GUI-based functionality that orchestrates and simplifies the installation, configuration, and upgrade of your Netcool/Proviso environment. The Common Installer consists of the launchpad, Topology Editor, and Deployer:

• Launchpad - The launchpad is a browser-based front end that provides you with a selected list of options to simplify installation-related tasks. It serves as a convenient, centralized starting point for installation, configuration, maintenance, and upgrade tasks, and also provides access to the Netcool/Proviso documentation suite.

• Topology Editor - The Topology Editor is a graphical user interface that allows you to define, install, configure, upgrade, or remove objects in your Netcool/Proviso environment. Only one Topology Editor exists in a Netcool/Proviso environment, and it typically resides on the DataMart host.

The Topology Editor provides a set of views that are used to describe the physical and logical topology of your Netcool/Proviso environment. For each host or component, the configuration parameters associated with a selected object are displayed in the accompanying table views. This functionality allows for a centralized and simplified configuration process for installing or making changes to your topology.

In contrast to earlier versions of Netcool/Proviso, most configuration is performed in the Topology Editor before the actual components are installed or changed. Previously, components were configured following installation using a series of component-specific .cfg files that were manually edited. The parameters in those files are now displayed and changed within the Topology Editor.

Once a topology is saved, the Topology Editor creates an XML file that is used by the Deployer to perform the actions defined within the topology against your hosts or Netcool/Proviso components.

• Deployer - The Deployer is a graphical user interface that provides product installation, upgrade, and maintenance capability. You can have several deployers in your environment: a primary deployer that resides with the Topology Editor and is always run first; and secondary deployers that reside on remote hosts and are used to install remote components locally.

For each topology XML file, the Deployer determines the sequence of steps that are required to properly install or change the Netcool/Proviso components. When a topology is deployed, the native installers of the Netcool/Proviso components are called silently and additional configuration is driven automatically with scripts. The Deployer validates each action taken and returns the results of each step in its display. If a step is unsuccessful, error information is supplied so that you can easily find, view, and change the affected parameters before attempting to run the step again.

Installing Netcool/Proviso

Netcool/Proviso 4.4.3 provides the capability to perform either a minimal deployment installation, or a distributed deployment installation.

Minimal Deployment Installation

A minimal deployment installation is used primarily for demonstration or evaluation purposes, and installs Netcool/Proviso on the smallest number of machines possible, with minimal user input. This installation type installs all the Netcool/Proviso components using a predefined topology file to define the infrastructure, and also installs the MIB-II SNMP Technology Pack.

To summarize a minimal deployment installation:

• Install an Oracle Server and Oracle Clients on each system that will host a Netcool/Proviso component.

• Use the launchpad to start the installation using the Minimal Deployment selection.


• Run the post-installation script.

• Configure the MIB-II Technology Pack.

Distributed Deployment Installation

A distributed deployment installation deploys Netcool/Proviso in a typical customer environment where there are multiple hosts for Netcool/Proviso components.

To summarize a distributed deployment installation:

• Install an Oracle Server and Oracle Clients on each system that will host a Netcool/Proviso component.

• Use the launchpad to install the Topology Editor.

• Use the Topology Editor to create the topology for your Netcool/Proviso component:

— Define the hosts that will be used in your environment in the Topology Editor’s Physical View.

— Configure the DataBase, DataMart, DataLoad collectors, DataChannel, and DataView components in the Topology Editor’s Logical View.

• Run the Deployer to install the components according to your topology.

• Install technology packs.

• Configure technology packs.

Installing Technology Packs

With Netcool/Proviso 4.4.3, there is now a separate installer, called the Technology Pack Installer, that is required to install both stand-alone and bundled technology packs. The Technology Pack Installer automates many of the manual tasks that were previously required to install a technology pack, such as performing confReload, stylesheet installation, localization enablization, and the deployment of formulas.

SNMP Technology Packs

To summarize an SNMP technology pack installation:

• Use the launchpad to start the installation using the Technology Pack Installer.

• Configure the technology pack according to the instructions provided in its Technology Pack User’s Guide.

UBA Technology Packs

To summarize a UBA technology pack installation:

• Use the launchpad to start the installation using the Technology Pack Installer.

• Use the Topology Editor to load the technology pack’s XSD information to the Database. Each UBA technology pack ships with an XSD file that defines the default values that need to be used in the configuration of the technology pack.

• Use the Topology Editor to add and configure a UBA collector in your topology (this replaces the configuration that used to be performed in the dc.cfg file).

• Run the Deployer to update your topology with the new UBA collector.

• Configure the technology pack according to the instructions provided in its Technology Pack User’s Guide.


Making Changes to Your Topology

While the Common Installer requires some up-front planning to determine how you want to create your Netcool/Proviso environment, it also simplifies updating the topology as it allows hosts and components to be added, moved, or removed as your Netcool/Proviso environment evolves.

Should you need to make changes, the Common Installer eases the planning and visualization of your Netcool/Proviso environment. By loading the deployed topology from your Database, the Topology Editor displays all components and parameters as they exist in your current environment, including installed technology packs. To make changes, simply add, move, or remove hosts or components, or change the configuration parameters in the Topology Editor, then run the Deployer to propagate the updated topology.

SNMP Bandwidth Control and Collection Smoothing

The Bandwidth Control and Collection Smoothing features are used to optimize the performance of SNMP collectors in your Netcool/Proviso environment.

SNMP Bandwidth Control is used to prevent SNMP collectors from consuming excessive bandwidth during periods of heavy network activity. The SNMP bandwidth control feature defines a bandwidth limitation that allows you to maximize the performance of the collectors without requiring an overly cautious approach to collection management.

Collection Smoothing is used to prevent spikes in collector activity that occur at the beginning of the polling period. Typically, the collector attempts to execute as many collection requests as it can in the shortest time possible, which leads to a pattern of a brief period of intense activity followed by an extended period of sparse collection activity.

Features Available in the FixPack 1 Release of Netcool/Proviso 4.4.3

The following sections describe features first made available in the FixPack 1 release of Netcool/Proviso 4.4.3:

• Upgrade Support from Netcool/Proviso 4.4.1 or 4.4.2 on page 18

• Supported Upgrade Paths on page 19

• Netcool/Proviso High Availability Manager on page 19

• DataView Uses Oracle Client Version 9.2.0.6 on page 19

Note: Features made available in the FixPack 1 release of Netcool/Proviso 4.4.3 will also be available in the FixPack 2 and FixPack 3 releases of Netcool/Proviso 4.4.3.

Upgrade Support from Netcool/Proviso 4.4.1 or 4.4.2

This feature is available in the FixPack 1 release of Netcool/Proviso 4.4.3.

This release of Netcool/Proviso introduces functionality that allows you to upgrade your existing Netcool/Proviso environment to Netcool/Proviso 4.4.3. New upgrade functionality has been added to the launchpad, Topology Editor, and deployer to help you gather configuration information, prepare, and deploy an upgrade topology that will bring your environment to the 4.4.3 level.

For more information, see the Netcool/Proviso Upgrade Guide.


Supported Upgrade Paths

The tools and procedures described in the Netcool/Proviso Upgrade Guide are intended to support a limited number of upgrade paths to Netcool/Proviso 4.4.3. To find version information for the Netcool/Proviso components installed in your environment, use the Netcool/Proviso Info Tool as described in the Netcool/Proviso Tools for Version Reporting Technical Note.

Consult the table below to determine what you need to do for your environment:

Netcool/Proviso High Availability Manager


The High Availability Manager (HAM) in Netcool/Proviso 4.4.3 is an optional component for large installations that want to use redundant SNMP collection paths. The HAM constantly monitors the availability of one or more SNMP collection hosts, and switches collection to a backup host (called a spare) if a primary host becomes unavailable. If a primary host becomes unavailable, it is detected by the HAM, so it dynamically unbinds the collection path from the primary host and binds it to the spare.

DataView Uses Oracle Client Version 9.2.0.6


Oracle Client version 9.2.0.6 must be used by any DataView component running on a host, while the other Netcool/Proviso components use Oracle Client version 9.2.0.8. To ensure that this Oracle client version is distinct from other Oracle versions or patches, it is recommended that you install the Oracle 9.2.0.6 patch into a separate directory in your Oracle environment (for example, /opt/oracle/product/9.2.0.6).

When configuring the DataView component, you must ensure that the Oracle home property in your topology points to the correct location (/opt/oracle/product/9.2.0.6, by default) for your Oracle Client version 9.2.0.6 distribution.

If the DataView component shares a host with another Netcool/Proviso component, DataView will use Oracle Client version 9.2.0.6, while the other component will use Oracle Client version 9.2.0.8.

Netcool/Proviso Version Supported Upgrade Path

Netcool/Proviso 4.4.1 MR1 or earlier

If you are running Netcool/Proviso 4.4.1 MR1 or earlier, you must first upgrade your environment to at least Netcool/Proviso 4.4.1 FixPack 1 before upgrading to Netcool/Proviso 4.4.3.

To upgrade to at least Netcool/Proviso 4.4.1 FixPack 1 from your current release, please contact Professional Services for more information.

Netcool/Proviso 4.4.1 FixPack 1 or later

If you are running Netcool/Proviso 4.4.1 FixPack 1 or later, you can upgrade directly to Netcool/Proviso 4.4.3.

Netcool/Proviso 4.4.2 If you are running Netcool/Proviso 4.4.2, you can upgrade directly to Netcool/Proviso 4.4.3.

Netcool/Proviso 4.4.3 If you are running Netcool/Proviso 4.4.3 and wish to apply a FixPack to that release, you must refer to the FixPack README and the Netcool/Proviso Installation Guide for instructions.

Netcool/Proviso technology packs

You do not have to upgrade your technology packs in order to upgrade to Netcool/Proviso 4.4.3. If you are running the Netcool/Proviso Alcatel 5620 SAM Technology Pack and/or the Netflow IPFIX Technology Pack, you must refer to the chapter that discusses how to upgrade technology packs in the Netcool/Proviso Upgrade Guide for more information.


Important: It is recommended that you use the same tnsnames.ora and sqlnet.ora files for both your Oracle Client 9.2.0.6 and Oracle Client 9.2.0.8 environments.

For more information on configuring DataView to use the correct version of Oracle, see the Installing the Oracle Client section of the Netcool/Proviso Installation Guide.


The following section describes a feature first made available in the FixPack 2 release of Netcool/Proviso 4.4.3:

• Matrix Tables on page 20

Matrix Tables


Note: Features made available in the FixPack 2 release of Netcool/Proviso 4.4.3 will also be available in the FixPack 3 release of Netcool/Proviso 4.4.3.

The Matrix table is an overview report that shows data on both directions in a set of bi-directional paths. It is frequently used to monitor a fully meshed set of sites by depicting site-to-site metrics.

In a Matrix table:

• The row labels show the sources and the column labels show the destinations of end-to-end paths or any resource-supporting From and To-type attributes (for example, Cisco IP SLA probes), and modeled as Sub-Elements (SEs).

• Each cell shows a metric value, the state of a threshold or both. Metric values can be either historic values from the database or the last value collected, that is, Near Real Time (NRT) as reported by the DataChannel.

• It is possible to drilldown from a cell to a report, typically a single time series report.

See the Netcool/Proviso DataView User’s Guide for more information on Matrix tables.


The following sections describe features first made available in the FixPack 3 release of Netcool/Proviso 4.4.3:

• Oracle10g Support (Upgrade Only) on page 20

• Red Hat Enterprise Linux 5 Support For SNMP DataLoad Collectors on page 21

• Topology Editor Enhancements to Simplify Upgrade of UBA Technology Packs on page 22

Note: Features made available in the FixPack 3 release of Netcool/Proviso 4.4.3 are NOT available in the FixPack 1 and FixPack 2 releases of Netcool/Proviso 4.4.3.

Oracle10g Support (Upgrade Only)

The ability to upgrade your Proviso database to the Oracle10g database (hereinafter referred to as Oracle10g) is available in the FixPack 3 release of Netcool/Proviso 4.4.3, with the following caveats:

• Oracle10g is not supported directly on new 4.4.3 installations.

• You must be running Solaris 10 before upgrading to Oracle10g.


• You must first install the FixPack 3 release of Netcool/Proviso 4.4.3 before upgrading to Oracle10g.

• You must refer to the Upgrade from 9i to 10g ReadMe that is distributed with the FixPack 3 release of Netcool/Proviso 4.4.3. This document references the Oracle documents and Oracle tools that you will need to successfully upgrade to Oracle10g.

• DataView continues to be supported on Oracle 9.2.06. See DataView Uses Oracle Client Version 9.2.0.6 on page 19 for more information.

Important: You must NOT upgrade the DataView server to Oracle10g. The Oracle 9.2.0.6 client that Silverstream uses on the DataView server will continue to work with Oracle10g.

Important: You should expect that Oracle intends to end Extended Support for Oracle 9.2 in July 2010, and it is strongly recommended that you upgrade to Oracle10g.

The environments identified in Table 1 are the only combinations of operating system and Oracle database that are supported for upgrade to Oracle10g. The only supported Oracle10g patch set is Oracle 10.2.0.4. As Table 1 shows, there is no way to install Oracle10g directly. You can install Oracle10g only as an upgrade from an installed instance of Oracle9i.

You should refer to the Upgrade from 9i to 10g ReadMe that is distributed with Netcool/Proviso FixPack 3. This ReadMe provides information you need to upgrade your Proviso database to the Oracle10g database.

Red Hat Enterprise Linux 5 Support For SNMP DataLoad Collectors

The FixPack 3 release of Netcool/Proviso 4.4.3 supports DataLoad SNMP collectors on Linux hosts running 64-bit Red Hat Enterprise Linux Version 5 with Oracle10g.

Note: Red Hat Enterprise Linux 5 requires the Oracle10g client.

The FixPack 3 release of Netcool/Proviso 4.4.3 continues to support DataLoad collectors on Linux hosts running 32-bit Red Hat Enterprise Linux Version 4, Update 5 with Oracle9i.

There is no simple upgrade from a host running 32-bit Red Hat Enterprise Linux Version 4, Update 5 with Oracle9i and DataLoad SNMP collectors to 64-bit Red Hat Enterprise Linux Version 5 with Oracle10g and SNMP DataLoad collectors.

The recommended upgrade procedure is to perform the following installations on the host currently running 32-bit Red Hat Enterprise Linux Version 4, Update 5 with Oracle9i and DataLoad SNMP collectors:

• A full installation of 64-bit Red Hat Enterprise Linux Version 5

• An install of the Oracle10g client

• A reinstall of Netcool/Proviso SNMP DataLoad

Table 1: Valid Upgrade Paths to Oracle10g

You Are Currently Running This Netcool/Proviso Version

You Are Currently Running This Operating System/Oracle Database

You Can Upgrade to This Operating System/Oracle Database

Netcool/Proviso 4.4.3 (with FixPack 3 installed)

Solaris9/Oracle9i Solaris 10/Oracle10g


Solaris 10/Oracle9i Solaris 10/Oracle10g


AIX5.3/Oracle9i AIX5.3/Oracle10g


Topology Editor Enhancements to Simplify Upgrade of UBA Technology Packs

This feature is available in the FixPack 3 release of Netcool/Proviso 4.4.3. This feature simplifies the upgrade of UBA technology packs by adding a Technology Pack XSD Upgrade Wizard to the Topology Editor. Prior to the FixPack 3 release of Netcool/Proviso 4.4.3, when you upgraded to Netcool/Proviso 4.4.3 from a previous version of Netcool/Proviso no XSDs were assigned to deployed UBA collectors. In this case, the Topology Editor treated pack-specific UBA properties for deployed UBA packs as free form, custom settings. Thus, the Topology Editor could not provide the appropriate validation of settings as it normally would during a typical pack install.

Because the Technology Pack XSD Upgrade Wizard is included as part of the Topology Editor, there is no need to invoke a separate utility. You simply invoke (start) the Topology Editor as described in the 4.4.3 Netcool/Proviso Installation Guide. The Technology Pack XSD Upgrade Wizard is automatically invoked when you right-click the appropriate folder and select the appropriate item from the pop-up menu, as described in the Netcool/Proviso Upgrade Guide.

The Topology Editor displays most UBA pack-specific properties with Green check mark icons, indicating that the property values are valid. The wizard obtains these values from the corresponding UBA pack-specific parameters specified in the dc.cfg file. (Remember that on pre-4.4.3 systems you edit UBA pack-specific parameters in the pack’s template file and then copy them to the dc.cfg file.) You have the option to verify and/or change these values.

See the Netcool/Proviso Upgrade Guide for more information on how to upgrade technology packs and when to use the Technology Pack XSD Upgrade Wizard.

Other Changes/New Features

The Netcool/Proviso Version 4.4.3 release contains the following enhancements:

• Platform support for 32-bit Red Hat Enterprise Linux Version 4, Update 5 with Oracle9i for the SNMP DataLoad Collector.

• Platform support for 64-bit Red Hat Enterprise Linux Version 5 with Oracle10g for the SNMP DataLoad Collector.

• Platform support for Solaris 10.

• Support for Veritas Cluster 5.x on Solaris 9 and Solaris 10.

• The name of the DataChannel version utility was changed to showVersion. In addition, the utility’s output has been changed to be consistent with the showVersion output for DataMart and DataLoad.

• Support for using a separate user ID for each of the Netcool/Proviso 4.4.3 components.

• Support for DataChannel Remote has been added. “DataChannel Remote” is a phrase used to describe a particular configuration where the CME resides on a separate host from its LDR (usually on the same host as its collector). In such configurations, the FTE sits between the CME and the LDR to move files from the remote host (normally, the FTE sits between the collector and CME).

The following features are not supported in Version 4.4.3:

• The pre-4.3-W Cisco IP Telephony and Cisco CWM Technology Packs

Problems Resolved in this Release

Table 2 lists the major problems that were resolved in Netcool/Proviso 4.4.3.


Table 2: Resolved Problems

APAR Number Description

IY09660 FTE continually crashes with: Message not understood

IY15146 BOFDUMP does not load patches from DataChannel state

IY97316 SNMP, ambiguities in string format - formula not working

IY99375 No NRAW report from purgeable partition on the boundary date

IZ04269 DataLoad resources are not being created for monitoring

IZ04663 Data are displayed on the report for daily/weekly granularities

IZ05452 Inventory NOC-REPORTGROUPING not working in FP001

IZ05838 Group with inactive interfaces outside of NOC reporting tree

IZ07911 UBA fails to create output files with ASMM pack in new version

IZ08517 Cannot see the modification in the reports for ratio charts

IZ08746 BOFDUMP after FP0001 upgrade cannot read SRAW files

IZ09660 FTE continuously crashes

IZ09767 Request Editor is not working property

IZ10026 UBA limitation

IZ10889 Collector calculates a wrong bandwidth limit regardless of the collection

IZ11472 Synchro fails when there’s no “sysname” property populated

IZ12677 DataLoad filesystem quota values from dl.cfg

IZ12953 Unable to set folder comments

IZ13798 Limit of 1000 application instances interfering with services script

IZ14229 Customer sees two “No data available” messages on the GRA

IZ14241 After regrouping, database doesn’t remove historical links

IZ15992 Timeseries table shows duplicated entries under monthly

IZ16469 Sticky requests

IZ17065 Can’t pass list of IPs to inventory with -SUBPROFILE option

IZ18717 Need fix for potential locking issue when two inventories are run

IZ18717 Inventory locking mechanism doesn’t always work

IZ19341 Duplicate rows in the SE_GRP_DESC_HIST table

IZ19342 New inventory return code

IZ15519 FP0003 install requires default SilverStream password setting


Netcool/Proviso Documentation

Netcool/Proviso documentation consists of the following:

• release notes

• configuration recommendations

• user guides

• technical notes

• online help

The documentation is available for viewing and downloading on the infocenter at: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_proviso.doc/welcome.htm

Note that Acrobat Reader requires GTK+ 2.2.2 or higher, and all its dependent packages. See the Netcool/Proviso Configuration Recommendations for detailed information.

DataMart Documentation Error

The Specifying SNMP Community Names section of the DataMart online help contains erroneous DES encryption information. For the correct information, please refer to the DataMart Configuration Guide available from the Tivoli Netcool/Proviso InfoCenter, which can be found at the following location:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_proviso.doc/welcome.htm


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_proviso.doc/welcome.htm

Appendix A: Expanded Versioning Information

Overview

This appendix lists the expanded versioning information for Netcool/Proviso Version 4.4.3, that can be obtained by running the following command for each component (DB, DC, DL, DM, DV, TOOLS) specified by the component parameter:

$PVMHOME/bin/dbMgr versionRptByProvisoApp E component

You can also run the following command, which writes all the version information for all components into a file on the database server in the $ORACLE_BASE/admin/PV/udump directory:

$PVMHOME/bin/dbMgr versionSupportLevelDump

For more information, see the Netcool/Proviso dbMgr Reference Guide.

Note: To obtain the expanded versioning information associated with the Netcool/Proviso DataChannel tools, you must invoke (start) them so that they register with the database. The example in this appendix shows the expanded version information associated with the bofDump utility. The expanded version information for bofDump is available only after it is invoked.

Netcool/Proviso Version 4.4.3 Versioning Information

----------------------------------------------

result : 0

Application: DB

Component Version Build

Registration Date

--------------------------------------------------------------------------

Database 4.4.3.3 R2E2 20081128

2009.06.22 12:22:27

----------------------------------------------

result : 0

Application: DC


Registration Date



-------------------------------------------------------------------------------

AMGR.TIGERK3 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

AMGR.TIGERK2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

AMGRW.TIGERK3 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

AMGRW.TIGERK2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

CME.2.100 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

CME.2.2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

CME.1.1 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

CMGR.TIGERK2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

CMGRW.TIGERK2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

CNSW.TIGERK2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

DISC.TIGERK2.1 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

DLDR.2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

DLDR.1 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

FTE.1.1 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

FTE.2.100 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

FTE.2.2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

LDR.2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

LDR.1 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

LOG.TIGERK2 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

LOGW.TIGERK2 4.4.3.3-324 Ginger.324



2009.06.22 12:55:26

UBA.2.100 4.4.3.3-324 Ginger.324

2009.06.22 12:55:26

----------------------------------------------

result : 0

Application: DL


Registration Date

--------------------------------------------------------------------------------

SNMP.2.2 4.4.3.3.8 App Ginger.324;

Lib Ginger.1052009.06.22 12:32:06

SNMP.1.1 4.4.3.3.8 App Ginger.324;

Lib Ginger.1052009.06.22 12:25:00

----------------------------------------------

result : 0

Application: DM


Registration Date

--------------------------------------------------------------------------------

PVM.tigerk2 4.4.3.3 R1E0 20090514

2009.06.22 13:00:04

----------------------------------------------

result : 0

Application: DV


Registration Date

--------------------------------------------------------------------------------

-----------------------------------

DataView.tigerk3.usma.ibm.com:8080 4.4.3.3 4433R0E2

2009.06.22 12:44:53



exteNd Application Server.tigerk3.usma.ibm.com:8084.0.0k 020918_1

2009.06.19 18:44:07

----------------------------------------------

result : 0

Application: TOOLS


Registration Date

--------------------------------------------------------------------------------

-----------------------------------

BOFDUMP.TIGERK2.USMA.IBM.COM 4.4.3.3-324 Ginger.324

2009.06.22 20:35:51

----------------------------------------------


Tivoli Netcool®/Proviso® 4.4.3 IBM · PDF fileQuestions on the capabilities of non-IBM...

Documents

Transcript of Tivoli Netcool®/Proviso® 4.4.3 IBM · PDF fileQuestions on the capabilities of non-IBM...