IBM Tivoli Netcool Performance Manager Wireline Component October 2012 Document Revision R2E1. Pack Installation and Configuration Guide

Size: px
Start display at page:

Download "IBM Tivoli Netcool Performance Manager Wireline Component October 2012 Document Revision R2E1. Pack Installation and Configuration Guide"

Transcription

1 IBM Tioli Netcool Performance Manager Wireline Component October 2012 Document Reision R2E1 Pack Installation and Configuration Guide

2 Note Before using this information and the product it supports, read the information in Notices on page 129. Copyright IBM Corporation 1997, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents About this information Intended audience Tioli Netcool Performance Manager - Wireline Component i What this information contains ii Chapter 1. Installing technology packs. 1 Types of technology packs Backing up inentory files Prerequisite software Prerequisite software for technology pack installation Additional information Preinstallation setup tasks Preparing to install technology pack patches Preparing the pack installation directory Installing a technology pack Installing technology packs by using the launchpad UBA collectors Log files Chapter 2. Configuring technology packs Configuring SNMP Technology Packs Configuring UBA Technology Packs Chapter 3. Additional configuration steps for certain SNMP Technology Packs Cisco CBQoS Technology Pack Losing indexes after deice reboots Customizing discoery results Chapter 4. Additional configuration steps for certain UBA Technology Packs Alcatel-Lucent 5620 SAM Technology Pack Deices and serices Setting up the Alcatel-Lucent 5620 SAM serers 33 Configure the technology pack Modifying the collection strategy Troubleshooting Alcatel-Lucent 5620 SAM Technology Pack configuration Alcatel-Lucent 5670 RAM Technology Pack Oeriew of Alcatel-Lucent 5670 RAM Technology Pack Bulk input file formats in Alcatel-Lucent 5670 RAM Technology Pack Configuring the RAM serer saminentory ramadaptor GenBand C20 Conerged IP Softswitch Technology Pack New bulk input file formats introduced in GenBand C20 Conerged IP Softswitch Technology Pack Configuring certain scripts for Genband C20 deices Actiating percentile requests UBA PVLine Format Technology Pack PVLine input file formats Additional Topology Editor parameters Chapter 5. Installing common packs 115 Prerequisite software Prerequisite software for common pack installation Additional information Upgrading Model Maker Oeriew of installing common packs for pack administrators The Base Common Pack Suite Creating a logins file with the appropriate passwords Adding a base common pack to the repository Adding multiple common packs to the repository Adding common packs by using the CLI Actiating common packs in the repository Actiating common packs by using the CLI Populating the calender schema table for TCR Time 121 Downloading common packs Publishing a common pack Listing common packs in the repository Uninstalling common packs Remoing common packs from the repository 124 Remoing downloaded common packs from the Windows computer Appendix. Installing technology packs by using the command line Notices Trademarks Additional copyright notices Copyright IBM Corp. 1997, 2012 iii

4 i IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

5 About this information Intended audience The IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide describes how to install and configure Tioli Netcool Performance Manager technology packs and common packs. Tioli Netcool Performance Manager is currently rolling out the ability to report on the performance data by using the Cognos reporting capability of Tioli Common Reporting, included as standard in Tioli Netcool Performance Manager since ersion Technology packs are enabled for Common Reporting by the additional installation of a common pack, which contains all the Cognos artifacts necessary for running common reports for a particular technology. You must also install some base common packs, which contain generic functionality used by multiple packs. Additional software is required to install and use common packs and their dependent base common packs. If you want to use Common Reporting for your reporting needs, install the additional software and then install the appropriate common packs for your technology pack according to the instructions in this guide. The audience for this guide. Network administrators or operations specialists responsible for installing and configuring technology packs and common packs on an IBM Tioli Netcool Performance Manager system on an enterprise network. Common pack modelers who want to create and publish data models for Common Reporting in Tioli Netcool Performance Manager. Readers must be familiar with the following topics: Basic principles of TCP/IP networks and network management SNMP concepts Administration of the Oracle database management system Tioli Netcool Performance Manager Tioli Netcool Performance Manager technology pack and common pack concepts Tioli Netcool Performance Manager reporting concepts IBM Tioli Common Reporting or IBM Cognos IBM Cognos Framework Manager Copyright IBM Corp. 1997, 2012

6 Tioli Netcool Performance Manager - Wireline Component IBM Tioli Netcool Performance Manager consists of a wireline component (formerly Netcool/Proiso) and a wireless component (formerly Tioli Netcool Performance Manager for Wireless). Tioli Netcool Performance Manager - Wireline Component consists of the following subcomponents: DataMart is a set of management, configuration, and troubleshooting GUIs. The Tioli Netcool Performance Manager System Administrator uses the GUIs to define policies and configuration, and to erify and troubleshoot operations. DataLoad proides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. DataChannel aggregates the data collected through Tioli Netcool Performance Manager DataLoad for use by the Tioli Netcool Performance Manager DataView reporting functions. It also processes online calculations and detects real-time threshold iolations. DataView is a reliable application serer for on-demand, web-based network reports. Technology Packs extend the Tioli Netcool Performance Manager system with serice-ready reports for network operations, business deelopment, and customer iewing. The following figure shows the different Tioli Netcool Performance Manager modules. Tioli Netcool Performance Manager documentation consists of the following: Release notes i IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

7 Configuration recommendations Technical notes Online help The documentation is aailable for iewing and downloading on the information center at com.ibm.netcool_pm.doc/welcome_tnpm.html. What this information contains This publication contains the following sections: Chapter 1, Installing technology packs, on page 1 Describes how to install and manage technology packs. Chapter 2, Configuring technology packs, on page 13 Describes how to configure the technology packs. Chapter 3, Additional configuration steps for certain SNMP Technology Packs, on page 23 Describes additional configuration steps required for certain SNMP technology packs. Chapter 4, Additional configuration steps for certain UBA Technology Packs, on page 27 Describes additional configuration steps required for certain UBA technology packs. Chapter 5, Installing common packs, on page 115 Describes how to install and manage common packs. Installing technology packs by using the command line, on page 127 Describes how to install technology packs by using command line. About this information ii

8 iii IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

9 Chapter 1. Installing technology packs Types of technology packs The Topology Editor was introduced at the same time as the 4.3-U technology pack release. All 4.3-U or higher UBA technology pack installations require the Topology Editor to configure the technology pack. Configuration details are described in the Pack Installation and Configuration Guide. Tioli Netcool Performance Manager supports the 4.3-U or higher technology pack installation procedures. All technology packs, both legacy bundle and stand-alone packs, require the Technology Pack Installer. Always use the latest Technology Pack Installer, regardless of the ersion of the technology pack. Important: A new Technology Pack Installer is released in 1.3-G release with the ersion This ersion has no feature enhancements but is released for license text changes. Note: Since the release of 4.3-W technology packs, the former Starter Kit was renamed to Pack Bundle Prerequisite pack. It is contained in the legacy bundle and is only required to be installed with a legacy pack that is also contained in a legacy bundle. All technology packs require that the Starter Kit or the Pack Bundle Prerequisite Pack to be installed. Tioli Netcool Performance Manager supports these types of technology packs. Bundled - Multiple technology packs that are contained in a single, bundled JAR file. Stand-alone - Indiidual technology packs that are contained in separate JAR files, one for each stand-alone technology pack. Both Bundled and stand-alone packs are installed with a common installer with slightly different screens depending on the type of pack you are installing. Typically, you might install a combination of bundled and stand-alone packs. The installation instructions coer the following installation scenarios: Bundled only Stand-alone only Bundled and Stand-alone Copyright IBM Corp. 1997,

10 Backing up inentory files Prerequisite software These backup steps are not required for an SNMP stand-alone technology pack. About this task For specific information about managing the inentory control files for an SNMP technology pack, see Chapter 2, Configuring technology packs, on page 13. Before you install a new technology pack from the technology pack bundle, or from a stand-alone pack, you must perform the following actions: Procedure 1. Change your working directory to the conf directory by using the following command: cd $PVMHOME/conf 2. Make backup copies of the inentory control files by entering the following commands: cp inentory_elements.txt inentory_elements.txt.orig cp inentory_subelements.txt inentory_subelements.txt.orig 3. After the installation of the technology pack is complete, you must follow the configuration steps Chapter 2, Configuring technology packs, on page After the configuration of the technology pack is complete, you must perform a diff between the inentory control files and the.orig ersions of the files, and merge back any differences. Ensure that you fulfil these prerequisites before you install and configure a technology pack. Prerequisite software for technology pack installation You must hae all the prerequisite software and required information before you install and configure a technology pack. IBM Tioli/Netcool Proiso or IBM Tioli Netcool Performance Manager. An SNMP collector. You can add an SNMP collector as described in Add a Collector in theibm Tioli Netcool Performance Manager: Installation Guide. Note: For UBA technology packs, you add a UBA collector and associate it with a UBA pack as part of this technology pack installation. Ensure that you hae access to the Tioli Netcool Performance Manager DataMart serer that is running an X Window System serer. Note: If there is no graphics card on the DataMart serer, the Xfb irtual frame buffer package that proides X Window System serices is automatically installed. For more information, see Setting Up a Remote X Window Display in the IBM Tioli Netcool Performance Manager: Installation Guide. Ensure that you hae access to the SilerStream serer (Tioli Netcool/Proiso 4.4.3) Ensure that you hae access to the Tioli Integrated Portal (Tioli Netcool Performance Manager or later) Ensure that you hae access to the DataChannel serer 2 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

11 Ensure that you hae access to the technology pack installation files on one of the following locations: Product distribution site: softwareandserices. On the product distribution site are theproisopackinstaller.jar file, and technology pack JAR files. Tioli Netcool Performance Manager CD distribution, which contains the ProisoPackInstaller.jar file, technology pack JAR files, and the JAR files for the Starter Kit components. For more information about the Starter Kit, see Preinstallation setup tasks on page 4. For more information about obtaining software, see your IBM customer representatie. The correct ersion of Jaa. For more information, see IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. Additional information An SNMP Technology Pack is MIB-based and its configuration is relatiely straightforward. UBA Technology Packs collect data against non-snmp deices, and rely on the UBA of the Tioli Netcool Performance Manager DataChannel to process the data. Before configuring a technology pack, ensure that you: Hae the following documentation for your ersion of Tioli Netcool Performance Manager: IBM Tioli Netcool Performance Manager: Pack Release Notes for the current technology pack release IBM Tioli Netcool Performance Manager: Installation Guide IBM Tioli Netcool Performance Manager: Upgrade Guide (if you are upgrading the core software) IBM Tioli Netcool Performance Manager: Pack Upgrade Guide (if you are upgrading the technology-pack software) IBM Tioli Netcool Performance Manager: DataMart Configuration Guide Note: Refer to this guide to create an inentory profile and initiate a discoery. Ensure that you hae access to the following site to check for interim fixes or fix packs that might apply to your technology pack: NetcoolProiso.html The Tioli Netcool Performance Manager documentation and the IBM Tioli Netcool Performance Manager: Pack Release Notes, which are aailable on the following website: _pm.doc/welcome_tnpm.html Always check the Release Notes before installing a technology pack to determine: If the pack is bundled or stand-alone pack. If the pack has any dependencies. For example, some packs require that the MIB-II Technology Pack to be installed. If the pack is an SNMP or a UBA pack. UBA packs must be associated with a UBA collector as part of the pack installation. If the pack is upgradeable. Chapter 1. Installing technology packs 3

12 Preinstallation setup tasks The Oracle TNS name of the serer on which you installed Oracle serer with the Tioli Netcool Performance Manager database configuration. For more information, see Specifying a Basename for DB_USER_ROOT in the IBM Tioli Netcool Performance Manager: Installation Guide. Ensure that all necessary configuration steps are completed on the prerequisite software. Determine the technology packs you want to install, and then see the release notes to determine whether the pack is bundled or stand-alone pack. Note: If you are installing multiple packs, plan to download all the JAR files and install all the packs at the same time. Completed the following tasks: Reiewed the release notes for the current technology pack. Note: Release notes contain important information that you need to consider before installing a technology pack. They also contain information about specific patches that need to be installed before you configure a technology pack Installed the current ersion of the Tioli Netcool Performance Manager components, as described in the IBM Tioli Netcool Performance Manager: Installation Guide. Installed the MIB-II Technology Pack. Note: The MIB-II Technology Pack is a stand-alone technology pack that is contained in its own JAR file. The MIB-II Technology Pack must be installed for those technology packs that hae a dependency on this pack. Configured at least one DataChannel. Configured an SNMP collector subchannel for an SNMP pack. Configured a UBA bulk collector subchannel for a UBA pack. Created a user on the serer with permission to FTP and delete files. Open a terminal emulator and log on to the DataMart serer as puser. Change your working directory to the DataMart home directory (/opt/datamart, by default). Load the shell with the DataMart enironment by sourcing the datamart.en file, as follows:. /opt/datamart/datamart.en Note: After you load the DataMart enironment into the shell, the PVMHOME ariable is set to the DataMart home directory, /opt/datamart, by default. These instructions assume that this ariable is set. Set and export the DISPLAY enironment ariable (see Setting Up a Remote X Window Display in the IBM Tioli Netcool Performance Manager: Installation Guide), so that the Technology Pack Installer GUI displays back on your system. Installed the Technology Pack. Note: Localization is done automatically during installation of the technology pack. 4 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

13 Preparing to install technology pack patches Describes how to install technology pack patches. Before you begin For the latest patch information for Tioli Netcool Performance Manager, see Installing an Interim fix in the IBM Tioli Netcool Performance Manager: Installation Guide. For the latest patch information for technology packs, download the Release Notes of the required technology pack release from the information center. Reiew the appendix that deals with interim fixes and fix packs in the release notes and note the patches required for the technology packs you intend to install. Procedure 1. Download the required patches for each technology pack that you intend to install. 2. Install the required patches for each technology pack that you intend to install. Preparing the pack installation directory You can obtain technology pack installation files from the IBM product distribution website, or from the Tioli Netcool Performance Manager technology pack CD. Before you begin If you are installing the packs using an instance of the Tioli Netcool Performance Manager launchpad on the local file system, you can install directly from the CD. Otherwise, you must create a temporary directory and copy the technology pack files to the local system before you begin the installation. You cannot run the launchpad from the Tioli Netcool Performance Manager DVD, and then install technology packs directly from the CD distribution. Note: If you are using a local instance of the launchpad and you want to install directly from the technology pack CD, you can skip this step and proceed to Installing a technology pack on page 6. Procedure 1. On the system where DataMart is located, use the mkdir command to create app-packs directory to hold the technology pack JAR files and the ProisoPackInstaller.jar file, for example: mkdir -p $PVMHOME/ersion/app-packs 2. If you want to use technology packs from the IBM product distribution website, download the JAR files by following these steps: a. Use the cd command to change your working directory to the app-packs directory that you created in Step 1. For example: cd $PVMHOME/ersion/app-packs b. Download the following from this website: ProisoPackInstaller.jar file JAR files for technology packs you want to install (the bundled JAR file for bundled packs or indiidual JAR files for stand-alone packs) Chapter 1. Installing technology packs 5

14 Installing a technology pack 3. If you want to use technology packs from the Tioli Netcool Performance Manager technology pack CD, browse to the /Proiso/AP/jar location on the CD and copy the following files to the temporary directory: ProisoPackInstaller.jar file JAR files for technology packs you want to install (the bundled JAR file for bundled packs or indiidual JAR files for stand-alone packs) 4. Unmount the CD. You can install a Tioli Netcool Performance Manager technology pack either from a launchpad or by using the command line. Installing technology packs by using the launchpad Use this information to install a technology pack by using the launchpad. Before you begin Check the ersion of Jaa running on your system by entering the following command: jaa -ersion You might need to upgrade your ersion of Jaa depending on the technology pack release. Important: For 4.3-U and higher technology packs, the launchpad requires you to enter the path to supported Jaa runtime binary files. Only ersion 1.5.0_b(14+) is supported. The Tioli Netcool Performance Manager topology editor proides a supported ersion of the Jaa binary files. Using the older Jaa ersion might result in an error detailing that it is not possible to proceed with the installation. About this task To install a Tioli Netcool Performance Manager technology pack, follow these steps: Procedure 1. Start the installer as follows: a. If it is not already open, open the launchpad (see Starting the Launchpad in the IBM Tioli Netcool Performance Manager: Installation Guide). Note: Open a terminal emulator and log on to the DataMart serer as puser. You must su to root. Otherwise, the launchpad fails to start. b. On the launchpad, click Install Technology Pack. c. On the Install Technology Pack window, enter the following information: The DataMart home directory (for example,/opt/datamart, by default). The Jaa run time enironment home directory (for example, /opt/ibm/proiso/topologyeditor/jre/bin). Note: For information about supported JRE ersions, see the IBM Tioli Netcool Performance Manager: Configuration Recommendations. The Tioli Netcool Performance Manager user (for example, puser). 6 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

15 d. Click the Install Technology Pack link. A window prompts you to select the technology pack installation setup directory. e. Click Browse to locate the temporary directory ($PVMHOME/ersion/apppacks) that you created in Preparing the pack installation directory on page 5, or the directory on the Tioli Netcool Performance Manager CD where the pack JAR files are located (by default, /Proiso/AP/jar). The technology pack can be loaded to the serer where the Tioli Netcool Performance Manager database is installed. f. Click the directory, and then click Select to display the specified directory in the window. g. Click OK. When the Technology Pack Installer starts, it displays a Tioli Netcool Performance Manager Technology Packs Welcome window. 2. Click Next. 3. Accept the license agreement, and then click Next. The Technology Pack Installer displays the Database Access Parameters window with the parameter alues that you specified when installing and configuring Oracle, the Tioli Netcool Performance Manager database, and Tioli Netcool Performance Manager DataMart. For more information, see Installing and configuring the prerequisite software and Installing in a distributed enironment in the IBM Tioli Netcool Performance Manager: Installation Guide. 4. Re-enter the password of the database user, which is PV by default. 5. Click Next to continue. The Technology Pack Installer displays the SilerStream or Tioli Integrated Portal access parameter alues that you specified when installing and configuring Tioli Netcool Performance Manager DataView as described in Installing in a distributed enironment in the IBM Tioli Netcool Performance Manager: Installation Guide. Note: The Technology Pack Installer GUI always displays as the default port number for Tioli Integrated Portal. If you want to use a different port number, you must gie the port number at the time of Tioli Netcool Performance Manager installation. Otherwise, the Technology Pack Installer displays an error message and you cannot proceed with the installation. 6. Re-enter the password of the SilerStream user, which is admin by default, or tipadmin for the Tioli Integrated Portal user. The Technology Pack Installer displays a Feature Selection window, which lists all the packs you downloaded to the directory created in Preparing the pack installation directory on page 5 in the left panel. All the packs are automatically selected for installation. 7. Clear any technology packs in the list that you do not want to install, and then click Next. Note: The prerequisites for technology packs item in the Feature Selection window is always installed. You cannot clear this item. The Starter Kit is not included in this item. Depending on the type of packs you install, you might be presented with slightly different windows. Stand-alone packs only: a. Click Next to start the installation. As the stand-alone packs are installed, the Technology Pack Installer Chapter 1. Installing technology packs 7

16 displays the name of each pack and indicates the progress. When the installation completes, the Technology Pack Install Complete window is displayed. b. Click Finish to exit the Technology Pack Installer. c. Go to What to do next section to perform post-installation tasks. Bundled and stand-alone packs: The Technology Pack Installer installs all of the stand-alone technology packs and displays the name of each pack and indicates progress. When the installation of the stand-alone packs completes, the Tioli Netcool Performance Manager Technology Packs screen opens, and the installation of bundled packs begins. Bundled packs: To Install the bundle packs, follow these steps: CAUTION: For 4.3-Y or higher Technology Packs Only. Before installing bundled packs, the Installer looks for an enironment ariable named PROVISO_JAVA. This points to the directory that contains the approed 1.5 IBM Jaa Virtual Machine. If PROVISO_JAVA enironment ariable is not set, the installer attempts to use the default system Jaa and causes an issue when installing bundled packs. a. An Update Proiso Database message box displays briefly, followed by a Tioli Netcool Performance Manager Technology Packs screen. Click Next to continue. The Technology Pack Installer displays the Database Details screen with the parameter alues that you specified when installing and configuring Oracle, the Tioli Netcool Performance Manager database, and Tioli Netcool Performance Manager DataMart as described in preious chapters of this installation guide. For more information, see Installing and configuring the prerequisite software and Installing in a distributed enironment in the IBM Tioli Netcool Performance Manager: Installation Guide. b. Re-enter the password of the database user, which is PV by default. c. Click Next to continue. The Select Packages screen opens. d. On the Select Packages screen, do the following: If not preiously installed, select the Pack Bundle Prerequisites. Select indiidual bundled technology packs that you want to install. e. Click Next to continue. f. Confirm your bundled pack selections on the Install Options Selected screen or click Back to return to the Select Packages screen to remoe or add technology packs to the list. g. When you are satisfied with your selections, click Next. The Technology Pack Installer begins copying files associated with the bundled packs, displaying seeral status windows. Note: If it detects existing files, the Technology Pack Installer might display Replace File window, for example, inentory_elements.txt and inentory_subelements.txt. For more information about backing up these files, see Backing up inentory files on page 2. When the Technology Pack Installer finishes copying all the necessary files for the bundled packs and updates the database, it displays the ReadMe File screen. By default, the check box for reiewing the README file is selected. The README file tells you to download the Pack Release Notes from the information center. 8 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

17 h. Click Finish. The Technology Pack Installer displays a series of messages in the terminal emulator as it uploads style sheets and other pack-related files to the database. Upon completion, the Technology Pack Installer displays a Technology Pack Install Complete screen. i. Click Finish to exit the Technology Pack Installer. What to do next After the installation completes, do the following, depending upon the types of packs (bundled or stand-alone packs, SNMP or UBA packs) you installed: Note: See IBM Tioli Netcool Performance Manager: Pack Release Notes to determine the pack type (SNMP or UBA). Important: A technology pack does not work until it is configured. After configuring the technology pack, data is collected and reports are populated. SNMP packs Configure the technology pack, as described in Chapter 2, Configuring technology packs, on page 13. UBA packs Add a UBA collector, as follows: All UBA packs except the Nortel CS2000 Technology Pack, see Adding a UBA collector for a UBA pack on page 10 The Nortel CS2000 Technology Pack, see Adding UBA collectors for the Nortel CS2000 Technology Pack on page 11 Configure the technology pack, as described in Chapter 2, Configuring technology packs, on page 13. UBA collectors The UBA collector is associated with two DataChannel components: Complex Metric Engine (CME) x.x - Performs calculations on the collected data. File Transfer Engine (FTE) x.x - Transfers files from the collector output directories and places them in the input directory of the CME. Note: Topology Editor includes the channel and collector numbers in the component names. For example, Data Channel 1 could hae Collector UBA 1.1, with Complex Metric Engine 1.1 and File Transfer Engine 1.1. The FTE writes data to the file /ar/adm/wtmpx on each system that hosts a collector. As part of routine maintenance, check the size of this file to preent it from growing too large. For more information about Disk Quota Management, see IBM Tioli Netcool Performance Manager: Installation Guide. Note: The Solaris ersion can be configured with strict access default settings for secure enironments. Strict FTP access settings might interfere with automatic transfers between a DataChannel subchannel and the DataLoad serer. Check for FTP lockouts in /etc/ftpd/ftpusers, and check for strict FTP rules in /etc/ftpd/ftpaccess. For all UBA technology packs except for the Nortel CS2000 Technology Pack, follow the instructions in Adding a UBA collector for a UBA pack on page 10. Chapter 1. Installing technology packs 9

18 For the Nortel CS2000 Technology Pack, follow the instructions in Adding UBA collectors for the Nortel CS2000 Technology Pack on page 11. This technology pack has some specific requirements beyond the typical UBA pack and requires some additional steps. Adding a UBA collector for a UBA pack Use this information to add a UBA collector for a UBA Pack. About this task To add a UBA collector, follow these steps: Procedure 1. Load the pack XSD file into an existing topology, as follows: a. If it is not already open, open the Topology Editor (see Starting the Topology Editor in the IBM Tioli Netcool Performance Manager: Installation Guide). b. Open a deployed topology (a topology.xml file) (see Opening an Existing Topology File in the IBM Tioli Netcool Performance Manager: Installation Guide). c. In the Technology Pack iew, right-click the Technology Packs folder and select Load Technology Pack from the menu. The Load the technology pack configuration metadata window displays. There are two radio buttons: XSD file and JAR file. d. Click the JAR file radio button and select Browse. There is a known issue and a workaround for opening an XSD file from a UBA pack. For more information, see UBA pack XSD file inside a JAR file cannot be loaded into the Topology Editor section in IBM Tioli Netcool Performance Manager: Pack Release Notes. e. Using the Directory: field, the up and down arrows, and the Folders pane on the configuration metadata window, go to the directory where the technology pack JAR files exist (for example, $PVMHOME/APFiles or a directory on the Tioli Netcool Performance Manager CD). f. For Bundled UBA packs: Select the Bundled JAR file, then click OK. The Bundled JAR file displays in the Load the technology pack configuration metadata window. Click Next. The Topology Editor displays the list of XSD files for the Bundled packs you installed. Select one or more XSD files to import into the topology. Click Select all to select all of the XSD files. Note: You can also click a single XSD file and press the CTRL key to select any number of other XSD files. Click Finish. The Topology Editor adds the selected Bundled Technology Pack or packs to the list of technology packs displayed in the Technology Packs iew. g. For Stand-alone UBA packs: Select a technology pack JAR file, and then click OK. The pack JAR file is displayed in the configuration metadata window. Click Finish. The Topology Editor adds the selected stand-alone technology pack to the list of technology packs displayed in the Technology Packs iew. 10 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

19 2. After loading a UBA pack XSD file, you must add a UBA collector and associate it with a UBA technology pack as follows: a. In the Logical iew, right-click the DataChannel x folder and select from the Add collector UBA menu. The Configure Collector window opens. b. Select the appropriate technology pack (for example, Alcatel Lucent 5529 SDC) from the list of technology packs, and then click Next. c. Using the list of aailable hosts on the Configure Collector window, select the workstation that hosts the collector (for example, corinth). d. Accept the default collector number (for example, 2). e. Click Finish. The Topology Editor displays the new collector under the DataChannelx folder in the Logical iew. f. Highlight the collector to iew its properties. The Topology Editor displays both the UBA collector core parameters and the UBA technology pack-specific parameters. The core parameters are configured with all UBA technology packs. Reiew the alues for the parameters to make sure that they are alid. For information about the core parameters, see the IBM Tioli Netcool Performance Manager: Property Reference Guide. For information about the pack-specific parameters, see the Topology Editor Help. g. To add additional UBA collectors for a UBA technology pack, repeat Step 2-a through Step 2-f. h. Redeploy the updated topology (see Starting the Deployer in the IBM Tioli Netcool Performance Manager: Installation Guide). 3. Configure the UBA technology packs. Adding UBA collectors for the Nortel CS2000 Technology Pack Use this information to add UBA collectors for the Nortel CS2000 Technology Pack. About this task The Nortel CS2000 Technology Pack requires you to add one UBA collector for each of the following deices running in the network: Passport Packet Voice Gateway (PVG) The UBA executing on this subchannel retriees Bulk input files generated by the PVG deice. Uniersal Signaling Point (USP) The UBA executing on this subchannel retriees Bulk input files generated by the USP deice. Nortel CS2K Performance The UBA executing on this subchannel retriees Bulk input files generated by the Nortel CS2K Performance deice. Nortel Integrated Element Management System (IEMS) The UBA executing on this subchannel retriees Bulk input files generated by the Nortel CS2K IEMS system. Nortel Serer Session Lines (SSL) The UBA executing on this subchannel retriees Bulk input files generated by a Nortel CS2K SSL deice. Attention: The following two UBA Collectors, SST and CPR, are only applicable for 4.3-X and higher Technology Packs. Nortel Session Serer Trunk (SST) The UBA executing on this subchannel retriees Bulk input files generated by a Nortel CS2K SST deice. Nortel Common Performance Reporting (CPR) CPR is a log format. The bulk input files generated by the PVG deice are manipulated by the IEMS system and conerted into CPR format. Nortel recommends that the CPR log format be manipulated ia the IEMS system, instead of directly from the MDM. So this is Chapter 1. Installing technology packs 11

20 facilitated by the CPR Adaptor. The CPR Adaptor is also somewhat of a generic adaptor as it can be used to support SST data in CPR format. One instance of the CPR Adaptor can simultaneously support both CPR and SST formats. For example, if there are two PVG deices you would add two UBA collectors, one for each PVG deice operating in the network. If there are two USP deices you would add two UBA collectors, one for each USP deice operating in the network, and so forth. The Nortel CS2000 Technology Pack also requires you to add multiple UBA collectors for the following call records: Nortel Succession Communication Serer 2000 (CS2K) CDR call records The UBAs executing on this subchannel retriee Bulk input files generated by the cs2kcdr.pl pre-processor. For example, if you expect the UBA to process a large amount of CS2K CDR call records you would add multiple (for example, three) UBA collectors, each with a unique collector number. Each of these UBA collectors is then mapped to a Master UBA. The Topology Editor displays the appropriate windows for you to add multiple UBA collectors and add the Master UBA. The Topology Editor simplifies the task of adding UBA collectors for each of these deices and the CS2K CDR call records by associating each with a technology pack that displays in the Technology Packs iew after you load the XSD file. The table below maps each deice to its associated technology pack. CS2000 Deice/System/Calls Records PVG Nortel CS2K CDR USP Nortel CS2K Performance IEMS SSL SST CPR Pack Displayed in Technology Packs iew Nortel CS2K - PVG Nortel CS2K - CDR Nortel CS2K - USP Nortel CS2K - CS2K Performance Nortel CS2K - IEMS Nortel CS2K - SSL Nortel CS2K - SST Nortel CS2K - CPR Log files The Technology Pack Installer writes log files to the /usr/tmp directory. Log files in this directory contain a detailed history of the tasks the Technology Pack Installer performs as it installs technology packs. You can check this log file to help sole any issues that might occur during technology pack installation. For example, a log file might contain a message that indicates that the Technology Pack Installer GUI could not display back on your system because the DISPLAY enironment ariable was not set. For more information, see Setting Up a Remote X Window Display in the IBM Tioli Netcool Performance Manager: Installation Guide. Log files for bulk technology packs are named installertimestamp.log, where timestamp is the time the file was created in seconds since the UNIX epoch. Log files for stand-alone packs are named: APInstalltimestamp.log. For technology packs, log file names hae the format APInstallnumber.log. For example: APInstall log for 1.3-E technology packs. 12 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

21 Chapter 2. Configuring technology packs Typical configuration steps for SNMP and UBA technology packs and also additional configuration steps required for certain technology packs. Configuring SNMP Technology Packs About this task To configure an SNMP Technology Pack, follow these steps: Procedure 1. Load the DataMart enironment. To load the shell with the DataMart enironment, follow these steps: a. Log on to the DataMart serer as puser. b. Change your working directory to the DataMart home directory (/opt/datamart, by default), using the following command: cd /opt/datamart c. Load the shell with the DataMart enironment, by sourcing the datamart.en file, as follows:. /opt/datamart/datamart.en Note: After you load the DataMart enironment into the shell, the PVMHOME ariable is set to the DataMart home directory,/opt/datamart by default. These instructions assume that this ariable is set. 2. Actiate data collection requests. During installation of the technology pack, all predefined data collection requests are promoted to the database and set to inactie (that is, idle displays in the Actie column of the Tioli Netcool Performance Manager DataMart Request Editor). You must actiate these predefined data collection requests by using the Request Editor. To set data collection requests to actie, follow these steps: a. Change your working directory to $<PVMHOME>/bin (/opt/datamart/bin, by default) on the DataMart serer. b. Enter the following command, and then press Enter to open the DataMart GUI: pm c. Click the Configuration tab, and then click Request Editor to open the Request Editor. d. Click the Collection tab. e. Click Refresh. The predefined data collection requests are loaded into the Request Editor from the database. f. Click the Inactie button in the Filter group box to display only idle requests. g. In the Sub-Element Groups pane, select all idle data collection requests in the following group or groups: Root > Sub-Element Collect > <tech_pack> Copyright IBM Corp. 1997,

22 h. Click the Actie box under Details. The Request Editor toggles the idle setting for these data collection requests from idle to actie in the Actie column. i. Click Sae. 3. Merge the technology pack subelement inentory text files. Subelement inentory control rules for the technology pack are contained in the file <tech_pack>_inentory_subelements.txt, which is installed in the following directory on the DataMart serer: <$PVMHOME>/APFiles/<tech_pack>/datamart/conf You must merge the contents of this file with the file inentory_subelements.txt located in <$PVMHOME>/conf (by default, /opt/datamart/conf) on the DataMart serer. Important: You must perform the following steps on the MIB-II Technology Pack before you perform them on the SNMP Technology Pack that has a dependency on the MIB-II Technology Pack. To merge the subelement inentory control rules for the Technology Pack, follow these steps: a. Enter the following command to change your working directory to <$PVMHOME>/conf cd <$PVMHOME>/conf b. Copy <tech_pack>_inentory_subelements.txt to the <$PVMHOME>/conf directory, by entering the following command: cp $<$PVMHOME>/APFiles/<tech_pack>/datamart/conf/ <tech_pack>_inentory_subelements.txt c. Enter the following command to make a backup copy of the inentory_subelements.txt file: cp inentory_subelements.txt inentory_subelements.txt.orig d. Enter the following command to append the contents of <tech_pack>_inentory_subelements.txt to inentory_subelements.txt: Important: Ensure that you use two forward brackets (>>); otherwise, the original content of inentory_subelements.txt is oerwritten. cat <tech_pack>_inentory_subelements.txt >> inentory_subelements.txt e. Perform diff on the backed-up file and the appended file to ensure that the merge succeeded, as shown in the following example: diff inentory_subelements.txt inentory_subelements.txt.orig 4. Run the initial SNMP inentory and initiate a discoery. An inentory collects data about the network resources that the technology pack monitors. After you install an SNMP technology pack, you must create an inentory profile by using the Inentory Tool Wizard, and then initiate a discoery by running the inentory profile by using the Inentory Tool. Running the initial inentory against SNMP objects is an intricate task and unfortunately beyond the scope of this configuration chapter. For instructions on using the Inentory Tool Wizard to create an inentory profile, and the Inentory Tool to run the inentory profile, see the IBM Tioli Netcool Performance Manager: DataMart Configuration Guide. 5. Deploy reports. After the technology pack installation completes, the rules for the new deice are automatically loaded into the database. The inentory process uses these rules to group elements and subelements. You must manually deploy 14 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

23 (auto-group) the reports by associating them with groups in the NOC Reporting tree in the DataMart Resource Editor. To deploy the Technology Pack reports, follow these steps: a. Open the Tioli Netcool Performance Manager DataMart Resource Editor. b. Click the Report SE Group tab. c. Moe the cursor to the left pane and scroll up to select any group under the SUB-ELEMENTS > NOC Reporting tree. d. Right-click and select the AutoGrouping option from the menu. The AutoGrouping option places the reports in dynamically generated groups created during inentory. e. Click Yes to continue. f. Click Close to exit the message box. Or, click Details to iew a description of any errors. g. Optional: Create an entry cron that uses the inentory CLI command and the -reportgrouping option to deploy reports on a regular basis. The following example shows an entrycron that periodically deploys the report operation: 0****./opt/datamart/dataMart.en && inentory -nox -reportgrouping This option instructs the inentory command to run the report grouping rules and update the deployed reports stored in the database. Report grouping rules must be created before this option can be used. For more information about creating report grouping rules, see the IBM Tioli Netcool Performance Manager: DataMart Configuration Guide. For more information about the inentory command, see the IBM Tioli Netcool Performance Manager: Command Line Interface Guide What to do next Verifying resources Use the Tioli Netcool Performance Manager DataMart Resource Editor to determine whether the following technology pack resources (elements, subelements, properties, and so on) are successfully discoered and created in the database during inentory. For more information about Tioli Netcool Performance Manager DataMart Resource Editor, see the IBM Tioli Netcool Performance Manager: DataMart Configuration Guide. Configuring UBA Technology Packs About this task To configure a UBA Technology Pack, follow these steps: Procedure 1. Load the DataMart enironment. To load the shell with the DataMart enironment, follow these steps: a. Log in to the DataMart serer as puser. b. Change your working directory to the DataMart home directory (/opt/datamart, by default), using the following command: cd /opt/datamart Chapter 2. Configuring technology packs 15

24 c. Load the shell with the DataMart enironment, by sourcing the datamart.en file, as follows:. /opt/datamart/datamart.en Note: After you load the DataMart enironment into the shell, the <PVMHOME> ariable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this ariable has been set. 2. Copy technology-specific files from the DataMart serer to the DataChannel serer. Technology-specific files are used to associate a UBA technology pack with a specific instance of the UBA. Note: While it is possible to install DataMart and DataChannel on the same serer, in a typical installation these modules are installed on separate serers. If so, use FTP to copy the technology-specific files. Otherwise, if DataMart and DataChannel are on the same serer, use the cp command to copy the files to the appropriate DataChannel directory. To copy technology-specific files to the DataChannel serer, follow these steps: a. Log in to the Tioli Netcool Performance Manager DataChannel serer by entering the user name and password that you specified when installing and configuring a DataChannel. The default user name and password are puser and PV. b. Change your working directory to the<data_channel_home>/scripts directory by entering the following command, replacing <DATA_CHANNEL_HOME> with the DataChannel home directory (/opt/datachannel, by default): $cd<data_channel_home>/scripts c. Copy the <tech_pack> directory from <$PVMHOME>/APFiles/<tech_pack>/ datachannel/scripts to <DATA_CHANNEL_HOME>/scripts. d. Verify that the technology-specific files are now located in the target directory as follows: Verify that the bulk adapter design files (*.js), scripts (if any), other files (if any) are now located in the <DATA_CHANNEL_HOME>/ scripts/<tech_pack> directory. 3. Actiate data collection requests. During installation of the technology pack, all predefined data collection requests are promoted to the database and set to inactie (that is, idle displays in the Actie column of the Tioli Netcool Performance Manager DataMart Request Editor). You must actiate these predefined data collection requests using the Request Editor. To set data collection requests to actie, follow these steps: a. Change your working directory to <$PVMHOME>/bin (/opt/datamart/bin, by default) on the DataMart serer. b. Enter the following command, and then press Enter to inoke the DataMart GUI: pm c. Click the Configuration tab, and then click Request Editor to open the Request Editor. d. Click the Collection tab. e. Click Refresh. The predefined data collection requests are loaded into the Request Editor from the database. 16 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

25 f. Click the Inactie button in the Filter group box to display only idle requests. g. In the Sub-Element Groups pane, select all idle data collection requests in the following group or groups: Root > Sub-Element Collect > <tech_pack> h. Click the Actie box under Details. The Request Editor toggles the idle setting for these data collection requests from idle to actie in the Actie column. i. Click Sae. 4. Edit pack-specific UBA parameters, based on Tioli Netcool/Proiso and Tioli Netcool Performance Manager platforms: In this release of Tioli Netcool Performance Manager, you are instructed to modify the technology pack-specific UBA parameters when you install the technology pack by using the Topology Editor. If you hae not modified the UBA parameters with site-specific alues or you want to make additional edits, you can do so now. Otherwise, you can go to the next step. 5. Load the DataChannel enironment. In subsequent steps, you execute dccmd commands. To ensure that you can run these commands, load the shell with the DataChannel enironment by following these steps: a. Log in to the DataChannel serer as puser. b. Change your working directory to the DataChannel home directory (/opt/datachannel, by default), by using the following command: cd /opt/datachannel c. Load the shell with the DataChannel enironment, by sourcing the datachannel.en file, as follows:. /opt/datachannel/datachannel.en 6. Restart the DataChannel to actiate the UBA and read in changes to the deployed topology. a. Open a terminal emulator on the DataChannel serer. b. Use the dccmd command to stop all DataChannel applications: dccmd stop all c. Use the dccmd command to release all daemons running in the DataChannel: dccmd forget all d. Use the following command to find the process identifiers (pids) associated with the DataChannel isual processes: <DATA_CHANNEL_HOME>/bin/findisual where: <DATA_CHANNEL_HOME> is/opt/datachannel, by default. e. Use the following commands to stop each DataChannel isual process: kill -9 <cnsw_pid> kill -9 <logw_pid> kill -9 <amgrw_pid> kill -9 <cmgrw_pid> Note: The logw is a Jaa process and must to be killed by using ps -ef grep LOG, and then kill the logw process ID. f. Use the following commands to restart each DataChannel isual process: cnsw logw cmgrw amgrw g. Use the dccmd command to start all DataChannel applications: dccmd start all Chapter 2. Configuring technology packs 17

26 h. Use the dccmd command to erify that all of the DataChannel applications started properly: dccmd status all Note: More specifically, make sure that the UBA application associated with the DataChannel that is configured for the technology pack is running. i. Watch the output of the status switch to erify that all the necessary processes are running. If these processes are running, run the tail utility on the log file for the UBA by issuing a command similar to the following example: tail -f DATA_CHANNEL_HOME/log/proiso.log grepuba.<channel_number>.<collector_number>- more where: Variable <DATA_CHANNEL_HOME> <channel_number> The trailing dash ( ) after <collector_number> Description By default,/opt/datachannel Specifies the channel number (for example, 1) you specified when configuring this DataChannel. Remoes extraneous log messages from your iew. That is, the trailing dash guarantees that the command displays only those messages generated by your application. The first set of messages relates to syntax checks. The following table identifies some eents to watch for during the syntax check: Eent The UBA application starts successfully, but then stops executing. The bulk adapter design file might be corrupted. The UBA application connects to the database. Description Typically, this eent occurs because of a licensing issue. This eent causes a syntax error before the UBA application connects to the database. This eent causes a message similar to the following example to display: DB_CONNECT Connecting to <sid> as <user> If you see this database connection message without prior errors, the UBA application has passed the syntax check. 7. Ensure that the bulk input files can be read. To erify that the UBA application can read the bulk input files, follow these steps: a. Place a bulk input file at the source input location. The source input location for bulk input files is specified using the URI parameter from the pack XSD file, which you can iew using the Topology Editor. Within the configured file retrieal interal (typically, 5 minutes), the UBA application retriees the bulk input file and copies it to the following directory: <DATA_CHANNEL_HOME>/UBA.<channel_number>.<collector_number>/<instance>/do/ 18 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

27 where: Variable <DATA_CHANNEL_HOME> <channel_number> <collector_number> <instance> Description By default,/opt/datachannel Specifies the channel number (for example, 1) that you specified when configuring this DataChannel. Specifies the collector number (for example, 100) that you specified when configuring this UBA bulk collector. Specifies the string for the INSTANCES parameter in the pack XSD file. Typically, this string represents the name of the pack and is read-only. You can iew the string specified for INSTANCES by using the Topology Editor. The UBA application then processes the bulk input file according to the instructions in the bulk adapter design file. Note: The first time that the UBA processes a bulk input file, it passes a metric to the CME. The CME rejects this metric as abad_metric metric does not hae an associated grouped subelement before this metric is recorded. This is an expected behaior. The CME accepts metrics from the bulk input files after the inentory is run. b. Ensure that the UBA application can successfully read the bulk input file that you copied into the source input location, by issuing a tail command similar to the following example: tail -f <DATA_CHANNEL_HOME>/log/proiso.log grep UBA.<channel_number>.<collector_number>- more The following table identifies the success messages that you must look for. Success message PERF_INPUT_PROCESSING Processed <integer> records in <float> seconds (<float> records/minute): <int> records METRIC_STREAM_INFO completed writing metric output: DATA_CHANNEL_HOME/UBA.<channel_number>.<collector_number>/ streaming/ state/temp/output/ <time>.<instance>.nraw.bof; wrote <int> metrics; <int> bad resource IDs; <int> bad formula names (#()) Description Specifies a bulk adapter design file completion message. A bulk adapter design file successfully completes when an informational message similar to this one displays in the log file. Success occurs when <int> records equals 0. Specifies a metric creation success message. The UBA application successfully creates metrics when a debug 2 message similar to this one displays in the log file. For some technology packs, the metric creation might be done across different instances of UBA applications. Success occurs when <int> metric is greater than one, <int> bad resource IDs equals 0, and <int> bad formula names equals 0. Chapter 2. Configuring technology packs 19

28 Success message PERF_INVFLUSH Inserted/updated <int> inentory objects in <float> seconds Description Specifies an inentory success message. The inentory successfully completes when an informational message similar to this one displays in the log file. If <int> is greater than one, the UBA application created or updated at least one subelement, and the inentory process is successful. The log file might record further details (if necessary) in the messages associated with the PERF_INVFLUSHPV subelement message category. 8. Run the bulk inentory profile. The UBA application handles the inentory and metrics according to the instructions proided in the technology pack design file or files. The UBA application inserts the created elements, subelements, and metrics into the database. Howeer, the UBA application does not handle the grouping of these elements and subelements. To handle the grouping of the elements and subelements that were inserted into the database, UBA technology packs supply a bulk inentory profile. This bulk inentory profile is automatically created when the pack is installed. Bulk inentory profiles use the following name syntax: bulk_n Where: Syntax item bulk_ N Description Identifies as a bulk inentory profile for a UBA technology pack. Specifies the collector number (for example, 100) that the user specified when configuring this UBA bulk collector. You must use the Inentory Tool to run a bulk inentory profile. To run the bulk inentory profile for this technology pack, perform the following steps: a. In the command window where you loaded the DataMart enironment, change your working directory to <$PVMHOME>/bin (/opt/datamart/bin, by default) on the DataMart serer. b. Inoke the DataMart GUI by entering the following command and pressing Enter: pm c. Click Inentory Tool in the Resource tab. The Inentory Tool window appears. This window displays a list of the existing inentory profiles on the Configuration tab. The name of the inentory profile to run is bulk_n, where N is the collector number configured for this pack. d. On the Configuration tab, click the bulk inentory profile for this technology pack, and then select Run Profile from the Action menu. The 20 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

29 Lie Information tab displays messages about the status of the profile. See the IBM Tioli Netcool Performance Manager DataMart Configuration Guide for more information about running an inentory profile. e. Optional: Eery time the UBA technology pack design file creates new elements, subelements, and metrics, you must perform the preious steps to group the elements and subelements. One way to accomplish this task on a regular basis is to create an entrycron that uses the inentory CLI command. The following example shows an entrycron that periodically performs the grouping operation for a bulk inentory profile called bulk_100: 0****./opt/datamart/dataMart.en && inentory -name bulk_100 -action pregrouping -reload -nox 0****./opt/datamart/dataMart.en && inentory -name bulk_100 -action grouping -reload -nox See the IBM Tioli Netcool Performance Manager: Command Line Interface Guide for more information about the inentory command. 9. Deploy reports. After the technology pack installation completes, the rules for the new deice are automatically loaded into the database. The inentory process uses these rules to group elements and subelements. You must manually deploy (auto-group) the reports by associating them with groups in the NOC Reporting tree in the DataMart Resource Editor. To deploy the Technology Pack reports, follow these steps: a. Open the Tioli Netcool Performance Manager DataMart Resource Editor. b. Click the Report SE Group tab. c. Moe the cursor to the left pane and scroll up to select any group under the SUB-ELEMENTS > NOC Reporting tree. d. Right-click and select the AutoGrouping option from the menu. The AutoGrouping option places the reports in dynamically generated groups created during inentory. e. Click Yes to continue. f. Click Close to exit the message box. Or, click Details to iew a description of any errors. g. Optional: Create an entrycron that uses the inentory CLI command and the -reportgrouping option to deploy reports on a regular basis. The following example shows an entrycron that periodically deploys report operation: 0****./opt/datamart/dataMart.en && inentory -nox -reportgrouping This option instructs the inentory command to run the report grouping rules and update the deployed reports stored in the database. Report grouping rules must hae been created before this option can be used. For more information about creating report grouping rules, see the IBM Tioli Netcool Performance Manager: DataMart Configuration Guide. See the IBM Tioli Netcool Performance Manager: Command Line Interface Guide for more information about the inentory command. What to do next Verifying resources Chapter 2. Configuring technology packs 21

30 Use the Tioli Netcool Performance Manager DataMart Resource Editor to determine whether the following technology pack resources (elements, subelements, properties, and so on) are successfully discoered and created in the database during inentory. See the IBM Tioli Netcool Performance Manager: DataMart Configuration Guide for more information about Tioli Netcool Performance Manager DataMart Resource Editor. Changing predefined threshold requests If a technology pack supplies predefined threshold requests. The setup program automatically loads these predefined threshold requests into the database and configures them for you. You do not need to actiate them, but you can use Tioli Netcool Performance Manager to change them. See the IBM Tioli Netcool Performance Manager: DataMart Configuration Guide for information about working with predefined threshold requests. 22 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

31 Chapter 3. Additional configuration steps for certain SNMP Technology Packs Additional configuration steps are required for certain SNMP Technology Packs. Cisco CBQoS Technology Pack Additional configuration steps required for Cisco CBQoS Technology Pack. Losing indexes after deice reboots After a network deice reboot, the CISCO-CLASS-BASED-QOS-MIB must be repolled to re-establish the following indexes: cbqosconfigindex cbqospolicyindex cbqosobjectsindex Repolling is required because a reboot can cause the order of the Modular Quality of Serice (QoS) Command-Line Interface (CLI) (MQC) configuration to differ from the actual configuration order, which is user-drien and unpredictable. Traditionally, MIB persistence is handled by Cisco IOS APIs, which sae the index and key information to NVRAM. The data is then retrieed and repopulated after reloading. Howeer, this approach does not work well for the current implementation of the cbqosobjectsindex because of the large amount of information that needs to be saed. An index encoding scheme based on configuration entries instead of operational sequence is implemented to proide persistent indexes on router reload so that MIB information retains the same set of object alues each time a networking deice reboots. You might want to configure networking deices to use the QoS: CBQoS MIB Index Enhancements feature. Customizing discoery results The properties of the following subelements are merged with and display as properties of the CB QoS Class Map subelement: CB QoS Queueing Action CB QoS Police Action CB QoS Traffic Shaping Action By modifying the cbqos_object_id_m.pl script, it is possible to customize the results of the Discoery formulas and to fill in the indexes associated with the QueueID,PoliceID and ShapeID properties. Attention: Edits to the scripts described in the following sections must be done under the guidance of IBM Professional Serices. Copyright IBM Corp. 1997,

32 Customizing InentoryAppPack.sh About this task This generic script resides in the <$PVMHOME>/conf directory. It contains processing logic for a number of technology packs and is configured to perform Cisco QoS-related steps as follows: Procedure 1. Determines if the ProfileName, CollectorNumber and DirProfile parameters are passed to it by InentoryHook.sh. If so, it assigns the parameter alues to internal ariables. If not, it generates a failure message and exits. 2. Determines if the TaskName parameter ealuates to AfterDiscoery. If not, it generates a failure message and exits. 3. Determines if the ProfileName parameter ealuates to Cisco_QoS. If not, it generates a failure message and exits. 4. Passes the following files to cbqos_object_id_m.pl: a. $DirProfile/inentory/subelement_inariant.dat An input file containing index alues associated with the QueueID,PoliceID and ShapeID properties. b. $DirProfile/inentory/subelement_inariant.dat_mod An output file to which cbqos_object_id_m.pl writes the results of its index substitution operations. 5. Waits for cbqos_object_id_m.pl to process the files and generates an appropriate message if cbqos_object_id_m.pl returns successfully. Otherwise, it generates a failure message and exits. 6. Copies subelement_inariant.dat to a backup file called subelement_inariant.dat.orig. 7. Moes subelement_inariant.dat_mod to a file named subelement_inariant.dat. This oerwrites the input file that was backed up in the preious step. Customizing cbqos_object_id_m.pl About this task Located in <$PVMHOME>/bin, this script reads the input file, performs a substitution procedure, and writes the results to the output file. The substitution procedure assigns index alues to the QueueID,PoliceID and ShapeID properties so that these properties are assigned to the CB_QoS Class Map subelement. It uses the following steps: Procedure Determines if the input (subelement_inariant.dat) and output (subelement_inariant.dat_mod) files were passed to it by InentoryAppPack.sh. If not, it generates a failure message and exits. Otherwise, it opens both files for processing. Searches the input file for the strings QueueID,PoliceID and ShapeID, and then stores their associated index alues in three internal ariables. It then searches for the strings <P1>, <S1>, and <Q1> and replaces them with the stored index alues. Prints the results to the output file (subelement_inariant.dat_mod). (If no substitution is performed, it prints no results to the output file). Closes both files and returns the results to InentoryAppPack.sh. 24 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

33 Configure the cbqos_object_id_m.pl script by giing the following commands: dos2unix /opt/datamart/apfiles/cisco_cbqos/datamart/bin/cbqos_object_id_m.pl > /tmp/temp m /tmp/temp /opt/datamart/bin/cbqos_object_id_m.pl To change the file permissions for the script files, execute these commands: chmod 777 /opt/datamart/bin/cbqos_object_id_m.pl chmod 777 /opt/datamart/conf/inentoryapppack.sh Note: If the ProfileName parameter ealuates to Cisco_QoS, you must use these scripts. Chapter 3. Additional configuration steps for certain SNMP Technology Packs 25

34 26 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

35 Chapter 4. Additional configuration steps for certain UBA Technology Packs Additional configuration steps for certain UBA Technology Packs. Alcatel-Lucent 5620 SAM Technology Pack Additional configuration steps required for Alcatel-Lucent 5620 SAM Technology Pack. Deices and serices In this topic, you will learn details about Alcatel-Lucent 5620 SAM serer compatibility, supported deices, Alcatel-Lucent 5620 SAM serices, data collection model, bulk input file formats, and bulk adapter design files. Alcatel-Lucent 5620 SAM serer compatibility The Alcatel-Lucent 5620 SAM Technology Pack currently runs on the following Alcatel-Lucent 5620 SAM serers: Alcatel-Lucent 5620 SAM Serer Release 7 Alcatel-Lucent 5620 SAM Serer Release 8 Alcatel-Lucent 5620 SAM Serer Release 9 Alcatel-lucent 5620 SAM Serer Release 10 Supported deices The list of deices supported by the Alcatel-Lucent 5620 SAM Technology Pack depends on the ersion of the technology pack. Deices supported in this release This ersion of the Alcatel-Lucent 5620 SAM Technology Pack supports the following deices: Alcatel-Lucent 7750 Serice Router Alcatel-Lucent 7710 Serice Router Alcatel-Lucent 7705 Serice Aggregation Router Alcatel-Lucent 7450 Ethernet Serice Switch Alcatel-Lucent 7210 Serice Access Switch Alcatel-Lucent OmniSwitch 6850 Alcatel-Lucent OmniSwitch 6250 For more information about these deices, see How the deices are supported The Alcatel-Lucent 5620 SAM Technology Pack supports these deices in the following ways: Defines data generation, data storage, and data collection methods The Alcatel-Lucent 5620 SAM Technology Pack communicates with the deice through the Simple Object Access Protocol / Extensible Markup Language (SOAP/XML) interface, and uses JMS for notification of inentory changes. See Data collection model for more information about the SOAP/XML interface and Copyright IBM Corp. 1997,

36 other components associated with the data collection model. Defines Tioli Netcool Performance Manager propertiesthe Alcatel-Lucent 5620 SAM defines and manages all of the releant objects associated with the deice in the Alcatel-Lucent XML-based equipment package. The Alcatel-Lucent 5620 SAM Technology Pack maps the appropriate set of SAM object properties defined in the equipment package to Tioli Netcool Performance Manager properties. In general, the Netcool Performance Manager property name is the same as the SAM object property name, except that the Netcool Performance Manager property name also has the prefix sam. For information about the properties currently supported by the Alcatel-Lucent 5620 SAM Technology Pack, see the IBM Tioli Netcool Performance Manager Alcatel-Lucent 5620 SAM Technology Pack Reference. Alcatel-Lucent 5620 SAM serices Alcatel-Lucent 5620 SAM users can configure such serices as VPRN, VPLS, and customer or subscriber sites to the core network at the SAPs. A user might also configure a set of policies to manage different classes of traffic at the SAPs. A SAP can hae one policy applied for ingress traffic, and another for egress (to the customer site). The Alcatel-Lucent 5620 SAM has a predefined set of 8 traffic classes: be, l2, af, l1, h2, ef, h1, and nc. In addition, the Alcatel-Lucent 5620 SAM supports unicast, multicast, and broadcast IP traffic. A user can define a policy to manage each combination of traffic classes and cast types uniquely. With eight classes and four types, 32 different combinations are possible. On a SAP, each unique combination is supported by a separate queue, which means up to 32 queues to be managed. On ingress, the SAPs support separate queues for the different casts of traffic. Howeer, on egress, the SAPs do not support separate queues. Therefore, on egress, there is a maximum of eight queues. The Alcatel-Lucent 5620 SAM represents these entities in the following objects: SAPs: A SAP object represents a SAP. The SAP object has a PolicyId property. Policies: The Policy object represents the policy. ForwardingClasses: A ForwardingClass object represents one of the eight possible classes of traffic. This object has a PolicyId property that indicates the policy to which it belongs. If the object is an ingress ForwardingClass, it has four queue IDs, one each for Unicast, Multicast, Broadcast, and Other. If the object is an egress ForwardingClass, it has one queue ID. Serice queues: An Egress Serice Queue object or an Ingress Serice Queue object represents a serice queue on a SAP. Data collection model The Alcatel-Lucent 5620 SAM Technology Pack integrates with the Alcatel-Lucent 5620 SAM, collecting and reporting performance metrics for the networking infrastructure and serices that the Alcatel-Lucent 5620 SAM manages. Figure 1. Data collection model for the Alcatel-Lucent 5620 SAM Technology Pack Communication between Tioli Netcool Performance Manager components and Alcatel-Lucent 5620 SAM is through the SOAP/XML interface and XML files. Simple Object Access Protocol (SOAP) is a lightweight XMLbased messaging protocol that is used to encode the information in Web serice request and response messages before sending them oer a network. SOAP messages are 28 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

37 independent of any operating system or protocol and can be transported using a ariety of Internet protocols, including Simple Mail Transfer Protocol (SMTP), Multipurpose Internet Mail Extensions (MIME), and HyperText Transfer Protocol (HTTP). When the technology pack is operating, Tioli Netcool Performance Manager periodically commands the Alcatel- Lucent 5620 SAM, ia SOAP/XML, to generate XML files that contain metrics for a number of the managed resources. These XML files are then collected and processed, with the results presented in a set of Web-based reports, which are listed and described in Alcatel-Lucent 5620 SAM Technology Pack Reference. Inentory The Alcatel-Lucent 5620 SAM contains an object database that represents the network resources and their relationships to other network resources. It also represents some abstract resources and relationships. Serices and their owners (called Subscribers) are represented, along with their relationships to each other and to the Serice Access Point Queues. Figure shows that the Alcatel-Lucent 5620 SAM Technology Pack manages the inentory of the resources, real and abstract, in two ways: Complete inentory Eent-drien inentory Complete inentory Figure shows that in the complete inentory, the SAM Inentory File (SAMIF) adapter application uses the instructions contained in the SAMIF design files to send a single SOAP/XML request to the Alcatel-Lucent 5620 SAM for each SAM object type needed to execute the inentory. Specifically, the request is for an XML file containing information about all instances of that object type. The requests from the SAMIF adapter application will filter the set of property alues returned for each SAM object type. This filter operation limits the set of property alues to those that matter to the technology pack inentory. The SAMIF adapter application reads each XML file and does the following actions: Collects inentory for Tioli Netcool Performance Manager-monitored objects that the Alcatel-Lucent 5620 SAM Technology Pack manages, and stores this object information in its memory. Creates the appropriate subelements. Maps Tioli Netcool Performance Manager properties to their associated SAM object properties. Assigns these Tioli Netcool Performance Manager properties to their associated subelements. Stores these resources in the Tioli Netcool Performance Manager database. Furthermore, the SAMIF adapter application creates an ID Map file whose purpose is to proide inentoryrelated information to the Bulk Load Balancer (BLB) adapter. The ID Map file maps foreign keys of the external system to the Resource ID and Collector ID used within Tioli Netcool Performance Manager. When the inentory and metrics are located in separate bulk input files (as is the case in the Alcatel-Lucent 5620 SAM enironment), a technology pack deeloper typically implements seeral types of bulk adapter design files, as described in Bulk adapter design files on page 11. Eent-drien inentory The Jaa Message Serice (JMS) API is a messaging standard that enables application components based on the Jaa 2 Platform, Enterprise Edition (J2EE) to create, send, receie, and read messages. The JMS API enables distributed Chapter 4. Additional configuration steps for certain UBA Technology Packs 29

38 communication that is loosely coupled, reliable, and asynchronous. The Alcatel-Lucent 5620 SAM uses the JMS API to iew real-time eents and alarm feed information from the managed network. See the Alcatel- Lucent 5620 SAM-O OSS Interface Deeloper Guide for more information. Note: Alcatel-Lucent 5620 SAM-O is an open interface on the Alcatel-Lucent 5620 SAM. An OSS client application can access information through the Alcatel-Lucent 5620 SAM-O. Figure shows that in the eent-drien inentory, the SAMIF adapter application uses the instructions contained in the SAMIF design files to process JMS create, delete, and update messages. For more information about SAMIF design files, see Bulk adapter design files. Metrics The Bulk Load Balancer (BLB) periodically makes requests to the Alcatel-Lucent 5620 SAM serer to retriee SAM statistics for one period. The SAM statistics are then passed to the UBA for parsing and processing into Tioli Netcool Performance Manager metrics. Bulk input file formats The Alcatel-Lucent 5620 SAM deices gather performance data and other SAM statistics from multiple network elements, in XML format. This data is referred to collectiely as network health metrics. Each Alcatel-Lucent 5620 SAM deice produces, on an hourly basis, bulk input files that contains the network health metrics and other information. The Alcatel-Lucent 5620 SAM Technology Pack supports multiple input files per UBA, where each input file contains data for one polling period only. The syntax for these bulk input files is discussed in Bulk input file name. The Alcatel-Lucent 5620 SAM Technology Pack proides seeral files that interpret these bulk input files. See Bulk adapter design files for more information. Bulk input file name In the Alcatel-Lucent 5620 SAM enironment, the inentory and metrics are located in separate bulk input files. Inentory bulk input file name The Alcatel-Lucent 5620 SAM Technology Pack uses the following syntax for inentory file names: proiso-inentorytype-daterequested-timerequested-* Here are some example inentory file names: proiso-physicalport proiso-mplsinterface proiso-iesl3accessinterface Bulk adapter design files Tioli Netcool Performance Manager bulk adapters can support seeral data formats for bulk input files, for example CSV, XML, and binary. The Alcatel-Lucent 5620 SAM serer produces data in XML format, and uses JMS for notification of inentory changes. Each UBA technology pack proides at least one bulk adapter design file to define the data format supported by that technology pack. Technology pack deelopers implement bulk adapter design files using JaaScript. Some technology packs proide seeral bulk adapter design files, each of which handles a specific bulk input file format. 30 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

39 A bulk adapter design file typically can process both inentory and metrics data from the same bulk input file, and proides a function that creates the bulk collection formula names. When the inentory and metrics are located in separate bulk input files (as is the case in the Alcatel-Lucent 5620 SAM enironment), a technology pack deeloper typically implements seeral types of bulk adapter design files. The Alcatel-Lucent 5620 SAM Technology Pack proides the following types of bulk adapter design files: SAMIF design files UBA design files BLB design files SAMIF design files The SAM Inentory File (SAMIF) adapter is a DataChannel application that interprets and parses bulk input files that contain inentory data. A technology pack deeloper implements SAMIF design files that tell the SAMIF adapter application how to interpret and parse these bulk input files. The main SAMIF design file, SAMIFAdaptor.js, contains global ariable declarations and statements that import the other SAMIF design files. The Alcatel-Lucent 5620 SAM Technology Pack proides the following SAMIF design files: SAMIF_aingr_aengr_forwarding_class.js SAMIF_aingr_aengr_policy.js SAMIF_aingr_aengr_queue.js SAMIF_aosqos_policy.js SAMIF_cfm_ethernet.js SAMIF_cfm_loopback.js SAMIF_cfm_oneway_delay.js SAMIF_cfm_twoway_delay.js SAMIF_equipment_cardSlot.js SAMIF_equipment_channel.js SAMIF_equipment_hw_enironment.js SAMIF_equipment_physical_port.js SAMIF_equipment_shelf.js SAMIF_icmp_ping.js SAMIF_lag_interface.js SAMIF_mpls_dynamic_lsp.js SAMIF_mpls_interface.js SAMIF_mpls_ping.js SAMIF_mpls_site.js SAMIF_ppp_control_protocol.js SAMIF_ppp_interface.js SAMIF_rtr_irtual_router.js SAMIF_selectJmsVersion.js SAMIF_serice_access_interface.js SAMIF_serice_access_point.js SAMIF_serice_site_ping.js SAMIF_sq_aggregation_scheduler.js SAMIF_st_sdp_binding.js Chapter 4. Additional configuration steps for certain UBA Technology Packs 31

40 SAMIF_st_tunnel_ping.js SAMIF_st_cc_ping.js SAMIFAdaptor.js SAMIF_cfm_single_ended_loss.js SAMIF_ethernetoam_mep.js UBA design files The Uniersal Bulk Adaptor (UBA) is a DataChannel application that interprets and parses bulk input files that contain inentory and metrics data, or (as is the case in the Alcatel-Lucent 5620 SAM enironment) metrics data only. A technology pack deeloper implements UBA design files that tell the UBA application how to interpret and parse these bulk input files. The current ersion of the Alcatel-Lucent 5620 SAM Technology Pack supports two UBA Bulk Collectors. Therefore, the Alcatel-Lucent 5620 SAM Technology Pack proides two main UBA design files: The SAMUBAAdaptor_polled.js file is used by the first UBA Bulk Collector and handles most of the metrics. The SAMUBAAdaptor_accounting.js file is used by the second (accounting) UBA Bulk Collector and handles the accounting metrics. These metrics are serice-oriented metrics. The Alcatel-Lucent 5620 SAM Technology Pack proides the following UBA design files: SAMUBA_aosqos_policy.js SAMUBA_aail_aggregator.js SAMUBA_aail_extensions.js SAMUBA_aail_operator.js SAMUBA_aail_schema.js SAMUBA_cfm_ethernet.js SAMUBA_cfm_oneway_delay.js SAMUBA_equipment_allocated_memory.js SAMUBA_equipment_aailable_memory.js SAMUBA_equipment_cardSlot.js SAMUBA_equipment_digital_diagnostic_monitoring.js SAMUBA_equipment_interface.js SAMUBA_equipment_interface_additional.js SAMUBA_equipment_media_independent.js SAMUBA_equipment_system_cpu.js SAMUBA_equipment_system_memory.js SAMUBA_ethernet_equipment_dot3_stats.js SAMUBA_hw_enironment.js SAMUBA_metrics.js SAMUBA_mpls_interface.js SAMUBA_mpls_site.js SAMUBA_mss.js SAMUBA_nqueue_combined_network_egress.js SAMUBA_nqueue_combined_network_ingress.js SAMUBA_OAM_ping_results.js 32 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

41 SAMUBA_ppp_control_protocol.js SAMUBA_ppp_interface.js SAMUBA_rtr_route_stats.js SAMUBA_schema.js SAMUBA_sdp_binding_base_stats.js SAMUBA_sc_complete_serice_egress.js SAMUBA_sc_complete_serice_ingress.js SAMUBA_sc_pppoe.js SAMUBAAdaptor_accounting.js SAMUBAAdaptor_polled.js SAMUBA_cfm_single_ended_loss.js BLB design files The Bulk Load Balancer (BLB) adapter is a DataChannel application that requests bulk data files from the SAM serer. The BLB then passes the bulk data files to the UBA for processing. The BLB also parses ID map files receied from the SAMIF, to understand what inentory exists. The Alcatel-Lucent 5620 SAM Technology Pack proides the following BLB design file: SAMBLBAdaptor.js Other JaaScript files The Alcatel-Lucent 5620 SAM Technology Pack also proides the following JaaScript files, which are used internally: AppLogger.js jms_2_0.js jms_2_1.js jms_3_0.js SAM_app_config.js SAM_hash_array.js SAM_property_mapping.js SAM_property_storage.js SAM_soap_filter.js SAMCommon.js SAMDomainModel.js Setting up the Alcatel-Lucent 5620 SAM serers The SAM serer administrator must set up the appropriate SAM serers enironment so that the Alcatel-Lucent 5620 SAM Technology Pack operates correctly. About this task Setting up the Alcatel-Lucent 5620 SAM serers includes the following tasks: Install SAM on the primary and redundant serers The SAM serer administrator should hae installed SAM on primary and redundant serers. The Alcatel-Lucent 5620 SAM Technology Pack accesses the SAM serers to request the inentory and metrics. Chapter 4. Additional configuration steps for certain UBA Technology Packs 33

42 Synchronize the clocks Use the appropriate tool to ensure that the clocks on the SAM serer and the serer on which the Tioli Netcool Performance Manager DataChannel is installed are identical. For example, make sure the Coordinated Uniersal Time (UTC) on the serer on which Tioli Netcool Performance Manager DataChannel is operating matches the UTC time on the serer on which Alcatel-Lucent 5620 SAM is operating. Install the Alcatel-Lucent 5620 SAM Client GUI The SAM serer administrator should hae installed the Alcatel-Lucent 5620 SAM Client GUI on some client computer or serer. During the installation, the SAM serer administrator configured the IP addresses of the SAM primary and redundant serers. Configure an OSS user account The SAM serer administrator uses the Alcatel-Lucent 5620 SAM Client GUI to configure an OSS (operational support system) user account from the client computer or serer. This user account consists of a username and password that allows the user to access the SAM primary and redundant serers. This OSS user account should not hae administratie priileges. The SAM serer administrator should record the username and password for this OSS user account and keep it in a secure place. The DataChannel BLB application needs access to this OSS account. The Alcatel-Lucent 5620 SAM Technology Pack supplies the following parameters in which the preiously listed OSS user account information can be specified: SAM.USERNAME SAM.PASSWORD The Alcatel-Lucent 5620 SAM Technology Pack supplies these parameters for Tioli Netcool Performance Manager ersion and later. These parameters are in the pack XSD file. You specify alues for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information about adding a bulk collector, see the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager Installation Guide. Configure the SAM accounting and polling statistics Accounting policies are releant to the Access Interfaces and the metrics that they report. The type of accounting policy on an Access Interface determines the metrics that are reported. When inentory is collected, Tioli Netcool Performance Manager learns the accounting policy for each Access Interface. From these accounting policies, the Alcatel-Lucent 5620 SAM Technology Pack can determine the accounting policy type. The Alcatel-Lucent 5620 SAM defines and manages accounting policies, which determine how SAM accounting statistics are collected. The Alcatel-Lucent 5620 SAM Technology Pack currently supports two types of SAM accounting statistic: access-port statistics and network-port statistics. The accounting package proides a maximum of 13 actie accounting policies, one for each type of record for the eight access-port statistics types and for the fie network-port statistics types. 34 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

43 The SAM serer administrator uses the Alcatel-Lucent 5620 SAM Client GUI to configure SAM accounting statistics on the primary and redundant SAM serers. The Alcatel-Lucent 5620 SAM Technology Pack supports the accounting policies listed in the Table below, depending on the type of nodes being monitored. Table 1. Supported accounting policies Accounting policy CombinedNetworkEgressOctetsLogRecord CombinedNetworkIngressOctetsLogRecord CompleteSericeEgressPacketOctets LogRecord CompleteSericeIngressPacketOctets LogRecord SericeEgressOctetsLogRecord SericeEgressPacketsLogRecord SericeIngressOctetsLogRecord SericeIngressPacketsLogRecord Description Manages the collection of octet actiity for egress network queues. Manages the collection of octet actiity for ingress network queues. Manages the collection of packet and octet actiity for egress serice queues. Manages the collection of packet and octet actiity for ingress serice queues. Manages the collection of octet actiity for egress serice queues. Manages the collection of packet actiity for egress serice queues. Manages the collection of octet actiity for ingress serice queues. Manages the collection of packet actiity for ingress serice queues. Note: The serice.sericeegressoctetslogrecord class and the serice.sericeegresspacketslogrecord class are mutually exclusie. You cannot collect metrics for both classes at the same time. Similarly, the serice.sericeingressoctetslogrecord class and the serice.sericeingresspacketslogrecord class are mutually exclusie. You cannot collect metrics for both classes at the same time. The SAM serer administrator uses the appropriate utility to configure polling statistics for SAM statistics classes. To configure polling statistics for these SAM statistics classes, enable the appropriate MIBs on the primary and redundant SAM serers. The default Tioli Netcool Performance Manager collection period for all types of SAM statistics is set to eery fifteen minutes, so the SAM serer policies should be configured to match this default alue. Note: The collection period for any type of SAM statistics must be set to the same alue as the collection period for the corresponding Tioli Netcool Performance Manager requests. For information about how to change the collection period for SAM statistics, see Changing the collection period for SAM accounting statistics on page 71. Enable the MIBs for the SAM statistics classes: Chapter 4. Additional configuration steps for certain UBA Technology Packs 35

44 SAM serer administrator must enable all of the MIBs listed in the table for the Alcatel-Lucent 5620 SAM Technology Pack. The first column of the table identifies the SAM statistics class on which to enable polling statistics; the second column identifies the MIBs to enable for the SAM statistics classes; and the third column identifies the object types to enable. The SAM serer administrator can enable additional object types, but the Alcatel-Lucent 5620 SAM Technology Pack expects at a minimum the ones listed in the third column. Table 2. MIBs to enable for SAM statistics classes SAM statistics class MIB Object types equipment.allocatedmemory TIMETRA-SYSTEMMIB sgimemorypoolallocat ed StatsLogRecord equipment.aailablememory TIMETRA-SYSTEMMIB sgimemoryaailable StatsLogRecord equipment.interface AdditionalStatsLogRecord IF-MIB ifxentry equipment.interfacestats LogRecord IF-MIB (located in the file named rfc2233- IF-MIB) ifentry equipment.mediaindependent HC-RMON-MIB mediaindependententry StatsLogRecord equipment.systemcpustats TIMETRA-SYSTEMMIB sgicpuusage LogRecord equipment.systemmemory TIMETRA-SYSTEMMIB sgimemoryused StatsLogRecord mpls.mplsinterfacestats TIMETRA-MPLS-MIB RtrMplsIfStatEntry LogRecord ppp.pppstatslogrecord and TIMETRA-PPP-MIB tmnxpppentry ppp.pppcontrolprotocol st.sdpbindingbasestats TIMETRA-SERV-MIB sdpbindbasestatsentr y LogRecord ethernetequipment.dot3 EtherLike-MIB dot3statsentry StatsLogRecord mpls.sitestatslogrecord TIMETRA-MPLS-MIB RtrMplsGeneralStatE ntry serice.pppoesapstats LogRecord TIMETRA-PPPOEMIB tmnxpppoesapstatsent ry sq.custmultiscsiteing SchedPlcyPortStatsLogRecord sq.custmultiscsiteegr SchedPlcyPortStatsLogRecord aosqos.qosingresspolicy StatsLogRecord equipment.cardhealth StatsLogRecord TIMETRA-SERV-MIB TIMETRA-SERV-MIB ALCATEL-IND1- QOS-MIB ALCATEL-IND1- HEALTH-MIB custmultiscsiteings chedplcyportstatsent ry custmultiscsiteegrs chedplcyportstatsent ry alaqosruleentry healthmoduleentry Configure FTP accounts on the primary and redundant SAM serers The SAM serer administrator uses the ftp utility to configure FTP user accounts on the primary and redundant SAM serers 36 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

45 The FTP users must hae access to the SAM XML output directory, which by default is /opt/5620sam/serer/xml_output. The FTP users must also hae permission to delete files. Important: You must set the permissions for the SAM XML output directory and the parent directories so that the DataChannel BLB and SAMIF applications can successfully retriee the XML source input files. The SAM serer administrator should record the following information about the FTP user accounts and keep this information in a secure place: User names for the FTP accounts on SAM serer 1 and SAM serer 2 Encrypted passwords for the FTP accounts on SAM serer 1 and SAM serer 2 Host names of SAM serer 1 and SAM serer 2 The name of the serer on which the Alcatel-Lucent 5620 SAM Technology Pack was installed The DataChannel BLB and SAMIF applications need to retriee the XML source input files from these two FTP accounts. The Alcatel-Lucent 5620 SAM Technology Pack supplies the following URI-related parameters in which the preiously listed FTP account information can be specified: SAM.EXPORT_URI SAM.EXPORT_URI_2 The Alcatel-Lucent 5620 SAM Technology Pack supplies these parameters. These parameters are supplied in the pack s XSD file. You specify alues for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information about adding a UBA Bulk Collector, see the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager Installation Guide. For conenience, the descriptions for these parameters are proided in Appendix A, UBA parameters (Tioli Netcool/Proiso and Tioli Netcool Performance Manager). Configure the HTTP SOAP and JMS accounts The SAM serer administrator uses the Alcatel-Lucent 5620 SAM Client GUI to configure HTTP SOAP and JMS accounts on the primary and redundant SAM serers. The SAM serer administrator should record the following information about the HTTP SOAP and JMS user accounts and keep it in a secure place: Host name of SAM serer 1 that hosts HTTP SOAP and JMS accounts Host name of SAM serer 2 that hosts HTTP SOAP and JMS accounts The DataChannel BLB and SAMIF applications need to know about these HTTP SOAP accounts and the SAMIF needs to know about the JMS accounts. The Alcatel-Lucent 5620 SAM Technology Pack supplies the following parameters in which the preiously listed HTTP SOAP and JMS account information can be specified: SAM.SOAP_URI SAM.SOAP_URI_2 SAM.JMS_URI SAM.JMS_URI_2 Chapter 4. Additional configuration steps for certain UBA Technology Packs 37

46 The Alcatel-Lucent 5620 SAM Technology Pack supplies these parameters. These parameters are supplied in the pack s XSD file. You specified alues for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information on adding a UBA Bulk Collector, see the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager: Installation Guide. Specify the JMS port The DataChannel SAMIF application must hae access to the JMS accounts that the SAM serer administrator created on the primary and redundant SAM serers. The SAM.JMS_PORT parameter specifies the JMS port number for the SAM primary serer. Two related parameters (SAM.JMS_URI and SAM.JMS_URI_2) identify, using http URLs, the JMS account locations on the primary and redundant SAM serers. These URI-related parameters use the JMS port number specified for the SAM.JMS_PORT parameter. You configure the JMS port number on the SAM serer when you install or reconfigure the SAM serer. The alue of the JMS port number depends on the number of SAM serers in your configuration, as follows: If your configuration has two SAM serers, set the SAM.JMS_PORT parameter to port number 1100 for both the primary serer and the redundant serer. If your configuration is a standalone SAM serer, set the SAM.JMS_PORT parameter to port number Note: Ensure that you configure the SAM.JMS_PORT parameter to hae the same alue as the corresponding alue on the SAM serer. The Alcatel-Lucent 5620 SAM Technology Pack supplies this parameter. This parameter is supplied in the pack s XSD file. You specified a alue for this parameter as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information about adding a UBA Bulk Collector, see the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager: Installation Guide. Install the JRE 1.6 or later Enironment The SAMIF application expects that the serer on which the Alcatel-Lucent 5620 SAM Technology Pack was installed is running the JAVA Run Time Enironment (JRE) 1.6 or later. More specifically, the SAMIF application looks for the JRE 1.6 in the standard location, which is /usr/jaa/jre. If the JRE 1.6 is installed in a nonstandard location, the SAMIF needs a way to locate it. The SAM.JAVA_PATH parameter identifies the nonstandard location of the JRE 1.6. The Alcatel-Lucent 5620 SAM Technology Pack supplies this parameter. This parameter is supplied in the pack s XSD file. You specified a alue for this parameter as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information about adding a UBA Bulk Collector, see the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager: Installation Guide. Set up ping tests The SAM serer enables SAM serer administrators to run ping tests in order to receie information about traffic latency and jitter. 38 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

47 The results from the tests can include SAM statistics such as round-trip time, one-way trip time, jitter, and so on. These test results can be collected as metrics against OAM Test object subelements representing the tests. Note: This section describes one method of creating OAM (ping) tests. This method uses the Alcatel-Lucent 5620 SAM Client GUI to set up the OAM test to run periodically using the scheduler on the SAM serer. To run the OAM test on the SAM serer, you must set the NE scheduler setting to off. This is only one method for running OAM tests and is proided for users who hae no knowledge about how to run OAM tests. In other methods for running OAM tests, the NE scheduler setting can be set to on. In any method employed to run the OAM tests, the period of the tests must be set to the same alue as the period for the metric requests. The default alue is fifteen minutes. A SAM serer administrator can create ping tests in two ways: Alcatel-Lucent 5620 SAM Client GUI The Alcatel-Lucent 5620 SAM Client GUI allows a SAM serer administrator to set up a ping test, specifying the period of the test, the type of test, and so on. OSS requests The SAM serer administrator may also establish OSS requests that will create ping tests on the SAM serer. Although these two methods are aailable, the Alcatel-Lucent 5620 SAM Technology Pack expects that a SAM serer administrator will manually set up ping tests using the Alcatel-Lucent 5620 SAM Client GUI. For more information about setting up these ping tests, see the Alcatel-Lucent 5620 Serice Aware Manager Release 7.0 User Guide. To collect ping-related SAM statistics that are meaningful within Tioli Netcool Performance Manager, multiple consecutie data points need to be collected for any particular OAM Test object subelement. Thus, it is recommended that ping tests be set up to run on a schedule that lasts for a significant duration (minimum three hours). This section summarizes the steps to follow. See the Alcatel-Lucent 5620 Serice Aware Manager Release 7.0 User Guide for details. Create a test suite. Make sure the NE Scheduable option is not selected so that the test schedule runs on the SAM serer and not the routers themseles. Create one or more ping tests. The Alcatel-Lucent 5620 SAM Technology Pack supports seeral types of ping tests. Remember not to select the NE Scheduable option. Make sure the tests run without errors. Add the ping tests to the test suite. Create a schedule to run the test suite. Set the schedule to run at the same frequency as the Tioli Netcool Performance Manager collection requests for jitter and latency. For example, if Tioli Netcool Performance Manager collection requests occur eery fifteen minutes, then set the schedule to run the ping test suite eery fifteen minutes. Note: Ensure that you set the frequency to a alue that is consistent with the other collection periods. See Changing the collection period for SAM accounting statistics on page 71 for guidelines about setting this schedule. Chapter 4. Additional configuration steps for certain UBA Technology Packs 39

48 Apply the schedule to the test suite and run the tests contained in the suite. Each time a test completes, Tioli Netcool Performance Manager collects a set of metrics. SAM serer administrators can run seeral types of ping tests to measure traffic characteristics at different leels of the network stack. Each ping test is represented by its own SAM class and associated ping result class. For more information about these classes, see the Alcatel-Lucent 5620 SAM XML Reference - Release 7.0 documentation. Configure the technology pack In this topic, you will learn how to configure the Alcatel-Lucent 5620 SAM Technology pack. Before you begin Ensure that you: Hae the following software and documentation for your ersion of Tioli Netcool Performance Manager: IBM Tioli Netcool Performance Manager Technology Pack Release Notes for the current technology pack release IBM Tioli Netcool Performance Manager Installation Guide. IBM Tioli Netcool Performance Manager Pack Installation and Configuration Guide. IBM Tioli Netcool Performance Manager Upgrade Guide (if you are upgrading the core software). IBM Tioli Netcool Performance Manager Technology Pack Upgrade Guide (if you are upgrading the technology pack software). IBM Tioli Netcool Performance Manager DataMart Configuration and Operation Guide. Important: Refer to this guide to run a bulk inentory profile. Access to the Tioli Netcool Performance Manager DataMart serer An X Window serer on the DataMart serer. Note: (Tioli Netcool Performance Manager pre-4.4.3) If there is no graphics card on the DataMart serer, you can install the Xfb irtual frame buffer package to proide X Window serices, as described in the IBM Tioli Netcool Performance Manager Installation Guide. Access to the SilerStream serer. Access to the Tioli Integrated Portal Access to the DataChannel serer. Hae completed the following tasks: Reiewed the release notes for the current technology pack. Note: Release notes contain important information you need to consider before installing a technology pack. They also contain information on specific patches that need to be installed before you configure a technology pack. Installed the current ersion of the Tioli Netcool Performance Manager components, as described in the IBM Tioli Netcool Performance Manager Installation Guide. 40 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

49 Installed the Alcatel-Lucent 5620 SAM Technology Pack. Note: Installation instructions for a technology pack can be found in the IBM Tioli Netcool Performance Manager Pack Installation and Configuration Guide. Upgrade instructions for a technology pack can be found in the IBM Tioli Netcool Performance Manager Technology Pack Upgrade Guide. Localization is done automatically during installation of the technology pack. Configured at least one DataChannel. Configured two UBA Bulk Collector subchannels. Created a user on the Alcatel-Lucent 5620 SAM serer with permission to ftp and delete files. Configured the technology-specific components. The Alcatel-Lucent 5620 SAM Technology Pack requires that you configure the following technology-specific components: Bulk Load Balancer (BLB) DataSync 5620 SAM (also referred to as SAMIF or SAM Inentory File) You configured these components as follows: Tioli Netcool/Proiso V4.4.3 and Tioli Netcool Performance Manager As part of the DataChannel installation, you: 1. Loaded the pack XSD file into an existing topology. 2. Added two UBA Bulk Collectors and associated them with the Alcatel-Lucent 5620 SAM Technology Pack. 3. Modified the technology pack-specific parameters for the BLB and SAMIF. Note: At this time, you also modified technology pack-specific parameters for the UBA. 4. Redeployed the updated topology. See the IBM Tioli Netcool Performance Manager Pack Installation and Configuration Guide for more information. Note: You will hae another opportunity to modify these pack-specific UBA, BLB, and SAMIF parameters during pack configuration, as described in this chapter. To configure the Alcatel-Lucent 5620 SAM Technology Pack, follow these steps: Procedure 1. Load the DataMart enironment. To load the shell with the DataMart enironment, follow these steps: a. Log in to the DataMart serer as puser. b. Change your working directory to the DataMart home directory (/opt/datamart, by default), using the following command: $cd /opt/datamart c. Load the shell with the DataMart enironment, by sourcing the datamart.en file, as follows: $. /opt/datamart/datamart.en Note: After you load the DataMart enironment into the shell, the PVMHOME ariable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this ariable has been set. 2. Copy technology-specific files from the DataMart serer to the DataChannel serer. Technology-specific files are used to associate a UBA technology pack with a specific instance of the UBA. Chapter 4. Additional configuration steps for certain UBA Technology Packs 41

50 Note: While it is possible to install DataMart and DataChannel on the same serer, in a typical installation these modules are installed on separate serers. If this is the case, use ftp to copy the technology-specific files. Otherwise, if DataMart and DataChannel are on the same serer, use the cp command to copy the files to the appropriate DataChannel directory. To copy technology-specific files to the DataChannel serer, follow these steps: a. Log in to the Tioli Netcool Performance Manager DataChannel serer by entering the user name and password that you specified when installing and configuring a DataChannel. The default user name and password are puser and PV, respectiely. b. Change your working directory to the DATA_CHANNEL_HOME/scripts/ alcatel_5620_sam directory by entering the following command, replacing DATA_CHANNEL_HOME with the DataChannel home directory (/opt/datachannel, by default): $ cd DATA_CHANNEL_HOME/scripts/ alcatel_5620_sam c. Using the ftp utility in text mode, log into the DataMart serer using the appropriate user name and password (puser and PV, by default). d. Using the cd subcommand, change your working directory to the $PVMHOME/APFiles/alcatel_5620_sam/datachannel/scripts/ alcatel_5620_sam directory. e. Using the get subcommand, copy the bulk adapter design files (*.js), scripts (if any), and other files (if any) from the DataMart serer to the DataChannel serer. f. Exit the ftp utility by entering the bye subcommand. g. Verify that the technology-specific files are now located in the target directory as follows: (Tioli Netcool/Proiso and Tioli Netcool Performance Manager) Verify that the bulk adapter design files (*.js), scripts (if any), other files (if any) are now located in the DATA_CHANNEL_HOME/scripts/ alcatel_5620_sam directory. 3. Copy the samoss.jar file to the DataChannel serer. In the preious step, you copied technology-specific files from the DataMart serer to the DATA_CHANNEL_HOME/scripts/alcatel_5620_sam directory on the DataChannel serer. The technology-specific files included SamJms.jar, the jar file required by the Alcatel-Lucent 5620 SAM Serer. The SamJms.jar file requires that the samoss.jar file also be in the DATA_CHANNEL_HOME/scripts/ alcatel_5620_sam directory. The samoss.jar file is distributed on a SAM distribution DVD referred to as the 5620 SAM software DVD-ROM, and is located in the following directory: <SAM_ROOT_RELEASE_DIR>/nms/ integrations/sam_o You must copy the samoss.jar file from the directory on the DVD to the DATA_CHANNEL_HOME/scripts/alcatel_5620_sam directory (/opt/datachannel/ scripts/alcatel_5620_sam, by default) on the DataChannel serer. After you complete the copy operation, the DATA_CHANNEL_HOME/scripts/ alcatel_5620_sam directory contains the samoss.jar file, the Bulk Adaptor Design files, the alcatel_5620_sam_sample_dc.cfg template file (Tioli Netcool Performance Manager pre only), SamJms.jar, and any other technology-specific files. 4. Actiate data collection requests. During installation of the technology pack, all predefined data collection requests are promoted to the database and set to inactie (that is, idle displays in the Actie column of the Tioli Netcool Performance Manager DataMart Request Editor). You need to actiate these 42 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

51 predefined data collection requests using the Request Editor. To set data collection requests to actie, follow these steps: a. Change your working directory to $PVMHOME/bin (/opt/datamart/bin, by default) on the DataMart serer. b. Inoke the DataMart GUI by entering the following command and pressing Enter: $ pm c. Click the Configuration tab, then click Request Editor to open the Request Editor. d. Click the Collection tab. e. Click Refresh. The predefined data collection requests are loaded into the Request Editor from the database. f. Click the Inactie button in the Filter group box to display only idle requests. g. In the Sub-Element Groups pane, select all idle data collection requests in the following group or groups: Root->Sub-Element Collect->Alcatel- Lucent 5620 SAM h. Click the Actie box under Details. The Request Editor toggles the idle setting for these data collection requests from idle to actie in the Actie column. i. Click Sae. 5. Edit pack-specific SAMIF, UBA, and BLB parameters, based on the following Tioli Netcool Performance Manager platforms: Tioli Netcool Performance Manager and Tioli Netcool Performance Manager In this release of Tioli Netcool Performance Manager, you were instructed to modify the technology pack-specific SAMIF, UBA, and BLB parameters when you installed the Alcatel-Lucent 5620 SAM Technology Pack, using the Topology Editor. If you did not modify the SAMIF, UBA, and BLB parameters with site-specific alues or you want to make additional edits, you can do so now. Otherwise, you can go to the next step. See the IBM Tioli Netcool Performance Manager Pack Installation and Configuration Guide for more information. 6. Load the DataChannel enironment. In subsequent steps, you will execute dccmd commands. To ensure that you can run these commands, load the shell with the DataChannel enironment by following these steps: a. Log in to the DataChannel serer as puser. b. Change your working directory to the DataChannel home directory (/opt/datachannel, by default), using the following command: $cd /opt/datachannel c. Load the shell with the DataChannel enironment, by sourcing the datachannel.en file, as follows: $. /opt/datachannel/datachannel.en 7. Restart the DataChannel to actiate the UBA and read in changes to the deployed topology (4.4.3 and Tioli Netcool Performance Manager). a. Open a terminal emulator on the DataChannel serer. b. Use the dccmd command to stop all DataChannel applications: $ dccmd stop all c. Use the dccmd command to release all daemons running in the DataChannel: $ dccmd forget all d. Use the following command to find the process identifiers (pids) associated with the DataChannel isual processes: $ findisual e. Use the following commands to stop each DataChannel isual process: $ kill -9 <cnsw_pid> Chapter 4. Additional configuration steps for certain UBA Technology Packs 43

52 $ kill -9 <logw_pid> $ kill -9 <amgrw_pid> $ kill -9 <cmgrw_pid> f. Use the following commands to restart each DataChannel isual process: $ cnsw $ logw $ amgrw $ cmgrw g. Use the dccmd command to start all DataChannel applications: $ dccmd start all h. Use the dccmd command to erify that all of the DataChannel applications started properly: $ dccmd status all More specifically, make sure that the UBA application associated with the DataChannel that you configured for the Alcatel-Lucent 5620 SAM Technology Pack is running. i. Watch the output of the status switch to erify that all the necessary processes are running. If these processes are running, run the tail utility on the log file for the UBA by issuing a command similar to the following: $ tail -f DATA_CHANNEL_HOME/log/proiso.log grep UBA.<channel><collector>- more where: Variable <channel_number> <collector_number> The trailing dash ( ) after <collector_number> Meaning Is /opt/datachannel, by default. Specifies the collector number (for example, 100) that you specified when configuring this UBA Bulk Collector. Remoes extraneous log messages from your iew. That is, the trailing dash guarantees that the command displays only those messages generated by your application. The first set of messages relate to syntax checks. The following table identifies some eents to watch for during the syntax check: Eent The UBA application starts successfully, but then stops executing. The bulk adapter design file might be corrupt. The UBA application connects to the database. Meaning Typically, this eent occurs because of a licensing issue. This eent causes a syntax error before the UBA application connects to the database. This eent causes a message similar to the following example to display: DB_CONNECT Connecting to <sid> as <user> If you see this database connection message without prior errors, the UBA application has passed the syntax check. 8. Run the initial inentory. The initial inentory of elements and subelements runs automatically when you start the SAMIf component. This actiity can be time-consuming, depending on the size of the network that the Alcatel-Lucent 5620 SAM manages. In a large network, the initial inentory can take 6 to 12 hours. To run a subsequent inentory for the Alcatel-Lucent 5620 SAM Technology Pack, follow these steps: a. Login as puser on the serer that hosts the BLB process for the Alcatel-Lucent 5620 SAM Technology Pack. 44 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

53 b. Verify that all Alcatel-Lucent 5620 SAM Technology Pack components are running: $ /opt/datachannel/bin/dccmd status -channel channel# where channel# is the number of the DataChannel, which you specified when you configured the DataChannel for the Alcatel-Lucent 5620 SAM Technology Pack. c. Run the inentory utility. Note: In preious releases of the Alcatel-Lucent 5620 SAM Technology Pack samifdump was used to run the initial inentory utility. This is no longer necesssary, and may not een work, so it should not be used. Use of samifdump could mask JMS problems. To initate an inentory full dump, restart the SAMIF, and it will automatically perform an inentory dump and collection once it successfully connects to the JMS. If the full dump does not start, the JMS connection may need diagnosis. 9. Run the bulk inentory profile. The UBA application handles the inentory and metrics according to the instructions proided in the technology pack design file or files. The UBA application inserts the created elements, subelements, and metrics into the database. Howeer, the UBA application does not handle the grouping of these elements and subelements. To handle the grouping of the elements and subelements that were inserted into the database, UBA technology packs supply a bulk inentory profile. This bulk inentory profile is automatically created when the pack is installed. Bulk inentory profiles use the following name syntax: bulk_n where: Syntax item bulk_ N Meaning Identifies this as a bulk inentory profile for a UBA technology pack. Specifies the collector number (for example, 100) that the user specified when configuring this UBA Bulk Collector. You must use the Inentory Tool to run a bulk inentory profile. To run the bulk inentory profiles for this technology pack, perform the following steps: a. In the command window where you loaded the DataMart enironment, change your working directory to $PVMHOME/bin (/opt/datamart/bin, by default) on the DataMart serer. b. Inoke the DataMart GUI: $ pm c. Click Inentory Tool in the Resource tab. The Inentory Tool window appears. This window displays a list of the existing inentory profiles on the Configuration tab. The names of the inentory profiles to run are bulk_n1 and bulk_n2, where N1 and N2 are the collector numbers configured for this pack. d. On the Configuration tab, click on the bulk inentory profiles for this technology pack and then select Run Profile from the Action menu. The Lie Information tab displays messages about the status of the profiles. See the IBM Tioli Netcool Performance Manager DataMart Configuration and Operation Guide for more information about running an inentory profile. e. Optional: Eery time the UBA technology pack design file creates new elements, subelements, and metrics, you need to perform the preious steps to group the elements and subelements. One way to accomplish this task on a regular basis is to create a cron entry that make use of the inentory command. The following example shows the cron entries that periodically perform the grouping operation for the bulk inentory profiles called bulk_100 and bulk_101: Chapter 4. Additional configuration steps for certain UBA Technology Packs 45

54 0****./opt/datamart/dataMart.en && inentory -name bulk_100 -action pregrouping -reload -nox 0****./opt/datamart/dataMart.en && inentory -name bulk_100 -action grouping -reload -nox 0****./opt/datamart/dataMart.en && inentory -name bulk_101 -action pregrouping -reload -nox 0****./opt/datamart/dataMart.en && inentory -name bulk_101 -action grouping -reload -nox See the IBM Tioli Netcool Performance Manager Command Line Interface Guide for more information about the inentory command. 10. Deploy reports. After the technology pack installation completes, the rules for the new deice are automatically loaded into the database. The inentory process uses those rules to group elements and subelements. You must manually deploy (auto-group) the reports by associating them with groups in the NOC Reporting tree in the DataMart Resource Editor.To deploy the Alcatel-Lucent 5620 SAM Technology Pack reports, follow these steps: a. Open the Tioli Netcool Performance Manager DataMart Resource Editor. b. Click the ReportSEGroup tab. c. Moe the cursor to the left pane and scroll up to select any group under the SUB-ELEMENTS->NOC Reporting tree. d. Right-click and select the AutoGrouping option from the menu. The AutoGrouping option places the reports in dynamically generated groups created during inentory. e. Click Yes to continue. f. Click Close to exit the message box, or click Details to iew a description of any errors. g. Optional: You can also deploy reports on a regular basis by creating a cron entry that makes use of the inentory CLI command and the -reportgrouping option. This option instructs the inentory command to run the report grouping rules and update the deployed reports stored in the database. Report grouping rules must first hae been created before this option can be used. For information on creating report grouping rules, see the IBM Tioli Netcool Performance Manager DataMart Configuration and Operation Guide. The following example shows a cron entry that periodically performs the deploy report operation: 0****./opt/datamart/dataMart.en && inentory -nox -reportgrouping See the IBM Tioli Netcool Performance Manager Command Line Interface Guide for more information about the inentory command. Verifying resources Use the Tioli Netcool Performance Manager DataMart Resource Editor to determine whether the technology pack resources (elements, subelements, properties, and so on) were successfully discoered and created in the database during inentory. See the IBM Tioli Netcool Performance Manager DataMart Configuration and Operation Guide for information about using the DataMart Resource Editor. 46 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

55 Modifying the collection strategy This chapter describes how to modify the amount of data that is managed by the Alcatel-Lucent 5620 SAM Technology Pack. You can make this modification by changing the types of data that are collected, or by changing the collection period for the SAM statistics, or both. Specifying what inentory and metrics to collect Use the include and exclude filter parameters to specify what inentory and metrics to collect. About this task These parameters are supplied in the pack XSD file. Use the Topology Editor to specify a alue for the include and exclude filter parameters when you configure the technology-specific components (BLB and SAMIF) as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. See the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager Installation Guide for more information about adding this type of collector. For information about how the filtering mechanism has changed in recent ersions of the Alcatel-Lucent 5620 SAM Technology Pack, see Changes in the filtering mechanism for inentory and metric section in IBM Tioli Netcool Performance Manager: Pack Upgrade Guide. Guidelines for using filter parameters: Use the following guidelines when using the include and exclude filter parameters to filter specific categories of inentory and metrics. These guidelines assume that you hae configured one instance of the Alcatel-Lucent 5620 SAM Technology Pack. About this task See Issues when configuring multiple Alcatel-Lucent 5620 SAM Technology Pack instances for issues related to using the include and exclude filter parameters when configuring more than one instance of the Alcatel-Lucent 5620 SAM Technology Pack. Note: If you want to collect all categories of inentory and metrics, accept the default alue for the include and exclude filter parameters. (The default alue for the include and exclude filter parameters is no alue.) You do not need to do anything further. You can skip this and subsequent sections related to the include and exclude filter parameters. Procedure 1. The inentory filters apply to the SAMIF, and the metrics filters apply to the BLB. 2. Use the first column of Table 3 to determine the subelement type for which you want to include and exclude inentory and metrics. In this example, the subelement type is Physical Port objects. Chapter 4. Additional configuration steps for certain UBA Technology Packs 47

56 3. Use the second column of Table 3 to identify the include and exclude inentory and metrics filter parameters associated with this subelement type. In this example, the inentory filter parameters are: INC_FILTER_EQUIPMENT_PHYSICAL_PORT EXC_FILTER_EQUIPMENT_PHYSICAL_PORT INC_FILTER_CFM_SINGLE_ENDED_LOSS EXC_FILTER_CFM_SINGLE_ENDED_LOSS In this example, the metrics filter parameters are: INC_FILTER_EQUIPMENT_INTERFACE EXC_FILTER_EQUIPMENT_INTERFACE INC_FILTER_EQUIPMENT_INTERFACE_ADD EXC_FILTER_EQUIPMENT_INTERFACE_ADD INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT EXC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT INC_FILTER_CFM_SINGLE_ENDED_LOSS EXC_FILTER_CFM_SINGLE_ENDED_LOSS 4. Specify the alues for the include and exclude filter parameters according to the information proided in Valid alues for include and exclude filter parameters. To include the metrics and associated inentory for a subelement, assign the appropriate alue to the include filter parameters for the inentory and metrics. Assign the same alue to all of the include filter parameters for that subelement. In this example, set the alues for the INC_FILTER_EQUIPMENT_PHYSICAL_PORT, INC_FILTER_EQUIPMENT_INTERFACE, INC_FILTER_EQUIPMENT_INTERFACE_ADD, and INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT parameters. Do not assign a alue for the exclude filter parameters. Conersely, to exclude the metrics and associated inentory for a subelement, assign the appropriate alue to the exclude filter parameters for the inentory and metrics. Assign the same alue to all of the exclude filter parameters for that subelement. In this example, set the alues for the EXC_FILTER_EQUIPMENT_PHYSICAL_PORT, EXC_FILTER_EQUIPMENT_INTERFACE, EXC_FILTER_EQUIPMENT_INTERFACE_ADD, and EXC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT parameters. Do not assign a alue for the include filter parameters. Supported filter parameters: Table 3 on page 49 proides the following information: First column -- Specifies the subelement type. Second column -- Specifies the names of the filter parameters, for the categories of inentory and metrics that are aailable for the specified subelement type. These filter parameters control the inclusion or exclusion of the different categories of inentory and metrics. Third column -- Specifies the Alcatel-Lucent 5620 SAM-O XML package inentory and metrics classes associated with the parameters listed in the second column, and the name of the Alcatel-Lucent 5620 SAM property that contains the IP address for an object, which is the default alue used to filter the inentory and metrics. See the Alcatel-Lucent 5620 SAM XML Reference - Release 7.0 documentation for descriptions of these classes. 48 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

57 Table 3. Include and exclude filter parameters and associated XML packages and classes Subelement Include and exclude filter parameters Access Interface object Inentory: INC_FILTER_IES_L3_ACCESS_INTERFACE EXC_FILTER_IES_L3_ACCESS_INTERFACE INC_FILTER_MIRROR_L2_ACCESS_ INTERFACE EXC_FILTER_MIRROR_L2_ACCESS_ INTERFACE INC_FILTER_VLL_L2_ACCESS_INTERFACE EXC_FILTER_VLL_L2_ACCESS_INTERFACE INC_FILTER_VPLS_L2_ACCESS_INTERFACE EXC_FILTER_VPLS_L2_ACCESS_INTERFACE INC_FILTER_VPRN_L3_ACCESS_INTERFACE EXC_FILTER_VPRN_L3_ACCESS_INTERFACE INC_FILTER_IPIPE_L2_ACCESS_INTERFACE EXC_FILTER_IPIPE_L2_ACCESS_INTERFACE Alcatel-Lucent 5620 SAM-O XML package class Inentory: serice.l2accessinterface serice.l3accessinterface ies.l3accessinterface mirror.l2accessinterface ll.l2accessinterface pls.l2accessinterface prn.l3accessinterface ipipe.l2accessinterface Default filter property: nodeid Metrics: N/A Metrics: Aailability metrics AOSQOS Object Inentory: INC_FILTER_AOSQOS_POLICY EXC_FILTER_AOSQOS_POLICY ALCATEL_5620_SAM.AVAIL_NAME_ SPACE Default filter property PHYSICAL_PORT Inentory: aosqos.policy Default filter property siteid Metrics: INC_FILTER_AOSQOS_POLICY EXC_FILTER_AOSQOS_POLICY Metrics: aosqos.qosingresspolicystatslogrecord Default filter property monitoredobjectsiteid Chapter 4. Additional configuration steps for certain UBA Technology Packs 49

58 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters Alcatel-Lucent 5620 SAM-O XML package class Egress Serice Queue object Ingress Serice Queue object (Alcatel- Lucent 7750 Serice Router and Alcatel- Lucent 7450 Ethernet Serice Switch) Inentory: INC_FILTER_IES_L3_ACCESS_INTERFACE EXC_FILTER_IES_L3_ACCESS_INTERFACE INC_FILTER_MIRROR_L2_ACCESS_ INTERFACE EXC_FILTER_MIRROR_L2_ACCESS_ INTERFACE INC_FILTER_VLL_L2_ACCESS_INTERFACE EXC_FILTER_VLL_L2_ACCESS_INTERFACE INC_FILTER_VPLS_L2_ACCESS_INTERFACE EXC_FILTER_VPLS_L2_ACCESS_INTERFACE INC_FILTER_VPRN_L3_ACCESS_INTERFACE EXC_FILTER_VPRN_L3_ACCESS_INTERFACE Metrics: INC_FILTER_COMPLETE_SERVICE_EGRESS EXC_FILTER_COMPLETE_SERVICE_EGRESS INC_FILTER_COMPLETE_SERVICE_INGRESS EXC_FILTER_COMPLETE_SERVICE_INGRESS Inentory: ies.l3accessinterface mirror.l2accessinterface ll.l2accessinterface pls.l2accessinterface prn.l3accessinterface Default filter property nodeid Metrics: serice.completesericeegresspacket OctetsLogRecord serice.completesericeegresspacket OctetsLogRecord serice.completesericeegresspacket OctetsLogRecord Default filter property monitoredobjectsiteid 50 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

59 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters Alcatel-Lucent 5620 SAM-O XML package class Channel object CardSlot Object Inentory: INC_FILTER_CHANNEL_DS0_GROUP EXC_FILTER_CHANNEL_DS0_GROUP INC_FILTER_CHANNEL_DS1E1 EXC_FILTER_CHANNEL_DS1E1 INC_FILTER_CHANNEL_DS3E3 EXC_FILTER_CHANNEL_DS3E3 INC_FILTER_CHANNEL_STS1 EXC_FILTER_CHANNEL_STS1 INC_FILTER_CHANNEL_STS12 EXC_FILTER_CHANNEL_STS12 INC_FILTER_CHANNEL_STS192 EXC_FILTER_CHANNEL_STS192 INC_FILTER_CHANNEL_STS3 EXC_FILTER_CHANNEL_STS3 INC_FILTER_CHANNEL_STS48 EXC_FILTER_CHANNEL_STS48 INC_FILTER_CHANNEL_TRIB EXC_FILTER_CHANNEL_TRIB INC_FILTER_CHANNEL_TRIB_GROUP EXC_FILTER_CHANNEL_TRIB_GROUP INC_FILTER_CHANNEL_TU3 EXC_FILTER_CHANNEL_TU3 INC_FILTER_CHANNEL_TUG3_GROUP EXC_FILTER_CHANNEL_TUG3_GROUP Metrics: INC_FILTER_EQUIPMENT_INTERFACE EXC_FILTER_EQUIPMENT_INTERFACE INC_FILTER_EQUIPMENT_INTERFACE_ADD EXC_FILTER_EQUIPMENT_INTERFACE_ADD Inentory: INC_FILTER_EQUIPMENT_CARD_SLOT EXC_FILTER_EQUIPMENT_CARD_SLOT Inentory: tdmequipment.ds0channelgroup tdmequipment.ds1e1channel tdmequipment.ds3e3channel sonetequipment.sts1channel sonetequipment.sts12channel sonetequipment.sts192channel sonetequipment.sts3channel sonetequipment.sts48channel sonetequipment.tributarychannel sonetequipment.tributarygroup sonetequipment.tu3channel sonetequipment.tug3group Default filter property siteid Metrics: equipment.interfacestatslogrecord equipment.interfaceadditionalstatslogrecord Default filter property: monitoredobjectsiteid Inentory: equipment.cardslot Default filter property: siteid Metrics: INC_FILTER_EQUIPMENT_CARD_SLOT EXC_FILTER_EQUIPMENT_CARD_SLOT Metrics: equipment.cardhealthstatslogrecord Default filter property: monitoredobjectsiteid Chapter 4. Additional configuration steps for certain UBA Technology Packs 51

60 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters Alcatel-Lucent 5620 SAM-O XML package class Egress Serice Queue object Ingress Serice Queue object (Alcatel- Lucent 7705 Serice Aggregation Router and Alcatel- Lucent 7210 Serice Access Switch) Inentory: INC_FILTER_IES_L3_ACCESS_INTERFACE EXC_FILTER_IES_L3_ACCESS_INTERFACE INC_FILTER_MIRROR_L2_ACCESS_ INTERFACE EXC_FILTER_MIRROR_L2_ACCESS_ INTERFACE INC_FILTER_VLL_L2_ACCESS_INTERFACE EXC_FILTER_VLL_L2_ACCESS_INTERFACE INC_FILTER_VPLS_L2_ACCESS_INTERFACE EXC_FILTER_VPLS_L2_ACCESS_INTERFACE INC_FILTER_VPRN_L3_ACCESS_INTERFACE EXC_FILTER_VPRN_L3_ACCESS_INTERFACE Metrics: INC_FILTER_SERVICE_EGRESS EXC_FILTER_SERVICE_EGRESS INC_FILTER_SERVICE_INGRESS EXC_FILTER_SERVICE_INGRESS Inentory: ies.l3accessinterface mirror.l2accessinterface ll.l2accessinterface pls.l2accessinterface prn.l3accessinterface Default filter property: nodeid Metrics: serice.sericeegressoctetslogrecord Or serice.sericeegresspacketslogrecord serice.sericeingressoctetslogrecord Or serice.sericeingresspacketslogrecord Default filter property: monitoredobjectsiteid Egress Serice Queue object Ingress Serice Queue object (Alcatel- Lucent 7750 Serice Router and Alcatel- Lucent 7450 Ethernet Serice Switch) Inentory: INC_FILTER_IES_L3_ACCESS_INTERFACE EXC_FILTER_IES_L3_ACCESS_INTERFACE INC_FILTER_MIRROR_L2_ACCESS_ INTERFACE EXC_FILTER_MIRROR_L2_ACCESS_ INTERFACE INC_FILTER_VLL_L2_ACCESS_INTERFACE EXC_FILTER_VLL_L2_ACCESS_INTERFACE INC_FILTER_VPLS_L2_ACCESS_INTERFACE EXC_FILTER_VPLS_L2_ACCESS_INTERFACE INC_FILTER_VPRN_L3_ACCESS_INTERFACE EXC_FILTER_VPRN_L3_ACCESS_INTERFACE Metrics: INC_FILTER_COMPLETE_SERVICE_EGRESS EXC_FILTER_COMPLETE_SERVICE_EGRESS INC_FILTER_COMPLETE_SERVICE_INGRESS EXC_FILTER_COMPLETE_SERVICE_INGRESS Inentory: ies.l3accessinterface mirror.l2accessinterface ll.l2accessinterface pls.l2accessinterface prn.l3accessinterface Default filter property: nodeid Metrics: serice.completesericeegresspacketoctets LogRecord serice.completesericeingresspacketoctets LogRecord Default filter property: monitoredobjectsiteid 52 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

61 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters Alcatel-Lucent 5620 SAM-O XML package class Ethernet CFM Object Inentory: INC_FILTER_CFM_ONEWAY_DELAY EXC_FILTER_CFM_ONEWAY_DELAY INC_FILTER_CFM_ETHERNET EXC_FILTER_CFM_ETHERNET INC_FILTER_CFM_SINGLE_ENDED_LOSS EXC_FILTER_CFM_SINGLE_ENDED_LOSS Metrics: ethernetoam.cfmethtest ethernetoam.cfmsingleendedlosstest Default filter property: siteid Metrics: INC_FILTER_CFM_ONEWAY_DELAY EXC_FILTER_CFM_ONEWAY_DELAY INC_FILTER_CFM_ETHERNET EXC_FILTER_CFM_ETHERNET INC_FILTER_CFM_SINGLE_ENDED_LOSS EXC_FILTER_CFM_SINGLE_ENDED_LOSS Hardware EnironmentInentory: object INC_FILTER_EQUIPMENT_HW_ ENVIRONMENT EXC_FILTER_EQUIPMENT_HW_ ENVIRONMENT Metrics: ethernetoam.cfmonewaydelaytestresult ethernetoam.cfmethtestresult ethernetoam.cfmsingleendedlosstestresult Default filter property: fromnodeid Inentory: equipment.hwenironment Default filter property: siteid LAG Interface object Metrics: INC_FILTER_EQUIPMENT_HW_ ENVIRONMENT EXC_FILTER_EQUIPMENT_HW_ ENVIRONMENT Inentory: INC_FILTER_LAG_INTERFACE EXC_FILTER_LAG_INTERFACE Metrics: INC_FILTER_EQUIPMENT_INTERFACE EXC_FILTER_EQUIPMENT_INTERFACE INC_FILTER_EQUIPMENT_INTERFACE_ADD EXC_FILTER_EQUIPMENT_INTERFACE_ADD Metrics: equipment.hwenironment Default filter property: siteid Inentory: lag.interface Default filter property: siteid Metrics: equipment.interfacestatslogrecord equipment.interfaceadditionalstatslogrecord Default filter property: monitoredobjectsiteid Chapter 4. Additional configuration steps for certain UBA Technology Packs 53

62 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters MPLS Interface object Inentory: INC_FILTER_MPLS_INTERFACE EXC_FILTER_MPLS_INTERFACE Alcatel-Lucent 5620 SAM-O XML package class Inentory: mpls.interface Default filter property: nodeid MPLS Object Network Queue object Metrics: INC_FILTER_MPLS_INTERFACE EXC_FILTER_MPLS_INTERFACE Inentory: INC_FILTER_MPLS_SITE EXC_FILTER_MPLS_SITE Metrics: INC_FILTER_MPLS_SITE EXC_FILTER_MPLS_SITE Inentory: INC_FILTER_NETWORK_QUEUE EXC_FILTER_NETWORK_QUEUE Metrics: mpls.mplsinterfacestatslogrecord Default filter property: monitoredobjectsiteid Inentory: mpls.site Default filter property: nodeid Metrics: mpls.sitestatslogrecord Default filter property: monitoredobjectsiteid Inentory: nqueue.entry nqueue.forwardingclass nqueue.policy Default filter property: siteid Metrics: INC_FILTER_COMBINED_NETWORK_EGRESS EXC_FILTER_COMBINED_NETWORK_EGRESS INC_FILTER_COMBINED_NETWORK_ INGRESS EXC_FILTER_COMBINED_NETWORK_ INGRESS Metrics: serice.combinednetworkegressoctets LogRecord serice.combinednetworkingressoctets LogRecord serice.networkegresspacketslogrecord serice.networkingresspacketslogrecord INC_FILTER_NETWORK_EGRESS EXC_FILTER_NETWORK_EGRESS INC_FILTER_NETWORK_INGRESS EXC_FILTER_NETWORK_INGRESS Default filter property: monitoredobjectsiteid 54 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

63 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters OAM Test object Inentory: INC_FILTER_ICMP_PING EXC_FILTER_ICMP_PING INC_FILTER_MPLS_PING EXC_FILTER_MPLS_PING INC_FILTER_SERVICE_SITE_PING EXC_FILTER_SERVICE_SITE_PING INC_FILTER_TUNNEL_PING EXC_FILTER_TUNNEL_PING INC_FILTER_VCCV_PING EXC_FILTER_VCCV_PING INC_FILTER_CFM_LOOPBACK EXC_FILTER_CFM_LOOPBACK INC_FILTER_CFM_TWOWAY_DELAY EXC_FILTER_CFM_TWOWAY_DELAY Alcatel-Lucent 5620 SAM-O XML package class Inentory: icmp.icmpping mpls.lspping serice.siteping st.tunnelping st.vccping ethernetoam.cfmloopback ethernetoam.cfmonewaydelaytest ethernetoam.cfmtwowaydelaytest Default filter property: fromnodeid Metrics: INC_FILTER_ICMP_PING EXC_FILTER_ICMP_PING INC_FILTER_MPLS_PING EXC_FILTER_MPLS_PING INC_FILTER_SERVICE_SITE_PING EXC_FILTER_SERVICE_SITE_PING INC_FILTER_TUNNEL_PING EXC_FILTER_TUNNEL_PING INC_FILTER_VCCV_PING EXC_FILTER_VCCV_PING INC_FILTER_CFM_LOOPBACK EXC_FILTER_CFM_LOOPBACK INC_FILTER_CFM_TWOWAY_DELAY EXC_FILTER_CFM_TWOWAY_DELAY Metrics: icmp.icmppingresult mpls.lsppingresult serice.sitepingresult st.tunnelpingresult st.vccpingresult ethernetoam.cfmloopbackresult ethernetoam.cfmonewaydelaytest ethernetoam.cfmtwowaydelaytest Default filter property: fromnodeid Chapter 4. Additional configuration steps for certain UBA Technology Packs 55

64 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters Physical Port object Inentory: INC_FILTER_EQUIPMENT_PHYSICAL_PORT EXC_FILTER_EQUIPMENT_PHYSICAL_PORT Alcatel-Lucent 5620 SAM-O XML package class Inentory: equipment.physicalport Default filter property: siteid PPP Control Protocol object PPP Interface object Metrics: INC_FILTER_EQUIPMENT_INTERFACE EXC_FILTER_EQUIPMENT_INTERFACE INC_FILTER_EQUIPMENT_INTERFACE_ADD EXC_FILTER_EQUIPMENT_INTERFACE_ADD INC_FILTER_EQUIPMENT_MEDIA_ INDEPENDENT EXC_FILTER_EQUIPMENT_MEDIA_ INDEPENDENT INC_FILTER_ETHERNET_EQUIPMENT_ DOT3_STATS EXC_FILTER_ETHERNET_EQUIPMENT_ DOT3_STATS INC_FILTER_EQUIPMENT_DDM EXC_FILTER_EQUIPMENT_DDM Inentory: It is not currently possible to filter the inentory for PPP Control Protocol objects. Howeer, each PPP Control Protocol object requires an associated PPP Interface object. Therefore, the filtering that is applied to the PPP Interface object is also applied to the associated PPP Control Protocol object. Metrics: INC_FILTER_PPP_CONTROL_PROTOCOL EXC_FILTER_PPP_CONTROL_PROTOCOL Inentory: INC_FILTER_PPP_INTERFACE EXC_FILTER_PPP_INTERFACE Metrics: INC_FILTER_PPP_INTERFACE EXC_FILTER_PPP_INTERFACE Metrics: equipment.interfacestatslogrecord equipment.interfaceadditionalstatslogrecord equipment.mediaindependentstatslogrecord ethernetequipment.dot3statslogrecord equipment.digitaldiagnosticmonitoring Default filter property: monitoredobjectsiteid Inentory: ppp.pppcontrolprotocol Default filter property: Not applicable Metrics: ppp.pppcontrolprotocol Default filter property: siteid Inentory: ppp.interface Default filter property: nodeid Metrics: ppp.pppstatslogrecord Default filter property: monitoredobjectsiteid 56 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

65 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters SDP Binding object Inentory: INC_FILTER_SVT_MESH_SDP_BINDING EXC_FILTER_SVT_MESH_SDP_BINDING INC_FILTER_SVT_MIRROR_SDP_BINDING EXC_FILTER_SVT_MIRROR_SDP_BINDING INC_FILTER_SVT_SPOKE_SDP_BINDING EXC_FILTER_SVT_SPOKE_SDP_BINDING Alcatel-Lucent 5620 SAM-O XML package class Inentory: st.meshsdpbinding st.mirrorsdpbinding st.spokesdpbinding Default filter property: fromnodeid Metrics: INC_FILTER_SVT_SDP_BINDING_BASE EXC_FILTER_SVT_SDP_BINDING_BASE Metrics: st.sdpbindingbasestatslogrecord Default filter property: monitoredobjectsiteid Shelf object Inentory: INC_FILTER_EQUIPMENT_SHELF EXC_FILTER_EQUIPMENT_SHELF Inentory: equipment.shelf Default filter property: siteid Serice Access Point Object Metrics: INC_FILTER_EQUIPMENT_CPU EXC_FILTER_EQUIPMENT_CPU INC_FILTER_EQUIPMENT_MEMORY EXC_FILTER_EQUIPMENT_MEMORY Inentory: INC_FILTER_VPRN_SERVICE_ACCESS_POINT EXC_FILTER_VPRN_SERVICE_ACCESS_POINT INC_FILTER_IES_SERVICE_ACCESS_POINT EXC_FILTER_IES_SERVICE_ACCESS_POINT Metrics: equipment.systemcpustatslogrecord equipment.systemmemorystatslogrecord Default filter property: monitoredobjectsiteid Inentory: prn.sericeaccesspoint ies.sericeaccesspoint Default filter property: siteid Metrics: INC_FILTER_SVC_PPPOE EXC_FILTER_SVC_PPPOE Metrics: serice.pppoesapstatslogrecord Default filter property: monitoredobjectsiteid Chapter 4. Additional configuration steps for certain UBA Technology Packs 57

66 Table 3. Include and exclude filter parameters and associated XML packages and classes (continued) Subelement Include and exclude filter parameters Multi Serice Site object Inentory: INC_FILTER_SVQ_AGGREGATION_ SCHEDULER EXC_FILTER_SVQ_AGGREGATION_ SCHEDULER Alcatel-Lucent 5620 SAM-O XML package class Inentory: sq.aggregationscheduler Default filter property: siteid Virtual Router Metrics: INC_FILTER_MSS_INGRESS EXC_FILTER_MSS_INGRESS INC_FILTER_MSS_EGRESS EXC_FILTER_MSS_EGRESS Inentory: INC_FILTER_VIRTUAL_ROUTER EXC_FILTER_VIRTUAL_ROUTER Metrics: INC_FILTER_ROUTE_STATS EXC_FILTER_ROUTE_STATS Metrics: sq.custmultiscsiteingschedplcyportstats LogRecord sq.custmultiscsiteegrschedplcyportstats LogRecord Default filter property: monitoredobjectsiteid Inentory: rtr.virtualrouter Default filter property: siteid Metrics: rtr.routestatslogrecord Default filter property: monitoredobjectsiteid Filter parameters that apply to seeral subelement types: Some metrics apply to seeral subelement types. Take care before excluding the metrics for a particular subelement type, in case those metrics are also associated with other subelement types. In such cases, you might prefer to edit the filter to exclude the particular subelement, rather than exclude the metrics for all subelements. Table 4 table lists the metrics, and the subelement types associated with each metric. Table 4. Metrics filter parameters and associated subelement types Include and exclude filter parameters INC_FILTER_COMBINED_NETWORK_EGRESS EXC_FILTER_COMBINED_NETWORK_EGRESS INC_FILTER_COMBINED_NETWORK_INGRESS Subelement Network Queue object Network Queue object EXC_FILTER_COMBINED_NETWORK_INGRESS 58 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

67 Table 4. Metrics filter parameters and associated subelement types (continued) Include and exclude filter parameters Subelement INC_FILTER_COMPLETE_SERVICE_EGRESS EXC_FILTER_COMPLETE_SERVICE_EGRESS Egress Serice Queue object Ingress Serice Queue object (Alcatel-Lucent 7750 Serice Router and Alcatel-Lucent 7450 Ethernet Serice Switch) INC_FILTER_COMPLETE_SERVICE_INGRESS EXC_FILTER_COMPLETE_SERVICE_INGRESS INC_FILTER_EQUIPMENT_CPU EXC_FILTER_EQUIPMENT_CPU INC_FILTER_EQUIPMENT_HW_ENVIRONMENT Egress Serice Queue object Ingress Serice Queue object (Alcatel-Lucent 7750 Serice Router and Alcatel-Lucent 7450 Ethernet Serice Switch) Shelf object Hardware Enironment object EXC_FILTER_EQUIPMENT_HW_ENVIRONMENT INC_FILTER_EQUIPMENT_INTERFACE_ADD EXC_FILTER_EQUIPMENT_INTERFACE_ADD Channel object LAG Interface object Physical Port object INC_FILTER_EQUIPMENT_INTERFACE EXC_FILTER_EQUIPMENT_INTERFACE INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT Channel object LAG Interface object Physical Port object Physical Port object EXC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT INC_FILTER_EQUIPMENT_DDM INC_FILTER_EQUIPMENT_DDM EXC_FILTER_EQUIPMENT_DDM INC_FILTER_EQUIPMENT_MEMORY Shelf object EXC_FILTER_EQUIPMENT_MEMORY Chapter 4. Additional configuration steps for certain UBA Technology Packs 59

68 Table 4. Metrics filter parameters and associated subelement types (continued) Include and exclude filter parameters Subelement OAM Test object INC_FILTER_ICMP_PING EXC_FILTER_ICMP_PING INC_FILTER_MPLS_INTERFACE EXC_FILTER_MPLS_INTERFACE INC_FILTER_MPLS_PING EXC_FILTER_MPLS_PING INC_FILTER_PPP_CONTROL_PROTOCOL EXC_FILTER_PPP_CONTROL_PROTOCOL INC_FILTER_PPP_INTERFACE EXC_FILTER_PPP_INTERFACE INC_FILTER_NETWORK_EGRESS EXC_FILTER_NETWORK_EGRESS INC_FILTER_NETWORK_INGRESS MPLS Interface object OAM Test object PPP Control Protocol object PPP Interface object Network Queue object Network Queue object EXC_FILTER_NETWORK_INGRESS INC_FILTER_SERVICE_EGRESS EXC_FILTER_SERVICE_EGRESS Egress Serice Queue object Ingress Serice Queue object (Alcatel-Lucent 7705 Serice Aggregation Router and Alcatel-Lucent 7210 Serice Access Switch) INC_FILTER_SERVICE_INGRESS EXC_FILTER_SERVICE_INGRESS INC_FILTER_ROUTE_STATS EXC_FILTER_ROUTE_STATS INC_FILTER_SERVICE_SITE_PING Egress Serice Queue object Ingress Serice Queue object (Alcatel-Lucent 7705 Serice Aggregation Router and Alcatel-Lucent 7210 Serice Access Switch) Virtual Router OAM Test object EXC_FILTER_SERVICE_SITE_PING 60 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

69 Table 4. Metrics filter parameters and associated subelement types (continued) Include and exclude filter parameters Subelement SDP Binding object INC_FILTER_SVT_SDP_BINDING_BASE EXC_FILTER_SVT_SDP_BINDING_BASE INC_FILTER_TUNNEL_PING EXC_FILTER_TUNNEL_PING INC_FILTER_VCCV_PING EXC_FILTER_VCCV_PING INC_FILTER_IPIPE_L2_ACCESS_INTERFACE EXC_FILTER_IPIPE_L2_ACCESS_INTERFACE INC_FILTER_CFM_LOOPBACK EXC_FILTER_CFM_LOOPBACK INC_FILTER_CFM_ONEWAY_DELAY OAM Test object OAM Test object Access Interface object OAM Test object Ethernet CFM Object EXC_FILTER_CFM_ONEWAY_DELAY INC_FILTER_CFM_TWOWAY_DELAY EXC_FILTER_CFM_TWOWAY_DELAY INC_FILTER_CFM_ETHERNET EXC_FILTER_CFM_ETHERNET INC_FILTER_CFM_SINGLE_ENDED_LOSS EXC_FILTER_CFM_SINGLE_ENDED_LOSS INC_FILTER_AOSQOS_POLICY EXC_FILTER_AOSQOS_POLICY INC_FILTER_EQUIPMENT_CARD_SLOT EXC_FILTER_EQUIPMENT_CARD_SLOT INC_FILTER_MPLS_SITE AOSQOS Object CardSlot Object MplsSite Object EXC_FILTER_MPLS_SITE Chapter 4. Additional configuration steps for certain UBA Technology Packs 61

70 Table 4. Metrics filter parameters and associated subelement types (continued) Include and exclude filter parameters Subelement Multi Serice Site object INC_FILTER_SVQ_AGGREGATION_SCHEDULER EXC_FILTER_SVQ_AGGREGATION_SCHEDULER INC_FILTER_MSS_INGRESS EXC_FILTER_MSS_INGRESS INC_FILTER_MSS_EGRESS EXC_FILTER_MSS_EGRESS INC_FILTER_VPRN_SERVICE_ACCESS_POINT Serice Access Point Object EXC_FILTER_VPRN_SERVICE_ACCESS_POINT INC_FILTER_IES_SERVICE_ACCESS_POINT EXC_FILTER_IES_SERVICE_ACCESS_POINT INC_FILTER_SVC_PPPOE EXC_FILTER_SVC_PPPOE Valid alues for include and exclude filter parameters: The include and exclude filter parameters for inentory and metrics enable you to specify the inentory and metrics objects to include or exclude during a specified collection. Table 5 table summarizes the alid alues for these filter parameters. The subsequent sections proide examples. It is impractical and beyond the scope of this guide to proide exhaustie descriptions and explanations of the Alcatel-Lucent 5620 SAM technology. Table 5. Valid alues for include and exclude filter parameters Value No alue Meaning For INC_ parameters: Includes all of the aailable inentory and metrics for this Alcatel-Lucent 5620 SAM-O class. * (asterisk character for exclude inentory parameters) For EXC_ parameters: Excludes none of the aailable inentory and metrics for this Alcatel-Lucent 5620 SAM-O class. For INC_ parameters: Includes all of the aailable inentory and metrics for this Alcatel-Lucent 5620 SAM-O class. For EXC_ parameters: Excludes all (that is, does not collect any) inentory for this Alcatel-Lucent 5620 SAM-O class. 62 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

71 Table 5. Valid alues for include and exclude filter parameters (continued) Value Single property and associated alue Property using the UNIX? (question mark) file name specification Meaning Includes or excludes the inentory and metrics for these Alcatel-Lucent 5620 SAM-O classes generated for the specified property. Includes or excludes the inentory and metrics for these Alcatel-Lucent 5620 SAM-O classes generated for the specified property range. In this case, the range was specified using the UNIX? file name specification. Property using the UNIX * (asterisk) file name specification Single IP address IP address using the UNIX? (question mark) file name specification IP address using the UNIX * (asterisk) file name specification range(n..m) The UNIX? specification matches any single character. Includes or excludes the inentory and metrics for these Alcatel-Lucent 5620 SAM-O classes generated for the specified property range. In this case, the range was specified using the UNIX * file name specification. The UNIX * specification matches any number of characters. Includes or excludes the inentory and metrics for these Alcatel-Lucent 5620 SAM-O classes generated for the specified IP address. Includes or excludes the inentory and metrics for these Alcatel-Lucent 5620 SAM-O classes generated for the specified IP address range. In this case, the range was specified using the UNIX? file name specification. The UNIX? specification matches any single character. Includes or excludes the inentory and metrics for these Alcatel-Lucent 5620 SAM-O classes generated for the specified IP address range. In this case, the range was specified using the UNIX * file name specification. The UNIX * specification matches any number of characters. Supports metric filtering on integers using numeric ranges. The range supports the logic of 'greater than or equal to AND less than or equal to'. There is a logical AND between the upper and lower bounds of the range. The range() functionality can only be used on properties that are purely integer alues. Chapter 4. Additional configuration steps for certain UBA Technology Packs 63

72 Rules for specifying filter alues: The following list defines the rules for specifying parameter alues: Use a space to separate multiple alues for a property. Use a semicolon to separate multiple property specifications in one filter parameter. Note that the exclude specifications oerride the include specifications. Specify the same alue for a metrics filter parameter and its associated inentory filter parameters, for a gien subelement. See Supported filter parameters on page 48 for the include and exclude filter parameter mappings for metrics and inentory. Syntax Use the following syntax to specify parameter alues: FilterParameter=Prop1:al1 al2; Prop2: al3 al4 al5; Prop3: al6 al7 where Prop1 matches al1 OR al2 AND Prop2 matches al3 OR al4 OR al5 AND Prop3 matches al6 OR al7 For the INC_ filter parameters, "matches" means that the filter includes the items that match the specified alues. For the EXC_ filter parameters, "matches" means that the filter excludes the items that match the specified alues. Specifying the properties Specify the names of the properties as defined on the SAM serer, not the Tioli Netcool Performance Manager names. For example, you can filter on the property sitename, but not on the property samsitename. The Alcatel-Lucent 5620 SAM XML Reference - Release 7.0 documentation contains details about all of the packages and their associated objects and properties. Specifying the alues Some alues can come from the SAM serer in two different ways: As a text string, which usually occurs during the full dump As a numerical alue, which comes from the JMS object creation messages You must include both of these alues in the filter specification, as shown in the following example: EXC_FILTER=operationalState:portInSerice 2 In this example, the text ersion of the operationalstate property is portinserice, but the numerical alue passed through JMS is 2. Specifying properties in a filter In older ersions of the Alcatel-Lucent 5620 SAM Technology Pack, the only type of alues that you could specify for the filter parameters were IP addresses. 64 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

73 Starting with Alcatel-Lucent 5620 SAM Technology Pack Version , the filtering mechanism is een more granular. You can now filter on other properties, not just IP addresses, and you can proide seeral alues for each property. Specifying an IP address in a filter In older ersions of the Alcatel-Lucent 5620 SAM Technology Pack, you did not explicitly specify a property with the IP address, because the filtering mechanism automatically handled the property specification. Starting with Alcatel-Lucent 5620 SAM Technology Pack Version , you can specify seeral other kinds of properties in addition to IP addresses. Therefore, you must also specify the corresponding property name. Howeer, property names are not consistent across the different objects. For some inentory objects, the IP address is stored in the siteid property. For other objects, the IP address is stored in the nodeid property. You must ensure that you hae the correct property for each object. To identify the name of the Alcatel-Lucent 5620 SAM property that contains the IP address for an object (that is, the default alue used to filter the inentory and metrics for that object), see Table 3 on page 49 table. Note: IP address filtering is a special case. IP address filtering automatically maps the property specifications, so that you do not hae to specify the different IP-address-containing property for each object type. The old filtering syntax still works. If you hae filters that use the old syntax, and you do not want to change the filter (for example, by filtering on additional properties), you can still use the existing filters. You can also just use the old filtering syntax in one clause of a filter, and hae other clauses that use the new syntax for other properties. Matching patterns in filter syntax: strings and numbers In earlier releases, you could use only IP addresses to filter the inentory and metrics. IP addresses are defined on the SAM serer as strings. Starting with Tioli Netcool Performance Manager Version , you can use many other properties to specify what inentory and metrics to collect. Some of these filtering properties are defined on the Alcatel-Lucent 5620 SAM serer as strings, and some are defined as numbers. Pattern matching in filter syntax is currently performed by a pure string match only. The UNIX? and * characters can only be applied to string-type properties (including IP addresses). They cannot be applied to ranges of numbers. With the addition of the range () filter it is now possible to specify a range of numbers in a filter. See Examples that use the range() specification on page 68. The following example shows a filter specification that contains a number but is treated as a string -- in this example, the text ersion of the operationalstate property is portinserice, but the numerical alue passed through JMS is 2. SAMIF ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_PHYSICAL_PORT =operationalstate: portinserice 2 Chapter 4. Additional configuration steps for certain UBA Technology Packs 65

74 The following example shows an inalid specification, because the scid property is defined on the Alcatel-Lucent 5620 SAM serer as a number, and the UNIX? and * specifications cannot be applied to numbers: SAMIF ALCATEL_5620_SAM.APP.INC_FILTER_VPLS_L2_ACCESS_INTERFACE=scId: 1100* For alid examples of filter specifications that use the UNIX? and * characters, see Examples that use the UNIX "?" file name specification on page 67 and Examples that use the UNIX "*" file name specification on page 67. Maximum filter parameter length Tioli Netcool Performance Manager does not impose a limit on how many characters can be included in a filter parameter specification. Although there is no defined limit for filter parameter length, excessiely long filter settings can affect performance. Example filter parameter specifications: This section proides seeral different examples to show how to use the filter parameters. The following examples show how to use the old-style simple IP filtering: Example that shows how to include all alues Example that shows how to exclude all alues Examples that use a single IP address on page 67 Examples that use the UNIX "?" file name specification on page 67 Examples that use the UNIX "*" file name specification on page 67 Examples that use the range() specification on page 68 The following examples show the new, more complex, property filtering: Examples that use multiple properties and alues on page 68 Example that includes and excludes specific inentory and metrics on page 69 Example that shows how to include all alues: The following example shows how to include all aailable inentory and metrics associated with the Physical Port object. V4.4.3 and later Use the Topology Editor to ensure that no alue is set for these SAMIF parameters: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_PHYSICAL_PORT= ALCATEL_5620_SAM.APP.EXC_FILTER_EQUIPMENT_PHYSICAL_PORT= Use the Topology Editor to ensure that no alue is set for these BLB parameters: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE= ALCATEL_5620_SAM.APP.EXC_FILTER_EQUIPMENT_INTERFACE= ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE_ADD= ALCATEL_5620_SAM.APP.EXC_FILTER_EQUIPMENT_INTERFACE_ADD= ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT= ALCATEL_5620_SAM.APP.EXC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT= Example that shows how to exclude all alues: The following example shows how to exclude all (that is, do not collect any) aailable inentory associated with the Physical Port object. V4.4.3 and later Use the Topology Editor to set this SAMIF parameter to * (that is, asterisk): 66 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

75 ALCATEL_5620_SAM.APP.EXC_FILTER_EQUIPMENT_PHYSICAL_PORT=siteId:* Note: Take care before turning off the metrics for a particular subelement type, in case those metrics are also associated with other subelement types. In such cases, you might prefer to edit the filter to exclude the particular subelement, rather than turn off the metrics for all subelements. See Table for more information about the subelement types associated with each metric. Examples that use a single IP address: The following examples show how to include, at a specified IP address, all aailable inentory and metrics associated with the Physical Port object. V4.4.3 and later Use the Topology Editor to supply an IP address to these SAMIF parameters: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_PHYSICAL_PORT= Use the Topology Editor to supply an IP address to these BLB parameters: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE= ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE_ADD= ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT= All aailable metrics generated at address are collected for the equipment.interfacestatslogrecord, equipment.interfaceadditionalstatslogrecord, and equipment.mediaindependentstatslogrecord classes defined in the equipment package. Examples that use the UNIX "?" file name specification: The following examples show how to include, at a specified range of IP addresses, all aailable inentory and metrics associated with the Physical Port object. The range specification makes use of the UNIX? (question mark) file name specification. V4.4.3 and later Use the Topology Editor to supply an IP address range to this SAMIF parameter: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_PHYSICAL_PORT= ? Use the Topology Editor to supply an IP address range to these BLB parameters: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE= ? ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE_ADD= ? ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT= ? All aailable metrics generated at addresses through inclusie are collected for the equipment.interfacestatslogrecord, equipment.interfaceadditionalstatslogrecord, and equipment.mediaindependentstatslogrecord classes defined in the equipment package. You could also hae specified the range as ??. This range specification matches through inclusie. Examples that use the UNIX "*" file name specification: The following examples show how to include, at a specified range of IP addresses, all aailable inentory and metrics associated with the Physical Port object. The range specification makes use of the UNIX * (asterisk) file name specification. Tioli Netcool Performance Manager and later Use the Topology Editor to supply an IP address range to this SAMIF parameter: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_PHYSICAL_PORT= * Use the Topology Editor to supply an IP address range to these BLB parameters: Chapter 4. Additional configuration steps for certain UBA Technology Packs 67

76 ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE= * ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE_ADD= * ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_MEDIA_INDEPENDENT= * All aailable inentory generated at addresses from , through inclusie, and through inclusie are collected for the equipment.physicalport class defined in the equipment package. All aailable metrics generated at addresses , through inclusie, and through inclusie are collected for the equipment.interfacestatslogrecord, equipment.interfaceadditionalstatslogrecord, and equipment.mediaindependentstatslogrecord classes defined in the equipment package. Another example, *.*, would match any inentory and metrics for these classes in the X.X subnet. You could also hae specified the range as ??. This range specification matches through inclusie. Examples that use the range() specification: The following examples show how to include metric filtering on integers using numeric ranges. Syntax: range(n..m) The range supports the logic of 'greater than or equal to AND less than or equal to'. Note: There is a logical AND between the upper and lower bounds of the range. The range() functionality can only be used on properties that are purely integer alues. The * and? can only be used on strings. The * and? can be used on IP addresses that are strings, but you cannot use the range() on IP addresses. Example - scid: range( ) In the aboe example, numbers greater than or equal to 1010 AND less than or equal to 1050 match the filter. Also, multiple ranges used together are supported. Example - scid: range(1..10) range( ) In the aboe example, numbers greater than or equal to 1 AND less than or equal to 10 OR numbers greater than or equal to 100 AND less than or equal to 200 match the filter. Note: There is a logical OR between ranges when there is more than one range. Examples that use multiple properties and alues: SAMIF ALCATEL_5620_SAM.INC_FILTER_PHYSICAL_PORT= SAMIF ALCATEL_5620_SAM.INC_FILTER_PHYSICAL_PORT=cardSlotId:10 11; lagmembershipid: 0 SAMIF ALCATEL_5620_SAM.INC_FILTER_PHYSICAL_PORT= * * SAMIF ALCATEL_5620_SAM.EXC_FILTER_PHYSICAL_PORT=siteId: SAMIF ALCATEL_5620_SAM.INC_FILTER_PHYSICAL_PORT= *; cardslotid:10 11; lagmembershipid: 0 Note: The last example shows how to combine the old filter style with the new filter style. 68 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

77 Example that includes and excludes specific inentory and metrics: The following example shows how to include, at a specified IP address, all aailable inentory and metrics associated with the equipment.physicalport class defined in the equipment package and to exclude all aailable inentory from the lag.interface class defined in the lag package. V4.4.3 and later Use the Topology Editor to supply an IP address to this SAMIF parameter: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_PHYSICAL_PORT=siteId: Use the Topology Editor to supply an asterisk (collect no inentory) to this SAMIF parameter: ALCATEL_5620_SAM.APP.EXC_FILTER_LAG_INTERFACE=* Use the Topology Editor to supply an IP address to this BLB parameter: ALCATEL_5620_SAM.APP.INC_FILTER_EQUIPMENT_INTERFACE=siteId: Issues when configuring multiple Alcatel-Lucent 5620 SAM Technology Pack instances: Specifying alues for the include and exclude filter parameters when there is only one instance of the Alcatel-Lucent 5620 SAM Technology Pack is relatiely straightforward. All of the Tioli Netcool Performance Manager resources (elements and subelements) are located on the same instance. Howeer, when your enironment requires two or more instances, then you need to understand the Tioli Netcool Performance Manager elements and the instances on which they are located. This is necessary because you want to specify the correct alue for the include and exclude filter parameters. Table 6 on page 70 table has the following columns: First column -- Specifies the instance of the Alcatel-Lucent 5620 SAM Technology Pack. In this example there are two: instance 1 and instance 2. Second column -- Specifies the element type. Third column -- Specifies the family names of the subelements associated with this element. Table 6 on page 70 table shows that the subelements for the MPLS Serice object, Router object, and Network Queue object are located on one instance, and the subelements for the remaining objects are located on another instance. Do not split the subelements that are associated with the same element across two collectors. This will cause SQL errors. Your inentory or metrics or both will not be collected properly, and you will lose data. Also, the Network Queue object should not be split from the physical ports, they should reside in the same instance. Chapter 4. Additional configuration steps for certain UBA Technology Packs 69

78 Table 6. Tioli Netcool Performance Manager elements on multiple Alcatel-Lucent 5620 SAM Technology Pack instances Instance Element type Subelement family SAMIF BLB UBA UBA SAMIF BLB UBA UBA MPLS Serice object Router object Network Queue object Serice object Serice Tunnel object 5620_SAM_MPLSInterface 5620_SAM_Channel 5620_SAM_Hw_Enironment 5620_SAM_LAGInterface 5620_SAM_OAM_Test 5620_SAM_PhysicalPort 5620_SAM_PPP_Interface 5620_SAM_PPP_Protocol 5620_SAM_Shelf 5620_SAM_Virtual_Router 5620_SAM_NQueue 5620_SAM_SericeAccessInterface 5620_SAM_AingrAengrQueue 5620_SAM_SdpBinding Changing the collection period for SAM statistics This section proides general guidelines on how to change the collection period for SAM statistics, and describes how to change the collection periods for arious types of SAM statistics: General guidelines on changing the collection period for SAM statistics Changing the collection period for SAM accounting statistics on page 71 Changing the collection period for SAM polling statistics on page 71 Changing the collection period for SAM OAM test statistics on page 72 Changing the collection period for SAM aailability statistics on page 72 Example to show how to change the collection period for SAM statistics on page 72 General guidelines on changing the collection period for SAM statistics: The default collection period for all SAM statistics is 15 minutes. If you change any collection period, ensure that you follow these guidelines: 1. You must set the APP.FILE_PERIOD parameter (on each UBA component) and the SAM.EXPORT_SCHEDULE parameter (on the BLB component) to equialent alues. For example, if you set the APP.FILE_PERIOD parameter to 600 (that is, 600 seconds, or 10 minutes), then you must set the SAM.EXPORT_SCHEDULE parameter to 0,10,20,30 ****. Note: The APP.FILE_PERIOD parameter is specified in seconds, and the SAM.EXPORT_SCHEDULE parameter is specified as a series of alues expressed in minutes. 70 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

79 2. Both the APP.FILE_PERIOD and SAM.EXPORT_SCHEDULE parameters must be set to the minimum alue of the following collection periods: collection period for SAM accounting statistics (see Changing the collection period for SAM accounting statistics ) collection period for SAM polling statistics (see Changing the collection period for SAM polling statistics ) collection period for SAM OAM Test statistics (see Changing the collection period for SAM OAM test statistics on page 72) collection period for SAM aailability statistics (see Changing the collection period for SAM aailability statistics on page 72) See also the Example to show how to change the collection period for SAM statistics on page The collection period for any type of SAM statistics must be set to the same alue as the collection period for the corresponding Tioli Netcool Performance Manager requests. The Alcatel-Lucent 5620 SAM Technology Pack supplies these parameters based on the following Tioli Netcool Performance Manager platforms: Tioli Netcool Performance Manager and later - These parameters are supplied in the pack XSD file. You specified alues for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. See the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager Installation Guide for more information. Changing the collection period for SAM accounting statistics: To change the collection period for the SAM accounting statistics, do the following actions: 1. Change the accounting period on the SAM serer, as described in the SAM Serer documentation. 2. Change the Tioli Netcool Performance Manager request period for the subelements in the following folders in the Sub-Element Collect tree:sub-element Collect > Alcatel-Lucent 5620 SAM > Serices > AingrAengrQueue Sub-Element Collect > Alcatel-Lucent 5620 SAM > Router > NetworkQueues 3. Change the file period on the SAM serer, as described in the SAM Serer documentation. This alue must be the same as, or greater than, the accounting period that you specified in Step Change the alue of the APP.FILE_POLICY_PERIOD parameter (on the BLB component). 5. Reiew the alue of the APP.FILE_PERIOD and SAM.EXPORT_SCHEDULE parameters, as described in General guidelines on changing the collection period for SAM statistics on page 70. See also the Example to show how to change the collection period for SAM statistics on page 72. Changing the collection period for SAM polling statistics: To change the collection period for the SAM polling statistics, do the following actions: 1. Change the collection period for the MIBs listed in Enable the MIBs for the SAM statistics classes on page Change the Tioli Netcool Performance Manager request period for the subelements in the following folders in the Sub-Element Collect Chapter 4. Additional configuration steps for certain UBA Technology Packs 71

80 tree:sub-element Collect > Alcatel-Lucent 5620 SAM > Router Sub-Element Collect > Alcatel-Lucent 5620 SAM > Serices > SdpBinding 3. Reiew the alue of the APP.FILE_PERIOD and SAM.EXPORT_SCHEDULE parameters, as described in General guidelines on changing the collection period for SAM statistics on page 70. See also the Example to show how to change the collection period for SAM statistics. Changing the collection period for SAM OAM test statistics: To change the collection period for the SAM OAM Test statistics, do the following actions: 1. Perform the steps described in Set up ping tests on page Change the Tioli Netcool Performance Manager request period for the subelements in the following folder in the Sub-Element Collect tree:sub-element Collect > Alcatel-Lucent 5620 SAM > Router > OAM Tests 3. Reiew the alue of the APP.FILE_PERIOD and SAM.EXPORT_SCHEDULE parameters, as described in General guidelines on changing the collection period for SAM statistics on page 70 See also the Example to show how to change the collection period for SAM statistics. Changing the collection period for SAM aailability statistics: To change the collection period for the SAM aailability statistics, do the following actions: 1. Change the alue of the JMS_FILE_OUTPUT.ACCESS_INTERFACE.PERIOD and JMS_FILE_OUTPUT.PHYSICAL_PORT.PERIOD parameters (on the SAMIF component). 2. Change the Tioli Netcool Performance Manager request period for the subelements in the following folders in the Sub-Element Collect tree:sub-element Collect > Alcatel-Lucent 5620 SAM > Router > Interface Sub-Element Collect > Alcatel-Lucent 5620 SAM > Serices > SericeAccessInterface 3. Reiew the alue of the APP.FILE_PERIOD and SAM.EXPORT_SCHEDULE parameters, as described in General guidelines on changing the collection period for SAM statistics on page 70. See also the Example to show how to change the collection period for SAM statistics. Example to show how to change the collection period for SAM statistics: The table below shows how to set seeral parameters to change the collection period for arious SAM statistics from the default alue of 15 minutes to a new alue of 10 minutes, based on the guidelines proided in General guidelines on changing the collection period for SAM statistics on page 70, where UBA1 is the polling UBA, and UBA2 is the accounting UBA. Table 7. Example Parameter Values to Change the Collection Period for SAM Statistics Parameter Component Default Value New Value APP.FILE_PERIOD UBA1, UBA APP.FILE_POLICY_PERIOD BLB JMS_FILE_OUTPUT. ACCESS_INTERFACE.PERIOD SAMIF JMS_FILE_OUTPUT. PHYSICAL_PORT.PERIOD SAMIF IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

81 Table 7. Example Parameter Values to Change the Collection Period for SAM Statistics (continued) Parameter Component Default Value New Value SAM.EXPORT_SCHEDULE BLB 0,15,30,45 **** 0,10,20,30 **** The Alcatel-Lucent 5620 SAM Technology Pack supplies these parameters in one of the following ways: Tioli Netcool Proiso and Tioli Netcool Performance Manager or later - These parameters are supplied in the pack XSD file. You specified alues for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information about adding a UBA Bulk Collector, see the section in the IBM Tioli Netcool Performance Manager: Installation Guide. Changing the collection strategy for aailability metrics The UBAs calculate the aailability of physical ports (calculated by UBA1) and serices (calculated by UBA2) by using operational status information receied through JMS. The JMS data is receied by the SAMIF. The SAMIF puts intermediate files in the DATA_CHANNEL_HOME /jms_xml directory to be picked up by the UBAs. DATA_CHANNEL_HOME is the DataChannel home directory ( /opt/datachannel, by default). Seeral of the steps in this section tell you to make sure that the correct alues are specified for parameters in the deployed topology (V4.4.3 and later). You specify the alues for these parameters in one of the following ways: Tioli Netcool Proiso and Tioli Netcool Performance Manager or later - These parameters are supplied in the pack XSD file. You used the Topology Editor to specify a alue for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information about adding a UBA Bulk Collector, see the section in the IBM Tioli Netcool Performance Manager: Installation Guide. Stopping the collection of aailability metrics: To stop collecting aailability metrics for Access Interface objects and Physical Port objects, do the following steps: 1. Stop each UBA: $ dccmd stop UBA.<channel_number>. <collector_number1> $ dccmd stop UBA.<channel_number>. <collector_number2> 2. Set the AVAIL_NAME_SPACE parameter for each collector to a null alue:. UBA. <channel_number>.<collector_number1>.alcatel_5620_sam.avail_name_space= UBA. <channel_number>.<collector_number2>.alcatel_5620_sam.avail_name_space= 3. Set the JMS_FILE_OUTPUT.<object_type>.ACTIVE parameters to the alue FALSE. The following example shows to set these parameters for Tioli Netcool Performance Manager in the Topology Editor help XSD file: SAMIF.<channel_number>.<collector_number1>.ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT. PHYSICAL_PORT.ACTIVE=FALSE SAMIF.<channel_number>.<collector_number1>.ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT. ACCESS_INTERFACE.ACTIVE=FALSE 4. Remoe the following folders: Chapter 4. Additional configuration steps for certain UBA Technology Packs 73

82 DATA_CHANNEL_HOME /UBA. <channel_number>.<collector_number1> /ALCATEL_5620_SAM/state DATA_CHANNEL_HOME /UBA. <channel_number>.<collector_number2> /ALCATEL_5620_SAM/state where DATA_CHANNEL_HOME is the DataChannel home directory ( /opt/datachannel, by default). 5. Stop and restart the SAMIF. $ dccmd stop SAMIF.<channel_number>.<collector_number1> $ dccmd start SAMIF.<channel_number>.<collector_number1> 6. Restart each UBA: $ dccmd start UBA.<channel_number>.<collector_number1> $ dccmd start UBA.<channel_number>.<collector_number2> 7. Wait to ensure that the UBAs stop producing the aailability data, but continue to produce other data. For example: Wait to see whether the UBAs continue to produce output BOF files in the following directories: DATA_CHANNEL_HOME/UBA.<channel_number>.<collector_number1>/output DATA_CHANNEL_HOME/UBA.<channel_number>.<collector_number2>/output Check to see whether any files exist in the following directories: DATA_CHANNEL_HOME DATA_CHANNEL_HOME /jms_xml/port/* (for Physical Port objects) /jms_xml/access/* (for Access Interface objects) These directories contain the input files that the UBAs use to produce the aailability data. If the UBAs do not moe the input files from these directories, the UBAs are probably not producing the aailability data. Starting the collection of aailability metrics: To start collecting aailability metrics for Access Interface objects and Physical Port objects, do the following steps: 1. Stop the BLB: $ dccmd stop BLB.<channel_number>. <collector_number1> 2. Stop each UBA $ dccmd stop UBA.<channel_number>. <collector_number1> $ dccmd stop UBA.<channel_number>. <collector_number2> 3. Set the AVAIL_NAME_SPACE parameter for each collector to the appropriate alue. The following example shows to set these parameters for Tioli Netcool Performance Manager in the Topology Editor XSD file: UBA. <channel_number>.<collector_number1>.alcatel_5620_sam.avail_name_space=physical_port UBA. <channel_number>.<collector_number1>.alcatel_5620_sam.avail_name_space=access_interface 4. Remoe the following folders: DATA_CHANNEL_HOME /UBA. <channel_number>.<collector_number1> /ALCATEL_5620_SAM/state DATA_CHANNEL_HOME /UBA. <channel_number>.<collector_number2> /ALCATEL_5620_SAM/state where DATA_CHANNEL_HOME is the DataChannel home directory ( /opt/datachannel, by default). 5. Set the JMS_FILE_OUTPUT.<object_type>.ACTIVE parameters to the alue TRUE. The following example shows to set these parameters for Tioli Netcool Performance Manager pre in the dc.cfg file: SAMIF. <channel_number>.<collector_number1>. ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT.PHYSICAL_PORT.ACTIVE=TRUE SAMIF. <channel_number>.<collector_number1>. ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT.ACCESS_INTERFACE.ACTIVE=TRUE 6. Stop and restart the SAMIF: $ dccmd stop SAMIF.<channel_number>. <collector_number1> $ dccmd start SAMIF.<channel_number>. <collector_number1> 7. Start each UBA: $ dccmd start UBA.<channel_number>. <collector_number1> $ dccmd start UBA.<channel_number>. <collector_number2> 74 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

83 8. Start the BLB: $ dccmd start BLB.<channel_number>. <collector_number1> Troubleshooting Alcatel-Lucent 5620 SAM Technology Pack configuration Troubleshooting tips for issues related to the SAM Inentory File (SAMIF), Bulk Load Balancer (BLB), and Uniersal Bulk Adaptors (UBAs). Specifying parameter alues Seeral of the tips to tell you to make sure that the correct alues were specified for parameters in the deployed topology (Tioli/Netcool Proiso and later). You specify the alues for these parameters in one of the following ways, depending on the Tioli Netcool Performance Manager platform: Tioli Netcool Proiso and Tioli Netcool Performance Manager or later These parameters are supplied in the pack XSD file. You used the Topology Editor to specify a alue for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent 5620 SAM Technology Pack. For more information, see the section on adding a UBA Bulk Collector in the IBM Tioli Netcool Performance Manager Installation Guide. Inentory issues If you do not see the expected inentory in your Tioli Netcool Performance Manager instance, use the information in this section. Complete the steps in each subsection, to erify that you hae configured your instance correctly. Oeriew of inentory: The Alcatel-Lucent 5620 SAM Technology Pack creates inentory through two mechanisms. Full dump mechanism Requests bulk files of inentory data from the SAM serer. JMS mechanism Proides incremental inentory updates through an eent-notification system. Note: The full dump will not run unless the JMS is working correctly. The inentory files from a full dump are located in a directory on the SAM serer. The default location is the /opt/5620sam/serer/xml_output directory. The SAM serer administrator sets this location during SAM serer configuration. The Alcatel-Lucent 5620 SAM Technology Pack uses the following syntax for inentory file names: proiso-inentorytype-daterequested-timerequested-* When you are diagnosing an inentory problem, you can use the inentorytype information from the inentory file name to identify which type of object has the inentory problem. Here are some example inentory file names: Chapter 4. Additional configuration steps for certain UBA Technology Packs 75

84 proiso-physicalport proiso-mplsinterface proiso-iesl3accessinterface JMS is not working: If JMS is not working, complete the following troubleshooting steps: 1. Ensure that the DATA_CHANNEL_HOME/scripts/alcatel_5620_sam directory contains the SamJms.jar and samoss.jar files. 2. Ensure that you are using the samoss.jar file that comes with the SAM serer ersion that you are running. Do not use an older ersion of the samoss.jar file. 3. Make sure that the correct alue was specified for the SAM.JAR_PATH parameter, as described in Specifying parameter alues on page 75 based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.JAR_PATH The SAM.JAR_PATH parameter specifies the location of the SamJms.jar and samoss.jar files. 4. Make sure that the correct alue was specified for the SAM.JAVA_PATH parameter, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.JAVA_PATH The SAM.JAVA_PATH parameter identifies the full path of the JRE 1.6 executable. The default alue is /usr/bin/jaa. If Jaa is installed in any other location, you must set the SAM.JAVA_PATH parameter. 5. Verify that Jaa is aailable and can be run, by running the following command: $ jaa -ersion If Jaa is installed in a nondefault location, specify the full path for the JAVA executable. For example, if Jaa is installed in the /export/home/puser/jaa1.6 directory: a. Set the SAM.JAVA_PATH parameter to/export/home/puser/jaa1.6/jaa. b. Run the following command: $ /export/home/puser/jaa1.6/jaa -ersion 6. Ensure that you are using JRE Version 1.6 or later. To identify the JRE ersion, use the jaa -ersion command as described in Step Make sure that the correct alue was specified for the JMS port number, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.JMS_PORT The alue of the JMS port number depends on the number of SAM serers in your configuration, as described in Specifying parameter alues on page To test whether the JMS port is actie, run the following command: $ telnet <sam_serer> <JMS_port> 76 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

85 JMS Filter is not updated in the Topology Editor: When you try to upgrade the 4.3Y/1.3A/1.3B Alcatel-Lucent SAM Technology Pack that is running on Tioli Netcool/Proiso to 1.3D ( ), the JMS filter is not updated in the Topology Editor. To work around this issue, follow these steps: 1. Extract the XSD file from Alcatel-Lucent SAM Technology Pack. 2. Launch Topology Editor. 3. Right-click Application Packs in the Application Packs pane, and then click Load Application Pack. 4. Select XSD file, and then click Browse to naigate to the path where the current XSD file is stored. 5. Click OK to oerwrite the existing file. 6. In the Logical View pane, naigate to SAMIF under the UBA primary collector to see the Adanced Properties tab. 7. Select the ALCATEL_5620_SAM.SAM_JMS_FILTER property under Adanced Properties. to find the current updates to this property. The alue must be as follows: ALA_clientId in ( proiso-klpro01z5-1-2, ) and MTOSI_objectType in ( KeepAlieEent, StateChangeEent, TerminateClientSession, equipment.physicalport, equipment.shelf, equipment.hwenironment, mpls.interface, lag.interface, ll.l2accessinterface, prn.l3accessinterface, ies.l3accessinterface, pls.l2accessinterface, mirror.l2accessinterface, aengr.forwardingclass, aingr.forwardingclass, aengr.queue, aingr.queue, st.meshsdpbinding, st.mirrorsdpbinding, st.spokesdpbinding, aingr.policy, aengr.policy, icmp.icmpping, mpls.lspping, st.tunnelping, st.vccping, serice.siteping, sonetequipment.sts1channel, sonetequipment.sts3channel, sonetequipment.sts12channel, sonetequipment.sts48channel, sonetequipment.sts192channel, tdmequipment.ds1e1channel, tdmequipment.ds3e3channel, sonetequipment.tributarychannel, sonetequipment.tu3channel, sonetequipment.tributarygroup, sonetequipment.tug3group, tdmequipment.ds0channelgroup, ppp.interface, ppp.pppcontrolprotocol, nqueue.forwardingclass, nqueue.policy, nqueue.entry, sasqos.meter, sasqos.accessingress, sasqos.accessingressforwardingclass, sasqos.portaccessegress, sasqos.portaccessegressforwardingclass, sasqos.portaccessegressqueue, rtr.virtualrouter, ipipe.l2accessinterface, equipment.cardslot, ethernetoam.cfmloopback, ethernetoam.cfmonewaydelaytest, ethernetoam.cfmtwowaydelaytest, ethernetoam.cfmethtest, aosqos.policy, sq.aggregationscheduler, mpls.site, prn.sericeaccesspoint, ies.sericeaccesspoint, ethernetoam.cfmsingleendedlosstest, ethernetoam.mep ) and ALA_category not in ( STATISTICS, ACCOUNTING ) 8. If any of the filters are missing, you must add them manually by using the aboe information. Or, you can take the updated filters from the XSD file for Alcatel-Lucent SAM Technology Pack. SAM inentory fails and does not start the full dump: During the full dump the SAMIF application requests inentory data files from the SAM serer, and retriees them to process and create the inentory. If one of the files it requests is not able to be retrieed, then it will not start the full dump. If this failure condition persists, then this full dump failure situation will loop repeatedly. In this case, complete the following troubleshooting steps: 1. User configuration or file/directory permissions do not allow the full dump files to be seen or retrieed by the SAMIF. Check the permissions as specified Chapter 4. Additional configuration steps for certain UBA Technology Packs 77

86 in Setting up the Alcatel-Lucent 5620 SAM serers on page 33, and in particular in the section Configure FTP accounts on the primary and redundant SAM serers on page Check user-specified filters. If there is a problem with user-specified filters, this could result in files not being written to and the full dump could loop. If the user specifies a filter of the type property: alue and the filter specification is not alid for the SAM serer, it will fail to write a file, thus causing the full dump to fail. There is no log indication for this failure case, but it will cause a "file not found" during the full dump. There are two cases where this could happen: a. The property specified in the filter is not aailable in the inentory class being requested. For example, if there is a typo in the property name, or simply specified a property that is not applicable to that class. This will cause the file request to fail, and the full dump will loop. Note: Information about the properties that are alid for each class are outside of the scope of this user guide. b. The filter specification uses the wrong kind of matching syntax for the property specified. As described in the section Matching patterns in filter syntax: strings and numbers on page 154, the * and? are only applicable to string properties, and the range() match is only applicable to numerical properties. Using these matching constructs on the wrong type of property will result in failure to retriee a file, and the full dump will loop. Note: Information about the types of properties (whether they are numerical or string) is outside the scope of this guide. SAM inentory does not exist in the SAM serer: If inentory does not exist in the SAM serer, make sure that discoery is turned on in the SAM serer. Use the Alcatel-Lucent 5620 SAM Client GUI to check whether discoery is turned on. SAM inentory does not exist in Tioli Netcool Performance Manager: If inentory does not exist in Tioli Netcool Performance Manager, complete the following troubleshooting steps: 1. Make sure that the Jaa Message Serice (JMS) is working. To erify that JMS is working, search for the "JMS_CONNECTION_ESTABLISHED" message. The following example shows the expected output when JMS is working UTC SAMIF I SAM_CONNECT Attempting connection to sam serer: UTC SAMIF EXSTATUSCHANGE SAM JMS communication process listening for eents since: UTC SAMIF [DL39218] JMS_PROCESS_STARTED The SAM JMS communication process has started (pid: 2849) UTC SAMIF I SAM_CONNECTED Connection established with UTC SAMIF I [DL39222] JMS_CONNECTION_ESTABLISHED The SAM JMS connection has been established (a keep-alie message was receied) If the "JMS_CONNECTION_ESTABLISHED" message is not displayed, the JMS is not working. Reiew the $DC_HOME/log/proiso.log file for errors. Complete the steps in JMS is not working on page 76, to erify that you hae configured your instance correctly. 78 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

87 2. Make sure the SAMIF full dump is working. To erify that the full dump is working, search for the Full Dump Complete message. The following example shows the expected output when the full dump is working UTC SAMIF I [SAMIF] onfulldump **** Full Dump Started **** UTC SAMIF I [SAMIF] onfulldump **** Full Dump Complete ****. If the "Full Dump Started" message is repeated, there is a problem with the inentory. Stop the SAMIF and reiew the $DC_HOME/log/proiso.log file for errors with the SAMIF. SAM inentory does not complete: If the customer inentory is particularly large, a full dump might take too long to complete. In this situation, the SAMIF times out, and a new full dump is requested because the original full dump is assumed to hae failed. To fix this problem, increase the alue specified for the SAM.SOAP_TIMEOUT parameter, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.SOAP_TIMEOUT The default alue for the SAM.SOAP_TIMEOUT parameter is 900 (900 seconds). Loading metadata takes a long time to complete on SAMIF component restart or reestablish connection to SAM serer: This issue occurs most often when you hae a large number of subelements with a lot of properties. It can happen with any component that reads metadata, for example the SAMIF or CME. You can optimize the Oracle queries for the specific data in your database by running the following command in the DataMart enironment: 'dbmgr analyzemetadatatables A Y' This command must be run any time a large number of objects has been inentoried or if the inentory is changed significantly, for example, if a new property is added to the subelements. Typically, this command must be cron'd to run at least once a day in actie networks. SAMIF files do not exist in the SAM serer directory: If the inentory files are not transferred to the default directory on the SAM serer, as described in the Oeriew of inentory on page 75, complete the following troubleshooting steps: 1. Make sure that an OSS user account is configured on the SAM serer. See Configure an OSS user account on page 34 for more information. 2. Make sure that the correct alues were specified for the SAM.USERNAME and SAM.PASSWORD parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Chapter 4. Additional configuration steps for certain UBA Technology Packs 79

88 Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.USERNAME ALCATEL_5620_SAM.SAM.PASSWORD 3. Make sure that the correct alue was specified for the SAM.SAM_VERSION parameter, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.SAM_VERSION The SAM.SAM_VERSION parameter refers to the JMS protocol ersion, not the SAM serer ersion. 4. Make sure that the correct alues were specified for the SAM.SOAP_URI and SAM.SOAP_URI_2 parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.SOAP_URI ALCATEL_5620_SAM.SAM.SOAP_URI_2 SAMIF files do not exist in the SAMIF temp directory: Typically, the DataChannel File Transfer Engine (FTE) application transfers inentory files to the DataChannel SAMIF application temp and done directories. If the inentory files are not transferred to the SAMIF application temp and output directories, complete the following troubleshooting steps: 1. Make sure that an FTP user account is configured on the primary and redundant SAM serers. See Configure FTP accounts on the primary and redundant SAM serers on page 36 for more information. 2. Make sure that the correct alues were specified for the SAM.EXPORT_URI and SAM.EXPORT_URI_2 parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.EXPORT_URI ALCATEL_5620_SAM.SAM.EXPORT_URI_2 3. Check the UNIX file permissions on the SAM serer. Ensure that the permissions on the xml_output directory are set to allow read, write, and execute by the SAM FTP user. 4. If files in the temp directory are 60 bytes in size, one of the following conditions exists: The SAM serer has no inentory of that type. The SAM serer is not configured to discoer inentory of that type. The inentory filter parameters might be set such that they do not match any inentory on the SAM serer. For more information about filter parameters, see Specifying what inentory and metrics to collect on page 47. You can use the inentorytype information from the inentory file name to identify which type of object has the inentory problem, as described in Oeriew 80 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

89 of inentory on page 75. If you think that you should hae inentory of that type, make sure that the discoery polling for that type is configured on the SAM serer. BLB does not put files in its output directory: Typically, the DataChannel File Transfer Engine (FTE) application transfers idmap files to the DataChannel SAMIF application output and done directories, and then to the DataChannel BLB application output and done directories. If the BLB is processing files, but does not put files in the output directory, the BLB might not hae receied notification of the inentory from SAMIF through the idmap files. If the idmap files do not exist in the BLB application output directory, complete the following troubleshooting steps: 1. Regenerate the idmap files, as follows: $ dccmd debug SAMIF "self serer firstadaptor modelinterface generatefullidmap" Replace with the channel and collector number for your installation. 2. Check the $DC_HOME/log/proiso.log file. If the proiso-*.xml files appear in the SAMIF temp directory and no SAMIF idmap files eer appear in the output directory, the SAMIF DataChannel application might be failing with an error. 3. Determine whether the inentory has been run once and is now being rerun. In this case, no new idmap files appear in the SAMIF output directory, because none of the inentory is new. This scenario is unlikely to occur. If the idmap files do not exist in the BLB application done directory, complete the following troubleshooting steps: 1. Make sure that the BLB application is configured correctly. 2. Make sure that the BLB application is running. 3. Make sure that the correct alue was specified for the IDMAP.URI parameter, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform Tioli Netcool/Proiso and Tioli Netcool Performance Manager or later Parameter ALCATEL_5620_SAM.IDMAP.URI UBA idmap files are no longer supported: Starting with Alcatel-Lucent 5620 SAM Technology Pack Version , idmap files are no longer used by the UBA. Metric data collection issues: If you do not see the expected metrics in your Tioli Netcool Performance Manager instance, use this information. Complete the steps in each subsection, to erify that you hae configured your instance correctly. The following sections proide an oeriew of metric data, and describe troubleshooting tips for issues related to the metric data collection: Oeriew of metric data: Chapter 4. Additional configuration steps for certain UBA Technology Packs 81

90 The SAM serer supports the following types of metric data: Polled Polled metric data is collected by the SAM serer from the routers using SNMP. To collect this data, MIBs must be enabled on the SAM serer, and polling periods must be set. For more information about the MIBs that are needed, see Enable the MIBs for the SAM statistics classes on page 35. Exception to the Rule: The exception is the HwEnironmentTemperature files. These files are in effect inentory files in which the temperature properties are read in as metrics. For a ariety of reasons related to this data not being real metrics, the temperature data is only aailable for a subelement under the following conditions: The CPU utilization metric for that subelement is aailable. The data being processed is current : the BLB and UBA hae caught up to the wall-clock time as much as is possible, and no backlog of data is being processed. Accounting Accounting metric data is collected by the routers into files. These files are retrieed by the SAM serer, and read into its database. To get this data, the accounting and file policies must be configured on the SAM serer and distributed to the routers. Accounting data is the data collected for serices. For more information about accounting data, see Configure the SAM accounting and polling statistics on page 34. Aailability data from the JMS The UBA calculates the aailability of physical ports and serices by using operational status information receied through JMS. The JMS data is receied by the SAMIF. Therefore, for the aailability calculations to work, the SAMIF must be running. The SAMIF puts intermediate files in the datachannel/jms_xml directory, to be picked up by the UBA. If the SAMIF is not running, and the UBA is expecting aailability data, all data output of the UBA will block until this data is receied. The Alcatel-Lucent 5620 SAM Technology Pack uses the following syntax for metric-data file names: filedescription_datecollected-timecollected.host_channel_collector.xml Here is an example file name for a metric-data file: InterfaceStats_ HOST22_2_100.xml SAM metrics do not display in the Alcatel-Lucent 5620 SAM Client GUI: The SAM serer administrator uses the Alcatel-Lucent 5620 SAM Client GUI to display metrics for the different objects (for example, serices and network elements) located in a SAM network enironment. If SAM metrics do not display in the Alcatel-Lucent 5620 SAM Client GUI, complete the following troubleshooting steps: 1. Enable the appropriate MIBs for the polled data. 2. Enable an accounting policy for the serice data. SAM metric files are empty or do not exist in the SAM serer: 82 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

91 Typically, SAM metric files are transferred to a directory, such as /opt/5620sam/nms/serer/xml_output, on the SAM serer. If the SAM metric files are empty (that is, the XML file has left and right angle brackets with no data, and is 60 bytes or less), complete the following troubleshooting steps: 1. Determine whether the absence of data is because there are no inentory elements and subelements from which to receie metrics. 2. Ensure that you enabled the appropriate MIBs for polled data. 3. Ensure that you enabled an accounting policy for serice data. 4. Ensure that you hae set your filter parameters correctly. For more information about filter parameters, see Specifying what inentory and metrics to collect on page 47. If SAM metric files do not exist in the SAM serer, complete the following troubleshooting steps: 1. Make sure that an OSS user account is configured. See Configure an OSS user account on page 34 for more information. 2. Make sure that the correct alues were specified for the SAM.USERNAME and SAM.PASSWORD parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform Tioli Netcool/Proiso and Tioli Netcool Performance Manager or later Parameter ALCATEL_5620_SAM.SAM.USERNAME ALCATEL_5620_SAM.SAM.PASSWORD 3. Make sure that the correct alue was specified for the SAM.SAM_VERSION parameter, as described in Specifying parameter alues on page 75 based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.SAM_VERSION The SAM.SAM_VERSION parameter refers to the JMS protocol ersion, not the SAM serer ersion. 4. Make sure that the correct alues were specified for the SAM.SOAP_URI and SAM.SOAP_URI_2 parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.SOAP_URI ALCATEL_5620_SAM.SAM.SOAP_URI_2 5. Check the UNIX file permissions. Ensure that the permissions on the xml_output directory are set to allow read, write, and execute by the SAM FTP user. 6. Ensure that you hae enough disk space. For more information, see Metrics collection fails due to lack of disk space on page 87. SAM metric files do not exist in BLB directories: Typically, the DataChannel File Transfer Engine (FTE) application transfers SAM metric files to the DataChannel BLB application do, done, and output directories. Chapter 4. Additional configuration steps for certain UBA Technology Packs 83

92 If SAM metric files are not transferred to the BLB application do, done, and output directories, complete the following troubleshooting steps: 1. Make sure that an FTP user account is configured on the primary and redundant SAM serers. See Configure FTP accounts on the primary and redundant SAM serers on page 36 for more information. 2. Make sure that the correct alues were specified for the SAM.EXPORT_URI and SAM.EXPORT_URI_2 parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform V4.4.3 and later Parameter ALCATEL_5620_SAM.SAM.EXPORT_URI ALCATEL_5620_SAM.SAM.EXPORT_URI_2 3. Check the UNIX file permissions. Ensure that the permissions on the do, done, and output directories are set to allow read, write, and execute by the SAM FTP user. 4. Ensure that the BLB has receied notification of the inentory from SAMIF through the idmap files. If the idmap files do not exist in the BLB application output directory, regenerate the idmap files, as follows: $ dccmd debug SAMIF "self serer firstadaptor modelinterface generatefullidmap" Replace with the channel and collector number for your installation. 5. Ensure that you hae enough disk space. For more information, see Metrics collection fails due to lack of disk space on page 87. SAM metric files do not exist in UBA directories: Typically, the DataChannel File Transfer Engine (FTE) application transfers SAM metric files to the DataChannel Uniersal Bulk Adaptor (UBA) application do, done, and output directories. If the SAM metric files do not exist in the UBA application do, done, and output directories, complete the following troubleshooting steps: 1. Make sure that an OSS user account is configured. See Configure an OSS user account on page 34 for more information. 2. Make sure that the correct alues were specified for the following parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform. 3. Check UNIX file permissions. 4. Ensure that the SAMIF is running. The UBA must get files from all of its inputs, to produce any BOF files in the output directory. If one of the inputs is blocked, all BOF production is blocked. One of these inputs is the datachannel/jms_xml directory, which contains aailability data. This data is generated by the SAMIF. Therefore, if the SAMIF is not running, UBA data generation is blocked. 5. Ensure that you hae enough disk space. For more information, see Metrics collection fails due to lack of disk space on page 87. Files do not exist in UBA output directory: Typically, the DataChannel File Transfer Engine (FTE) application transfers files to the DataChannel Uniersal Bulk Adaptor (UBA) application output directory. 84 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

93 Make sure the that UBA receies all the expected input files. If the UBA does not receie these files, it will block the creation of BOFs (Binary Object Files) until they are receied. If the files do not exist in the UBA application output directory, complete the following troubleshooting steps: 1. Check the Bulk Load Balancer (BLB) output directory to make sure that the UBAs are picking up the files. 2. Check the UBA and SAMIF settings. The creation of BOF files is blocked when, aailability data in the SAMIF is disabled, for either the physical port or access interfaces, and the UBA is configured to expect this aailability data. In this case, make sure that the SAMIF settings are configured as follows: ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT.PhysicalPort.ACTIVE=TRUE ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT.AccessInterface.ACTIVE=TRUE When ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT.AccessInterface.ACTIVE=TRUE it will collect the aailability xml files and inentory for AccessInterface. When ALCATEL_5620_SAM.SAM.JMS_FILE_OUTPUT.AccessInterface.ACTIVE=FALSE it will not collect the aailability xml files and inentory for AccessInterface. Note: The aboe TRUE and FALSE settings only apply to AccessInterface and not to PhysicalPort. Howeer, if the intention is to not collect the aailability data, then make sure that the UBA has a blank alue assigned as follows: UBA ALCATEL_5620_SAM.AVAIL_NAME_SPACE= Note: If the UBA setting aboe is changed to either a blank alue or an actual alue, then the UBA state may need to be remoed and restarted if the change is not effectie by just changing the configuration and restarting. 3. Check that the SAMIF is running. When collecting aailability metrics, the SAMIF needs to be running as it proides raw data used for aailability calculations to the UBAs. If the SAMIF is stopped, and therefore not producing this data, the UBA(s) will not produce any BOF output. 4. Make sure the BLB requests to the SAM serer are successfully creating all the expected input files. BLB files may not be correctly written by the SAM serer if they hae erroneous metric filter specifications configured. See BLB requests metric files but they are not created on page 87 for more information. 5. If the UBA is not producing files because it is not receiing input, then it may be possible to issue a debug command to help determine the schema that is not receiing input. The command: dccmd debug UBA "(self serer firstadaptor rootoperator sources collect: [:each each source -> each peek])" This displays the timestamp and records the status of each schema. "nil" can indicate a schema has not seen any data, but it could also show nil while the pack is processing. dccmd debug UBA "(self serer firstadaptor rootoperator sources collect: [:each each source -> each peek notnil])" This displays the schema inputs, and if any are false, then they may hae no input. Alternatiely, they are between inputs. This can be useful for debugging stream merge blockage issues. Chapter 4. Additional configuration steps for certain UBA Technology Packs 85

94 BOF files exist with no meaningful data in the UBA output directory: Typically, the DataChannel File Transfer Engine (FTE) application transfers BOFs (Binary Object Files) to the DataChannel Uniersal Bulk Adaptor (UBA) application output directory. If the BOF files exist in the UBA application output directory with no meaningful data (that is, there are no metric IDs in the files), complete the following troubleshooting steps: 1. Make sure that you correctly installed the Alcatel-Lucent 5620 SAM Technology Pack 2. Try to re-run the inentory 3. Perform the following actions as a last resort: a. Stop the SAMIF application. b. Delete all of the inentory. c. Remoe the SAMIF directory (including all subdirectories). d. Restart the SAMIF application. These actions re-create the inentory with new IDs. In general, do not use this troubleshooting tip except during initial installation of the Alcatel-Lucent 5620 SAM Technology Pack. BOF files do not exist in the FTE output directory: Typically, the DataChannel File Transfer Engine (FTE) application transfers BOFs (Binary Object Files) to the DataChannel FTE application output directory. If the BOF files are not transferred to the FTE application output directory, complete the following troubleshooting steps: 1. Make sure that an FTP user account is configured on the primary and redundant SAM serers. See Configure FTP accounts on the primary and redundant SAM serers on page 36 for more information. 2. Make sure that the user exists on the SAM serer and that the correct FTP username and password alues were specified for the SAM.EXPORT_URI and SAM.EXPORT_URI_2 parameters, as described in Specifying parameter alues on page 75, based on the Tioli Netcool Performance Manager platform: Platform Tioli Netcool/Proiso and Tioli Netcool Performance Manager or later Parameter ALCATEL_5620_SAM.SAM.EXPORT_URI ALCATEL_5620_SAM.SAM.EXPORT_URI_2 3. Check the UNIX permissions. 4. Ensure that you hae enough disk space. For more information, see Metrics collection fails due to lack of disk space on page 87 BOF files do not exist in the CME output directory: Typically, the DataChannel File Transfer Engine (FTE) application transfers BOFs (Binary Object Files) to the DataChannel Complex Metric Engine (CME) application output directory. If the BOF files are not transferred to the CME application output directory, complete the following troubleshooting steps: 86 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

95 1. Make sure that you imported the Alcatel-Lucent 5620 SAM Technology Pack predefined collection requests. For more information, see the Actiate data collection requests step in Configuring UBA Technology Packs on page Check the UNIX permissions. 3. Ensure that you hae enough disk space. For more information, see Metrics collection fails due to lack of disk space. BLB requests metric files but they are not created: The BLB application requests metric data files from the SAM serer each period, and retriees them to process and create the metric. If one of the files it requests is not created, then that file will be missing for a period. If BLB metric files are missing, complete the following steps: 1. Check user-specified filters. If there is a problem with user-specified filters, this could result in files not being written to and the full dump could loop. If the user specifies a filter of the type property: alue and the filter specification is not alid for the SAM serer, it will fail to write a file. There is no TNPM log indication for this failure case, but the file will not be written to the XML output directory on the SAM serer. If SOAP request logging is enabled on the SAM serer, the error will be logged by the SAM serer in the response to the request. There are two cases where this could happen: a. The property specified in the filter is not aailable in the metric class being requested. For example, if there is a typo in the property name, or simply specified a property that is not applicable to that class. This will cause the file request to fail, and no metric file will be written. Note: Information about the properties that are alid for each class are outside of the scope of this user guide. b. The filter specification uses the wrong kind of matching syntax for the property specified. As described in the section Matching patterns in filter syntax: strings and numbers, the * and? are only applicable to string properties, and the range() match is only applicable to numerical properties. Using these matching constructs on the wrong type of property will result in failure to retriee a file, and no metric file will be written. Note: Information about the types of properties (whether they are numerical or string) is outside the scope of this guide. Metrics collection fails due to lack of disk space: If the metric-collection operation fails on the SAM serer, make sure that you hae enough disk space on the computer or serer on which Tioli Netcool Performance Manager is installed. The amount of space required depends on the following: Size of the SAM network Values set for the following retention parameters in the dc.cfg file: Platform Tioli Netcool/Proiso and Tioli Netcool Performance Manager or later Parameter FC_RETENTION_HOURS Chapter 4. Additional configuration steps for certain UBA Technology Packs 87

96 It is possible, in a SAM networking enironment, that seeral gigabytes worth of data files could be collected and transferred to the UBA application done directory each day. These data files accumulate according to the alues specified for the retention parameters. Therefore, it is possible to use the maximum disk space before the retention period expires and the DataChannel deletes the data files from the done directory. You must monitor the size of the data files transferred to the done directory during metric collection, and determine whether adjustments must be made to the retention parameters. SAM serer software hangs: When the SAM serer software hangs, no inentory files are transferred to the default directory on the SAM serer. If the SAM serer software hangs, make sure that you imported the Alcatel-Lucent 5620 SAM Technology Pack predefined collection requests. For more information, see the Actie data collection requests step in Configuring UBA Technology Packs on page 15. Binary files acquired instead of text files: If a BLB or UBA application that is expecting text input acquires binary files, there is a risk of corrupting the persistent state of the BLB or UBA application. This corruption could cause errors to occur when the BLB or UBA application restarts, or later when it runs. Although such a BLB or UBA application is ery unlikely to acquire binary files instead of text files, this situation could happen in either of the following circumstances: The URIs are inadertently altered to pick up bad files. The file becomes corrupted. To aoid the risk of corrupting the persistent state of the BLB or UBA application, make sure that the BLB or UBA application that is expecting text input is neer allowed to acquire binary files. There is no workaround to this issue. If this situation occurs, contact IBM Professional Serices. Alcatel-Lucent 5670 RAM Technology Pack Additional configuration steps required for Alcatel-Lucent 5670 RAM Technology Pack. Oeriew of Alcatel-Lucent 5670 RAM Technology Pack Alcatel-Lucent 5670 RAM Technology Pack is bundled with ramadaptor and saminentory tools. You must configure the saminentory on page 91 and ramadaptor on page 92. Alcatel-Lucent 5620 SAM Technology Pack ersion or later is the dependent pack and this pack must be installed and the SAM inentory is running. The Alcatel-Lucent 5670 RAM Technology Pack data flow is as shown in the following diagram: 88 IBM Tioli Netcool Performance Manager: Pack Installation and Configuration Guide

97 1. ramadaptor SFTP xdr files from the RAM serer. 2. ramadaptor conerts the xdr file from binary format to text format. 3. ramadaptor distributes the xdr text files to multiple directories. 4. UBA collectors pick up the xdr text files from ramadaptor directory and process the files. 5. UBA collectors pick up the cs file generated by saminentory. The content of the cs file is obtained from the Alcatel-Lucent 5620 SAM Technology Pack resource properties during inentory and the alues are assigned to the Alcatel-Lucent 5670 RAM Technology Pack resource properties. Bulk input file formats in Alcatel-Lucent 5670 RAM Technology Pack There are many formats associated with Bulk input files, for example CSV, XML, and binary. Typically, a technology pack proides a Bulk Adaptor Design File (implemented as a JaaScript file) that defines the format or formats of the Bulk input files for which it is responsible for processing. This Bulk Adaptor Design File processes both inentory and statistics from the same Bulk input file. More specifically, this Bulk Adaptor Design File proides a function that creates the Bulk collection formula names. Some technology packs might proide seeral Bulk Adaptor Design Files each of which handles a specific Bulk input file format. Alcatel-Lucent 5670 RAM deices produce xdr files that are named by using the following syntax: <statistics types>_n<ip>_d<file_inteal>_t<unix_timestamp>_v<ersion>.xdr For example: AA_AP N D15 T V2.xdr Chapter 4. Additional configuration steps for certain UBA Technology Packs 89

IBM Tivoli Netcool Performance Manager Wireline Component October 2015 Document Revision R2E1. Pack Upgrade Guide IBM

IBM Tivoli Netcool Performance Manager Wireline Component October 2015 Document Revision R2E1. Pack Upgrade Guide IBM IBM Tioli Netcool Performance Manager Wireline Component October 2015 Document Reision R2E1 Pack Upgrade Guide IBM Note Before using this information and the product it supports, read the information in

More information

IBM Tivoli Netcool Performance Manager Wireline Component July 2014 Document Revision R2E1. Installing Technology Packs

IBM Tivoli Netcool Performance Manager Wireline Component July 2014 Document Revision R2E1. Installing Technology Packs IBM Tioli Netcool Performance Manager Wireline Component July 2014 Document Reision R2E1 Installing Technology Packs Note Before using this information and the product it supports, read the information

More information

IBM Tivoli Netcool Performance Manager Wireline Component April 2014 Document Revision R2E1. Pack Release Notes

IBM Tivoli Netcool Performance Manager Wireline Component April 2014 Document Revision R2E1. Pack Release Notes IBM Tioli Netcool Manager Wireline Component April 2014 Document Reision R2E1 Pack Release Notes Note Before using this information and the product it supports, read the information in Notices on page

More information

Installation Guide 1.3.1

Installation Guide 1.3.1 Tioli Netcool Performance Manager 1.3.1 Wireline Component Document Reision R1E10 Installation Guide 1.3.1 Note Before using this information and the product it supports, read the information in Notices

More information

IBM Operational Decision Manager Version 8 Release 5. Installation Guide

IBM Operational Decision Manager Version 8 Release 5. Installation Guide IBM Operational Decision Manager Version 8 Release 5 Installation Guide Note Before using this information and the product it supports, read the information in Notices on page 51. This edition applies

More information

IBM Tivoli Netcool Performance Manager Wireline Component June 2018 Document Revision R2E1. Installing Technology Packs IBM

IBM Tivoli Netcool Performance Manager Wireline Component June 2018 Document Revision R2E1. Installing Technology Packs IBM IBM Tivoli Netcool Performance Manager Wireline Component June 2018 Document Revision R2E1 Installing Technology Packs IBM Note Before using this information and the product it supports, read the information

More information

Road Map for the Typical Installation Option of IBM Tivoli Monitoring Products, Version 5.1.0

Road Map for the Typical Installation Option of IBM Tivoli Monitoring Products, Version 5.1.0 Road Map for the Typical Installation Option of IBM Tioli Monitoring Products, Version 5.1.0 Objectie Who should use the Typical installation method? To use the Typical installation option to deploy an

More information

IBM Security Access Manager for Web Version 7.0. Installation Guide GC

IBM Security Access Manager for Web Version 7.0. Installation Guide GC IBM Security Access Manager for Web Version 7.0 Installation Guide GC23-6502-02 IBM Security Access Manager for Web Version 7.0 Installation Guide GC23-6502-02 Note Before using this information and the

More information

IBM Cognos Dynamic Query Analyzer Version Installation and Configuration Guide IBM

IBM Cognos Dynamic Query Analyzer Version Installation and Configuration Guide IBM IBM Cognos Dynamic Query Analyzer Version 11.0.0 Installation and Configuration Guide IBM Product Information This document applies to IBM Cognos Analytics ersion 11.0.0 and may also apply to subsequent

More information

IBM Features on Demand. User's Guide

IBM Features on Demand. User's Guide IBM Features on Demand User's Guide IBM Features on Demand User's Guide Note: Before using this information and the product it supports, read the general information in Appendix B, Notices, on page 55.

More information

IBM i Version 7.2. Security Service Tools IBM

IBM i Version 7.2. Security Service Tools IBM IBM i Version 7.2 Security Serice Tools IBM IBM i Version 7.2 Security Serice Tools IBM Note Before using this information and the product it supports, read the information in Notices on page 37. This

More information

Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Server

Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Server Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Serer ii Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Serer Contents Installing with

More information

xseries Systems Management IBM Diagnostic Data Capture 1.0 Installation and User s Guide

xseries Systems Management IBM Diagnostic Data Capture 1.0 Installation and User s Guide xseries Systems Management IBM Diagnostic Data Capture 1.0 Installation and User s Guide Note Before using this information and the product it supports, read the general information in Appendix C, Notices,

More information

IBM Tivoli Monitoring for Business Integration. User s Guide. Version SC

IBM Tivoli Monitoring for Business Integration. User s Guide. Version SC IBM Tioli Monitoring for Business Integration User s Guide Version 5.1.1 SC32-1403-00 IBM Tioli Monitoring for Business Integration User s Guide Version 5.1.1 SC32-1403-00 Note Before using this information

More information

IBM Tivoli Monitoring: AIX Premium Agent Version User's Guide SA

IBM Tivoli Monitoring: AIX Premium Agent Version User's Guide SA Tioli IBM Tioli Monitoring: AIX Premium Agent Version 6.2.2.1 User's Guide SA23-2237-06 Tioli IBM Tioli Monitoring: AIX Premium Agent Version 6.2.2.1 User's Guide SA23-2237-06 Note Before using this information

More information

IBM Agent Builder Version User's Guide IBM SC

IBM Agent Builder Version User's Guide IBM SC IBM Agent Builder Version 6.3.5 User's Guide IBM SC32-1921-17 IBM Agent Builder Version 6.3.5 User's Guide IBM SC32-1921-17 Note Before you use this information and the product it supports, read the information

More information

IBM. Installing. IBM Emptoris Suite. Version

IBM. Installing. IBM Emptoris Suite. Version IBM Emptoris Suite IBM Installing Version 10.1.0 IBM Emptoris Suite IBM Installing Version 10.1.0 ii IBM Emptoris Suite: Installing Copyright Note: Before using this information and the product it supports,

More information

IBM Tivoli Netcool Performance Manager Wireline Component October 2014 Document Revision R2E1. Pack Release Notes

IBM Tivoli Netcool Performance Manager Wireline Component October 2014 Document Revision R2E1. Pack Release Notes 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.

More information

IBM Tivoli Storage Manager for Windows Version Tivoli Monitoring for Tivoli Storage Manager

IBM Tivoli Storage Manager for Windows Version Tivoli Monitoring for Tivoli Storage Manager IBM Tioli Storage Manager for Windows Version 7.1.0 Tioli Monitoring for Tioli Storage Manager IBM Tioli Storage Manager for Windows Version 7.1.0 Tioli Monitoring for Tioli Storage Manager Note: Before

More information

License Administrator s Guide

License Administrator s Guide IBM Tioli License Manager License Administrator s Guide Version 1.1.1 GC23-4833-01 Note Before using this information and the product it supports, read the information under Notices on page 115. Second

More information

Deployment Overview Guide

Deployment Overview Guide IBM Security Priileged Identity Manager Version 1.0 Deployment Oeriew Guide SC27-4382-00 IBM Security Priileged Identity Manager Version 1.0 Deployment Oeriew Guide SC27-4382-00 Note Before using this

More information

IBM. Basic system operations. System i. Version 6 Release 1

IBM. Basic system operations. System i. Version 6 Release 1 IBM System i Basic system operations Version 6 Release 1 IBM System i Basic system operations Version 6 Release 1 Note Before using this information and the product it supports, read the information in

More information

Tivoli Application Dependency Discovery Manager Version 7.3. Installation Guide IBM

Tivoli Application Dependency Discovery Manager Version 7.3. Installation Guide IBM Tioli Application Dependency Discoery Manager Version 7.3 Installation Guide IBM Tioli Application Dependency Discoery Manager Version 7.3 Installation Guide IBM Note Before using this information and

More information

Solutions for BSM Version 1.1. Solutions for BSM Guide

Solutions for BSM Version 1.1. Solutions for BSM Guide Solutions for BSM Version 1.1 Solutions for BSM Guide Solutions for BSM Version 1.1 Solutions for BSM Guide Note Before using this information and the product it supports, read the information in Notices.

More information

IBM Director Virtual Machine Manager 1.0 Installation and User s Guide

IBM Director Virtual Machine Manager 1.0 Installation and User s Guide IBM Director 4.20 Virtual Machine Manager 1.0 Installation and User s Guide Note Before using this information and the product it supports, read the general information in Appendix D, Notices, on page

More information

IBM i Version 7.2. Connecting to IBM i IBM i Access for Web IBM

IBM i Version 7.2. Connecting to IBM i IBM i Access for Web IBM IBM i Version 7.2 Connecting to IBM i IBM i Access for Web IBM IBM i Version 7.2 Connecting to IBM i IBM i Access for Web IBM Note Before using this information and the product it supports, read the information

More information

Installation and Setup Guide

Installation and Setup Guide IBM Tioli Monitoring for Business Integration Installation and Setup Guide Version 5.1.1 SC32-1402-00 IBM Tioli Monitoring for Business Integration Installation and Setup Guide Version 5.1.1 SC32-1402-00

More information

IBM Tivoli Netcool Performance Manager Wireline Component June 2018 Document Revision R2E1. Pack Release Notes IBM

IBM Tivoli Netcool Performance Manager Wireline Component June 2018 Document Revision R2E1. Pack Release Notes IBM IBM Tivoli Netcool Manager Wireline Component June 2018 Document Revision R2E1 Pack Release Notes IBM Note Before using this information and the product it supports, read the information in Notices on

More information

Tivoli Application Dependency Discovery Manager Version 7 Release 2.1. Installation Guide

Tivoli Application Dependency Discovery Manager Version 7 Release 2.1. Installation Guide Tioli Application Dependency Discoery Manager Version 7 Release 2.1 Installation Guide Tioli Application Dependency Discoery Manager Version 7 Release 2.1 Installation Guide Note Before using this information

More information

DataView User and Administrator Guide

DataView User and Administrator Guide Tioli Netcool Performance Manager 1.3 Wireline Component (Netcool/Proiso 5.2) Document Reision R2E1 DataView User and Administrator Guide Note Before using this information and the product it supports,

More information

IBM Tivoli Storage Manager for Windows Version 7.1. Installation Guide

IBM Tivoli Storage Manager for Windows Version 7.1. Installation Guide IBM Tioli Storage Manager for Windows Version 7.1 Installation Guide IBM Tioli Storage Manager for Windows Version 7.1 Installation Guide Note: Before using this information and the product it supports,

More information

IBM. RSE for z/os User's Guide. IBM Explorer for z/os. Version 3 Release 1 SC

IBM. RSE for z/os User's Guide. IBM Explorer for z/os. Version 3 Release 1 SC IBM Explorer for z/os IBM RSE for z/os User's Guide Version 3 Release 1 SC27-8433-03 IBM Explorer for z/os IBM RSE for z/os User's Guide Version 3 Release 1 SC27-8433-03 Note Before using this information,

More information

IBM Spectrum Protect Snapshot for Oracle Version What's new Supporting multiple Oracle databases with a single instance IBM

IBM Spectrum Protect Snapshot for Oracle Version What's new Supporting multiple Oracle databases with a single instance IBM IBM Spectrum Protect Snapshot for Oracle Version 8.1.4 What's new Supporting multiple Oracle databases with a single instance IBM IBM Spectrum Protect Snapshot for Oracle Version 8.1.4 What's new Supporting

More information

Registration Authority Desktop Guide

Registration Authority Desktop Guide IBM SecureWay Trust Authority Registration Authority Desktop Guide Version 3 Release 1.1 SH09-4530-01 IBM SecureWay Trust Authority Registration Authority Desktop Guide Version 3 Release 1.1 SH09-4530-01

More information

IBM InfoSphere Information Server Integration Guide for IBM InfoSphere DataStage Pack for SAP BW

IBM InfoSphere Information Server Integration Guide for IBM InfoSphere DataStage Pack for SAP BW IBM InfoSphere Information Serer Version 11 Release 3 IBM InfoSphere Information Serer Integration Guide for IBM InfoSphere DataStage Pack for SAP BW SC19-4314-00 IBM InfoSphere Information Serer Version

More information

IBM Security Access Manager for Web Version 7.0. Upgrade Guide SC

IBM Security Access Manager for Web Version 7.0. Upgrade Guide SC IBM Security Access Manager for Web Version 7.0 Upgrade Guide SC23-6503-02 IBM Security Access Manager for Web Version 7.0 Upgrade Guide SC23-6503-02 Note Before using this information and the product

More information

IBM. Client Configuration Guide. IBM Explorer for z/os. Version 3 Release 1 SC

IBM. Client Configuration Guide. IBM Explorer for z/os. Version 3 Release 1 SC IBM Explorer for z/os IBM Client Configuration Guide Version 3 Release 1 SC27-8435-01 IBM Explorer for z/os IBM Client Configuration Guide Version 3 Release 1 SC27-8435-01 Note Before using this information,

More information

IBM Tivoli Storage Manager for Windows Version Installation Guide

IBM Tivoli Storage Manager for Windows Version Installation Guide IBM Tioli Storage Manager for Windows Version 7.1.1 Installation Guide IBM Tioli Storage Manager for Windows Version 7.1.1 Installation Guide Note: Before using this information and the product it supports,

More information

iplanetwebserveruser sguide

iplanetwebserveruser sguide IBM Tioli Monitoring for Web Infrastructure iplanetwebsereruser sguide Version 5.1.0 SH19-4574-00 IBM Tioli Monitoring for Web Infrastructure iplanetwebsereruser sguide Version 5.1.0 SH19-4574-00 Note

More information

Internet Information Server User s Guide

Internet Information Server User s Guide IBM Tioli Monitoring for Web Infrastructure Internet Information Serer User s Guide Version 5.1.0 SH19-4573-00 IBM Tioli Monitoring for Web Infrastructure Internet Information Serer User s Guide Version

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Windows GC32-1604-00 Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Windows GC32-1604-00

More information

IBM. Troubleshooting Operations Center client updates

IBM. Troubleshooting Operations Center client updates IBM Troubleshooting Operations Center client updates ii Troubleshooting Operations Center client updates Contents Troubleshooting Operations Center client updates............ 1 iii i Troubleshooting Operations

More information

Solutions for BSM 1.1 Expanded Operating System Release. Solutions for BSM Guide

Solutions for BSM 1.1 Expanded Operating System Release. Solutions for BSM Guide Solutions for BSM 1.1 Expanded Operating System Release Solutions for BSM Guide Solutions for BSM 1.1 Expanded Operating System Release Solutions for BSM Guide Note Before using this information and the

More information

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Windows GC32-1618-00 Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Windows GC32-1618-00 Note: Before using this information

More information

Upward Integration Modules Installation Guide

Upward Integration Modules Installation Guide IBM Director 4.1 Upward Integration Modules Installation Guide SC01-R051-20 IBM Director 4.1 Upward Integration Modules Installation Guide SC01-R051-20 Note: Before using this information and the product

More information

IBM Unica Optimize Version 8 Release 6 May 25, Installation Guide

IBM Unica Optimize Version 8 Release 6 May 25, Installation Guide IBM Unica Optimize Version 8 Release 6 May 25, 2012 Installation Guide Note Before using this information and the product it supports, read the information in Notices on page 35. This edition applies to

More information

IBM System Migration Assistant 4.2. User s Guide

IBM System Migration Assistant 4.2. User s Guide IBM System Migration Assistant 4.2 User s Guide IBM System Migration Assistant 4.2 User s Guide Note: Before using this information and the product it supports, read the general information in Appendix

More information

DocumentationcorrectionsforIBMTivoli Storage Productivity Center V4.2

DocumentationcorrectionsforIBMTivoli Storage Productivity Center V4.2 DocumentationcorrectionsforIBMTioli Storage Productiity Center V4.2 ii Documentation corrections for IBM Tioli Storage Productiity Center V4.2 Contents Documentation corrections for IBM Tioli Storage Productiity

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Migration Guide for Windows GC32-1608-00 Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Migration Guide for Windows GC32-1608-00

More information

IBM Marketing Operations and Campaign Version 9 Release 0 January 15, Integration Guide

IBM Marketing Operations and Campaign Version 9 Release 0 January 15, Integration Guide IBM Marketing Operations and Campaign Version 9 Release 0 January 15, 2013 Integration Guide Note Before using this information and the product it supports, read the information in Notices on page 51.

More information

IBM Marketing Operations and Campaign Version 9 Release 1.1 November 26, Integration Guide

IBM Marketing Operations and Campaign Version 9 Release 1.1 November 26, Integration Guide IBM Marketing Operations and Campaign Version 9 Release 1.1 Noember 26, 2014 Integration Guide Note Before using this information and the product it supports, read the information in Notices on page 55.

More information

IBM. Connecting to IBM i IBM i Access for Web. IBM i 7.1

IBM. Connecting to IBM i IBM i Access for Web. IBM i 7.1 IBM IBM i Connecting to IBM i IBM i Access for Web 7.1 IBM IBM i Connecting to IBM i IBM i Access for Web 7.1 Note Before using this information and the product it supports, read the information in Notices,

More information

IBM. Installing and Configuring Operations and Engineering Dashboards

IBM. Installing and Configuring Operations and Engineering Dashboards IBM Tioli Netcool Performance Manager 1.4.3 Operations and Engineering Dashboards Document Reision R2E2 Installing and Configuring Operations and Engineering Dashboards IBM Note Before using this information

More information

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Unix GC32-1619-00 Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Unix GC32-1619-00 Note: Before using this information

More information

Tivoli IBM Tivoli Advanced Catalog Management for z/os

Tivoli IBM Tivoli Advanced Catalog Management for z/os Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring Agent User s Guide SC23-9818-00 Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring Agent User s Guide

More information

Netcool Configuration Manager Version Installation and Configuration Guide R2E6 IBM

Netcool Configuration Manager Version Installation and Configuration Guide R2E6 IBM Netcool Configuration Manager Version 6.4.1 Installation and Configuration Guide R2E6 IBM Netcool Configuration Manager Version 6.4.1 Installation and Configuration Guide R2E6 IBM Note Before using this

More information

IBM Tivoli Storage Manager for Virtual Environments Version Data Protection for VMware Installation Guide IBM

IBM Tivoli Storage Manager for Virtual Environments Version Data Protection for VMware Installation Guide IBM IBM Tioli Storage Manager for Virtual Enironments Version 7.1.6 Data Protection for VMware Installation Guide IBM IBM Tioli Storage Manager for Virtual Enironments Version 7.1.6 Data Protection for VMware

More information

System i and System p. Capacity on Demand

System i and System p. Capacity on Demand System i and System p Capacity on Demand System i and System p Capacity on Demand Note Before using this information and the product it supports, read the information in Notices on page 65 and the IBM

More information

IBM Monitoring Agent for OpenStack Version User's Guide IBM SC

IBM Monitoring Agent for OpenStack Version User's Guide IBM SC IBM Monitoring Agent for OpenStack Version 7.5.0.1 User's Guide IBM SC27-6586-01 IBM Monitoring Agent for OpenStack Version 7.5.0.1 User's Guide IBM SC27-6586-01 Note Before using this information and

More information

IBM Interact Version 9 Release 1 October 25, Installation Guide

IBM Interact Version 9 Release 1 October 25, Installation Guide IBM Interact Version 9 Release 1 October 25, 2013 Installation Guide Note Before using this information and the product it supports, read the information in Notices on page 65. This edition applies to

More information

Planning and Installation

Planning and Installation Tioli Workload Scheduler Version 8.5. (Reised October 200) Planning and Installation SC32-273-09 Tioli Workload Scheduler Version 8.5. (Reised October 200) Planning and Installation SC32-273-09 Note Before

More information

IBM Tivoli Configuration Manager for Automated Teller Machines. Release Notes. Version 2.1 SC

IBM Tivoli Configuration Manager for Automated Teller Machines. Release Notes. Version 2.1 SC IBM Tioli Configuration Manager for Automated Teller Machines Release Notes Version 2.1 SC32-1254-00 IBM Tioli Configuration Manager for Automated Teller Machines Release Notes Version 2.1 SC32-1254-00

More information

Installation and Setup Guide

Installation and Setup Guide IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide Version 5.1.1 GC32-0839-01 IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide Version 5.1.1

More information

Version 10 Release 0 February IBM Marketing Platform Installation Guide IBM

Version 10 Release 0 February IBM Marketing Platform Installation Guide IBM Version 10 Release 0 February 2017 IBM Marketing Platform Installation Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 69. This edition

More information

Managing Server Installation and Customization Guide

Managing Server Installation and Customization Guide IBM Tioli Composite Application Manager for Application Diagnostics Version 7.1.0.4 Managing Serer Installation and Customization Guide SC27-2825-00 IBM Tioli Composite Application Manager for Application

More information

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Active Directory Agent Fix Pack 13.

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Active Directory Agent Fix Pack 13. IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Actie Directory Agent 6.3.1 Fix Pack 13 Reference IBM IBM Tioli Composite Application Manager for Microsoft Applications:

More information

IBM Tivoli Monitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning Version 7.1 Fix Pack 1. User s Guide SC

IBM Tivoli Monitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning Version 7.1 Fix Pack 1. User s Guide SC IBM Tioli Monitoring for Virtual Enironments: Dashboard, Reporting, and Capacity Planning Version 7.1 Fix Pack 1 User s Guide SC14-7493-01 IBM Tioli Monitoring for Virtual Enironments: Dashboard, Reporting,

More information

Mass Data Extraction User's Guide

Mass Data Extraction User's Guide Tioli Netcool Performance Manager 1.3 Wireline Component (Netcool/Proiso 5.2) Document Reision R2E2 Mass Data Extraction User's Guide Note Before using this information and the product it supports, read

More information

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Linux on Intel and Linux on iseries GC32-1616-00 Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Linux on Intel and

More information

Monitoring: Windows OS Agent Version Fix Pack 2 (Revised May 2010) User s Guide SC

Monitoring: Windows OS Agent Version Fix Pack 2 (Revised May 2010) User s Guide SC Tioli Monitoring: Windows OS Agent Version 6.2.2 Fix Pack 2 (Reised May 2010) User s Guide SC32-9445-03 Tioli Monitoring: Windows OS Agent Version 6.2.2 Fix Pack 2 (Reised May 2010) User s Guide SC32-9445-03

More information

IBM EMM Reports Version 9 Release 1 October 25, Installation and Configuration Guide

IBM EMM Reports Version 9 Release 1 October 25, Installation and Configuration Guide IBM EMM Reports Version 9 Release 1 October 25, 2013 Installation and Configuration Guide Note Before using this information and the product it supports, read the information in Notices on page 133. This

More information

IBM. Installing and configuring. Version 6.4

IBM. Installing and configuring. Version 6.4 IBM Installing and configuring Version 6.4 ii Installing and configuring Contents Installing and configuring....... 1 Planning for installation.......... 1 Premium feature actiation......... 1 Installation

More information

Extended Search Administration

Extended Search Administration IBM Extended Search Extended Search Administration Version 3 Release 7 SC27-1404-00 IBM Extended Search Extended Search Administration Version 3 Release 7 SC27-1404-00 Note! Before using this information

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Unix GC32-1605-00 Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Unix GC32-1605-00

More information

Installing and Configuring Tivoli Enterprise Data Warehouse

Installing and Configuring Tivoli Enterprise Data Warehouse Installing and Configuring Tioli Enterprise Data Warehouse Version 1 Release 1 GC32-0744-00 Installing and Configuring Tioli Enterprise Data Warehouse Version 1 Release 1 GC32-0744-00 Installing and Configuring

More information

IBM Sterling Gentran:Server for Windows. Installation Guide. Version 5.3.1

IBM Sterling Gentran:Server for Windows. Installation Guide. Version 5.3.1 IBM Sterling Gentran:Serer for Windows Installation Guide Version 5.3.1 IBM Sterling Gentran:Serer for Windows Installation Guide Version 5.3.1 Note Before using this information and the product it supports,

More information

Network Service Manager REST API Users Guide

Network Service Manager REST API Users Guide Netcool Configuration Manager Version 641 Network Serice Manager REST API Users Guide for R2E3 Netcool Configuration Manager Version 641 Network Serice Manager REST API Users Guide for R2E3 Note Before

More information

IBM Security Access Manager Version Appliance administration topics

IBM Security Access Manager Version Appliance administration topics IBM Security Access Manager Version 8.0.0.5 Appliance administration topics IBM Security Access Manager Version 8.0.0.5 Appliance administration topics ii IBM Security Access Manager Version 8.0.0.5:

More information

WebSphere MQ Configuration Agent User's Guide

WebSphere MQ Configuration Agent User's Guide IBM Tioli Composite Application Manager for Applications Version 7.1 WebSphere MQ Configuration Agent User's Guide SC14-7525-00 IBM Tioli Composite Application Manager for Applications Version 7.1 WebSphere

More information

IBM Campaign Version 9 Release 1 October 25, User's Guide

IBM Campaign Version 9 Release 1 October 25, User's Guide IBM Campaign Version 9 Release 1 October 25, 2013 User's Guide Note Before using this information and the product it supports, read the information in Notices on page 229. This edition applies to ersion

More information

IBM Tivoli Privacy Manager for e-business. Installation Guide. Version 1.1 SC

IBM Tivoli Privacy Manager for e-business. Installation Guide. Version 1.1 SC IBM Tioli Priacy Manager for e-business Installation Guide Version 1.1 SC23-4791-00 IBM Tioli Priacy Manager for e-business Installation Guide Version 1.1 SC23-4791-00 Note: Before using this information

More information

ImageUltra Builder Version 1.1. User Guide

ImageUltra Builder Version 1.1. User Guide ImageUltra Builder Version 1.1 User Guide ImageUltra Builder Version 1.1 User Guide Note Before using this information and the product it supports, be sure to read Notices on page 83. First Edition (October

More information

Tivoli Monitoring: Windows OS Agent

Tivoli Monitoring: Windows OS Agent Tioli Monitoring: Windows OS Agent Version 6.2.2 User s Guide SC32-9445-03 Tioli Monitoring: Windows OS Agent Version 6.2.2 User s Guide SC32-9445-03 Note Before using this information and the product

More information

Guide to Managing Common Metadata

Guide to Managing Common Metadata IBM InfoSphere Information Serer Version 11 Release 3 Guide to Managing Common Metadata SC19-4297-01 IBM InfoSphere Information Serer Version 11 Release 3 Guide to Managing Common Metadata SC19-4297-01

More information

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Unix GC32-1615-00 Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Unix GC32-1615-00 Note: Before using this information

More information

IBM Endpoint Manager Version 9.0. Patch Management for AIX User's Guide

IBM Endpoint Manager Version 9.0. Patch Management for AIX User's Guide IBM Endpoint Manager Version 9.0 Patch Management for AIX User's Guide IBM Endpoint Manager Version 9.0 Patch Management for AIX User's Guide Note Before using this information and the product it supports,

More information

WebSphere Message Broker Monitoring Agent User's Guide

WebSphere Message Broker Monitoring Agent User's Guide IBM Tioli OMEGAMON XE for Messaging on z/os Version 7.1 WebSphere Message Broker Monitoring Agent User's Guide SC23-7954-03 IBM Tioli OMEGAMON XE for Messaging on z/os Version 7.1 WebSphere Message Broker

More information

IBM FAStT Storage Manager Version 8.2 IBM. Installation and Support Guide for Novell NetWare

IBM FAStT Storage Manager Version 8.2 IBM. Installation and Support Guide for Novell NetWare IBM FAStT Storage Manager Version 8.2 IBM Installation and Support Guide for Noell NetWare IBM FAStT Storage Manager Version 8.2 Installation and Support Guide for Noell NetWare Note Before using this

More information

IBM Tivoli Enterprise Console. User s Guide. Version 3.9 SC

IBM Tivoli Enterprise Console. User s Guide. Version 3.9 SC IBM Tioli Enterprise Console User s Guide Version 3.9 SC32-1235-00 IBM Tioli Enterprise Console User s Guide Version 3.9 SC32-1235-00 Note Before using this information and the product it supports, read

More information

Authorization C API Developer Reference

Authorization C API Developer Reference IBM Security Access Manager for Web Version 7.0 Authorization C API Deeloper Reference SC23-6515-02 IBM Security Access Manager for Web Version 7.0 Authorization C API Deeloper Reference SC23-6515-02

More information

Tivoli System Automation Application Manager

Tivoli System Automation Application Manager Tioli System Automation Application Manager Version 3.1 Installation and Configuration Guide SC33-8420-01 Tioli System Automation Application Manager Version 3.1 Installation and Configuration Guide SC33-8420-01

More information

LotusLive. LotusLive Engage and LotusLive Connections User's Guide

LotusLive. LotusLive Engage and LotusLive Connections User's Guide LotusLie LotusLie Engage and LotusLie Connections User's Guide LotusLie LotusLie Engage and LotusLie Connections User's Guide Note Before using this information and the product it supports, read the information

More information

Director Client Guide

Director Client Guide IBM InfoSphere DataStage and QualityStage Version 11 Release 3 Director Client Guide SC19-4273-00 IBM InfoSphere DataStage and QualityStage Version 11 Release 3 Director Client Guide SC19-4273-00 Note

More information

IBM Unica PredictiveInsight Version 8 Release 6 May 25, Installation Guide

IBM Unica PredictiveInsight Version 8 Release 6 May 25, Installation Guide IBM Unica PredictieInsight Version 8 Release 6 May 25, 2012 Installation Guide Note Before using this information and the product it supports, read the information in Notices on page 47. This edition applies

More information

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Linux GC32-1620-00 Tioli Tioli Proisioning Manager Version 2.1 Migration Guide for Linux GC32-1620-00 Note: Before using this information

More information

IBM Tivoli Netcool Performance Manager Wireline Component Document Revision R2E1. Installation Guide

IBM Tivoli Netcool Performance Manager Wireline Component Document Revision R2E1. Installation Guide IBM Tivoli Netcool Performance Manager 1.3.3 Wireline Component Document Revision R2E1 Installation Guide Note Before using this information and the product it supports, read the information in Notices

More information

IBM System Migration Assistant 4.1. User s Guide SC90-P288-70

IBM System Migration Assistant 4.1. User s Guide SC90-P288-70 IBM System Migration Assistant 4.1 User s Guide SC90-P288-70 Note: Before using this information and the product it supports, read the general information in Appendix D, Notices, on page 81. Third Edition

More information

IBM Tivoli Storage Manager for AIX Version Tivoli Monitoring for Tivoli Storage Manager

IBM Tivoli Storage Manager for AIX Version Tivoli Monitoring for Tivoli Storage Manager IBM Tioli Storage Manager for AIX Version 7.1.0 Tioli Monitoring for Tioli Storage Manager IBM Tioli Storage Manager for AIX Version 7.1.0 Tioli Monitoring for Tioli Storage Manager Note: Before using

More information

ImageUltra Builder Version 2.0. User Guide

ImageUltra Builder Version 2.0. User Guide ImageUltra Builder Version 2.0 User Guide ImageUltra Builder Version 2.0 User Guide Note Before using this information and the product it supports, be sure to read Appendix A, Notices, on page 153. Fifth

More information

WebSEAL Installation Guide

WebSEAL Installation Guide IBM Tioli Access Manager WebSEAL Installation Guide Version 4.1 SC32-1133-01 IBM Tioli Access Manager WebSEAL Installation Guide Version 4.1 SC32-1133-01 Note Before using this information and the product

More information