IBM Tivoli Netcool Performance Manager Wireline Component Document Revision R2E1 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
Note Before using this information and the product it supports, read the information in “Notices” on page 83. © Copyright IBM Corporation 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Installing and Using Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack . v Intended audience . . . . . . . . . . Tivoli Netcool Performance Manager - Wireline Component. . . . . . . . . . . . . Service Management Connect . . . . . . Tivoli technical training . . . . . . . . Support information . . . . . . . . . Conventions used in this publication . . . . Typeface conventions . . . . . . . . . . v . . v . . vi . . vii . . vii . . vii . . vii Chapter 1.
Upgrading the Alcatel-Lucent 5620 SAM LogToFile 2.2.0.0 Technology Pack to Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 . . . . . . . . . . . . . 54 Chapter 9. Setting up the Alcatel-Lucent 5620 SAM servers to support LogToFile . . . . . . . . . . 57 Install SAM on the primary and redundant servers Synchronize the clocks. . . . . . . . . . . Install the Alcatel-Lucent 5620 SAM Client GUI . . Configure an OSS user account . . . . . . . .
Installing and Using Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack Installing and Using Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack describes how to install and configure the various components such as: v IBM InfoSphere Information Server v IBM InfoSphere Information Client v Apache ActiveMQ Apart from these installations, this guide also talks about the following topics: v Job related tasks v The devices and technologies that operate in the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
v Technology Packs extend the Tivoli Netcool Performance Manager system with service-ready reports for network operations, business development, and customer viewing. The following figure shows the different Tivoli Netcool Performance Manager modules.
Tivoli Netcool Performance Manager Wiki on developerWorks Tivoli technical training For Tivoli technical training information, see the following Tivoli Netcool Performance Manager Training website at https://tnpmsupport.persistentsys.com/ training. Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at http://www.ibm.
v Variables and values you must provide: ... where myname represents....
Chapter 1. Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack overview The LogToFile feature is added to the SAM server to allow downstream systems to retrieve metric data as it arrives and without any filtering. The data is fed to the downstream systems in a streaming fashion. The downstream system must do the filtering with caution and as necessary.
v Filters the inventory and metric data. This function was previously handled by SAM server. v Partitions data by UBA-based partition key. This information is taken from Proviso DB. v Waits for complete data for a window period. v Merges metrics and inventory into one CSV file per period per UBA. Data collection model The performance data and accounting data metrics are for the network infrastructure and services that the Alcatel-Lucent 5620 SAM LogToFile Technology Pack manages. Figure 1.
The UBAs handle processing of both inventory and metric data. Any number of UBAs can be configured to handle this process with each UBA designated either as accounting UBA or performance UBA. The number of UBAs are best scaled up to load. These XML files are then collected and processed, with the results presented in a set of web-based reports. These reports are listed and described in Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack Reference.
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 1 shows that in the event-driven inventory, DataStage processes JMS create, delete, and update messages. DataStage resynchronizes the element names that are based on IP address and subchannel affiliations from the Tivoli Netcool Performance Manager database on startup.
Chapter 2. Devices and services Details about Alcatel-Lucent SAM 5620 LogToFile server compatibility, supported devices, Alcatel-Lucent SAM 5620 LogToFile services, data collection model, bulk input file formats, and bulk adapter design files. Alcatel-Lucent 5620 SAM server compatibility Currently, the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack runs on the Alcatel-Lucent 5620 SAM Server Release 10 and Release 11.
the SAM object property name, except that the Netcool Performance Manager property name also has the prefix sam. For information about the properties that are currently supported by the Alcatel-Lucent 5620 SAM LogToFile Technology Pack, see the IBM Tivoli Netcool Performance Manager: Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack Reference.
Bulk input file formats DataStage produces one file for each UBA per period. These files contain records of inventory and metric data. The inventory and metrics data records are in the CSV format. The initial integer identifier of the CSV files specifies a record type, and the subsequent fields contain the actual data of the record. The output CSV file from the DataStage has two sections: 1. Header 2. Data Header starts with 0 (zero), and is called as the 0-record schema.
Bulk adapter design files Tivoli Netcool Performance Manager bulk adapters support bulk input files in the CSV format. The DataStage server produces data in CSV format and uses JMS for notification of inventory changes. Each UBA technology pack provides at least one bulk adapter design file to define the data format supported by that technology pack. Technology pack developers implement bulk adapter design files using JavaScript®. Some technology packs provide several bulk adapter design files.
Chapter 3. Installation and configuration of IBM InfoSphere Information Server and related components Describes how to install and configure the various IBM InfoSphere Information Server and other related components that are required for Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack such as: Components v IBM InfoSphere Information Server 8.7 v IBM InfoSphere Information Server Client 8.7 v Apache ActiveMQ 5.5.
v Click System > System Firewall > Disable Firewall to disable the firewall. Disable the firewall temporarily until the installation is complete. About this task When you first start the installation program, it presents a non-graphical interface. The program starts a self-contained web server on the computer. You can then start a web browser on the computer or on a remote computer and access the graphical interface.
The page displays the results of the check as PASSED or FAILED. If the check found issues that might cause problems with the installation, it is marked as WARNING on the page. For more information about resolving the failed installation prerequisites, see http://pic.dhe.ibm.com/infocenter/iisinfsv/v8r7/topic/ com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/ wsisinst_install_prereq_check_fails.html. 6. When all early requirements checks are passed, click Next. 7.
15. Click Install WebSphere Application Server in the "Application Server Options" page and click Next. 16. Click Browse to select the installation directory for the WebSphere Application Server. By default, the installation directory is /opt/IBM/WebSphere/AppServer. 17. Select the Customize WebSphere Application Server profile ports check box in the "IBM WebSphere Application Server Installation" page, and then click Next. 18.
33. Click Add Projects and enter the InfoSphere DataStage projects to create in the "IBM InfoSphere DataStage Projects" page. You must create at least one project during installation. By default, a project by name dstage1 is created. Remove the dstage1 project and add the UDM project. 34. Click Next. The installation program runs a system requirements check for the selections that are made. The page displays the results of the check as PASSED or FAILED.
About this task When you first start the installation program, it presents a non-graphical interface. The program starts a self-contained web server on the computer. You can then start a web browser on the computer or on a remote computer and access the graphical interface. After you enter your settings in the wizard pages, the program stores your settings in a response file. If you run the installation program again, you can load your settings from this file into the program instead of entering them again.
The page displays the results of the check as PASSED or FAILED. If the check found issues that might cause problems with the installation, it is marked as WARNING on the page. 5. When all early requirements checks are passed, click Next. 6. Click Browse to select the directories where you want to install the Information Server in the Installation directory field, and then click Next. By default, the installation directory is C:\IBM\InformationServer 7.
11. Select the Create desktop shortcuts check box in the "Desktop shortcut creation option" page and click Next. After the installation program has collected your selections, it runs another, more detailed system requirements check in the "System Requirements Check" page that is based on your selections. During this check, it analyzes your computer resources and file system to determine whether the installation is likely to succeed. 12. Click Next if all the system requirements checks are passed.
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r7/topic/ com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/ wsisinst_ts_is_container.html. You can find more troubleshooting information in the information centers and customer support technical notes for various product modules and components. Verifying and testing the installation After you install and configure InfoSphere DataStage and InfoSphere QualityStage™, test the installation by logging in to the Administrator and Designer clients.
Installing Apache ActiveMQ Apache ActiveMQ is an open source software that is customized and bundled with Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack JAR file. Apache ActiveMQ is responsible for buffering messages that are received from SAM JMS for the DataStage Job. Apache ActiveMQ is an interface to JMS poller to pass messages. About this task Apache ActiveMQ must be installed on the same server where the IBM InfoSphere Information Server server is installed. Procedure 1.
b. Or To check that the ActiveMQ service is running, give the following command: ps -ef |grep active Installing Oracle 11g client Oracle 11g is required for DataStage to establish connection with Proviso DB. On Job start, DataStage connects to Proviso DB to obtain all collector information, which can be used for data partition for UBA. Before you begin Ensure that all dependencies are installed and kernel parameters that are updated so.
Note: The 64-bit Oracle client must be installed. 2. Configure the tnsname.ora file that is located in $ORACLE_HOME/network/admin to connect to Tivoli Netcool Performance Manager wireline. 3. Update the DataStage dsenv file that is located in $DS_HOME. By default, the $DS_HOME is /opt/IBM/InformationServer/Server/DSEngine. 4. Create a soft link to libccora11g.
Chapter 4. Configure the InfoSphere Information Server components Describes the configuration tasks. Opening the IBM InfoSphere Information Server web console Use the InfoSphere Information Server web console to manage security, view scheduled tasks, work with reports, or perform tasks that are related to IBM® InfoSphere® Business Glossary or the Information Services catalog. Before you begin To access the web console, determine the URL to use, configure your browser, and go to the console window.
Procedure 1. Open a web browser, and go to the console. The URL to use depends upon the IBM WebSphere Application Server communication protocol and configuration in use. 2. Type your user name and password. By default, use wasadmin user and password. 3. Click OK to open the Home tab. Configuring Microsoft Internet Explorer to open the IBM InfoSphere Information Server web console Procedure 1. Enable JavaScript: a. Click Tools > Internet Options . b. On the Security tab, click Custom Level. c.
Configuring Mozilla Firefox to open the IBM InfoSphere Information Server web console Procedure 1. Enable JavaScript: a. Click Tools > Options in the Content tab. 2. Set the browser to accept cookies for the InfoSphere Information Server host site. a. Click Tools > Options. b. On the Privacy tab, click the Accept cookies from sites option or click Exceptions and add the site to the allowed site list by entering the host name and click Allow. 3. Enable pop-windows for the URL of the web console. a.
accesses IBM InfoSphere Information Analyzer, you must assign the suite user role, and also the Information Analyzer Project Administrator, Data Administrator, or User role. 7. Link the dsadm user to Server Engine by using these steps: a. Expand Domain Management from Navigation pane. b. Click Engine Credentials. c. Select the server. d. Open Configuration. e. Select the Share User registry between Infosphere Information Server and its engine option. f. Click Save and Close. 8.
Chapter 5. Deploying Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 DataStage jobs You can design InfoSphere DataStage Administrator jobs by using the IBM InfoSphere DataStage and QualityStage Designer client. To deploy DataStage LogToFile, the following clients are used: Administrator Client You can create and configure the UDM project. Designer Client You can import, configure, and compile the UDM project. Director Client You can run and monitor a job.
CSV output for UBAs CSV file requires less processing effort that is compared to XML. Multiple small files are bundled in single UBA input to improve I/O utilization. Setting up a project A project is a container that organizes and provides security for objects that are supplied, created, or maintained for data integration, data profiling, quality monitoring, and so on. Projects are a method for organizing your work. You define data files, stages, and build jobs in a specific project.
4. Click the Projects tab to list the Projects. 5. Select the project UDM, and then click Properties. 6. In the Project Properties window, click Environment. The Environment Variables window opens. 7. Expand General and change the value for LD_LIBRARY_PATH variable to: /usr/lib:.:/opt/IBM/InformationServer/Server/Projects/UDM/udm/lib This is the path where the custom libraries are located. 8.
3. On the menu bar, click Import > DataStage Components. 4. In the DataStage Repository Import window, browse to the directory where you transferred the job files. Select ds_job_v2.2.0.0.6.dsx as the import file. 5. Select Import selected radio button and Perform impact analysis check box. 6. Click OK to import the job. You see the Import load progress window that shows the number of items that are loaded. 7. In the "DataStage Import" window, select all the items that are loaded and click OK. 8.
7. Click OK. 8. Click File > Exit to close IBM InfoSphere DataStage and QualityStage Designer. Configuring the CSV files in the cfg directory The four CSV files that you must configure from the cfg directory where the IBM InfoSphere Information Server server is installed. You can access the cfg directory from this location: /opt/IBM/InformationServer/Server/Projects/UDM/udm/cfg The files that you must configure are as follows: server_lookup.
collector_mapping.csv When you want to provision a new element and you have the load balancing criteria, you can specify the family, IP address of the element and collector ID it must be mapped to.
Enabling the firewall on the IBM InfoSphere Information Server and WebSphere Application Server Open and make the TCP ports available through firewall for InfoSphere Information Server and WebSphere Application Server. Procedure 1. Activate the firewall on the DataStage server by using the following steps: a. Click System > Administration > Security Level and Firewall. b. In the Security Level Configuration window, click Firewall list and select Enabled. c.
Compiling the job You must compile the job to prepare it to run on your system on the IBM InfoSphere DataStage and QualityStage Designer. Before you begin Ensure that the job named J02main5620sam that you created is open and active in the job design area. Procedure 1. Select File > Compile. ) button from the toolbar. The "Compile Job" Or, click the Compile ( window opens. As the job is compiled, the window is updated with messages from the compiler. 2.
8. Select File > Exit to close the Director client. What to do next You see many warning messages at the time of a job startup. These warning messages can be ignored. These warnings are thrown by DataStage checks. But pay attention to the warnings that you might see while the job is running. These warnings are displayed to alert the user. The job starts a daemon. This daemon is connected to SAM JMS and directs all the messages to ActiveMQ. The DataStage job reads from the ActiveMQ.
UDMD_STATUS=STOPPED UDMD_REASON=’daemon no longer running’ DS_DIR=${DS_DIR-/opt/IBM/InformationServer/Server/DSEngine} SAM_JMSURL1=${SAM_JMSURL1-10.0.0.56} SAM_JMSURL2=${SAM_JMSURL2-10.0.0.79} DS_WORKSPACE=${DS_WORKSPACE-//opt/IBM/InformationServer/Server/Projects/UDM} SAM_UNIQUE_ID=${SAM_UNIQUE_ID-devds_J01main5620sam} SAM_USERNAME=${SAM_USERNAME-sam-o} SAM_PASSWORD=${SAM_PASSWORD-5620Sam!} Look at the sam-jms-daemon.log file from the /opt/IBM/InformationServer/ Server/Projects/UDM/udm/logs directory.
Data flow in the data subdirectories Access the data directory from here: /opt/IBM/InformationServer/Server/ Projects/UDM/udm/data. The data directory contains all the data files. The different subdirectories in the data directory are as follows: in When there is a file available message from the SAM server, DataStage job fetches the XML files and places it in the in directory. done After the DataStage job processes these XML files, it moves them into the done directory.
36 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
Chapter 6. Installing the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack 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. You can install the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack either from a launchpad or by using the command line.
v Ensure that you have access to the Tivoli Integrated Portal. v Ensure that you have access to the DataChannel server. v Ensure that you have access to the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack installation files on one of the following locations: – Product distribution site: https://www-112.ibm.com/software/howtobuy/ softwareandservices. On the product distribution sites are the ProvisoPackInstaller.jar file, and technology pack JAR files.
Preinstallation setup tasks Ensure that all necessary configuration steps are completed on the prerequisite software. v Completed the following tasks: – Reviewed the release notes for the current technology pack. Note: Release notes contain important information that you must consider before you install a technology pack. They also contain information about specific patches that must be installed before you configure a technology pack – Installed the 1.3.
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 ProvisoPackInstaller.jar file. For example: mkdir -p $PVMHOME/version/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.
Note: Open a terminal emulator and log on to the DataMart server as pvuser. 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: v The DataMart home directory (for example,/opt/datamart, by default). v The Java run time environment home directory (for example, /opt/IBM/proviso/topologyEditor/jre/bin).
Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack installation directory” on page 39 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.
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 can have Collector UBA 1.1, with Complex Metric Engine 1.1 and File Transfer Engine 1.1.
g. Click Finish. The Topology Editor adds the selected stand-alone technology pack to the list of technology packs displayed in the Technology Packs view. 2. After you load 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 view, right-click the DataChannel x folder and select from the Add collector UBA menu. The Configure Collector window opens. b. Select the technology pack.
Chapter 7. Configuring the technology pack Configure the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology pack. Before you begin Ensure that you: v Have the following software and documentation for your version of Tivoli Netcool Performance Manager: – IBM Tivoli Netcool Performance Manager: Pack Release Notes for the current technology pack release – Installing Tivoli Netcool Performance Manager - Wireline Component. – IBM Tivoli Netcool Performance Manager: Pack Installation and Configuration Guide.
– Accounting UBA 4. Click Run > Run Deployer for Installation to deploy the topology that you configured. To configure the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack, follow these steps: Procedure 1. Load the DataMart environment. To load the shell with the DataMart environment, follow these steps: a. Log in to the DataMart server as pvuser. b. Create new folder DATA_CHANNEL_HOME/scripts/alcatel_5620_sam_log2file. c.
v Verify that the bulk adapter design files (*.js), scripts, other files (if any) are now in the $ cd DATA_CHANNEL_HOME/scripts/ alcatel_5620_sam_log2file directory. 3. Copy the samOss.jar file to the IBM InfoSphere Information Server. The samOss.jar file is distributed on a SAM distribution DVD referred to as the 5620 SAM software DVD-ROM, and is in the following directory: /nms/integrations/SAM_O, You must copy the samOss.
$ dccmd forget all d. Use the following command to find the process identifiers (pids) associated with the DataChannel visual processes: $ findvisual e. Use the following commands to stop each DataChannel visual process: $ $ $ $ kill kill kill kill -9 -9 -9 -9 f. Use the following commands to restart each DataChannel visual process: $ $ $ $ cnsw logw amgrw cmgrw g. Use the dccmd command to start all DataChannel applications: $ dccmd start all h.
Event Meaning The UBA application connects to the database. This event causes a message similar to the following example to display: DB_CONNECT Connecting to as If you see this database connection message without prior errors, the UBA application passed the syntax check. 7. Run the bulk inventory profile. The UBA application handles the inventory and metrics according to the instructions provided in the technology pack design file or files.
0 * * * -action 0 * * * -action * . /opt/datamart/dataMart.env && inventory -name bulk_101 pregrouping -reload -noX * . /opt/datamart/dataMart.env && inventory -name bulk_101 grouping -reload -noX For more information about the inventory command, see Command Line Interface Reference. 8. Deploy reports. After the technology pack installation completes, the rules for the new device are automatically loaded into the database. The inventory process uses those rules to group elements and subelements.
Configuring Secure File Transfer support in Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack If you want to use Secure File Transfer, OpenSSH must be configured for key-based authentication when you connect from the Tivoli Netcool Performance Manager account on the client (the host that is running the Tivoli Netcool Performance Manager process that must use SFTP) to the account on the server.
52 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
Chapter 8. Upgrading the technology pack Describes how to upgrade Alcatel-Lucent 5620 SAM 2.14.0.0 Technology Pack and Alcatel-Lucent 5620 SAM LogToFile 2.2.0.0 Technology Pack to Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack. Upgrading the Alcatel-Lucent 5620 SAM 2.14.0.0 Technology Pack to Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 You can upgrade the Alcatel-Lucent 5620 SAM 2.14.0.0 Technology Pack to Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0.
4. 5. 6. 7. 8. 9. v /opt/proviso/datachannel/log rm –rf *log Create backup of the DataChannel directories and do not delete them from the original location except UBA directories. Install the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack. For more information, see “Installing the technology pack by using the launchpad” on page 40. Copy the core patches to/opt/proviso/datachannel/state. Start the Topology Editor and load the technology pack from the JAR file.
4. Click the Collection tab. 5. From the Formulas pane, expand the following group: AP > Specific > Alcatel > 5620 SAM > Bulk > Equipment > InterfaceAdditionalStats > timeCaptured 6. Right-click timeCaptured, select Apply as filter, and click Refresh. The metrics are displayed in the pane for the timeCaptured filter. 7. Right-click within the pane and click Select All. All the metrics are selected. 8. Right-click within the pane and click Remove Selection. 9.
v /opt/proviso/datachannel/state rm –rf *pid rm -rf *_visual 3. 4. 5. 6. 7. v /opt/proviso/datachannel/log rm –rf *log Create backup of the DataChannel directories and do not delete them from the original location. Install the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack. For more information, see “Installing the technology pack by using the launchpad” on page 40. Copy the core patches to/opt/proviso/datachannel/state. Start the Topology Editor and load the technology pack from the JAR file.
Chapter 9. Setting up the Alcatel-Lucent 5620 SAM servers to support LogToFile The SAM server administrator must set up the appropriate SAM servers environment so that the Alcatel-Lucent SAM 5620 LogToFile Technology Pack operates correctly. About this task Setting up the Alcatel-Lucent 5620 SAM servers includes the following tasks: Install SAM on the primary and redundant servers The SAM server administrator must have installed SAM on primary and redundant servers.
Configure the SAM accounting and polling statistics Accounting policies are relevant 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 inventory is collected, Tivoli Netcool Performance Manager learns the accounting policy for each Access Interface. From these accounting policies, the Alcatel-Lucent 5620 SAM LogToFile Technology Pack can determine the accounting policy type.
Similarly, the service.ServiceIngressOctetsLogRecord class and the service.ServiceIngressPacketsLogRecord class are mutually exclusive. You cannot collect metrics for both classes at the same time. The SAM server 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 servers.
Table 2. MIBs to enable for SAM statistics classes (continued) SAM statistics class MIB Object types aosqos.QoSIngressPolicyStatsLogRecord ALCATEL-IND1QOS-MIB alaQoSRuleEntry equipment.CardHealthStatsLogRecord ALCATEL-IND1HEALTH-MIB healthModuleEntry Setting up ping tests The SAM server enables SAM server administrators to run ping tests to receive information about traffic latency and jitter. The results from the tests can include SAM statistics such as round-trip time, one-way trip time, jitter.
NE Schedulable option and set the Test Result Storage to Both Database and File. Make sure the tests run without errors. v Add the ping tests to the test suite. v Create a schedule to run the test suite. Set the schedule to run at the same frequency as the Tivoli Netcool Performance Manager collection requests for jitter and latency. For example, if Tivoli Netcool Performance Manager collection requests occur every 15 minutes, then set the schedule to run the ping test suite every 15 minutes.
62 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
Chapter 10. Modifying the collection strategy Describes how to modify the amount of data that is managed by the Alcatel-Lucent 5620 SAM LogToFile Technology Pack. You can modify by changing the types of data that are collected, or by changing the collection period for the SAM statistics, or both. Specifying what inventory and metrics to collect The types of inventory and metrics that must be collected from SAM server is specified in the configuration files.
It is the simple way to filter out all records of class equipment.PhysicalPort. Configuring multiple UBA collectors instances Partitioning The UBA partitioning involves two configuration files: 1. collector_lookup.csv 2. collector_mapping.csv collector_lookup.csv The name of the filter file is collector_lookup.csv, and has the configuration level as User. No match for this file is not available. This file is used to specify the number of UBAs that are available in the environment, and the type of each UBA.
Class Family Possible family classes are as follows: v 5620_SAM_AingrAengrQueue v 5620_SAM_Aosqos_Policy v 5620_SAM_BaseCard v 5620_SAM_CardSlot v 5620_SAM_CfmEthTest v 5620_SAM_CfmOneWayDelay v 5620_SAM_CfmTwoWayDelay v 5620_SAM_CfmSingleEndedLoss v 5620_SAM_Channel v 5620_SAM_ControlProcessor v 5620_SAM_DaughterCard v 5620_SAM_DHCP6_Address v 5620_SAM_DS1_E1 v 5620_SAM_Hw_Environment v 5620_SAM_IMALink v 5620_SAM_ISA_Mda v 5620_SAM_ISA_Member v 5620_SAM_LAGInterface v 5620_SAM_MCMCard v 5620_SAM_MME v 56
balance. However, this configuration does not overwrite mapping that the Job gathers from Proviso. Therefore, following is the partition rule: Mapping from Priviso DB → collector_mapping.csv → Job key hash.
frequency, then you must increase the collection period for all the metrics classes. However, you must ensure that you have adequate machine resource. WINDOW_PERIOD is measured in seconds. The values are 900 (default) and 300 for 15-Minutes and 5-Minutes periods respectively. However, on special mix period, you must set the value at 900 (15 Minutes) WAVE_PERIOD is an internal window sliding period that is measured in seconds. This value must be non-zero integer, and a denominator value for WINDOW_PERIOD.
Tivoli Netcool Performance Manager 1.3.2 settings The Alcatel-Lucent 5620 SAM LogToFile Technology Pack supplies these parameters that are based on the Tivoli Netcool Performance Manager platforms. These parameters are supplied in the pack XSD file. You specify values for these parameters as part of adding a UBA Bulk Collector and associating it with the Alcatel-Lucent SAM 5620 LogToFile Technology Pack.
v v v v v equipment.SystemCpuMonStats equipment.SystemCpuStatsLogRecord equipment.SystemMemoryStatsLogRecord ethernetequipment.AggrMaintRxStats ethernetequipment.AggrMaintTxStats v v v v v v v ethernetequipment.Dot3StatsLogRecord ethernetoam.CfmEthTest ethernetoam.CfmLoopback ethernetoam.CfmOneWayDelayTest ethernetoam.CfmTwoWayDelayTest ethernetoam.Mep icmp.IcmpPing v v v v v v ies.L3AccessInterface ies.ServiceAccessPoint ipipe.L2AccessInterface lag.Interface lte.S11AgwPeerStats lte.S11Peer v lte.
v v v v v radioequipment.PdhFrameHopHistoryDataStats15Min radioequipment.PdhFrameLinkHistoryDataStats15Min radioequipment.RadioAnalogueMeasure rtr.RouteStatsLogRecord rtr.VirtualRouter v v v v v v v sasqos.AccessIngress sasqos.Meter sasqos.PortAccessEgress sasqos.PortAccessEgressQueue service.CombinedNetworkEgressOctetsLogRecord service.CombinedNetworkIngressOctetsLogRecord service.CompleteServiceEgressPacketOctetsLogRecord v v v v v v service.CompleteServiceIngressPacketOctetsLogRecord service.
Classes that are disabled v v v v equipment.DigitalDiagnosticMonitoring ethernetoam.CfmEthTestResult ethernetoam.CfmOneWayDelayTestResult ethernetoam.CfmSingleEndedLossTestResult v v v v v v v mirror.L2AccessInterface ppp.PppStats sasqos.AccessIngressForwardingClass sasqos.PortAccessEgressForwardingClass service.NetworkEgressPackets service.NetworkIngressPackets service.ServiceEgressOctets v service.ServiceEgressPackets v service.ServiceIngressOctets v v v v v service.ServiceIngressPackets service.
v Remove the dot that is available before Request type. Notice that the dot that was added before findToFile is removed in the following example: findToFile,... equipment.DigitalDiagnosticMonitoring... .registerLogToFile, ... service.NetworkEgressPackets... 72 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
Chapter 11. Troubleshooting Alcatel-Lucent 5620 SAM LogToFile Technology Pack Troubleshooting tips for issues related to Alcatel-Lucent 5620 SAM LogToFile Technology Pack and its related components. Specifying parameter values Several of the tips to tell you to make sure that the correct values were specified for parameters in the deployed topology. You specify the values for these parameters depending on the Tivoli Netcool Performance Manager platform. Tivoli Netcool Performance Manager 1.3.
v The data being processed is “current”: the UBA has 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 retrieved by the SAM server, and read into its database. To get this data, the accounting and file policies must be configured on the SAM server and distributed to the routers. Accounting data is the data collected for services.
If SAM metric files do not exist in the SAM server, complete the following troubleshooting steps: 1. Make sure that an OSS user account is configured. For more information, see “Configure an OSS user account” on page 57. 2. Make sure that the correct values were specified for the SAM.USERNAME and SAM.PASSWORD parameters, as described in “Specifying parameter values” on page 73, based on the Tivoli Netcool Performance Manager platform: Platform Parameter Tivoli Netcool Performance Manager 1.3.
4. Ensure that you have enough disk space. For more information, see “Metrics collection fails due to lack of disk space” 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: 1.
MPR > IMA Link > Error Management Near-End. General Alcatel-Lucent 5620 SAM LogToFile 2.2.0.0 Technology Pack issues These are the general issues for Alcatel-Lucent 5620 SAM LogToFile 2.2.0.0 Technology Pack. Data for the Inbound Errors might not be displayed Symptoms If you run the Packet Health for LAG interface Group report on the Tivoli Integrated Portal, data for the Inbound Errors might not be displayed.
Accounting collectors. The subelement time changes on several unexpected occasions In the Resource Editor, the subelement date must change when: v A subelement is added, updated, or deleted. v JMS event is triggered. However, in the Alcatel-Lucent 5620 SAM LogToFile Technology Pack, the subelement date also changes when: v A full dump file is processed by the UBA even if a subelement is not inserted, updated, or deleted. v Performance or Accounting CSV file is created by DataStage.
Partitioning must be done at the element level Symptoms DataStage collector mapping configuration provides fine level of partitioning at the subelement level. However, some subelements must be configured to the same collector. Because this rule is not verified by the DataStage job, mistakes might be introduced in the relation lookup configuration file. Resolving the problem To avoid this problem, you must create the partition at the element level only.
$ grep "^registerSasLogToFile" ./data/responsexmls.csv | perl -e ’while (<>){m/(.*)<\/fullClassName>/; print $1."\n"}’ | sort | uniq ethernetoam.CfmLoopbackResult ethernetoam.CfmTwoWayDelayTestResult icmp.IcmpPingResult mpls.LspPingResult svt.TunnelPingResult svt.VccvPingResult $ grep "^registerSasLogToFile" ./data/responsexmls.csv | wc -l 222 # Unexpected logs of registerSasLogToFile - you must expect up to 6 lines, which means 6 classes.You notice 222 lines that is not correct.
General IBM InfoSphere Information Server related issues These are the general issues for IBM InfoSphere Information Server that is required for Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack. Troubleshooting IBM InfoSphere Information Server installations You can resolve all installation problems, with this information. For all troubleshooting problems with installation, see http:// publib.boulder.ibm.com/infocenter/iisinfsv/v8r7/topic/ com.ibm.swg.im.iis.productization.iisinfsv.install.
Verifying that the ports are enabled for all the components required for Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack Enabling the ports for all the components that are required for Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack. This is applicable for Apache ActiveMQ also. Symptoms If you cannot access the IBM InfoSphere Information Server server or client components, verify that the component ports are enabled.
Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A.
IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. 86 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.
Printed in USA
