with IBM Corp. · Upgrading Huawei U2000 DSLAM T echnology Pack ..... . 45 Notices ... The T ivoli Netcool Performance Manager technology pack distribution is available

IBM Tivoli Netcool Performance ManagerWireline ComponentJune 2017Document Revision R2E1

Pack Upgrade Guide

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 49.

© Copyright IBM Corporation 1997, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Overview . . . . . . . . . . . . . . vAudience . . . . . . . . . . . . . . . vOrganization . . . . . . . . . . . . . . vTivoli Netcool Performance Manager - WirelineComponent. . . . . . . . . . . . . . . vTivoli Netcool Performance Manager documentation vi

Chapter 1. Introduction . . . . . . . . 1Before you begin the upgrade . . . . . . . . 1Supported upgrade paths for Tivoli NetcoolPerformance Manager technology packs . . . . . 1Installing prerequisite software . . . . . . . . 2Tivoli Netcool Performance Manager technology packdistribution . . . . . . . . . . . . . . . 2

Chapter 2. Upgrading technology packson Tivoli Netcool/Proviso 4.4.3 fix pack1 or pre-fix pack 3 . . . . . . . . . . 3Overview . . . . . . . . . . . . . . . 3Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3and technology packs . . . . . . . . . . . 3Upgrade scenario for Tivoli Netcool/Proviso 4.4.3and Alcatel-Lucent 5620 SAM. . . . . . . . . 4

Upgrading the Alcatel-Lucent 5620 SAMTechnology Pack . . . . . . . . . . . . 5

Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3and Netflow IPFIX . . . . . . . . . . . . 6

Upgrading the Netflow IPFIX Technology Pack . . 7Documents you need for technology pack upgrade 8

Current limitations with Tivoli Netcool/Proviso 4.4.3fix pack 1 and pre-fix pack 3. . . . . . . . . 11

Limitations with how the Topology Editor treatsUBA pack-specific parameters . . . . . . . 11Limitations with UBA pack-specific parameterkey/value pairs . . . . . . . . . . . . 12

Before you begin a technology pack upgrade . . . 13Standard procedure for upgrading technology packs(Except Alcatel-Lucent 5620 SAM and NetflowIPFIX) . . . . . . . . . . . . . . . . 14

Upgrade scenario 1 (SNMP and UBA technologypacks) . . . . . . . . . . . . . . . 14Upgrade scenario 2 (UBA packs only) . . . . 16

Chapter 3. Upgrading technology packson Tivoli Netcool/Proviso 4.4.3 fix pack3 or Tivoli Netcool PerformanceManager . . . . . . . . . . . . . . 19Overview . . . . . . . . . . . . . . . 19

Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3and Tivoli Netcool Performance Managertechnology packs . . . . . . . . . . . . 20Upgrade scenario for Tivoli Netcool/Proviso 4.4.3and Alcatel-Lucent 5620 SAM . . . . . . . . 21

Upgrading the Alcatel-Lucent 5620 SAMTechnology Pack. . . . . . . . . . . . 22

Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3or Tivoli Netcool Performance Manager andNetflow IPFIX . . . . . . . . . . . . . 22

Upgrading the Netflow IPFIX Technology Pack 23Netflow IPFIX upgrade scenario 1 . . . . . . 24Netflow IPFIX upgrade scenario 2 . . . . . . 25

Documents you need to perform a technology packupgrade . . . . . . . . . . . . . . . 25

Essential information in the pack installation andconfiguration guide. . . . . . . . . . . 28Essential information in pack release notes . . . 29Essential Information in the Installation Guide. . 29Essential information in the TivoliNetcool/Proviso fix pack 3 or Tivoli NetcoolPerformance Manager ReadMe . . . . . . . 30

Topology Editor and UBA pack-specific properties 30Technology pack XSD upgrade wizard . . . . 31Limitations with UBA pack-specific parameterkey/value pairs . . . . . . . . . . . . 32

Before you begin a technology pack upgrade . . . 33Before you begin upgrade scenario 2 (UBA packsonly) . . . . . . . . . . . . . . . 34

Standard procedure for upgrading technology packs 36Upgrade scenario 1 (SNMP and UBA technologypacks) (except Alcatel-Lucent 5620 SAM, NetflowIPFIX) . . . . . . . . . . . . . . . 36Upgrade scenario 2 (UBA packs only) (IncludingAlcatel-Lucent 5620 SAM, Netflow IPFIX) . . . 41Upgrading to Alcatel-Lucent 5620 SAM LogToFile2.5.0.0 . . . . . . . . . . . . . . . 43Upgrading Alcatel-Lucent 5670 RAM . . . . . 44Upgrading Huawei U2000 DSLAM TechnologyPack . . . . . . . . . . . . . . . . 45

Notices . . . . . . . . . . . . . . 49Terms and conditions for product documentation. . 51Trademarks . . . . . . . . . . . . . . 52Additional copyright notices. . . . . . . . . 53

© Copyright IBM Corp. 1997, 2017 iii

iv IBM Tivoli Netcool Performance Manager: Pack Upgrade Guide

Overview

The purpose of this guide is to help upgrade your IBM® Tivoli® Netcool®

Performance Manager technology packs and common packs.

AudienceThe audience for this manual is the network administrator or operations specialistresponsible for installing the Tivoli Netcool Performance Manager product suite onan enterprise network.

To install Tivoli Netcool Performance Manager technology packs successfully, youshould have a thorough understanding of the following subjects:v Basic principles of TCP/IP networks and network managementv SNMP conceptsv Administration of the Solaris or AIX operating environmentv Administration of the Oracle database management systemv Tivoli Netcool Performance Managerv Upgrade scenarios associated with Tivoli Netcool Performance Manager

OrganizationThis guide is organized as follows:v Chapter 1, “Introduction,” on page 1v Chapter 2, “Upgrading technology packs on Tivoli Netcool/Proviso 4.4.3 fix pack

1 or pre-fix pack 3,” on page 3v Chapter 3, “Upgrading technology packs on Tivoli Netcool/Proviso 4.4.3 fix pack

3 or Tivoli Netcool Performance Manager,” on page 19

Tivoli Netcool Performance Manager - Wireline ComponentIBM Tivoli Netcool Performance Manager consists of a wireline component(formerly Netcool/Proviso) and a wireless component (formerly Tivoli NetcoolPerformance Manager for Wireless).

Tivoli Netcool Performance Manager - Wireline Component consists of thefollowing subcomponents:v DataMart is a set of management, configuration, and troubleshooting GUIs. The

Tivoli Netcool Performance Manager System Administrator uses the GUIs todefine policies and configuration, and to verify and troubleshoot operations.

v DataLoad provides flexible, distributed data collection and data import of SNMPand non-SNMP data to a centralized database.

v DataChannel aggregates the data collected through Tivoli Netcool PerformanceManager DataLoad for use by the Tivoli Netcool Performance ManagerDataView reporting functions. It also processes online calculations and detectsreal-time threshold violations.

v DataView is a reliable application server for on-demand, web-based networkreports.

© Copyright IBM Corp. 1997, 2017 v

v Technology Packs extend the Tivoli Netcool Performance Manager system withservice-ready reports for network operations, business development, andcustomer viewing.

The following figure shows the different Tivoli Netcool Performance Managermodules.

Tivoli Netcool Performance Manager documentation consists of the following:v Release notesv Configuration recommendationsv Installation and upgrade informationv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the informationcenter at http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/tnpm_1.4_kc_welcome.html?lang=en.

Tivoli Netcool Performance Manager documentationIBM provides the following Tivoli Netcool Performance Manager documentation:v Release notesv Configuration recommendationsv Referencesv Technology pack upgrade guidev Installation guidev Technical notesv Online help

vi IBM Tivoli Netcool Performance Manager: Pack Upgrade Guide

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/tnpm_1.4_kc_welcome.html?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/tnpm_1.4_kc_welcome.html?lang=en

Chapter 1. Introduction

Provides information concerning requirements and considerations that must besatisfied before you upgrade your Tivoli Netcool Performance Manager technologypacks.

Before you begin the upgradeThis guide assumes that you have a fully functioning Tivoli Netcool PerformanceManager environment.

To upgrade your environment to Tivoli Netcool/Proviso 4.4.3 fix pack 3 or TivoliNetcool Performance Manager version 1.3.0 or above, you must do the followingtasks:v Verify that your environment is running the supported versions of both the

prerequisite software and Tivoli Netcool/Proviso 4.4.3 or Tivoli NetcoolPerformance Manager 1.3.1. For more information, see Supported upgrade pathsforTivoli Netcool Performance Manager technology packs.

v Download the Tivoli Netcool Performance Manager technology pack distributionto disk. For more information, see Downloading the Tivoli Netcool PerformanceManager distribution to disk in Upgrading Tivoli Netcool Performance Manager -Wireline Component that relates to your version of Tivoli Netcool PerformanceManager.

v Shut down Tivoli Netcool Performance Manager. For more information, seeShutting down the Tivoli Netcool Performance Manager components in UpgradingTivoli Netcool Performance Manager - Wireline Component that relates to yourversion of Tivoli Netcool Performance Manager.

v Create and prepare the upgrade topology for deployment in your environment.For more information, see Preparing the upgrade topology for deployment inUpgrading Tivoli Netcool Performance Manager - Wireline Component that relates toyour version of Tivoli Netcool Performance Manager.

v Start Tivoli Netcool Performance Manager. For more information, see Starting upthe Tivoli Netcool Performance Manager components in Upgrading Tivoli NetcoolPerformance Manager - Wireline Component that relates to your version of TivoliNetcool Performance Manager.

Supported upgrade paths for Tivoli Netcool Performance Managertechnology packs

See the IBM Tivoli Netcool Performance Manager: Pack Release Notes to determine theversion from which a technology pack is upgradeable. For example, the IBM TivoliNetcool Performance Manager: Pack Release Notes might specify that your technologypack is upgradeable from Tivoli Netcool/Proviso version 4.3-U or later.

© Copyright IBM Corp. 1997, 2017 1

Installing prerequisite softwareAbout this task

Before upgrading your Tivoli Netcool Performance Manager environment and thenupgrading the technology pack, you must install the prerequisite software listed inthe Configuration Recommendations.

Tivoli Netcool Performance Manager technology pack distributionThe Tivoli Netcool Performance Manager technology pack distribution is availableas a DVD/CD and as an electronic image. The instructions in this guide assumethat you are installing from an electronic image.

If you install the product from an electronic image, be sure to keep a copy of thedistribution image in a well-known directory, because you will need this image inthe future to make changes to the environment.

2 IBM Tivoli Netcool Performance Manager: Pack Upgrade Guide

Chapter 2. Upgrading technology packs on TivoliNetcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3

Describes how to upgrade Tivoli Netcool/Proviso technology packs after youupgrade your system to Tivoli Netcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3.

About this task

If you have upgraded your Tivoli Netcool/Proviso 4.4.3 system to TivoliNetcool/Proviso fix pack 3 or Tivoli Netcool Performance Manager, you mustfollow the upgrade instructions described in Chapter 3, “Upgrading technologypacks on Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool PerformanceManager,” on page 19.

What to do next

Important: IBM does not support Tivoli Netcool/Proviso pre-v4.3.3 from 1.3-Erelease onwards. It is recommended that you upgrade to Tivoli Netcool/Proviso4.4.3 fix pack 3 or Tivoli Netcool Performance Manager.

OverviewThis chapter explains how to upgrade technology packs after you upgrade yourTivoli Netcool Performance Manager system.

Specifically, this chapter provides instructions on how to upgrade technology packsaccording to several upgrade scenarios. For UBA technology packs, this chapteralso provides:v Information about what to expect with regards to UBA pack-specific property

settings for deployed packs when upgrading to Tivoli Netcool/Proviso 4.4.3pre-fix pack 3.

v Guidelines for verifying UBA technology pack-specific properties whenupgrading a UBA technology pack after upgrading to Tivoli Netcool/Proviso4.4.3 pre-fix pack 3.

v Specific upgrade scenarios for the Alcatel-Lucent 5620 SAM Technology Packand the Netflow IPFIX Technology Pack.

Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3 and technologypacks

This section provides information you need to upgrade technology packs so thatthey operate correctly on a Tivoli Netcool/Proviso 4.4.3 system.

Table 1 on page 4 identifies the upgrade scenarios for Tivoli Netcool/Proviso 4.4.3and technology packs.


Table 1. Tivoli Netcool/Proviso and technology pack upgrade scenarios

Upgrade scenarioUpgrade scenario

description Upgrade scenario steps

Upgrade scenario 1 (SNMPand UBA packs)

Tivoli Netcool/ProvisoupgradeYou are currently runningTivoli Netcool/Proviso 4.4.1MR1 or earlier, 4.4.1 fix pack1 or later, or 4.4.2. You wantto upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 1 or pre-fix pack 3.Technology pack upgradeYou want to upgradecurrently deployedtechnology packs to 4.3-U orlater.

Perform the following steps:

1. Upgrade TivoliNetcool/Proviso 4.4.3 fixpack 1 or pre-fix pack 3.

2. See “Documents youneed for technology packupgrade” on page 8 forthe documents you needto perform this upgradescenario.

3. See “Upgrade scenario 1(SNMP and UBAtechnology packs)” onpage 14 for details aboutthis upgrade scenario.

Upgrade scenario 2 (UBApacks only)

Tivoli Netcool/Proviso fixpack updateYou are currently runningTivoli Netcool/Proviso 4.4.3.You want to update to fixpack 1 or pre-fix pack 3.Technology pack upgradeYou want to upgradecurrently deployed 4.3-UUBA technology packs to4.3-V or later.


1. Upgrade TivoliNetcool/Proviso 4.4.3 tofix pack 1 or pre-fix pack3


3. See “Upgrade scenario 2(UBA packs only)” onpage 16 for details.

Upgrade scenario for Tivoli Netcool/Proviso 4.4.3 and Alcatel-Lucent5620 SAM

This section provides information you need to upgrade the Alcatel-Lucent 5620SAM Technology Pack so that it operates correctly on a Tivoli Netcool/Proviso4.4.3 fix pack 1 or pre-fix pack 3 system.

Important: Design changes in Tivoli Netcool/Proviso 4.4.3 require you to upgradeAlcatel-Lucent 5620 SAM before upgrading to Tivoli Netcool/Proviso 4.4.3 fix pack1 or pre-fix pack 3. Otherwise, this pack stops working.

Table 2 on page 5 identifies the upgrade scenario for Tivoli Netcool/Proviso 4.4.3fix pack 1 or pre-fix pack 3 and the Alcatel-Lucent 5620 SAM Technology Pack.


Table 2. Alcatel-Lucent 5620 SAM Technology Pack and Tivoli Netcool/Proviso upgradescenario

Alcatel-Lucent 5620 SAMupgrade scenario


descriptionAlcatel-Lucent 5620 SAM

upgrade scenario steps


Tivoli Netcool/ProvisoupgradeYou are currently runningTivoli Netcool/Provisoupgrade 4.4.3. You want toupgrade to fix pack 1 orpre-fix pack 3.Technology pack upgradeYou want to upgradecurrently deployedAlcatel-Lucent 5620 SAM4.3-T or 4.3-U UBATechnology Pack to 4.3-V orlater.



2. Follow the upgradeinstructions described in“Alcatel-Lucent 5620SAM upgrade scenario”

3. Upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 1 or pre-fix pack 3.

Upgrading the Alcatel-Lucent 5620 SAM Technology PackThe following section discusses how to upgrade the Alcatel-Lucent 5620 SAMTechnology Pack according to the following scenario:v “Alcatel-Lucent 5620 SAM upgrade scenario”

In this scenario, you currently deployed a 4.3-V Alcatel-Lucent 5620 SAMTechnology Pack on Tivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fix pack 1or later, or 4.4.2. You want to upgrade to 4.3-U or later after upgrading to TivoliNetcool/Proviso 4.4.3 pre-fix pack 3.

Alcatel-Lucent 5620 SAM upgrade scenarioIn this scenario, you currently deployed a 4.3-V Alcatel-Lucent 5620 SAMTechnology Pack on Tivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fix pack 1 orlater, or 4.4.2. You want to upgrade to 4.3-U or later after upgrading to TivoliNetcool/Proviso 4.4.3 pre-fix pack 3.

About this task

To continue to deploy the 4.3-V Alcatel-Lucent 5620 SAM Technology Pack afterupgrading to Tivoli Netcool/Proviso 4.4.3 pre-fix pack 3, follow these steps:

Procedure1. Upgrade to Tivoli Netcool/Proviso 4.4.3 pre-fix pack 3 by following the

instructions in Upgrading Tivoli Netcool Performance Manager - Wireline Componentthat relates to your version of IBM Tivoli Netcool Performance Manager.

2. Check the Tivoli Netcool Performance Manager product support site for theinterim fixes that must be installed so that the Alcatel-Lucent 5620 SAMTechnology Pack can operate on Tivoli Netcool/Proviso 4.4.3 pre-fix pack 3. See“Essential information in the technology pack release notes” on page 9 for theproduct support site URL.

Note: Stop the Alcatel-Lucent 5620 SAM Technology Pack and DataChannelcomponents before applying the necessary interim fixes on Tivoli NetcoolPerformance Manager 4.4.3 pre-fix pack 3.

Chapter 2. Upgrading technology packs on Tivoli Netcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3 5

Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3 and Netflow IPFIXThis section provides information you need to upgrade the Netflow IPFIXTechnology Pack so that it operates correctly on a Tivoli Netcool/Proviso 4.4.3 fixpack 1 or pre-fix pack 3 system.

About this task

Important: Design changes in Tivoli Netcool/Proviso 4.4.3 require you to upgradethe Netflow IPFIX Technology Pack before upgrading to Tivoli Netcool/Proviso4.4.3 fix pack 1 or pre- fix pack 3. Otherwise, this pack stops working.

Table 3 identifies the upgrade scenarios for Tivoli Netcool/Proviso 4.4.3 fix pack 1or pre-fix pack 3 and the Netflow IPFIX Technology Pack.

Table 3. Netflow IPFIX Technology Pack and Tivoli Netcool/Proviso upgrade scenarios

Netflow IPFIX upgradescenario

Netflow IPFIX upgradescenario description

Netflow IPFIX upgradescenario steps

Netflow IPFIX upgradescenario 1

Tivoli Netcool/ProvisoupgradeYou are currently runningTivoli Netcool/Proviso 4.4.1MR1 or earlier, 4.4.1 fix pack1 or later, or 4.4.2. You wantto upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 1 or pre-fix pack 3.Technology pack upgradeYou want to upgrade thecurrently deployed 4.3-T or4.3-U Netflow IPFIXTechnology Pack to 4.3-V orlater.



2. Follow the upgradeinstructions described in“Netflow IPFIX upgradescenario 1” on page 7



Tivoli Netcool/ProvisoupgradeYou are currently runningTivoli Netcool/Proviso 4.4.3.You want to update to fixpack 1 or pre-fix pack 3.Technology pack upgradeYou want to upgradecurrently deployed 4.3-UNetflow IPFIX TechnologyPack to 4.3-V or later.Note: The Cisco NetflowTechnology Pack is renamedNetflow IPFIX TechnologyPack in 4.3-V because it nowsupports IPFIX.



2. Follow the upgradeinstructions described in“Netflow IPFIX upgradescenario 2” on page 8



Upgrading the Netflow IPFIX Technology PackThe following sections discuss how to upgrade the Netflow IPFIX Technology Packaccording to the following scenarios:v “Netflow IPFIX upgrade scenario 1”v “Netflow IPFIX upgrade scenario 2” on page 8

Netflow IPFIX upgrade scenario 1You must perform these steps when upgrading from 4.3-T or 4.3-U.

Before you begin

You must be logged in as root user to perform the following procedure:

About this task

In this scenario, you want to:v Upgrade the currently deployed 4.3-T or 4.3-U Netflow IPFIX Technology Pack

to 1.3-Lv Upgrade to Tivoli Netcool/Proviso 4.4.3 pre-fix pack 3

Note: The Cisco Netflow Technology Pack is renamed Netflow IPFIX TechnologyPack in 1.3-L because it now supports IPFIX.

To upgrade to the 1.3-L Netflow IPFIX Technology Pack and TivoliNetcool/Proviso 4.4.3 pre-fix pack 3, follow these steps:

Procedure

Uninstall the previous flow collector or Aurora Netflow Collector before installingthe TNPMFLOW Collector by following these steps:

Important: You must perform these steps when upgrading from 4.3-T or 4.3-U.You must be logged in as root user to perform the following procedure:1. For flow collector, follow these steps:

a. Stop the currently running flow collector by issuing the followingcommand:/opt/netcool/flowcoll/support/stop_flowcoll

b. Delete S22flowcollstart and K22flowcollstart from the /etc/init.d and/etc/rc3.d directories.

Note: For Aurora Netflow Collector, follow these steps:a. Stop the currently running Aurora Netflow Collector by issuing the

following command:aurora stop

b. Uninstall the Aurora Netflow Collector by issuing the following command:aurora deinstall

2. Install the 1.3-L Netflow IPFIX Technology Pack using the instructionscontained in the Installing and Configuring Technology Packs.

3. Using the root account, install the tnpmflow adaptor by changing to thefollowing directory:cd /opt/datamart/APFiles/cisco_netflow/adaptor

4. Extract the tnpmflow tar gunzip file. For example:


gunzip tnpmflow-4.1.1.9-2013.06.13-sparc64.tar.gztar -xf tnpmflow-4.1.1.9-2013.06.13-sparc64.tar

5. Change to the tnpmflow directory, and then run the INSTALL script.6. Configure the 1.3-L Netflow IPFIX Technology Pack by following the

instructions contained in the Technology Pack Installation and Configuration Guide.

Note: See “Limitations with UBA pack-specific parameter key/value pairs” onpage 12 for information related to specifying UBA key/value pairs.

Important: Technology packs might not work unless they are configured.7. Validate that the Netflow IPFIX Technology Pack is working in the Netflow

IPFIX environment before upgrading to Tivoli Netcool/Proviso 4.4.3 pre-fixpack 3.

What to do next

If you are not running the Alcatel-Lucent 5620 SAM Technology Pack 4.3-U orearlier, proceed to the next step.

Netflow IPFIX upgrade scenario 2In this scenario, you want to upgrade currently deployed 4.3-U Netflow IPFIXTechnology Pack to 4.3-V or later, after upgrading to Tivoli Netcool/Proviso 4.4.3pre-fix pack 3.

Documents you need for technology pack upgradeBefore upgrading a technology pack, ensure that you have the documents listed inTable 4.

Note: The Tivoli Netcool Performance Manager documentation (includingUpgrading Technology Packs, and Pack Release Summary and Installing and ConfiguringCommon Packs are available at the

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.3.2/com.ibm.tnpm.doc/welcome_tnpm.html

Table 4. Documents needed to perform a technology pack upgrade

Upgrade scenario Documents you need Essential information


v Installing Tivoli NetcoolPerformance Manager -Wireline Component (for4.4.3)

v Upgrading Technology Packs

v Pack Release Summary (for4.3-U and the later)

v See “Essential informationin the installation guide”on page 10

v See “Essential informationin the technology packrelease notes” on page 9




v The ReadMe for pre-fixpack 3

v Pack Release Summary (for4.3-V or later)


v See “Essential informationin Tivoli Netcool/Provisopre-fix pack 3 ReadMe” onpage 10

v See “Essential informationin the technology packrelease notes” on page 9




Table 4. Documents needed to perform a technology pack upgrade (continued)

Upgrade scenario Documents you need Essential information


v IBM Tivoli Netcool/Proviso:Installation Guide (for 4.4.1or 4.4.2) and InstallingTivoli Netcool PerformanceManager - WirelineComponent (for 4.4.3)

v Upgrading Tivoli NetcoolPerformance Manager -Wireless Component (for4.3-V)



v See “Essential informationin the technology packrelease notes”


v IBM Tivoli Netcool/Proviso:Installation Guide (for 4.4.1or 4.4.2) and InstallingTivoli Netcool PerformanceManager - WirelineComponent (for 4.4.3)


v Pack Release Summary (for4.3-V or later)






v Pack Release Summary (for4.3-V)



Note: For technology packs released in 1.3-E release onwards, the user guides aredeprecated. For more information, see Pack Release Summary.

Essential information in the technology pack release notesThe following information in the technology pack release notes is essential whenperforming a technology pack upgrade:v Complete list of supported technology packs table in Appendix A of the Release

Notes- The following columns of the table are of particular interest:– Technology pack - Specifies the name of the technology pack.– Type - Specifies the type of technology pack you are upgrading. The pack

configuration steps and pack upgrade steps differ, depending on the packtype.

– Upgradeable from - Indicates whether the pack you are upgrading supportsan upgrade path. If this column displays No upgrade path then thistechnology pack does not support an upgrade. The pack upgrade proceduresdescribed in this chapter do not succeed.

– Dependencies - Specifies whether the pack has any dependencies. Forexample, some packs require that the MIB-II technology pack to be installed.

v Interim fixes for Tivoli Netcool/Proviso v4.4.3.3 and Interim fixes for TivoliNetcool Performance Manager v1.3 table - The following columns of the tableare of particular interest:– Pack - Gives the name of the technology Pack


– Interim fix - Gives the name of the interim fix for that technology pack

Important: Before upgrading (installing) any technology pack, check the TivoliNetcool Performance Manager product support site for the latest interim fixes.Since status of interim fixes is subject to change at any time, it is important thatyou do this. The site address is:http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.html

Note: To receive announcements about new interim fixes, you might sign up foremail updates or subscribe to the Tivoli Netcool/Proviso support RSS feed. Theseoptions are available on the support page.

Essential information in the installation guideThis information is essential to performing a technology pack upgrade.

Upgrade scenario 1Refer to the technology pack installation chapter provided in the 4.4.3 IBMTivoli Netcool/Proviso: Installation Guide. Because there is an existing UBACollector, you can skip the section that describes how to add UBACollectors.

See “Upgrade scenario 1 (SNMP and UBA technology packs)” on page 14for more details.

Upgrade scenario 2Refer to the technology pack installation chapter provided in the 4.4.3 IBMTivoli Netcool/Proviso: Installation Guide. Because you are instructed on howto associate an existing XSD file with the upgraded pack's XSD file, youcan skip the section that describes how to add UBA Collectors.

See “Upgrade scenario 2 (UBA packs only)” on page 16 for more details.

Netflow IPFIX upgrade scenario 1Refer to the 4.3-U/4.3-V technology pack installation appendix that isprovided in the 4.4.1 or 4.4.2 IBM Tivoli Netcool/Proviso: Installation Guide.You need these instructions to upgrade (install) the 4.3-V versions of thesepacks.

Refer to the 4.4.3 IBM Tivoli Netcool/Proviso: Installation Guide to installTivoli Netcool/Proviso 4.4.3.

Alcatel-Lucent 5620 SAM upgrade scenario and Netflow IPFIX upgrade scenario2 There is no need to refer to the IBM Tivoli Netcool/Proviso: Installation Guide

because you are not upgrading the Alcatel-Lucent 5620 SAM TechnologyPack or Netflow IPFIX Technology Pack in these scenarios.

Essential information in Tivoli Netcool/Proviso pre-fix pack 3ReadMeThe Tivoli Netcool/Proviso pre-fix pack 3 ReadMe contains the instructions forupdating Tivoli Netcool/Proviso 4.4.3 to pre-fix pack 3. See “Essential informationin the technology pack release notes” on page 9 for the URL to the site address forinterim fixes and fix packs.


http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.html


Current limitations with Tivoli Netcool/Proviso 4.4.3 fix pack 1 andpre-fix pack 3

Starting in 4.3-U, each UBA technology pack is delivered with an XML SchemaDefinition (XSD) file. Each pack's XSD file describes and validates pack-specificparameters (referred to as properties in the Topology Editor environment) by usingan XML format. Typical pack-specific properties that are defined in these XSD filesinclude DELETEONACQUIRE, DESIGNFILE, and URI. In fact, the pack-specific propertiesthat are defined in XSD files map almost one-to-one with the UBA pack-specificparameters delivered in UBA pack dc.cfg template files.

Using the Topology Editor, you add a UBA Collector for a specific UBA pack. Thistask involves loading the pack's XSD file into an existing topology configuration(represented by the topology.xml file). After you load the pack's XSD file, theTopology Editor displays all of the pack-specific UBA properties.

Using the Topology Editor, you modify these pack-specific UBA properties. Whenyou deploy a topology configuration by using a topology.xml file, the values thatare specified for these properties are written to the database. The Topology Editormakes it easier for you to supply site-specific values to these UBA propertiesbecause there is a built-in logic in the XSD files. For example, the DESIGNFILEproperty definition in the XSD file is set to read-only because the value for thisproperty must never be changed. The Topology Editor enforces that state bydisplaying the property and its value as read-only.

The previous scenario describes a new installation of Tivoli Netcool/Proviso 4.4.3core components and a UBA technology pack. When you upgrade to TivoliNetcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3, however, the followinglimitations exist:v Limitations with the way the Topology Editor treats pack-specific UBA

parametersv Limitations with UBA parameter key/value pairs

Limitations with how the Topology Editor treats UBApack-specific parameters

When you upgrade Tivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fix pack 1 orlater, or 4.4.2 to Tivoli Netcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3, no XSDsare assigned to deployed UBA Collectors. In this case, the Topology Editor treatspack-specific UBA properties for deployed UBA packs as free form, customsettings. Thus, the Topology Editor cannot provide the appropriate validation ofsettings as it normally would during a typical pack installation.

Table 5 on page 12 describes the current limitations that are associated with howthe Topology Editor treats UBA pack-specific property settings for the upgradescenarios that are described in “Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3and technology packs” on page 3.

Note: SNMP technology packs do not have associated XSD files.


Table 5. Current limitations with Topology Editor and UBA pack-specific properties

Upgrade scenario Current limitations (UBA Packs Only)

Upgrade Scenario 1 The Topology Editor treats the UBApack-specific property settings for currentlydeployed UBA packs as free form, customsettings because there are no XSD files thatare associated with the UBA Collectors. Youneed not do anything with these customsettings. However, if you want to modifyany of the UBA pack-specific propertysettings, you would need to modify thecustom setting. It means the Topology Editorcannot provide the appropriate validation ofsettings as it normally would during atypical pack installation. In addition, theTopology Editor cannot display anyassociated Help text. In this case, you wouldneed to refer to the UBA Parameters Reference(Tivoli Netcool Performance Manager 443 andHigher) appendix in this UBA pack's userguide.

Upgrade Scenario 2 The Topology Editor treats the UBApack-specific property settings for theupgraded UBA pack as free form, customsettings because there is no XSD fileassociated with the deployed UBA Collector.In this scenario, you need to verify (by usingthe dc.cfg template file) that the site-specificvalues for the pack-specific UBA propertiesare correct, as discussed in “Upgradescenario 1 (SNMP and UBA technologypacks)” on page 14.Note: The Topology Editor identifies customproperties with a check mark in the IsCustom column of the Properties andAdvanced Properties tabs.

Limitations with UBA pack-specific parameter key/value pairsDesign changes in Tivoli Netcool/Proviso 4.4.3 effect UBA pack-specific parameterkey/value pairs as follows:v Each UBA parameter key/value pair is limited to 40 characters.v Each UBA parameter key must be specified in uppercase.

Note: For the Alcatel-Lucent 5620 SAM Technology Pack, the previous limitationsalso apply to the BLB and SAMIF key/value pairs.

The following example shows a UBA pack-specific parameter key/value pair fromthe Alcatel-Lucent 5620 SAM Technology Pack's dc.cfg template file that adheresto the previously described limitations:

UBA.1.100.ALCATEL_5620_SAM.SAM_EQUIPMENT_INTERFACE.DELETEONACQUIRE=true

In this example, the key/value pair consists of the pack-specific UBA parameterDELETEONACQUIRE and its associated value true.


Before you begin a technology pack upgradeAbout this task

Before you upgrade a technology pack, ensure that you completed the followingsteps:

Procedurev Consulted the latest version of theIBM Tivoli Netcool Performance Manager: Pack

Release Notes. For more information about specific sections to consult before youperform the pack upgrade, see “Essential information in the technology packrelease notes” on page 9.

v Consulted with your IBM Professional Services representative before youupgrade a technology pack. Your IBM Professional Services Representative usesthe documentation sources that are described in “Documents you need fortechnology pack upgrade” on page 8.CAUTION:If you have a customized technology pack that is installed at your site withmodified content, it is overwritten if the same pack is upgraded to a laterversion. Check with your IBM customer service representative before youupgrade an existing technology pack to a later version.

v The correct version of Java. For more information, see “Essential information inthe technology pack release notes” on page 9.

v Access to the product distribution site:https://www-112.ibm.com/software/howtobuy/softwareandservices

On the product distribution site is the ProvisoPackInstaller.jar file, thebundled JAR file, and individual stand-alone technology pack JAR files.

v Access to the following site to check for interim fixes or fix packs that mightapply to your technology pack:http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.html

For more information, see “Essential information in the technology pack releasenotes” on page 9.

v Access to the Tivoli Netcool Performance Manager documentation, technologypack user guides, and technology pack release notes, which are available at theTivoli Netcool Performance Manager Technology Pack Knowledge CenterFor more information about what to look for in the documents that are neededfor technology pack upgrades, see “Documents you need for technology packupgrade” on page 8.

v Used the following GUI components that were introduced in TivoliNetcool/Proviso 4.4.3:– Topology Editor, including:

- How to work with UBA technology pack XSD files (see “Currentlimitations with Tivoli Netcool/Proviso 4.4.3 fix pack 1 and pre-fix pack 3”on page 11 for current limitations.)

- How to work with custom propertiesv Read and understood the upgrade scenarios that are described in the chapter.


https://www-112.ibm.com/software/howtobuy/softwareandservices


http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_wln_tp.doc/wln_tech_pack_release_welcome.html

Standard procedure for upgrading technology packs (ExceptAlcatel-Lucent 5620 SAM and Netflow IPFIX)

About this task

The following sections discuss how to upgrade technology packs according to thefollowing scenarios:v “Upgrade scenario 1 (SNMP and UBA technology packs)”v “Upgrade scenario 2 (UBA packs only)” on page 16

Important: See “Upgrading the Alcatel-Lucent 5620 SAM Technology Pack” onpage 5 and “Upgrading the Netflow IPFIX Technology Pack” on page 7 forinstructions on how to perform the upgrade scenarios for these technologypacks.

Upgrade scenario 1 (SNMP and UBA technology packs)About this task

You are currently running Tivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fixpack 1 or later, or 4.4.2. You want to do the following:v Upgrade to Tivoli Netcool/Proviso 4.4.3 pre-fix pack 3 (which you do before

performing the pack upgrade by following the instructions in the UpgradingTivoli Netcool Performance Manager - Wireline Component that relates to yourversion of Tivoli Netcool/Proviso).

v Upgrade currently deployed technology packs to 4.3-U or later.

To upgrade currently deployed technology packs to 4.3-U or later, follow thesesteps:

Procedure1. Upgrade the technology pack to 4.3-U or later by following the instructions in

the installing technology packs chapter that is provided in the 4.4.3 IBM TivoliNetcool/Proviso:Upgrading Technology Packs

Note: (UBA packs only). Because there is an existing UBA Collector, you canskip the section that describes how to add UBA Collectors.

2. (For SNMP packs only) Configure the SNMP technology pack that youupgraded, by referring to the configuration appendix of the appropriatetechnology pack user's guide.

Important: Technology packs do not work unless they are configured.3. Perform the following steps (for UBA packs only):

a. Use the Topology Editor to display the pack-specific UBA properties.Remember that these properties are displayed as free form, customproperties.

4. Optional: If you must add a custom property, follow these steps:a. Open the Topology Editor.b. Open the topology that is associated with the UBA pack you upgraded.c. In the Application Pack view, select the UBA pack that you upgraded.d. Display the COLLECTOR_UBA.x.x entry. The DataChannel core and

pack-specific properties display in the properties window.


e. Select the blue + (plus) icon that displays at the right top corner of theproperties window. The Add Custom Property for UBA Collector wizarddisplays.

f. The wizard displays three fields:v Name - Specifies the pack-specific UBA property to associate with a UBA

pack subelement.v Value - Specifies the value that is associated with this pack-specific UBA

property.v Alias - Specifies the name of the property that the Topology Editor

displays in the Property view. Valid values include the pack-specific UBAproperty name that is specified in the Name field or descriptive text.

g. Specify the name of the new UBA pack-specific parameter in the Namefield. In this example, the name that is specified would be ERRORFILEMAX.

Note: Do not enter the channel number (<CHANNEL>, collectornumber(<COLLECTOR>, instance (UNIV_WAN_MGR, and schema(AVAIL) in theName field.

h. Specify a value in the Alias field according to the discussed guidelines. Inthis example, ERRORFILEMAX is specified.

i. Click Finish.5. Optional: If you must delete (remove) a custom property, follow these steps:

a. Open the Topology Editor.b. Open the topology that is associated with the UBA pack you upgraded.c. In the Application Pack view, select the UBA pack that you upgraded.d. Display the COLLECTOR_UBA.x.x entry. The DataChannel core and

pack-specific parameters display in the properties window.e. Select the pack-specific UBA custom property to remove in the Properties or

Advanced Properties tab.f. Click the Remove Custom Property (a red X icon that appears in the

Property view).6. After you validate the UBA pack-specific properties:

a. Redeploy the updated topology, as described in the 4.4.3 TivoliNetcool/Proviso Upgrading Technology Packs.

7. Configure the UBA technology pack that you upgraded, by referring to theconfiguration appendix of the appropriate technology pack user guide.

Important: Technology packs do not work unless they are configured.

Table 6. Example Mappings for Ciena Transmission Technology Pack

Template fileparameter Topology Editor property Comments

UBA.2.100.INSTANCES=streaming

INSTANCES=CIENA_DEVICE The INSTANCES parameter that is used to be anarbitrary string as illustrated by the stringstreaming specified in the template fileparameter. The convention now is to use astring that represents the name of thetechnology pack, as illustrated by the TopologyEditor property value, CIENA_DEVICE.Note: It is not necessary to specify the channelnumber, collector number, and schema in thevalues for the Topology Editor properties. SeeStep 4-g for an example of how to enter thename of a new UBA pack-specific parameter.


Table 6. Example Mappings for Ciena Transmission Technology Pack (continued)

Template fileparameter Topology Editor property Comments

UBA.2.100.streaming.DESIGNFILE=CienaAdaptor.js

CIENA_DEVICE.DESIGNFILE=CienaAdaptor.js

The Bulk Adaptor Design file (in this case,CienaAdaptor.js) must be the same in both thetemplate file parameter and the TopologyEditor property.

UBA.2.100.streaming.CEMS.URI=file:///export/home/pvuser/uba_files/CEMS/input/*.csv

CIENA_DEVICES.CEMS.URI=$5f tp://$1:$2@$3/$4/*.csv

The value in the template file for the URIparameter is typically an example URLspecification. The URI property in the TopologyEditor is typically read-only and its associatedvalue is a concatenation of the followingproperties:

v INPUT_USE_SECURE_FTP ($5)

v INPUT_FTP_HOST ($3)

v INPUT_FTP_USERNAME ($1)

v INPUT_FTP_PASSWORD ($2)

v INPUT_DIRECTORY ($4)

Note: The values ($1 through $5) specifiedhere are taken from the Ciena TransmissionTechnology Pack's XSD file to show theconcatenation of properties.Because there is no XSD, you must specify theURL specification in the URI property, not theindividual properties that are listed.

UBA.2.100.streaming.DELETEONACQUIRE=false

CIENA_DEVICE.CEMS.DELEATEONACQUIRE=false

In this example, the DELETEONACQUIREparameter in the template file and theTopology Editor property have the same value(false). It might not always be the case.

Upgrade scenario 2 (UBA packs only)Before you begin

The Topology Editor maintains the association with the existing XSD file.Therefore, it verifies the values that are currently specified for the UBApack-specific property settings.

In this scenario, you perform the following steps:v Currently, you deployed 4.3-U UBA technology packs running on Tivoli

Netcool/Proviso 4.4.3.v Completed the update of Tivoli Netcool/Proviso 4.4.3 to fix pack 3 or Tivoli

Netcool Performance Manager by following the instructions in the fix pack 3ReadMe.

v Want to upgrade currently deployed 4.3-U technology packs to 4.3-V or later.

About this task

To upgrade currently deployed 4.3-U technology packs to 4.3-V or later, followthese steps:

Procedure1. Update the UBA technology pack metadata by following these steps:

a. Open the Topology Editor.


b. Create a new empty topology by selecting File > create new topology.Retain the default number of resources as this operation is only necessary topopulate the Application Pack view.

c. In the Application Pack view, right-click the Application Packs folder andselect Load Application Pack from the menu.

d. Navigate to the directory where you copied the new stand-alone (orbundled) JAR file. The Topology Editor displays a message warning that theXSD exists. The message also asks if you want to replace the XSD. Specifythat you want to replace the XSD.

e. After you replace the XSD, close the Topology Editor. You successfullyreplaced the UBA technology pack metadata.

2. Reopen the Topology Editor and select the existing deployed topology(topology.xml). The UBA pack-specific properties are applied to the existingdeployed topology according to the following rules:v Properties that were added to the pack XSD displays in the Property tab

with their default values. You can modify, if necessary, any writableproperties.

v Properties that were removed in the XSD shows in the Property tab ascustom properties. If not needed, you can remove these properties byfollowing these instructions:

a. Open the Topology Editor.b. Open the topology that is associated with the UBA pack you upgraded.c. In the Application Pack view, select the UBA pack that you upgraded.d. Display the COLLECTOR_UBA.x.x entry. The DataChannel core and


Advanced Properties tab.f. Click the Remove Custom Property (a red X icon that appears in the

Property view).3. Redeploy the updated topology, as described in the 4.4.3 Tivoli

Netcool/ProvisoInstalling Technology Packs.4. Use the dccmd command to stop the UBA application:

dccmd -action stop UBA

5. Upgrade the 4.3-U UBA technology pack to 4.3-V or later by following theinstructions that are provided in the pack installation chapter of the 4.4.3 TivoliNetcool/ProvisoInstalling Technology Packs.

Note: Because there is an existing UBA Collector, you can skip the section thatdescribes how to add UBA Collectors.

6. Configure the UBA technology pack that you upgraded, by referring to theconfiguration appendix of the appropriate technology pack user guide. One ofthe configuration steps instructs you to restart the DataChannel to activate theUBA and read in changes to the deployed topology.




Chapter 3. Upgrading technology packs on TivoliNetcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool PerformanceManager

This chapter describes how to upgrade your technology packs, after you upgradedto Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Manager.

If you upgraded to Tivoli Netcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3, youmust follow the upgrade instructions that are presented in Chapter 2, “Upgradingtechnology packs on Tivoli Netcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3,” onpage 3.

OverviewThis chapter explains how to upgrade technology packs after you upgrade yourTivoli Netcool Performance Manager system. Specifically, the chapter providesinstructions on how to upgrade technology packs according to several upgradescenarios.

For UBA technology packs, the chapter also provides:v Information about what to expect regarding UBA pack-specific property settings

for deployed packs when you upgrade to Tivoli Netcool/Proviso 4.4.3 fix pack 3or Tivoli Netcool Performance Manager (“Topology Editor and UBApack-specific properties” on page 30.)

v Guidelines for verifying UBA technology pack-specific properties when youupgrade a UBA technology pack after you upgrade to Tivoli Netcool/Proviso4.4.3 fix pack 3 or Tivoli Netcool Performance Manager (“Topology Editor andUBA pack-specific properties” on page 30.)

v Specific upgrade scenarios for the following technology packs:– Alcatel-Lucent 5620 SAM Technology Pack. For more information, see

“Upgrade scenario for Tivoli Netcool/Proviso 4.4.3 and Alcatel-Lucent 5620SAM” on page 4.

– Netflow IPFIX Technology Pack. For more information, see “Upgradescenarios for Tivoli Netcool/Proviso 4.4.3 and Netflow IPFIX” on page 6.

Important: Design changes in Tivoli Netcool/Proviso 4.4.3 require that you mustupgrade Alcatel-Lucent 5620 SAM and Netflow IPFIX before you upgrade fromTivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fix pack 1 or later, and 4.4.2 toTivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Manager.Otherwise, these packs stop working.

See also the Pack Release Summary to determine the version from which atechnology pack is upgradeable. For example, the Release Summary for Tivoli NetcoolPerformance Manager might specify that your technology pack is upgradeable fromversion 4.3-V or later.


Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3 and Tivoli NetcoolPerformance Manager technology packs

This section provides information you need to upgrade technology packs so thatthey operate correctly on a Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli NetcoolPerformance Manager system.

Table 7 identifies the upgrade scenarios for Tivoli Netcool/Proviso 4.4.3 andtechnology packs.

Table 7. Tivoli Netcool Performance Manager and technology pack upgrade scenarios

Upgrade scenarioUpgrade scenario

description Upgrade scenario steps


Tivoli Netcool PerformanceManager upgradeYou are currently runningTivoli Netcool/Proviso 4.4.1MR1 or earlier, 4.4.1 fix pack1 or later, or 4.4.2. You wantto upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 3 or Tivoli NetcoolPerformance Manager.Technology pack upgradeYou want to upgradecurrently deployedtechnology packs to 4.3-U orlater.


1. Upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 3 or Tivoli NetcoolPerformance Manager.

2. See“Documents youneed to perform atechnology packupgrade” on page 25 forthe documents you mustperform this upgradescenario.

3. See “Upgrade scenario 1(SNMP and UBAtechnology packs) (exceptAlcatel-Lucent 5620 SAM,Netflow IPFIX)” on page36 for details about thisupgrade scenario.


Tivoli Netcool/Proviso fixpack updateYou are currently runningTivoli Netcool/Proviso 4.4.3.You want to update to TivoliNetcool/Proviso 4.4.3 fixpack 3 or Tivoli NetcoolPerformance Manager.Technology pack upgradeYou want to upgradecurrently deployed 4.3-UUBA technology packs to4.3-V or later.


1. Upgrade TivoliNetcool/Proviso 4.4.3 tofix pack 3 or TivoliNetcool PerformanceManager

2. See “Documents youneed to perform atechnology packupgrade” on page 25 forthe documents you mustperform this upgradescenario.

3. See “Upgrade scenario 2(UBA packs only)(Including Alcatel-Lucent5620 SAM, NetflowIPFIX)” on page 41 fordetails.


Upgrade scenario for Tivoli Netcool/Proviso 4.4.3 and Alcatel-Lucent5620 SAM

This section provides information you need to upgrade the Alcatel-Lucent 5620SAM Technology Pack so that it operates correctly on a Tivoli Netcool/Proviso4.4.3 fix pack 1 or pre-fix pack 3 system.

Important: Design changes in Tivoli Netcool/Proviso 4.4.3 require you to upgradeAlcatel-Lucent 5620 SAM before upgrading to Tivoli Netcool/Proviso 4.4.3 fix pack3 or Tivoli Netcool Performance Manager. Otherwise, this pack stops working.

Table 8 identifies the upgrade scenario for Tivoli Netcool/Proviso 4.4.3 fix pack 3or Tivoli Netcool Performance Manager and the Alcatel-Lucent 5620 SAMTechnology Pack.

Table 8. Alcatel-Lucent 5620 SAM Technology Pack and Tivoli Netcool/Proviso upgradescenario


Alcatel-Lucent 5620 SAM upgradescenario description

Alcatel-Lucent5620 SAMupgrade

scenario steps


Tivoli Netcool/Proviso upgradeYou are currently running TivoliNetcool/Proviso 4.4.3. You want toupgrade to fix pack 3 or Tivoli NetcoolPerformance Manager.Technology pack upgrade You want toupgrade the currently deployedAlcatel-Lucent 5620 SAM 4.3-T or 4.3-UUBA Technology Pack to the ReleaseSummary for Tivoli Netcool PerformanceManager.Tivoli Netcool PerformanceManager Release.

Perform thefollowing steps:

1. “Documentsyou need fortechnologypackupgrade” onpage 8 forthedocumentsyou mustperform thisupgradescenario.

2. Follow theupgradeinstructionsdescribed inAlcatel-Lucent 5620SAMupgradescenario.

3. Upgrade toTivoliNetcool/Proviso 4.4.3fix pack 1 orpre-fix pack3.

Chapter 3. Upgrading technology packs on Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Manager 21

Upgrading the Alcatel-Lucent 5620 SAM Technology PackExample

The following section discusses how to upgrade the Alcatel-Lucent 5620 SAMTechnology Pack according to the following scenario:

Important: Tivoli Netcool/Proviso Technology Pack Installer 3.1.2.0 or later isrequired for the upgrade to Alcatel-Lucent 5620 SAM 4.3-Y or later technologypack.v “Alcatel-Lucent 5620 SAM upgrade scenario”

Alcatel-Lucent 5620 SAM upgrade scenarioFollow the instructions for upgrade scenario, as described in “Upgrade scenario 2(UBA packs only) (Including Alcatel-Lucent 5620 SAM, Netflow IPFIX)” on page41.

Important: For more information about upgrading from previous releases of theAlcatel-Lucent 5620 SAM Technology Pack to Alcatel-Lucent 5620 SAM TechnologyPack for Alcatel-Lucent 5620 SAM Server Release 9, see Alcatel-Lucent 5620 SAM2.11.0.0 Technology Pack User Guide.

Upgrade scenarios for Tivoli Netcool/Proviso 4.4.3 or Tivoli NetcoolPerformance Manager and Netflow IPFIX

This section provides information you need to upgrade the Netflow IPFIXTechnology Pack so that it operates correctly on a Tivoli Netcool/Proviso 4.4.3 fixpack 3 or Tivoli Netcool Performance Manager system.

About this task

Important: Design changes in Tivoli Netcool/Proviso 4.4.3 require you to upgradethe Netflow IPFIX Technology Pack before upgrading from Tivoli Netcool/Proviso4.4.1 MR1 or earlier, 4.4.1 fix pack 1 or later, and 4.4.2 to Tivoli Netcool/Proviso4.4.3 fix pack 3 or Tivoli Netcool Performance Manager. Otherwise, this pack stopsworking.

Table 9 on page 23 identifies the upgrade scenarios for Tivoli Netcool/Proviso 4.4.3fix pack 3 or Tivoli Netcool Performance Manager and the Netflow IPFIXTechnology Pack.


Table 9. Netflow IPFIX Technology Pack and Tivoli Netcool Performance Manager upgradescenarios

Netflow IPFIX upgradescenario

Netflow IPFIX upgradescenario description

Netflow IPFIX upgradescenario steps


Tivoli Netcool PerformanceManager upgradeYou are currently runningTivoli Netcool/Proviso 4.4.1MR1 or earlier, 4.4.1 fix pack1 or later, or 4.4.2. You wantto upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 3 or Tivoli NetcoolPerformance Manager.Technology pack upgradeYou want to upgrade thecurrently deployed 4.3-VNetflow IPFIX TechnologyPack to 4.3-W or later.


v See “Documents you needto perform a technologypack upgrade” on page 25for the documents youmust perform this upgradescenario.

v Follow the upgradeinstructions described in“Netflow IPFIX upgradescenario 1” on page 24

v Upgrade to TivoliNetcool/Proviso 4.4.3 fixpack 3 or Tivoli NetcoolPerformance Manager.


Tivoli Netcool/Proviso fixpack updateYou are currently runningTivoli Netcool/Proviso 4.4.3.You want to upgrade toTivoli Netcool/Proviso 4.4.3fix pack 3 or Tivoli NetcoolPerformance Manager.Technology pack upgradeYou want to upgrade acurrently deployed NetflowIPFIX 4.3-V UBA TechnologyPack to 4.3-X or later.


v Upgrade TivoliNetcool/Proviso 4.4.3 tofix pack 3 or TivoliNetcool PerformanceManager.

v See “Documents you needto perform a technologypack upgrade” on page 25for the documents youmust perform this upgradescenario.

v See “Netflow IPFIXupgrade scenario 2” onpage 25 for details.

Upgrading the Netflow IPFIX Technology PackAbout this task

The following sections discuss how to upgrade the Netflow IPFIX Technology Packaccording to the following scenarios:v “Netflow IPFIX upgrade scenario 1” on page 24v “Netflow IPFIX upgrade scenario 2” on page 25


Netflow IPFIX upgrade scenario 1About this task

In this scenario, you want to do the following:v Upgrade the currently deployed 4.3-U or 4.3-V Netflow IPFIX Technology Pack

to 4.3-X or later.v Upgrade to Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool

Performance Manager.

To upgrade to the 4.3-X or later Netflow IPFIX Technology Pack and TivoliNetcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Manager, followthese steps:

Procedure1. Uninstall the previous flow collector or Aurora Netflow Collector before

installing the TNPMFLOW Collector by following these steps:

Important: You must perform these steps when upgrading from 4.3-U or 4.3-V.You must be logged in as root to perform the following procedure:a. For flow collector, follow these steps:

1) Stop the currently running flow collector by issuing the followingcommand:/opt/netcool/flowcoll/support/stop_flowcoll

2) Delete S22flowcollstart and K22flowcollstart from the /etc/init.dand /etc/rc3.d directories.

Note: For Aurora Netflow Collector, follow these steps:1) Stop the currently running Aurora Netflow Collector by issuing the

following command:aurora stop

2) Uninstall the Aurora Netflow Collector by issuing the followingcommand:aurora deinstall

b. Install the 1.3-L Netflow IPFIX Technology Pack using the instructionscontained in the Installing and Configuring Common Packs.

c. Using the root account, install the tnpmflow adaptor by changing to thefollowing directory:cd /opt/datamart/APFiles/cisco_netflow/adaptor

d. Extract the tnpmflow tar gunzip file. For example:gunzip tnpmflow-4.1.1.9-2013.06.13-sparc64.tar.gztar -xf tnpmflow-4.1.1.9-2013.06.13-sparc64.tar

e. Change to the tnpmflow directory and run the INSTALL script.2. Configure the 1.3-L Netflow IPFIX Technology Pack by following the

instructions contained in the Installing and Configuring Common Packs.

Note: See “Limitations with UBA pack-specific parameter key/value pairs” onpage 32 for information related to specifying UBA key/value pairs.

Important: Technology packs do work unless they are configured.3. Validate that the Netflow IPFIX Technology Pack is working in the Netflow

IPFIX environment before upgrading to Tivoli Netcool/Proviso 4.4.3.


4. Upgrade to Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli NetcoolPerformance Manager by following the instructions in Upgrading Tivoli NetcoolPerformance Manager - Wireline Component that relates to your version of TivoliNetcool Performance Manager.

Netflow IPFIX upgrade scenario 2Follow the instructions for upgrade scenario 2, as described in “Upgrade scenario 2(UBA packs only) (Including Alcatel-Lucent 5620 SAM, Netflow IPFIX)” on page41.

Documents you need to perform a technology pack upgradeBefore upgrading a technology pack, ensure that you have the documents listed inTable 10.

Note: The Tivoli Netcool Performance Manager documentation (includingUpgrading Tivoli Netcool Performance Manager - Wireline Component), Release Summaryfor Tivoli Netcool Performance Manager and Installing and Configuring Technology Packsthat are available at the following website:http://www-01.ibm.com/support/knowledgecenter

Table 10. Documents you need to perform a technology pack upgrade

Upgrade scenario Documents you needEssential

information


v Installing Tivoli Netcool PerformanceManager - Wireline Component

v Upgrading Tivoli Netcool PerformanceManager - Wireline Component

v Installing and Configuring Technology Packs

v Release Summary for Tivoli NetcoolPerformance Manager

v See “EssentialInformation intheInstallationGuide” onpage 29

v See “Essentialinformation inthe packinstallationandconfigurationguide” onpage 28

v See “Essentialinformation inpack releasenotes” onpage 29


http://www-01.ibm.com/support/knowledgecenter

Table 10. Documents you need to perform a technology pack upgrade (continued)


information


v Installing Tivoli Netcool PerformanceManager - Wireline Component


v The Fix pack 3 (or later) ReadMe


v Release Summary for Tivoli NetcoolPerformance Manager (for 4.3-U or later)


v See “Essentialinformation inthe TivoliNetcool/Proviso fixpack 3 orTivoli NetcoolPerformanceManagerReadMe” onpage 30






information


v IBM Tivoli Netcool/Proviso: Installing TivoliNetcool Performance Manager - WirelineComponent (for 4.4.3)


v IBM Tivoli Netcool Performance Manager:Alcatel-Lucent 5620 SAM 2.11.0.0Technology Pack User Guide

v Release Summary for Tivoli NetcoolPerformance Manager (for January 2012release)




v See“Alcatel-Lucent 5620SAM upgradescenario” onpage 22


v IBM Tivoli Netcool/Proviso: InstallationGuide (for 4.4.1 or 4.4.2)

v IBM Tivoli Netcool/Proviso: Installing TivoliNetcool Performance Manager - WirelineComponent (for 4.4.3)



v Release Summary for Tivoli NetcoolPerformance Manager (for January 2012release)







information


v IBM Tivoli Netcool/Proviso: InstallationGuide (for 4.4.3)


v IBM Tivoli Netcool Performance Manager:Netflow IPFIX Technology Pack User Guide

v Release Summary for Tivoli NetcoolPerformance Manager (for 4.3-X)



v See “Essentialinformation inthe packinstallationandconfigurationguide”

v See “Upgradescenario 2(UBA packsonly)(IncludingAlcatel-Lucent5620 SAM,NetflowIPFIX)” onpage 41

Essential information in the pack installation andconfiguration guide

The following information is essential for performing a pack upgrade:

(SNMP and UBA packs) ConfigurationThe IBM Tivoli Netcool Performance Manager: Pack Installation andConfiguration Guide contains a configuration chapter. After you upgrade atechnology pack to a later version, you must perform the configurationsteps that are described in the configuration chapter. The sections in thischapter that describe the upgrade scenarios specify when you must refer tothe configuration chapter in IBM Tivoli Netcool Performance Manager: PackInstallation and Configuration Guide for the pack you are upgrading.

Note: Before Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli NetcoolPerformance Manager, some of the upgrade scenarios caused the TopologyEditor to treat these pack-specific UBA properties as free from customproperties. Thus, the Topology Editor was unable to display the associatedHelp. For information about how Tivoli Netcool/Proviso 4.4.3 fix pack 3 orTivoli Netcool Performance Manager corrects these limitations, see“Topology Editor and UBA pack-specific properties” on page 30.


Essential information in pack release notesThe following information in the pack release notes is essential when performing apack upgrade:v Complete list of Supported technology packs table - The following columns of

the table are of particular interest:– Technology pack - Specifies the name of the technology pack.– Type - Specifies the type of technology pack you are upgrading. The pack

configuration steps and technology pack upgrade steps differ, depending onthe technology pack type.

– Upgradeable from - Indicates whether the pack you are upgrading supportsan upgrade path. If this column displays No upgrade path, then thistechnology pack does not support an upgrade. The pack upgrade proceduresdescribed in this chapter do not succeed.

– Dependencies - Specifies whether the pack has any dependencies. Forexample, some packs require that the MIB-II technology pack to be installed.

v Interim fixes for Tivoli Netcool/Proviso v4.4.3.3 and Interim fixes for TivoliNetcool Performance Manager v1.3 and above table - The following columns ofthe table are of particular interest:– Pack - Gives the name of the technology Pack– Interim fix - Gives the name of the interim fix for that technology pack

Important: Before upgrading (installing) any technology pack, check the TivoliNetcool Performance Manager product support site for the latest interim fixes.Since status of interim fixes is subject to change at any time, it is important thatyou do this procedure.The site address is:http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.html

Note: To receive announcements about new interim fixes, you might sign up foremail updates or subscribe to the Tivoli Netcool Performance Manager supportRSS feed. These options are available on the support page.

Essential Information in the Installation GuideThe following information is essential to performing a technology pack upgrade:v For Upgrade Scenario 1 - Refer to the appropriate technology pack installation

appendix provided in the 4.4.3 Installing Tivoli Netcool Performance Manager -Wireline Component. Because there is an existing UBA collector, you can skip thesection that describes how to add UBA collectors.See “Upgrade scenario 1 (SNMP and UBA technology packs) (exceptAlcatel-Lucent 5620 SAM, Netflow IPFIX)” on page 36 for more details.

v For Upgrade Scenario 2, Alcatel-Lucent 5620 SAM Upgrade Scenario, andNetflow Upgrade Scenario 2- Refer to the appropriate technology packinstallation appendix provided in the 4.4.3 Installing and Configuring TechnologyPacks. Because you are instructed on how to associate an existing XSD file withthe upgraded pack XSD file, you can skip the section that describes how to addUBA collectors.See “Upgrade scenario 2 (UBA packs only) (Including Alcatel-Lucent 5620 SAM,Netflow IPFIX)” on page 41 for more details.




Essential information in the Tivoli Netcool/Proviso fix pack 3or Tivoli Netcool Performance Manager ReadMe

The Tivoli Netcool/Proviso fix pack ReadMe contains the instructions for updatingTivoli Netcool/Proviso 4.4.3 to the latest fix pack (in this case fix pack 3 or TivoliNetcool Performance Manager). See “Essential information in pack release notes”on page 29 for the URL to the site address for interim fixes and fix packs.

Topology Editor and UBA pack-specific propertiesStarting from 4.3-U, each UBA technology pack delivers with an XML SchemaDefinition (XSD) file. Each pack XSD file describes and validates pack-specificparameters (referred to as properties in the Topology Editor environment) by usingan XML format.

Typical pack-specific properties that are defined in these XSD files includeDELETEONACQUIRE, DESIGNFILE, and URI.

Note: Before Tivoli Netcool/Proviso 4.4.3, you added the pack-specific UBAparameters that are delivered in the pack template file to the deployed dc.cfg file.This is no longer required in Tivoli Netcool/Proviso 4.4.3.

Using the Topology Editor, you add a UBA collector for a specific UBA pack. Thistask involves loading the pack XSD file into an existing topology configuration(represented by the topology.xml file). After you load the pack XSD file, theTopology Editor displays all of the pack-specific UBA properties. For some morecomplicated UBA technology packs, adding a UBA collector causes the TopologyEditor to also display pack-specific BLB (Bulk Load Balancer) and IF (InventoryFile) properties.

Using the Topology Editor, you modify these pack-specific UBA properties (andpack-specific BLB and IF properties if the pack defines these components in itsXSD file). When you deploy a topology configuration by using a topology.xml file,the values that are specified for these properties are written to the database. TheTopology Editor makes it easier for you to supply site-specific values to these UBAproperties because there is a built-in logic in the XSD files. For example, theDESIGNFILE property definition in the XSD file is set to read-only because the valuefor this property must never be changed. The Topology Editor enforces that stateby displaying the property and its value as read-only.

The previous scenario describes a new installation of Tivoli Netcool/Proviso 4.4.3core components and a UBA technology pack. Before Tivoli Netcool/Proviso 4.4.3fix pack 3 or Tivoli Netcool Performance Manager, when you upgraded to TivoliNetcool/Proviso 4.4.3 fix pack 1 or pre-fix pack 3 the following limitations existed:v Limitations with the way the Topology Editor treated pack-specific UBA

parametersv Limitations with UBA parameter key/value pairs

Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Managerremoves the limitations with the way the Topology Editor treats pack-specificparameters by providing a feature in the Topology Editor called the Technologypack XSD upgrade wizard. However, Tivoli Netcool/Proviso 4.4.3 fix pack 3 orTivoli Netcool Performance Manager does not remove the limitations with UBAparameter key/value pairs.


The following sections describe the Technology pack XSD upgrade wizard and theLimitations that are associated with UBA parameter key/value pairs.

Technology pack XSD upgrade wizardThe GUI and Technology Pack Installer (introduced in Tivoli Netcool/Proviso 4.4.3and 4.3-U) make it easier to install and configure technology packs.

The current technology pack release continues to take advantage of the graphicaluser interface (GUI) and the Technology Pack Installer single installation utility.

The following list highlights GUI tools that help improve the installation andupgrade of technology packs:v Launchpad - The launchpad, an HTML-based application, is the preferred

method for installing technology packs. The launchpad provides an option forstarting the Technology Pack Installer, which installs bundled and stand-alonetechnology packs.

v Topology Editor - In addition to improving the installation of Tivoli NetcoolPerformance Manager components (DataChannel, DataView, and DataMart), theTopology Editor (accessed through the launchpad) makes it easier to add UBAcollectors for UBA technology packs. Using the Topology Editor, you modifypack-specific UBA parameters (also referred to as properties). When you deploya topology configuration by using a topology.xml file, the values that arespecified for these parameters are written to the database. On TivoliNetcool/Proviso 4.4.3 systems, there is no need to edit pack-specific UBAparameters in the pack template file and copy these edits to the dc.cfg file.

In Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Managerthe Topology Editor includes a Technology pack XSD upgrade wizard that makes iteasier to deal with UBA pack-specific properties. Before Tivoli Netcool/Proviso4.4.3 fix pack 3 or Tivoli Netcool Performance Manager, when you upgraded toTivoli Netcool/Proviso 4.4.3 from a previous version of Tivoli Netcool/Proviso, noXSDs were assigned to the deployed UBA collectors. In this case, the TopologyEditor treated pack-specific UBA properties for deployed UBA packs as free form,custom settings. Thus, the Topology Editor might not provide the appropriatevalidation of settings as it normally would during a typical pack installation.

Because the Technology pack XSD upgrade wizard is included as part of theTopology Editor in Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli NetcoolPerformance Manager, there is no need to start a separate utility. You start theTopology Editor as described in the Installing Tivoli Netcool Performance Manager -Wireline Component. The Technology pack XSD upgrade wizard is automaticallystarted when, in the Application Packs view, you right-click the Application Packsfolder and select Associate components with new AP from the menu.

Note: Typically, you use the technology pack XSD upgrade wizard with upgradescenario 2, specifically to upgrade UBA packs. For more information, see“Upgrading currently deployed UBA technology packs to 4.3-U or later” on page36.

Note: SNMP technology packs do not have associated XSD files.

The technology pack XSD upgrade wizard removes the previously describedlimitations from upgrade scenario 2, as described in Table 11 on page 32.


Table 11. Removal of limitations with Topology Editor and UBA pack-specific properties

Upgradescenario

Limitations (UBA packsonly) before 4.4.3 fix

pack 3 or Tivoli NetcoolPerformance Manager

Removal of limitations (UBA packs only) 4.4.3fix pack 3 or Tivoli Netcool Performance

Manager

Upgradescenario 2

The Topology Editortreated the UBApack-specific propertysettings for theupgraded UBA pack asfree form, customsettings because therewas no XSD fileassociated with thedeployed UBA collector.Note: The TopologyEditor identifies customproperties with a checkmark in the Is Customcolumn of the Propertiesand AdvancedProperties tabs.

First, you load a technology pack XSD file intothe Topology Editor. Then, the Technology packXSD upgrade wizard is automatically startedwhen, in the Application Packs view, youright-click the Application Packs folder andselect Associate components with new AP fromthe menu. You associate one of the listed UBAcollectors with this technology pack XSD file.(You configured this UBA collector in 4.4.1 MR1or earlier, 4.4.1 fix pack 1 or later, or 4.4.2 andupgraded it to Tivoli Netcool/Proviso 4.4.3 fixpack 3 or Tivoli Netcool Performance Manager).The Technology pack XSD upgrade wizarddisplays:

v UBA pack-specific properties with Greencheck mark icons, indicating that the propertyvalues are valid. The wizard obtains thesevalues from the corresponding UBApack-specific parameters that are specified inthe dc.cfg file. You have the option to verifyand change these values.

v UBA pack-specific properties with Red Xicons for any properties where the XSD doesnot provide a default value or the value ismissing or is incorrect. Ideally, there must befew or zero properties with Red X iconswhere values are missing or are incorrect. Aproperty might display with a Red X icon ifthe XSD file defines a property without acorresponding parameter in the dc.cfg file.You use the Topology Editor Help to specifyappropriate values for all UBA pack-specificproperties that display with Red X icons.

v UBA pack-specific properties with a checkmark in the Is Custom column of theProperties and Advanced Properties tabs.Ideally, there must be few or zero customproperties.

Limitations with UBA pack-specific parameter key/value pairsDesign changes in Tivoli Netcool/Proviso 4.4.3 affect UBA pack-specific parameterkey/value pairs as follows:v Each UBA parameter key/value pair is limited to 40 characters.v Each UBA parameter key must be specified in uppercase.

Note: For the Alcatel-Lucent 5620 SAM Technology Pack, the previous limitationsalso apply to the BLB and SAMIF key/value pairs.


Before you begin a technology pack upgradeAbout this task

Before you upgrade a technology pack, ensure that you performed the followingsteps:

Procedurev Consulted the latest version of the Release Summary for Tivoli Netcool Performance

Manager. For more information about specific sections to consult before youperform the pack upgrade, see “Essential information in pack release notes” onpage 29.

v Consulted with your IBM Professional Services representative before youupgrade a technology pack. Your IBM Professional Services Representative usesthe documentation sources that are described in “Documents you need toperform a technology pack upgrade” on page 25.CAUTION:If you have a customized technology pack that is installed at your site withmodified content, it is overwritten if the same pack is upgraded to a laterversion. Check with your IBM customer service representative before youupgrade an existing technology pack to a later version.

v The correct version of Java. For more information, see “Essential information inpack release notes” on page 29.

Note: For 4.3-W and 4.3-X technology packs the launchpad requires you to enterthe path to supported Java runtime binaries. Only versions 1.4.2_b(17+) and1.5.0_b(14+) are supported. The Topology Editor provides a supported version ofthe Java binaries.

Note: Note: For 4.3-Y, 4.3-Z, 1.3-A technology packs the launchpad requires youto enter the path to supported Java runtime binaries. Only version 1.5.0_b(14+)is supported. The Tivoli Netcool/Proviso Topology Editor provides a supportedversion of the Java binaries. Using Java version 1.4 results in an error detailingthat it is not possible to proceed with the installation.

v Access to the product distribution site:https://www-112.ibm.com/software/howtobuy/softwareandservicesOn the product distribution site are the ProvisoPackInstaller.jar file, thebundled JAR file, and individual stand-alone technology pack JAR files.

v Access to the following site to check for interim fixes or fix packs that mightapply to your technology pack:http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.htmlFor more information, see “Documents you need to perform a technology packupgrade” on page 25.

v Access to the Tivoli Netcool Performance Manager documentation, technologypack user' guides, and technology pack release notes, which are available at thefollowing web site:http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_wln_tp.doc/wln_tech_pack_release_welcome.htmlFor more information about what to look for in the documents that are requiredfor pack upgrades, see “Documents you need to perform a technology packupgrade” on page 25.


https://www-112.ibm.com/software/howtobuy/softwareandservices





v Used the following GUI components that were introduced in TivoliNetcool/Proviso 4.4.3:– Topology Editor, including:

- How to work with UBA technology pack XSD files (see “Limitations withUBA pack-specific parameter key/value pairs” on page 32 for currentlimitations.)

- How to work with custom properties

Note: Because the Technology Pack XSD Upgrade wizard is included aspart of the Topology Editor in Tivoli Netcool/Proviso 4.4.3 fix pack 3 orTivoli Netcool Performance Manager, there is no need to start a separateutility. You start the Topology Editor as described in the 4.4.3 InstallingTivoli Netcool Performance Manager - Wireline Component. The Technologypack XSD Upgrade wizard is automatically started when, in theApplication Packs view, you right-click the Application Packs folder andselect Associate components with new AP from the menu. You areinstructed on how to do this in “Upgrading currently deployed UBAtechnology packs to 4.3-U or later” on page 36.

v Read and understood the upgrade scenarios that are described in this chapter.

Before you begin upgrade scenario 2 (UBA packs only)About this task

In addition to the prerequisite tasks described in “Before you begin a technologypack upgrade” on page 33, you must also perform the prerequisite tasks describedin the following sections before performing the steps described in “Upgradingcurrently deployed UBA technology packs to 4.3-U or later” on page 36.

Before you begin upgrading a currently deployed UBAtechnology pack to 4.3-U or laterAbout this task

Before you upgrade a currently deployed UBA technology pack to 4.3-U or later,ensure that you have done the following:v For UBA packs that require one UBA collector - Identified the UBA collector

subchannel that you configured for the pack.v For UBA packs that require multiple UBA collectors - Identified the UBA

collector subchannels that you configured for the pack.v For UBA packs that require a UBA collector, BLB (Bulk Load Balancer), and IF

(Inventory File) - Identified the UBA collector subchannel, BLB, and IF youconfigured for the pack.

You configured the UBA collector or collectors (and BLB and IF, if required) inTivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fix pack 1 or later, or 4.4.2 andupgraded it to Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli NetcoolPerformance Manager. The Topology Editor technology pack XSD upgrade wizardrequires you to select this UBA collector or collectors in one of the steps that aredescribed in “Upgrading currently deployed UBA technology packs to 4.3-U orlater” on page 36.


Table 12. Examples of identifying UBA collectors, BLB, and IF

Technology pack

UBA collectorconfigured for

technology packBLB/IF configured

for technology pack Comments

Ciena Transmission UBA.1.100 Not applicable The UBA collector forthis pack wasconfigured with achannel number of 1and a subchannelnumber of 100. TheTopology Editortechnology pack XSDupgrade wizarddisplays this UBAcollector as a choicein one of the stepsthat are described in“Upgrading currentlydeployed UBAtechnology packs to4.3-U or later” onpage 36.

Alcatel 5620 NM UBA.1.200 BLB.1.200 IF.1.200 The UBA collector forthis pack wasconfigured with achannel number of 1and a subchannelnumber of 200. Thetechnologypack-specificcomponents - theBLB and QCIF - werealso configured onchannel 1 andsubchannel 200. TheTopology Editortechnology pack XSDupgrade wizarddisplays this UBAcollector as a choicein one of the stepsthat are described in“Upgrading currentlydeployed UBAtechnology packs to4.3-U or later” onpage 36


Standard procedure for upgrading technology packsThe following sections discuss how to upgrade technology packs according to thefollowing scenarios:v “Upgrade scenario 1 (SNMP and UBA technology packs) (except Alcatel-Lucent

5620 SAM, Netflow IPFIX)”v “Upgrade scenario 2 (UBA packs only) (Including Alcatel-Lucent 5620 SAM,

Netflow IPFIX)” on page 41

Upgrade scenario 1 (SNMP and UBA technology packs)(except Alcatel-Lucent 5620 SAM, Netflow IPFIX)

About this task

You are currently running Tivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1 fixpack 1 or later, or 4.4.2. You want to do the following:v Upgrade to Tivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool

Performance Manager (which you do before performing the pack upgrade byfollowing the instructions in Upgrading Tivoli Netcool Performance Manager -Wireline Component that relates to your version of Tivoli Netcool PerformanceManager).

v Upgrade currently deployed technology packs to 4.3-U or later.

Important: See “Upgrading the Alcatel-Lucent 5620 SAM Technology Pack” onpage 22 and “Upgrading the Netflow IPFIX Technology Pack” on page 23 forinstructions on how to perform the upgrade scenarios for these technology packs.

Refer to the following sections for upgrade instructions:

Upgrading currently deployed SNMP technology packs to 4.3-Uor laterAbout this task

To upgrade currently deployed SNMP technology packs to 4.3-U or later, followthese steps:v Upgrade the technology pack to 4.3-U or later by installing the 4.3-U or later

SNMP pack, following the instructions in the appropriate technology packinstallation appendix provided in the 4.4.3 Installing Tivoli Netcool PerformanceManager - Wireline Component.

v Configure the 4.3-U or later SNMP technology pack you upgraded (installed), byreferring to the configuration chapter in the Installing Tivoli Netcool PerformanceManager - Wireline Component.


Upgrading currently deployed UBA technology packs to 4.3-U orlaterAbout this task

To upgrade currently deployed UBA technology packs to 4.3-U or later, followthese steps:


Procedure1. Complete the pre-installation setup tasks, as described in the appropriate

technology pack installation appendix that is provided in the 4.4.3 IBM TivoliNetcool Performance Manager: Installation Guide. These setup tasks describe howto download the ProvisoPackInstaller.jar file, any 4.3-U and laterstand-alone JAR files, and the 4.3-U and later bundled JAR file.

Important: Do not install any 4.3-U and later UBA technology packs yet. Youare asked to install 4.3- U and later technology packs in STEP 17.

2. Make sure that you have the available information that is described in “Beforeyou begin upgrade scenario 2 (UBA packs only)” on page 34

3. Open the Topology Editor.4. Open a deployed topology (a topology.xml file).5. After you click Finish, the topology is displayed in the Topology Editor.6. Load the UBA pack XSD file into the existing topology by following the

instructions that are provided in the 4.4.3 Installing Tivoli Netcool PerformanceManager - Wireline Component.

7. In the Application Packs view, right-click the Application Packs folder andselect Associate components with new AP from the menu.

Note: The technology pack XSD upgrade wizard is automatically startedwhen you right-click the Application Packs folder and select Associatecomponents with new AP from the menu.

8. Select a technology pack XSD file from the list of available technology packs.

Note: The technology packs that display in this list are the 4.3-U and laterpacks you downloaded in STEP 1.

9. Click Next to continue.10. The Create new AP from template and assign components window displays

every UBA collector subchannel that is not currently assigned to a technologypack.

Note: These UBA collectors were created in Tivoli Netcool/Proviso 4.4.1 MR1or earlier, 4.4.1 fix pack 1 or later, and 4.4.2. When you upgrade to TivoliNetcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool Performance Manager, theUBA collectors are not associated with any currently deployed UBAtechnology packs. The create new AP from template and assign componentswindow allows you to associate these UBA collectors with currently deployedpre-4.3-U technology packs.The new AP from template and assign components window displays thefollowing fields:v Create - A check box that directs the Topology Editor to associate the UBA

collector listed in the Collector ID field with the XSD file associated withthe technology pack selected from the Collector Template list.

v Collector ID - The list of UBA collector(s) that were added to the topologywhen you upgraded from Tivoli Netcool/Proviso 4.4.1 MR1 or earlier, 4.4.1fix pack 1 or later, or 4.4.2 to Tivoli Netcool/Proviso 4.4.3 fix pack 3 orTivoli Netcool Performance Manager. For example:UBA.1.100

If the technology pack you selected in STEP 8 has BLB (Bulk Load Balancer)and IF (Inventory File) components, this window displays only UBA collectorsubchannels that include the BLB and IF components. The Topology Editor


does not display BLB/IF components in the Collector Template list becauseno technology pack XSD defines more than one BLB and IF.

Note: These BLB and IF components were created in Tivoli Netcool/Proviso4.4.1 MR1 or earlier, 4.4.1 fix pack 1 or later, and 4.4.2. When you upgrade toTivoli Netcool/Proviso 4.4.3 fix pack 3 or Tivoli Netcool PerformanceManager, the BLB and IF components (and their associated UBA collectors) arenot associated with any currently deployed UBA technology packs. The createnew AP from template and assign components window allows you toassociate these UBA collectors and their associated BLB and IF componentswith currently deployed pre-4.3-U technology packs. The Topology Editorautomatically associates a UBA collector with its associated BLB and IFcomponents when you load a technology pack XSD file that defines thesecomponents.

11. To associate a UBA collector with a UBA technology pack, follow these steps:a. Check the box in the Create field associated with a UBA collector

subchannel listed in the Collector ID field. You must have identified thisUBA collector for a currently deployed pack, as described in “Before youbegin upgrading a currently deployed UBA technology pack to 4.3-U orlater” on page 34.

b. Select a technology pack from the Collector Template list. You must haveidentified this UBA pack, as described in “Before you begin upgrading acurrently deployed UBA technology pack to 4.3-U or later” on page 34.

c. Repeat STEP 11-a and STEP 11-b for each UBA collector subchannel youwant to associate with a technology pack.

d. Click Finish to continue.12. Verify that each UBA collector is associated with the technology pack you

selected in STEP 8. To do this, select technology packs view in the TopologyEditor. The UBA collector displays under the specified technology pack, forexample:Collector UBA 1.100

13. The Topology Editor also displays each UBA collector under the DataChannelx folder in the Logical view. Highlight the collector to view its properties. TheTopology Editor displays both the UBA collector core parameters and the UBAtechnology pack-specific parameters. The core parameters are configured withall UBA technology packs. For information about the core properties, see theIBM Tivoli Netcool Performance Manager: Properties Reference.The Topology Editor displays the UBA technology pack-specific propertiesaccording to the rules specified in Table 11 on page 32. Do the following:a. Verify the values for the UBA technology pack-specific properties that are

displayed with Green check mark icons. To illustrate how you might verifythe technology pack-specific properties, Table 13 on page 40 provides amapping of some dc.cfg file parameters to Topology Editor properties forthe Ciena Transmission technology pack. The comments in the tableprovide more guidelines that you can use to help verify the properties inyour technology pack.For information about the pack-specific properties, see the Topology EditorHelp.

b. Determine whether the UBA technology pack-specific properties displayedwith Red X icons are valid. See Table 11 on page 32 for guidelines on howto deal with these types of properties.

c. Determine whether the UBA technology pack-specific properties that aredisplayed in the Is Custom column of the Properties and Advanced


Properties tabs are valid. See Table 11 on page 32 for guidelines on how todeal with these types of properties. To delete a custom property, see STEP14. To add a custom property, see STEP 15.

14. (Optional) If you must delete (remove) a custom property, follow these steps:a. Open the Topology Editor.b. Open the topology that is associated with the UBA pack you upgraded.c. In the Application Packs view, select the UBA pack that you upgraded.d. Display the COLLECTOR_UBA.x.x entry. The DataChannel core and

pack-specific parameters display in the properties window.e. Select the pack-specific UBA custom property to remove in the Properties

or Advanced Properties tab.f. Click the Remove Custom Property button (a Red X icon that appears in

the Property view).15. (Optional) If you must add a custom property, follow these steps:

a. Open the Topology Editor.b. Open the topology that is associated with the UBA pack you upgraded.c. In the Application Packs view, select the UBA pack that you upgraded.d. Display the COLLECTOR_UBA.x.x entry. The DataChannel core and

pack-specific properties display in the properties window.e. Select the blue + (plus) icon that displays at the right top corner of the

properties window. The Add Custom Property for UBA Collector wizarddisplays.

f. The wizard displays three fields:v Name - Specifies the pack-specific UBA property to associate with a UBA

pack subelement.v Value - Specifies the value that is associated with this pack-specific UBA

property.v Alias - Specifies the name of the property that the Topology Editor

displays in the Property View. Valid values include the pack-specificUBA property name that is specified in the Name field or descriptivetext.

g. Specify the name of the new UBA pack-specific parameter in the Namefield. In this example, the name that is specified would beERRORFILEMAX.

Note: Do not enter the channel number (<CHANNEL>, collector number<COLLECTOR>, instance (UNIV_WAN_MGR), and schema (AVAIL) in the Namefield.

h. Specify a value in the Alias field according to the previously discussedguidelines. In this example, ERRORFILEMAX is specified.

i. Click Finish.16. Specify the name of the new UBA pack-specific parameter in the Name field.

In this example, the name that is specified would be ERRORFILEMAX.17. Upgrade the currently deployed pre-4.3-U technology pack or packs by

installing the 4.3-U or later version of the pack or packs, following theinstructions in the appropriate technology pack installation appendix that isprovided in the IBM Tivoli Netcool Performance Manager: Installation Guide.

Note: You downloaded the 4.3-U or later version of the currently deployedpre-4.3-U technology pack or packs in STEP 1.


Note: Because there is an existing UBA collector, you can skip the section thatdescribes how to add UBA collectors. You associated these UBA collectorswith pre-4.3-U technology packs in STEP 11.

18. Configure the UBA technology pack that you upgraded, by referring to theconfiguration chapter in IBM Tivoli Netcool Performance Manager: Installation andConfiguration Guide.

Note: Technology packs do not work unless they are configured.

Table 13. Example mappings for Ciena Transmission Technology Pack

dc.cfg fileparameter

Topology Editorproperty Comments

UBA.1.100.INSTANCES=streaming

INSTANCES=CIENA_DEVICE

The Topology Editor displays the INSTANCES propertywith a Green check mark icon and the value asspecified in the dc.cfg file. The INSTANCES parameterused to be an arbitrary string as illustrated by thestring streaming specified in the dc.cfg file parameter.The convention now is to use a string that representsthe name of the technology pack, as illustrated by theTopology Editor property value, CIENA_DEVICE.

Some more recent technology packs deliver withtemplate files that specify INSTANCES parameters withstrings that represent the names of the technologypacks.Note: The INSTANCES property is read-only. In thiscase, either value - arbitrary string or pack namestring - that the Topology Editor obtains from thedc.cfg file is valid.Note: It is not necessary to specify the channelnumber, collector number, and schema in the valuesfor the Topology Editor properties.

UBA.2.100.streaming.DESIGNFILE=CienaAdaptor.js

CIENA_DEVICE.DESIGNFILE=CienaAdaptor.js

The Topology Editor must display the DESIGNFILEproperty with a Green check mark icon and the stringthat identifies the name of the Bulk Adaptor Designfile as specified in the dc.cfg file.

The name of the Bulk Adaptor Design file (in this case,CienaAdaptor.js) must be the same in both thetemplate file parameter and the Topology Editorproperty.Note: The DESIGNFILE property is read-only.


Table 13. Example mappings for Ciena Transmission Technology Pack (continued)

dc.cfg fileparameter

Topology Editorproperty Comments

UBA.2.100.streaming.CEMS.URI=file:///export/home/pvuser/uba_files/CEMS/input/*.csv

CIENA_DEVICES.CEMS.URI=$5ftp://$1:$2@$3/ $4/*.csvCIENA_DEVICES.CEMS.URI=file:///export/home/pvuser/uba_files/CEMS/input/*.csv

The Topology Editor must display the URI propertywith a Green check mark icon and the value asspecified in the dc.cfg file, in this case a URLspecification that directs the UBA to the location forthe Bulk input files (in this case, *.csv files).

The Topology Editor displays the URI property asread-only and its associated value is a concatenation ofthe following properties defined in the pack XSD file:

v INPUT_USE_SECURE_FTP ($5)

v INPUT_FTP_HOST ($3)

v INPUT_FTP_USERNAME ($1)

v INPUT_FTP_PASSWORD ($2)

v INPUT_DIRECTORY ($4)

Note: The values ($1 through $5) specified here aretaken from the Ciena Transmission Technology PackXSD file to show the concatenation of properties. TheTopology Editor must display the INPUT-relatedproperties with Red X icons because the pack XSD filedoes not provide default values for these properties.

It is recommended that you specify values for theINPUT-related properties by using the guidelines thatare provided by the Topology Editor Help.

UBA.2.100.streaming.DELETEONACQUIRE=false

CIENA_DEVICE.CEMS.DELEATEONACQUIRE=false

The Topology Editor must display theDELETEONACQUIRE property with a Green check markicon and the value as specified in the dc.cfg file, inthis case the value false.In this example, the DELETEONACQUIRE parameter in thedc.fg file and the Topology Editor property have thesame value (false). This might not always be the case.

The Topology Editor displays the DELETEONACQUIREproperty as read/write. Therefore, you can change thevalue of this property by using the Topology Editor.

Upgrade scenario 2 (UBA packs only) (IncludingAlcatel-Lucent 5620 SAM, Netflow IPFIX)

The Topology Editor maintains the association with the existing XSD file.Therefore, it verifies the values currently specified for the UBA pack-specificproperty settings.

Before you beginv Currently, you deployed 4.3-V UBA technology packs running on Tivoli

Netcool/Proviso 4.4.3.v Completed the update of Tivoli Netcool/Proviso 4.4.3 to Tivoli Netcool/Proviso

4.4.3 fix pack 3 or Tivoli Netcool Performance Manager by following theinstructions in the Fix pack ReadMe.

v Want to upgrade currently deployed 4.3-V technology packs to 4.3-X or later.

About this task

To upgrade currently deployed 4.3-V technology packs to 4.3-X or later, followthese steps:


Procedure1. Update the UBA technology pack metadata by following these steps:

a. Open the Topology Editor.b. Create a new empty topology by selecting File > Create new topology.

Retain the default number of resources as this operation is only necessary topopulate the Application Packs view.

c. In the Application Packs view, right-click the Application Packs folder andselect Load Application Pack from the menu.

d. Navigate to the directory where you copied the new stand-alone (orbundled) JAR file. The Topology Editor displays a message warning that theXSD exists. The message also asks if you want to replace the XSD. Specifythat you want to replace the XSD.

e. After replacing the XSD, close the Topology Editor. You successfullyreplaced the UBA technology pack metadata.

2. Reopen the Topology Editor and select the existing deployed topology(topology.xml). The UBA pack-specific properties are applied to the existingdeployed topology according to the following rules:v Properties that were added to the pack XSD displays in the Property tab

with their default values. You can modify, if necessary, any writableproperties.

v Properties that were removed in the XSD shows in the Property tab ascustom properties. If not needed, you can remove these properties byfollowing these instructions:

a. Open the Topology Editor.b. Open the topology associated with the UBA pack you upgraded.c. In the Application Packs view, select the UBA pack you upgraded.d. Display the COLLECTOR_UBA.x.x entry. The DataChannel core and


Advanced Properties tab.f. Click the Remove Custom Property button (a red X icon that appears in the

Property view).3. Redeploy the updated topology, as described in the 4.4.3 Installing Tivoli

Netcool Performance Manager - Wireline Component.4. Use the dccmd command to stop the UBA application:

dccmd -action stop UBA

5. Upgrade the 4.3-V UBA technology pack to 4.3-X or later by following theinstructions provided in the pack installation chapter of the 4.4.3 InstallingTivoli Netcool Performance Manager - Wireline Component.

Note: Because there is an existing UBA collector, you can skip the section thatdescribes how to add UBA collectors.

6. Configure the UBA technology pack you upgraded, by referring to theconfiguration appendix of the appropriate Configuring Technology Packs. Oneof the configuration steps instructs you to restart the DataChannel to activatethe UBA and read in changes to the deployed topology.


Note: Starting with version 4.3-X, the Alcatel-Lucent 5620 SAM TechnologyPack requires you to configure two UBA Bulk Collectors. For information about


how to configure additional UBA Bulk Collectors, see the Installing TivoliNetcool Performance Manager - Wireline Component. For more informationabout this configuration change, see IBM Tivoli Netcool Performance Manager:Alcatel-Lucent 5620 SAM 2.11.0.0 Technology Pack User Guide.

Upgrading to Alcatel-Lucent 5620 SAM LogToFile 2.5.0.0This chapter contains steps that are needed to upgrade to Alcatel-Lucent 5620 SAMLogToFile 2.5.0.0.

Upgrading the Alcatel-Lucent 5620 SAM LogToFile 2.4.0.0Technology Pack to Alcatel-Lucent 5620 SAM LogToFile 2.5.0.0You can upgrade the Alcatel-Lucent 5620 SAM 2.4.0.0 Technology Pack toAlcatel-Lucent 5620 SAM LogToFile 2.5.0.0.

About this task

To upgrade the Alcatel-Lucent 5620 SAM 2.4.0.0 Technology Pack to Alcatel-Lucent5620 SAM LogToFile 2.5.0.0.

Procedure1. Upgrading the DataStage Job

a. Stop the Job by referring to Gracefully shutting down the job section.b. Move the existing udm directory inside UDM project to udm_bk.c. Create a directory by name udm inside the project that being created by

using the following commands:$ cd /opt/IBM/InformationServer/Server/Projects/UDM$ umask 002$ mkdir udm

d. Extract the alcatel_5620_sam_ds_vm.n.0.0_build_b.tar.gz file in/opt/IBM/InformationServer/Server/Projects/UDM/udm by using thefollowing command:$ tar -zxvf alcatel_5620_sam_ds_vm.n.0.0_build_b.tar.gz

e. Configuration files under udm/cfg folder will have default configuration,change it as per requirements.

f. Copy samOss.jar file to IBM InfoSphere Information Server. The samOss.jarfile is distributed on a SAM distribution DVD which referred to as the 5620SAM software DVD-ROM. It is available in the followingdirectory<SAM_ROOT_RELEASE_DIR>/nms/integrations/SAM_O . Please copy thesamOss.jar file from the directory on the DVD to /opt/IBM/InformationServer/Server/Projects/UDM/udm/jar directory.

g. Importing DataStage job in DataStage Designer Client. Refer to Importing anIBM InfoSphere DataStage job section.

h. Run the DataStage job from Director Client. Refer to Running the job section2. Upgrading Technology Pack

a. Stop the DataChannel:1) Start a terminal emulator on the DataChannel server2) Run the dccmd command to stop all the DataChannel applications:

$ dccmd stop all

3) Run the following command to find the process identifiers (pids) thatare associated with the DataChannel visual processes:$ findvisual


4) Run the following commands to remove the files:$ kill -9 <cnsw_pid>$ kill -9 <logw_pid>$ kill -9 <amgrw_pid>$ kill -9 <cmgrw_pid>

b. Run the following commands to remove the files:v /opt/proviso/datachannel/bin

rm –rf *_visual

v /opt/proviso/datachannel/staterm –rf *pidrm -rf *_visual

v /opt/proviso/datachannel/logrm –rf *log

c. Create backup of the DataChannel directories and do not delete them fromthe original location.

d. Install the Alcatel-Lucent 5620 SAM LogToFile 2.4.0.0 Technology Pack. Formore information, see Installing Technology Packs guide.

e. Start the Topology Editor and load the technology pack from the JAR file.f. Check the properties set in the UBA Collectors. Modify the value

accordingly for the upgrade environment, if needed.g. Save the topology.h. Run the deployer to complete the installation.i. Start the Request Editor, set to inactive, and then Save.j. Update the polling time to 5 Minutes or 15 Minutes, set to active, and then

click Save

k. Run the following commands to restart each DataChannel visual process:$ cnsw$ logw$ amgrw$ cmgrw

l. Run the dccmd command to start all the DataChannel applications:$ dccmd start all

m. Compile the uba profiles.n. Run the auto-grouping again after the full dump process is completed for

the first time.

Upgrading Alcatel-Lucent 5670 RAMThis chapter contains steps that are needed to upgrade the Alcatel-Lucent 5670RAM technology pack.

Upgrading to Alcatel-Lucent 5670 RAM 2.2.0.0In this topic, you will learn about the steps that are needed to upgrade theAlcatel-Lucent 5670 RAM technology pack from version 2.1.0.0 to 2.2.0.0. Toupgrade the technology pack:

Procedure1. Restore the files:

a. Go to the APFIles directory at /opt/datamart/.b. Rename the alcatel_5670_ram directory to alcatel_5670_ram_2.1.0.0.


2. Add the UBA collector. For details on how to add a UBA collector, see Adding aUBA collector for a UBA pack in Installing technology packs>Installing a technologypack>UBA collectors: Pack Installation and Configuration Guide.

3. Configure the technology pack. For details on how to configure the technologypack, see Configuring UBA Technology Packs in Configuring technology packs: PackInstallation and Configuration Guide.

4. Restore the samInventory and ramAdaptor directories of the base pack:

Important: Make sure that the last samInventory file at the hour is picked upby UBA, for example, for the file that is with 15 minutes interval, the last file ofthat hour is at 45 minutes.a. After the last samInventory file at the hour is picked up, stop the

samInventory and ramAdaptor processes.b. Rename the samInventory directory to samInventory_2.1.0.0, and the

ramAdaptor directory to ramAdaptor_2.1.0.0.5. Complete the upgrade procedure by following the additional configuration

steps that are available in Alcatel-Lucent 5670 RAM Technology Pack in Additionalconfiguration steps for certain UBA Technology Packs: Pack Installation andConfiguration Guide.

Important: Make sure that the samInventory and ramAdaptor processes arestarted at 50 minutes of the hour.

6. After you start the samInventory and ramAdaptor processes, start all the dccmdand CORBA processes.

Upgrading Huawei U2000 DSLAM Technology PackThis section explains how to upgrade Huawei U2000 DSLAM 2.2.0.0 TechnologyPack to Huawei U2000 2.1.0.0 Technology Pack.

Before you begin

Before you upgrade Huawei U2000 DSLAM 2.2.0.0 Technology Pack to HuaweiU2000 2.1.0.0 Technology Pack, you must remove the existing reports that arelinked to Huawei U2000 DSLAM 2.2.0.0 Technology Pack.

To remove the existing reports that are linked to Huawei U2000 DSLAM 2.2.0.0Technology Pack, follow these steps:1. Source the dataMart.env file by using the following command:

source /opt/datamart/dataMart.env

2. Start the DataMart GUI by using the following command:pvm &

3. Click the Resource tab, and then click Resource Editor to open the ResourceEditor.

4. Click the Report SE Group tab.5. Move the cursor to the left pane and click SUB-ELEMENTS > NOC

Reporting > Huawei U2000 > DSLAM > Ethernet. You can see reports thatare assigned to Ethernet on the right side.

6. Select all the reports and press Ctrl+X. The following message is displayed:Unlink <n> Report SE Group(s) of ~NOC Reporting~Huawei U2000~DSLAM~Ethernet:Are you Sure?

7. Click Yes to confirm. The reports are removed.


8. Move the cursor to the left pane and from the Ethernet folder, clickRU_%(Element.Name). You can see reports that are assigned toRU_%(Element.Name) on the right side.

9. Select all the reports and press Ctrl+X. The following message is displayed:Unlink <n> Report SE Group(s) of ~NOC Reporting~Huawei U2000~DSLAM~Ethernet~RU_%(Element.Name):Are you Sure?

10. Click Yes to confirm. The reports are removed.11. Close the DataMart GUI.

To upgrade Huawei U2000 DSLAM 2.2.0.0 Technology Pack to Huawei U20002.1.0.0 Technology Pack, follow these steps:

Procedure1. Log on as the root user.2. Change your working directory by using the following command:

cd /opt/IBM/proviso/topologyEditor

3. Start the topology editor by using the following command:./topologyEditor &

4. Load topology from the database by following these steps.a. In the topology editor, click Topology > Open existing topology. From the

Open topology window, select the From database radio button and clickNext.

b. Enter the password in the Database Password field in the Open topologywindow and click Next. The Topology loaded successfully message isdisplayed on the Open topology window.

5. Remove the Huawei U2000 DSLAM collector by following this step.v From the Logical View tab, click Netcool/Proviso Topology >

DataChannels > DataChannel 1. Right-click the <collector_name> andselect Remove. The Huawei U2000 DSLAM collector is removed from theTopology editor.

Note: The <collector_name> here indicates the name that is assigned to theHuawei U2000 DSLAM collector.

6. Load the Huawei U2000 2.1.0.0 Technology Pack by following these steps.a. From the Technology Packs tab, right-click the Technology Packs folder

and select Load Technology Pack. The Load Technology Pack window isdisplayed.

b. In Load Technology Pack window, select XSD file radio button. Browsefor the .xsd file by using the Browse button and click Finish.

7. Add the Huawei U2000 collector by following these steps.a. From the Logical View tab, click Netcool/Proviso Topology >

DataChannels. Right-click DataChannel 1 and select Add Collector UBA.The Configure Collector window is displayed.

b. In the Configure Collector window, select Huawei U2000 from the list andclick Next.

c. Enter the collector number (that you used for the Huawei U2000 DSLAMTechnology Pack) in the Select the collector number field and click Finish.


d. From the Logical View tab, click Netcool/Proviso Topology >DataChannels > DataChannel 1 > <collector_name> ><collector_UBA_name>. The properties of Huawei U2000 Technology Packare displayed on the right side.

e. Enter the appropriate values for .csv input file password, user name, host,and directory in the HUAWEI_U2000.INPUT_FTP_PASSWORD,HUAWEI_U2000.INPUT_FTP_USERNAME,HUAWEI_U2000.INPUT_FTP_HOST, andHUAWEI_U2000.INPUT_FTP_DIRECTORY fields.

8. Click Topology > Save topology.9. Click Topology > Exit.

10. Start the topology editor again and reload the topology.11. Click Run > Run Deployer for Installation and follow the on-screen

instructions.12. Click Topology > Exit.



Notices

This information was developed for products and services that are offered in theUSA.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785United States of America

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationDepartment number/Building numberSite mailing address_City, State; Zip Code_USA (or appropriate country)

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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

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

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

Portions of this code are derived from IBM Corp. Sample Programs.

© Copyright IBM Corp. _enter the year or years_. All rights reserved.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

Notices 51

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.


http://www.ibm.com/legal/us/en/copytrade.shtml

http://www.ibm.com/legal/us/en/copytrade.shtml

Additional copyright noticesThe following copyright information is for software used by Tivoli NetcoolPerformance Manager Wireline Component.

Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3

This software is copyrighted by the Regents of the University of California, SunMicrosystems, Inc., Scriptics Corporation, and other parties. The following termsapply to all files associated with the software unless explicitly disclaimed inindividual files.

The authors hereby grant permission to use, copy, modify, distribute, and licensethis software and its documentation for any purpose, provided that existingcopyright notices are retained in all copies and that this notice is included verbatimin any distributions. No written agreement, license, or royalty fee is required forany of the authorized uses. Modifications to this software may be copyrighted bytheir authors and need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANYPARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIALDAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITSDOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THEAUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN"AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,ENHANCEMENTS, OR MODIFICATIONS.

GOVERNMENT USE: If you are acquiring this software on behalf of the U.S.government, the Government shall have only "Restricted Rights" in the softwareand related documentation as defined in the Federal Acquisition Regulations(FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of theDepartment of Defense, the software shall be classified as "Commercial ComputerSoftware" and the Government shall have only "Restricted Rights" as defined inClause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authorsgrant the U.S. Government and others acting in its behalf permission to use anddistribute the software in accordance with the terms specified in this license.

SCOTTY Stack

This software is copyrighted by Juergen Schoenwaelder, the Technical University ofBraunschweig, the University of Twente, and other parties. The following termsapply to all files associated with the software unless explicitly disclaimed inindividual files.

The authors hereby grant permission to use, copy, modify, distribute, and licensethis software and its documentation for any purpose, provided that existingcopyright notices are retained in all copies and that this notice is included verbatimin any distributions. No written agreement, license, or royalty fee is required forany of the authorized uses. Modifications to this software may be copyrighted by

Notices 53

their authors and need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file where they apply.


THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN“AS IS” BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,ENHANCEMENTS, OR MODIFICATIONS.

Various copyrights apply to this package, listed in 3 separate parts below. Pleasemake sure that you include all the parts. Up until 2001, the project was based atUC Davis, and the first part covers all code written during this time. From 2001onwards, the project has been based at SourceForge, and Networks AssociatesTechnology, Inc hold the copyright on behalf of the wider Net-SNMP community,covering all derivative work done since then. An additional copyright section hasbeen added as Part 3 below also under a BSD license for the work contributed byCambridge Broadband Ltd. to the project since 2001.

Part 1: CMU/UCD copyright notice: (BSD like)

Copyright © 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright © 1996, 1998-2000 The Regents of the University of California

All Rights Reserved

Permission to use, copy, modify and distribute this software and its documentationfor any purpose and without fee is hereby granted, provided that the abovecopyright notice appears in all copies and that both that copyright notice and thispermission notice appear in supporting documentation, and that the name of CMUand The Regents of the University of California not be used in advertising orpublicity pertaining to distribution of the software without specific writtenpermission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIMALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALLIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENTSHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BELIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES ORANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATAOR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OROTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITHTHE USE OR PERFORMANCE OF THIS SOFTWARE.

Part 2: Networks Associates Technology, Inc copyright notice (BSD)


Copyright © 2001, Networks Associates Technology, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:v Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.v Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.

v Neither the name of the NAI Labs nor the names of its contributors may be usedto endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Part 3: Cambridge Broadband Ltd. copyright notice (BSD)

Portions of this code are copyright © 2001, Cambridge Broadband Ltd.


Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:v Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.v Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.

v The name of Cambridge Broadband Ltd. may not be used to endorse or promoteproducts derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THECOPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

Notices 55

STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BLT 2.4u

Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 SunMicrosystems, Inc., and (c) 1987-1993 The Regents of the University of California.

Permission to use, copy, modify and distribute this software and its documentationfor any purpose and without fee is hereby granted, provided that the abovecopyright notice appears in all copies and that both that copyright notice and thispermission notice appear in supporting documentation, and that the names ofAT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and The Regents of theUniversity of California not be used in advertising or publicity pertaining todistribution of the software without specific written permission.

THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALLWARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALLIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENTSHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLEFOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANYDAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA ORPROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OROTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITHTHE USE OR PERFORMANCE OF THIS SOFTWARE.

CMU-SNMP 1.14

CMU/UCD copyright notice: (BSD like)

Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of theUniversity of California

All Rights Reserved




Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2

Portions Copyright (c) 1987-1994 The Regents of the University of California.Copyright (c) 1994-1995 Sun Microsystems, Inc.

This software is copyrighted by the Regents of the University of California, SunMicrosystems, Inc., and other parties. The following terms apply to all filesassociated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and licensethis software and its documentation for any purpose, provided that existingcopyright notices are retained in all copies and that this notice is included verbatimin any distributions. No written agreement, license, or royalty fee is required forany of the authorized uses. Modifications to this software may be copyrighted bytheir authors and need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file where they apply.


THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN"AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subjectto the restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in TechnicalData and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-19.

Portions Copyright (c) 1993-1998 Lucent Technologies, Inc.

Permission to use, copy, modify, and distribute this software and its documentationfor any purpose and without fee is hereby granted, provided that the abovecopyright notice appear in all copies and that both that the copyright notice andwarranty disclaimer appear in supporting documentation, and that the names ofLucent Technologies any of their entities not be used in advertising or publicitypertaining to distribution of the software without specific, written priorpermission.

Lucent disclaims all warranties with regard to this software, including all impliedwarranties of merchantability and fitness. In no event shall Lucent be liable for anyspecial, indirect or consequential damages or any damages whatsoever resultingfrom loss of use, data or profits, whether in an action of contract, negligence orother tortuous action, arising out of or in connection with the use or performanceof this software.

Notices 57

UCD SNMP 4.2.5

Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University. DerivativeWork - 1996, 1998-2000, Copyright 1996, 1998-2000 The Regents of the University ofCalifornia All Rights Reserved



Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c)2001-2003, Cambridge Broadband Ltd, (c) 2003-2005, Sparta, Inc., (c) 2004, Cisco,Inc and Information Network Center of Beijing University of Posts andTelecommunications, (c) Fabasoft R&D Software GmbH & Co KG, [email protected].


Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list ofconditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, thislist of conditions and the following disclaimer in the documentation and/or othermaterials provided with the distribution.

3. Neither the names of Networks Associates Technology, Inc, CambridgeBroadband Ltd., Sparta, Inc., Cisco, Inc, Beijing University of Posts andTelecommunications, Fabasoft R&D Software GmbH & Co KG or any of itssubsidiaries, brand or product names, nor the names of their contributors may beused to endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT


NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

JDOM 1.0

Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list ofconditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, thislist of conditions, and the disclaimer that follows these conditions in thedocumentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products derivedfrom this software without prior written permission. For written permission, pleasecontact <request_AT_jdom_DOT_org>.

4. Products derived from this software may not be called "JDOM", nor may"JDOM" appear in their name, without prior written permission from the JDOMProject Management <request_AT_jdom_DOT_org>.

In addition, we request (but do not require) that you include in the end-userdocumentation provided with the redistribution and/or in the software itself anacknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project(http://www.jdom.org/)." Alternatively, the acknowledgment may be graphicalusing the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS ORTHE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

This software consists of voluntary contributions made by many individuals onbehalf of the JDOM Project and was originally created by Jason Hunter<jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>.For more information on the JDOM Project, please see <http://www.jdom.org/>.

Notices 59

Regex 1.1a

Copyright (C) 1996, 1999 Vassili Bykov. It is provided to the Smalltalk communityin hope it will be useful.

1. This license applies to the package as a whole, as well as to any component of it.By performing any of the activities described below, you accept the terms of thisagreement.

2. The software is provided free of charge, and `às is'', in hope that it will beuseful, with ABSOLUTELY NO WARRANTY. The entire risk and all responsibilityfor the use of the software is with you. Under no circumstances the author may beheld responsible for loss of data, loss of profit, or any other damage resultingdirectly or indirectly from the use of the software, even if the damage is caused bydefects in the software.

3. You may use this software in any applications you build.

4. You may distribute this software provided that the software documentation andcopyright notices are included and intact.

5. You may create and distribute modified versions of the software, such as portsto other Smalltalk dialects or derived work, provided that:

a. any modified version is expressly marked as such and is not misrepresented asthe original software;

b. credit is given to the original software in the source code and documentation ofthe derived work;

c. the copyright notice at the top of this document accompanies copyright noticesof any modified version.


Notices 61

IBM®

Printed in USA