Escolar Documentos
Profissional Documentos
Cultura Documentos
0 for
Alcatel-Lucent
5620 SAM
Installation and Configuration
December 2013
2
web : www.infovista.com
E-mail: support@infovista.com
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide
3
Contents
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Contents
4
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Contents
5
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Contents
6
5 Troubleshooting VistaLink
Generating a support package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Troubleshooting VistaMart provisioning update failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Troubleshooting missing data in VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Replaying missing performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Replay missing performance data in FindToFile or Find mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Troubleshooting issues when entering a JMS client name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Contents
1 Getting Started with
VistaLink® 4.0 for Alcatel-
Lucent 5620 SAM
This chapter provides an overview of the VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
documentation, of the new features and of the VistaLink process.
7
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM About this guide 8
Purpose
This VistaLink for Alcatel-Lucent 5620 SAM Installation Guide contains all the necessary
information to install, configure, upgrade and customize a VistaLink for Alcatel-Lucent 5620 SAM.
Intended audience
This guide is intended for operators and engineers in charge of installing, configuring and
customizing the VistaLink for Alcatel-Lucent 5620 SAM.
To use this guide effectively, you need to be familiar with:
• Windows®, Solaris® or Linux® environments
• network-specific features
Organization
This table provides an overview and direct access to the information available in this guide:
Section Topics
"Getting Started with Provides an overview of the VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for documentation, its new features and processes.
Alcatel-Lucent 5620
SAM"
"Installing VistaLink Provides the installation workflow and explains how to install, uninstall
for Alcatel-Lucent and upgrade VistaLink for Alcatel-Lucent 5620 SAM.
5620 SAM"
"Configuring Describes how to configure the VistaLink once you have installed
VistaLink for Alcatel- VistaLink® 4.0 for Alcatel-Lucent 5620 SAM. It also describes how to back
Lucent 5620 SAM" up and restore the configuration and manage the VistaLink service.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM About this guide 9
Section Topics
"Customizing your Explains how to customize your VistaLink to be able to discover new
VistaLink for Alcatel- instance types, filter the instance types to discover and create your own
Lucent 5620 SAM" indicators.
"Troubleshooting Indicates how to generate a support package and provides basic
VistaLink" procedures for troubleshooting your VistaLink.
"Monitoring Provides basic steps for monitoring VistaLink from the VistaCockpit
VistaLink with Management Console.
VistaCockpit"
"Instance naming Provides the necessary information to interpret the codification of the
and tagging name and tag (identifier) of each monitored instance.
conventions"
"Supported classes Provides the comprehensive list of Alcatel-Lucent classes and MIB
and MIB’s" variables supported by VistaLink for Alcatel-Lucent 5620 SAM.
Related documentation
VistaLink for Alcatel-Lucent 5620 SAM documentation
Depending on your objectives you can use the following Alcatel-Lucent 5620 SAM documents in
either PDF or HTML format.
Document Purpose
Installation Guide Use the present Installation Guide if you are planning to install, deploy,
upgrade or customize a VistaLink for Alcatel-Lucent 5620 SAM on
Windows, Solaris or Linux platforms. In particular, this guide describes the
Configuration Wizard that you will use each time you need to modify your
VistaLink Setup.
User Guide Use this guide to understand how VistaLink for Alcatel-Lucent 5620 SAM
works and to get VistaPortal page package and indicator descriptions.
The HTML version of the User Guide helps you navigate through the
VistaPortal pages. It provides a detailed description of the available
reports and a definition of the Key Performance Indicators (KPI’s) that are
started for the VistaLink.
Other documents
To perform given tasks described in the VistaLink for Alcatel-Lucent 5620 SAM Installation Guide
or to understand some concepts, you need to refer to the following additional VistaFoundation Kit
documents:
• VistaMart User Guide
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM About this guide 10
In some cases, you may also need to refer to the Alcatel-Lucent 5620 SAM documentation.
You can also access the PDF version from the HTML version by clicking the icon at the
top right of any HTML page.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM What’s new? 11
What’s new?
This releases includes the following new features:
Enhanced • By using the new VistaLink extensible framework, this version enables
scalability
polling and reporting on:
• more resources
• instance types that you add to your InfoVista solution model.
• Archiving is improved.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 12
Technology overview
The VistaLink for Alcatel-Lucent 5620 SAM is an InfoVista product that enables you to push
statistic and topology data obtained from the Alcatel-Lucent 5620 SAM (Service Aware Manager)
server into VistaMart.
VistaLink monitors the performance, availability and utilization of the various devices managed by
the SAM server.
This section provides an overview of the following topics:
"Architecture and data flow" on page 12
"Data retrieval modes" on page 13
"Data acquisition mechanism" on page 17
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 13
VistaLink process
Once VistaLink is installed and connection is established with the SAM server, VistaLink starts
retrieving data from the SAM server. As illustrated in the diagram above, when you launch
VistaLink, it:
1 accesses topology changes on the SAM server via FTP (File Transfer Protocol) following a
SOAP (Simple Object Access Protocol) request.
2 provisions the topology changes into VistaMart.
3 accesses statistics files on the SAM server via FTP following a SOAP request and, in the case of
LogToFile mode (see "Data retrieval modes" on page 13), a JMS (Java Message Service)
notification.
4 parses the statistics files depending on the slots that are started on the VistaMart server and
generates the KPI (Key Performance Indicator) values required for performance management
and imports them into VistaMart.
• FindToFile mode
• Find mode
• Local mode
All modes are used to retrieve statistics (performance and accounting) data and topology data,
except for the LogToFile Mode which is used only to retrieve statistics data.
This section describes each mode.
To set the data retrieval mode, see "Setting the data retrieval mode" on page 62.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 14
FindToFile mode
In FindToFile data retrieval mode, VistaLink sends SOAP requests to the SAM server. The SAM
server answers to the VistaLink by indicating availability and location of the statistics or topology
XML files each time they are generated by the SAM server. VistaLink then retrieves the XML files
using FTP or SFTP (depending on what you set in sam_cfg.xml). This mode requires that you have
set an FTP server on your Alcatel-Lucent 5620 SAM machine and that you know the SAM output
directory (this is configured when you install your SAM server). The request results are then stored
in the specified data directory.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 15
LogToFile mode
The LogToFile data retrieval mode maintains up-to-date accounting and performance statistics
export files. In this mode, the SAM server periodically notifies the VistaLink of XML data files
availability and location (possibly on an auxiliary host) via a JMS event service. VistaLink retrieves
the compressed statistics files, formats them and makes them available for processing. InfoVista
recommends using this mode which supports high data collection rates. If you wish to minimize
collection latency and reduce system load, use the LogToFile option.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 16
Find mode
In Find data retrieval mode, VistaLink sends XML requests to the SAM server. Answers are
delivered as XML/SOAP messages. In this mode, the request results are not stored.
Local mode
In Local data retrieval mode, instead of sending requests to the SAM server, VistaLink retrieves
data from a local directory where it is stored.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 17
2 At each subsequent polling, VistaLink compares the data maximum history duration to the time
elapsed between the current timestamp (now) and the ‘last run’ timestamp stored in the
LastRun.csv file:
• If the elapsed time is smaller than the History (minutes) parameter value, VistaLink refers to
the ‘last run’ timestamp and polls all the points available from that time, as illustrated below.
There is no loss of data.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Technology overview 18
• If the elapsed time is larger than the History (minutes) parameter value, VistaLink ignores
the ‘last run’ timestamp and polls only the points made available during the Data Maximum
History period, as illustrated below. All the points beyond the data maximum history value are
lost.
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Starting the VistaLink 19
Installation and Configuration Guide - Chapter 1 Getting Started with VistaLink® 4.0 for Alcatel-Lucent 5620 SAM
2 Installing VistaLink for
Alcatel-Lucent 5620 SAM
This chapter provides the standard installation workflow and explains how to install, uninstall and
upgrade VistaLink for Alcatel-Lucent 5620 SAM.
20
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Standard installation workflow 21
Once the installation is completed successfully, VistaLink starts retrieving data from the Alcatel-
Lucent 5620 SAM server then automatically pushes data into VistaMart.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Ensuring installation prerequisites 22
• has read and write rights to access FTP files and delete processed files.
In the case remote file compression is to be activated from the VistaLink Configuration Wizard,
create a Unix user with SSH (Secured SHell) permissions and rights to create files in the Alcatel-
Lucent 5620 SAM data directories.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Ensuring installation prerequisites 23
• configuring accounting
• Make sure the VistaFoundation products are installed in the following order:
• Make sure VistaMart, VistaPortal and database services are up and running.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Ensuring installation prerequisites 24
infovista user
• The infovista user is automatically configured so that it cannot be used for login except from
root for installation and configuration purposes. Do not modify the infovista user. So not set any
password.
• The VistaLink installation script automatically checks if the infovista user and the infovista
group already exist. If they are not found, the script creates them automatically.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring VistaMart 25
Configuring VistaMart
This section describes the following configuration procedures you need to perform from the
VistaMart Inventory Manager:
"Importing VistaView libraries" on page 25
"Importing event message formats" on page 26
"Setting up VistaLink data visibility in VistaMart" on page 27
5 Make sure the libraries in bold are selected and click (Import).
6 When the process is completed, in the Message box click OK.
7 Click Close.
8 Repeat procedure from step 3 for the following VistaView packages, depending on your case:
• <VistaLink Installation Directory>\vviews\patches\<build_number>-vviews.zip,
whether you are installing for the first time or upgrading your solution
• <VistaLink Installation Directory>\vviews\Upgrade\SAM40_Upgrade_VV_Package.zip, only
in the case of an upgrade.
9 Close the Library Management window.
10 In VistaMart Inventory Manager, click the Model tab.
The VistaView libraries appear under the VistaMart and VistaBridge libraries nodes.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring VistaMart 26
8 In the Targets tab, select the VistaMart target and click Edit.
The Target edition dialog box opens.
9 In the Filterset drop-down list, select Infovista Solution and click OK.
10 In the Event Target Management window, click Save then Close.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring VistaMart 27
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaLink 28
Installing VistaLink
This section addresses the installation of VistaLink® 4.0 for Alcatel-Lucent 5620 SAM in the
following environments:
• Windows
• Solaris
Prerequisites
• You have ensured installation prerequisites (see "Ensuring installation prerequisites" on
page 22).
• You have configured VistaMart and imported the VistaViews library packages (see "Configuring
VistaMart" on page 25).
Install VistaLink
1 In the VistaLink installation package:
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaLink 29
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaLink 30
• Click Restore Default Folder to reset the path to the default directory.
3 Check that the VistaLinks\SAM directory is now available at your choice location. By default:
• For Windows: C:\Program Files (x86)\Infovista\VistaLinks\SAM
• For Unix: /opt/InfoVista/VistaLinks/SAM
For details on the contents of the installation directory, see "Checking directories and files" on
page 31.
4 Use the Configuration Wizard to prepare your VistaLink for Alcatel-Lucent 5620 SAM
configuration (see "Using the Configuration Wizard" on page 55).
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, thereby ensuring that you are not prompted twice for identical data.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Checking directories and files 31
Directory Description
bin Contains VistaLink scripts, including the support package generation tool
and the Configuration Wizard.
config Contains VistaLink properties files.
doc Contains HTML and PDF folders where you find the:
• the PDF version of both VistaLink Installation and User guides
• done, used for archiving the statistics and topology files from the SAM
Server once they have been processed
• ini, which contains the default protocol templates and discovery files.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 32
Prerequisite
You have installed the VistaLink (see "Installing VistaLink" on page 28).
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 33
The HTML version of the Alcatel-Lucent 5620 SAM User Guide opens.
You can now log into your VistaPortal Management Console home page and perform the following
steps:
"Creating the connection to the database" on page 33
"Importing the Page Packages" on page 35
"Importing users and groups" on page 37
Prerequisite
You have deployed the VistaLink on VistaPortal (see "Deploying VistaLink and solution page online
help on VistaPortal" on page 32).
Name Description
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.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 34
Name Description
Host The host name of the VistaMart Oracle database 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 SID The name of the VistaMart database. This corresponds to the
database IVDB. This field is mandatory.
Database type Select the default option: ORACLE
User A valid operator user for the host. This field is mandatory. The user
and password were set in VistaMart when the database was created;
the VistaMart administrator can provide a valid viewer user for the
database to use in this field.
Password Password for the login name
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 35
Prerequisite
You have deployed the VistaLink on VistaPortal (see "Deploying VistaLink and solution page online
help on VistaPortal" on page 32).
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 36
8 Click Import.
A message indicates that the import was successful.
9 Click Close.
10 Verify that the following Page Packages and related pages were correctly imported.
Refer to the VistaLink for Alcatel-Lucent 5620 SAM User Guide for a description of each page
package.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 37
Prerequisite
You have deployed the VistaLink on VistaPortal (see "Deploying VistaLink and solution page online
help on VistaPortal" on page 32).
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 38
8 Click Import.
9 Click Close.
10 Verify that the SAM users groups were correctly imported:
11 Connect to the VistaPortal login page and use the default user name and password:
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 39
Prerequisites
You have imported the VistaLink for Alcatel-Lucent 5620 SAM solution pages, users and groups
into VistaPortal (see "Importing the Page Packages" on page 35 and "Importing users and groups"
on page 37).
3 Select the User group you wan to add a user to (for example, Customer Users).
4 In the Users tab of the chosen user group page, click Add.
The Add New User window appears.
5 Add a login for the new user. The other fields are optional.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 40
6 Click Save.
The Users tab of the chosen user group page refreshes with the new user.
For information on creating a customized user not linked to an existing Users Group or
creating a new subgroup, refer to chapter Managing Users and Subgroups of the VistaPortal
Author Guide.
Prerequisites
You have created users in VistaPortal (see "Creating customized users" on page 39).
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 41
7 Click Save.
Once you have saved the variable and re-run a report in VistaPortal, the report for the customer
user displays only the designated customer.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installing VistaPortal resources 42
The following example displays the report before and after filtering:
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Uninstalling VistaLink 43
Uninstalling VistaLink
Use the following procedures to uninstall your VistaLink either from a Windows or a Unix platform.
Prerequisites
• If you want to save your configuration as well as data before you uninstall your VistaLink back
up the following directories from your VistaLink installation directory:
• config
• sam, with all its sub-directories.
• Stop the VistaLink service.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 44
What changes
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM is based on a VistaLink extensible framework and
provides many customization features. As a server component, VistaLink now handles task
scheduling autonomously without VistaCockpit. It uses topology mapping files that you can
customize for each instance type and supports many more classes. Therefore the mapping and
general VistaLink configuration files of your previous version are no longer applicable.
Configuration files
After its upgrade, the VistaLink will no longer use the following files:
• general VistaLink configuration files:
• sam_cfg.xml (in its previous format)
• sam_global.xml
• mapping files:
• samTopoMapping.xml
• samMapping.xml
• samStatAddMapping_Advmodule.xml
• samStatAddMapping.xml
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 45
VistaCockpit workflows
• VistaLink no longer requires setting workflows in VistaCockpit.
VistaMart zones
• VistaLink automatically creates and names four different zones in VistaMart during its
configuration.
• The upgrade transfers the resources to the new zones if the zone names change during the
upgrade.
• Former zones are preserved and left either empty or with instances that could not be migrated.
• the instance name has not changed from one version to another
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 46
File.. includes...
OLD_Instances_Not_ the instances that are part of the previous topology that were not
Found_In_4_0.csv discovered in the new SAM server topology
4_0_New_Instances. the instances discovered in the new SAM server topology that were not
csv part of the previous topology and therefore do not need to be migrated
OLD_Duplicate_Inst all the instances (mainly service instances) from the previous VistaMart
ances.csv database that have multiple names and therefore cannot be matched by
their names
4_0_Duplicate_Inst all the instances from the SAM server topology that have multiple names
ances.csv and therefore cannot be matched by their names
If... then...
you want to keep the users you created with unsubscribe all the users from the previous
your previous version Page Packages (see following section
‘Unsubscribing the previous VistaLink for SAM
Users‘)
you do not need to keep the users you delete the user groups (see following section
created with your previous version ‘Deleting the previous VistaLink for SAM Users’)
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 47
• sam_global.bat(sh)
• sam_global.xml
• samTopoMapping.xml
• samMapping.xml
• samStatAddMapping_Advmodule.xml
• samStatAddMapping.xml
Copy these files and any other configuration files you have possibly customized for the previous
VistaLink version to a temporary directory to keep a backup of your previous configuration
parameters. If you are installing the new VistaLink version on a different machine make sure to
copy these files to the new machine.
3 In the right-hand pane, in the Subscriptions tab, unsubscribe all the users from the
SAM31_Customer page package by clicking :
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 48
4 In the tree view, expand SAM Users Groups and select Customer Users.
5 In the right-hand pane, click the Subscriptions tab.
6 Unsubscribe all the users that belong to the Customer Users group from the SAM31 Customer
page package by clicking .
7 Repeat procedure similarly from step 4 for Engineers Users and Manager Users.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 49
All the users that are part of the SAM Users Group are now deleted.
! The upgrade process updates the topology and the VistaViews in your VistaMart database.
VistaMart database updates cannot be undone. Make sure you have backed up your
VistaMart database before launching the upgrade.
Prerequisite
See "Ensuring upgrade prerequisites" on page 46
The Welcome panel of the installation wizard should indicate that a previous version
has been detected and will be upgraded.
4 When the Configuration Wizard starts, set the parameters as needed in the VistaMart
Connection panel and click Next.
If VistaLink detects the existence of former SAM data in the VistaMart database, the Upgrade
Wizard starts.
5 Depending on the case:
• If you have launched the installation on the machine where the previous VistaLink is installed,
read the welcome panel of the upgrade wizard and click Proceed. The Upgrade Wizard
automatically retrieves the pre-existing configuration files in the former VistaLink installation
directory.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 50
• If you have launched the installation on a different machine, the following welcome panel
appears: click ... to browse to the location on your machine where you copied the
configuration files from the former machine and click Proceed.
The Configuration Files Analysis panel opens and indicates the results of the configuration
parameters and mapping files analysis.
For example:
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 51
6 Depending on the operating system of your new VistaLink platform, and if the Upgrade process
has detected customized KPI’s in your previous configuration, you can obtain formula
suggestions for those KPI’s either by:
• browsing to the <New VistaLink installation
directory>\VL_SAM_Upgrade_Output\KpiGeneratedFiles and opening the Custom_KPIs.csv
• or, if available, clicking View Configuration Analysis, which takes you directly to the folder
that contains the file.
7 Click Next.
The Topology Analysis panel opens and indicates the percentage of instances that can be
migrated and why the other instances cannot be migrated.
For example:
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 52
8 Depending on the operating system of your new VistaLink platform, you can obtain details on the
instances that cannot be migrated either by:
• browsing to the <New VistaLink installation
directory>\VL_SAM_Upgrade_Output\topologyGeneratedFiles folder.
• or, if available, clicking View Topology Analysis, which takes you directly to the folder that
contains the files.
For information on the files provided under <New VistaLink installation
directory>\VL_SAM_Upgrade_Output\topologyGeneratedFiles see "Upgrade process overview"
on page 45.
9 Click Next.
The Upgrade Process Information box opens and possibly reminds the percentage of instances
that cannot be migrated and that the migration process cannot be undone.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Upgrading to VistaLink® 4.0 for Alcatel-Lucent 5620 SAM 53
For the instances that were not migrated due to a name change issue, you may modify
their name manually directly from your VistaMart Inventory Manager (see your
VistaMart User Guide). For those that encounter a tag change issue, in order to ensure
data continuity, you have to request help from your InfoVista support.
Installation and Configuration Guide - Chapter 2 Installing VistaLink for Alcatel-Lucent 5620 SAM
3 Configuring VistaLink for
Alcatel-Lucent 5620 SAM
This chapter describes how to use the Configuration wizard which is launched automatically by the
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM installer. It also describes how to start it later in order
to modify the initial configuration.
This chapter also provides advanced configuration procedures that you can perform after running
the Configuration Wizard.
54
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 55
A web browser is required to access the help pages from the Configuration Wizard.
Whether the configuration starts automatically following the VistaLink for Alcatel-Lucent SAM
installation or whenever you decide to run it, you are guided to perform tasks in a given order:
Your configuration is saved only if you validate it in the last Finish panel (see "Finalizing the
configuration" on page 87).
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 56
Prerequisite
You have installed the VistaLink (see "Installing VistaLink for Alcatel-Lucent 5620 SAM" on
page 20).
On... perform...
Windows either from the:
• the Start menu, select All Programs > InfoVista > VistaLink SAM
Configuration Wizard, or
• the <VistaLink Installation Directory>\bin directory, run
sam_config.exe.
Unix 1 Log in as the root user.
2 Go to the bin directory using command cd /opt/InfoVista/
VistaLinks/SAM/bin.
3 Run the ./sam_config.sh command.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 57
4 When you use the Configuration Wizard for the first time, enter each panel in sequence. If you
need to modify a given configuration panel, click Next until you reach it.
5 To obtain online help on a given panel, click Help.
6 To set parameters:
7 Once you have finished your settings, click Next until you reach the final panel.
8 Click Finish.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 58
Prerequisites
The VistaMart panel of the VistaLink configuration wizard is open.
If you use VistaInsight for Networks, you can use its parameters for configuring VistaMart
here, including host, user, password, etc.
1 Set the following parameters:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 59
• Devices
• Performance
• Accounting
SAM Groups the name of the zone designed to contain the group instances such as
Services and Customers.
(default value = SAM_GROUPS)
SAM Devices the name of the zone designed to contain the monitored devices
(routers, Microwave and LAN switches)
(default value = SAM_DEVICES)
SAM Performance the generic name of the zones designed to contain the monitored proxy
instances such as interfaces, cards, LAGs, SAM SAP’s, etc.
(default value = SAM_PERFORMANCE)
VistaLink may create several zones of this type depending on the
number of discovered proxies.
The size of this zone is constrained by a configurable threshold. To
configure the maximum number of instances to provision into the zones
dedicated to proxies (see "Understanding zones" on page 103).
SAM Accounting the generic name of the zones designed to contain the monitored proxy
instances such as OAM probes, SAP and network queues, etc.
(default value = SAM_ACCOUNTING)
VistaLink may create several zones of this type depending on the
number of discovered proxies.
The size of this zone is constrained by a configurable threshold. To
configure the maximum number of instances to provision into the zones
dedicated to proxies (see "Understanding zones" on page 103).
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 60
For example:
2 Click Next.
The Test Panel window opens to indicate the status of the:
• Application Services Connection test
• SAM VistaViews Test
• VistaMart Zone Test
• Database Connection test
If a status is red, select a test to get details on the test results at the bottom of the window.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 61
For example:
3 Click Close.
4 If necessary, correct your VistaMart connection parameters or install the VistaViews if required
and click Next again.
The Configuration Wizard proceeds to the Retrieval Mode panel.
Next step
See "Setting the data retrieval mode" on page 62.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 62
• FindToFile mode
• Find mode
• Local mode
All modes are used to retrieve statistics (performance and accounting) data and topology data,
except for the LogToFile Mode which is used only to retrieve statistics data. For more information
of the retrieval modes, see "Data retrieval modes" on page 13.
The following procedure enables you to specify the data retrieval modes.
Prerequisites
The Retrieval Mode panel of the VistaLink configuration wizard is open.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 63
Select... to...
LogToFile Mode retrieve XML statistics data files upon notification from the SAM server,
format them and make them available for periodic insertion into
VistaMart.
2 Click Next.
The Configuration Wizard proceeds to the SAM Connection panel.
Next step
See "Setting the SAM connection parameters" on page 64.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 64
Prerequisites
The SAM Connection panel of the VistaLink configuration wizard is open.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 65
To use https, you must create a KeyStore file using the Java
key tool (see the java web site at http://java.sun.com) and
configure the SAM server. This tag refers to the certificate file
(.keystore file): enter the path to the .keystore file.
KeyStore password the password associated with the KeyStore file.
Connection Time the waiting period in seconds after which an HTTP or HTTPS connection
Out (seconds) is no longer attempted.
After attempting to connect to the SAM server, VistaLink waits for the
SAM server to reply then stops attempting to connect if unsuccessful
after the specified period.
Data Time Out the network time out in seconds.
(seconds)
When VistaLink has not received any data from the primary server for the
specified time period, due to any network connection issue, then
VistaLink connects to the backup server. If the backup server does not
answer after the specified time period, the process stops.
For example:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 66
5 If available, select the Backup SAM Server tab and in Host, enter the IP address or the name of
the backup server.
All other parameters are identical to those of the primary server. For example:
.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 67
The FTP parameters are not used if you are in Find mode.
Prerequisites
The SAM Connection panel of the VistaLink configuration wizard is open.
In order to remove files from the SAM Server, the FTP user
defined in the Configuration Wizard, must have Delete File
rights.
4 To activate the FTP passive mode, select the Passive Mode checkbox.
5 To use the same Connection Time Out (Seconds) and Data Time Out (Seconds) settings
defined for SAM-O in the previous tab, select Use timeouts defined for SAM-O.
For example:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 68
6 If available, select the Backup SAM Server tab and repeat procedure from step 2 to set the
parameters for the backup SAM server.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 69
The SSH parameters are not used if you are in LogToFile or Find mode.
Prerequisites
The SAM Connection panel of the VistaLink configuration wizard is open.
To use... then...
the same settings as for FTP connections select Same Settings as FTP.
different settings make sure Same Settings as FTP is not
selected.
In order to remove files from the SAM Server, the SSH user
defined in the Configuration Wizard, must have delete file
rights.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 70
For example:
6 If available, select the Backup SAM Server tab and repeat procedure from step 2 to set the
parameters for the backup SAM server.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 71
About SSL
When you enable SSL (Secure Socket Layer), the Alcatel-Lucent 5620 SAM-OSS clients can
receive JMS XML messages securely by encrypting them through SSL. The SSL Certificate is
configured on the Alcatel-Lucent 5620 SAM server.
You must also configure the following client components:
• SSL KeyStore file on the OSS client
Prerequisites
The SAM Connection panel of the VistaLink configuration wizard is open.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 72
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 73
For example:
6 If available, select the Backup SAM Server tab and repeat procedure from step 2 to set the
parameters for the backup SAM server.
7 Click Next.
At this time, VistaLink checks the configured connections then returns the check results. The
Test Panel window opens to indicate the status of the SAM-O, FTP and JMS primary and backup
servers, as applicable:
In the case of a redundant connection, the status of the non active server is red:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 74
Next step
See "Setting the topology retrieval rules parameters" on page 75.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 75
Prerequisites
The Topology Retrieval Rule panel of the VistaLink configuration wizard is open.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 76
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 77
• SAM interfaces
• WAN interfaces:
• MLPPP
• T1 Interface
• PortTerminationChannelInterface
• SonetChannelInterface
• DS0ChannelInstances
Channel the All checkbox, if you want to retrieve DSO channel groups, Port
Interfaces Termination Channel interfaces and Sonet channel interfaces
T1 Interfaces the All checkbox, if you want to retrieve T1 interfaces
Network Queue the All checkbox, if you want to retrieve Network Queue Groups
Groups
2 Click Next.
The Configuration Wizard proceeds to the Directories panel.
Next step
See "Setting the directories and data retention period" on page 78.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 78
Data directory
The data directory contains the statistics and topology files received from the SAM server. This
directory stores the results coming from the latest execution.
Done directory
The done directory contains the three following subdirectories:
• stat stores compressed XML files that contain the results of requests for the statistics data, in
subdirectories sorted by date and time.
• topo stores compressed XML files that contain the results of requests for the topology data, in
subdirectories sorted by date and time.
This done directory is used by InfoVista Support team because it is a backup of requests between
VistaLink and SAM. You must use the FindToFile or LogToFile data retrieval modes to store the
request results. You can decide the retention period for which you want to keep the XML files in
topo and stat using the Topology History (Days) and Statistical History (Days) from the
Directories panel of the VistaLink configuration wizard.
• wizard, stores for debugging purposes, the acquisition rates requested from the SAM server in
Find mode.
For more information about the VistaLink directories, see "Checking directories and files"
on page 31
Prerequisites
The Directories panel of the VistaLink configuration wizard is open.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 79
For example:
2 Click Next.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 80
Next step
See "Setting the filters" on page 81.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 81
Prerequisite
The Filters panel of the VistaLink configuration wizard is open.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 82
2 If you want to apply the filter you defined for customers to routers, in the Customer tab, select
Apply customer filters to Routers.
This option is active only if you selected Include Only for Customers and provided a
list of customers to monitor exclusively.
For example:
3 Click Next.
The Acquisition Rates Information dialog box opens to inform of the successful acquisition
rates retrieval or not.
4 Click OK.
5 If the Acquisition Rates Information dialog box indicated that acquisition rates are missing then
you need to import the VistaViews provided in your VistaLink Installation Directory (see
"Importing VistaView libraries" on page 25.)
6 Click Next.
The Configuration Wizard proceeds to the Statistics Retrieval panel.
Next step
See "Setting the statistics retrieval parameters" on page 83.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 83
Prerequisites
• The Statistics Retrieval panel of the VistaLink configuration wizard is open.
• You have imported the libraries into VistaMart (see "Importing VistaView libraries" on page 25)
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 84
2 To include data flagged with the “suspect” attribute set to true, select the Accept Suspect Data
checkbox.
! At this stage, if a value is higher in the SAM Acquisition column than in the VistaMart
Insertion column for a given Vista and you click Next to move to next panel, a warning
message appears and the corresponding row is highlighted red. The message warns
you that with the chosen settings, VistaLink is actually inserting data into VistaMart
more often than it is acquiring it from the SAM server. You are recommended to set
each insertion rate to be equal to the corresponding acquisition rates before
continuing.
3 To modify an acquisition rate for a given instance type, select any cell on the corresponding row
and click Edit.
The Acquisition Rate Detail Panel opens.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 85
4 Select the appropriate acquisition rate from the VistaMart Insertion drop-down menu.
5 Click OK.
8 Click OK.
The dialog box closes.
9 Repeat steps 6 to 8 to add another auxiliary server, if needed.
10 To delete an auxiliary server, select the server and click Delete, then Yes.
11 Click Next.
The Configuration Wizard proceeds to the Memory panel.
Next step
See "Allocating memory space" on page 86.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 86
• the process which exports the topology from the SAM server
The memory VistaLink requires depends on the topology managed by the SAM Server. The more
instances you intend to monitor, the more you must increase the memory size.
The memory you set here does not take into account the following processes:
• The JMS service used to monitor the device availability and to collect accounting statistics.
Prerequisite
The Memory panel of the VistaLink configuration wizard is open.
2 Click Next.
The Finish panel opens. You can now finalize the configuration.
Next step
See "Finalizing the configuration" on page 87.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Using the Configuration Wizard 87
Prerequisite
The Finish panel is open and prompts you to confirm the entire set of parameters.
Next steps
You can now perform the optional configuration tasks according to your needs:
• "Changing the default display rates for SAM data" on page 88
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Changing the default display rates for SAM data 88
! InfoVista strongly recommends you define display rates at least equal to the acquisition
rates set at SAM server level. By default, the global variables that define the display rates
for each Vista in VistaMart are all set to 15 minutes.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Changing the default display rates for SAM data 89
Prerequisites
• VistaLink is installed (see "Installing VistaLink" on page 28).
• You have imported the VistaView libraries into VistaMart (see "Importing VistaView libraries" on
page 25).
• You have successfully configured VistaLink using the Configuration Wizard (see "Using the
Configuration Wizard" on page 55).
4 On the right panel, click the row that corresponds to the global variable you want to modify.
5 Enter the value according to your needs in the Value field on the bottom-right panel and press
Enter.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Changing the default display rates for SAM data 90
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring discovery 91
Configuring discovery
By default, VistaLink discovers most types of instances. To enable or disable the discovery of given
instance types and instances, see the following sections:
"Enabling discovery of an instance type" on page 91
"Enabling discovery of filtered out instance types" on page 92
"Disabling discovery of an instance type" on page 93
"Disabling discovery of a specific instance type" on page 94
"Configuring instance discovery" on page 94
• OAM Tests
• MPLS LSP’s
• QoS Ports
• ACL Filters
• Physical Ports
• Channel Interfaces
• T1 Interfaces
• MS-ISA Cards
• IOM Cards
• Ethernet Cards
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring discovery 92
• AA Partition
• MS-ISA Card
• IOM Card
• Ethernet Card
To enable the discovery of one or several of these instance types, you need to deactivate the filter
applied to these instance types during SOAP requests to the SAM server. You do so by modifying
the wizardDefinedTopoFilters.xml file manually using the following procedure:
Prerequisites
• VistaLink is installed (see "Installing VistaLink" on page 28).
• You have successfully configured VistaLink using the Configuration Wizard (see "Using the
Configuration Wizard" on page 55).
Make sure to use commas to separate the instance types that you do not want to
discover.
Example To enable AA Partition and AA Group discovery, edit:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring discovery 93
• AA Partition
• MS-ISA Card
• IOM Card
• Ethernet Card
If you want to prevent the VistaLink from discovering a given instance type during the SOAP
requests to the SAM server, perform the appropriate procedures indicated in following table,
depending on the instance type:
• OAM Tests
• MPLS LSP’s
• QoS Ports
• ACL Filters
• Physical Ports
• Channel Interfaces
• T1 Interfaces
other instance types "Disabling discovery of a specific instance
type" on page 94
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring discovery 94
• PortTerminationChannelInterface
• SonetChannelInterface
• DS0ChannelInstances
You can do so using the following procedure by adding the interface type name to the
wizardDefinedTopoFilters.xml file.
Prerequisites
• VistaLink is installed (see "Installing VistaLink" on page 28).
• You have successfully configured VistaLink using the Configuration Wizard (see "Using the
Configuration Wizard" on page 55).
Make sure to use commas to separate the instance types that you do not want to
discover.
3 Save and close the file.
4 Restart the VistaLink service (see "Managing the VistaLink service" on page 102).
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Performing advanced filtering of the topology 95
vista block
The vista block defines the vista to which the filter applies. It occurs only once in the file. The
conditions element may embed several conditions elements.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Performing advanced filtering of the topology 96
conditions block
The conditions block requires the following attribute:
• And
• or
• Or
• not
• Not
• And
• or
• Or
• not
• Not
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Performing advanced filtering of the topology 97
• tag
• name
• tag
• name
• name
fileValue element
Use the fileValue element to filter instances and data based on a CSV file. The fileValue
element may include the following elements:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Performing advanced filtering of the topology 98
Examples
• The following filter enables you to provision only the SAM SAP Queue Ingress instances whose
Customer ID property is CUST1:
• The following filter enables you to provision only the Router instances whose tags are either
equal to 3145836 or to 3145737.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Performing advanced filtering of the topology 99
• The following filter enables you to provision only the SAM SAP instances with property values:
• instanceType equal to SAP
• hasSapQueue different from false
• The following filter specifies that you want to provision only instances which are in the
myFilterFile.csv file based on the value in column 1 (second column).
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Performing advanced filtering of the topology 100
Creating a filter
If you want to provision VistaMart with only a set of instances that conform to set criteria, you need
to create a filter for each concerned instance type and set of instances.
Create a filter
1 In <VistaLink Installation Directory>\sam\config\filters, create an xml file using your
favorite xml editor.
You can name the file as you feel appropriate based on the filter criteria.
2 In the file, create a Filter block.
3 In the Filter block, create a vista element.
4 In the vista element, enter the name of the concerned vista as named in VistaMart.
5 In the Filter block, create a conditions elements with attributes and elements according to
your needs (see "Filter file structure and elements" on page 95).
6 Save and close the file.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring logs 101
Configuring logs
Log files are saved to the VistaLink Installation Directory in the log directory.
The following sections provide configuration tips that apply to VistaLink log files.
Prerequisite
VistaLink is installed (see "Installing VistaLink" on page 28).
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing the VistaLink service 102
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Understanding zones 103
Understanding zones
VistaLink provisions the topology it discovers into VistaMart into a specific repository organized in
zones within a zone set.
Once VistaLink for Alcatel-Lucent 5620 SAM starts provisioning VistaMart, it automatically creates
the zone set and the zones in VistaMart. Following are the default names of the zones:
• SAM_GROUPS
• SAM_DEVICES
• SAM_PERFORMANCE
• SAM_ACCOUNTING
This section describes the zone creation process, the zone naming and how to modify the
threshold that constrains the number of instances that VistaLink can provision into the zones
dedicated to proxies.
"Zone creation process" on page 103
"Multiple proxy zones" on page 105
• customers
Devices with basics:
• Microwave devices
• LAN switches
• routers
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Understanding zones 104
• SonetChannelInterface • Interface
• LAG
Accounting with the following proxies:
• OAM probes • Sub MPLS LSP (MPLS LSP
Ingress)
• SAM SAP queues
• Sub SDP.
• SAM Network queues
All the proxies of a given basic are provisioned into the same zone. The size of the zones
dedicated to proxies is constrained by a configurable threshold (sam.vm.zone.split.threshold)
applied to the number of proxy instances to be provisioned. Once the threshold is crossed,
VistaLinks creates a new Performance type or Accounting type zone, depending on discovered
proxy type, with suffix -2. Each time the threshold is crossed a new zone is created and the suffix
is incremented by 1.
Following is an example of zones with customized names that VistaLink created in the VistaMart
Inventory Manager as a result of topology discovery and update:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Understanding zones 105
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Configuring the sizing of proxy zones 106
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing VistaMart modules 107
Required modules
The following SAM specific modules and all their related indicators are started by default:
Module
• SAM Basic
• SAM Customization
• SAM Distribution
• SAM SAP
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing VistaMart modules 108
Optional modules
To start indicators on volume type data, you need to start the following modules which are not
started by default:
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing VistaMart modules 109
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing VistaMart modules 110
6 Repeat procedure from step 3 for all the modules you want to start.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing VistaMart modules 111
7 Apply rules:
• From the Provisioning menu, select Test & Apply Rules.
• In the right-hand panel, select the zone where you want to apply the rules.
• Click the Apply Rules icon at the top right of the panel.
• Click yes in the Apply Rules dialog box.
• In the VistaMart provisioning window, once the process is successfully completed, click
Close.
8 Exit the VistaMart Inventory Manager.
6 Repeat procedure from step 3 for all the modules you want to stop.
7 Apply rules:
• From the Provisioning menu, select Test & Apply Rules.
• In the right-hand panel, select the zone where you want to apply the rules.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Managing VistaMart modules 112
• Click the Apply Rules icon at the top right of the panel.
• Click yes in the Apply Rules dialog box.
• In the VistaMart provisioning window, once the process is successfully completed, click
Close.
8 Exit the VistaMart Inventory Manager.
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Backing up and restoring the VistaLink configuration 113
Installation and Configuration Guide - Chapter 3 Configuring VistaLink for Alcatel-Lucent 5620 SAM
4 Customizing your
VistaLink for Alcatel-Lucent
5620 SAM
114
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your solution: main steps 115
If... then...
the VistaLink solution model does not provide create the Vista (see the VistaMart User
the Vista that corresponds to your new Guide).
instance type
the appropriate Vista exists but you want to be add the missing properties to the existing
able to retrieve properties not available in the Vista (see the VistaMart User Guide).
Vista
2 Create the topology mapping file for the new instance type (see "Creating a topology mapping
file" on page 142)
3 Define the statistics class for the new instance type (see "Creating a protocol template" on
page 160)
4 If necessary, create indicators (see "Creating an indicator" on page 162).
! Be sure to keep track of instance types you add, as you are solely responsible for managing
customized protocol template xml files.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your solution: main steps 116
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 117
Prerequisites
• You have installed the VistaLink (see "Installing VistaLink for Alcatel-Lucent 5620 SAM" on
page 20).
• You have a good understanding of the structure and content of the topology mapping files (see
"Topology mapping file structure" on page 126 and "Topology mapping file elements and
attributes" on page 127).
• You have analyzed the content of the default topology mapping files available for the various
OAM probes in <VistaLink Installation Directory>\sam\ini\samTopoMappings.
• You have used your Alcatel-Lucent 5620 SAM API to identify the discovery classes and
properties available for the new OAM probe.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 118
For this use case, you can base the new topology mapping file on either one of these
two files. This example, uses OAM_MAC_330.xml.
2 Duplicate the OAM_MAC_330.xml topology mapping file to the <VistaLink Installation
Directory>\sam\config\samTopoMappings folder.
3 Rename the duplicated file appropriately, using syntax instanceType_integer.xml (see
"Topology mapping file name" on page 125).
Example: OAM_CFM_TWO_WAY_SML_335.xml
4 Open the file using your favorite xml editor.
5 Modify elements as follows:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 119
7 Add the following properties elements that define the instance name and the instance tag to the
instanceProperties element:
8 To enable retrieval of the Alcatel-Lucent mepTargetMacAddr attribute value, map this attribute to
either existing VistaMart properties or to properties you have specifically created in VistaMart (to
create properties, see the VistaMart User Guide). You do so by adding simpleAssignment
property elements to the existing properties element.
Example
where VistaMart properties targetMacAddress and Location are already part of the InfoVista
Model.
9 To associate a specific protocol value with the OAM CFM Two Way Slm instance type, add a
fixedValue property element (for example, TwoWay) to the existing properties element.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 120
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 121
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 122
Prerequisites
• You have installed the VistaLink (see "Installing VistaLink for Alcatel-Lucent 5620 SAM" on
page 20).
• You have a good understanding of the structure and content of the topology mapping files (see
"Topology mapping file structure" on page 126 and "Topology mapping file elements and
attributes" on page 127).
• You have analyzed the content of the default interface_140.xml topology mapping files
available in <VistaLink Installation Directory>\sam\ini\samTopoMappings.
• You have used your Alcatel-Lucent 5620 SAM API to identify the discovery classes and
properties available related to optical ports.
• You have created two new properties in VistaMart in the LAN Interface vista (see the VistaMart
User Guide) that correspond to the tmnxDDMTxOutputPower and tmnxDDMRxOpticalPower Alcatel-
Lucent properties. Note their respective WID values. This use case uses the following
correspondences:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customization use cases 123
For this use case you do not need to modify or create any protocol template.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 124
! Be aware that a VistaLink upgrade deletes the topology mapping files stored in the ini
folder but saves those stored in the config folder. If you edit sample discovery files,
InfoVista recommends that you place your customized files in the <VistaLink Installation
Directory>\sam\config\samTopoMappings folder.
This section describes the topology mapping file name, structure and content, as well as how to
create or modify a topology mapping file:
• "Topology mapping file name" on page 125
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 125
• Router_40.xml
The numeric suffix defines the order in which VistaLink will process the files in the discovery
folder.
Example
A router must be processed before its proxies, because logically its cards and interfaces can exist
only after the router has been set up. It also must be discovered before the subnet it belongs to.
In such a case, the respective xml files would appear in the discovery folder in the following order:
• Router_40.xml
• MPLSInterface_50.xml
• Ethernet_Card_80.xml
• Interface_140.xml
By naming your initial files with multiple of 10 integers you will be later able to add new topology
mapping files using intermediate integers.
Example MyNewMicrowave_35.xml
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 126
Example Following is a partially collapsed view of the default Microwave topology mapping file
delivered with the VistaLink for Alcatel-Lucent 5620 SAM.
InfoVista recommends using only one instance block per topology mapping file. The block
elements and how you edit them are described in detail in the following sections.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 127
instanceInfo element
The instanceInfo element specifies the instance to be discovered. It is a mandatory element and
can be used only once in the file. It contains the name of the instance which can be user defined.
Its attributes provide the instanceType parameter value and indicate whether the instance is a
proxy or a basic.
Examples
• <instanceInfo isProxy=”false” statInstanceType=”Microwave”>Microwave</instanceInfo>
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 128
provisioningZone element
The provisioningZone element defines whether or not the instance is to be provisioned into
VistaMart, and in which VistaMart zone it should be provisioned. This element can have only the
following values:
Examples
• <provisioningZone>SAM_PERFORMANCE</provisioningZone>
• <provisioningZone>N/A</provisioningZone>
discoveryClasses block
The discoveryClasses block lists and specifies, in separate discoveryClass elements, all the
topology classes that are required for the instance to be discovered.
At least one discoveryClass element is mandatory in the discoveryClasses block.
In the default templates, the discoveryClasses block can also contain hardCodedDiscoveryClass
element. This element is used when some of the properties cannot be set using the topology
mapping file. In this case, discovery of the classes cannot be directly done using the topology
mapping files and a hard coded class that includes all elements required for the discovery is
defined.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 129
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 130
In this example:
• svt.SdpBinding is the SDP instance main discovery class.
• the correlation with the router is based on the siteName property of the router and the node
name of the instance.
• the svt.SpokeSdpBinding and svt.MeshSdpBinding discovery sub-classes are the only sub-
classes required in the response.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 131
• SDPInstanceDiscoverer is the name of the hard coded discovery class to use when the main
class cannot be directly discovered.
instanceProperties block
The instanceProperties block lists and specifies all the properties that need to be set for the
instance to be discovered. These properties are common to all of the discovery classes.
The instanceProperties block contains at least one properties element. In the default templates, it
can also contain a hardCodedPropertyAssignerClass element. The
hardCodedPropertyAssignerClass element is used when some of the properties cannot be set
using the topology mapping file. In this case, you need to set the properties using hard coded
property assigner classes.
properties element
The properties element is used in the specificProperties element of the discoveryClass
element and in the instanceProperties block. Each properties element can contain one or
several sub-elements.
Not all the following properties sub-elements are required but you have to organize them in the
following order:
1 reference
2 localProperty
3 simpleAssignment
4 booleanMapping
5 fixedValue
6 configuredProperty
7 calculatedProperty
8 conditionalProperty
! The reading of the topology mapping file returns an error if the properties are not defined in
the proper order. Make sure to observe the order.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 132
reference sub-element
The reference sub-element is optional. It defines the name of the class or instance which serves
as a reference to set the value of a property or an attribute.
Each reference sub-element contains at least one of the following sub-element:
• SamClass
• BasicInstance
• ChildClass
className the name of the class, in case the Optional
reference is a class.
instanceType the name of the instance, in case the Optional
reference is an instance.
Example
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 133
localProperty sub-element
The localProperty sub-element is optional. It defines the properties that may be required for
internal usage but do not need to be provisioned to VistaMart.
Each localProperty sub-element may have the following attributes:
Example In this example from the default Microwave topology mapping file, the localProperty
elements are used to:
• assign value Microwave to the instanceType property
• assign the value of the objectFullName attribute to the objectFullName property and populate
the value in the topology cache.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 134
simpleAssignment sub-element
The simpleAssignment sub-element is optional. It is used to set the property value based on the
value of a given attribute of the class.
Each simpleAssignment sub-element may have the following attributes:
Example
In the first simpleAssignment element of the following example, the VistaMart property IP from the
IpNode vista takes the value of the ipAddress attribute of the class.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 135
booleanMapping sub-element
The booleanMapping sub-element is optional. It is used to define a property value based on a the
false/true condition of a given class attribute.
Each booleanMapping sub-element contains at least one of the following sub-element:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 136
Example
The following booleanMapping elements define the values of the Capabilities property from the
Common vista to set depending on the true/false value of a given attribute. For example, in the first
element, if attribute bgpEnabled is true, then the Capabilities property value is set to BGP.
fixedValue sub-element
The fixedValue sub-element is optional. It is used to set the property value based on a hard coded
value.
Each fixedValue sub-element may have the following attributes:
Example
In the following example, fixed values are defined for three different VistaMart properties:
• value Alcatel is set for the Agent Vendor property of the SnmpNode vista
• value SAM is set for the Capabilities property of the Common vista
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 137
• value 161 is set for the port property of the SnmpNode vista
configuredProperty sub-element
The configuredProperty sub-element is optional. It is used to set a VistaMart property value
according to the value set for the corresponding attribute in the SAM-Poller.properties file, in
<VistaLink Installation Directory>\SAM\config.
Each configuredProperty sub-element may have the following attributes:
Example
In the following example, the VistaMart property defined as VL Identifier obtains its value (SAM)
from that assigned to its attribute vlIdentifier in the <VistaLink Installation
Di.rectory>\SAM\config\SAM-Poller.properties file, on line
sam.configuredProperty.vlIdentifier=SAM.
Property VL Identifier is part of the VL Device vista and its WID is
217744A047C811DFA3650019B912D35C.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 138
calculatedProperty sub-element
The calculatedProperty sub-element is optional. It is used to set the property value calculated
using a Java script.
Each calculatedProperty sub-element contains at least one of the following sub-elements:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 139
Example
In the following example, the value of the Interface Speed property from the Interface vista is
calculated from the formula indicated in the javaScript element and provisioned to VistaMart.
conditionalProperty sub-element
The conditionalProperty sub-element is optional. It is used to set the property value based on a
condition.
Each conditionalProperty sub-element contains at least one of the following sub-elements:
• simpleAssignment
• booleanMapping
• fixedValue
• calculatedProperty
Set those elements as described in their
respective sections.
The condition element has the following
attributes:
• attributeValue
• isRegExp
default the default property that is used when Optional Single
the conditions do not apply.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 140
Example
The following conditionalProperty block defines the properties to set in the case the value of
attribute mode is either access, network or hybrid. In these 3 cases, the value of the VistaMart
property Role from the SAM interface vista is set respectively to Access, Network and Hybrid. If
none of these three conditions are met then the mode attribute of the class is used to set the
property value.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 141
vistaList block
The vistaList block is mandatory. It contains the list of vistas to set for the instance.
Each vistaList sub-element contains at least one of the following sub-element:
Example
The following vistaList block from the default Interface topology mapping file indicates that the
SAM interface Name and VL Device vistas need to be set for the Interface instances.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 142
By default no sam10 folder is available under the samTopoMapping directory. In the case of a
SAM 10 server, VistaLink takes into account the mapping files available directly under
samTopoMapping and under the sam9 folder.
If no topology mapping file is available for this instance type you need to create one from an
existing topology mapping file (see "Creating a topology mapping file" on page 142).
Prerequisites
• You have installed the VistaLink (see "Installing VistaLink for Alcatel-Lucent 5620 SAM" on
page 20).
• You have a good understanding of the content of the topology mapping files (see "Topology
mapping file structure" on page 126 and "Topology mapping file elements and attributes" on
page 127).
• You have used your Alcatel-Lucent 5620 SAM API to identify the discovery classes and
properties available for the given instance type.
• You have created the necessary properties and vista, if applicable, in VistaMart (see the
VistaMart User Guide).
In the case of a SAM 10 server, you may create a sam10 folder under <VistaLink
Installation Directory>\sam\config\samTopoMappings where to store your customized
mapping files.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 143
! Be aware that a VistaLink upgrade deletes the topology mapping files stored in the ini
folder but saves those stored in the config folder.
2 Rename the duplicated file appropriately, using syntax instanceType_integer.xml (see
"Topology mapping file name" on page 125).
3 Open the file using your favorite xml editor.
4 Carefully modify the various elements and attributes according to your needs (see "Topology
mapping file elements and attributes" on page 127).
5 Save and close the file.
6 On a Unix platform, relaunch script <VistaLink Installation Directory>/bin/setprivs.sh.
7 Restart VistaLink (see "Managing the VistaLink service" on page 102).
! The structure of the customized mapping file should be same as the original mapping file. It
should contain all the blocks existing in the original mapping file.
You can modify only the content of the properties, specificVista and vistaList blocks.
Only the properties that need to be customized or added should be present in the custom
topology mapping file.
If you need to declare a new topology class then you need to create a new topology mapping
file (see "Creating a topology mapping file" on page 142).
The VistaLink first analyzes the topology mapping files of the <VistaLink Installation
Directory>\sam\ini\samTopoMappings then those available in <VistaLink Installation
Directory>\sam\config\samTopoMapping. If it finds two files with the same name in both folders, it
analyzes the delta between the two files and takes into account the changes (modified or added
properties, added vistas) made in the config folder and merges them with the information that was
not changed in the original files of the ini folder.
To modify a topology mapping file, perform the following procedures, depending on your needs,
then activate the topology mapping file as indicated.
Prerequisites
• You have a good understanding of the content of the topology mapping files (see "Topology
mapping file structure" on page 126).
• Use your Alcatel-Lucent 5620 SAM API to identify the discovery classes and properties
available for the given instance type.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 144
! Be aware that a VistaLink upgrade deletes the topology mapping files stored in the ini
folder but saves those stored in the config folder.
• Open the file using your favorite xml editor and:
• delete all the properties elements within the possibly existing specificProperties and
instanceProperties blocks, except the ones that contain the properties you plan to modify.
• within the properties elements that remain, delete all the properties except those you plan to
modify.
Deleting the properties from the customized topology mapping files does not affect
the discovery of these properties. They still will be discovered as specified in the
topology mapping files stored in the ini folder.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 145
• vistaList element of the specificVistas block, if the property is specific to the given
discovery class
• vistaList block of the file, if the property is common to all discovery classes for the given
instance.
Make sure the vista exists in VistaMart or create it first (see the VistaMart User Guide).
For details and examples on each element and attribute, see "Topology mapping file elements
and attributes" on page 127, and especially the ‘properties element’ section.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Customizing your instance discovery 146
Prerequisites
• VistaLink is installed (see "Installing VistaLink" on page 28).
• You have successfully configured VistaLink using the Configuration Wizard (see "Using the
Configuration Wizard" on page 55).
4 To set this property using the administrativeState attribute, replace the operationalState
attribute value with administrativeState:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 147
! Be aware that a VistaLink upgrade deletes the protocol templates stored in the ini folder but
saves those stored in the config folder. If you edit sample protocol template files, InfoVista
recommends that you place your customized files in the <VistaLink Installation
Directory>\sam\config\protocolTemplates folder.
This section describes the blocks, elements and attributes of a template and how to create or
modify protocol templates:
"Protocol template file name" on page 148
"Protocol template structure" on page 148
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 148
• the connection parameters that determine the SAM Host to which requests are to be made
• the table list which contains information regarding the different Class tables from which
indicators are to be calculated.
For example, the Microwave.xml file provides default connection properties and Class information
for the Microwave device:
where:
• instanceType defines the type of instance the protocol template applies to
• connectionProperty defines the connection properties used to connect to the SAM server
• tableInfoList defines all the Class tables that are referred to in the formulas of the indicators
related to the instance type.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 149
instanceType block
The instanceType block defines the type of instance the protocol template applies to.
It is a mandatory element and can be used only once in the file.
! You need to make sure that the instance type you are using is defined in the topology with
the same instanceType name.
Example
connectionProperty block
The connectionProperty block defines the connection properties used to connect to the SAM
server.
It is a mandatory element and can be used only once in the file. By default it defines the property of
the InfoVista Solution Model to use to identify the VistaLink server in VistaMart. You may need to
modify this property when you customize your topology.
It includes the following elements:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 150
Example
tableInfoList block
The tableInfoList block defines all the statistics class tables that are referred to in the formulas of
the indicators related to the instance type.
It is a mandatory element and can be used only once in the file.
It contains one or several tableInfo elements.
Each tableInfo element defines a particular class and contains specific attributes and elements.
Following are descriptions of the tableInfo element possible attributes:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 151
• simpleStatClass
polledClasses with details the SAM statistic classes Optional Single
that have to be present in the response
to the statistics request.
In case no polled class is defined, then
the main statistics class is entirely
considered in the response. If polled
classes are defined, then only the
selected sub-classes are considered in
the response.
The polledClasses element contains
the statClass element.
evaluationCondition the possible condition required for Optional Single
given statistics to be discovered.
If the condition doesn’t apply, the data
block that corresponds to the statistics
table is discarded.
This element contains the javaScript
element.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 152
• parserClass
• columnInfo
• instanceIdentifier
countColumn the VistaLink statistic counter of a given Optional Single
type.
It is required in case of specific
indicators such as NumberOfPorts.
It contains the following elements:
• difColumn
• calculatedType
logToFileInfo the minimum SAM server version for Mandatory Single
which LogToFile requests can be sent, for classes
in the case LogToFile was selected as requested in
the statistics retrieval mode. LogToFile
For other versions, FindToFile requests mode
are used.
It may contain the following elements:
• minimumSamVersion
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 153
• The following example shows a tableInfo element from the default oams.xml protocol template:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 154
This default template enables to retrieve data from OAM’s in LogToFile mode.
The following logToFileRequestType element is used for OAM protocol templates only and
requires value registerSasLogToFile whenever the VistaLink retrieves data in LogToFile mode.
samStatsClass element
The samStatsClass element defines the SAM statistic class used for the instance type. This class
can vary depending on conditions defined in sub-elements. It is a complex mandatory element that
includes optional and mandatory elements and attributes.
For availability type statistics, the value of the statClass attribute is equal to statClass.
Following are the elements that can be part of the samStatsClass element:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 155
• statClass
Following are the attributes that can be part of the samStatsClass element:
Examples
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 156
Following are the attributes that are part of the polledClasses element:
Example
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 157
Examples
• evaluationCondition element without the logOnError attribute:
• header
attributeName the name of the attribute present in the Mandatory Single
CLI response to be used in the
calculation of the column value.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 158
Example
countColumn attributes
The countColumn element defines the counter of a given type for a given VistaLink statistics
counter.
It is required in case of specific indicators such as NumberOfPorts.
It is a complex optional element that includes mandatory attributes.
Following are the attributes that are part of the countColumn element:
Example
logToFileInfo elements
The logToFileInfo element defines LogToFile specific information.
It is a complex element that includes the following mandatory and optional elements:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 159
Example
Example
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 160
Prerequisites
• You have enabled the discovery of this instance type (see "Enabling the discovery of an
instance" on page 142).
• You have a good understanding of the content of the protocol template files (see "Protocol
template structure" on page 148 and "Protocol template elements and attributes" on page 149).
• You know from which type of table the VistaLink will retrieve data for the given instance type.
• You know what statistic classes are used to retrieve the data for this instance type.
! Be aware that a VistaLink upgrade deletes the protocol template files stored in the ini
folder but saves those stored in the config folder.
2 In <VistaLink Installation Directory>\sam\config\protocolTemplate, rename it
appropriately, based on the new instance type name (see "Protocol template file name" on
page 148).
3 Open the file using your favorite xml editor.
4 Modify the instanceType and the tableInfoList blocks appropriately (see "Protocol template
elements and attributes" on page 149).
5 Save and close the file.
6 If running on Solaris/Linux: relaunch script bin/setprivs.sh.
7 Restart VistaLink (see "Managing the VistaLink service" on page 102).
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Defining the statistics classes 161
Prerequisites
• You have a good understanding of the content of the protocol template files (see "Protocol
template structure" on page 148).
• You know from which type of table the VistaLink will retrieve the data for this instance type.
• You know what statistic classes are used to retrieve the data for this instance type.
! Be aware that a VistaLink upgrade deletes the protocol template files stored in the ini
folder but saves those stored in the config folder.
2 In <VistaLink Installation Directory>\sam\config\protocolTemplate, open the file using
your favorite xml editor.
3 Modify the tableInfoList blocks appropriately (see "Protocol template structure" on page 148).
4 Save and close the file.
5 If running on Solaris/Linux: relaunch script bin/setprivs.sh.
6 Restart VistaLink (see "Managing the VistaLink service" on page 102).
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 162
Creating an indicator
You can create your own indicators to suit your reporting needs, as explained in the following
sections.
You can get data from a specific database and integrate this data into the VistaFoundation for
customized reporting.
You do this by adding your own indicators to a set of existing indicators.
There are two levels of customization. You can:
• create a new data indicator, or
Overview
This section provides basic information to enable you better to understand the different steps
involved in indicator creation.
Principles
You create your own indicators in your own libraries. You create these libraries for the specific
purpose of containing your indicators. Using your own libraries enables you to keep your
customized reporting whenever the out-of-the-box standard and/or ad hoc model(s) are overwritten
when VistaMart is upgraded.
InfoVista strongly recommends that you have a solid understanding of VistaMart principles before
you begin the example workflow.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 163
Rules
Generic rules are available in the SAM Customization module to start your indicator slots, meaning
that you may not need to create a rule if these generic rules meet your needs. Following is the list
of rules predefined for given resources:
Before you start to create an indicator, you should therefore verify that a rule exists for the
indicator you are about to create. If none is available, you need to create your own rule. This is
explained in "Apply the rules" on page 173 at the end of the section "Customizing your solution:
main steps" on page 115.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 164
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 165
This advanced function requires creating a syntactically-correct expression for each resolver you
add.
Creating multi-formula indicators, resolvers and their expressions are explained in detail in the
VistaMart User Guide, section ’Designing a multi-formula Display Indicator’. Before you put
together your own multi-formula indicators, InfoVista strongly recommends that you thoroughly
read this and related sections in the VistaMart User Guide.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 166
InfoVista strongly recommends that you refer to the VistaMart User Guide, section “Working with
Modules and Rules”, for in-depth information about rules.
Ensuring prerequisites
Using existing rules eliminates the need to write your own rules. However, be aware that these
rules are subject to change, and may not be available for all the indicators your want to add.
Before you start, verify that a generic rule exists for the indicator you are about to create. If no rule
exists for your indicator, you must create a rule to start the indicator slot. In this case, refer to the
procedure "Apply the rules" on page 173.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 167
Create a library
1 In the VistaMart Inventory Manager, click the Model tab.
2 Right-click the VistaBridge Libraries node and select New Library.
The New VistaBridge Libraries dialog box appears.
3 Enter a name for the new library (example: MyVistaBridgeLibrary) and an optional description.
4 Click Finish.
Your new library appears in the left- and right-hand panes:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 168
Create an indicator
1 In the VistaMart Inventory Manager, click the Model tab.
2 Under VistaBridge Libraries, expand the library you created for the indicator.
3 Right-click the Indicators node, and select New Indicator.
The New Indicators dialog box appears.
4 Type a name for the new indicator (example: MyVistaBridgeIndicator), then enter at least:
• Vista: select the appropriate vista name (example: Interface)
• Library: select the library to which it belongs (example: MyVistaBridgeLibrary)
• Vendor: select the appropriate vendor (example: Alcatel)
• Capability: select BasePI_Bridge.
• Solution: select SAM.
• User Field: type SAM Customization and press Enter, to start the rules associated with
indicators customized for SAM.
The SAM Customization module automatically associates the rules that provide the
relevant Acquisition and Display Rates to the indicator.
Depending on indicator, you may need to enter other fields, such as Unit. You can
enter the formula at this stage or later.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 169
5 Click Next.
The Resolver creation dialog box appear.
If you are creating a multi-formula indicator, enter the names of all the possible source indicators
(for example, depending on vendor).
6 Click Finish.
Your new indicator appears in the right-hand pane:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 170
Prerequisite
You have already created an indicator without entering its formula.
3 Click your indicator in the right-hand pane, then click the Indicator formula ellipsis button .
The Formula Editor appears.
4 Enter the formula required to get the values you want (see "VistaLink formula Syntax" on
page 174).
For example: delta(SAPQueueIngressStats.lowOctetsOffered).....
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 171
5 Click OK.
The formula appears in your new indicator:
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 172
Prerequisite
You have exported the VistaBridge Library where you created the indicator.
3 Click Add to add the library which contains your indicator. You can add more than one library.
4 Click Start checking to check the validity of the indicator(s).
5 The results appear in the Result pane.
You can save the results by clicking Export result. The file is saved to the bin directory.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Creating an indicator 173
Prerequisites
• You have created your indicators using the SAM Customization module (see "Creating a
VistaLink indicator" on page 168).
• You have verified that the formula syntax of the new indicators is correct.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 174
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 175
Syntax 1: ClassName.CounterName
Syntax 1 based on the ClassName.CounterName structure is the preferred syntax, unless operations
involve several counters of the same Class table.
You have four different ways of using this syntax:
Syntax Description
ClassName.CounterName Basic syntax that applies either with a single value counter
or in the case the parameter considers all values in a
multiple value counter.
ClassName.CounterName[index] Basic syntax that applies in the case the parameter
considers only given values in a multiple value counter.
Use a comma to separate the index values when
addressing several rows in the counter.
For more information on using indexes, see section "For
multi-value counters" on page 178
ClassName.COLUMN[“CounterName”] Syntax to use:
• with a single value counter or in the case the parameter
considers all values in a multiple value counter, and
• when the counter name includes a special character - for
example, dot (’ . ’), which is normally used as a
separator.
With COLUMN[“CounterName”] the formula parser does not
take the special character included in the counter name into
account and finds the actual counter.
ClassName.COLUMN[“CounterName”][ Syntax to use:
index] • in the case the parameter considers only given values in
a multiple value counter, and
• when the counter name includes a special character - for
example, dot (’ . ’), which is normally used as a
separator.
With COLUMN[“CounterName”] the formula parser does not
take the special character included in the counter name into
account and finds the actual counter.
For more information on using indexes, see section "For
multi-value counters" on page 178
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 176
Examples
• class0.counter1
• class0.counter1[3]
• class0.counter1[0,3]
• class1.counter[“A.B”]
• class1.counter[“A.B”][1]
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 177
When performing an operation on two counters, make sure to enclose the counter names in
parentheses, else ClassName applies only to the first element in the string preceding ’from’.
Example (counter1 + counter2 + counter3) from class1
You have four different ways of using this syntax:
Syntax Description
CounterName from ClassName Basic syntax that applies either with a single value counter
or in the case the parameter considers all values in a
multiple value counter.
CounterName[index] from Basic syntax that applies in the case the parameter
ClassName considers only given values in a multiple value counter.
Use a comma to separate the index values when
addressing several rows in the counter.
For more information on using indexes, see section "For
multi-value counters" on page 178
COLUMN[“CounterName”] from Syntax to use:
ClassName • with a single value counter or in the case the parameter
considers all values in a multiple value counter, and
• when the counter name includes a special character - for
example, dot (’ . ’), which is normally used as a
separator.
With COLUMN[“CounterName”] the formula parser does not
take the special character included in the counter name into
account and finds the actual counter.
COLUMN[“CounterName”][index] Syntax to use:
from ClassName • in the case the parameter considers only given values in
a multiple value counter, and
• when the counter name includes a special character - for
example, dot (’ . ’), which is normally used as a
separator.
With COLUMN[“CounterName”] the formula parser does not
take the special character included in the counter name into
account and finds the actual counter.
For more information on using indexes, see section "For
multi-value counters" on page 178
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 178
Examples
• counter1 from class0
• If you want to consider only a given value, specify, in brackets, the index which corresponds to
the value position in the array.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 179
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 180
Operators
The following arithmetic, aggregation and miscellaneous operators are supported.
These operators support either single-value or multiple-value parameters, and/or multiple
parameters.
Operators are not case-sensitive. For example, isnull and isNull are both valid.
Arithmetic operators
Arithmetic operators support multiple and single value parameters. However you can use them in
indicator formulas with multiple value parameters only with aggregation operators listed in the next
section.
Operators Function
+ Addition
Adds the values of two or more expressions.
Example (counter1 + counter2) from Class1
- Subtraction
Subtracts the values of two expressions.
Example (counter1 - counter2) from Class1
/ Division
Divides the values of two expressions.
Example (Counter1 - Counter2) from Class1
* Multiplication
Multiplies the values of two expressions.
Example (Counter1 * Counter2) from Class1
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 181
Aggregation operators
The aggregation operators described in this section all apply to multiple-value parameters. They
can also involve multiple parameters except for count(). Examples used in the operator
descriptions are based on sample class1 and class2 available at the end of the following table.
Operators Functions
sum(expression_1,... Summation
expression_n) or Performs spatial aggregation by adding values for a given timestamp.
sum(expression)
1 Adds the multiple values of a given counter for a given timestamp.
Example Using counter1 from class1 for the 10:00 timestamp with
formula:
sum(counter1) from class1
the returned value would be ‘15’ (10 + 5 = 15).
2 Adds single-value counters for a given timestamp.
Example Using counter1 and counter2 from class2 for the 10:15
timestamp with formula:
sum(counter1,counter2) from class2
the returned value would be ‘25’ (15 + 10 = 25)
mean(expression_1,..., Average
expression_n) or Performs spatial aggregation by averaging multiple values for a given
mean(expression) timestamp.
1 Averages the multiple values of a given counter for a given
timestamp.
Example Using counter1 from class1 for the 10:00 timestamp with
formula:
mean(counter1) from class01
the returned value would be ‘7.5’ ((10 + 5) / 2 = 7.5)
2 Averages a set of single-value counters for a given timestamp.
Example Using counter1 and counter2 from class2 for the 10:15
timestamp with formula:
mean(counter1,counter2) from class2
the returned value would be ‘12.5’ ((15 + 10)/2 = 12.5)
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 182
Operators Functions
min(expression_1,..., Minimum
expression_n) or Performs spatial aggregation by retaining the minimum value for a single
min(expression) timestamp.
1 Returns the smallest value of the multiple values of a given counter
for a given timestamp.
Example Using counter1 from class1 for the 10:00 timestamp with
formula:
min(counter1) from class01
the returned value would be ‘5’
2 Returns the smallest value between single-value counters for a given
timestamp.
Example Using counter1 and counter2 from class2 for the 10:15
timestamp with formula:
min(counter1,counter2) from class2
the returned value would be ‘10’
max(expression_1,..., Maximum
expression_n) or Performs spatial aggregation by retaining the maximum value for a given
max(expression) timestamp.
1 Returns the largest value of the multiple values of a given counter for
a given timestamp.
Example Using counter1 from class1 for the 10:00 timestamp with
formula:
max(counter1) from class01
the returned value would be ‘10’
2 Returns the largest value between single-value counters for a given
timestamp.
Example Using counter1 and counter2 from class2 for the 10:15
timestamp with formula:
max(counter1,counter2) from class2
the returned value would be ‘15’
count(expression) Returns the number of values available in a multiple-value counter for a
given timestamp.
Example Using counter2 from class1 for the 10:00 timestamp with
formula:
count(counter2) from class1
the returned value would be ‘2’
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 183
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 184
Miscellaneous operators
The operators described in this section handle only one single-value parameter, except for
isNull() which uses two single-value parameters.
Examples used in the operator descriptions are based on sample class2 available at the end of
the following table.
Operator Function
delta(expression) Computes the delta by subtracting the previous value from the
current value.
Example Using counter1 from class2 for the 10:15 timestamp
with formula:
delta(counter1) from class2
the returned value would be ‘5’ (15 - 10 = 5).
deltaBySec(expression) Divides the difference between counter values by the number of
seconds between the respective timestamps.
This operator is generally applied to bandwidth indicator
measurements and gives a useful picture of the difference in data
volume between given points in time.
Example Using counter1 from class2 for the 10:15 timestamp
with formula:
deltaBySec(counter1) from class2
the resulting value would be 5 / 900 = 0.0055, where
900 = 15 minutes is the timestamp difference in
seconds between 10:00 and 10:15, and 5 is the delta
between the counter1 values between those two
timestamps.
isNull(expression1, Removes an undefined value from a expression for a given
expression2) timestamp and replaces it with another to avoid an undefined or
invalid result.
This operator is typically used with a mean or division operator if
the expression1 evaluation is in error. In this case isNull provides
a replacement value to the undefined value with expression2.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 185
Operator Function
displayRate() Returns the display rate in seconds of the slot whose value is
inserted into VistaMart for a given timestamp. This operator does
not take any parameter.
Example Dividing the sum of counter1 and counter2 from class2
at 10:15 for a 15-minute display rate (900 seconds) with
formula:
(counter1 + counter2)/displayRate()
would return ‘0.03’ (25/900)
property(‘property_name’) Retrieves a property value for a given timestamp.
Example property(‘Interface Speed’) would return the speed
measured on the interface at the given timestamp.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM VistaLink formula Syntax 186
Examples
This section provides various indicator examples using actual Alcatel-Lucent 5620 SAM counters
and classes:
• Microwave_Availability.availability or availability from Microwave_Availability
where Microwave_Availability is the Class table where the indicator is found and
availability is the counter in the table that returns the required value.
• Indicator Alcatel - sam - Submitted Traffic (bps) uses formula:
QosPortQueueStats.qoSQueueStatsBytesDropped * 8 +
QosPortQueueStats.qoSQueueStatsBytesSent * 8
but can also use formula:
(qoSQueueStatsBytesDropped * 8 + qoSQueueStatsBytesSent * 8) from QosPortQueueStats
• Indicator Alcatel - sam - Interface Error IN (%) uses formula:
100 * delta(InterfaceStats.receivedBadPackets)/
(delta(InterfaceStats.receivedBadPackets) +
delta(InterfaceStats.receivedUnicastPackets)
+delta(InterfaceAdditionalStats.receivedBroadcastPackets +
InterfaceAdditionalStats.receivedMulticastPackets)+delta(InterfaceStats.receivedPacke
tsDiscarded))
• delta(SAPQueueIngressStats.outOfProfileOctetsForwarded) returns the difference between
the number of ingress forwarded octets, out of profile, on the SAP queue, between two points in
time.
• deltaBySec(SAPQueueIngressStats.inProfileOctetsForwarded) returns the difference between
the number of ingress forwarded octets, in profile, on the SAP queue, between two points in time
over the number of seconds elapsed between the two measurements.
• Using formula:
100 * 8 * isNull(deltaBySec( SAPQueueIngressStats.inProfileOctetsForwarded) /
property('Used Cir'), 0),
indicator Alcatel - sam - QueueIngLoadIN_CIR returns 0 when the
deltaBySec(SAPQueueIngressStats.inProfileOctetsForwarded) / property('Used Cir') value
is invalid. This happens when value property('Used Cir') is not defined.
Installation and Configuration Guide - Chapter 4 Customizing your VistaLink for Alcatel-Lucent 5620 SAM
5 Troubleshooting VistaLink
This chapter indicates how to generate a support package and provides basic procedures for
troubleshooting your VistaLink for Alcatel-Lucent 5620 SAM.
187
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Generating a support package 188
InfoVista strongly recommends to generate your VistaLink support package from the
VistaCockpit Management Console (see section ‘Working with VistaCockpit’, ‘Sending
information to InfoVista Support’ in the VistaCockpit User Guide).
If VistaCockpit or its agent is not available, you can use the following procedures from the
VistaLink platform:
Ensure your command arguments are between quotes when the directory names contain
spaces.
! Make sure to revert the setting to the default value when using the VistaLink in regular
production mode in order to protect your topology data from accidental overwriting.
Firewall issue
5 In the TimestampOfReference column, set the time from which you want to replay the data in
microseconds.
Make sure to set a value within the retention time period because the SAM Server
does not keep statistics beyond the retention time.
6 Save and close the file.
7 Restart the VistaLink service.
8 After a while, check if the missing data is now present in the VistaMart Inventory Manager.
Use the VistaLink Configuration Wizard to set and check the connection from the SAM
Connection panel.
Use the VistaLink Configuration Wizard to set and check the connection from the SAM
Connection panel.
Provided that a VistaCockpit agent is available on the VistaLink platform, you can start, stop and
monitor VistaLink from the VistaCockpit Management Console.
This chapter describes how you can manage your VistaLink for Alcatel-Lucent 5620 SAM from
VistaCockpit.
195
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Starting and stopping VistaLink from VistaCockpit 196
Prerequisite
A VistaCockpit Management Console session is started.
See section ‘Working with VistaCockpit’, ‘Executing actions remotely’ in the VistaCockpit User
Guide for the detailed procedures.
The name and tag (unique identifier) of each monitored instance are based upon the standard
Alcatel-Lucent 5620 SAM attributes. This appendix provides the necessary information to interpret
the codification.
198
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM SAM attribute definitions 199
This appendix provides the comprehensive list of Alcatel-Lucent classes and MIB variables
supported by VistaLink for Alcatel-Lucent 5620 SAM.
209
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Alcatel-Lucent classes supported by VistaLink 210
• lag.PortTermination
MPLS Interface mpls.Interface mpls.MplsInterfaceStatsLogRecord
MPLS LSP Mpls.lsp Mpls.LspStatsLogRecord
OAM Layer 2 ethernetoam.CfmOneWayD ethernetoam.CfmOneWayDelayTestResult
elayTest
ethernetoam.CfmTwoWayDelayTestResult
ethernetoam.MaintAssociati
on
mpls.LspPing Mpls.lspPingResult
Service.MacPing Service.MacPingResult
Service.MefMacPing Service.MefMacPingResult
Supported equipment
The following classes of statistics, when associated with both rtr.VirtualRouter and
netw.NetworkElement classes of topology,
• equipment.SystemCpuStatsLogRecord
• equipment.SystemMemoryStatsLogRecord
• equipment.AllocatedMemoryStatsLogRecord
• equipment.AvailableMemoryStatsLogRecord
all address the following Alcatel-Lucent equipment:
• Alcatel-Lucent OmniSwitches (all OS6xxxx and OS9xxxx versions)
Supported MIB’s
This section lists the MIB’s you must activate depending on the indicators you need:
"MIB’s to activate when using the default solution" on page 214
"MIB’s to activate when customizing your statistics retrieval" on page 217
"Which MIB for which indicators" on page 220
Routers
MIB: TIMETRA-SYSTEM-MIB.sgiCpuUsage
MIB: TIMETRA-SYSTEM-MIB.sgiMemoryUsed
MIB: TIMETRA-VRTR-MIB.vRtrStatTable
LAN/WAN Interfaces
MIB: IF-MIB.ifXTable
MPLS interfaces
MIB: TIMETRA-MPLS-MIB.vRtrMplsIfStatTable
MPLS LSPs
MIB: TIMETRA-MPLS-MIB.vRtrMplsLspStatTable
QoSPort (OmniSwitch)
MIB: ALCATEL-IND1-QOS-MIB.alaQoSQueueStatsTable
Service
MIB: TIMETRA-SERV-MIBSapIngQosQueueStatsEntry
SAM SDP
MIB: TIMETRA-SERV-MIB.sdpBindBaseStatsEntry
OAM
All following indicators are available through the TIMETRA-OAM-TEST-
MIB.tmnxOamPingResultsTable MIB. They are listed according to the selected statistics package
and class, and used attributes.
mpls.LspPingResult
vprn.VprnPingResult
service.MacPingResult
svt.VccvPingResult
icmp.IcmpPingResult
mpls.LspPingResult
service.SitePingResult
service.CpePingResult
svt.TunnelPingResult
ethernetoam.CfmOneWayDelayTestResult
ethernetoam.CfmTwoWayDelayTestResult
Index
VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
A VistaPortal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
accounting configuration . . . . . . . . . . . . . . . . . . . . . . . . creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
acquisition rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17, 83 indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Alcatel-Lucent 5620 SAM . . . . . . . . . . . . . . . . . . . . . . . customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
configuration requirements . . . . . . . . . . . . . . . . . . . 22 filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . customized indicators . . . . . . . . . . . . . . . . . . . . . . . . . .
definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 creating a rule for . . . . . . . . . . . . . . . . . . . . . . . . . 173
auxiliary server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing a rule for . . . . . . . . . . . . . . . . . . . . . . . . 170
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 customizing solution . . . . . . . . . . . . . . . . . . . . . . . . . . .
main steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
B
D
backing up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . 47 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
backing up configuration . . . . . . . . . . . . . . . . . . . . . . . 113 missing, replaying . . . . . . . . . . . . . . . . . . . . . . . . . 191
missing, troubleshooting . . . . . . . . . . . . . . . . . . . . 190
data acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
C data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210, 212 data indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 data lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
classes,statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . data maximum history . . . . . . . . . . . . . . . . . . . . . . . . . . 17
defining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 data retrieval mode . . . . . . . . . . . . . . . . . . . . . . . . . . . .
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
backing up and restoring. . . . . . . . . . . . . . . . . . . . 113 data visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . setting up in VistaMart. . . . . . . . . . . . . . . . . . . . . . . 27
backing up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 VistaLink installation . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuration wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
acquisition rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 topology mapping filename . . . . . . . . . . . . . . . . . . 125
filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 display indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
instance selection . . . . . . . . . . . . . . . . . . . . . . . . . . 75 display rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
memory space . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 changing default value for SAM data . . . . . . . . . . . 88
retrieval mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
SAM FTP parameters . . . . . . . . . . . . . . . . . . . . . . . 67 E
SAM host parameters . . . . . . . . . . . . . . . . . . . . . . . 64
SAM SSH parameters. . . . . . . . . . . . . . . . . . . . . . . 69 enabling instance discovery . . . . . . . . . . . . . . . . . . . . . 142
starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 event message formats . . . . . . . . . . . . . . . . . . . . . . . . .
VistaMart parameters . . . . . . . . . . . . . . . . . . . . . . . 58 importing into VistaMart . . . . . . . . . . . . . . . . . . . . . 26
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
retrieval mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Index
234
vista. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
F
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
J
filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMS Client connection . . . . . . . . . . . . . . . . . . . . . . . . .
user data in reports . . . . . . . . . . . . . . . . . . . . . . . . . 40 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Find mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 L
description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 LAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
FindToFile mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 importing into VistaMart . . . . . . . . . . . . . . . . . . . . . 25
description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Local mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
formula syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
verifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 LogToFile mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
H LSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
history parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
M
I Managing VistaMart modules. . . . . . . . . . . . . . . . . . . . 107
memory space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
event message formats. . . . . . . . . . . . . . . . . . . . . . 26 requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
page packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
VistaPortal users and groups . . . . . . . . . . . . . . . . . 37 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
indicator formula syntax . . . . . . . . . . . . . . . . . . . . . . . . default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
verifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 managing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . optional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
related modules . . . . . . . . . . . . . . . . . . . . . . . . . . 108 starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 stopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Modules, optional . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . related indicators. . . . . . . . . . . . . . . . . . . . . . . . . . 108
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 MPLS interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
data vs display . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 MPLS LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
installation directories. . . . . . . . . . . . . . . . . . . . . . . . . . . 31
installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . .
SAM server requirements . . . . . . . . . . . . . . . . . . . . 22 N
installing VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 O
instance discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
OmniSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
instance selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
instance type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Index
235
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Index
236
upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
U VistaLink architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
uninstalling VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 VistaLink data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VistaLink indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . .
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Unix users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . 24 VistaLink service . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . managing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . 44 VistaMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
launching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
tagging and naming conventions . . . . . . . . . . . . . . 45 VistaMart database . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VistaCockpit workflows . . . . . . . . . . . . . . . . . . . . . . 45 creating connection . . . . . . . . . . . . . . . . . . . . . . . . . 33
VistaMart zones . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 VistaMart zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
upgrade wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 VistaPortal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
upgrading VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . creating connection to database . . . . . . . . . . . . . . . 33
SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 deploying VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . 32
user data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VistaPortal page packages . . . . . . . . . . . . . . . . . . . . . .
filtering in reports . . . . . . . . . . . . . . . . . . . . . . . . . . 40 importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VistaPortal users . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
creating on VistaPortal . . . . . . . . . . . . . . . . . . . . . . 39 importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
importing into VistaPortal . . . . . . . . . . . . . . . . . . . . 37 VistaViews libraries . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 importing into VistaMart . . . . . . . . . . . . . . . . . . . . . 25
Volume indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
related modules. . . . . . . . . . . . . . . . . . . . . . . . . . . 108
V starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . stopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
LAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
MPLS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 W
MPLS LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 WAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
QoSPort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
SAM SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
WAN interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
X,Y,Z
VistaBridge library . . . . . . . . . . . . . . . . . . . . . . . . . . . . zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 configuring proxy zone size. . . . . . . . . . . . . . . . . . 103
VistaCockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . proxies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
displaying status from . . . . . . . . . . . . . . . . . . . . . . 197
starting or stopping VistaLink from . . . . . . . . . . . . 196
VistaCockpit workflows . . . . . . . . . . . . . . . . . . . . . . . . .
upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
VistaFoundation kit . . . . . . . . . . . . . . . . . . . . . . . . . . . .
requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
VistaLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
backing up and restoring configuration . . . . . . . . . 113
deploying on VistaPortal . . . . . . . . . . . . . . . . . . . . . 32
managing service . . . . . . . . . . . . . . . . . . . . . . . . . 102
uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
VistaLink® 4.0 for Alcatel-Lucent 5620 SAM Installation and Configuration Guide Index