IBM Tivoli Netcool Manager Wireline Component October Document Revision R2E1 Pack Release Notes
Note Before using this information and the product it supports, read the information in Notices on page 43. Copyright IBM Corporation 2006,. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Introduction............. v Intended audience............ v Tivoli Netcool Manager - Wireline Component............... v What this information contains........ vi Pack documentation........... vii Service Management Connect........ vii Tivoli Netcool Manager technical training............... vii Support information........... viii Conventions used in this publication..... viii Typeface conventions.......... viii Release summary.......... 1 Features and changes of this release...... 1 New technology packs.......... 1 New common packs........... 1 Updated technology packs......... 1 IPv6 address support.......... 2 Functional changes to technology packs.... 3 Installation and configuration of packs...... 4 Packs in this release........... 5 Supported SAM server versions....... 5 Installation and configuration notes for technology packs................ 7 Upgrade technology packs......... 13 Critical technology pack upgrade notes.... 13 Technology pack upgrade notes...... 14 Latest versions of supported packs...... 20 List of latest supported packs....... 20 Interim fixes and fix packs......... 40 Interim fixes for Tivoli Netcool Manager v1.4............. 40 Interim fixes for Tivoli Netcool Manager v1.3.2............ 40 Interim fixes for Tivoli Netcool Manager v1.3.1............ 41 Interim fixes for Tivoli Netcool Manager v1.3............. 41 Interim fixes for Tivoli Netcool/Proviso v4.4.3.3 42 Interim fixes for Tivoli Netcool/Proviso v4.4.3.2 42 Notices.............. 43 Additional copyright notices..... 47 Copyright IBM Corp. 2006, iii
iv IBM Tivoli Netcool Manager: Pack Release Notes
Introduction Intended audience These release notes support the July release of the IBM Tivoli Netcool Manager Technology Packs and Common Packs. The audiences for this guide are the network administration engineers at IBM customer sites who install, configure, and use technology packs and common packs as part of their Tivoli Netcool Manager installation. IBM Professional Services engineers might also find the guide useful. To install and use technology packs, you must have a working knowledge of the following subjects: v Tivoli Netcool Manager DataMart v TCP/IP networks v Telecommunications network management v Administration of the operating system The audiences must be familiar with the specific technology associated with the technology packs. To install and use common packs, you must have a working knowledge of the following subjects: v IBM Tivoli Common Reporting or IBM Cognos v IBM Cognos Framework Manager v IBM Model Maker that is delivered in Tivoli Netcool Manager v1.3.2. The audiences must be familiar with the specific technology associated with the common packs. Tivoli Netcool Manager - Wireline Component IBM Tivoli Netcool Manager consists of a wireline component (formerly Netcool/Proviso) and a wireless component (formerly Tivoli Netcool Manager for Wireless). Tivoli Netcool Manager - Wireline Component consists of the following subcomponents: v v v v DataMart is a set of management, configuration, and troubleshooting GUIs. The Tivoli Netcool Manager System Administrator uses the GUIs to define policies and configuration, and to verify and troubleshoot operations. DataLoad provides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. DataChannel aggregates the data collected through Tivoli Netcool Manager DataLoad for use by the Tivoli Netcool Manager DataView reporting functions. It also processes online calculations and detects real-time threshold violations. DataView is a reliable application server for on-demand, web-based network reports. Copyright IBM Corp. 2006, v
v Technology Packs extend the Tivoli Netcool Manager system with service-ready reports for network operations, business development, and customer viewing. The following figure shows the different Tivoli Netcool Manager modules. Tivoli Netcool Manager documentation consists of the following: v Release notes v Configuration recommendations v Installation and upgrade information v User guides v Technical notes v Online help The documentation is available for viewing and downloading on the information center at http://www-01.ibm.com/support/knowledgecenter/ssbnj7_1.3.2/ com.ibm.tnpm.doc/welcome_tnpm.html. What this information contains This publication is organized as follows: v Features and changes of this release on page 1 Provides a general introduction to this pack release and the specific contents of the release. Also describes features and changes associated with new and updated packs for this release. v Installation and configuration of packs on page 4 Provides information related to installing and configuring packs. v Upgrade technology packs on page 13 Provides information related to upgrading technology packs. v Latest versions of supported packs on page 20 Provides a table that lists all the details in the supported packs. v Interim fixes and fix packs on page 40 Lists the interim fixes and fix packs for specific packs. vi IBM Tivoli Netcool Manager: Pack Release Notes
Pack documentation Tivoli Netcool Manager user documentation includes technical notes, and release notes for previous technology pack and common pack releases, and the other documentation types listed in Tivoli Netcool Manager - Wireline Component on page v. The user documentation for the Tivoli Netcool Manager technology packs (and for the core software) is available from the following information centers: Product Tivoli Netcool Manager (Core software) Tivoli Netcool Manager (Technology Packs) Information center 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_wln_tp.doc/ wln_14a_tech_pack_welcome.html?lang=en Starting with 1.3-E release, new, and updated technology packs include reference documentation in the CD distribution for the pack, which can be downloaded from the IBM Passport Advantage site. Technology Pack User Guide is deprecated and the configuration information is moved to Configuring Technology Packs. Configuration and Installation information for Alcatel-Lucent 5620 SAM LogToFile 2.4.0.0 Technology Pack is now available in Installing Technology Packs and Configuring Technology Packs. Service Management Connect Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise. Access Network and Service Assurance community at https://www.ibm.com/ developerworks/servicemanagement/nsa/index.html. Use Service Management Connect in the following ways: v Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. v Connect one-on-one with the experts to collaborate and network about Tivoli and the Network and Service Assurance community. v Read blogs to benefit from the expertise and experience of others. v Use wikis and forums to collaborate with the broader user community. Related information: Tivoli Netcool Manager 1.4 community on developerworks Tivoli Netcool Manager technical training For Tivoli Netcool Manager technical training information, see the following Tivoli Netcool Manager Training website at: https://tnpmsupport.persistentsys.com/training. Introduction vii
Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at http://www.ibm.com/software/ support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to http://www.ibm.com/software/ support/isa. Troubleshooting Guide For more information about resolving problems, see the problem determination information for this product. Conventions used in this publication Several conventions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system. Typeface conventions This publication uses the following typeface conventions: Bold Italic v v v v v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) Keywords and parameters in text Citations (examples: titles of publications, diskettes, and CDs) Words defined in text (example: a nonswitched line is called a point-to-point line) v Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data. v Variables and values you must provide:... where myname represents... Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type viii IBM Tivoli Netcool Manager: Pack Release Notes
v Values for arguments or command options Bold monospace v Command names, and names of macros and utilities that you can type as commands v Environment variable names in text v Keywords v Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters v Process names v Registry variable names in text v Script names Introduction ix
x IBM Tivoli Netcool Manager: Pack Release Notes
Release summary Identifies the technology packs that have been released or updated and their installation and upgrade support. The release summary also contains information about the interim fixes and fix packs that must be installed for specific technology packs and common packs. Features and changes of this release A list of new and updated technology packs and data models in this release, and any packs that are no longer supported as well as features introduced in previous releases that are still worth discussing are provided. All supported technology packs, common packs, and data models are listed in Latest versions of supported packs on page 20. To determine the version of the Tivoli Netcool Manager modules installed on your system, see the Technical Note entitled IBM Tivoli Netcool Manager: Tools for Version Reporting Technical Note. See Pack documentation on page vii for information about how to access the user documentation, including technical notes. Note: From 1.4-A release, the common pack data models are based on new Tivoli Netcool Manager JDBC driver. For more information, see Installing and Configuring Common Packs. New technology packs There are no new technology packs in this release. New common packs The following common packs are added in this release: v Alcatel-Lucent 5670 RAM 2.5.0 v Arris CMTS DOCSIS 3.0 2.4.0 v Juniper Realtime Monitor (RPM) 2.3.0 Updated technology packs The following technology packs are updated in this release: v Alcatel-Lucent 5670 RAM 2.5.0.0 v Arris CMTS DOCSIS 3.0 2.4.0.0 v Juniper Realtime Monitor (RPM) 2.3.0.0 Copyright IBM Corp. 2006, 1
IPv6 address support Tivoli Netcool or later includes support for IPv6 addresses. The following technology packs are verified to be either neutral or support (see the following note) IPv6 addresses: v Accedian Metro Ethernet v ADVA Optical Metro Ethernet v Alcatel-Lucent 5670 RAM v Alcatel-Lucent 5529 SDC v Alcatel-Lucent 5620 SAM v Alcatel-Lucent 5620 SAM LogToFile v Arris CMTS DOCSIS v Cisco CBQoS v Cisco CMTS DOCSIS v Cisco Device v Cisco IP SLA v Cisco IP SLA Ethernet v Huawei SNMP CBQOS v Huawei SNMP Device v Huawei SNMP NQA v Huawei U2000 v Huawei U2000 DSLAM v GenBand C20 Converged IP Softswitch v Juniper M/T Series Chassis v Juniper M/T Series QoS v Juniper RSVP Tunnel v MIB-II v NetFlow IPFIX v NSN Carrier Ethernet Switch v UBA PVLine Format MIBs are often supported by a range of devices. Only some of these devices support IPv6. IBM cannot specify compliance for each device. Compliance of each device must be verified with the technology vendor. MIB neutrality means that the MIB does not contain IPv6 addresses. Note: For Accedian Metro Ethernet and ADVA Optical Metro Ethernet technology packs, the technology vendor for these packs do not support IPv6 because these packs do not use an IP address and are neutral. The following technology packs do not support IPv6: v Juniper MPLS v Proviso Monitoring v Cisco Class-Based QoS 2 IBM Tivoli Netcool Manager: Pack Release Notes
Functional changes to technology packs A brief description of functional changes to technology packs in this release. Alcatel-Lucent 5670 RAM 2.5.0.0 Technology Pack The Alcatel-Lucent 5670 Reporting and Analysis Manager (RAM) 2.5.0.0 provides application aware reporting. The Alcatel-Lucent 5670 RAM 2.5.0.0 Technology Pack provides Communication Service Providers (CSP) intelligence required for detailed understanding of IP traffic flow and triple play subscriber usage trends. The SDC supports two types of metric collection; bulk collection and on-demand details collection. Bulk collection is the long term, periodic collection of performance data. Details collection is for short term and ad-hoc collection of high resolution data. This pack is only concerned with bulk collection. The SDC is configured with a Collection Strategy that specifies which parameters to collect and how often. The collection strategy must be configured by the customer via the SDC s web interface. The collection strategy has to specify the parameters used by this Technology Pack. Alcatel-Lucent 5529 SDC Technology Pack supports isam and isamihub families and supports ALU 5529 SDC v-r8.2. Functional changes in this technology pack are as follows: v Technology pack is enabled for common reporting on IBM Cognos 10. Arris CMTS DOCSIS 3.0 2.4.0.0 The Arris CMTS DOCSIS 3.0 Technology Pack supports the Arris CMTS device technology, which is an industry-leading high-performance carrier-class CMTS for advanced IP services. It allows cable operators and multiple system operators (MSOs) to provide advanced voice, data and multimedia services over a converged IP network to residential and business subscribers. This release of technology pack introduces a features called Composite Sub-Element (CSE). Functional changes in this technology pack are as follows: v Technology pack is enabled for common reporting on IBM Cognos 10. Juniper Realtime Monitor (RPM) 2.3.0.0 Technology Pack Juniper RPM TP supplies a set of reports suitable for displaying information about the devices and activity associated with the Juniper RPM environment. Reports contain metrics that are generated by the formulas that this application pack provides. Metric names are the same as the names of the formulas that generate them. RPM is a service available in Junos OS that enables a router to measure metrics such as round-trip delays and unanswered echo requests. To achieve this, RPM exchanges a set of probes with other IP hosts in the network for monitoring and network tracking purposes. These probes are sent from a source node to other destination devices in the network that require tracking. Data such as transit delay and jitter can be collected from these probes, and this data can be used to provide an approximation of the delay and jitter experienced by live traffic in the network. Different live traffic metrics like round-trip time (RTT), positive egress jitter, negative egress jitter, positive ingress jitter, negative ingress jitter, positive round-trip jitter, and negative round-trip jitter can be gleaned from the results. RPM calculates minimum, maximum, average, peak-to-peak, standard deviation, and sum calculations for each of these measurements. v Release summary 3
Functional changes in this technology pack are as follows: v Technology pack is enabled for common reporting on IBM Cognos 10. Documentation changes The following changes are implemented in Technology Pack documentation suite: v v v v A new automatically generated Technology Pack Reference in HTML format is being produced directly from the pack model through tooling and delivered on the media alone. User Guide for technology packs is deprecated and the information is distributed in Pack Installation and Configuration Guide and Technology Pack Reference. The User Guides for releases before 1.3-E are still available on the Information Center. Alcatel-Lucent 5620 SAM LogToFile 2.4.0.0 Technology Pack installation and configuration information is merged with Installing Technology Packs and Configuring Technology Packs. The current documentation set consists of the following documents: Pack Release Summary Installing Technology Packs Configuring Technology Packs Upgrading Technology Packs Troubleshooting Packs Installing and Configuring Common Packs Technology Pack Reference per pack Tivoli Netcool Manager 1.4 Known Issues DCF Technote Note: The release documents are available on the Information Center from the following location: http://www-01.ibm.com/support/knowledgecenter/ssbnj7_1.4.0/ com.ibm.tnpm_wln_tp.doc/wln_tech_pack_release_welcome.html Installation and configuration of packs Read this information before you install and configure your packs. For information about how to access the user documentation, including core documentation, see Pack documentation on page vii. Important: Before installing and configuring technology packs, you must read the notes provided in Interim fixes and fix packs on page 40 to review the interim fixes and fix packs that must be installed for specific technology packs and common packs. After installing and configuring technology packs and common packs, you must read Known issues and workarounds from Troubleshooting Technology Packs to determine whether there are any additional tasks that you must perform. UBA and SNMP technology packs have different configurations. UBA and SNMP technology packs are configured differently, as described in the Configuring UBA Technology Packs and Configuring SNMP Technology Packs in Configuring Technology Packs. Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager: v A UBA technology pack requires an XSD file. You add a UBA Collector and associate it with a UBA pack as part of the technology pack installation. 4 IBM Tivoli Netcool Manager: Pack Release Notes
Tivoli Netcool Manager (all versions): v You do not add an SNMP Collector as part of the technology pack installation. You add an SNMP Collector before installing an SNMP technology pack. Additional information For instructions on how to install and configure a technology pack, see the following documentation in addition to these release notes: v v The Installing Tivoli Netcool Manager - Wireline Component for your supported version of Tivoli Netcool Manager Technology Packs. The Installing Technology Packs and Configuring Technology Packs for your supported version of Tivoli Netcool Manager Technology Packs and typical configuration steps for SNMP and UBA Technology Packs. For instructions on how to install and configure a common pack, see the following documentation in addition to these release notes: v v Installing and Configuring Common Packs for installing and configuring Tivoli Netcool Manager Common Packs. Common Reporting users can see the Technology Pack Reference for more information about the Cognos reports available in a common pack. Important: The Cognos Server time zone must be set to GMT to avoid incorrect time data in Cognos reports. Packs in this release The technology packs and common packs in this release. Pack Name Technology Pack Common Pack Alcatel-Lucent 5670 RAM 2.5.0.0 2.5.0 Arris CMTS DOCSIS 3.0 2.4.0.0 2.4.0 Juniper Realtime Monitor (RPM) 2.3.0.0 2.3.0 Note: Technology packs have Version Release Modification Fix (vrmf). Data models have Version Release Modification only. This change is by design. Supported SAM server versions The technology packs and common packs in this release. Table 1. Compatible SAM Server versions on different Tivoli Netcool Manager platforms SAM 8 SAM 9 SAM 10 SAM 10 Tivoli Netcool Manager 4.4.3.3 Alcatel-Lucent SAM 2.6.0.0 to 2.12.0.0 Alcatel-Lucent SAM 2.10.0.0 to 2.12.0.0 Alcatel-Lucent SAM 2.8.0.0 to 2.12.0.0 Not applicable Tivoli Netcool Alcatel-Lucent SAM 2.6.0.0 to 2.14.0.0 Alcatel-Lucent SAM 2.10.0.0 to 2.12.0.0 Alcatel-Lucent SAM 2.12.0.0 onwards Alcatel-Lucent SAM 2.12.0.0 onwards Release summary 5
Table 1. Compatible SAM Server versions on different Tivoli Netcool Manager platforms (continued) SAM 8 SAM 9 SAM 10 SAM 10 Tivoli Netcool Manager 1.3.2 Tivoli Netcool Manager 1.4 Not applicable Not applicable Alcatel-Lucent SAM 2.1.0.0 LogToFile up to Alcatel-Lucent SAM 2.3.0.0 LogToFile Alcatel-Lucent SAM 2.12.0.0 up to 2.14.0.0 Not applicable Not applicable ALU SAM 2.1.0.0 LogToFile up to Alcatel-Lucent SAM 2.4.0.0 LogToFile Alcatel-Lucent SAM 2.12.0.0 up to 2.14.0.0 ALU SAM 2.1.0.0 LogToFile up to Alcatel-Lucent SAM 2.3.0.0 LogToFile Alcatel-Lucent SAM 2.12.0.0 up to 2.14.0.0 ALU SAM 2.1.0.0 LogToFile up to Alcatel-Lucent SAM 2.4.0.0 LogToFile Alcatel-Lucent SAM 2.12.0.0 up to 2.14.0.0 Table 2. Device supported on different versions of Alcatel-Lucent SAM Technology Pack Device Support 7750 SR Up to Alcatel-Lucent SAM 2.14.0.0 7210 SAS Up to Alcatel-Lucent SAM 2.14.0.0 7705 SAR Up to Alcatel-Lucent SAM 2.14.0.0 7450 ESS Up to Alcatel-Lucent SAM 2.14.0.0 OmniSwitch 6250/6850 Alcatel-Lucent SAM 2.11.0.0 onwards 9500 MPR Alcatel-Lucent SAM 2.13.0.0 onwards Technology Pack version FindToFile LogToFile Up to Alcatel-Lucent SAM 2.4.0.0 LogToFile Up to Alcatel-Lucent SAM 2.4.0.0 LogToFile Up to Alcatel-Lucent SAM 2.4.0.0 LogToFile Up to Alcatel-Lucent SAM 2.4.0.0 LogToFile Alcatel-Lucent SAM 2.1.0.0 LogToFile onwards Alcatel-Lucent SAM 2.3.0.0 LogToFile onwards 7750 MG (LTE Core) Not applicable Alcatel-Lucent SAM 2.3.0.0 LogToFile 9471 WMM (LTE Core) Not applicable Alcatel-Lucent SAM 2.3.0.0 LogToFile 6 IBM Tivoli Netcool Manager: Pack Release Notes
Installation and configuration notes for technology packs Read these important notes before installing and configuring a technology pack. Minimum required version of Technology Pack Installer For Tivoli Netcool Manager installations that are upgraded to Tivoli Netcool Manager 1.4, you must use the Technology Pack Installer version 3.5.0.0 to install technology packs. To determine the version of the Technology Pack Installer, run the following command: $ java -jar ProvisoPackInstaller.jar -version Note: The latest Technology Pack Installer (ProvisoPackInstaller.jar file) version is 3.5.0.0. It works on both Oracle and IBM DB2. Minimum Java requirements Use this information to install the technology packs in this release successfully, you must use the Java Runtime Environment (JRE). AIX Linux Solaris 9 Solaris 10 Operating System Minimum software requirements IBM 32-bit JRE for AIX, Java 2 Technology Edition, Version 5.0, Service Refresh 6 IBM 32-bit JRE for Linux, Java 2 Technology Edition, Version 5.0, Service Refresh 6 IBM 32-bit JRE for Solaris, Java 2 Technology Edition, Version 5.0, Service Refresh 6 Solaris Patch 112874-45: libc patch, which is included in the several Solaris patches required by Tivoli Netcool Manager IBM 32-bit JRE for Solaris, Java 2 Technology Edition, Version 5.0, Service Refresh 6 In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, the correct Java version is installed with the Topology Editor in the following default location: /opt/ibm/proviso/jvm/jre/bin For more information, see Configuration Recommendations. Topology Editor JVM must be started by the correct user In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, the Topology Editor uses its own Java virtual machine (JVM) to run. When you install the Topology Editor, this JVM is installed under the Topology Editor installation directory. However, when the Topology Editor extracts the configuration metadata files (XSD files) from a UBA technology pack JAR file, it issues an external command. This external command inherits all the properties of the shell from which the Topology Editor was started. Therefore, if the Topology Editor is started by a user who has the Java path included in the PATH environment variable, the external command works correctly. Otherwise, the command fails. Release summary 7
Launchpad JVM version For 4.3-X and later technology packs, the launchpad requires you to enter the path to supported Java runtime binaries. Only IBM JRE 5.0 SR 6 or later is supported. The Tivoli Netcool Manager Topology Editor provides a supported version of the Java binaries. Note: If you try to use the Technology Pack Installer to install a technology pack on any version of Tivoli Netcool Manager that is running with Java 1.4, the installation fails with an error message. UBA pack XSD file inside a JAR file cannot be loaded into the Topology Editor In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, you cannot load an XSD file from the pack stand-alone JAR file into the Topology Editor. Choose the workaround that is most suitable for your site from the following two options: v Manually extract the XSD file from the pack stand-alone JAR file, and then load it into the Topology Editor. Typically, the pack XSD file is located in the following directory in the stand-alone JAR file: APFiles\pack_name\topologyeditor The name of the XSD file is <pack_name.xsd>. For example: APFiles\cisco_wan_mgr\topologyeditor\cisco_wan_mgr.xsd v Install the 4.4.3.0-TIV-PROV-IF0009 Tivoli Netcool Manager core interim fix. This patch enables you to load an XSD file from the pack stand-alone JAR file into the Topology Editor. For more information about interim fixes, fix packs, and the location for obtaining the fixes, see Interim fixes and fix packs on page 40. Bundled UBA technology pack XSD files In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, if you try to load a single UBA technology pack from the bundled JAR file, the Topology Editor erroneously loads all the XSD files contained in the bundled JAR file. To workaround this problem, follow these tasks: 1. After you import all the UBA technology packs from the bundled JAR file, close the Topology Editor. 2. Go to the metadata/apppacks directory under the Topology Editor installation directory. 3. Delete all the XSD files for the UBA technology packs you do not want to be available for deployment. The names of UBA technology pack XSD files are typically based on the name of the pack. For example, acme_packet_sbc_hdr.xsd is the name of the XSD file for the Acme Packet SBC/HDR Technology Pack. 4. Open the Topology Editor again. PROVISO_JAVA environment variable for all bundled technology packs If you try to install a 4.3-Y or later bundled technology pack, the Technology Pack Installer looks for the PROVISO_JAVA environment variable. 8 IBM Tivoli Netcool Manager: Pack Release Notes
The PROVISO_JAVA environment variable should point to the directory that contains the approved IBM version of JRE 5.0. For example: PROVISO_JAVA==/opt/IBM/proviso/jvm/jre/bin If the PROVISO_JAVA environment variable is not set, the Technology Pack Installer attempts to use the default system Java and might cause an issue when installing bundled packs. You receive an error message in the installer log file that appears as below: INFO [ToolKitData.getJavaPath] No JRE specified. To specify a JRE, use environment variable "PROVISO_JAVA" Downloading a technology pack JAR file in the background In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, if you download a pack JAR file in the background while the Topology Editor window is open, this JAR file is not displayed in the list of available packs. Procedure To correct this issue close and reopen the Topology Editor window to refresh the list of available packs. Location of bulk input files The UBA expects that the bulk input files associated with a specific device are generated on the server on which the device operates. The best practice for specifying the locations of these bulk input files is as follows: v Specify a directory on the server to store the in-process bulk input files. The in-process bulk input files refer to files that are still open for writing by the device or script generating them. Problems can occur when the UBA attempts to download in-process bulk input files. It is recommended that the device or script create a directory. For example, /opt/uba/inprocessbulkinputfiles in which to store the in-process bulk input files. v Specify a directory on the server to store the completed bulk input files. The completed bulk input files refer to files that are closed for writing by the device or script generating them. These bulk input files are the files that the UBA must download and process. In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, you specify the directory for the completed bulk input files by using the Topology Editor to modify the following pack-specific UBA parameters: INPUT_USE_SECURE_FTP INPUT_FTP_HOST INPUT_FTP_USERNAME INPUT_FTP_PASSWORD INPUT_DIRECTORY This is the parameter where you specify the directory (for example, /opt/uba/completedbulkinputfiles) that contains the completed bulk input files. The script that generates the bulk input files can move the completed files automatically through a file system hard link to the directory specified in INPUT_DIRECTORY. Install the DataView Navigator Reporter Set Wizard templates Before using the DataView Reporter Set Wizard, you must install the DataView Navigator Reporter Set Wizard templates, which are provided in the Tivoli Netcool Manager technology pack distribution. Release summary 9
If these templates are not installed, the wizard screen is blank. The required templates are an option in the Pack Bundle Prerequisites item on the Feature Selection screen. The option is called DV Navigator Reporter Set Wizard Pack, which is delivered as part of the Tivoli Netcool Manager technology pack bundle. For information about how to install the DV Navigator Reporter Set Wizard Pack, see the Installing Tivoli Netcool Manager - Wireline Componen. Removing Control-M characters (^M) from files Fujitsu MSAN and Huawei N2000 Technology Pack support files contain Control-M characters that must be removed manually before deploying the pack. About this task The following table lists the files that contain Control-M characters. Technology Pack Files Fujitsu MSAN v EMSPathnames.csv v DVAppPacksBundle.properties Huawei N2000 v HEMSPathnames.csv v DVAppPacksBundle.properties To remove the Control-M characters, follow these steps: Procedure 1. Log in to the DataMart server as pvuser. 2. Change your working directory to the APFiles directory by entering the following command, replacing (/opt/datamart, by default): $ cd DataMart_Home/APFiles 3. Make backup copies of the files by entering commands such as the following examples: $ cp EMSPathnames.csv EMSPathnames.csv.ORIG $ cp HEMSPathnames.csv HEMSPathnames.csv.ORIG 4. Open the file in vi editor. 5. Remove the Control-M characters at the end of all lines in vi, by using: :%s/^v^m//g The CONTROL-v character is ^v and CONTROL-m character is ^m. When you type this, it is as follows: :%s/^m//g 6. Save the file. Important: You can also use the dos2unix utility to remove the Control-M characters, if this utility is available. Packs can be installed directly from a CD In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, you can install technology packs directly from the CD distribution, if you are running an instance of the Tivoli Netcool Manager launchpad on the local file system. 10 IBM Tivoli Netcool Manager: Pack Release Notes
You cannot run the launchpad from the Tivoli Netcool Manager DVD, and then install technology packs directly from the CD distribution. Note: You can also install packs directly from the CD distribution by using the command line. Installing a technology pack by using the command line About this task If you use the command line to install technology packs, specify the java command with the -Xmx512M and -jar options, as follows: Procedure $ java -Xmx512M -jar ProvisoPackInstaller.jar The -Xmx512M option is required to allocate sufficient memory for the Technology Pack Installer to successfully install multiple bundled and stand-alone technology packs. Incorrect SilverStream password specified during technology pack installation In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, if you specify an incorrect SilverStream password during a technology pack installation, the Technology Pack Installer writes an error message to the terminal emulator and not to the launchpad GUI. Incorrect port number displayed for Tivoli Integrated Portal during technology pack installation The Technology Pack Installer GUI always displays 16710 as the default port number for Tivoli Integrated Portal. If you want to use a different port number, you must give the port number that you want for Tivoli Integrated Portal at the time of Tivoli Netcool Manager installation. Otherwise, the Technology Pack Installer displays an error message and you cannot proceed with the installation. Note: The default Tivoli Integrated Portal port is changed from 16315 to 16710. You must replace the Tivoli Integrated Portal port value to 16710 to proceed with the installation. Downloading technology pack JAR files When downloading the bundled JAR file and individual stand-alone pack JAR files from the product distribution site by using the ftp command, make sure to specify the binary option. Installation order for SNMP collectors, HAM, and SNMP technology packs About this task If you are setting up a new Tivoli Netcool Manager environment and plan to use a High Availability Manager (HAM) in that environment, perform the following tasks in the specified order: Procedure 1. Install all SNMP collectors. 2. Configure and start the HAM. Release summary 11
3. Install all SNMP technology packs. 4. Perform the discovery. Topology Editor does not support special characters in host names In Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, the Topology Editor does not accept special characters when specifying a host name. When you specify a value for the host name properties, specify a name with no special characters. For example, a host name such as APDEV-S-040 causes the Topology Editor to return errors, because it fails to accept the hyphen (-) in the host name. SSM Agent installer is available with the Technology Pack Bundle software The SSM Agents installer is now delivered with the Tivoli Netcool Manager Technology Pack Bundle software in the following directory: $PVMHOME/bin. This new path must be used instead of the one described in the User Guides of the Technology Pack Bundle, which is out of date now. Installing the SSM Agent: Tivoli Netcool Manager provides these files to support the installation of the SSM Agent, which you need if you purchased the Tivoli Netcool Manager Technology Pack Bundle. About this task v Netcool/SSM Agent installation files Netcool/SSM Agent Version: netcool-ssm-version-operating_system.installer, where: - version is the current version - operating_system is the name of your operating system - For example, netcool-ssm- 3.2.1-700-solaris-sparc.installer - For example, netcool-ssm- 4.0.0-1757-linux-x86.tar.gz Netcool/SSM Agent Fix Pack: ssm32-fixpack-version-operating_system.run - For example, ssm32- fixpack-727-solaris.run - For example, ssm40- fixpack-10-linux-86.run Netcool/SSM documentation, available for viewing and downloading on the information center at: http://www-01.ibm.com/support/knowledgecenter/ SSTFXA_6.2.0/com.ibm.netcool_ssm.doc/welcome.htm - Netcool/SSM Administration Guide - Netcool/SSM Reference Guide - Netcool/SSM Release Notes - README.txt file Note: First install the Netcool/SSM Agent, and then install the fix pack. To install the Netcool/SSM Agent, follow these steps: 12 IBM Tivoli Netcool Manager: Pack Release Notes
Upgrade technology packs Procedure 1. Change the permission of installation files to be executable. 2. Review the Netcool/SSM Release Notes. 3. Follow the instructions in the Netcool/SSM Administration Guide. To install the fix pack, follow the instructions in the README.txt file included in the software distribution. Use this information to determine whether your technology pack supports an upgrade to the January 2012 release. To determine whether your technology pack supports an upgrade to the January 2012 release without support from an IBM Professional Services representative, see Latest versions of supported packs on page 20. Ensure that you have the following documentation for your version of Tivoli Netcool Manager, in addition to these release notes: v Installing Technology Packs v Configuring Technology Packs v Upgrading Technology Packs v Installing Tivoli Netcool Manager - Wireline Component v Upgrading Tivoli Netcool Manager - Wireline Component v The configuration appendixes in the relevant Technology Pack User Guides for technology packs released before 1.3-E release. For information about how to access the user documentation, including core documentation, see Pack documentation on page vii. Note: Before upgrading technology packs, you must read the notes provided in Interim fixes and fix packs on page 40 to review the interim fixes and fix packs that must be installed for specific technology packs. After upgrading technology packs, you must read Known issues and workarounds from Troubleshooting Packs to determine whether there are any additional tasks that you must perform. CAUTION: If a customized technology pack is installed at your site with modified content, and you reinstall the same pack, you might overwrite all customization. Check with your IBM Professional Services representative before reinstalling an existing technology pack. Critical technology pack upgrade notes These notes refer to technology pack upgrade scenarios where you are running an earlier version of the pack and plan to upgrade to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager. The following sections highlight critical technology pack upgrade notes that apply when upgrading to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager. For more information about upgrading to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, see the Upgrading Tivoli Netcool Manager - Wireline Component. Release summary 13
CAUTION: If the previously described scenario applies to your pack upgrade, then you must read the notes described in the following sections. Otherwise, the technology pack upgrade fails. v Updating technology packs critical upgrade note v Alcatel-Lucent 5620 SAM Technology Pack critical upgrade note Updating technology packs critical upgrade note If you are running a version earlier than 4.3-V of the following technology packs and you plan to upgrade to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, you must upgrade the pack to 4.3-V or later before you upgrade to Tivoli Netcool Manager: v Alcatel-Lucent 5620 SAM v Cisco CMTS v Netflow IPFIX Alcatel-Lucent 5620 SAM Technology Pack critical upgrade note To upgrade the Alcatel-Lucent 5620 SAM Technology Pack, you need the latest Technology Pack Installer. If an earlier version of the Technology Pack Installer is used, the localization files are not updated on installation. Additionally, the upgrade might result in incorrect technology pack text. To identify the version of your Technology Pack Installer, run the following command: $ java -Xmx512M -jar ProvisoPackInstaller.jar Version: 3.3.1.0_build_<build_No> Technology pack upgrade notes You must read these notes before upgrading a technology pack. The following sections discuss problems and workaround that must be followed when upgrading a technology pack. The sections are organized alphabetically, by pack name. Upgrading Alcatel-Lucent 5620 SAM Technology Pack The following notes must be read before upgrading the Alcatel-Lucent 5620 SAM Technology Pack: Workaround for Service Tunnel navigation points labeled N/A: This note describes a workaround to an issue where some Service Tunnel navigation points are labeled N/A. This workaround is applied after upgrading the Alcatel-Lucent 5620 SAM Technology Pack from 4.3-Q or 4.3-R to a later version of the pack. If upgrading from the 4.3-Q or 4.3-R version of the Alcatel-Lucent 5620 SAM Technology Pack, some Service Tunnel navigation points are labeled N/A. To display a subscriber ID label instead of N/A you must run inventory and grouping, delete the empty N/A groups. Then, rerun grouping to eliminate the N/A group. For more information, see the IBM Tivoli Netcool Manager DataMart Configuration Guide. 14 IBM Tivoli Netcool Manager: Pack Release Notes
DataChannel parameter keys are converted to uppercase: Beginning with Tivoli Netcool/Proviso v4.4.3, DataChannel parameters are located in the database. When the parameters are placed into the database, all of the DataChannel keys, or the portion of the parameter definition that appears to the left of the equals sign (for example, DC_KEY=value), are converted to uppercase. This issue can affect customers who are upgrading their environment to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager. As most DataChannel keys are already in uppercase, this issue is unlikely to affect your environment. If you have any lowercase or mixed-case DataChannel keys, change these keys to all-uppercase before upgrading your environment, to ensure that your Tivoli Netcool Manager components work properly. Upgrading from Alcatel-Lucent 5620 SAM 4.3-Y Technology Pack: When you want to upgrade Alcatel-Lucent 5620 SAM Technology pack to a later version, you must manually delete the %(samportname rule from the Rule Editor if this rule exists. About this task To do this, follow these steps: Procedure 1. Log in as pvuser (or the user name that you specified during installation) on the system where DataMart is installed. 2. Source the DataMart environment using the following command: $. /opt/datamart/datamart.env 3. Run the following command to open the DataMart application: pvm 4. Click Rule Editor in the Resource tab. The Rule Editor window is displayed. 5. Go to the following level: NOC Reporting > Alcatel-Lucent 5620 SAM > SAM Router Health > Interfaces. 6. Locate the following rule: %(samsitename)-%(samsiteid) 7. Expand this rule and select the following child rule: %(samportname) 8. Delete the %(samportname) rule. For more information on upgrading the Alcatel-Lucent technology pack to Alcatel-Lucent SAM 2.11.0.0 that is released in 1.3G, see the Pack Upgrade Guide. Upgrading Cisco CBQoS Technology Pack The Cisco CBQoS Technology Pack, before 4.3-R, had dynamic properties that must be replaced by new static properties before upgrading the pack. To fix this issue, you must run a shell script that is bundled with the technology pack. The following note describes how to extract the.tar file that contains the technology pack, patch, and a README. The README explains how to install the patch. Extracting the tar file that contains pack, interim fix, README, and shell script: Release summary 15
About this task To extract the.tar file, follow these steps: Procedure 1. Log in to the server that is running Tivoli Netcool Manager DataMart by entering the user name and password that you specified when installing DataMart. The default user name and password (as recommended in the IBM Tivoli Netcool Management: Installation Guide) arepvuser and PV. 2. Start a bash shell: $ bash 3. Change your working directory to the DataMart home directory (/opt/datamart, by default): $ cd /opt/datamart 4. Load the bash shell with the DataMart environment by sourcing the datamart.env file: $. /opt/datamart/datamart.env 5. Download the.tar file that contains the technology pack, interim fix, README, and shell script to the/tmp directory. This.tar file can be on the product distribution site: https://www-112.ibm.com/software/howtobuy/softwareandservices 6. Extract the.tar file as follows, replacing <filename> with the name of the.tar file: $ tar -vxf /tmp/<filename> Upgrading Cisco CWM Technology Pack If you are running a version earlier than 4.3-V of the Cisco CWM Technology Pack and plan to upgrade to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, there is an issue where the ODBC driver can produce SQL errors that affect inventory for this pack. About this task Apply this workaround after you upgrade to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, by doing the following tasks on each DataChannel host in your environment: Procedure 1. Open an xterm session on the DataChannel host. 2. Change your working directory to the DataChannel home directory (/opt/datachannel, by default): $ cd /opt/datachannel 3. Using a text editor, open the datachannel.env file. a. On Solaris systems, search for the LD_LIBRARY_PATH environment variable. b. On AIX systems, search for the LIBPATH environment variable. 4. Add the $DC_PRODUCT_HOME/license path to the LD_LIBRARY_PATH or LIBPATH environment variables. For example: a. After adding the specified path, the LD_LIBRARY_PATH environment variable on Solaris is similar to the following example: LD_LIBRARY_PATH=$DC_PRODUCT_HOME/license:$DC_PRODUCT_HOME/ lib:$oracle_home/lib:$ld_library_path 16 IBM Tivoli Netcool Manager: Pack Release Notes
b. After adding the specified path, the LIBPATH environment variable on AIX is similar to the following example: LIBPATH=$DC_PRODUCT_HOME/license:$DC_PRODUCT_HOME/lib:$ORACLE_HOME/ lib:$ld_library_path 5. Write and quit the datachannel.env file. 6. Load the shell with the DataChannel environment, by sourcing the datachannel.env file: $. /opt/datachannel/datachannel.env 7. Stop the AMGR (Application Manager). To manually stop the AMGR, follow these steps: a. Log in as pvuser on the host computer running the AMGR. b. At a shell prompt run the following command: $ ps -edf grep amgr grep -v grep The above command returns the process ID of the AMGR process. c. Stop the AMGR by killing the process ID returned in the previous step. This process ID is represented by amgr_pid in the following example: $ kill -9 amgr_pid 8. Restart the AMGR. To manually restart the AMGR, follow these steps: a. Log in as pvuser on the host computer running the AMGR. b. At a shell prompt, change to the DataChannel/bin subdirectory. For example: $ cd /opt/datachannel/bin c. Enter the following command at a shell prompt: $./amgrw 9. Bounce (restart) any UBA that runs the Cisco CWM Technology Pack: $ dccmd bounce UBA.<channel_number>.<subchannel_number> Where: v <channel_number> - Replace with the channel number that was configured for this technology pack. v <subchannel_number> - Replace with the subchannel (also referred to as the collector) number that was configured for this technology pack. Upgrading Cisco IP Telephony Technology Pack If you are running a version earlier than 4.3-V of the Cisco IP Telephony Technology Pack and plan to upgrade to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, there is an issue where the ODBC driver can produce SQL errors that affect inventory for this pack. About this task Apply this workaround after you upgrade to Tivoli Netcool/Proviso v4.4.3 or Tivoli Netcool Manager, by doing the following tasks on each DataChannel host in your environment: Procedure 1. Open an xterm session on the DataChannel host. Change your working directory to the DataChannel home directory (/opt/datachannel, by default): $ cd /opt/datachannel 2. Using a text editor, open the datachannel.env file. a. On Solaris systems, search for the LD_LIBRARY_PATH environment variable. Release summary 17
b. On AIX systems, search for the LIBPATH environment variable. 3. Add the$dc_product_home/license path to the LD_LIBRARY_PATH or v environment variables. For example: a. After adding the specified path, the LD_LIBRARY_PATH environment variable on Solaris is similar to the following example: LD_LIBRARY_PATH=$DC_PRODUCT_HOME/license:$DC_PRODUCT_HOME/ lib:$oracle_home/lib:$ld_library_path b. After adding the specified path, the LIBPATH environment variable on AIX is similar to the following example: LIBPATH=$DC_PRODUCT_HOME/license:$DC_PRODUCT_HOME/lib:$ORACLE_HOME/ lib:$ld_library_path 4. Write and quit the datachannel.env file. 5. Load the shell with the DataChannel environment, by sourcing the datachannel.env file: $. /opt/datachannel/datachannel.env 6. Stop the AMGR (Application Manager). To manually stop the AMGR, follow these steps: a. Log in as pvuser on the host computer running the AMGR. b. At a shell prompt run the following command: $ ps -edf grep amgr grep -v grep The above command returns the process ID of the AMGR process. a. Stop the AMGR by killing the process ID returned in the previous step. This process ID is represented by amgr_pid in the following example: $ kill -9 amgr_pid 7. Restart the AMGR. To manually restart the AMGR, follow these steps: a. Log in as pvuser on the host computer running the AMGR. b. At a shell prompt, change to the DataChannel/bin subdirectory. For example: $ cd /opt/datachannel/bin c. Enter the following command at a shell prompt: $./amgrw 8. Bounce (restart) any UBA that runs the Cisco IP Telephony Technology Pack: $ dccmd bounce UBA.<channel_number>.<subchannel_number> Where: v <channel_number> - Replace with the channel number that was configured for this technology pack. v <subchannel_number> - Replace with the subchannel (also referred to as the collector) number that was configured for this technology pack. Upgrading IP Multicast Technology Pack The note below specifies that you must delete entries from the inventory_subelements.txt file before you merge it with the ip_multicast_inventory_subelements.txt file. You perform this task only when upgrading the IP Multicast Technology Pack. Deleting entries from the inventory subelements file: About this task IP Multicast entries must be deleted from the inventory_subelements.txt file located in the datamart/conf directory before you merge it with the ip_multicast_inventory_subelements.txt file, as described in the Netcool/Proviso IP Multicast Technology Pack User Guide. 18 IBM Tivoli Netcool Manager: Pack Release Notes