• No se han encontrado resultados

Describes how to configure the Huawei U2000 GPON Technology Pack.

Appendix A, UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later)

Provides UNIX® reference pages for each of the pack-specific UBA parameters supplied with the XSD file for the Huawei U2000 GPON Technology Pack.

Appendix B, Template file (Tivoli Netcool/Proviso pre-v4.4.3 only)

Explains the edits that must be made to the pack-specific UBA parameters delivered in the pack template file.

The Tivoli Netcool/Proviso product suite

Tivoli Netcool/Proviso is made up of the following components:

Tivoli Netcool/Proviso DataMart is a set of management, configuration and troubleshooting GUIs that the Tivoli Netcool/Proviso system administrator uses to define policies and configuration, as well as to verify and troubleshoot operations.

Tivoli Netcool/Proviso DataLoad provides flexible, distributed data collection and data import of SNMP and non-SNMP data to a centralized database.

Tivoli Netcool/Proviso DataChannel aggregates the data collected through Tivoli Netcool/Proviso DataLoad for use by the Tivoli Netcool/Proviso DataView reporting functions. It also processes on-line calculations and detects real-time threshold violations.

Tivoli Netcool/Proviso DataView is a reliable application server for on-demand, web-based network reports.

Tivoli Netcool/Proviso Technology Packs extend the Tivoli Netcool/Proviso system with service-ready reports for network operations, business development, and customer viewing.

Figure 1 shows the different Tivoli Netcool/Proviso modules.

Figure 1: Tivoli Netcool/Proviso modules

IBM provides the following Tivoli Netcool/Proviso documentation:

• Release notes

• Configuration recommendations

Chapter 2: Devices and services

This chapter discusses the following topics:

Overview

This chapter provides a summary of the Huawei U2000 device technology, and the associated bulk input file format, that the Huawei U2000 GPON Technology Pack is designed to support.

Summary of device technology

The Huawei iManager U2000 Unified Network Management System (Huawei U2000) can collect data from several different types of network elements: routers, switches, security devices, access equipment, and PTN equipment, as shown in the following figure.

Topic Page

Overview 3 Summary of device technology 3

Bulk input file formats 4 Bulk adapter design files 5

The Huawei U2000 can store the collected performance data in a database, or as files in a specified directory.

Tivoli Netcool/Proviso technology packs retrieve the data from the files only, not from the database.

Tivoli Netcool/Proviso provides several technology packs to monitor the performance data of Huawei network elements, where each technology pack monitors a different group of data.

The Huawei U2000 GPON Technology Pack shows the metrics that are related to port statistics, line quality and optics module statistics.

Bulk input file formats

The Huawei U2000 communicates with each Huawei element in the network to gather performance data and other statistics. This data is referred to collectively as network health metrics. The Huawei U2000 creates, on a specified regular basis, a bulk input file that contains the network health metrics and other information. This bulk input file is a Comma-Separated Values (CSV) file.

The Universal Bulk Adaptor (UBA) communicates with the Huawei U2000 using the FTP performance northbound interface (NBI) of the Huawei U2000. Bulk input files for a specified time interval are acquired by the UBA script through an FTP process, and then each record in those files is sorted and processed.

The Huawei U2000 GPON Technology Pack supports multiple input files, where each input file contains data for one polling period only.

The Huawei U2000 GPON Technology Pack extracts KPIs from nine indicator groups, where each indicator group file contains data for its KPI type.

The syntax for these bulk input files is discussed in Bulk input file name on page 4.

The Huawei U2000 GPON Technology Pack provides a file that interprets these bulk input files. See Bulk adapter design files on page 5 for more information.

Bulk input file name

Huawei U2000 devices produce CSV files that are named using the following syntax:

PM_IGIndicatorGroupID_DevID_Granularity_Timestamp_SerialNumber.csv where:

IndicatorGroupID specifies the unique identifier of the indicator group.

DevID specifies the unique identifier of the device from which the data was collected.

Granularity specifies the collection granularity, which defines the performance measurement period.

Timestamp specifies the date on which the data was collected. The timestamp format is as follows:

yyyyMMddHHmmZ where:

Chapter 2: Devices and services

SerialNumber specifies the serial number of the file. This value starts at 01.

Example CSV file name:

PM_IG80113_7340032_15_200909180300Z_01.csv

Bulk input file schema

The bulk input file schema is defined as follows:

• The first line provides the indicator group name, the indicator group description, the timestamp, and the number of data records in the file.

• The first six columns on the second line provide the field headers to describe the device ID, device name, resource ID, resource name, collection time, and granularity period.

The collection time should be specified in the following format:

yyyy-MM-dd HH:mm:SS

• The remaining columns provide the field metrics for bulk data collection.

Bulk adapter design files

Tivoli Netcool/Proviso bulk adapters can support several data formats for bulk input files, for example CSV, XML, and binary. The Huawei U2000 produces data in CSV format.

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, each of which handles a specific bulk input file format.

A bulk adapter design file typically can process both inventory and metrics data from the same bulk input file, and provides a function that creates the bulk collection formula names. When the inventory and metrics are located in separate bulk input files, a technology pack developer typically implements several types of bulk adapter design files.

The Huawei U2000 GPON Technology Pack provides the following bulk adapter design files:

• adaptor.js

NOTES

Chapter 3: Supported reports and KPIs

This chapter discusses the following topics:

Overview

The Huawei U2000 GPON Technology Pack supplies a set of reports to display information about the devices and activity associated with the Huawei U2000 environment.

The reports contain metrics that are generated by the formulas that this technology pack provides. The metric names are the same as the names of the formulas that generate them. For information about a metric that is listed for a particular report, see the description of the associated formula in the Collection Formulas section of the IBM Tivoli Netcool/Proviso Huawei U2000 GPON 2.1.0.0 Technology Pack Reference.

For information about how to navigate to a particular report on the DataView portal, see the NOC Reporting tree in the Subelement Groups section of the IBM Tivoli Netcool/Proviso Huawei U2000 GPON 2.1.0.0 Technology Pack Reference. This chapter provides information about deployed reports only.

For information about understanding report types, creating reports, configuring reports, viewing and working with reports, and deploying reports, see the IBM Tivoli Netcool/Proviso DataView User’s Guide. This Technology Pack User Guide assumes an understanding of the report-related topics discussed in the IBM Tivoli Netcool/Proviso DataView User’s Guide.

Reporter sets

A reporter set contains a group of reporters that together provide information about a specific technology or vendor device. Technology pack developers use the Reporter Set Wizard to choose the type of template on which to base the reporter set. Technology packs use reporter sets as the framework for defining reports.

The Huawei U2000 GPON Technology Pack reports display, on a Web portal, the collected information about the devices and technologies that operate in the Huawei U2000 environment.

Topic Page

Overview 7 Reporter sets 7

Reporter set tree 8

Reporter set contents 9

Key performance indicators 19

Table 1 shows a summary of the reports in each reporter set provided by the Huawei U2000 GPON Technology Pack.

See the IBM Tivoli Netcool/Proviso DataView User’s Guide for more information about reporter sets and the Reporter Set Wizard.

Reporter set tree

The Huawei U2000 GPON Technology Pack provides the following reporter sets, which are listed as they appear in the DataView Navigator tree structure:

Huawei U2000 GPON

OLT NNI Port

OLT UNI Port

ONT Ethernet Port

ONT GEM Port

ONT Optical Port Table 1: Reporter set summary

Reporter set Dashboard Group Resource Detail Threshold TopN

OLT NNI Port 0 1 1 1 0 0

OLT UNI Port 0 2 2 3 0 1

ONT Ethernet Port 0 1 1 2 0 0

ONT GEM Port 0 1 1 1 0 0

ONT Optical Port 0 3 3 3 0 1

TOTALS 0 8 8 10 0 2

Chapter 3: Supported reports and KPIs

Reporter set contents

This section describes the contents of the reporter sets provided in the Huawei U2000 GPON Technology Pack.

For each report it includes the key performance indicators (KPIs) and their Indicator IDs.

OLT NNI Port

NNI Traffic Summary - GST

KPIs

• Received GEM Frames [101955]

• Received PLOAM Frames [101953]

• Received Ethernet Frames [101957]

• Sent OMCI Frames [101952]

• Sent GEM Frames [101956]

• Sent PLOAM Frames [101954]

• Sent Ethernet Frames [101958]

• Received OMCI Frames [101951]

NNI Traffic Summary - RST

KPIs

• Received GEM Frames [101955]

• Received PLOAM Frames [101953]

• Received Ethernet Frames [101957]

• Sent OMCI Frames [101952]

• Sent GEM Frames [101956]

• Sent PLOAM Frames [101954]

• Sent Ethernet Frames [101958]

• Received OMCI Frames [101951]

NNI Traffic Summary - DC

KPIs

• Received GEM Frames [101955]

• Received PLOAM Frames [101953]

• Received Ethernet Frames [101957]

• Sent OMCI Frames [101952]

• Sent GEM Frames [101956]

• Sent PLOAM Frames [101954]

• Sent Ethernet Frames [101958]

• Received OMCI Frames [101951]

Charts

• Received PLOAM Frames [101953]

• Sent GEM Frames [101956]

• Sent Ethernet Frames [101958]

• Received GEM Frames [101955]

• Received Ethernet Frames [101957]

• Sent PLOAM Frames [101954]

• Sent OMCI Frames [101952]

• Received OMCI Frames [101951]

OLT UNI Port

UNI GTC Traffic Summary - GST

KPIs

• Sent PLOAM Frames [100994]

• Received PLOAM Frames [100990]

• Received OMCI Frames [100989]

• Sent OMCI Frames [100993]

• Sent GEM Frames [100992]

• Received GEM Frames [100988]

Chapter 3: Supported reports and KPIs

• Received Multicast Frames [100958]

• Received Broadcast Frames [100957]

• Received Frames [100954]

• Received Unicast Frames [100959]

• Sent Multicast Frames [100973]

• Sent Average Throughput [100983]

UNI GTC Traffic Summary - RST

KPIs

• Sent PLOAM Frames [100994]

• Received PLOAM Frames [100990]

• Received OMCI Frames [100989]

• Sent OMCI Frames [100993]

• Sent GEM Frames [100992]

• Received GEM Frames [100988]

UNI Ethernet Traffic Summary - RST

KPIs

• Sent Broadcast Frames [100972]

• Sent Unicast Frames [100974]

• Sent Frames [100955]

• Received Average Throughput [100968]

• Received Multicast Frames [100958]

• Received Broadcast Frames [100957]

• Received Frames [100954]

• Received Unicast Frames [100959]

• Sent Multicast Frames [100973]

• Sent Average Throughput [100983]

UNI Ethernet Traffic Summary - Top5

KPIs

• Received Average Throughput [100968]

• Sent Average Throughput [100983]

Charts

• Received Average Throughput [100968]

• Sent Average Throughput [100983]

UNI GTC Traffic Summary - DC

KPIs

• Sent PLOAM Frames [100994]

• Received PLOAM Frames [100990]

• Received OMCI Frames [100989]

• Sent OMCI Frames [100993]

• Sent GEM Frames [100992]

• Received GEM Frames [100988]

Charts

• Received PLOAM Frames [100990]

• Sent OMCI Frames [100993]

• Received OMCI Frames [100989]

• Received GEM Frames [100988]

• Sent PLOAM Frames [100994]

• Sent GEM Frames [100992]

UNI Ethernet Traffic Summary Received - DC

KPIs

• Received Average Throughput [100968]

• Received Multicast Frames [100958]

• Received Broadcast Frames [100957]

• Received Frames [100954]

• Received Unicast Frames [100959]

Charts

• Received Frames [100954]

• Received Average Throughput (kbps) [100968]

• Received Multicast Frames [100958]

• Received Unicast Frames [100959]

• Received Broadcast Frames [100957]

UNI Ethernet Traffic Summary Sent - DC

Chapter 3: Supported reports and KPIs

Charts

• Sent Unicast Frames [100974]

• Sent Multicast Frames [100973]

• Sent Broadcast Frames [100972]

• Sent Average Throughput (kbps) [100983]

• Sent Frames [100955]

• Received Unicast Frames [101050]

• Sent Multicast Frames [101053]

• Received Broadcast Packets [101016]

• Sent Broadcast Frames [101052]

• Received Multicast Packets [101017]

• Sent Unicast Frames [101051]

Ethernet Traffic Summary - RST

KPIs

• Received Packets [101015]

• Received Frames [101024]

• Received Unicast Frames [101050]

• Sent Multicast Frames [101053]

• Received Broadcast Packets [101016]

• Sent Broadcast Frames [101052]

• Received Multicast Packets [101017]

• Sent Unicast Frames [101051]

Ethernet Traffic Summary Packet - DC

KPIs

• Received Packets [101015]

• Received Broadcast Packets [101016]

• Received Multicast Packets [101017]

Charts

• Received Packets [101015]

• Received Broadcast Packets [101016]

• Received Multicast Packets [101017]

Ethernet Traffic Summary Frame - DC

KPIs

• Received Frames [101024]

• Received Unicast Frames [101050]

• Sent Multicast Frames [101053]

• Sent Broadcast Frames [101052]

• Sent Unicast Frames [101051]

Charts

• Sent Unicast Frames [101051]

• Received Frames [101024]

• Sent Multicast Frames [101053]

• Sent Broadcast Frames [101052]

• Received Unicast Frames [101050]

ONT GEM Port

GEM Traffic Summary - GST

KPIs

• Received Frames [101012]

• Received Blocks [101013]

• Sent Blocks [100879]

• Received Severe Error Blocks [100880]

• Frames Loss [101010]

GEM Traffic Summary - RST

KPIs

Chapter 3: Supported reports and KPIs

GEM Traffic Summary - DC

KPIs

• Received Frames [101012]

• Received Blocks [101013]

• Sent Blocks [100879]

• Received Severe Error Blocks [100880]

• Frames Loss [101010]

Charts

• Frames Loss [101010]

• Received Blocks [101013]

• Received Frames [101012]

• Received Severe Error Blocks [100880]

• Sent Blocks [100879]

ONT Optical Port

Optics Module Summary - GST

KPIs

• Optics Temperature Selector [100881]

• Optics Bias Current Selector [100882]

• Optics TxPower Selector [100883]

• Optics RxPower Selector [100884]

• Optics Supply Voltage [100885]

Line Quality Summary - GST

KPIs

• Downstream BIP Error Frames [100987]

• Upstream Scape Error Frames [100985]

• Upstream BIP Error Frames [100986]

Optical Traffic Summary - GST

KPIs

• Down Frames [101005]

• Up Frames [101004]

• Up Discard Frames [101008]

• Down Discard Frames [101009]

• Up Average Throughput [101006]

• Down Average Throughput [101007]

Optics Module Summary - RST

KPIs

• Optics Temperature Selector [100881]

• Optics Bias Current Selector [100882]

• Optics TxPower Selector [100883]

• Optics RxPower Selector [100884]

• Optics Supply Voltage [100885]

Line Quality Summary - RST

KPIs

• Downstream BIP Error Frames [100987]

• Upstream Scape Error Frames [100985]

• Upstream BIP Error Frames [100986]

Optical Traffic Summary - RST

KPIs

• Down Frames [101005]

• Up Frames [101004]

• Up Discard Frames [101008]

• Down Discard Frames [101009]

• Up Average Throughput [101006]

• Down Average Throughput [101007]

Chapter 3: Supported reports and KPIs

Optics Module Summary - DC

KPIs

• Optics Temperature Selector [100881]

• Optics Bias Current Selector [100882]

• Optics TxPower Selector [100883]

• Optics RxPower Selector [100884]

• Optics Supply Voltage [100885]

Charts

• Optics RxPower Selector (dBm) [100884]

• Optics TxPower Selector (dBm) [100883]

• Optics Bias Current Selector (mA) [100882]

• Optics Temperature Selector (C) [100881]

• Optics Supply Voltage (mV) [100885]

Line Quality Summary - DC

KPIs

• Downstream BIP Error Frames [100987]

• Upstream Scape Error Frames [100985]

• Upstream BIP Error Frames [100986]

Charts

• Upstream BIP Error Frames [100986]

• Downstream BIP Error Frames [100987]

• Upstream Scape Error Frames [100985]

Optical Traffic Summary - DC

KPIs

• Down Frames [101005]

• Up Frames [101004]

• Up Discard Frames [101008]

• Down Discard Frames [101009]

• Up Average Throughput [101006]

• Down Average Throughput [101007]

Charts

• Up Average Throughput (kbps) [101006]

• Down Discard Frames [101009]

• Up Discard Frames [101008]

• Up Frames [101004]

• Down Frames [101005]

• Down Average Throughput (kbps) [101007]

Optical Traffic Summary - Top5

KPIs

• Up Average Throughput [101006]

• Down Average Throughput [101007]

Charts

• Up Average Throughput (kbps) [101006]

• Down Average Throughput (kbps) [101007]

Chapter 3: Supported reports and KPIs

Key performance indicators

Table 2 lists all of the key performance indicators (KPIs) supported by the Huawei U2000 GPON Technology Pack.

Table 2: Key performance indicators

KPI Comment

Down Average Throughput [101007] Downstream average throughput.

Down Discard Frames [101009] Downstream discard frames.

Down Frames [101005] Downstream total frames.

Downstream BIP Error Frames [100987] Downstream BIP error frames.

Frames Loss [101010] Count of the frames loss.

Optics Bias Current Selector [100882] Optical bias current selector.

Optics RxPower Selector [100884] Optical receive power selector.

Optics Supply Voltage [100885] Optical supply voltage.

Optics Temperature Selector [100881] Optical temperature selector.

Optics TxPower Selector [100883] Optical transmit power selector.

Received Average Throughput [100968] Received average throughput.

Received Blocks [101013] Count of the received blocks.

Received Broadcast Frames [100957] Received broadcast frames.

Received Broadcast Packets [101016] Received broadcast packets.

Received Ethernet Frames [101957] Received ethernet frames.

Received Frames [100954] Received total frames.

Received Frames [101012] Count of the received frames.

Received Frames [101024] Received total frames.

Received GEM Frames [100988] Received GEM frames.

Received GEM Frames [101955] Received GEM frames.

Received Multicast Frames [100958] Received multicast frames.

Received Multicast Packets [101017] Received multicast packets.

Received OMCI Frames [100989] Received OMCI frames.

Received OMCI Frames [101951] Received OMCI frames.

Received PLOAM Frames [100990] Received PLOAM frames.

Received PLOAM Frames [101953] Received PLOAM frames.

Received Packets [101015] Received total packets.

Received Severe Error Blocks [100880] Count of the received severe error blocks.

Received Unicast Frames [100959] Received unicast frames.

Received Unicast Frames [101050] Received unicast frames.

Sent Average Throughput [100983] Send average throughput.

Sent Blocks [100879] Count of the transmitted blocks.

Sent Broadcast Frames [100972] Sent broadcast frames.

Sent Broadcast Frames [101052] Sent broadcast frames.

Sent Ethernet Frames [101958] Sent ethernet frames.

Sent Frames [100955] Sent total frames.

Sent GEM Frames [100992] Sent GEM frames.

Sent GEM Frames [101956] Sent GEM frames.

Sent Multicast Frames [100973] Sent multicast frames.

Sent Multicast Frames [101053] Sent multicast frames.

Sent OMCI Frames [100993] Sent OMCI frames.

Sent OMCI Frames [101952] Sent OMCI frames.

Sent PLOAM Frames [100994] Sent PLOAM frames.

Sent PLOAM Frames [101954] Sent PLOAM frames.

Sent Unicast Frames [100974] Sent unicast frames.

Sent Unicast Frames [101051] Sent unicast frames.

Up Average Throughput [101006] Upstream average throughput.

Up Discard Frames [101008] Upstream discard frames.

Up Frames [101004] Upstream total frames.

Upstream BIP Error Frames [100986] Upstream BIP error frames.

Upstream Scape Error Frames [100985] Upstream scape error frames.

Table 2: Key performance indicators

KPI Comment

Chapter 4: Configuring the technology pack

This chapter explains how to configure the Huawei U2000 GPON Technology Pack and consists of the following topics:

Overview

The Huawei U2000 GPON Technology Pack is a bulk or Universal Bulk Adaptor (UBA) technology pack. Bulk technology packs collect data against non-SNMP devices, and rely on the UBA of the Tivoli Netcool/Proviso DataChannel to process the data. Prior to Tivoli Netcool/Proviso version 4.4.3, bulk packs could be very difficult to configure, and in many cases required extensive Tivoli Netcool/Proviso domain knowledge.

Tivoli Netcool/Proviso version 4.4.3 introduced a GUI to configure Tivoli Netcool/Proviso UBA technology packs on supported Tivoli Netcool/Proviso platforms.

Before you begin

Before configuring the Huawei U2000 GPON Technology Pack, ensure that you:

• Have the following software and documentation for your version of Tivoli Netcool/Proviso:

— Release notes for the current technology pack release.

— IBM Tivoli Netcool/Proviso Installation Guide.

— IBM Tivoli Netcool/Proviso Upgrade Guide (if performing an upgrade).

— IBM Tivoli Netcool/Proviso DataMart Configuration Guide.

Important: Refer to this guide to run a bulk inventory profile.

— Access to the Tivoli Netcool/Proviso DataMart server.

— An X Window server on the DataMart server.

Note: (Tivoli Netcool/Proviso pre-v4.4.3) If there is no graphics card on the DataMart server, you can install the Xvfb virtual frame buffer package to provide X Window services, as described in the IBM Tivoli Netcool/Proviso Installation Guide.

— Access to the SilverStream server.

— Access to the DataChannel server.

Topic Page

Overview 21 Before you begin 21 Configure the technology pack 22

• Have completed the following tasks:

— Reviewed the release notes for the current technology pack.

Important: 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 version of the Tivoli Netcool/Proviso components, as described in the IBM Tivoli Netcool/Proviso Installation Guide.

— Installed the Huawei U2000 GPON Technology Pack.

Note: Installation instructions for a technology pack can be found in the Appendices of the IBM Tivoli Netcool/Proviso Installation Guide (covers core and technology packs).

Upgrade instructions for a technology pack can be found in Chapter 3 of the IBM Tivoli Netcool/Proviso Upgrade Guide (covers core and technology packs).

Localization is done automatically during installation of the technology pack.

— Configured at least one DataChannel.

— Configured a UBA bulk collector subchannel.

— Created a user on the Huawei U2000 server with permission to ftp and delete files.

Configure the technology pack

To configure the Huawei U2000 GPON Technology Pack, follow these steps:

1. Load the DataMart environment.

To load the shell with the DataMart environment, follow these steps:

1-a. Log in to the DataMart server as pvuser.

1-b. Change your working directory to the DataMart home directory (/opt/datamart, by default), using the following command:

cd /opt/datamart

1-c. Load the shell with the DataMart environment, by sourcing the dataMart.env file, as follows:

. /opt/datamart/dataMart.env

Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set.

2. Copy technology-specific files from the DataMart server to the DataChannel server.

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 server, in a typical installation

Chapter 4: Configuring the technology pack

2-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

2-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