Sie sind auf Seite 1von 73

CA ® eHealth ®

Integration for Alcatel User Guide

r6.1

CA ® e Health ® Integration for Alcatel User Guide r6.1

This documentation and any related computer software help programs (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies.

The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user’s applicable license agreement.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227- 7014(b)(3), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2008 CA. All rights reserved.

CA Product References

This document references the following CA product:

CA eHealth ® (eHealth)

CA eHealth ® Integration for Alcatel (eHealth – Alcatel)

Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.

Contents

Contents Chapter 1: Introducing the Integration 9 Integration Overview 9 How to Set Up and Install
Contents Chapter 1: Introducing the Integration 9 Integration Overview 9 How to Set Up and Install

Chapter 1: Introducing the Integration

9

Integration Overview

9

How to Set Up and Install the Integration

10

Setup Program

11

System Requirements

11

eHealth – Alcatel System Setup Prerequisites

11

eHealth Configuration Prerequisites

12

How to Configure Alcatel 5620 NM Systems

13

Verify the NM Version

14

How to Create a QCnetwork User Account for eHealth

15

Restart an Alcatel QC Network to Close the Connection

18

How to Enable Statistics Collection

18

Setup Checklists

19

Required Licenses

19

How to License eHealth – Alcatel

20

Statistics Polling Status

20

Import Polling Status

20

Discovery of Polled Elements

21

Chapter 2: Setting Up the Integration

23

eHealth – Alcatel Setup Program

23

Run the eHealth – Alcatel Setup Program

24

Upgrade Option for Elements

25

Installation Log

25

How the Configuration Process Works

25

Element Configuration Tasks

27

Add or Reconfigure Alcatel Elements

28

Group, Modify, and Exclude Elements

28

nhConfig Command – Updates the Poller Configuration

29

Tips for Using nhConfig Arguments

31

LAN/WAN Group Configuration

32

Disable Default LAN/WAN Grouping

34

Schedule the Configuration Process

34

Data Modification in the Poller Configuration

36

Modify or Delete Elements in the Poller Configuration

37

Files Used to Configure Elements

38

Element Files

38

Index Values for Alcatel Elements

39

Element Definition Examples

40

Chapter 3: Using the Integration

43

How the Statistics Import Process Works

43

How eHealth Imports Raw Statistics

44

Statistics Data Files

45

Stop the Import Process

45

Change the Import Polling Interval

46

Supported eHealth Reports

46

Availability, Latency, and Reachability

47

Guidelines for Scheduling Reports

47

Unsupported Reports and Charts

47

Chapter 4: Troubleshooting the Integration

49

Installation Problems

49

Version Error

49

Invalid License Error

50

Configuration Problems

50

Cannot Connect to the NM

50

eHealth Cannot Log In to the NM

52

Configuration Process Occupies QCnetwork API Resources

53

Login Retries Exceed Number Permitted

53

CIR/SIR/speed Error

54

Polling Problems

55

Cannot Connect to the NM to Import Statistics

56

Problems Importing Statistics for Elements

58

Missing Elements

60

No Data in Reports

60

No Data for Elements

60

FastBUS Elements Not Imported or Polled

61

Missing Statistics Data

61

Missing Performance Variables

62

Data Gaps in eHealth Reports

63

Appendix A: Setup Checklists

67

Alcatel 5620 NM System Checklist

67

QCnetwork Checklist

68

eHealth System Checklist

69

Index

71

Chapter 1: Introducing the Integration

Chapter 1: Introducing the Integration This section contains the following topics: Integration Overview (see page 9
Chapter 1: Introducing the Integration This section contains the following topics: Integration Overview (see page 9

This section contains the following topics:

Integration Overview (see page 9) How to Set Up and Install the Integration (see page 10) Setup Program (see page 11) System Requirements (see page 11) How to Configure Alcatel 5620 NM Systems (see page 13) Setup Checklists (see page 19) Required Licenses (see page 19) How to License eHealth – Alcatel (see page 20)

Integration Overview

The Alcatel 5620 Network Manager (NM) collects configuration information and statistics data for Alcatel Frame Relay and ATM devices in your infrastructure. eHealth – Alcatel enables your eHealth system to collect this data from the Alcatel 5620 NM system. You can then run LAN/WAN At-a-Glance, Top N, Trend, and Health reports on this data.

eHealth – Alcatel does the following:

Extracts configuration information from the Alcatel 5620 NM and transfers this information to the eHealth system.

Creates LAN/WAN groups for similar element types in partitions that the Alcatel NM user can view.

Adds or updates LAN/WAN groups as needed, if you use rules files.

Updates the eHealth poller configuration, database, and groups with the configuration information.

Collects raw statistics from the Alcatel 5620 NM and enables eHealth to import them.

This guide describes how to install, configure, and use the eHealth Integration for Alcatel module (eHealth – Alcatel).

How to Set Up and Install the Integration

How to Set Up and Install the Integration

Before you set up eHealth – Alcatel, review the tasks described in this section and complete the setup checklists that you will use during the setup procedure. You can then start eHealth and license eHealth – Alcatel to access and run the setup program. Then you must configure your Alcatel elements, which represent the Alcatel network devices (such as switches and routers) for which eHealth collects and analyzes data to generate reports.

To set up and use eHealth – Alcatel, you must do the following:

1. Install eHealth on one or more dedicated Solaris systems.

Note: For more information, see the eHealth Installation Guide.

2. Make sure that the Alcatel 5620 NM is properly installed and configured.

Note: For more information, see your Alcatel documentation.

3. Verify that you meet the eHealth and Alcatel system requirements.

Note: For more information, see the eHealth Integration Modules Release Notes.

4. Complete the setup checklists in the appendix.

5. License the integration module.

6. Run the eHealth – Alcatel setup program on each eHealth system that you want to use to report on your Alcatel elements.

7. Extract configuration information from the Alcatel 5620 NM and update the eHealth poller configuration, database, and groups.

More information:

How to License eHealth – Alcatel (see page 20)

How the Statistics Import Process Works (see page 43)

Setup Program

Setup Program

The setup program does the following:

Collects information about active and standby Alcatel 5620 NM systems.

Installs one configuration file on each Alcatel 5620 NM system (both active and standby systems) in your infrastructure.

Upgrades any existing Alcatel elements that reside in the eHealth database. (This upgrade is optional.)

Note: Alcatel elements were formerly named Newbridge.

Configures the eHealth import interval.

QCnetwork is the application programming interface (API) that enables an application to communicate with the Alcatel 5620 NM.

You can configure both a primary (active) Alcatel 5620 NM and a secondary (standby) Alcatel 5620 NM. If eHealth cannot connect to the primary Alcatel 5620 NM, it automatically connects to the secondary NM.

System Requirements

eHealth - Alcatel is supported on Solaris operating systems only.

Note: For information about version support for eHealth and the Alcatel 5620 NM system, see the eHealth Integration Modules Release Notes.

eHealth – Alcatel System Setup Prerequisites

The following are required for your eHealth – Alcatel system:

Sun Solaris operating system

eHealth – Alcatel license

Supported version of Alcatel 5620 Network Manager

Note: For information about the latest versions that support eHealth – Alcatel, see the eHealth Integration Modules Release Notes.

System Requirements

The following are required for your Alcatel 5620 NM system:

Alcatel QCnetwork Services

Alcatel QCnetwork API user account configured for exclusive use by eHealth

Make sure that you create the QCnetwork User Account (see page 16).

Alcatel Statistics Collector software

You must do the following for your eHealth – Alcatel system:

Synchronize the time on the Alcatel 5620 NM system to within one minute of the time on the eHealth system before you set up eHealth – Alcatel.

If you plan to use Secure FTP, configure it on your eHealth system and the Alcatel 5620 NM host.

Note: For information about setting up Secure FTP on your NM host, see your Alcatel documentation.

Enable statistics collection for each element on which you want to report.

Make sure that you set the shell environment to C.

In addition to these requirements, the eHealth system and the Alcatel 5620 NM system have configuration and operational requirements.

More information:

How to License eHealth – Alcatel (see page 20)

How to Enable Statistics Collection (see page 18)

How to Configure Alcatel 5620 NM Systems (see page 13)

eHealth Configuration Prerequisites

You should install eHealth on a dedicated system instead of on the system where you are running the Alcatel 5620 NM. If you must install both applications on the same system, however, make sure that the system has sufficient disk space, swap space, and shared memory to run both applications.

If you run eHealth – Alcatel on multiple eHealth systems, note the following:

You can configure multiple eHealth systems to extract information from a single Alcatel 5620 NM system.

You cannot configure a single eHealth system to extract information from multiple Alcatel 5620 NM systems.

How to Configure Alcatel 5620 NM Systems

How to Configure Alcatel 5620 NM Systems

To help ensure that the Alcatel 5620 NM is set up properly for use with eHealth – Alcatel, you must do the following:

1. Verify the NM version number.

2. Create a QCnetwork user account for eHealth.

3. Enable statistics collection for each element.

4. Set the shell environment to C on each Alcatel 5620 NM from which eHealth systems collect data.

The Telnet connection between eHealth and the NM requires the C shell environment.

5. Open the following CORBA ports in the firewall on the NM side to establish normal interaction with eHealth:

8248 – CORBA naming service port

8264 – QC_network service on the NM system

How to Configure Alcatel 5620 NM Systems

Verify the NM Version

You must verify the version number of your Alcatel 5620 NM to make sure that you are using the version of the NM that eHealth – Alcatel supports.

Note: For information about the supported Alcatel 5620 Network Manager versions, see the eHealth Integration Modules Release Notes.

To obtain the version number of the Alcatel 5620 NM

1. Locate the 46230_VERSION file in the /opt/netmgt/stats/bin directory on the Alcatel 5620 NM.

A list of alphanumeric characters appears.

2. Convert the first entry in this file to the version number as shown in the following example:

Example: Convert the Version Number

This example assume that the number SBN214-H3-00 is the first entry in the 46230_VERSION file. Convert this number to the version number as shown in the following diagram and corresponding steps.

as shown in the following diagram and corresponding steps. a. Identify the major revision number, which

a. Identify the major revision number, which is located in the sixth field within the entry. (In the previous example, the major revision number is 4.)

b. Identify the minor revision number is one number less than the number that follows the first three letters in the entry. (In the previous example, the minor revision number is 1.)

c. Identify the hardness level is the letter H and the single-digit number that follows it. (In the example, the hardness level is H3.)

The resulting version number in this example is 4.1 H3, which contains a major revision number followed by a minor revision number and a hardness number.

The version number is determined and you can verify that the version number is supported by comparing the resulting version number in the eHealth Integration Modules Release Notes.

How to Configure Alcatel 5620 NM Systems

How to Create a QCnetwork User Account for eHealth

eHealth must have at least one QCnetwork user account to connect to the QCnetwork server. This account contains information about the cache size, event buffer queue size, and maximum number of concurrent sessions allowed for eHealth. It also grants access to the appropriate Alcatel 5620 NM partitions.

Note: eHealth can also have multiple user accounts that connect to the same QCnetwork server. Users with a valid user name and password can create multiple, simultaneous QCnetwork sessions.

To prepare for and set up this account, do the following:

1. Start the QCnetwork configuration tool on the QCnetwork server system.

2. Create the QCnetwork user account (see page 16) with the create command.

3. Grant eHealth Access to an Alcatel 5620 NM partition (see page 17) by using the add command.

4. Set the maximum number of QCnetwork sessions (see page 17) by using the sessions command.

5. (Optional) Reset the event buffer queue size by using the buffer command.

Note: For more information, see your Alcatel documentation. If you are running a later version of eHealth - Alcatel and QCnetwork, see the appropriate Alcatel documentation for current procedures.

Start the QCnetwork Configuration Tool

You must start the QCnetwork configuration tool to create the QCnetwork account.

Note: For more information about the configuration tool, see your Alcatel documentation.

To start the QCnetwork configuration tool

1. Execute the following command on the system on which your QCnetwork server resides:

cd /opt/netmgt/bin

The directory is changed to /bin.

2. Execute the following command:

QCF_config

How to Configure Alcatel 5620 NM Systems

3. Enter the following information when you are prompted:

QCnetwork server system name

IP address or host name

Operator account name. The default is QCF_config.

Operator account password for the operator account name. The default is mainstreet.

The main QCnetwork configuration menu appears.

When you start this tool from the command-line interface, you must set the LD_LIBRARY_PATH variable so that your system points to the TAO library. If you are using the C shell, add the following line to your .cshrc file:

setenv LD_LIBRARY_PATH“$LD_LIBRARY_PATH”:/opt/netmgt/corba/tao/lib

Create the QCnetwork User Account

When you create a QCnetwork user account you must provide a name and password for the account.

To create the QCnetwork user account

1. Execute the following command in the command line:

create

2. Enter the following information when prompted:

eHealth QCnetwork account name

Password for the account name

Confirmation password for the account name

The QCnetwork server displays an error message if the two password entries do not match.

The user account and password are set.

More information:

Alcatel 5620 NM System Setup Prerequisites (see page 11)

How to Create a QCnetwork User Account for eHealth (see page 15)

How to Configure Alcatel 5620 NM Systems

Grant eHealth Access to an Alcatel 5620 NM Partition

You must grant eHealth access to an Alcatel 5620 NM partition for your eHealth account.

To grant eHealth access to an Alcatel partition

1. Execute the following command in the command line:

add

2. Enter the following information when prompted:

eHealth QCnetwork account name to which you want to add a partition

Valid Alcatel 5620 NM partition name

More information:

How to Create a QCnetwork User Account for eHealth (see page 15)

Set the Maximum Number of QCnetwork Sessions

You must set the maximum number of QCnetwork sessions for the eHealth user.

To set the maximum number of concurrent sessions

1. Access the command line and execute the following command:

sessions

2. Enter the client account name of the eHealth QCnetwork account for which you want to set or change the maximum number of concurrent sessions.

The server displays the current value for the maximum number of concurrent sessions.

3. Enter a new value at the new maximum number of concurrent sessions prompt.

Default: 0

Limits: 0 to 32767

More information:

How to Create a QCnetwork User Account for eHealth (see page 15)

How to Configure Alcatel 5620 NM Systems

Restart an Alcatel QC Network to Close the Connection

If you stop an nhAnmGetCfg with Ctrl-C, the connection remains and you must restart your Alcatel QC network to close the connection.

To restart a QC network and close any unused connections, execute the following commands in the command line on an Active NM:

nmsa1% ps -ef | grep QC nmssyssh 1574 897 0 21:12:27 ? 0:52 sbin/QC_network QC_network -ORBEndpoint iiop://localhost:8264 -ORBlnitRef NameService nmsa1% kill Pid QC-network will be restarted. Warning: ppid of pid QC-Network is the NMS ./RED_comms stop/start If you kill ppid (here 412)NMS will be restarted. The Alcatel QCnetwork restarts.

If the commands entered in the previous step do not work, restart NMS ./RED_comms stop and ./RED_comms start (Activity Switch).

How to Enable Statistics Collection

Before you configure eHealth – Alcatel, you must make sure that the Alcatel 5620 NM is collecting statistics for each Frame Relay and ATM element on which you want eHealth to report.

Note: The configuration process does not discover element information for certain ATM circuits by design.

Setup Checklists

To enable eHealth to collect statistics from the NM, you must do the following:

1. Set up read/write access for the following directories on both active and standby Alcatel 5620 NM systems:

/opt/netmgt/stats/format

/opt/netmgt/stats/filter

2. Install the Alcatel 5620 Statistics Collector software on the NM system.

3. Use the List Statistics dialog box on the NM system to enable statistics collection for each element that you want to monitor.

Note: For more information about installing the Statistics Collector software and enabling statistics collection, see your Alcatel documentation. For information about the hardware that eHealth supports for Alcatel Frame Relay and ATM elements and supported statistics, see the eHealth Integration Modules Release Notes.

More information:

How the Configuration Process Works (see page 25)

Setup Checklists

Setup checklists for the Alcatel 5620 NM system, QCnetwork, and eHealth system are available in the appendix. Before installing eHealth – Alcatel, photocopy and complete the checklist for each Alcatel host where you plan to install the software. These checklists help you gather the information that the setup program prompts you for. This information can also be useful for troubleshooting problems that you may encounter after the installation. When you finish installing eHealth – Alcatel, store the checklists with the documentation for future reference.

Required Licenses

The following licenses are required to use your eHealth system with eHealth – Alcatel:

Poller

eHealth – Alcatel

LAN/WAN

Frame Relay (if you want to monitor Frame Relay devices)

ATM (if you want to monitor ATM devices)

How to License eHealth – Alcatel

How to License eHealth – Alcatel

The process for adding licenses is as follows:

When you start eHealth for the first time, you must specify your eHealth, poller, and application licenses.

If you have already been using eHealth, you must specify additional licenses only for eHealth – Alcatel.

After you add licenses for your eHealth – Alcatel system, eHealth does the following:

Updates the console with the appropriate buttons and menu options

Opens one or more polling status windows

Opens the Discover dialog

If you plan to run the eHealth – Alcatel setup program on multiple eHealth systems, you must obtain a license for each system.

Note: For information about adding eHealth licenses, see the eHealth Administration Guide or eHealth Help.

Statistics Polling Status

The Statistics Polling Status window displays information about the statistics poller, which uses Simple Network Management Protocol (SNMP) to poll for data on discovered elements. If you are using your eHealth system to report on Alcatel elements only, you can close this window. eHealth – Alcatel does not use SNMP to import statistics data.

Note: For more information about the Statistics Polling Status window, see the eHealth Administration Guide.

Import Polling Status

The Import Polling Status window displays information about the import poller, which imports statistics from sources such as the Alcatel 5620 NM. This information includes the the time of the next import, the number of records imported, and the number of elements with invalid data or missing statistics.

If you close the Import Polling Status window, you can reopen it at any time by selecting Console, Import Polling Status.

How to License eHealth – Alcatel

During the import process, the Import Polling Status window displays good (green) poll bars on the Imported Records graph to indicate the number of records imported successfully, and bad (red) poll bars on the Missed Polls graph to indicate the number of records that were not imported successfully. The poll bars are updated with each import poll.

Note: If the NM is not accessible at the start of a statistics import, poll bars are not displayed. When the NM becomes available, eHealth – Alcatel attempts to recover any missed statistics data.

You can select Show Messages in the Import Polling Status window to display messages about the import process, such as the names of files that were imported. The Import Polling Status window also displays an error message if the NM has not generated a statistics file for an element in the poller configuration within a given period. By default, eHealth saves these messages in the $NH_HOME/log/pollerStatus/messages.import.log file.

Note: For more information about the Import Polling Status window, see the eHealth Administration Guide. For information about eHealth – Alcatel error messages and how to resolve them, see the troubleshooting chapter in this guide.

Discovery of Polled Elements

You can use the Discover dialog to locate the elements that eHealth polls by using SNMP. Since eHealth – Alcatel does not use SNMP to import statistics from the Alcatel 5620 NM, you can close the Discover dialog.

Note: For more information about the Discover dialog, see the eHealth Administration Guide.

Chapter 2: Setting Up the Integration

Chapter 2: Setting Up the Integration Before you can use eHealth – Alcatel, you must install
Chapter 2: Setting Up the Integration Before you can use eHealth – Alcatel, you must install

Before you can use eHealth – Alcatel, you must install the integration software on the Alcatel NM and configure Alcatel elements in your eHealth poller configuration.

This section contains the following topics:

eHealth – Alcatel Setup Program (see page 23) How the Configuration Process Works (see page 25) Element Configuration Tasks (see page 27) nhConfig Command – Updates the Poller Configuration (see page 29) Tips for Using nhConfig Arguments (see page 31) LAN/WAN Group Configuration (see page 32) Disable Default LAN/WAN Grouping (see page 34) Schedule the Configuration Process (see page 34) Data Modification in the Poller Configuration (see page 36) Modify or Delete Elements in the Poller Configuration (see page 37) Files Used to Configure Elements (see page 38) Element Files (see page 38)

eHealth – Alcatel Setup Program

The eHealth – Alcatel setup program places software on the Alcatel NM. This software enables eHealth to collect configuration information and raw statistics data.

You cannot set up eHealth – Alcatel on Distributed eHealth consoles. You can, however, set up eHealth – Alcatel on Distributed eHealth systems from which you plan to monitor Alcatel elements.

Note: For more information about distributed systems, see the Distributed eHealth Administration Guide.

The command-line setup program asks a series of questions, validates your answers, and prompts you to supply a new answer if the one that you provided is invalid.

Default responses for a particular question appear in brackets [ ]. You can press Enter to accept the default response. You can also exit the setup program at any time by entering q to quit.

eHealth – Alcatel Setup Program

The setup program consists of three parts:

The first portion prompts you for information about the Alcatel 5620 NM.

The second portion prompts you for information about the QCnetwork software

The final portion prompts you for information about your eHealth system.

As you perform the setup, refer to the setup checklists that you completed.

Run the eHealth – Alcatel Setup Program

You must run the eHealth – Alcatel setup program on each eHealth system that you want to use to report on your Alcatel elements.

To run the eHealth – Alcatel setup program

1. Log in to eHealth as the eHealth administrator (or any user who has been added to the eHealth database with the nhManageUsers command).

2. Change to the eHealth directory by entering the following command in any terminal window (such as an xterm or shell window):

cd ehealth

ehealth

Specifies the full pathname of the eHealth directory.

3. (Optional) Use one of the commands listed in the following table to source the appropriate eHealth resource file to set your environment.

Shell

Command

Bourne

. nethealthrc.sh

C

source nethealthrc.csh

Korn

. nethealthrc.ksh

Note: If you do not source the resource file, change to the $NH_HOME/bin directory, or specify the full pathname in your eHealth commands.

4. Execute the following command:

ehealth

The server starts and the console window appears.

5. Execute the following command:

nhAnmSetup

The setup program describes the setup process and begins prompting you for information. You can accept the default values that the program provides, or enter other valid values. Refer to your setup checklists.

How the Configuration Process Works

Upgrade Option for Elements

Prior to prompting you for information about your eHealth system, the setup program searches the eHealth database for existing eHealth – Newbridge elements. If any exist, the setup program provides an option to proceed with converting these elements for use with eHealth – Alcatel.

Note: The configuration extraction program runs during the conversion process.

Installation Log

eHealth – Alcatel stores a record of each installation session in a log file named $NH_HOME/log/nhiAnmSetup.log.

You might find it useful to examine the nhiAnmSetup.log file to review the results of the eHealth – Alcatel installation. Keep the installation log as a reference for yourself and for Technical Support if you need assistance.

How the Configuration Process Works

Each time you run the eHealth – Alcatel configuration process, eHealth does the following:

Extracts configuration information about the elements in the Alcatel database and transfers this information to the eHealth system.

Adds interface elements to the eHealth database and poller configuration.

Updates the eHealth database with information about existing elements.

Adds or updates LAN/WAN groups as needed, if you use rules files.

The configuration process extracts element information from the Alcatel database and adds the elements to the eHealth poller configuration. eHealth – Alcatel supports the following types of Alcatel Frame Relay and ATM elements:

Frame Relay paths (FRPs), which are equivalent to permanent virtual circuits (PVCs)

Frame Relay links (FRLs), which are the Alcatel network-to-network interfaces (NNIs) and user-to-network interfaces (UNIs)

Alcatel Frame Relay/Asynchronous Transfer Mode (FRATM) Internetworking Units

Frame Relay Engine cards (PE/FRE)

Frame Relay to ATM Paths/Channels

How the Configuration Process Works

Frame Relay Switch cards

Time division multiplexing (TDM) data termination units (DTUs)

ATM ports

ATM over Sonet/SDH ports

ATM virtual paths (ATM VPCs)

ATM virtual channels (ATM VCCs)

Note: Certain ATM circuits are not discovered by eHealth – Alcatel by design. In the Alcatel 5620 NM, ATM circuits can be configured with a Service Category, and each Service Category has a speed attribute associated with it. The eHealth software discovers only those ATM elements that are configured to have a Service Category with the speed attribute of Sustained Information Rate (SIR). Currently, the Service Categories with the SIR speed attribute include: rt-VBR and nrt-VBR. A QC network client warning indicates that the circuit is not supported

eHealth defines one element for each endpoint of an FRP, FRL, ATM VPC, and ATM VCC. Thus, for each of these element types, eHealth defines two elements. eHealth defines one element for each Frame Relay card, FRATM unit, and ATM port.

Note: For more information about the format used for element names, see the eHealth Data Integration Guide.

You can schedule the configuration process (see page 34) to update your poller configuration automatically.

Element Configuration Tasks

The following graphic illustrates the configuration process that adds Alcatel elements to the eHealth database.

process that adds Alcatel elements to the eHealth database. More information: How to Enable Statistics Collection

More information:

How to Enable Statistics Collection (see page 18)

Files Used to Configure Elements (see page 38)

Element Configuration Tasks

Configuration tasks in your eHealth poller configuration include adding, reconfiguring, grouping, modifying, and excluding Alcatel elements.

Element Configuration Tasks

Add or Reconfigure Alcatel Elements

To add elements to eHealth or reconfigure them, you must extract configuration information from the Alcatel 5620 NMS.

To add or reconfigure elements

1. Log in to the eHealth system as the eHealth user.

2. Open a terminal window and access the eHealth directory.

3. (Optional) Source the eHealth resource file that is appropriate for your shell environment by using the -dciCmd nhAnmGetCfg or -dciOut dciOutputFile command.

Note: If you do not source the eHealth resource file, navigate to the $NH_HOME/bin directory or specify that directory in your eHealth commands.

4. Execute the following nhConfig command:

nhConfig -dciCmd nhAnmGetCfg

-dciCmd nhAnmGetCfg

Extracts configuration information for Alcatel elements from the Alcatel 5620 NMS.

Group, Modify, and Exclude Elements

To group, modify, and exclude elements

1. Log in to the eHealth system as the eHealth user.

2. Open a terminal window and access the eHealth directory.

3. (Optional) Source the eHealth resource file that is appropriate for your shell environment by using the -dciCmd nhAnmGetCfg or -dciOut dciOutputFile command.

4. Execute the following nhConfig command:

nhConfig -dciCmd nhAnmGetCfg -dciOut dciOutputFile

-dciCmd nhAnmGetCfg

Extracts information about element configuration from an Alcatel 5620 NMS by using the nhAnmGetCfg command.

-dciOut dciOutputFile

Saves the processed element configuration in the element file specified in dciOutputFile.

nhConfig Command – Updates the Poller Configuration

5. Examine the dciOutputFile and note the patterns that you can use to group, modify, or exclude elements.

Example: Note common strings in element names. You might want to group all elements that share a common string. You might want to divide the elements between multiple eHealth systems to exclude elements that you will add to another eHealth system.

6. Create a rules file that specifies the grouping, modifying, or excluding actions.

Note: For more information about creating rules files, see the eHealth Data Integration Guide.

7. Execute the following nhConfig command:

nhConfig -dciCmd nhAnmGetCfg -dciRule rulesFile

-dciCmd nhAnmGetCfg

Extracts information from an Alcatel 5620 NMS by using the nhAnmGetCfg command.

-dciRule rulesFile

Specifies the pathname of a rules file that you created to filter and group elements in the poller configuration.

More information:

Element Files (see page 38)

nhConfig Command – Updates the Poller Configuration

The nhConfig command updates the poller configuration with the information that it obtains from the Alcatel database.

This command has the following syntax:

nhConfig [-help] [-rev] [-verbose] [-verify] -dciCmd nhAnmGetCfg [-dciOut dciOutputFile]

[-dciRule rulesFile [-dataFiles file1

[-dciIn dciInputFile] [-commit {yes|no}] [-createNew {yes|no}] [-merge {yes|no} ]

-help

filen]]

(Optional) Displays the syntax of the nhConfig command.

-rev

Displays the product version.

nhConfig Command – Updates the Poller Configuration

-verbose

(Optional) Prints information at each phase of processing.

-verify

(Optional) Processes input and produces an element file, but does not add the elements to the eHealth database.

If you specify -verify, the command automatically includes -verbose. Specifying -verify also implies setting -commit to no and -createNew to no.

-dciCmd nhAnmGetCfg

Extract information from an Alcatel 5620 NMS by using the nhAnmGetCfg command.

-dciOut dciOutputFile

(Optional) Saves the processed element information in the specified file. Use this argument to create a file from which you can review the configuration information.

-dciRule rulesFile

(Optional) Specifies the pathname of a rules file that you can use to filter and group elements from the NMS database in the poller configuration.

-dataFiles file1

filen

(Optional) Specifies the pathnames of data files that you can use with the specified rules file to process the configuration information.

-dciIn dciInputFile

(Optional) Specifies an input file to the nhConfig command. You can use this option as an alternative to the -dciCmd nhAnmGetCfg option for the nhConfig command.

By using the dciOutputFile from a previous run of the nhConfig command as the argument to -dciIn, you can examine the output of a previous configuration extraction without having to repeat the extraction process.

-commit {yes|no}

(Optional) Specifies whether to commit changes to the eHealth database.

yes

Commits changes to the database. Specifying -commit yes implies setting -merge to yes because it merges element information with elements from the database and saves the results. This value is the default.

no

Produces a change file and does not commit changes to the database.

Tips for Using nhConfig Arguments

-createNew {yes|no}

Specifies whether to create new elements in the eHealth database.

yes

Creates new elements in the database. This value is the default.

no

Does not create new elements in the database. Existing elements in the database might be updated.

-merge {yes|no}

Specifies whether to merge the processed element information with elements from the eHealth database.

yes

Merges the element information with elements from the database. This value is the default.

no

Does not merge the element information with elements from the database. If -commit is set to yes, setting -merge to no has no effect.

Tips for Using nhConfig Arguments

The following tips can help you use the nhConfig command more effectively:

You can use the -dciOut argument to create an element file (see page 38) that you can review for information about each element that was added.

You can use the dciOutputFile from a previous run of the nhConfig command as an argument to the -dciIn command. This approach lets you examine the output of a previous configuration extraction without having to repeat the extraction process.

Note: For more information and examples, see the eHealth Data Integration Guide.

You can use the -verify argument to create a temporary element file in the $NH_HOME/tmp directory, and the nhConfig command will not update the poller configuration. The command displays the element file name when the processing completes. You can review the element file to determine whether you want to import the elements or use grouping or filtering options.

LAN/WAN Group Configuration

You can use the -dciRule and -dataFiles arguments to customize the extraction process and do the following:

Filter out elements that you do not want to include in your eHealth reports.

Group elements by name, type, or other criteria.

– Include or exclude (filter) elements on the eHealth system where the nhConfig command runs.

Change element information.

You can create your own rules and data files to customize the extraction process. These files use the element information to perform filtering, grouping, and modifications.

Note: For more information, see the eHealth Data Integration Guide.

LAN/WAN Group Configuration

The nhConfig -dciCmd nhAnmGetCfg command extracts configuration information for all elements defined on the Alcatel 5620 NM, downloads the information to the eHealth system, and adds all of the elements to the poller configuration.

The QCnetwork API user account that eHealth uses to access the NM must have permission to view one or more system partitions on the NM. The nhConfig -dciCmd nhAnmGetCfg command automatically creates LAN/WAN groups for the elements in these partitions. If you would like to create your own groups, you can disable default element grouping as described in Disable Default LAN/WAN Grouping (see page 34).

The LAN/WAN groups that the nhAnmGetCfg command automatically creates are named partition-elementType, where partition is the name of the Alcatel partition assigned to the API user and elementType is one of the values defined in the following table.

elementType Value

For

FRL

Frame Relay links

FRP

Frame Relay paths

CARD

Alcatel Frame Relay cards

DEVICE

Alcatel devices including FRATM units

ATM-PORT

ATM ports

ATM-VP

ATM virtual paths (ATM VPCs)

LAN/WAN Group Configuration

elementType Value

For

ATM-VC

ATM virtual channels (ATM VCCs)

RESOURCE

IMA ATM resources

eHealth assigns elements of the same type to the associated group for a partition.

Example: For the Supply Network partition, group names would appear in the poller configuration as follows:

Supply_Network-FRL

Supply_Network-FRP

Supply_Network-CARD

Supply_Network-DEVICE

Supply_Network-ATM-PORT

Supply_Network-ATM-VP

Supply_Network-ATM-VC

Supply_Network-RESOURCE

Supply_Network-SONET_LINE

Supply_Network-SONET_PATH

Supply_Network-SONET_SECTION

You can also create your own customized element groups by using rules files and data files.

Note: For more information, see the eHealth Data Integration Guide.

Disable Default LAN/WAN Grouping

Disable Default LAN/WAN Grouping

You can disable the default element grouping if you would like to create your own groups.

To disable default grouping, execute the following command:

nhAnmGetCfg -noGrouping -dciOut filename

-noGrouping

Turns off the default element grouping.

-dciOut filename

Specifies the filename of the resulting DCI file that eHealth can import.

Default grouping is disabled.

Schedule the Configuration Process

You can add a scheduled job to run the nhConfig command to extract configuration information regularly from the Alcatel 5620 NMS. The scheduled job updates your poller configuration automatically with changes to Alcatel elements.

To create a new job type and schedule the job, you must run the nhSchedule command from the command line. You cannot use the eHealth Schedule Jobs dialog to schedule the extraction of configuration information from the NM.

To create and schedule an Alcatel configuration job

1. Log in to the eHealth system as the eHealth user.

2. Open a terminal window and access the eHealth directory.

3. (Optional) Source the eHealth resource file appropriate for your shell environment by using the -dciCmd nhAnmGetCfg or -dciOut dciOutputFile command.

Note: If you do not source the eHealth resource file, access the $NH_HOME/bin directory or specify that directory in your eHealth commands.

Schedule the Configuration Process

4. Execute the nhSchedule command that creates a new job type.

Example: The following command creates a job type named Alcatel Config that uses 100 percent of the system resources. The job executes the command nhConfig -dciCmd nhAnmGetCfg when it runs.

nhSchedule -defineType "Alcatel Config" -load 100 -cmd "nhConfig -dciCmd nhAnmGetCfg"

5. Execute the nhSchedule command that schedules the job.

Example: The following command schedules the Alcatel Config job to extract configuration information each day at 12:30 a.m. and update the eHealth poller configuration. The command takes the name of the rules file as an argument.

nhSchedule -schedule "Alcatel Config" -time "12:30 AM" -daily yyyyyyy -args "-dciRule rulesFile "

These nhSchedule commands are only examples. When scheduling jobs for your environment, specify a time and frequency that correspond to the frequency with which changes are made to your network. For example, if PVC assignments change daily, schedule configuration jobs to run daily.

If you schedule several configuration jobs, make sure that you leave enough time between jobs to allow the completion of one job before the next one starts.

Note: For more information about the nhSchedule command, see the eHealth Administration Guide.

More information:

How the Configuration Process Works (see page 25)

Group, Modify, and Exclude Elements (see page 28)

Data Modification in the Poller Configuration

Data Modification in the Poller Configuration

Poller configuration consists of changing the attributes of your Alcatel elements by using the nhConfig command or the Poller Configuration dialog.

The nhConfig command updates the configuration with information from the Alcatel database.

When you delete elements from the Alcatel database, a subsequent nhConfig command does not remove those elements from the eHealth database. Instead, you must delete these elements through the Poller Configuration dialog.

The Poller Configuration dialog lets you change attributes such as the name and speed of your Alcatel elements.

If you change any attributes other than name and speed, the changes will be overwritten the next time that eHealth – Alcatel imports configuration information from the Alcatel database if the information is different.

When you disable polling for an Alcatel element, eHealth does not add imported statistics data for the element to the database.

Note: Do not change the agent type for Alcatel elements.

The configuration process automatically updates the speeds for the following Alcatel element types:

Frame Relay paths

Frame Relay links

ATM virtual paths

ATM virtual channels

IMA ports

Modify or Delete Elements in the Poller Configuration

Modify or Delete Elements in the Poller Configuration

You can change the attributes of your Alcatel elements or delete them from the Alcatel database if they are no longer needed.

To modify or delete elements in the poller configuration

1. Access the eHealth console.

2. Select Setup, Poller Configuration.

The Poller Configuration window appears.

To modify an element, double-click the element or select it and click Modify.

The Modify Element window appears.

To delete an element, select it and click Delete.

Note: For more information about the Poller Configuration dialog, see the eHealth Administration Guide.

Files Used to Configure Elements

Files Used to Configure Elements

You can use rules files and data files to group, modify, and exclude elements during the configuration process. Before you can create rules files and data files, you should understand the structure of element files.

Element files, rules files, and data files are described as follows:

Element file

Defines each element's configuration information in ASCII file format.

When you run the nhConfig command with the -dciOut dciOutputFile argument, nhConfig saves the element information in an element file. You can examine the contents of the element file to determine the rules to implement in a rules file.

An element file is also known as a DCI file.

Rules file

Specifies criteria for selecting and processing elements in ASCII file format.

For example, a rules file can specify a selection condition (elements that have the text port in their name) and an action (add the selected elements to the poller configuration).

Data file

Specifies a list of elements in ASCII file format.

You can specify a data file as the selection condition in the rules file.

Note: For more information, see the eHealth Data Integration Guide.

Element Files

An element file (also known as a DCI file) is an ASCII file that defines the configuration information for each element in comma-separated fields. You can create rules files that use these fields to filter elements, modify element information, and group elements during the configuration process. For example, you can create rules files that rename elements with more meaningful names.

When the configuration process extracts the configuration information for Alcatel elements, eHealth creates temporary element files. These temporary element files are deleted after the element information is added to the poller configuration.

Element Files

The element file consists of element definitions (see page 40). Each element definition contains several fields.

Note: For more information about the fields in an element file, see the eHealth Data Integration Guide.

More information:

nhConfig Options (see page 31)

Index Values for Alcatel Elements (see page 39)

Index Values for Alcatel Elements

The element file contains up to four index values for each Alcatel Frame Relay and ATM element in your poller configuration. Knowing the index values can help you map elements to entries in the Alcatel statistics data files (see page 45) on the NM.

The following table lists the applicable index field values for each Alcatel element type, where callID, nodeID, shelf#, slot#, and device# are replaced with the values for these fields in the Alcatel database.

Alcatel Element Type

index1

index2

index3

index4

Value

Value

Value

Value

Frame Relay path

callID

1

 

(endpoint

A)

2

(endpoint

B)

Frame Relay link

callID

1

 

(endpoint

A)

2

(endpoint

B)

DEVICE (For example:

nodeID

shelf#

slot#

device#

FRATM unit)

Card

nodeID

shelf#

slot#

ATM port

nodeID

shelf#

slot#

port#

Element Files

Alcatel Element Type

index1

index2

index3

index4

Value

Value

Value

Value

ATM virtual path

callID

1

 

(endpoint

A)

2

(endpoint

B)

ATM virtual channel

callID

1

 

(endpoint

A)

2

(endpoint

B)

Resource (For example:

nodeID

shelf#

slot#

resource#

IMA)

More information:

Examine the Alcatel Statistics File for the Cause of Data Gaps (see page 64)

Element Definition Examples

The following examples of Alcatel element definitions are formatted for readability. Some of the fields might not have values. A field containing an empty string is shown as a set of empty quotation marks.

Example: Frame Relay Path

The following is an example of an element definition for a Frame Relay path (FRP):

e351,A/P1-1-3-1:B/P1-1-3-1_Path-SRC-DLCI-16,,"5:1 pathsrc-

5.1",Yes,,,"5:1",,,64000,,A,alcatelNm-imp-fr-36170-pvc-

cufr.mtf,255.255.255.255,,,Yes,,5:1,5,1,,,,,,AlcatelNm,,"Path 36170A/P1-1-3-1.16 : 36170B/P1-1-3-1.16",,alcatelNm-imp-fr-36170-pvc-cufr.mtf,"A/P1-1-3-1:B/P1-1-3-1 Path",Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Example: Frame Relay Link

The following is an example of an element definition for a Frame Relay link (FRL):

e341,AChannel1-:-ResouceC1-SRC,,"42:1 frlinksrc-

42.1",Yes,,,"42:1",,,64000,,A,alcatelNm-imp-fr-36177-frl-

cufr.mtf,127.18.2.1,,,Yes,,42:1,42,1,,,,,,AlcatelNm,,"FRL T36177/3-3-1 :

T36177/3-C-1",,alcatelNm-imp-fr-36177-frl-cufr.mtf,AChannel1-:-

ResouceC1,Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Element Files

Example: Device

The following is an example of an element definition for a device (such as a FRATM unit):

e221,FRATM-node-26-shelf-1-slot-1,,"26:1:1:4 device-

26.1.1.4",Yes,,,"26:1:1:4",,,,,,alcatelNm-imp-fr-

atm.mtf,255.255.255.255,,,Yes,,26:1:1:4,26,1,1,4,,,,AlcatelNm,,"Port FRATM/A1-

1",,alcatelNm-imp-fr-atm.mtf,"",Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Example: Card

The following is an example of an element definition for a card:

e1,3600A-node-15-shelf-1-slot-1,,"15:1:1 card-

15.1.1",Yes,,,"15:1:1",,,,,,alcatelNm-imp-card-

frs.mtf,255.255.255.255,,,Yes,,15:1:1,15,1,1,,,,,AlcatelNm,,"3600A/Slot

A1",,alcatelNm-imp-card-frs.mtf,"",Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Example: ATM Port

The following is an example of an element definition for an ATM port:

e17,7270A-node-2-shelf-1-slot-4-port-1,,"2:1:4:1 port-

2.1.4.1",Yes,,,"2:1:4:1",,,,,,alcatelNm-imp-atm-oc3-

port.mtf,255.255.255.255,,,Yes,,2:1:4:1,2,1,4,1,,,,AlcatelNm,,"Port 7270A/3-

1",,alcatelNm-imp-atm-oc3-port.mtf,"",Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Example: ATM Virtual Path

The following is an example of an element definition for an ATM virtual path connection (VPC):

e375,36170_E3_VPC_Path-SRC-VPI-0,,"65:1 pathsrc-

65.1",Yes,,,"65:1",,,1000216,,A,alcatelNm-imp-atm-

path.mtf,172.18.1.1,,,Yes,,65:1,65,1,,,,,,AlcatelNm,,"Path T36170/P1-4-1.0 :

TT36170/P1-3-1.0",,alcatelNm-imp-atm-path.mtf,"36170 E3 VPC Path",Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Example: ATM Virtual Channel

The following is an example of an element definition for an ATM virtual channel connection (VCC):

e371,36150_E3ATM_VCC_Path-SRC-VPI-0-VCI-32,,"63:1 pathsrc-

63.1",Yes,,,"63:1",,,1000216,,A,alcatelNm-imp-atm-

pvc.mtf,127.18.1.5,,,Yes,,63:1,63,1,,,,,,AlcatelNm,,"Path T36150/A4-1.0.32 :

TT36150/A4-1.0.32",,alcatelNm-imp-atm-pvc.mtf,"36150 E3ATM VCC Path",Active,,,,,,,,,,,,,,,,,,,,,,,,,,,

Element Files

Example: Resource

The following is an example of an element definition for a Resource:

e398,7470B-node-42-shelf-1-slot-2-resource-1,,"42:1:2:1 resource-

42.1.2.1",Yes,,,"42:1:2:1",,,3046512,,,alcatelNm-imp-atm-ima-

port.mtf,172.17.100.1,,,Yes,,42:1:2:1,42,1,2,1,,,,AlcatelNm,,"Resource 7470B/P1-

1-IMA1",,alcatelNm-imp-atm-ima-port.mtf,7470-

T1IMA1,Deleted,,,,,,,,,,,,,,,,,,,,,,,,,,,

More information:

Element Files (see page 38)

Chapter 3: Using the Integration

Chapter 3: Using the Integration After you have configured eHealth with information from the Alcatel 5620
Chapter 3: Using the Integration After you have configured eHealth with information from the Alcatel 5620

After you have configured eHealth with information from the Alcatel 5620 NM, you can import statistics and run eHealth reports on your Alcatel elements.

This section contains the following topics:

How the Statistics Import Process Works (see page 43) Supported eHealth Reports (see page 46) Unsupported Reports and Charts (see page 47)

How the Statistics Import Process Works

When the configuration process ends, the eHealth import poller initializes and connects to the Alcatel 5620 NMS to obtain statistics for the elements in the poller configuration. The Import Polling Status window shows the number of records imported and the time of the next poll. At each poll, the import poller connects to the Alcatel 5620 NMS, obtains statistics data for the Alcatel elements, and adds the data to the eHealth database.

How the Statistics Import Process Works

How eHealth Imports Raw Statistics

eHealth polls the Alcatel 5620 NMS to import and store the statistics about your Alcatel elements. You specify the polling interval when you run the installation program on each eHealth system. The following graphic illustrates how eHealth – Alcatel imports statistics from the Alcatel 5620 NM.

– Alcatel imports statistics from the Alcatel 5620 NM. At each import polling interval, the eHealth

At each import polling interval, the eHealth system connects to the Alcatel 5620 NMS and transfers the statistics for the Alcatel elements. eHealth adds the statistics to the eHealth database.

How the Statistics Import Process Works

Statistics Data Files

The statistics data files that the integration module imports and sends to eHealth are located in the /opt/netmgt/stats/format directory on the Alcatel 5620 NM system. These files have the following format:

yyyy.mm.dd.interval_number.format

interval_number

Specifies a value from 0–96, which represents the 15-minute interval of the day.

Example: The value 01 represents 00:15:00 (12:15 a.m.).

Stop the Import Process

You can stop importing statistics data or stop importing data for one or more elements.

To stop importing data for a period of time

1. Select Setup, Poller Controls from the eHealth console.

2. Select Off next to Poller.

3. Click OK.

Data is not imported and elements are not polled.

To stop importing data for one or more elements

1. Select one or more elements in the Poller Configuration dialog.

2. Select the element or elements for which you want to stop importing data and click Modify.

3. Do one of the following:

If you selected one element, select Off under Poll in the Modify Element dialog and click OK or Apply/Next.

If you selected more than one element, select Off next to Change Poll To in the Modify Elements dialog and click OK.

4. Click OK.

Data is not imported for the selected element(s).

Note: For more information about using the Poller Configuration dialog, see the eHealth Administration Guide.

Supported eHealth Reports

Change the Import Polling Interval

The default import polling interval for eHealth – Alcatel is 15 minutes. You can increase or decrease the import polling interval as needed, but make sure that you synchronize the interval with the data collection schedule on the Alcatel 5620 NMS.

Typically, the Alcatel 5620 NM collects statistics every 15 minutes. The NM keeps backup records of several previous polls. If the import polling interval that you set is longer than the amount of time that the backup records are kept, you might miss some records. With too little time between polls, the import poller does not return records until the NM polls the Alcatel switches again.

Note: Before you change the nmsPollInterval setting, make sure that you know how often the Alcatel 5620 NM collects statistics data and how many backup records it saves. For complete information, see your Alcatel documentation.

To change the import polling interval

1. Run the eHealth – Alcatel Setup program.

2. Choose 'Specify the section(s) to run' from the main menu.

3. Choose Change the eHealth Settings.

4. Specify the new Import Polling Interval when prompted.

5. Exit the Setup program.

Supported eHealth Reports

You can run all eHealth reports on your LAN/WAN elements. You can run Health, At-a-Glance, Service Level, Top N, and Trend reports on your Alcatel elements and LAN/WAN groups.

Note: For information about running and scheduling reports from the console, see the eHealth Administration Guide. For information about running reports from the web interface, see the eHealth Help.

Unsupported Reports and Charts

Availability, Latency, and Reachability

The Alcatel 5620 NMS provides availability statistics for some Alcatel ATM ports, but does not provide statistics on availability, latency, or reachability for any other Frame Relay and ATM element types that eHealth – Alcatel currently supports.

Note:

Alcatel Frame Relay and ATM elements, see the eHealth Integration for Alcatel 5620 Network Manager Application Brief (Version 4.1 and later) on the eHealth web site.

For more information about the statistics that eHealth monitors for

Guidelines for Scheduling Reports

When you schedule eHealth reports on elements that have imported data, such as Alcatel elements, be sure to consider the data analysis schedule that is in effect. You should schedule reports so that the last import poll completes before the data analysis job that analyzes the imported data begins.

Note: For more information about the data analysis schedule, see the eHealth Administration Guide.

Unsupported Reports and Charts

The following table lists the reports and charts that are not available for most Alcatel elements on certain eHealth report types.

Report

Unavailable Reports and Charts

LAN/WAN Health reports

Availability and Latency Supplemental report

LAN/WAN Executive Service Level reports

Availability Distribution for All Groups chart and Latency Distribution for All Groups chart

LAN/WAN Customer Service Level reports

Availability chart

LAN/WAN At-a-Glance reports

Availability chart and Latency chart

Chapter 4: Troubleshooting the Integration

Chapter 4: Troubleshooting the Integration This section contains the following topics: Installation Problems (see page
Chapter 4: Troubleshooting the Integration This section contains the following topics: Installation Problems (see page

This section contains the following topics:

Installation Problems (see page 49) Configuration Problems (see page 50) Polling Problems (see page 55)

Installation Problems

The following problems can occur while you are running the eHealth – Alcatel setup program:

Version error

Invalid license error

More information:

Setup Program (see page 11)

Version Error

Symptom:

My system displays a version error.

Solution:

Make sure that you are running a supported version of the Alcatel 5620 NM.

Note: For a list of supported Alcatel versions, see the eHealth Integration Modules Release Notes.

Configuration Problems

Invalid License Error

Symptom:

I received a missing or invalid license error.

Solution:

You must obtain and install an eHealth – Alcatel license to enable the integration module.

More information:

How to License eHealth – Alcatel (see page 20)

Configuration Problems

The following problems can occur while you are configuring your Alcatel elements:

Cannot connect to the NM

eHealth cannot log in to the IM

Configuration process occupies QCnetwork API resources

Login retries exceed number permitted

CIR/SIR/speed error

Note: For information about installing and administering the Alcatel 5620 NM, see your Alcatel documentation.

Cannot Connect to the NM

Symptom:

eHealth cannot connect to the Alcatel 5620 NM, and error messages appear in the terminal window where I run the nhConfig command.

Solution:

The following are possible causes for these errors:

The Alcatel 5620 NM is not reachable on the network.

The Alcatel 5620 NM is not running.

The QCnetwork Services software is not correctly installed on the NM.

The alcatelNm.init file on the eHealth system incorrectly specifies the primary or secondary Alcatel 5620 NM.

Configuration Problems

Complete the following steps to identify and troubleshoot the problem:

1. Execute the following command in a terminal window to determine if the Alcatel 5620 NM system is reachable:

ping host

host

Specifies the hostname or IP address of the primary or secondary NM specified in the alcatelNm.init file.

If you do not receive an Internet Control Message Protocol (ICMP) echo

reply message from the NM before the timeout period expires, a network connectivity problem exists between the eHealth system and the Alcatel 5620 NM. Contact your system administrator for assistance.

2. Make sure the alcatelNm.init file on the eHealth system has been correctly edited.

The $NH_HOME/modules/alcatelNm/alcatelNm.init file on each eHealth system must include correct specifications for the hostname or IP address of the primary and secondary Alcatel 5620 NM systems. If you do not have

a secondary NM, set the nmsSecondary field in the alcatelNm.init file to the same hostname or IP address as the primary NM.

3. Execute the following command in a terminal window to determine if the Alcatel QCnetwork Services are reachable:

nhAnmQcnVerify -host<host> -port 8248 -user <user> -password <password>

host

Specifies the hostname or IP address of the primary NM specified in the alcatelNm.init.file.

user

Specifies the QCnetwork user account for eHealth.

Example: QCF_config

password

Specifies the QCnetwork user password for eHealth.

Example: mainstreet

Configuration Problems

4. Make sure that the Alcatel QCnetwork Services software is installed on the Alcatel 5620 NM.

a. Log in to the Alcatel 5620 NM as root.

b. Make sure that the 5620.QC_network.xml and 5620.QcnNamingService.xml files are in the following directory:

/opt/netmgt/etc/nms

c. If the QCnetwork API Services software is not installed, you or your system administrator must install it on the NM and create a QCnetwork user account for eHealth.

5. Make sure that the network daemon is running on the Alcatel 5620 NM.

a. Log in to the NM system as root and navigate to the /opt/netmgt/bin directory.

b. Execute the following command to determine the status of the network daemon:

./RED_comms status

If the network daemon is not running on the NM, execute the following command to start it:

./RED_comms start

c. Look for a message indicating that the daemon is up and running.

eHealth Cannot Log In to the NM

Symptom:

eHealth cannot log in to the NM through the API, and error messages appear in the terminal window where I run the nhConfig command.

Solution:

eHealth accesses the Alcatel 5620 NM through an Alcatel API user that you create with the QCnetwork Services software. Possible causes for these errors include the following:

The alcatelNm.init file on the eHealth system incorrectly specifies the user name and password of the API user.

The API user is not correctly set up on the Alcatel 5620 NM.

You must create the QCnetwork user name and password on the Alcatel 5620 NM by using the QCnetwork Services software. This process is not the same as creating a standard user account on a UNIX system.

More information:

How to Create a QCnetwork User Account for eHealth (see page 15)

Configuration Problems

Configuration Process Occupies QCnetwork API Resources

Symptom:

An eHealth – Alcatel configuration process that is running is occupying QCnetwork API resources on the NM.

Solution:

Do not interrupt the nhConfig -dciCmd nhAnmGetCfg command before it finishes running.

eHealth – Alcatel uses the QCnetwork API to extract information about Frame Relay and ATM elements from the database on the NM and then updates the eHealth poller configuration with these elements.

Login Retries Exceed Number Permitted

Symptom:

The number of unsuccessful attempts to log in to the Alcatel 5620 NM exceeds the number of login retries permitted on the NM.

Solution:

Complete the following steps to identify and troubleshoot the problem:

1. Verify that the NM systems are online and reachable, and that QCnetwork services are running correctly.

2. Verify that your QCnetwork user name and password are correct.

3. Verify that the QCnetwork port number specified during the installation is correct.

4. Make sure the alcatelNm.init file on the eHealth system is correctly edited.

The $NH_HOME/modules/alcatelNm/alcatelNm.init file on each eHealth system must include correct specifications for the user name and password of the QCnetwork user on the NM.

5. Open a terminal window on the eHealth system and execute the following command to determine if an instance of the eHealth – Alcatel configuration process (nhiAnmGetCfg) is still running from a previous nhConfig command:

ps -ef | grep nhiAnmGetCfg

If the configuration process is still running, it might be occupying resources on the NM.

Configuration Problems

6. If necessary, stop the configuration process by executing the following command:

kill -9 processID

processID

Specifies the process ID (PID) of the nhiAnmGetCfg process.

7. If configuration problems persist, try resetting the login attempts for the QCnetwork API user:

a. On the Alcatel 5620 NM, display the Modify User dialog for the API user that you created for eHealth.

b. Select Reset Login Attempts and save the changes.

CIR/SIR/speed Error

Symptom:

A CIR/SIR/speed warning indicates that CIR or SIR parameters were not

configured on the Alcatel 5620 NM for some path destinations.

Solution:

Make sure that the CIR/SIR values for the elements on which you are

reporting are correctly configured through the Alcatel 5620 NM user interface. This situation will not prevent statistics collection or configuration import, but

it might affect some reports that include Bandwidth Utilization charts.

Note: For more information, see your Alcatel documentation.

Polling Problems

Polling Problems

The following problems can occur during the polling process:

Cannot Connect to the NM to Import Statistics

Problems Importing Statistics for Elements

Missing Elements

No Data in Reports

No Data for Elements

FastBUS Elements Not Imported or Polled

Missing Statistics Data

Missing Performance Variables

Data Gaps in eHealth Reports

eHealth – Alcatel imports statistics data for the Alcatel elements in your poller configuration. For the eHealth import polling process to work, you must install the Alcatel 5620 Statistics Collector software on the Alcatel 5620 NM and enable statistics collection for each element on which you want eHealth to report.

The Statistics Collector software can be installed on the Alcatel 5620 NM or on another remote system. Check with your Alcatel system administrator to determine the configuration at your site. Although eHealth – Alcatel can import statistics from either the NM or from the remote system on which the Statistics Collector is installed, knowledge of the configuration at your site might help you isolate and resolve polling problems.

Note: For instructions about installing and administering the Alcatel 5620 NM, see your Alcatel documentation.

More information:

How the Statistics Import Process Works (see page 43)

Polling Problems

Cannot Connect to the NM to Import Statistics

Symptom:

eHealth cannot connect to the Alcatel 5620 NM or to the system on which the Statistics Collector software is installed, and it cannot import statistics data for Alcatel elements. An error message appears in the Import Polling Status window and in the $NH_HOME/log/pollerStatus/messages.import.log file.

Solution:

Possible causes for this error include the following:

The NM or the system on which the Statistics Collector is installed is not reachable on the network.

The NM or the system on which the Statistics Collector is installed is not running.

The QCnetwork API Services software is not installed correctly on the NM.

The Statistics Collector software is not installed correctly on the NM or on a remote system.

If you receive error messages that indicate problems with accessing the statistics directory on the Alcatel 5620 NM, verify that the user specified during the installation has read/write permissions for the following directories:

/opt/netmgt/stats/format

/opt/netmgt/stats/filter

Polling Problems

Complete the following steps to identify and troubleshoot the problem:

1. Execute the following command in a terminal window to determine if the Alcatel 5620 NM system is reachable:

ping host

host

Specifies the hostname or IP address of the primary or secondary NM specified in the alcatelNm.hosts.sci file.

If you do not receive an ICMP echo reply message from the NM before the timeout period expires, a network connectivity problem exists between the eHealth system and the Alcatel 5620 NM. Contact your system administrator for assistance.

2. Make sure the network daemon is running on the Alcatel 5620 NM. (Errors are indicated by FTP, failed to connect messages.)

a. Log in to the NM system as root and change to the /opt/netmgt/bin directory.

b. Execute the following command to determine the status of the network daemon:

./RED_comms status

c. If the network daemon is not running on the NM, execute the following command to start it:

./RED_comms start

d. Look for a message indicating that the daemon is up and running.

3. Make sure the QCnetwork API Services software and Statistics Collector software are installed on the Alcatel 5620 NM.

a. Log in to the Alcatel 5620 NM as root.

b. Make sure that the 5620.QC_network.xml and 5620.QcnNamingService.xml files are in the /opt/netmgt/etc/nms directory.

c. If the QCnetwork API Services software is not installed, you or your system administrator must install it on the NM and create a QCnetwork user account for eHealth.

Note: The Statistics Collector software might be installed on another system in your network instead of on the NM. Check with your Alcatel system administrator to determine if this configuration is the one at your

site.

Polling Problems

Problems Importing Statistics for Elements

Symptom:

eHealth – Alcatel encountered problems importing statistics for Alcatel elements and displayed the following:

Bad (red) poll bars on the Missing Polls graph in the Import Polling Status window. These bars may appear when duplicate elements in the poller configuration must be removed.

Error messages in the Import Polling Status window and in the $NH_HOME/log/pollerStatus/messages.import.log file. (The name of the element experiencing the problem appears in parentheses at the end of each message.)

Note: In the polling error messages, Statistics Collector refers to the Alcatel 5620 Statistics Collector software installed on the Alcatel 5620 NM or on a remote Alcatel system.

Solution:

Complete the following steps to correct the polling problem:

1. If the message indicates that statistics data for the element is unavailable during the current collection period, wait four or more polling intervals to see if data becomes available.

The Alcatel 5620 NM collects statistics for most elements every 15 minutes by default. This interval matches the default eHealth – Alcatel import polling interval of 15 minutes.

For some elements, such as Frame Relay paths with endpoints on an Alcatel 7470 Multiservice Platform, the NM collects statistics at 60-minute intervals. Even though eHealth polls Alcatel elements every 15 minutes by default, statistics for these Frame Relay paths are available only every 60 minutes. Consequently, when eHealth polls these elements, only every fourth poll is successful.

If errors persist after you wait at least four import-polling intervals, contact Alcatel Customer Support for assistance.

Polling Problems

2. Change the eHealth import polling interval or the NM statistics collection period if necessary.

In most cases, the eHealth import polling interval should match the statistics collection period on the Alcatel 5620 NM. For example, if you are polling Alcatel elements that have statistics collected every 60 minutes, you might want to change the pollInterval value to 60.

To change the eHealth import polling interval, you can specify a new value for the pollInterval field during setup. The value of the pollInterval field is stored in the $NH_HOME/modules/alcatelNm directory on the eHealth system in one of the following files:

module.init – If the field was changed during setup.

module.defaults.init – If the field was not changed.

To change the statistics collection interval on the Alcatel NM, reinstall the Statistics Collector software.

Note: For more information, see your Alcatel documentation.

3. If the message indicates an error between the Statistics Collector and the system on which the element resides, contact Alcatel Customer Support for assistance.

You must provide the Alcatel Customer Support representative with the names of the Alcatel elements that are experiencing problems.

4. If the message indicates that statistics collection is not enabled for this element on the Alcatel 5620 NM, enable statistics collection for the element:

a. Display the List Statistics dialog on the Alcatel 5620 NM.

b. Create a list of the elements that you want to include in eHealth reports.

c. Make sure that the status of each element in this list indicates that statistics are being collected.

Note: For information about enabling statistics collection on the Alcatel 5620 NM, see your Alcatel documentation.

5. If you turn off statistics collection for an element on the Alcatel 5620 NM, you must manually turn off polling for the element in the eHealth poller

configuration.

You cannot automatically disable polling in the eHealth poller configuration by running nhConfig. The same requirement applies if you turn on statistics collection for an element on the Alcatel 5620 NM for an element that is already in the poller configuration.

More information:

Index Values for Alcatel Elements (see page 39)

Polling Problems

Missing Elements

Symptom:

Expected elements are missing from an import polling interval.

Solution:

The elements may have been off-line during the configuration import. Verify that the missing elements are online through the Alcatel 5620 NM user interface and then re-import the configuration.

No Data in Reports

Symptom:

Elements are imported, but data does not display in your reports.

Solution:

The elements may have been off-line, or statistics collection may have been disabled for these elements during the configuration import.

Verify that the missing elements are online and enable statistics collection through the Alcatel 5620 NM user interface. Then reimport the configuration.

No Data for Elements

Symptom:

Data does not display for any elements.

Solution:

This error could indicate a problem caused by the Alcatel 5620 Statistics Collector.

Verify that statistics files are in the /opt/netmgt/stats/format directory and are not zero-length.

Note: For troubleshooting information for your Alcatel 5620 Statistics Collector, see your Alcatel documentation or Alcatel Customer Support.

Polling Problems

FastBUS Elements Not Imported or Polled

Symptom:

FastBUS elements are not imported or polled.

Solution:

This version of eHealth – Alcatel does not support configuration extraction for FastBUS elements.

eHealth – Alcatel does support statistics collection for converted Newbridge FastBUS elements. If you chose to convert your Newbridge elements to Alcatel elements during the eHealth – Alcatel installation, enable polling for these elements in the poller configuration.

Missing Statistics Data

Symptom:

Statistics data is not available on the Alcatel 5620 NM for a particular Alcatel element, and error messages appear in the Import Polling Status window and in the $NH_HOME/log/pollerStatus/messages.import.log file.

Solution:

Possible causes for these errors include the following:

Statistics collection might not be enabled for this element on the Alcatel 5620 NM.

Statistics collection is only partially enabled.

Network traffic may not be associated with the element. If an element has no traffic, it does not appear in the statistics data files that eHealth – Alcatel imports.

Statistics data might be unavailable for this element during the current collection period.

Polling Problems

Complete the following steps to identify and troubleshoot the problem:

1. Be sure that statistics collection is enabled on the Alcatel 5620 NM for each element that you want to include in eHealth reports:

a. Display the List Statistics dialog on the Alcatel 5620 NM.

b. Create a list of the elements that you want to include in eHealth reports.

c. Make sure the status of each element in this list indicates that statistics are being collected.

d. Confirm all statistics are being collected. Partial collection results in bad polls and reports with 0 value.

Note: For information about enabling statistics collection on the Alcatel 5620 NM, see your Alcatel documentation.

2. Determine whether network traffic is flowing through the element:

a. Display the Network Performance Monitor window for the element you want to test on the Alcatel 5620 NM.

b. Start monitoring statistics for the element and display a graph of the results.

No statistics for the element or statistics values consisting of zeros indicate that the element has no traffic. Elements without traffic do not have entries in the statistics files that eHealth – Alcatel imports.

3. Determine whether the element has an entry in the Alcatel statistics file for the specified interval.

More information:

Alcatel Statistics Files (see page 63)

Missing Performance Variables

Symptom:

When I eHealth polls the Alcatel NM, performance data is missing.

Solution:

Reconfigure the Alcatel 5620 NM to collect all performance variables for polled elements.

The $NH_HOME/modules/alcatelNmVarFile.csi file controls how eHealth manages missing performance data. Default behavior sets each variable in the file to no, which causes eHealth to discard any polls with incomplete data. If the variables are set to yes, eHealth keeps the polls that contain partial data and substitutes 0 for any missing variables. Reports on those missing variables will have a consistent value of 0.

Polling Problems

Data Gaps in eHealth Reports

Symptom:

eHealth reports occasionally display gaps in the data for Alcatel elements.

Solution:

Data gaps can result from any of the polling problems (see page 55).

You can identify and troubleshoot the problem as follows:

1. Examine the Import Polling Status window or the $NH_HOME/log/pollerStatus/messages.import.log file.

Look for error messages logged for the Alcatel element on the date on which the gap occurred. The error messages usually explain the cause of the data gaps.

2. Examine the Alcatel statistics file on the NM (if the file is available) for the specified date and collection interval.

The entries in the statistics file might help explain the cause of the data gaps.

Alcatel Statistics Files

eHealth imports statistics files for Alcatel elements from the Alcatel 5620 NM to generate LAN/WAN Health, At-a-Glance, Top N, and Trend reports. Typically, Alcatel statistics files reside in the /opt/netmgt/stats/data directory on the Alcatel 5620 NM. The name of the statistics file includes the date and interval when the statistics were collected and has a .data extension.

Example: The file 1999.06.30.25.data contains information about statistics collected on June 30, 1999 during interval 25.

The Alcatel 5620 NM stores statistics files at 15-minute intervals. The intervals are numbered from 1 through 96, based on the number of hours since 12:00 a.m. (midnight) Greenwich Mean Time (GMT). If gaps appear in the data for Alcatel elements on eHealth reports, you can examine statistics files to troubleshoot the cause. You must convert the eHealth report time to the corresponding Alcatel interval, however, to determine which statistics files to examine.

Polling Problems

Examine the Alcatel Statistics File for the Cause of Data Gaps

If gaps appear in the data for Alcatel elements on eHealth reports, you can examine the Alcatel statistics file for the specified date and collection interval to troubleshoot the cause of the gaps.

To examine the Alcatel statistics file for the cause of data gaps

1. Note the time of the eHealth report containing the data gaps.

Example: Assume that the eHealth report was generated on June 10, 1999 at 3:30 p.m. Eastern Daylight Time (EDT).

2. Convert the eHealth report time to the number of hours since 12:00 a.m. GMT.

Example: In the EDT time zone (GMT + 4 hours), the time 3:30 p.m. would be 15.5 hours since 12:00 a.m. GMT plus 4 hours, or a total of 19.5 hours.

3. Obtain the Alcatel interval number by multiplying the result of the previous step by 4 because four 15-minute intervals are in one hour.

In this example, the Alcatel interval number is 78 (19.5 multiplied by 4).

4. Identify the relevant Alcatel statistics file to examine.

In this example, you should look for an Alcatel statistics file named 1999.06.10.78.data in the /opt/netmgt/stats/data directory on the NM.

5. Log in to the Alcatel 5620 NM system.

6. Change to the /opt/netmgt/stats/data directory and make sure it contains the statistics file you want to examine.

7. Convert the statistics file to ASCII format by executing the following command:

/opt/netmgt/stats/bin/ST_DisplayElem filename.data > filename.txt

filename.data

Specifies the original Alcatel statistics file.

filename.txt

Specifies the readable ASCII version.

Example: Convert a Statistics File to an ASCII Text File

The following command converts the statistics file named 1999.06.10.78.data to an ASCII text file named 1999.06.10.78.txt:

/opt/netmgt/stats/bin/ST_DisplayElem 1999.06.10.78.data > 1999.06.10.78.txt

Polling Problems

8. Examine the statistics file to determine the possible cause of the data gaps.

The statistics file should contain an entry for each Alcatel element. The entries contain index values for each element (see page 39). Knowing how eHealth uses these index values to uniquely identify Alcatel elements can help you map eHealth elements to entries in the statistics file and find the information that you need.

Note: For information about interpreting the statistics file, see your Alcatel documentation.

Appendix A: Setup Checklists

Appendix A: Setup Checklists During the setup process, you have to provide information about your Alcatel
Appendix A: Setup Checklists During the setup process, you have to provide information about your Alcatel

During the setup process, you have to provide information about your Alcatel system, QCnetwork Services software, and eHealth system. The setup checklists describe the setup prompts in the order in which they appear. Complete these checklists before running the setup program so that your system information will be available when you run the program.

This section contains the following topics:

Alcatel 5620 NM System Checklist (see page 67) QCnetwork Checklist (see page 68) eHealth System Checklist (see page 69)

Alcatel 5620 NM System Checklist

The questions in the following checklist correspond to the first set of questions in the setup program and relate to your primary Alcatel 5620 NM system.

Note: Fields requiring data can be case-sensitive, so make sure that you record uppercase and lowercase letters accurately.

Description

Your System Information

The hostname of the primary Alcatel 5620 NM system.

The user name that eHealth uses to log in to the Alcatel 5620 NM system.

Example: admin

Note: This user name must provide access to the operating system and to the Alcatel 5620 statistics directory.

The password for this user on the NM system.

The hostname of the fail-over Alcatel 5620 NM system, if any.

The user name that eHealth uses to log in to the fail-over Alcatel 5620 NM system, if any.

The password for this user on the fail-over NM system.

QCnetwork Checklist

QCnetwork Checklist

Complete one checklist for each system that you want to configure for the QCnetwork Services software.

Note: Fields requiring data can be case-sensitive, so make sure that you record uppercase and lowercase letters accurately.

Description

Your System Information

The primary QCnetwork port that eHealth uses to connect to the Alcatel 5620 NM to extract configuration information.

Default: 8248

The user name that eHealth uses to log in to the Alcatel 5620 QCnetwork server.

Example: QCF_config

This name must be unique. Do not use the default user name.

Note: This user name must provide access to the network partitions in which eHealth places configuration information for your Alcatel elements.

The password for this user on the NM system.

Would you like the configuration extraction to import ATM and Frame Relay paths for which source or destination speed cannot be determined?

Note: If you specify yes, you must set those speed values manually or provide a DCI rule to set them during import.

eHealth System Checklist

eHealth System Checklist

The questions in the following checklist correspond to questions relating to your eHealth system.

Note: Fields requiring data can be case-sensitive, so make sure that you record uppercase and lowercase letters accurately.

Information That You Are Prompted For

Your System Information

The eHealth polling interval in minutes. This interval should be approximately the same as the rate at which the Alcatel 5620 NM collects data.

Default: 15

Limits: 15, 30, 45, 60, 75, 90, 105, or 120

The maximum time (in minutes) to allow for the completion of a configuration extraction.

Default: 15

Limits: 1 to 1440

Index

Index A adding elements • 28 Alcatel API Services software • 50 element types supported •
Index A adding elements • 28 Alcatel API Services software • 50 element types supported •

A

adding elements • 28 Alcatel API Services software • 50 element types supported • 25 enabling statistics collection • 18, 58 statistics collection schedule • 46, 58 Statistics Collector software • 55 statistics files, examining • 63 troubleshooting polling problems • 55 Alcatel 5620 NMS API Services software • 50

availability, latency, and reachability stati •

47

enabling statistics collection • 18, 58 primary • 11, 50 secondary • 11, 50 statistics collection schedule • 46, 58 Statistics Collector software • 18, 55 statistics files, examining • 63 synchronizing time with • 11 troubleshooting configuration problems • 50 troubleshooting polling problems • 55 verifying version numbers • 14 API user, Alcatel creating LAN/WAN groups for • 32 ATM elements, Alcatel index values • 39 LAN/WAN group names • 32 list of supported types • 25 statistics collected • 47 availability in eHealth reports • 47

C

commands nhConfig • 28, 29 nhSchedule • 34 configuration problems • 50 cannot connect to the NM • 50 CIR/SIR/speed error • 54 configuration process occupies QCnetwork API resources • 53 eHealth cannot log in to the IM • 52 login retries exceed number permitted • 53

configuring elements about • 25 Alcatel types supported • 25 creating LAN/WAN groups • 32 diagram • 25 index values • 39 running nhConfig command • 28 scheduling jobs • 34 steps for • 28 connecting to NMS • 50, 56 CORBA ports, opening in the firewall • 13

D

data analysis schedule • 47 data file, defined • 38 data gaps in reports, troubleshooting • 63 DCI files. See element files • 38 defining elements, examples of • 40 diagrams configuration process • 25 import polling process • 44 disabling polling for an element • 45

E

eHealth - Alcatel about • 9 configuring elements • 25 importing statistics • 43 running installation program • 24 running reports • 46 troubleshooting • 49 eHealth - Alcatel, about • 9 eHealth reports and data analysis schedule • 47 availability, latency, and reachability • 47 matching to Alcatel interval • 63 running • 46 scheduling • 47 troubleshooting data gaps • 63 unsupported • 47 element files about • 38 defined • 38 index values • 39 sample element definitions • 40

temporary • 31 elements adding • 28 Alcatel statistics collected • 47 Alcatel types supported • 25 configuring • 28 creating LAN/WAN groups • 32 defining, examples of • 40 disabling polling • 45 excluding • 28 grouping • 28, 38 importing • 28 index values • 39 modifying • 28 troubleshooting • 49 examples element definitions • 40 LAN/WAN groups • 32, 34 excluding elements 28 extraction process creating LAN/WAN groups 32 customizing 31

F

Frame Relay elements, Alcatel index values • 39 LAN/WAN group names • 32 list of supported types • 25 sample definitions • 40 statistics collected • 47

G

gaps in reports, troubleshooting • 63 grouping elements • 28, 38 groups, LAN/WAN about • 32 naming • 32

I

import polling about • 20 changing the interval • 58 diagram • 44 disabling for elements • 45 elements • 28 missed polls • 46, 58 statistics • 43 troubleshooting • 55 import polling interval, about • 44

Import Polling Status window • 20, 58 importing statistics data files • 45 index values in element files about • 39 using to troubleshoot • 63 installation problems • 49 invalid license error • 50 version error • 49 installing running installation program • 24 troubleshooting • 49 using log file • 25