VistaLink 3.

0 for AlcatelLucent 5620 SAM

Installation Guide

2
Part Number: 34_302_000_30 Copyright 1996-2008 InfoVista S.A. All rights reserved. InfoVista, VistaView, VistaBridge, VistaMart, VistaDiscovery, VistaPortal, VistaFoundation , VistaInsight, VistaLink, Vista Plug-In, VistaProvisioner, Vista Troubleshooter, VistaCockpit, and Vista Watch are trademarks or registered trademarks of InfoVista S.A. in the United States and/or other countries. The information contained in this document is the property of InfoVista S.A. No part of this publication may be reproduced in any form (including photocopying or electronic storage on any medium) or by any means or used to make any derivative work (such as translation, transformation or adaptation) without the express written permission of InfoVista S.A. The information contained in this document is subject to change without notice and does not carry any contractual obligation for InfoVista. InfoVista reserves the right to make changes to any products or services described in this document at any time without notice. InfoVista shall not be held responsible for the direct or indirect consequences of the use of the information contained in this document. Brand and product names mentioned in this publication may be registered trademarks or trademarks of their respective holders.

web : www.infovista.com E-mail: [email protected]

VistaLink 3.0 for Alcatel-Lucent 5620 SAM Installation Guide

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Contents
1 Getting Started with VistaLink 3.0 for Alcatel-Lucent 5620 SAM
Whats new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New features in VistaLink 3.0 for Alcatel-Lucent 5620 SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 8 8 8 8 9

VistaLink for Alcatel-Lucent 5620 SAM overview

Technology overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alcatel-Lucent 5620 SAM main features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VistaLink features and objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How does VistaLink work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Architecture and data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11 11 13 13

Installation and configuration

Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alcatel-Lucent 5620 SAM Database, Server and Client prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . VistaFoundation kit prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing VistaLink on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing VistaLink on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directories and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating memory spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the VistaMart parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the zoneset parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the VistaBridge parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the user credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the SAM host parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the SAM FTP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the SAM SSH parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the directories and files parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 15 16 17 17 17 20 22 23 23 23 24 25 25 25 26 27 27 27

Installation Guide

VistaLink 3.0 for Alcatel-Lucent 5620 SAM Setting the naming and retrieval rules parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the timeout parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the history management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the filters parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional configurations in sam_cfg.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring filter interface in the sam_cfg.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the name of the log file in sam_cfg.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating new SAM ZoneSet and Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing VistaView libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing event message formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new InfoVista Server object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the VistaLink environment on VistaPortal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Page Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing users and groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About timestamping in VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28 29 29 30 31 32 32 32 33 33 36 37 37 39 40 41 43 43

Data files generation

Topology data generation (manually) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching the topology script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provisioning VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating and provisioning the topology data in one script (OPTIONAL) . . . . . . . . . . . . . . . . . . . . . Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance data generation (manually) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching the performance script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing the performance data for a specified period of time . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provisioning VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating the performance data in one script (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling files generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling tasks with VistaCockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling tasks with the system tool (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error of type 1 - file configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error of type 2 - network failure, connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error of type 3 - memory problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 46 47 47 49 49 51 51 52 52 53 53 54 55 55 61 63 63 64 69

Installation Guide

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Customizing VistaLink
How to customize VistaLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping file overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XML structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 71 73 74

Instances naming conventions

SAM attributes definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Instances names syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Supported classes and MIB

Alcatel-Lucent classes supported by VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB activated by default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB to activate (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 84 84 86

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Installation Guide

1 Getting Started with VistaLink 3.0

for Alcatel-Lucent 5620 SAM

This chapter introduces you to the new features of VistaLink 3.0 for Alcatel-Lucent 5620 SAM and provides key information on the documentation (i.e:purpose, intended audience, organization, related documentation).

"Whats new" on page 7 "Documentation overview" on page 8

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Whats new

Whats new
This section introduces you to the new features available with the VistaLink 3.0 for Alcatel-Lucent 5620 SAM. It also provides a brief overview of the new features related to the documentation delivered with this version.

New features in VistaLink 3.0 for Alcatel-Lucent 5620 SAM

This new release comprises of the following new features: > > > > > > New product Installer Configuration wizard (no more need to edit configuration files) Provisioning of topology using HTTP API (no more need to install VistaLink on VistaMart server) Statistic files compression to improve transfer time from SAM server Process of statistics per period of time to allow better integration on large volume of data Support of the new VistaPortal 4.0 features > New Portal pages designed to use Page Package, Extended Object Navigator (tree and dashboard), event in Graph on Demand and Matrix Reports. Sets of pages for Service Manager / Network Engineer / Customer users New indicators that provide statistics on VistaMart Service groups that compute the load distribution of the SAP Queues Ingress & Egress and the Response Time distribution (pie chart) of the OAM Probes.

New Service and SAP Key Performance Indicators (KPIs):

> > > >

Capacity Planning KPIs ( utilization, forecast, baseline, saturation, time to saturation Support of LAG (Link Aggregation Group) Temperature KPI calculation (with specific workflow) Support of the new VistaMart 4.0 features: New InfoVista events that allow intelligent display of incidents in VistaPortal pages. MTU ping Tunnel ping Service Site ping CPE ping ICMP ping VCCV ping

>

Support of new OAMs:

>

Manage the filtering of physical interfaces on state (allows down interfaces to be kept in the inventory) Getting Started with VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installation Guide - Chapter 1

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Documentation overview

Documentation overview
This section describes the purpose, intended audience and organization of this guide, and provides information on related documentation delivered with VistaLink 3.0 for Alcatel-Lucent 5620 SAM.

Purpose
This Installation Guide contains technical information that explain how to install and configure VistaLink 3.0 for Alcatel-Lucent 5620 SAM.

Intended audience
IT staff familiar with Windows or/and Solaris environments. The person in charge of installing and configuring must be familiar with: > > > InfoVista products of the VistaFoundation XML syntax Alcatel-Lucent APIs (for example: attributes, classes, packages)

Organization
This table describes the organization of the Installation Guide, enabling you to directly access the chapter you are interested in.
Chapter "VistaLink for Alcatel-Lucent 5620 SAM overview" on page 10 "Installation and configuration" on page 14 Description

This section introduces you to VistaLink 3.0 for Alcatel-Lucent 5620 SAM . This section explains how to install and configure VistaLink 3.0 for Alcatel-Lucent 5620 SAM. This section explains how to generate topology files and performance data files. After each generation, you must import the results into VistaMart, either manually or automatically. This section describes how to customize VistaLink using the mapping file samVbMapping.xml.

"Data files generation" on page 45

"Customizing VistaLink" on page 70

Installation Guide - Chapter 1

Getting Started with VistaLink 3.0 for Alcatel-Lucent 5620 SAM

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Documentation overview

Chapter "Instances naming conventions" on page 77

Description

This appendix lists the naming conventions used to define instances. The tables give the necessary information to understand the Instances names. This appendix lists the classes and MIB supported by VistaLink. You can use this list to set the polling interval of the MIB.

"Supported classes and MIB" on page 81

Related documentation
You can access the document either through the doc directory in the Installation package or directly from one of the VistaPortal pages.

USER ONLINE HELP You use this html online help to understand the technology VistaLink 3.0 for Alcatel-Lucent 5620 SAM and navigate through the VistaPortal pages. This online help provides a detailed description of VistaPortal pages and the definition of Key Performance Indicators.

Installation Guide - Chapter 1

Getting Started with VistaLink 3.0 for Alcatel-Lucent 5620 SAM

2 VistaLink for Alcatel-Lucent 5620

SAM overview

This chapter introduces you to VistaLink for Alcatel-Lucent 5620 SAM.

"Technology overview" on page 11 "How does VistaLink work?" on page 13

10

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Technology overview

11

Technology overview
The 5620 SAM (Service Aware Manager) is a network management system used to manage devices, such as the Alcatel-Lucent routers 7750 SR, 7250 SAS and 7450 ESS. VistaLink is an InfoVista solution that allows you to manage the 5620 SAM.

Alcatel-Lucent 5620 SAM main features

The 5620 SAM provides details about networking information on Alcatel-Lucent routers and their associated interfaces and services. The 5620 SAM is composed of: > > > a database, which stores network objects and configurations. a client, which provides a GUI to configure IP network elements. a server, which mediates between the 5620 SAM database, the 5620 SAM client, and the network.

The 5620 SAM discovers devices and reconciles them to the 5620 database. The 5620 SAM collects two types of performance data (also referred to as statistics): > > accounting statistics for SAPs and network ports, which can be used for billing and traffic-analysis purposes. network object performance statistics, for control plane, data forwarding plane, and device utilization statistics.

OAM Operations, Administration and Maintenance

This expression is used to describe the costs, tasks involved or other aspects of operating, administering and managing a telecommunication network. The 5620 SAM provides a series of OAM tools to monitor and administer the network.

SAP QUEUES A SAP (Service Access Point) is a point of communication exchange

between an application and the LLC or between layers of software.

SDPS Service Distribution Path. The 5620 SAM uses this term interchangeably with
service tunnel. A service tunnel acts as a logical way of directing traffic from one device to another device. The service tunnel is provisioned to a specific encapsulation method.

VistaLink features and objectives

VistaLink for Alcatel-Lucent 5620 SAM provides real-time performance management features and service level assurance capabilities across networks, systems and applications. As a multi-vendor, multi-technology integration solution, VistaLink consolidates accounting and performance statistics from Alcatel-Lucent devices managed by the

Installation Guide - Chapter 2

VistaLink for Alcatel-Lucent 5620 SAM overview

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Technology overview

12

5620 SAM, as well as performance data of the rest of the network infrastructure within a single end-to-end view. VistaLink is an InfoVista solution that enables you to put the information coming from the 5620 SAM into the InfoVista Model.

The VistaLink solution provides: > > > Synchronization between the Alcatel-Lucent 5620 SAM topology/inventory and VistaFoundation objects using the SAM Open Interface. VistaCockpit workflows to schedule the topology and performance data generation. "Ready to use" reports that define the KPIs (Key Performance Indicators) useful to monitor the L2/L3 Services provisioned by the 5620 SAM. Monitoring is provided at various levels: technical, capacity planning and SLA management. HTTPS and SFTP compatibility. Network failure management. Presentation engines (the VistaPortal Family) that present those performance data in a variety of reports and formats. Complete of these reports to address customers needs: internal or external reporting, capacity planning or troubleshooting, etc. Full compatibility with VistaInsight for Network.

> > > > >

Installation Guide - Chapter 2

VistaLink for Alcatel-Lucent 5620 SAM overview

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

How does VistaLink work?

13

How does VistaLink work?

The following paragraphs help you understand how VistaLink works with AlcatelLucent 5620 SAM.

Architecture and data flow

VistaLink is a Java program that utilizes the 5620 SAM API to extract topology and performance data of the devices managed by the 5620 SAM. The following schema shows the interaction between InfoVista products and AlcatelLucent 5620 SAM in a typical architecture.
NOTE

The actions illustrated below take place after the 5620 SAM collects topology and performance data from the devices. These data are stored in the 5620 SAM database).

When you launch VistaLink processes

Topology data generation

> VistaLink sends a request to the Alcatel-Lucent 5620 SAM server to retrieve
topology data and stores them in two XML files. The two XML data files are consolidated in a third XML file. The 5620 SAM server gets these data from its database.

> Topology data files are imported into VistaMart via the Inventory Manager.
Performance data generation

> VistaLink sends a request to Alcatel-Lucent 5620 SAM server to retrieve the
performance data and stores them in CSV files and creates corresponding XML files. The 5620 SAM server gets these data from its database.

> Performance data files are then imported into VistaMart via VistaBridge .
Reporting in VistaPortal

The User can analyze the reports via VistaPortal User interface.
NOTE

VistaCockpit manages VistaLink processes via specific workflows.

Installation Guide - Chapter 2

VistaLink for Alcatel-Lucent 5620 SAM overview

3 Installation and configuration

This section explains how to install and configure VistaLink 3.0 for Alcatel-Lucent 5620 SAM. This chapter includes the following sections:

"Installation prerequisites" on page 15 "Installing VistaLink" on page 17 "The Configuration Wizard" on page 23 "Configuring VistaMart" on page 33 "Installing the VistaLink environment on VistaPortal" on page 39 "Configuring VistaLink" on page 43

14

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installation prerequisites

15

Installation prerequisites
NOTE

Please refer to the Readme file for more details on the products versions, recommended hardware, and supported platforms.

Before installing VistaLink ensure you follow the prerequisites listed below.

Alcatel-Lucent 5620 SAM Database, Server and Client prerequisites

> You must create a user with OSS Management permission.
NOTE

For further information on how to create users refer to Alcatel-Lucent 5620 Service Aware Manager User Guide.

>

Configure the Accounting to specify: The file policy, that is how often log files of collected statistics counters are collected and managed. The accounting policy, that is the types of statistics collected on a per-usage and per-service basis.
NOTE

For further information on how to configure the Accountings refer to AlcatelLucent 5620 Service Aware Manager User Guide.

>

Ensure all MIBs referenced in "Supported classes and MIB" on page 81 are enabled.
NOTE

For further information on how to enable the MIBs refer to Alcatel-Lucent 5620 Service Aware Manager User Guide.

VistaFoundation kit prerequisites

NOTE

For detailed information on supported platforms, supported versions of VistaFoundation kit, refer to the README file available in the installation package.

Ensure you have installed the products of the VistaFoundation in the following order:

1 VistaCockpit 2 VistaMart Oracle database 3 VistaMart Server 4 VistaPortal 5 VistaMart Client 6 VistaBridge on the same machine as the one hosting VistaMart Client.
Installation Guide - Chapter 3 Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installation prerequisites

16

WARNING Ensure you have installed VistaMart Client before you install VistaBridge.

NOTE

For detailed information please refer to the Installation guides provided with InfoVista products. Make sure that you install or upgrade each component according to the precise versions supplied with the kit.

Installation steps
The installation and configuration take place in the following order:

1 Installing VistaLink directories and files (see "Installing VistaLink" on page 17). 2 Configuring VistaMart for 5620 SAM (see "Configuring VistaMart" on page 33). 3 Configuring VistaPortal for 5620 SAM (see "Installing the VistaLink environment
on VistaPortal" on page 39).

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing VistaLink

17

Installing VistaLink
This section addresses the installation of VistaLink 3.0 for Alcatel-Lucent 5620 SAM in the Windows and Solaris environment.

Installing VistaLink on Windows

This section addresses the installation of VistaLink on Windows .
NOTE

You must launch the VistaLink installation on the machine where you have installed the VistaMart Client and VistaBridge.

Install VistaLink on Windows 1 From the VistaLink installation package, launch setup.exe. The Installer appears. 2 Click Next. The license agreement appears: select I accept the terms of the
license agreement.

3 Click Next . The Setup Readme file appears.

You can click Open in web browser to view the Readme file in a browser.

4 Click Next . Select the installation path. By default this directory is: <InfoVista
installation directory>. You have two options: Click Choose to change the path. Click Restore Default Folder to reset the path to the default directory.

5 Click Next . The InfoVista Products configuration appears which displays the
InfoVista products the setup configures.

6 Click Next . A window appears to summarize the installation parameters: ensure all
parameters are correct (Installation directory, shortcut directory, Disk Space Information). Click Previous to change the parameters.

7 Click Install to copy files to disk, or click Cancel to cancel the installation and then
Quit to confirm you want to cancel.

Installing VistaLink on Solaris

This section addresses the installation of VistaLink on Solaris .

Creating Solaris users and groups for VistaLink

Installing and executing VistaLink in the Solaris environment requires specific users and groups as listed below.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing VistaLink

18

How to create users and groups [Solaris 10 only]

You can create either remote or local users and groups.

CREATING USERS AND GROUPS (REMOTE) To declare users/groups ( infovista group,

infovista user and <john> user) as part of the user directories (LDAP, NIS, etc.), your system administrator must refer to the contents of the createinfovistauser.sh script (located in the installation package) in order to manually create them on the directory system and with the proper privileges mapping before the installation. The system administrator can create several users of type <john>.

CREATING INFOVISTA USER AND INFOVISTA GROUP To create the infovista user and the
infovista group locally, the system administrator launches the installer. At the beginning of the installation, the installer verifies that both the infovista group and the infovista user exist. Depending on what the installer finds on the host, the installer performs the workflow:

1 The installer detects the infovista user and the infovista group. 2 The installer does not detect the infovista user or the infovista group. 3 The installer only detects either the infovista user or the infovista group.
See below for detailed description of the workflow:

1 If the installer detects infovista user and infovista group, the installation
continues.

2 If the installer does not detect the infovista user or the infovista group, it creates
them locally. The installer executes createinfovistauser.sh, which creates the infovista group and the infovista user with its privileges. This guarantees that the infovista user will be able to run other InfoVista services. The createinfovistauser.sh script is located in the installation package.

3 If the installer detects only the infovista user or only the infovista group, the
installation stops. The system administrator must: Delete the element detected by the installer ( infovista user or infovista group). Launch the installer.

At the end of the installation, setprivs.sh is executed . This script grants the users of the infovista group the necessary execute/write/read rights on the directories and files set by the installer. The setprivs.sh script is located in <<Product Name> installation directory>/bin.
NOTE

Each time you install a hotfix, the hotfix installer runs the setprivs.sh script. (You must launch it manually if you do not use the hotfix installer)

WARNING Do not use the regular adduser command to create the local infovista user.

CREATING A <JOHN> USER

The <john> user represents any user that launches the VistaLink application. The system administrator can create several users of type <john>.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM For each new <john> user, the system administrator must:

Installing VistaLink

19

1 Declare the <john> user as being part of the infovista group. 2 Declare a home directory specific to the <john> user. 3 Ensure the <john> user has the sufficient rights to write on his home directory. We
recommend that you set the umask as follows: /usr/bin/umask -S u=rwx,g=rwx,o=.

4 Execute (example with <john> user) grep john /etc/passwd to ensure the user
has a dedicated home directory. As a result you obtain different data separated by :: john:x:501:59:This is the john account:/home/john:/bin/bash, where /home/john indicates the user home directory.

5 Execute (example with <john> user) ls -ld /home/john to ensure the user home
directory has the correct rights aSolarisnd is part of the infovista group: As a result you obtain: drwxrwx--- 176 john infovista 16384 jun 18 08:50 /home/john/, where infovista is the name of the group and drwxrwx--- indicates the rights set for the home/john/ home directory. The rights must correspond to the umask set with step 3.
NOTE

After upgrading the operating system to Solaris 10, we recommend reinstalling the <Product Name> application in order to redefine the user identities and file rights. This will enable you to start from a clean user environment.

Installing VistaLink on Solaris

This section addresses the installation of VistaLink on Solaris.
NOTE

You must launch the VistaLink installation on the machine where you have installed the VistaMart Client and VistaBridge.

Install VistaLink directories and files 1 From the VistaLink installation package, launch setup.bin. The Installer appears. 2 Click Next. The license agreement appears: select I accept the terms of the
license agreement.

3 Click Next. The Setup Readme file appears.

You can click Open in web browser to view the Readme file in a browser.

4 Click Next . Select the installation path. By default this directory is: <InfoVista
installation directory>. You have two options: Click Choose to change the path. Click Restore Default Folder to reset the path to the default directory.

5 Click Next. The InfoVista Products configuration appears which displays the
InfoVista products the setup configures.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing VistaLink

20

6 Click Next. A window appears to summarize the installation parameters: ensure all
parameters are correct (Installation directory, shortcut directory, Disk Space Information). Click Previous to change the parameters.

7 Click Install to copy files to disk, or click Cancel to cancel the installation and then
Quit to confirm you want to cancel.

Directories and files

In the <InfoVista installation directory>, open VistaLinks\SAM and ensure it contains the following directories:
Directory Description bin cockpit data

> Contains VistaLink scripts (sam_global, sam_topo, sam_stat, sam_provisioner, sam_VB, etc) and configuration files ( sam_cfg.xml, samVbMapping.xml). > Contains the four workflows to import in VistaCockpit (see "Scheduling tasks with
VistaCockpit" on page 55). Contains the data files generated with the scripts. This directory stores the results coming from the latest execution:

> pairs of CSV/XML files corresponding to performance data.(one pair by Vista). > XML topology files ( samTopo_Basic.xml, samTopo_Proxy. xml, samTopo.xml) > .lastDoneDir.txt that contains the subdirectory name (located in the data directory)
storing the results of the latest execution. VistaCockpit uses this file to notify an error occurring during the import process (i.e: during the VistaMart provisioning). See also: "During the import process (when VistaLink connects to VistaMart to import data files)" on page 67

> tmp directory: contains XML files for a temporary period. The XML files contain the results
of the requests sent to the SAM Server. Once the results are converted into topology and performance data files, the XML files are stored in the done directory.
doc

Contains VistaLink Installation guide.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing VistaLink

21

Directory Description done

Contains two subdirectories topo and stat.

topo stores: > the XML files containing the results of requests for the topology data, in subdirectories
sorted by date and time

> the XML topology files named with date and time. stat stores the XML files containing the results of requests for the performance data, in subdirectories sorted by date and time. Topo and stat directories are empty when you install VistaLink. If you delete them, they are automatically created after the first script execution.
NOTE

This directory is often used by InfoVista Support team in case of issue because it is a backup of requests between VistaLink and SAM. You must use the FindtoFile request mode to store the requests results. You can decide the period for which you want to keep the XML files in topo and stat using the keepTopoHistory and keepStatHistory tags in the sam_cfg.xml file.

lib log

Contains .jar files for VistaLink including the sam.jar file. Contains two sub-directories export and import.

export contains the log files that trace the activity of: > the connection between SAM Server and VistaLink for topology data generation ( Summary_Topo.log) > the connection between SAM Server and VistaLink for statistics data generation (Summary_Stats.log) import contains the log files that trace the activity of: > VistaMart provisioning with topology data ( ProvisioningStatus.log) > statistics files generation by Vista ( Router.log, LANWANInterface.log, etc.) > VistaMart provisioning with statistics data ( PushStatus.log)
portal vviews

Contains the zip file storing VistaPortal report templates and pages. This directory contains the following:

> The SAM30_Basic_VV_Package.zip file. > Contains the Config directory that comprises of the new file SAM30_Vmart_config.zip.
For more information on how to import this new file, see "Uninstalling VistaLink" on page 22.
HotFixes Contains the latest hotfix for VistaPortal, VistaBridge and VistaMart. registry jre

Contains the installation engine for the hotfix. contains the jdk used by VistaLink.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing VistaLink

22

Uninstalling VistaLink
Below is the procedure for uninstalling VistaLink on Windows or Solaris.
T

Uninstall VistaLink on Windows 1 From the SAM\uninst\launcher launch uninstall.exe . The UnInstaller window
appears.

2 Click Uninstall to uninstall VistaLink. 3 Click Done to complete the installation.

T

Uninstall VistaLink on Solaris 1 Open a command line window and run the command
<installation directory>\....SAM\uninst\launcher>uninstall where <installation directory> is where your VistaLink is installed. The UnInstaller window appears.

2 Click Uninstall to uninstall VistaLink. 3 Click Done to complete the installation.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

The Configuration Wizard

23

The Configuration Wizard

The Configuration Wizard sets up the VistaLink Applications and Services that interact with the SAM server and the VistaMart Repository. Being part of the whole installation package, it is launched automatically as soon as the installer has completed its tasks. At that time, parameters shared by the connected applications are passed from the installer to the Configuration Wizard, there by ensuring that you are not prompted twice for identical data. However, you will be able to run it separately for modifying previously installed components. The configuration process is platform-independent and applies the same way to both Windows and Solaris environments. The Help button in each screen enables you to access the online help that assists you with the configuration process.
NOTE

A valid web browser needs to be installed to access the help page from the Configuration Wizard.

Starting the Configuration Wizard

T

Run the Configuration Wizard 1 For Windows:

From the Start menu, select InfoVista\VistaLink SAM Configuration Wizard (Windows) or Run vistalink_sam_configuration_wizard.exe from the bin directory. Log in as the infovista user and go to the bin directory (enter the command opt/InfoVista/VistaLinks/SAM/bin). Run the ./ vistalink_sam_configuration_wizard.sh command.

2 For Solaris:

Allocating memory spaces

The JVM Memory Parameters page enables you to adjust the memory allocated to VistaLink. The default allocated memory is 1024 MB. The amount of memory used for the different processes depends on your infrastructure. The more instances you have, the more you must increase the size of the memory used by the processes. In order to optimize your operating environment, we recommend that you set the amount of memory that is allocated to each process.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

The Configuration Wizard

24

Adjust the allocated memory 1 Enter the amount of memory you want to allocate to VistaLink. 2 Click Next .

Setting the VistaMart parameters

The VistaMart parameters provision the topology and performance data into the VistaMart. If the VistaFoundation Kit is 2.0, then the host name is the local host name and the VistaMart connection is a combination of the host name, port number, and the SID of the VistaMart. If the VistaFoundation Kit is 4.0, then the VistaMart Connection is expressed as http://hostname:11080. Also, the host name for the server is the hostname of the system where VistaMart is located.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

The Configuration Wizard

25

Set the VistaMart parameters 1 Enter the VistaMart user name and password. 2 Enter the VistaMart server host name, Oracle port number, and the VistaMart SID. 3 Enter the VistaMart directory., VistaMart Connection, and Http Provisioning URL. 4 Click Next.

Setting the zoneset parameters

This page enables you to change the parameters set for each zone. For more information about zones, refer to "Creating new SAM ZoneSet and Zones" on page 33.
T

Set the Zoneset parameters 1 Enter the parameters for the zones. 2 Click Next.

Setting the VistaBridge parameters

You can define the parameters in VistaBridge to provision the performance data into the VistaMart. This page enables you to define the acquisition rate and time zone for SAM data. For more information about the acquisition rate, refer to the VistaBridge User Guide.
T

Set the VistaBridge parameters 1 Enter the acquisition rate (AR) and time zone for SAM data. 2 Enter the path to the VistaBridge bin directory or click the Browse button to direct
the wizard to the directory.

3 Click Next.

Verifying the user credentials

This page enables the SAM server to validate the user and the user encrypted password. The password is generated by the MD5Hash tool.
NOTE

The SAM user login and password are common to the primary server and to the backup server.

Validate the user 1 Enter the user name and password. 2 Click Next .

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

The Configuration Wizard

26

Setting the SAM host parameters

This page enables you to define the parameters to connect to the primary server and the secondary server. If the VistaLink fails to connect to the primary server of the SAM host, the secondary server takes over the role as primary.

Set the host parameters 1 Enter the IP address or hostname of the machine hosting the SAM server. 2 Enter the port number for receiving SOAP requests. 3 Select the protocol to be used from the drop-down list. 4 If you use https, you must create a KeyStore file using Java's keytool (see the
Java web site at http://java.sun.com) and configure the 5620 SAM server to use HTTPS. This tag refers to the certificate file (.keystore file): enter the path to the.keystore file.

5 Click Next .

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

The Configuration Wizard

27

Setting the SAM FTP parameters

This page enables you to define the parameters to connect to the SAM server via FTP. If the VistaLink fails to connect to the primary FTP host, the secondary host takes over the role as primary.
T

Set the FTP parameters 1 Enter the ip address or hostname of the machine hosting the SAM server. 2 Enter the FTP port number, user login, and password. 3 Enter the FTP directory path where the data files are stored in the SAM server. 4 Select True to activate the passive mode or False to deactivate the passive mode.
When the FTP server is in passive mode it automatically determines the Port number.

5 Select FTP or SFTP depending on the type of mode you want to set. 6 Click Next.

Setting the SAM SSH parameters

The SSH enablement allows you to control and compress the SAM-generated statistical files before transferring them to VistaLink. VistaLink then uncompresses this file before pushing the statistical data into VistaMart.
T

Set the SSH parameters 1 Select True if you want to compress the statistical data files else select False . 2 Enter the SSH host, port number, user login and password. 3 Enter the SSH Directory path where the compressed files are stored in the SAM
server.

4 Click Next .

Setting the directories and files parameters

VistaLink provides two ways to send requests to the SAM server. > In the FindToFile mode, VistaLink sends XML requests to the SAM server. The SAM server generates the answer as a XML files on the SAM server. VistaLink retrieves the XML files using FTP or SFTP (depending on what you set in sam_cfg.xml). This mode requires that you have an FTP server on your 5620 SAM machine and that you know the 5620 SAM output directory (this is configured when you install your SAM server). The requests are then stored in the specified data directory. In Find mode, VistaLink sends XML requests to the SAM server. Answers are also delivered as XML/Soap messages. In this mode, the requests are not stored.

>

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

The Configuration Wizard

28

Set the directory and file parameter 1 Select the request mode. The provided options are:
File Find To File.

2 Enter the path to the data directory that contains the path to the generated data
files or click the Browse button to direct the wizard to the directory.

3 Enter the path to the log directory or click the Browse button to direct the wizard to
the directory. For more information about the log directory, See Installing VistaLink on page 17.

4 Enter the path to the Done directory or click the Browse button to direct the wizard
to the directory. This stores the files after the results have been generated.

5 Enter the name you want to give to your output topology file. 6 Enter the mapping file name used to generate statistics data. The mapping file is
located in the bin directory.

7 Click Next .

Setting the naming and retrieval rules parameters

This page allows you to define the method to name the service instances such as SAPs and SAP Queues.
T

Set the naming and retrieval rules parameters 1 Select the service rule from the drop-down list:
1, to use the sn attribute (service name), the service Id attribute, the outerEncapValue attribute, and the innerEncapValue attribute. 2, to use only the sn attribute. 3, to use the service Id attribute in addition to the sn attribute (service name). For example, you can set the tag to 3 Retrieve only SAP Queues with statistics Retrieve all SAP Queues Do not retrieve SAP Queues Retrieve only Network Queues with statistics Retrieve ALL Network Queues Do not retrieve Network Queues Retrieve only SDP with statistics Retrieve All SDPs Do not retrieve SDPs

2 Select one of the options to create SAP Queues Vista (topology data file only):

3 Select one of the options to create network queues Vista:

4 Select one of the options to create SDPs:

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

The Configuration Wizard

29

5 Select one of the options to create OAMs:

True, to create OAM Vista. False, if you do not want to create OAM Vista.

6 The Use Suspects allows you to retrieve statistics data flagged with the suspect
attribute. Select one of the options from the drop-down list: True, to retrieve all data (included data flagged with the suspect attribute set to true). False, to retrieve only data flagged with the suspect attribute set to false.

Setting the timeout parameters

If VistaLink is unable to connect to the primary SAM server in a specified amount of time, the timeout enables it to connect to the secondary SAM server. This page allows you to define the period after which the timeout takes place.
T

Set the timeout parameters 1 Enter the network timeout. When the primary server does not answer VistaLink for
the specified time period due to any physical connection problem, then VistaLink connects to the backup server. Now, if the backup server does not answer after the specified time period, the process stops.

2 Enter the connection timeout. When the primary server does not answer VistaLink
for the specified time period due to any logical connection problem, then VistaLink connects to the backup server. Now, if the backup server does not answer after the specified time period, the process stops.

Setting the history management parameters

This page enables you to set the number of days before deleting the files.
T

Set the history management parameters 1 Enter the time period in minutes. When you launch the sam_stat script for the first
time, VistaLink refers to this value to determine the starting point. VistaLink computes the starting point: Current date and time - Data Maximum History (Minutes). When you launch the script later, the process refers to the LastRun.xml file and ignores this value. For more information about determining the starting point, see See About timestamping in VistaLink on page 43.

2 Enter the number of days for which you want to keep the XML files that contain the
requests for topology data.
NOTE

Each time you execute the script, VistaLink counts the number of days elapsed between the current date and the creation date of the topology files in ../done/ topo. If the number of days exceeds the number you enter here VistaLink deletes the corresponding files.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

The Configuration Wizard

30

3 Enter the number of days for which you want to keep the XML files that contain the
requests for performance data (i.e. Statistics data).
NOTE

Each time you execute the script, VistaLink counts the number of days elapsed between the current date and the creation date of the XML files in ../done/stat. If the number of days exceeds the number you enter here VistaLink deletes the corresponding files.

4 Enter the number of days for which you want to keep the performance data values
(i.e the lines that contain the value) in the LastRun.xml file.

Setting the filters parameters

This page enables you to define what data VistaLink needs to retrieve from the SAM server. For example: For routers, if you set the option as Include Only and enter the router sim_81, VistaLink retrieves the data related to the router sim_81 and its interfaces.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

The Configuration Wizard

31

Set the filter parameters 1 Select either:

Include Al l. This retrieves the data for all the routers or customers from the SAM server. Include Only then enter the name of the routers or customers. This retrieves data for the specified routers or customers from the SAM server.

2 Click Next.

Completing the configuration

The final page opens and prompts you to confirm the set parameters.
T

Complete the configuration 1 Click Finish . This launches the actual configuration process. A File Write
Information box appears confirming the completion of the configuration process.

2 Click Ok .

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Additional configurations in sam_cfg.xml

32

Additional configurations in sam_cfg.xml

Below are the tags that you cannot set in the configuration wizard and but can set in the sam_cfg.xml.

Configuring filter interface in the sam_cfg.xml file

The filterInterfaceDown tag allows you to set up the filter in sam_cfg.xml file. When this is set to True, interfaces with State = Down are not included in the topology file. When set to False all interfaces are included in the topology file regardless of the State.

Changing the name of the log file in sam_cfg.xml

The logFileName tag enables you to define the name of the log file. Once you have updated the name in the sam_cfg.xml file, run the configuration wizard to automatically update this in the log4j.properties file.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Configuring VistaMart

33

Configuring VistaMart
The following procedures explain how to create three SAM zones, how to import SAM VistaViews and create a new InfoVista Server object. This configuration prepares VistaMart to future provisioning.

Creating new SAM ZoneSet and Zones

You must create three zones in the same zoneSet (in a SAM zoneSet for example): > SAM_GROUPS, you use this zone to provision VistaMart with group instances (i.e. services and customers). >
SAM_BASIC, you use this zone to provision VistaMart with Basic Instances (i.e. MPLS Interface, SAM SAP, MPLS LSP, SAM Service Component, 5620 SAM Resource, etc.) SAM_PROXY, you use this zone to provision VistaMart with Proxy Instances (i.e. OAM, SAM SAP Queue).

>

This division makes it possible to display the results of the provisioning more rapidly and avoids to overload the system. It allows you to monitor only what you need, for example if you dont need to monitor OAM or SAM SAP Queues, you can use the zones to separate what you monitor from what you do not.
T

Create a SAM zoneSet 1 In the Inventory Manager, open the Config tab. 2 Right-click Zone Set Definition and select New Zone Set.

The New Wizard dialog box opens.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Configuring VistaMart

34

3 Enter a Zoneset Name, here SAM. This zone set will contain all corresponding
zones (here: SAM_BASIC , SAM_PROXY, and SAM_GROUPS) .

4 Enter a Zoneset Identifier. By default, this value is the same as the zoneset name.
This attribute must be unique for each zoneset.

5 Enter a Zoneset Description (optional).

Create new zones

NOTE

Repeat the following steps to create a SAM_BASIC zone, SAM_PROXY zone and SAM_GROUPS zone.

1 In the Inventory Manager, open the Config tab. 2 Expand ZoneSet Definition, right-click the ZoneSet (here SAM) to associate with
the new zone and select New zone.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Configuring VistaMart

35

3 In the New Wizard window, add the parameters as required.

NOTE

All parameters flagged with a * are mandatory.

Description

Parameter Zone name*

A name (up to 64 characters) which corresponds to a type of reporting you want it to handle (for example, here you name a first zone SAM_BASIC and a second zone SAM_PROXY). By default the Identifier takes the same value as the zone name. A relevant description (up to 2048 characters). Enter Manual. This indicates that the zone will be provisioned with topology files. Associate the new zone with an InfoVista group. By default the Default server group is used. NOTE You can modify this parameter at a later date. You can set a physical location for the Instances in this zone. Select any Country/City combination from the drop-down list.

Zone Identifier* Zone Description Zone Kind Default IV Servers Group* Default Location

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Configuring VistaMart

36

Parameter Resource Activation*

Description

By default, all related values for the following resources are activated:

> Solution > Report Template Capabilities > Indicators Capabilities > Vendor > Template Frequency > Vistas > Template/Indicator Library
They can be deactivated or reactivated using zone filters.
Lifetime before Archiving

The lifetime of instances in unstable status. Once this time has elapsed, the instance is archived. NOTE You may need to increase this value.

WARNING You must disable all VIN rules for the new zones. VistaBridge needs the slots to

be disabled to activate them.

Importing VistaView libraries

At this stage, VistaMart must be installed and running.
T

Import VistaView libraries 1 Run the VistaMart Client to connect to your VistaMart database. 2 From the File menu, select Manage Libraries. 3 In this window, click the Set the repository of Libraries button
.

4 From VistaLink Installation directory, select vview and click Set Repository. 5 In the main window, there are several libraries (in bold): select them and click
Import

From VistaMart Inventory Manager, click the Model tab, the following VistaView libraries appear: > under the IV Server libraries node: InfoVista Core InfoVista IP QOS - Basics InfoVista MPLS Network - Alcatel 5620 SAM* InfoVista Network Basics InfoVista Problem Resolution Model

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM >

NOTE

Configuring VistaMart

37

InfoVista Resources - Basics InfoVista Routers - Alcatel 5620 SAM* InfoVista SAM Model* InfoVista Service - Alcatel 5620 SAM* InfoVista Solution Model InfoVista Common InfoVista Groups InfoVista SAM* InfoVista SAM VB* InfoVista VistaMart Solution Model
These are specific SAM libraries.

under the VistaMart libraries node:

Importing event message formats

In order to get explicit messages when the system raises an event, you must load an xml file that contains the message format.
T

Import event message formats 1 From the VistaMart/ bin/ inventory.sh directory, run the VistaMart Inventory
Manager to connect to your VistaMart database.

2 From the File menu, select Manage Event Target. 3 At the bottom of this window, click Import. A pop-up message prompts you to
confirm your action. Click Yes.

4 In the Import an xml file window, browse for the VistaLink for Alcatel-Lucent 5620
SAM installation package and select the file vviews\config\Infovista_VM__Event_Conf.xml.

5 Click Import. In the Targets tab of the Event Target Management window, the list of
URLs is updated.

6 Click Save, then Close.

Creating a new InfoVista Server object

To enable VistaBridge to insert data into VistaMart, you must create a Virtual IV Server. All instances and data coming from an external source must be associated to a server for purposes of aggregation. The aggregation process is launched by the VistaMart Gateway on a per server basis. The data that VistaBridge inserts must also be aggregated; for this reason, the data needs to be linked to a dedicated server and server group.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Configuring VistaMart

38

Create a new Server Group dedicated to SAM 1 From the Inventory Manager, click the Config tab. 2 Right click the IV Servers Groups node and select New IV Servers Group. 3 In the Server Group Wizard enter parameters as required. 4 Click Finish. The new Server group is added to the list.
NOTE

Parameters flagged with a * are mandatory.

Description

Parameter Group Name* Group Description Type* Backup Group

T

Group name (255 characters maximum). Textual description of the group (2048 characters maximum). Production by default. The Backup option is reserved to VistaCockpit purposes. The name of the IV Server group used as a backup.

Create a new InfoVista Server object 1 From the Inventory Manager, click the Config tab. 2 Expand the IV Servers Groups node. 3 Right click the Server group you have created ( SAM for example) and select New
IV Server.

4 Enter the Name and Type parameters as follows:

Parameter Alias Name Type
NOTE

Description

Name by which the server is known.

EXAMPLE

Virtual

Select VistaBridge. The other parameters are not used by VistaLink. For further information please refer to the VistaMart User guide.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing the VistaLink environment on VistaPortal

39

Installing the VistaLink environment on VistaPortal

The objective of this procedure is to install the VistaLink for Alcatel-Lucent 5620 SAM page structure and report templates on your VistaPortal server.
T

Install VistaLink for Alcatel-Lucent 5620 SAM on VistaPortal 1 Close all your applications. 2 From the Installation package main directory, copy and unzip the file
portal\Portal.zip to your VistaPortal server machine, under <InfoVista Installation directory>. Ensure you have: > SAM3 directory under <VistaPortal Installation directory>\reporting\Templates\report\InfoVista containing the report templates for VistaLink for Alcatel-Lucent 5620 SAM, VistaLink for SAM page packages and users (two xml files) under <VistaPortal Installation directory>\reporting\SAM3: InfoVista_SAM_Solutions_Page_Packages.xml InfoVista_SAM_Solutions_Users_Groups.xml

>

You can then log in to your VistaPortal Management console home page and perform the following steps: "Verify the connection to your VistaMart database" on page 40 "Import VistaLink for Alcatel-Lucent 5620 SAM Page Packages" on page 40 "Import the VistaPortal users and groups" on page 41

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Installing the VistaLink environment on VistaPortal

40

Verify the connection to your VistaMart database 1 Connect to the VistaPortal Management Console and enter your administrator
login and password.

2 In the left-hand pane, expand Server List node and select VistaMart Database. 3 If your VistaMart database is not present, click Add and enter:
Label
The name to display in the lists of VistaMart databases in the displets. This field is optional. If you leave it blank, the Hostname is used in the displet lists. The DNS name of the host which runs the VistaMart Repository you want to connect to. This field is mandatory. Note: If necessary, you can specify hostname:port to connect to a VM server with a port other than 1521.
Database name Database Type Login Password

Hostname

The name of the VistaMart database. This corresponds to the database IVDB. This field is mandatory. Select the default option: ORACLE. A valid login name for the host 'hostname'. This field is mandatory. Password for the login name

4 Click the Test button to test the connection to VistaMart database. 5 If the test is successful, click Save to make the new connection, or Cancel to
ignore the entries and return to the list of connections.

Importing Page Packages

T

Import VistaLink for Alcatel-Lucent 5620 SAM Page Packages 1 Connect to the VistaPortal Management Console and enter your administrator
login and password.

2 In the tree pane, click the node Page Packages . 3 At the right of the page, click Import. A popup window appears.

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing the VistaLink environment on VistaPortal

41

4 In the Input File field, click the Browse button to select the file that contains the
VistaLink for Alcatel-Lucent 5620 SAM Page Packages: <VistaPortal Installation directory>\reporting\SAM3\InfoVista_SAM_Solutions_Page_Packages.xml. This file contains the VistaPortal Page Packages and pages.

5 Verify that the first three options are deselected. 6 Select the last option Replace VistaMart database(s) in import file with. This
option allows you to define which VistaMart schema will be used as the source of information for the displets. Select the VistaMart you require from the drop-down list.

7 Click Import. 8 Verify that the following Page Packages and related pages are correctly imported.

NOTE

Refer to the User Guide to get the full description of each page package.

Importing users and groups

T

Import the VistaPortal users and groups 1 Connect to the VistaPortal Management Console and enter your administrator
login and password.

2 In the tree pane, click All . 3 At the right of the page, click Import. A popup window appears:

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Installing the VistaLink environment on VistaPortal

42

4 In the Input File field, enter the path to the file that contains the VistaLink for
Alcatel-Lucent 5620 SAM users and groups: <VistaPortal Installation directory>\reporting\VIS3\InfoVista_SAM_Solutions_Users_Groups.xml.

5 Verify that the four options are deselected. 6 Click Import .

The tree now displays the following structure:

To verify that the User groups are correctly imported connect to the VistaPortal login page and use the default username/password:
User groups Customer Users Engineer Users Manager Users VP Group Users Default username/password

SAMCustomer/[blank] (no password) SAMEngineer/[blank] (no password) SAMManager/[blank] (no password) SAMVB//[blank] (no password)

Installation Guide - Chapter 3

Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Configuring VistaLink

43

Configuring VistaLink
The following steps configure scripts according to your network parameters.

About timestamping in VistaLink

Timestamping is based on devices instead of being based on classes. The objective is to take into account the difference between two devices of the same class that record data at different time. During the execution of sam_stat script VistaLink associates a value for one instance with a timestamp. The timestamps are listed in data/ LastRun.xml

Determining the starting point for polling instances

When you execute the script to retrieve performance data ( sam_stat), VistaLink stores the latest values for the indicators of type delta in data/ LastRun.xml. When you launch the script for the first time, VistaLink refers to the value of <dataMaxHistory> in the sam_cfg.xml file to determine the starting point of the polling. Then, during the following executions, VistaLink refers to the LastRun.xml to determine the starting point of the polling.

EXAMPLE Here is an example of what occurs when you set <dataMaxHistory> to 300
(minutes) : <dataMaxHistory>300</dataMaxHistory>. If you execute the script for the first time at 11:00 a.m, you get the following results at 11:15 a.m in the data directory: > LastRun.xml file contains the latest values for each indicator of type delta (i.e.: the delta indicator values are the result of the difference between two other values from two other indicators). <Vista>.csv files and their associated < Vista.xml> files contain values from 6:00 a.m. (i.e. 11:00 - 300) until 11:15 a.m.

>

Then during the next script execution, VistaLink refers to LastRun.xml to know the starting point of the polling: VistaLink sends the requests to SAM server from the last value retrieved from LastRun.xml. If you schedule the script execution at 12:00 a.m., here are the results at 12:15 a.m.: > > LastRun.xml file contains the latest values for each indicator of type delta. <Vista>.csv files and their associated < Vista.xml> files contain the result of the comparison between old values and new values.

Determining the period for archiving values

During the script execution, VistaLink also refers to <keepLastRunHistory> in the sam_cfg.xml file to determine the number of days for which to keep the lines (i.e. the lines that contain values) in the LastRun.xml file. The <keepLastRunHistory> value Installation Guide - Chapter 3 Installation and configuration

VistaLink 3.0 for Alcatel-Lucent 5620 SAM works as a lifetime for one pair of instance/indicator.

Configuring VistaLink

44

VistaLink deletes the line(s) that have a timestamp exceeding the period you define in <keepLastRunHistory>.

EXAMPLE In the following example, VistaLink processes are launched on the 5th of April. Here are the results in the LastRun.xml:
<Vista name="SAP Queue Egress"> <LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_82:7006:1/1/4:7:0:1:Egress" value="0" timestamp="1175786900000" />

(1175786900000=Thu, 5 Apr 2007 15:28:20 UTC)

<LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_80:5098:1/1/3:99:0:1:Egress" value="64" timestamp="1175795160000" />

(1175795160000=Thu, 5 Apr 2007 17:46:00 UTC)

<LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_81:7024:1/1/4:25:1:Egress" value="256" timestamp="1175796900000" />

(1175796900000=Thu, 5 Apr 2007 18:15:00 UTC)

<LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_80:5029:1/1/3:30:0:1:Egress" value="64" timestamp="1175795160000" />

(1175795160000=Thu, 5 Apr 2007 17:46:00 UTC)

</Vista> (...)

Two days later, we launch VistaLink processes, with the <keepLastRunHistory> tag set to 1. In our example, between the 5th and the 7th, the polling of the instance sim_82:7006:1/1/4:7:0:1:Egress has been stopped. Here are the results in the LastRun.xml:
<Vista name="SAP Queue Egress"> <LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_80:5098:1/1/3:99:0:1:Egress" value="64" timestamp="1175942880000" /> )

(1175942880000=Sat, 7 Apr 2007 10:48:00 UTC

<LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_81:7024:1/1/4:25:1:Egress" value="256" timestamp="1175796900000" />

(1175972880000=Sat, 7 Apr 2007 19:08:00 UTC)

<LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_80:5029:1/1/3:30:0:1:Egress" value="64" timestamp="1175952880000" />

(1175952880000=Sat, 7 Apr 2007 13:34:40 UTC)

</Vista>

If the user had set the <keepLastRunHistory> tag to a greater value, then the line <LastValue wid="9AB68330CE3211DAA2D300904B88C603" instanceName="sim_82:7006:1/1/4:7:0:1:Egress" value="0" timestamp="1175786900000" /> would have been kept.

Installation Guide - Chapter 3

Installation and configuration

4 Data files generation

This section explains how to generate topology files and performance data files. After each generation, you must import the results into VistaMart, either manually or automatically. This chapter includes the following sections:

"Topology data generation (manually)" on page 46 "Performance data generation (manually)" on page 51 "Scheduling files generation" on page 55 "Troubleshooting" on page 63

45

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Topology data generation (manually)

46

Topology data generation (manually)

When you generate the topology data for the first time, you proceed in two stages described below:

1 Launching the topology script to export topology data from SAM server. 2 Provisioning VistaMart to import topology data into VistaMart.
If the VistaFoundation Kit is 4.0, then the new scripts Sam_provisionerAPI.sh (bat) or Sam_provisionerAPI_schedule.sh (bat)use the Http Provisioning URl to transfer the processed topology file into VistaMart. After the first generation, you can schedule the two stages, refer to "Scheduling files generation" on page 55.
NOTE

You can also generate the topology data in one stage: see "Generating and provisioning the topology data in one script (OPTIONAL)" on page 49. If you use VistaLink with InfoVista Server (i.e. with VistaInsight for Network), make sure you correctly configured the sam_cfg.xml file.

NOTE

The topology script exports the topology data from the 5620 SAM server to two xml files, corresponding to Basic Instances on the one hand and Proxy Instances on the other hand, then the two files are merged in one topology file.
NOTE

See also "Creating new SAM ZoneSet and Zones" on page 33

Prerequisites
Before launching the scripts, ensure: > > > Alcatel-Lucent 5620 SAM Server is up and running. The configuration wizard is run atleast once. You correctly configured the sam_cfg.xml file using the configuration wizard.
NOTE

If you change the naming convention you set in <serviceNameRule> after the VistaMart provisioning, new instances will be created and you will lose historical data.

> >

You have correctly configured the scripts using the configuration wizard. These parameters are mandatory to connect to the SAM server. You have configured your mail notification settings in order to receive alert on the success or failure of data generation. For more information on configuring mail notification, refer to the VistaCockpit Users Guide.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Topology data generation (manually)

47

Launching the topology script

ABOUT NETWORK FAILURE MANAGEMENT When you launch the topology script you must
enter the following arguments: > >
number of retry: indicates how many times VistaLink tries to connect to the SAM server timeout: indicates the period (in seconds) that separates each retry. When a connection has failed, the system waits for all processes to be stopped. Then the system launches the next retry.
NOTE

The values for number of retry and timeout depend on the size of your database and on the scheduling you set. For example, for a 5 MegaBytes database and a 1 hour scheduling we recommend to set 5 as <number of retry> and 10 as <timeout>.

Launch sam_topo.bat or sam_topo.sh 1 Open a command prompt window or a terminal. 2 Place the command line in the bin directory ( <InfoVista Installation
Directory>\VistaLinks\SAM\bin\ for Windows, or <InfoVista Installation Directory>/VistaLinks/SAM/bin/ for Solaris) .

3 Enter sam_topo.bat sam_cfg.xml <number of retry> <timeout (seconds)> (or

sam_topo.sh sam_cfg.xml <number of retry> <timeout (seconds)> for Solaris).

4 Press ENTER key.

NOTE

By default, the number of retry is 1.

RESULTS
Three new topology files are created in <InfoVista Installation Directory>\VistaLinks\SAM\data for Windows (or <InfoVista Installation Directory>/VistaLinks/SAM/data, for Solaris): samTopo_basic.xml samTopo_proxy.xml samTopo.xml (only used to aggregate the two other files)

Provisioning VistaMart
Once you have generated the topology data files, you must import these files into VistaMart.
WARNING If you change the naming convention you set in <serviceNameRule> after the

VistaMart provisioning, new instances will be created and you will lose historical data.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Topology data generation (manually)

48

Import topology in VistaMart (via the Inventory Manager) 1 Launch VistaMart Inventory Manager. 2 Select Provisioning > Import Topology.
You can also access the Import Topology option by selecting and right-clicking a zone in the Config tab or Browser tab.

3 Select the appropriate Zone and Mode.

NOTE

You can only provision one zone at a time.

4 Click the browse button in the Topology file field to select the XML topology file. 5 Select the samTopo_basic.xml file and click Open. 6 Ensure the Topology file format is set to XML File. 7 Click Preview. This allows you to test the validity of the submitted file and display
the changes compared to the previous topology. VistaMart uses the submitted topology file to simulate what changes (additions, deletions, modifications) would be made to the database for these objects:
Instances: Inserted (blue), changed (green), removed (red). Any Instances which need resynchronizing in the database are also displayed in yellow. Reports (for each Instance) Slots (for each Instance) Properties (for each Instance)

8 To display Reports/Slots/Property information, select an Instance in the Instance

pane. For more information on each individual object, leave the cursor on the name to display the Tooltip.

9 Click OK to close the Preview window. 10 Click Run to actually apply the changes.
VistaMart updates the database according to the information returned in the review window. All instances are created/updated/deleted as required. Instances which are no longer in the zone topology file are not deleted immediately from the database but turned as unstable instances. This means that they can be submitted again until the expiration of their Lifetime before Archiving.
NOTE

Repeat the whole procedure for samTopo_proxy.xml file. For further information on the provisioning modes, please refer to the VistaMart User guide.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Topology data generation (manually)

49

Generating and provisioning the topology data in one script (OPTIONAL)

You can follow this procedure to launch the topology files generation and the provisioning in one stage. To do so, you execute sam_provisioner_schedule. The script exports topology data from SAM server then provisions VistaMart with the topology data in Device mode.
NOTE T

If you use this method, VistaLink does not handle the network failures.

Generate topology data 1 Open a command prompt window or a terminal. 2 Place the command line in the InfoVista/VistaLinks/SAM/bin directory. 3 Execute sam_provisioner_schedule.bat (or .sh).

Results
Once the topology files are imported, ensure Instances display correctly in your VistaMart Inventory Manager.
T

Display Instances 1 Launch the VistaMart Inventory Manager. 2 Expand each zone you provisioned. 3 Select Instances.
SAM objects appear (see "Instances naming conventions" on page 77).

Select an object to browse for its attributes (Vistas, properties, reports, slots).

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Topology data generation (manually)

50

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Performance data generation (manually)

51

Performance data generation (manually)

When you generate the performance data for the first time, you proceed in two stages described below:

1 Launching the performance script to export performance data from the SAM server
to pairs of CSV / XML files (one pair is created for each Vista).

2 Provisioning VistaMart to import performance data into VistaMart via VistaBridge.

After the first generation, you can schedule the two stages, refer to "Scheduling files generation" on page 55.
NOTE

You can also generate the performance data in one stage: see "Generating the performance data in one script (optional)" on page 53. If you use VistaLink with InfoVista Server (i.e. with VistaInsight for Network), make sure you correctly configured the specific parameters sam_cfg.xml file.

NOTE

Prerequisites
WARNING Before generating the performance data, you must have provisioned

VistaMart with topology data.

Before launching the script, ensure that: > > > Alcatel-Lucent 5620 SAM Server is up and running. SNMP Statistics and Accounting policies are configured on the 5620 SAM Server. You correctly configured the sam_cfg.xml file using the configuration wizard.
WARNING If you change the naming convention you set in <serviceNameRule> after the

VistaMart provisioning, new instances will be created and you will lose historical data).

>

You have correctly configured the scripts using the configuration wizard. These parameters are mandatory to connect to the SAM server.
WARNING In the sam_VB script, pay particular attention when you set the TZ (Time Zone) and AR (Acquisition Rate) parameters . It is not possible to change them

afterwards without important effect (for example you would have to delete the historical data).

>

You have configured your mail notification settings in order to receive alert on the success or failure of data generation. For more information on configuring mail notification, refer to the VistaCockpit Users Guide.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Performance data generation (manually)

52

Launching the performance script

ABOUT NETWORK FAILURE MANAGEMENT When you launch the performance script you can
add the following options: > >
number of retry: indicates how many times VistaLink tries to connect to the SAM server. timeout : indicates the time interval (in seconds) before the next attempt. When a connection has failed, the system waits for all processes to be stopped. Then the system launches the next attempt.
NOTE

The values for number of retry and timeout depend on the size of your database and on the scheduling you set. For example, for a 5 MegaBytes database and a 1 hour scheduling we recommend to set 5 as <number of retry> and 10 as <timeout>.

Launch sam_stat.bat or sam_stat.sh 1 Open a command prompt window or a terminal. 2 Place the command line in the bin directory ( <InfoVista Installation
Directory>\VistaLinks\SAM\bin\ for Windows, or <InfoVista Installation Directory>/VistaLinks/SAM/bin/ for Solaris) .

3 Enter sam_stat.bat sam_cfg.xml <number of retry> <timeout (seconds)> (or

sam_stat.sh sam_cfg.xml <number of retry> <timeout (seconds)> for Solaris).

4 Press ENTER key.

NOTE

By default, the number of retry is 1.

RESULTS
> CSV files and their corresponding XML files are created in <InfoVista Installation Directory>\VistaLinks\SAM\data for Windows (or <InfoVista Installation Directory>/VistaLinks/SAM/data, for Solaris). Each pair of files is identified with the name of the Vista.

>

Processing the performance data for a specified period of time

When sam_stat.sh (bat) is not run for a long period of time, or when handling large amounts of data, the memory requirement to process the data may exceed the available memory on the VistaLink. Also, the VM server may get overloaded when huge amount of data is pushed into VistaMart. The sam_stat_VB_split.sh helps resolve these issues by processing huge files in multiple steps. It allows you to specify the amount of data (in hours) you want to process in each step. When you execute the script, VistaLink refers to the LastRun.xml to determine the starting point of the polling. The script processes the data until the timestamp is equal to or greater than the value of the LastRun.xml + X hours. Installation Guide - Chapter 4 Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Performance data generation (manually)

53

Launch sam_stat_VB_split.sh 1 Open a command prompt window or a terminal. 2 Place the command line in the bin directory ( <InfoVista Installation
Directory>\VistaLinks\SAM\bin\ for Windows, or <InfoVista Installation Directory>/VistaLinks/SAM/bin/ for Solaris) .

3 Enter sam_stat_VB_split.sh <cfg_file> -H <period in Hours>

RESULTS
> CSV files and their corresponding XML files are created in <InfoVista Installation Directory>\VistaLinks\SAM\data for Windows (or <InfoVista Installation Directory>/VistaLinks/SAM/data, for Solaris). Each pair of files is identified with the name of the Vista. The CSV files are then pushed into VistaMart using VistaBridge.

> >

Provisioning VistaMart
Once you have generated the performance data files, you must import these files into VistaMart.
WARNING If you change the naming convention you set in <serviceNameRule> after the

VistaMart provisioning, new instances will be created and you will lose historical data).
T

Import performance data files in VistaMart via VistaBridge 1 Open a command prompt window or a terminal. 2 Place the command line in the bin directory ( <InfoVista Installation
Directory>\VistaLinks\SAM\bin\ for Windows, or <InfoVista Installation Directory>/VistaLinks/SAM/bin/ for Solaris) .

3 Execute sam_VB.bat <number of retry> <timeout (seconds)> (or sam_VB.sh

<number of retry> <timeout (seconds)>)
NOTE

By default, the number of retry is 1.

Generating the performance data in one script (optional)

You can follow this procedure to launch the performance files generation and the VistaMart provisioning in one stage.
NOTE

If you use this method, VistaLink does not handle the network failures.

The script exports performance data from 5620 SAM server to pairs of CSV / XML files (one pair is created for each Vista). Then the script provisions VistaMart via VistaBridge.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Performance data generation (manually)

54

Launch sam_stats_VB.bat or sam_stats_VB.sh 1 Open a command prompt window. 2 Place the command line in the bin directory ( <InfoVista Installation
Directory>\VistaLinks\SAM\bin\ for Windows, or <InfoVista Installation Directory>/VistaLinks/SAM/bin/ for Solaris) .

3 Enter sam_stats_VB.bat (or sam_stats_VB.sh for Solaris). 4 Press ENTER key.

Results
Once you have imported the performance data into VistaMart, ensure the data display correctly in your VistaMart Inventory Manager.
T

Display performance data 1 In the Browser tab, expand the Vista node. 2 Expand a Vista node. 3 Click Instances. 4 In the right pane, right-click an Instance and select Display Data...
The aggregated values appear in graphs.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Scheduling files generation

55

Scheduling files generation

Once you have launched a generation and a provisioning manually, you can schedule the tasks related to topology data and performance data. To schedule the tasks you can use VistaCockpit or the system tool of your choice.

Scheduling tasks with VistaCockpit

VistaCockpit is the administration tool of the VistaFoundation. It provides extensive alerting and diagnostic functionalities as well as recovery on certain products. VistaCockpit installation takes place in two stages, in this precise order:

1 Installation of a VistaCockpit Server 2 Installation of one agent per monitored host

Each agent reports to the VistaCockpit Server, providing information about the installed products on that host.
NOTE

To install and configure VistaCockpit, please refer to VistaCockpit installation guide.

With VistaCockpit it is possible to set and schedule the workflows dedicated to VistaLink. Instead of launching the scripts via the .bat [ .sh] files (with your system tool), VistaCockpit offers you to launch them via configured workflows. A workflow is a set of linked tasks. VistaLink is delivered with two workflows configured in four XML files > VistaLink_workflow_Statistics.xml > VistaLink_workflow_Topology.xml > VistaLink_workflowAPI_Topology.xml > VistaLink_workflow_StatAdd.xml > VistaLink_workflow_Purge_Logs.xml
NOTE

The Statistics and Topology workflows contain the task(s) that correspond to the two steps you perform manually.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM Here are the descriptions of the workflows.
Workflow Statistics Description

Scheduling files generation

56

This workflow contains the following tasks:

> SAM Statistics, that launches the generation of the performance

files.

> Pushing Data using VistaBridge, that launches the provisioning

of VistaMart with the performance files.
Topology

This workflow contains the following tasks:

> SAM Topology, that launches the generation of the topology

files.

> SAM Provisioning, that launches the provisioning of VistaMart

with the topology files.
Topology HttpAPI

This workflow contains the following tasks:

> HTTP Provisioning, that launches the provisioning of topology

files using HTTP API.

> SAM Topology, that launches the generation of the topology

files.
Temperature

This workflow contains the below task:

> SAM Temperature Statistics, that launches the generation of

temperature statistics for each router.
Purge Logs

This workflow contains the below task:

> Purge VistaLink SAM Logs, that deletes the log files older
than 7 days.

The following section describes how to import a workflow and set specific parameters. Then it provides you with the necessary information to schedule the tasks.

Importing the workflows

Before scheduling the workflows, you must import them into VistaCockpit.
WARNING Ensure you previously declared a VistaMart database (refer to VistaCockpit

User Guide in Getting Started - Declaring the VistaMart Database)

T

Import the VistaLink workflows 1 Launch the VistaCockpit console. 2 Click the Tasks tab. 3 Right-click the Workflows on Schedule node and select Import Workflow(s). 4 Browse to locate the 4 XML files. ( <Installation
directory>\VistaLinks\SAM\cockpit).

5 Select a file and click Import. VistaCockpit imports the selected workflow. 6 Repeat step 2 to 5 to import each file.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Scheduling files generation

57

After each importation the Import successfully message appears in the right panel. The workflows appear in the Tasks tab of VistaCockpit, under Tasks > Workflows on schedule: > VistaLink for SAM 5620 Workflow (Topology) > VistaLink for SAM 5620 Workflow (Statistics) > VistaLink for SAM 5620 Workflow (Topology HttpAPI) > VistaLinks for SAM 5620 Workflow (Temperature) > VistaLinks for SAM 5620 Purge Logs
NOTE

The workflows are imported with pre-configured tasks. For detailed information on how to configure and schedule these tasks, refer to the VistaMart Administration Guide.

Configuring the workflows

T

Configure the VistaLink for SAM 5620 Workflow (Topology) workflow 1 Click on the workflow in the left panel. 2 Click on the Tasks tab of the right panel: the two tasks appear with some
parameters already configured.

3 Set the SAM Topology task as follows:

Tab\field Value

General\Targets Parameters\Program Parameters\Parameters

Select the system on which you want to execute the task. Enter the path to sam_topo.bat or [.sh] Enter the following parameters separated by space, in this precise order: 1 name of the configuration file: sam_cfg.xml 2 number of retries (1 by default) 3 timeout period in seconds (30 by default)
EXAMPLE

sam_cfg.xml 1 30

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Scheduling files generation

58

4 Set the SAM Provisioning task as follows

Tab\field Value

General\Targets Parameters\Program Parameters\Parameters

Select the system on which you want to execute the task. Enter the path to sam_provisioner.bat or [.sh] Enter the following parameters separated by space, in this precise order: 1 number of retries (5 by default) 2 timeout period in seconds (30 by default)
EXAMPLE

5 10

For users using VistaMart 4.0

Tab\field Value

General\Targets

Select the system on which you want to execute the task.

Parameters\Program Enter the path to sam_provisionerAPI.bat or [.sh] Parameters\Paramet ers Enter the following parameters separated by space, in this precise order: 1 name of the configuration file: sam_cfg.xml 2 name of the configuration file: sam_globalcfg.xml 3 number of retries (3 by default)
EXAMPLE NOTE

5 10

The SAM Provisioning task only launches when the SAM topology task is successful.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Scheduling files generation

59

Configure the VistaLink for SAM 5620 Workflow (Statistics) workflow 1 Click on the workflow in the left panel. 2 Click on the Tasks tab of the right panel: the two tasks appear with some
parameters already configured.

3 Set the SAM Statistics task as follows:

Tab\field Value

General\Targets Parameters\Program Parameters\Parameters

Select the system on which you want to execute the task. Enter the path to sam_stat.bat or [.sh] Enter the following parameters separated by space, in this precise order: 1 name of the configuration file: sam_cfg.xml 2 number of retries ( 1 by default) 3 timeout period in seconds ( 30 by default)
EXAMPLE

sam_cfg.xml 1 30

4 Set the Pushing Data using VistaBridge task as follows

Tab\field Value

General\Targets Parameters\Program Parameters\Parameters

Select the system on which you want to execute the task. Enter the path to sam_VB.bat or [.sh] Enter the following parameters separated by space, in this precise order: 1 number of retries (5 by default) 2 timeout period in seconds (30 by default)
EXAMPLE

5 10

NOTE

The SAM Pushing task only launches when the SAM Statistics task is successful.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Scheduling files generation

60

Configure the VistaLink for SAM 5620 Workflow (Temperature) workflow 1 Click on the workflow in the left panel. 2 Click on the Tasks tab of the right panel: the two tasks appear with some
parameters already configured.

3 Set the SAM Topology task as follows:

Tab\field Value

General\Targets Parameters\Program

Select the system on which you want to execute the task. Enter the path to sam_stat.bat or [.sh] or s am_statAdd.

Configure the VistaLinks for SAM 5620 Purge Logs workflow 1 Click on the workflow in the left panel. 2 Click on the Tasks tab of the right panel: the two tasks appear with some
parameters already configured.

3 Set the SAM Topology task as follows:

Tab\field Value

General\Targets

Select the system on which you want to execute the task.

Parameters\Program Enter the path to sam_del_logs.bat or [.sh] Parameters\Paramet ers Enter the below parameter: number of days (7 by default)

Scheduling the workflows

A workflow is a group of linked tasks, and the schedule to define at this stage sets the starting point for the initial task(s) in the workflow. Subsequently, the configured tasks are launched according to the order defined in the task linking.
T

Schedule the workflows 1 Click a workflow 2 Click the Schedule tab and set the following parameters:
Frequency
Select a frequency from the drop-down list, and set an interval for the selected frequency.

Max Duration Use the arrow keys to set a maximum duration for the workflow in hours and minutes. If the limit is reached, VistaCockpit lets jobs already running reach completion, but stops the workflow - remaining tasks are not launched.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Start Date

Scheduling files generation

61

Click the arrow to open a calendar and select a starting date for the workflow.
WARNING This defines a minimum date/time, but in certain cases, it is not

the start date/time. In order to display the real start date, select the icon to view a scheduling preview.

Start Time

Use the arrow keys to set a start time for the workflow. your workflow:

Repeat mode Select one of the radio buttons to define the Repeat mode for

> Infinite Repeat - the workflow continues to execute at the defined

interval indefinitely.

> Repeat - Use the arrow keys to set the number of repetitions for
workflow execution.

> Repeat until - Use the arrow key to select a termination date for
workflow execution.

Here are recommended frequencies for workflows:

Workflow VistaLink for SAM 5620 Workflow (Topology) VistaLink for SAM 5620 Workflow (Statistics) VistaLinks for SAM 5620 Workflow (Temperature) VistaLinks for SAM 5620 Purge Logs
NOTE

Recommended frequency

Once a day (i.e: daily) Every hour (i.e. hourly) Every 30 minutes Once every 7 days.

For further information on scheduling tasks and workflows, please refer to the VistaCockpit User Guide.

Scheduling tasks with the system tool (optional)

This section helps you configure your system tool to launch the VistaLink processes. This section is for information only as we recommend to use VistaCockpit to schedule the VistaLink processes.
NOTE

For a first utilization perform the generation of data files and the VistaMart provisioning in manual mode, see "Topology data generation (manually)" on page 46 and "Performance data generation (manually)" on page 51 Then when you are satisfied with the results, schedule the whole process.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Scheduling files generation

62

Topology data
You can perform the topology files generation and the VistaMart provisioning either manually or automatically by scheduling the execution of sam_provisioner_schedule.bat (or .sh) that generates the topology files and provisions VistaMart in Change mode. If you are using VistaMart 4.0, use the sam_provisionerAPI_schedule.sh (.bat)script. In this mode, instances can be created, modified, or deleted. The differences between the new topology file and the existing topology in the VistaMart database are compared and reconciled for a given zone.
NOTE NOTE

For further information on provisioning modes, refer to VistaMart User Guide. To use the scripts sam_provisioner_schedule.sh/bat and sam_provisioner.sh/bat, change the value of VMCNT to http://<Ip address of VM>:11080 in the sam_global.sh file.

Schedule the topology files generation and the VistaMart provisioning (Change mode)
> > use the system tool (Windows task scheduler or cron command). schedule the execution of sam_provisioner_schedule.bat (or .sh)/ sam_provisionerAPI_schedule.sh (.bat) once a day.

Performance data
You can perform the performance files generation and the VistaMart provisioning either manually or automatically by scheduling the execution of the following command line: sam_stats_VB.bat (or sam_stats_VB.sh for Solaris).
T

Schedule the performance file generation and the VistaMart provisioning

> > Use the system tool (Windows task scheduler or cron command). Schedule the execution of the command line every hour.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Troubleshooting

63

Troubleshooting
The following error messages can appear when you launch the scripts. Refer to the corresponding section to get information on how to solve the problem.
Error code Meaning 0 1 2 See

ok Any error (file configuration, etc.) Network failure or timeout connection to sam server. Out of Memory

/ "Error of type 1 - file configuration" on page 63 "Error of type 2 - network failure, connection problems" on page 64 "Error of type 3 - memory problems" on page 69

Error of type 1 - file configuration

Here is an example of the problems referenced as error of types 1.
EXAMPLE

The following messages display in the command prompt window and is recorded in VistaCockpit log file.

2 006-09-05 11:16:30,673 [main] FATAL com.infovista.sam.ftp.FtpClient - ftp

user/password incorrect for statistics files download 2006-09-05 11:16:30,675 [main] FATAL com.infovista.sam.SAMtopo user/password incorrect for statistics files download - ftp

2006-09-05 11:16:30,681 [main] INFO com.infovista.sam.SAMtopo - Program Complete with errors (1) in 4.636 seconds Program Complete with errors (1) in 4.636 seconds ########### Number attempt :1 ########### error processing step : vistaLink - processing stopped

How to resolve the problem

When VistaLink sends a message of type 1, you must verify the <ftpPwd> parameters you entered in the sam_cfg.xml file. Then can wait for VistaCockpit to launch the workflow at next schedule or execute immediately the workflow (Execute button).
NOTE

There is no retry for this type of error.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Troubleshooting

64

Error of type 2 - network failure, connection problems

This type of error can occur during topology data generation and during performance data generation. Here is an example of the problems referenced as error of types 2.
EXAMPLE

The following messages display in the command prompt window and is recorded in VistaCockpit log file.

2006-09-05 11:31:50,180 [main] INFO org.apache.commons.httpclient.HttpMethodBase - Recoverable exception caught when processing request 2006-09-05 11:31:50,182 [main] WARN org.apache.commons.httpclient.HttpMethodBase - Recoverable exception caught but MethodRetryHandler.retryMethod() returned false, rethrowing exception 2006-09-05 11:31:50,184 [main] FATAL com.infovista.sam.alcatel.XMLserver - Cannot connect to backup server !, exiting 2006-09-05 11:31:50,185 [main] FATAL com.infovista.sam.SAMtopo connect to server 2006-09-05 11:31:50,191 [main] INFO com.infovista.sam.SAMtopo Complete with errors (2) in 2.339 seconds Program Complete with errors (2) in 2.339 seconds ########### Number attempt :3 ########### error processing step : vistaLink - processing stopped - Cannot - Program

How to resolve the problem

The problem comes from too low values you set in the sam_cfg.xml file in: > > <networkTimeOut> <connectionTimeOut>

You must also verify that the network connection between VistaLink and SAM work correctly.

Network failure or connection problems during topology data generation

DURING THE EXPORT PROCESS (WHEN

VISTALINK CONNECTS TO SAM SERVER TO RETRIEVE DATA)

When a network failure occurs during the export process for example, you can replay the execution of the script to retrieve the missing topology data. You can use one of the following methods to execute the script: > with VistaCockpit. This method consists in launching the VistaCockpit workflow directly from the VistaCockpit Management Console. The workflow launches the topology file generation and the VistaMart provisioning. in command line. If you use the following method, once the generation is completed, you must launch the VistaMart provisioning manually.

>

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

T

Troubleshooting

65

Replay missing topology data (with VistaCockpit) 1 Launch the VistaCockpit Management Console. 2 From the Tasks tab, Select the VistaLink for SAM 5620 Workflow (Topology). 3 From the General tab in the right-hand pane, click the Execute button.

Replay missing topology data (in command line) 1 Backup the lastRun.xml file.
WARNING If you do not backup the lastRun.xml file, the system overrides the

existing file with the data corresponding to the directory you want to replay.

2 Open a command prompt window or terminal. 3 Execute the following command:

sam_topo.sh (or .bat) sam_cfg.xml <number_of_retry> <timeout>
EXAMPLE

To replay one hour of missing data, execute the following command:

sam_topo.sh sam_cfg.xml 1 1

4 Launch the VistaMart Inventory Manager to import the topology file.

NOTE

You can also generate the performance data in one stage: see "Generating the performance data in one script (optional)" on page 53. If you use VistaLink with InfoVista Server (i.e. with VistaInsight for Network), make sure you correctly configured the specific parameters sam_cfg.xml file.

NOTE

DURING THE IMPORT PROCESS (WHEN

VISTALINK CONNECTS TO VISTAMART TO IMPORT DATA FILES)

When a network failure occurs during the import process for example, you can relaunch the provisioning of VistaMart. > > Via VistaMart Inventory Manager, importing the topology file. In command line, using the sam_provisioner script in command line: sam_provisioner <number_of_retry> <timeout>

Network failure or connection problems during performance data generation

DURING THE EXPORT PROCESS (WHEN

VISTALINK CONNECTS TO SAM SERVER TO RETRIEVE DATA)

When a network failure occurs during the export process for example, you can replay the execution of the script to retrieve the missing performance data. Two methods enable to retrieve the missing performance data: >
replay one hour of missing data. You use this method to retrieve the data of one hour (i.e. one subdirectory). Once the generation is completed, you must launch the VistaMart provisioning manually. replay one or several hours of missing data ( SOLARIS ONLY). This method is only available on Solaris platforms. This method requires ProcessDir.sh located in the bin directory.

>

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Troubleshooting

66

When you use this method, you must create a new temporary directory in which you paste the subdirectories containing the XML files corresponding to the requests results you want to process. The temporary directory (referred to as source_directory) only works as a reference so that VistaLink knows which data to retrieve. The script then automatically provisions VistaMart.

For both methods, VistaLink launches the performance data generation for the file(s) included in the subdirectory you declare.
T

Replay one hour of missing performance data 1 Backup the lastRun.xml file.
WARNING If you do not backup the lastRun.xml file, the system overrides the

existing file with the data corresponding to the directory you want to replay.

2 Open a command prompt window or terminal. 3 Execute the following command:

sam_stat.sh (or .bat) sam_cfg.xml <number_of_retry> <timeout> -d <target_directory>
EXAMPLE

To replay one hour of missing data, execute the following command:

sam_stat.sh sam_cfg.xml 1 1 -d /opt/InfoVista/VistaLinks/SAM/ done/2006_08_28_19_11_45 The new request files are updated in the stat directory (located in VistaLinks\done). You can now import the performance data files (CSV/XML located in the data directory) into VistaMart (see "Import performance data files in VistaMart via VistaBridge" on page 53.)
T

Replay one or several hours of missing performance data (SOLARIS ONLY) 1 Copy the directories you want to replay in a new directory ( / replay for example).
NOTE

The generated performance files are located in ../done/stat. Each subdirectory is named with the date and time (i.e yyyy_mm_dd_hh_mm_ss)

2 Open a terminal. 3 Execute the following command:

ProcessDir.sh sam_cfg.xml <path_to_source_directory> <pathto_target_directory>
EXAMPLE

ProcessDir.sh sam_cfg.xml ../replay /tmp

4 The system displays: Keep current lastRun file? [Y/N] 5 Answer yes: Y or no: N
WARNING If you answer N (no), the system overrides the existing file with the data

corresponding to the replay directory.

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Troubleshooting

67

6 If you answer Y (yes), enter the directory name where you want to backup
lastRun.xml: /opt/InfoVista/VistaLinks/SAM/data
NOTE

In the ProcessDir.sh script, default values are defined for:

> number of retry = 1 > timeout period = 1 > > The new performance data files (CSV/XML) are updated in the data directory and automatically sent to VistaMart. The XML files containing the requests results are updated in the stat directory (located in VistaLinks/done).

DURING THE IMPORT PROCESS (WHEN VISTALINK CONNECTS TO VISTAMART TO IMPORT DATA FILES)
When a network failure occurs during the import process for example, you can replay the execution of the script to provision VistaMart with the missing performance data.
EXAMPLE

The following message displays in the command prompt window and is recorded in VistaCockpit log file. The message is also sent by email if you have configured VistaCockpit.

The message indicates the name of the task that could not be executed and the name of the files that were not imported in VistaMart.
T

Replay one hour of missing performance data 1 Backup the lastRun.xml file.
WARNING If you do not backup the lastRun.xml file, the system overrides the

existing file with the data corresponding to the directory you want to replay.

2 Open a command prompt window or terminal. 3 Execute the following command:

sam_stat.sh (or .bat) sam_cfg.xml <number_of_retry> <timeout> -d <target_directory> Installation Guide - Chapter 4 Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Troubleshooting

68

EXAMPLE

To replay one hour of missing data, execute the following command:

sam_stat.sh sam_cfg.xml 1 1 -d /opt/InfoVista/VistaLinks/SAM/ done/2006_08_28_19_11_45 The new request files are updated in the stat directory (located in VistaLinks\done)

4 Launch sam_VB to import the performance data files (CSV/XML located in the data
directory): sam_VB.bat <number of retry> <timeout (seconds)> (or sam_VB.sh <number of retry> <timeout (seconds)>)
T

Replay several hours of missing performance data (SOLARIS ONLY) 1 Copy the directories you want to replay in a new directory ( / replay for example).
NOTE

The generated performance files are located in ../done/stat. Each subdirectory is named with the date and time (i.e yyyy_mm_dd_hh_mm_ss)

2 Open a terminal. 3 Execute the following command:

ProcessDir.sh sam_cfg.xml <path_to_source_directory> <pathto_target_directory>
EXAMPLE

ProcessDir.sh sam_cfg.xml ../replay /tmp

4 The system displays: Keep current lastRun file? [Y/N] 5 Answer yes: Y or no: N
WARNING If you answer N (no), the system overrides the existing file with the data

corresponding to the replay directory.

6 If you answer Y (yes), enter the directory name where you want to backup
lastRun.xml: /opt/InfoVista/VistaLinks/SAM/data
NOTE

In the ProcessDir.sh script, default values are defined for:

> number of retry = 1 > timeout period = 1 > > The new performance data files (CSV/XML) are updated in the data directory and automatically sent to VistaMart. The XML files containing the requests results are updated in the stat directory (located in VistaLinks/done).

Installation Guide - Chapter 4

Data files generation

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Troubleshooting

69

Error of type 3 - memory problems

Here is an example of the problems referenced as error of types 3.
EXAMPLE

The following messages display in the command prompt window and is recorded in VistaCockpit log file.

Error occurred during initialization of VM Too small initial heap for new size specified ########### Number attempt :1 ########### error processing step : vistaLink - processing stopped

How to resolve the problem

Change the amount of memory allocated to VistaLink process. For more information, refer to the "The Configuration Wizard" on page 23.

Installation Guide - Chapter 4

Data files generation

5 Customizing VistaLink
This section describes how to customize VistaLink using the mapping file samVBmapping.xml.

"Mapping file overview" on page 73 "XML structure" on page 74

70

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

How to customize VistaLink?

71

How to customize VistaLink?

Customizing VistaLink consists in modifying the mapping file: samVbMapping.xml. For each Vista, the mapping file contains the definition of the calculation done by indicators to obtain the performance results. In the samVBmapping.xml, you can only act on the supported classes. To customize VistaLink follow the procedure below.
NOTE

Refer to the list of supported classes in "Alcatel-Lucent classes supported by VistaLink" on page 82

Customize VistaLink 1 Note the attribute and its class that corresponds to the information you want to get
and which does not already appear in the samVbMapping.xml.

2 Refer to "Alcatel-Lucent classes supported by VistaLink" on page 82 to verify if the

class is supported: If the class is not supported, you can not customize VistaLink. If the class is supported, you can create a new indicator in VistaMart that will receive the information from the class. In VistaMart, create a new indicator. This indicator will receive the information from the class.

3 Modify the samVbMapping.xml file such as:

<class name=supported class name> <BasicIndicator> <wid>new indicator wid</wid> <statAttrName>Alcatel-Lucent class attribute</statAttrName> <BasicIndicator> </class>

4 Note the MIB corresponding to the attribute and ensure this MIB is activated (refer
to "MIB to activate (optional)" on page 86).

Customization Example
In this example, we explain how to add a basic indicator that retrieves the data on Memory availability.

1 We note the attribute and its class that corresponds to the information we want to
get and which does not already appear in the samVbMapping.xml: package: equipment class: AvailableMemoryStatsLogRecord

Installation Guide - Chapter 5

Customizing VistaLink

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

How to customize VistaLink?

72

2 We refer to "Alcatel-Lucent classes supported by VistaLink" on page 82 to verify if the

class is supported: the AvailableMemoryStatsLogRecordclass is supported by VistaLink, so we can create a new indicator in VistaMart that will receive the information from the class.

3 In VistaMart, we create a new indicator. This indicator will receive the information
from the class: Indicator name = Available Memory WID = AAAAAAAAAAAAAA111111111111111111

4 We modify the samVbMapping.xml file such as:

5 We note the MIB corresponding to the attribute and ensure this MIB is activated
(refer to "MIB to activate (optional)" on page 86). The MIB corresponding to AvailableMemory is: TIMETRA-SYSTEM-MIB.sgiMemoryAvailable

Installation Guide - Chapter 5

Customizing VistaLink

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Mapping file overview

73

Mapping file overview

VistaLink refers to the mapping file during the data files generation (performance and topology). The mapping file samVbMapping.xml is located in the SAM/bin directory. Here is an extract of the mapping file:

Installation Guide - Chapter 5

Customizing VistaLink

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Mapping file overview

74

XML structure
The following table describes the XML tags of the mapping file.
XML tag Description

<mapping> <separator> <vistas> <vista>

Contains the whole set of tags. Indicates the type of character used as separator in the generated file. Contains all the Vista to map. Contains:

> <vistaname>: the Vista name. > <wid>: the Vista WID. > <statClasses> (see below) <statClasses> <class name=>
Lists the Alcatel-Lucent classes that provide performance data. Contains one <class name> tag per Alcatel-Lucent class. Indicates the name of the Alcatel-Lucent class (see "Alcatel-Lucent classes supported by VistaLink" on page 82). Contains the indicators definitions:

> <BasicIndicator> > <addIndicator> > <divideIndicator> > <deltaIndicator> > <deltaBySecsIndicator> > <corelIndicator> <BasicIndicator>
Contains:

> <wid>: indicator WID. > <statAttrName>: Alcatel-Lucent class attribute. > <output>: (optional tag) indicates if the indicator is generated ( YES) or not ( NO). YES is set as a default value. <addIndicator>
Contains:

> <wid>: indicator WID. > <baseWid>: WID of the indicators value to add. > <output>: (optional tag) indicates if the indicator is generated ( YES) or not ( NO). YES is set as a default value.

Installation Guide - Chapter 5

Customizing VistaLink

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Mapping file overview

75

XML tag

Description

<divideIndicator>

Contains:

> <wid>: indicator WID. > <baseWid>: WID of the indicator to take as the numerator. The denominator is defined by <divideBy> or a second <baseWid>. > <divideBy>: the denominator (the value is either a constant number or
the WID of an indicator).

> <output>: (optional tag) indicates if the indicator is generated ( YES) or not ( NO). YES is set as a default value. <deltaIndicator>
Contains:

> <wid>: indicator WID. > <maxValue>: maximum value of the counter ( 64bits by default). > <baseWid>: WID of the indicator on which the delta value is computed. > <output>: (optional tag) indicates if the indicator is generated ( YES) or not ( NO). YES is set as a default value. <deltaBySecsIndicator> Contains: > <wid>: indicator WID. > <maxValue>: maximum value of the counter ( 64bits by default). > <baseWid>: WID of the indicator on which the delta value is computed. > <output>: (optional tag) indicates if the indicator is generated ( YES) or not ( NO). YES is set as a default value. <corelIndicator>
Contains:

> <wid>: indicator WID. > <baseWid>: WID of the indicator which value is correlated with the value
coming from the topology data, defined by:

> <propertyVistaNameRef>: the Vista name. > <propertyNameRef>: name of the topology attribute. > <output>: (optional tag) indicates if the indicator is generated ( YES) or not ( NO). YES is set as a default value.

How to read the mapping file (Bandwidth calculation example)

The following table shows how the bandwidth is calculated from the mapping file. It helps you interpret the mapping file.

Installation Guide - Chapter 5

Customizing VistaLink

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Mapping file overview

76

Mapping file section

Corresponding calculation or meaning

<deltaBySecsIndicator> <output>NO</output> <wid>computeLoadIN</wid> <baseWid>DE2230CC405B9E4F87BD1CC323CF0709</ baseWid> </deltaBySecsIndicator> <divideIndicator> <output>NO</output> <wid>LoadIN</wid> <baseWid>computeLoadIN</baseWid> <divideBy>0.00125</divideBy> </divideIndicator> <corelIndicator> <wid>FAF66F51943A5D4C8853FE6926843D5A</wid> <baseWid>LoadIN</baseWid> <propertyVistaNameRef>LAN Interface</ propertyVistaNameRef> <propertyNameRef>Interface Speed</ propertyNameRef> </corelIndicator>

> the computeLoadIN indicator is a deltaBySecsIndicator > this indicator is not generated, i.e it is only
used for calculation purpose.

> this indicator is calculated from the indicator

which WID is

DE2230CC405B9E4F87BD1CC323CF0709. > the LoadIN indicator is a divideIndicator > this indicator is not generated, i.e it is only
used for calculation purpose.

> LoadIN = <computeLoadIN>/0.00125 (or x8x100) > the FAF66F51943A5D4C8853FE6926843D5A indicator is a corelIndicator > this indicator is generated, i.e it appears in
reports.

> Bandwidth=<LoadIN>/<Interface Speed>

About Accounting types and classes

Depending on the type of Accounting you set in the SAM server, you can choose the class you want to use to retrieve performance data for SAP Queues. In the mapping file extract, lets focus on the following Vistas: > > SAP Queues Ingress SAP Queues Egress

For each of these Vistas, you can replace the default classes by the following:
Vista SAP Queues Ingress Classes

> CombinedServiceIngressOctetsLogRecord > CompactServiceIngressOctetsLogRecord > ServiceIngressOctetsLogRecord

SAP Queues Egress

> CombinedServiceEgressOctetsLogRecord > ServiceEgressOctetsLogRecord

Installation Guide - Chapter 5

Customizing VistaLink

A Instances naming conventions

This appendix lists the naming conventions used to define instances. The following tables give the necessary information to understand the Instances names.

"SAM attributes definition" on page 78 "Instances names syntax" on page 79

77

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

SAM attributes definition

78

SAM attributes definition

The Instances names use the following SAM attributes.
SAM attributes siteName displayedName nodeName fromNodeName sn portName outerEncapValue innerEncapValue toNodeName pathId testTargetType Definition

the name of the device interface name node name destination Node name the service name the port number provisioned outer encap value. This value is propagated into: terminatedPortOuterEncapValue. provisioned inner encap value. This value is propagated into: terminatedPortInnerEncapValue. source node name path Id of Service Delivery Protocol Specifies the target type of the LSP ping test. The target can be an lsp, an lspPath, or a router. A target of lsp means that the targeted test will run against a specific LSP. The packetSize minimum is 98. A target of lspPath means that the targeted test will run against the specified path in an LSP. The lspPath parameter is mandatory when type is lspPath. The minimum packet size is 98. A target of router requires the ldpPrefix and ldpPrefixLen parameters to be configured. The targeted test will run on a router (specified in mplsSite) and attempt an LSP ping to a destination router(s) specified in the ldpPrefix and ldpPrefixLen. The minimum packet size is 84.

lspName forwardingClass profile testObject sourceIPAddress targetIPAddress

extracted from lsp the forwarding class the ping test uses. the profile value used with the forwarding class specified in forwardingClass. the managed object that is tested. the IPv4 address used as the source to perform the VPRN ping test. the IPv4 address used as the destination to perform the VPRN ping test.

Installation Guide - Appendix A

Instances naming conventions

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Instances names syntax

79

Instances names syntax

The following table shows the syntax of the Instances names as they appear in VistaMart Inventory Manager.
NOTE

The following syntax is only valid for Instances names, Instances tags have a different syntax.
Example

Vistas Router LAN/ WAN Interfaces MPLS Interface MPLS LSP Services (SAM SAP)

Instance Name syntax

siteName siteName:displayedName nodeName:displayedName-MPLS fromNodeName:displayedName-LSP

The syntax for the name of SAM SAP instances depends on how you set <serviceNameRule> in the sam_cfg.xml file

sim_80 sim_80:Port 1/1/1 sim_80:To 81 sim_80:80 to 82-LSP > sim_80:VPLS 11021:11021:Port 1/1/4:1601:0

> Case with <serviceNameRule> set to 1: nodeName:sn:serviceId:portName:outerEncapValue:innerE > sim_80:VPLS 11021: ncapValue Port 1/1/4:1601 > Case with <serviceNameRule> set to 2: nodeName:sn:portName:outerEncapValue > Case with <serviceNameRule> set to 3: nodeName:sn:serviceId:portName:outerEncapValue
See also: "" on page 44
SAP Queues The syntax for the name of the SAP Queues instances is based (Ingress or on the syntax of the SAM SAP and thus depends on how you Egress) set <serviceNameRule> in the sam_cfg.xml file .

> sim_80:VPLS 11021:11021: Port 1/1/4:1601

sim_80:IES service-4 sim_80 (10.1.1.1):N/ A:0:queue-1:Ingress

> Case with <serviceNameRule> set to 1: nodeName:sn:serviceId:portName:outerEncapValue:innerE ncapValue:displayedName:Ingress or Egress > Case with <serviceNameRule> set to 2 or 3: nodeName:sn:serviceId:portName:outerEncapValue:displa yedName:Ingress or Egress NOTE There is no difference between 2 and 3 as the name of a SAP queue instance contains the serviceId by default.
SAM SDP

fromNodeName:toNodeName:serviceName:pathId-SDP

sim_80:sim_81:VPLS 3:3201-SDP

Installation Guide - Appendix A

Instances naming conventions

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Instances names syntax

80

Vistas OAM LSP

Instance Name syntax

Example

testTargetType:fromNodeName:lspName:forwardingClass:p lsp:sim_80:LSP rofile 10.1.1.1 10.1.1.2:be:out vllSite:sim_82:EPIPE 11025 svc-mgr:service224:10.1.1.2:sim_81: 10.1.1.3:VPRN service-224 sim_81 (10.1.1.2)

OAM Layer 2 testTargetType:fromNodeName:serviceName OAM Layer 3 testObject:fromNodeName:targetIPAddress:serviceName

Installation Guide - Appendix A

Instances naming conventions

B Supported classes and MIB

This appendix lists the classes and MIB variables supported by VistaLink. You can use this list to set the polling interval of the MIB.

"Alcatel-Lucent classes supported by VistaLink" on page 82 "MIB" on page 84

81

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Alcatel-Lucent classes supported by VistaLink

82

Alcatel-Lucent classes supported by VistaLink

You use the following classes to modify the samVbMapping.xml.
NOTE

For further information on how to modify the samVbMapping

Classes integrated by default in the samVbMapping.xml

Class Package equipment

> systemCpuStats LogRecord > SystemMemoryStats LogRecord > InterfaceStatsLogRecord > InterfaceAdditionalStatsLogRecord > mplsInterfaceStatsLogRecord > LspStatsLogRecord > Lsp > LspPingResult > RouteStatsLogRecord > CompleteServiceIngressPacketOctetsLogRecord > CompleteServiceEgressPacketOctetsLogRecord > CombinedServiceEgressOctetsLogRecord > CombinedServiceIngressOctetsLogRecord > CompactServiceIngressOctetsLogRecord > ServiceEgressOctetsLogRecord > ServiceIngressOctetsLogRecord > MacPingResult > VprnPingResult

mpls

rtr service

vprn

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

Alcatel-Lucent classes supported by VistaLink

83

Classes requiring the creation of new indicators

To take the following classes into account, you have to create new indicators in VistaMart: one indicator per class. This indicator will receive the data retrieved by the class.
Class Package equipment

> AllocatedMemoryStatsLogRecord > AvailableMemoryStatsLogRecord > SonetSectionCurrentStats LogRecord > SonetFarEndLineIntervalStatsLogRecord > SonetLineCurrentStatsLogRecord > SonetPathCurrentStatsLogRecord > SonetFarEndPathCurrentStatsLogRecord

soneteequipment

> CompleteSubscriberIngressPacketOctetsLogRecord service > CompleteSubscriberIngressPacketOctetsLogRecord > NetworkEgressPacketsLogRecord > NetworkIngressPacketsLogRecord > NetworkEgressOctetsLogRecord > NetworkIngressOctetsLogRecord > CombinedNetworkIngressOctetsLogRecord > CombinedNetworkIngressOctetsLogRecord > Dot3Stats LogRecord > EthernetStatsLogRecord > EthernetStatsLogRecord > svt.SdpBindingBaseStatsLogRecord > service.CombinedSdpEgressPacketOctetsLogRecord > service.CombinedSdpIngressPacketOctetsLogRecord > service.CompleteSdpEgressPacketOctetsLogRecord > service.CompleteSdpIngressPacketOctetsLogRecord
svt ethernetequipment

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

84

MIB
This section lists the MIB activated by default and the MIB you can activate.

MIB activated by default

The followinf MIB are activated by default, with the contents of the mapping file.
NOTE

15 minutes is set as a default polling interval for each MIB.

Version MIB name MIB Entry name

Product name Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750

3.0.0 2.0.10 2.0.0 3.0.0 2.1.0 2.0.0 2.0.5 1.0.0 2.0.2 3.0.0 3.0.0 1.0.0 3.0.0 2.1.0 3.0.0 2.0.2 2.0.0 2.0.5 2.0.0 2.0.10 2.0.2 3.0.0 2.0.0 3.0.0

IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB IF-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB

ifEntry ifEntry ifEntry ifEntry ifEntry ifEntry ifEntry ifEntry ifEntry ifEntry ifXEntry ifXEntry ifXEntry ifXEntry ifXEntry ifXEntry ifXEntry ifXEntry ifXEntry ifXEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

85

Product name Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450

Version

MIB name

MIB Entry name

2.1.0 2.0.0 2.0.10 1.0.0 3.0.0 2.0.5 3.0.0 2.0.0 3.0.0 2.0.10 1.0.0 2.0.2 2.1.0 3.0.0 2.0.5 2.0.0 1.0.0 2.0.0 2.0.0 2.1.0 3.0.0 2.0.2 3.0.0 2.0.10 2.0.5 3.0.0 2.0.5 3.0.0 3.0.0 2.0.10 2.0.0 2.0.0 2.0.2

TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SERV-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-SYSTEM-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB

sdpBindBaseStatsEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry sdpBindBaseStatsEntry sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiCpuUsage sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed sgiMemoryUsed vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsIfStatEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

86

Product name Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450

Version

MIB name

MIB Entry name

3.0.0 1.0.0 2.1.0 3.0.0 3.0.0 3.0.0 2.0.0 1.0.0 2.1.0 2.0.0 2.0.5 2.0.10 2.0.2 2.0.10 3.0.0 2.0.0 3.0.0 2.0.2 3.0.0 1.0.0 2.0.5 2.1.0 2.0.0

TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-MPLS-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB TIMETRA-VRTR-MIB

vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsIfStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrMplsLspStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry vRtrStatEntry

MIB to activate (optional)

The following MIB must be activated if you customize the mapping file.
Product name Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Version MIB name MIB Entry name

2.0.2 3.0.0 3.0.0 4.0.0 2.0.0 4.0.0

EtherLike-MIB EtherLike-MIB EtherLike-MIB EtherLike-MIB EtherLike-MIB EtherLike-MIB

dot3StatsEntry dot3StatsEntry dot3StatsEntry dot3StatsEntry dot3StatsEntry dot3StatsEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

87

Product name Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750

Version

MIB name

MIB Entry name

2.0.0 3.0.0 1.0.0 2.1.0 2.0.5 2.0.5 2.0.2 2.1.0 3.0.0 2.0.0 2.0.0 4.0.0 3.0.0 4.0.0 3.0.0 3.0.0 3.0.0 3.0.0 4.0.0 4.0.0 3.0.0 3.0.0 4.0.0 4.0.0 3.0.0 4.0.0 3.0.0 2.1.0 2.0.5 2.0.0 2.0.2 1.0.0 2.0.0

EtherLike-MIB EtherLike-MIB EtherLike-MIB EtherLike-MIB EtherLike-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB RMON-MIB

dot3StatsEntry dot3StatsEntry dot3StatsEntry dot3StatsEntry dot3StatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry etherStatsEntry

TIMETRA-SYSTEM-MIB sgiMemoryAvailable TIMETRA-SYSTEM-MIB sgiMemoryAvailable TIMETRA-SYSTEM-MIB sgiMemoryAvailable TIMETRA-SYSTEM-MIB sgiMemoryAvailable TIMETRA-SYSTEM-MIB sgiMemoryAvailable TIMETRA-SYSTEM-MIB sgiMemoryPoolAllocated TIMETRA-SYSTEM-MIB sgiMemoryPoolAllocated TIMETRA-SYSTEM-MIB sgiMemoryPoolAllocated TIMETRA-SYSTEM-MIB sgiMemoryPoolAllocated TIMETRA-SYSTEM-MIB sgiMemoryPoolAllocated SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

88

Product name Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750

Version

MIB name

MIB Entry name

3.0.0 3.0.0 4.0.0 2.1.0 2.0.2 3.0.0 4.0.0 2.0.5 2.0.0 3.0.0 4.0.0 1.0.0 3.0.0 2.0.0 3.0.0 1.0.0 2.0.5 4.0.0 3.0.0 2.1.0 2.0.0 2.0.2 2.0.0 4.0.0 3.0.0 2.0.0 2.0.2 3.0.0 2.0.0 3.0.0 4.0.0 2.0.5 4.0.0

SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB

sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineCurrentEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndLineIntervalEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathCurrentEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

89

Product name Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750

Version

MIB name

MIB Entry name

3.0.0 2.1.0 1.0.0 4.0.0 3.0.0 2.1.0 3.0.0 2.1.0 3.0.0 4.0.0 3.0.0 3.0.0 3.0.0 4.0.0 1.0.0 4.0.0 2.0.5 2.0.0 2.0.2 2.0.0 3.0.0 2.1.0 2.1.0 3.0.0 4.0.0 3.0.0 1.0.0 2.0.2 2.0.0 4.0.0 3.0.0 2.0.5 2.0.0

SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB

sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndPathIntervalEntry sonetFarEndVTCurrentEntry sonetFarEndVTCurrentEntry sonetFarEndVTCurrentEntry sonetFarEndVTCurrentEntry sonetFarEndVTIntervalEntry sonetFarEndVTIntervalEntry sonetFarEndVTIntervalEntry sonetFarEndVTIntervalEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineCurrentEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry sonetLineIntervalEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

90

Product name Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450

Version

MIB name

MIB Entry name

4.0.0 2.0.0 4.0.0 3.0.0 1.0.0 2.0.5 2.0.2 2.1.0 3.0.0 2.0.0 3.0.0 2.0.0 3.0.0 1.0.0 2.0.5 2.1.0 3.0.0 4.0.0 4.0.0 2.0.0 3.0.0 2.0.2 2.1.0 2.0.0 3.0.0 4.0.0 2.0.5 3.0.0 3.0.0 2.0.0 1.0.0 4.0.0 2.0.2

SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB

sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathCurrentEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetPathIntervalEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry sonetSectionCurrentEntry

Installation Guide - Appendix B

Supported classes and MIB

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

MIB

91

Product name Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-ESS-7450 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7750 Alcatel-ESS-7450 Alcatel-SR-7710 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7750 Alcatel-SR-7710

Version

MIB name

MIB Entry name

2.0.0 3.0.0 2.0.5 3.0.0 4.0.0 2.0.0 2.1.0 3.0.0 2.0.2 4.0.0 1.0.0 3.0.0 4.0.0 2.1.0 3.0.0 3.0.0 2.1.0 4.0.0 3.0.0

SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB SONET-MIB

sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetSectionIntervalEntry sonetVTCurrentEntry sonetVTCurrentEntry sonetVTCurrentEntry sonetVTCurrentEntry sonetVTIntervalEntry sonetVTIntervalEntry sonetVTIntervalEntry sonetVTIntervalEntry

Installation Guide - Appendix B

Supported classes and MIB

92

Index
C
Configuration Wizard . . . . . . . . . . . . . . . . . . . . . 23

L
LastRun.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

F
files parameters . . . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . filters parameters . . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M
..
27 memory spaces . . . . . . . . . . . . . . . . . . . . . . . . . allocating . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

..
30

N
Network failure, connection problems . . . . . . . . 64

G
generating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance data . . . . . . . . . . . . . . . . . . . . 51

O
OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

H
history management parameters . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

P
Performance data. . . . . . . . . . . . . . . . . . . . . . . . launching the performance script . . . . . . . . network failure management. . . . . . . . . . . . provisioning VistaMart. . . . . . . . . . . . . . . . . results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VistaCockpit workflow (configuring) . . . 59, ProcessDir.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 52 52 53 54 60 65

I
Installation directories . . . . . . . . . . . . . . . . . . . . . bin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . doc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . done. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HotFixes . . . . . . . . . . . . . . . . . . . . . . . . . . . jre. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . vviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 20 20 20 20 21 21 21 21 21 21 21 21

R
retrieval rules parameters . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

S
SAM FTP parameters . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 SAM host parameters . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 SAM SSH parameters . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 samVbMapping.xml . . . . . . . . . . . . . . . . . . . . 8, 70 SAP queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

K
keepLastRunHistory . . . . . . . . . . . . . . . . . . . . . . 43

VistaLink 3.0 for Alcatel-Lucent 5620 SAM Installation Guide

Index

93
Scheduling files generation . . . . . . . . . . . . . . . . . with the system tool . . . . . . . . . . . . . . . . . . . 61 with VistaCockpit . . . . . . . . . . . . . . . . . . . . . 55 SDPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . users and groups. . . . . . . . . . . . . . . . . . . . . 17 VistaMart parameters . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

X,Y,Z
zoneset parameters . . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

T
timeout parameters . . . . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . keepLastRunHistory . . . . . . . . . . . . . . . . . . 43 Topology data . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 launching the topology script . . . . . . . . . . . . 47 network failure management . . . . . . . . . . . . 47 Provisioning VistaMart. . . . . . . . . . . . . . . . . 47 results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 VistaCockpit workflow (configuring). . . . . . . 57 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 63 error of type 1 . . . . . . . . . . . . . . . . . . . . . . . 63 error of type 2 . . . . . . . . . . . . . . . . . . . . . . . 64 error of type 3 . . . . . . . . . . . . . . . . . . . . . . . 69

U
user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . verifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

V
VistaBridge parameters . . . . . . . . . . . . . . . . . . . setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 VistaCockpit workflow . . . . . . . . . . . . . . . . . . . . . configuring . . . . . . . . . . . . . . . . . . . . . . . . . . 57 importing . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 performance (configure) . . . . . . . . . . . . . . . 59 schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 topology (configure). . . . . . . . . . . . . . . . . . . 57 VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 VistaLink on solaris . . . . . . . . . . . . . . . . . . . . . . installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 VistaLink on windows . . . . . . . . . . . . . . . . . . . . . installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configuring . . . . . . . . . . . . . . . . . . . . . . . . . . 33 creating a new InfoVista Server object . . . . 37

VistaLink 3.0 for Alcatel-Lucent 5620 SAM Installation Guide

Index

VistaLink 3.0 for Alcatel-Lucent 5620 SAM

94

Remarks
VistaLink 3.0 for Alcatel-Lucent 5620 SAM Installation Guide 2008

We welcome any comments you have on our product and its documentation. We examine thoroughly your remarks and take them into account whenever possible for future product versions.

ERRORS DETECTED

SUGGESTED IMPROVEMENTS

Please send this completed form to: InfoVista SA 6 rue de la Terre de Feu 91952 Courtaboeuf cedex France If you prefer, you may send your remarks via E-mail to [email protected] Thank you for your cooperation.

Installation Guide