InfoVista Server 3.2 SP2 Installation Guide

InfoVista® Server3.2 SP2

Installation Guide

2

InfoVista Server 3.2 SP2 Installation Guide

Part Number: 10_302_002_32_SP2

Copyright 1996-2006 InfoVista S.A.All rights reserved.InfoVista® and VistaView® are registered trademarks of InfoVista S.A. in the United States and/or other countries.

The information contained in this document is the property of InfoVista S.A. No part of this publication may be reproduced in any form (including photocopying or electronic storage on any medium) or by any means or used to make any derivative work (such as translation, transformation or adaptation) without the express written permission of InfoVista S.A.

The information contained in this document is subject to change without notice and does not carry any contractual obligation for InfoVista. InfoVista reserves the right to make changes to any products or services described in this document at any time without notice. InfoVista shall not be held responsible for the direct or indirect consequences of the use of the information contained in this document.

Brand and product names mentioned in this publication may be registered trademarks or trademarks of their respective holders.

InfoVista Server 3.2 SP2 Installation Guide Contents

Contents

1 Installation (Windows)InfoVista product details and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Performing a first-time installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing InfoVista Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Installing multiple IV Servers on a single machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Tuning the ObjectStore server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Starting InfoVista Servers and clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Starting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Starting the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Moving to InfoVista Server version 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Important recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Uninstalling InfoVista. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2 Installation (Solaris)Product details and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Performing a first-time installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Tuning the file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Creating Solaris users and groups for InfoVista products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Preparing the installation menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Installing multiple IV Servers on one machine (Solaris) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Tuning the ObjectStore server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Starting the InfoVista Server and client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Starting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Starting an InfoVista client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Upgrading to InfoVista Server version 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Important recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Upgrading to Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Uninstalling InfoVista. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3 Installation (Linux)Product details and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Performing a first-time installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Tuning the file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Preparing the installation menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installing multiple IV Servers on one machine (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Tuning the ObjectStore server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Starting the InfoVista Server and client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4

InfoVista Server 3.2 SP2 Installation Guide Contents

Starting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Starting an InfoVista client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Moving to InfoVista Server version 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Important recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Uninstalling InfoVista. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A Getting and setting a license keyLicense keys - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Using license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Installing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Installing the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Installing a VistaView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Requesting license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Entering a new license key (ivserver) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Entering a new VistaView license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

B Compatibility MatrixConnecting to 3.2 SP2 from former client versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

C General SettingsCache settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Address space settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5

1 Installation (Windows)

The InfoVista® Server and client work with systems running Windows 2000 SP4 and Windows 2003 SP1.

See:"InfoVista product details and prerequisites" on page 6"Performing a first-time installation" on page 8"Starting InfoVista Servers and clients" on page 14"Moving to InfoVista Server version 3.2" on page 16

InfoVista Server 3.2 SP2 InfoVista product details and prerequisites 6

Installation Guide - Chapter 1 Installation (Windows)

InfoVista product details and prerequisites

The InfoVista installation package contains InfoVista software (Server and Client).

SERVER SOFTWARE InfoVista Server software is protected by a license key. This determines the period of time you can access the server.> For an evaluation or demonstration period, use the EVAL key which gives you

access to the server for a period of 30 days starting from your first connection to the server.

> For an extended evaluation or an unlimited period, you need a license key provided by InfoVista. See "Getting and setting a license key" on page 50.

SOFTWARE REQUIREMENTS You can install the InfoVista Server (IVServer) and client (IVReport and IVCmd) on Windows 2000 SP4 and Windows 2003 SP1.

HARDWARE REQUIREMENTS Memory, processor and disk requirements can vary according to the way you use InfoVista software, notably in terms of database sizes.

However, as a general rule, the following are the minimum requirements:

Refer to Appendix C of this guide for more details regarding the memory cache settings. The InfoVista client applications (IVReport and IVCmd) used to consult objects and data managed by InfoVista Servers. Their memory requirements are low.You can connect to InfoVista Servers on Solaris or Linux from a Windows machine and vice versa.

4 GBYTES RAM TUNING On a Windows 2000 Advanced Server or Datacenter server version, it is possible to activate the 4 GBytes RAM Tuning feature. This feature lets an application requests for 3 GB of address space instead of the standard 2GBytes. The benefits are an increase in performance as it reduces the need to swap memory to the page file but an increase in the available space requested by InfoVista.To activate this feature, modify the file boot.ini by appending the switch /3GBytes to the line that corresponds to your operating system and then reboot the computer.

NOTE If you use an evaluation key, you cannot connect to the InfoVista Server after the evaluation period. However, any collected data is not lost and new data continues to be collected. You can access it again after entering a valid server license key.

NOTE Always install IV Server on a dedicated machine.

Memory 2 GB

Processor 900 MHz

Software disk space Double the RAM

Database disk space Dependent on number of devices polled (6 GB min. configuration)

NOTE Setup does not allow installation on non-supported operating systems.

InfoVista Server 3.2 SP2 InfoVista product details and prerequisites 7


CLIENT/SERVER COMPATIBILITY For a complete matrix of client/server compatibility, see Appendix B.

PERL INSTALLATION InfoVista 3.2 supports Perl 5.6.1. This package is provided on the CD-ROM.

PRE-INSTALLATION Before installing, and for optimal performance on a Windows server, it is better to optimize your computer for applications and not for file sharing.

VISTACOCKPIT 2.2 MONITORING InfoVista Server 3.2 is compliant with VistaCockpit 2.2.If you are ujsing VistaCockpit 2.2 for monitoring your InfoVista environment, it is mandatory that you first upgrade the Cockpit agent 2.2 to guarantee the compatibility between the Cockpit Server and its agent installed on your InfoVista Server.

InfoVista Server 3.2 SP2 Performing a first-time installation 8


Performing a first-time installation

A first-time installation includes the following:> installation of the InfoVista software,> import of pre-loaded InfoVista libraries (InfoVista Core and InfoVista Tuning) into

the InfoVista Server database,> installation of the Perl Integration Toolkit (SDK).You can then manually install any additional VistaView® you require from separate media, using the graphic interface, IVReport (see "Troubleshooting" on page 15).

Installing InfoVista Server

Start first-time installation

1 Insert the InfoVista CD into your CD-ROM drive. The installation procedure starts automatically. Follow the dialog boxes displayed on screen.

2 To restart the procedure (if the CD is already in the CD-ROM drive):• EITHER: From the Task bar, select Run and enter D:\win32\setup (this

assumes the CD is in drive D:). Press Enter• OR: In the Windows Explorer: double-click the Setup.exe program in the CD-

ROM directory \win32.

USER INFORMATION DIALOG BOX The installation prompts you to enter this information:.

SELECTING COMPONENTS TO INSTALL The Select Components window allows you to specify which software components are installed.To add a component, check the box to the left of its name.By default, all components are selected. You can also specify a different destination disk or directory in this window.> The Server Components and Client Components software packages are both

selected for installation by default. To install only one or the other, uncheck the box to the left of the item you do not wish to install.

> The Online Documentation component copies to disk the InfoVista Server documentation in PDF and HTML formats. The files can be opened (respectively with Acrobat Reader and a Web browser) in IVreport using the Help/Contents option or alternatively Start/Programs/InfoVista/Documentation.

Name Any string of characters.

Company Any string of characters.

License key If you have a license key, enter it here.If not, leave the evaluation key EVAL, which allows you to use the software for 30 days. Then apply to InfoVista for a new key. See "Getting and setting a license key" on page 50.



> The Perl Integration Toolkit component installs a Perl scripting-language extension, which allows you to include InfoVista commands in Perl scripts.

SETTING INFOVISTA SERVER INSTANCE NAME Set the name of the InfoVista Server instance to install (20 characters maximum). By default, the first server instance you install is called “iv1”.This name is used by the Service Manager and allows you to identify a given server instance when multiple servers are installed.

SETTING INFOVISTA SERVER DIRECTORIES You can modify the Manager and Collector database names and paths. Database names are based on the server instance name defined in the previous step (“manager_iv1.db” and “collector_iv1.db” by default).You can also modify the name and path of the log directory (by default: <installdir>\log).The default installation directory is C:\Program Files\InfoVista\Essentials. In this document, the installation directory is referred to as <installdir>.InfoVista software modules are installed in the following directories, by default:> InfoVista Manager: contains the manager.db file, responsible for updating the

InfoVista Information System model. Default: <installdir>\data

> InfoVista Collector: contains the collector.db file, which stores pollled data. Default: <installdir>\data

INFOVISTA LOG FILES InfoVista log files are installed in this directory. Default: <installdir>\log

To change the location of the Manager/Collector database files or the log directory, modify the paths displayed in the Server directories window. Note: Upgrades of existing installations do not propose a change in the log directory.

NOTE Upgrades of existing installations do not allow database directory changes.



SETTING INFOVISTA SERVER INSTANCE ENDPOINTS For each InfoVista Server endpoint, you can set a port number. If you leave the default (“Automatic”), the system randomly chooses an appropriate endpoint.

> Manager Endpoint (Port): the IP port number used to access the Manager.> Collector Endpoint (Port): the IP port number used to access the Collector.> Browser Endpoint (Port): the IP port number used to access the Browser.

OBJECTSTORE SETTINGS > Select Typical to proceed with a standard ObjectStore installation.> Select Custom to modify the location of the ObjectStore Transaction log file.

OBJECTSTORE TRANSACTION LOG FILE All ObjectStore transactions are recorded in a log file which is, by default, stored in the same location as the collector and manager databases:<installdir>\data\ossvrtxn.log

VISTACOCKPIT INSTALLATION Each InfoVista Server can be fully integrated with a VistaCockpit agent. VistaCockpit provides access to server status (logs, signals etc.) from a centralized console.The VistaCockpit Management Agent installation includes the installation of the Recovery agent. For more details on VistaCockpit, consult user documentation. To install an InfoVista VistaCockpit Management Agent, you must ensure an InfoVista VistaCockpit Management Server is accessible on the network.Enter the hostname and port number of the machine where the InfoVista VistaCockpit Management Server is installed. (Setup asks you to confirm these parameters).

SELECT PROGRAM FOLDER The installer adds the name InfoVista to the Program Folders/Start Menu. You can modify this name or select another one from the list of existing Folders.The installer does not copy the files to disk at this point.

FINISHING THE INSTALLATION Click Finish to complete the InfoVista installation. If you have made changes to certain system parameters, the Setup asks if you wish to reboot. It is recommended to reboot for changes to be taken into account. If you encounter difficulties, refer to te section "Troubleshooting" on page 15.

NOTE If you use a multiple IV Server instance configuration, it is no longer mandatory to specify the endpoints, except if you manage your servers with VistaCockpit 1.1.

NOTE If there is a firewall between the InfoVista client-server systems, it is necessary to use a fixed port number. Consult your firewall administrator to determine an available port number and enter it here.

NOTE With InfoVista Server 3.2, you can connect to a server with a connection string using the instance name in the case of a multi-server installation. See the InfoVista Server Administraton Guide, ‘Communicating with the server’ for additional information.



Installing multiple IV Servers on a single machineYou can install more than one server on a single machine providing the machine has multiple processors. Database sizes become more manageable and backup times are reduced thus improving performance.To install multiple InfoVista Servers on a single machine, it must be equipped at least with 2 processors and 4 GB of RAM per server. The following table summarizes the necessary hardware as a function of the number of server instances you want to install.

See the procedure to add an instance of an IV Server in the InfoVista Server Administration Guide.

Number of servers RAM required Number of processors

2 4 GB 2

3 6 GB 3

4 8 GB 4

etc. etc. etc.



Tuning the ObjectStore serverIf you plan to run several InfoVista Instances (i.e. two or more), you must change the following ObjectStore parameters:> ‘Max AIO Threads’ (default=3) set to match the number of database files that

ObjectStore manages (i.e. 2 x the number of servers)> ‘N Message Buffers’ (default=4) set to match the number of ObjectStore clients

(i.e. 3 x the number of servers).

PARAMETER DEFINITION You define these parameters in the registry, under ‘HKEY_LOCAL_MACHINE\SOFTWARE\Object Design Inc.\ObjectStore 6.0\Server’.Using the registry editor, add “REG_SZ” values to include the new parameter values.Once you have made the changes, you must restart IVServer and ObjectStore to take the modifications into account.See "Starting the server" on page 14 and "Starting the client" on page 14.

CHECKING THE DATABASE SIZE EVOLUTION It is highly recommended to check the evolution of the database on a regular basis. Refer to the InfoVista Server 3.2 Administration Guide, Database Size Management, for more details.



Installation directoriesAfter installation or upgrade, the following directories are created or upgraded in the installation directory (\InfoVista\Essentials):

Directory Contains...

bin InfoVista binary executables.

data ObjectStore databases.

doc Contains online documentation..

etc Resources used by the ObjectStore executables.

lib Resources used by the executables.

log InfoVista log files.

mibs MIB files

migration Libraries and executables needed to migrate a database from version 2.3.

perldist Perl software package

sdk Programming extensions for Perl and C. HTML documentation is included for the Perl API.

vistacockpit Directory reserved for VistaCockpit 2.0 (not yet released)

registry Product information used by the hotfix installer.

VViews The two automatically installed VistaView XML files (Core and Tuning).

InfoVista Server 3.2 SP2 Starting InfoVista Servers and clients 14


Starting InfoVista Servers and clients

After installing InfoVista, check that the server and client function correctly.

Starting the serverThe InfoVista Server is started automatically after installation (and at each system reboot). However, you may need to stop and start the server manually. The server requires the following services:> InfoVista Browser R3.2 iv1> InfoVista Collector R3.2 iv1> InfoVista Manager R3.2 iv1> InfoVista Port Mapper R3.2> ObjectStore Cache Manager R6.3> ObjectStore Server R6.3

Start and stop the services as follows

1 Select Start/Control Panel/Administrative Tools/Services.2 Select each service in turn and click either the Start or Stop.

Starting the clientTo start the InfoVista client, select Start/Programs/InfoVista/IVreport from the Task bar.By default, the connection parameters are:

Server Name Name of the system running the InfoVista Server. If the server is the local system (the same as the client), leave this parameter blank.

User name administrator

Password Change this password as soon as possible after startup.

NOTE You can connect to a server with a connection string using the instance name. See the InfoVista Server Administraton Guide, ‘Communicating with the server’ for additional information.

NOTE During a client connection attempt, the server license key is checked against the all known MAC addresses on a NIC (Network Interface Card).

InfoVista Server 3.2 SP2 Starting InfoVista Servers and clients 15


TroubleshootingIn the event IV Server does not operate properly, check the functions listed below.

WINDOWS SERVICES The installation program sets the following Windows services to Automatic:> InfoVista Browser R3.2 iv1> InfoVista Collector R3.2 iv1> InfoVista Manager R3.2 iv1> InfoVista Port Mapper R3.2> ObjectStore Cache Manager R6.3> ObjectStore Server R6.3> InfoVista VistaCockpit Management Agent (if you chose to install the agent).These services are all started automatically at system startup. After installation, if the services are not running, start them manually.If you experience server problems, check the status of these services. If any of these services have been stopped, you should restart them.

Restart services

1 Select Start/Control Panel/Administrative Tools/Services2 Click the start button for each of the services you wish to restart.

WINDOWS EVENT VIEWER The Windows Event Viewer can be used to obtain more detailed incident information.

Access the Event Viewer> Start/Control Panel/Administrative Tools/Event Viewer

InfoVista Server 3.2 SP2 Moving to InfoVista Server version 3.2 16


Moving to InfoVista Server version 3.2

> When going from InfoVista Server 3.x to 3.2, there is no need for a migration of data. This is an automatic upgrade that modifies the database schema, attributes, and model. It does not impact the data.

> When going from InfoVista Server 2.3 to InfoVista Server 3.2, the user must perform manually a database migration. The objective is to recreate a new database that is compatible with version 3.2 while conserving your data.

> See the InfoVista Server Administraton Guide for information about database migration.

Important recommendations> It is strongly recommended to make a backup of your databases before starting

the installation procedure. Refer to the "ObjectStore Management Guide" for details.

> As the trap format has changed and more precisely the information provided (manager and browser endpoints), it is mandatory to upload the new InfoVista Trap MIB in your trap receiver.

> Following the upgrade, MIB variables corresponding to the old version of the InfoVista-Statistics MIB are set to deprecated. They will not return any values. The old version of InfoVista Tuning VistaView is not migrated and will not be available in the new manager.

Uninstalling InfoVistaBefore uninstalling InfoVista, close IVReport if it is running.

Uninstall InfoVista

1 Select Start/Control Panel/Change/Remove Programs.2 Select InfoVista 3.x from the programs listed in the Install/Uninstall tab page and

click Change/Remove.3 If you do not intend to reinstall InfoVista, manually delete the installation directory

<installdir> and any files remaining in it.

17

2 Installation (Solaris)

InfoVista Server and client work with systems running under Solaris 9 and 10.

See:"Product details and prerequisites" on page 18"Performing a first-time installation" on page 21"Starting the InfoVista Server and client" on page 30"Upgrading to InfoVista Server version 3.2" on page 32"Uninstalling InfoVista" on page 34

InfoVista Server 3.2 SP2 Product details and prerequisites 18

Installation Guide - Chapter 2 Installation (Solaris)

Product details and prerequisites


INFOVISTA SERVER SOFTWARE PACKAGE The InfoVista Server software requires a license key. This determines the period of time you can access the server.> For an evaluation or demonstration period, use the key EVAL which gives server

access for a period of 30 days starting from your first connection.> For an extended evaluation or an unlimited period, you need a license key

provided by InfoVista. See "Getting and setting a license key" on page 50”.

SOFTWARE REQUIREMENTS You install the InfoVista Server and client on systems running under Solaris 9 and 10.

We recommend you run the InfoVista client under the CDE (Common Desktop Environment) visual presentation rather than OpenWindow.In addition, ensure that the SUNWi1of fonts package is installed on your machine. If not, some system fonts can be illegible on certain reports. See the Release notes for instructionsto install this package.On Solaris, if the cdrom is mounted with a mount option other than UDFS, the InfoVista Server installation cannot work. In this case, change the option to UDFS:>mount -F udfs -o nosuid,ro /vol/dev/dsk/c0t2d0/iv_cd /cdrom/iv_cd

As of Solaris 10, it is mandatory to execute InfoVista Server as a non-root user. Whenever other VistaFoundation products are installed on the same machine hosting the InfoVista Server, they must be run under the user infovista.The user infovista executes the Client/Server and handles the InfoVista Server administration tasks (such as creating additional concurrent servers).

SYSLOG DAEMON The syslog daemon must be activated on the server where InfoVista is running.

FONTS On Solaris, the ISO-8859-1 (Latin-1) Optional Fonts package (package name is SUNWi1of) may not be installed. In this case, reports using system fonts may be difficult to read. To get a report text correct rendering, apply the following procedure.

NOTE If you are using an evaluation key, you cannot connect to the InfoVista Server after the evaluation period. However, collected data remains and polling continues. You can access it again after you enter a new server license key.


NOTE Due to high security level compliance, Fail-Over doesn’t work with the default right granted to the user infovista created during the installation. If you want to benefit from the Fail-Over features, you need to assign a password to the user infovista for all the machines pertaining to the VistaFoundation.



Font settings

1 Logon as 'root'2 Use the command pkginfo to check if the SUNWi1of package is present on the

machine:pkginfo SUNWi1of If yes, go to step 3.if not, copy the package from the Solaris CD-ROM distribution, using the command:pkgadd -d /cdrom/cdrom0/solaris_2.9/product/SUNWi1of

The TrueType fonts are copied to the directory:/usr/openwin/lib/X11/fonts/TrueType

3 To permanently activate this font path under CDE, add the following block of instructions to /usr/dt/config/Xsetup.if [ -f /usr/openwin/lib/X11/fonts/TrueType/fonts.dir ]; then

if [ -z "$fontpath" ]; then

fontpath=/usr/openwin/lib/X11/fonts/TrueType

else

fontpath=$fontpath,/usr/openwin/lib/X11/fonts/TrueType

fi

fi

This block should be placed around line 151 between the block if [ "$LANG" != "C" ]; then

/. . ./

fi

and the block if [ ! -z "$fontpath" ]; then

$XDIR/xset fp+ $fontpath

fi

4 Reboot to take the new fonts into account.

HARDWARE REQUIREMENTS (SERVER) Memory, processor and disk requirements can vary depending on how you use InfoVista, notably in terms of database sizes.Always install IV Server on a dedicated machine. As a general rule, the following are the minimum requirements:

Refer to Appendix C of this guide for more details regarding the memory cache settings.

Minimum RAM 2 GB

Processor 900 MHz

Swap Double the RAM

Database disk space Dependent on number of devices polled (minimum 6 GB)



PERL INSTALLATION InfoVista 3.2 supports Perl 5.6.1 which is on the CD-ROM. See the Release notes for details on installing the Perl Software Development Kit.


VISTACOCKPIT 2.2 MONITORING InfoVista Server 3.2 is compliant with VistaCockpit 2.2.If you are ujsing VistaCockpit 2.2 for monitoring your InfoVista environment, it is mandatory that you first upgrade the Cockpit agent 2.2 to guarantee the compatibility between the Cockpit Server and its agent installed on your InfoVista Server.

EXPORT HTML TUNING REPORTS Xvfb is required to be able to export HTML tuning reports from the InfoVista Server. It is required by ivsupport (support package).When the user chooses to install IVReport on Solaris, Xvfb is now also installed.As of Solaris 9, Xvfb is integrated into the operating system. The setup checks that it is properly installed.The InfoVista installation is not stopped if Xvfb is not configured properly.




A first-time installation includes the following tasks:> installation of InfoVista software,> installation of two bundled InfoVista libraries (VistaView for Core and VistaView for

InfoVista Tuning).

Begin the installation

1 Insert the InfoVista CD into your CD-ROM drive.2 Login as root.3 Change directory to the CD-ROM drive (for example: cd /cdrom/cdrom0)4 Execute the command: ./setup and follow the instructions on the screen.

Tuning the file systemThe file system configuration that works best on Unix uses the "forcedirectio" parameter.

Set the ‘forcedirectio’ parameterTo make this modification, you must have root privileges.

1 Modify the /etc/vfstab file to add the parameter ’forcedirectio’ to the partitions used to store the ObjectStore databases. Below is an example of a vfstab file after modification:

2 For the changes to take effect, unmount (umount /dbase) and then remount the drives.



Creating Solaris users and groups for InfoVista productsInstalling and executing InfoVista Server 3.2 SP2 in the Solaris environment requires specific users and groups as listed below.

Using specific users and groups

These tables describe the role of each user and the group to which this user must belong depending on the Solaris version running on your machine.

YOU ARE RUNNING SOLARIS 9

YOU ARE RUNNING SOLARIS 10

*In this table, the name ivuser indicates a generic user. That is, ivuser refers to any individual user name.All users and groups must be either remote or local. You must determine this carefully in agreement with your system administrator as described below.

The user... performs the following User must belong to the groups

root Installation of InfoVista Server 3.2 SP2Execution of InfoVista Server 3.2 SP2 application

n/an/a

The user... performs the following User must belong to the groups

root Installation of InfoVista Server 3.2 SP2 application.Installation of hotfixes.Never use root to run applications

n/a

infovista Execution of InfoVista Server 3.2 SP2 services and maintenance tasks

infovista (primary group)

ivuser* Running the InfoVista Server 3.2 SP2 client (IVReport, IVCmd)

infovista



Creating users and groups [Solaris 10 only]

> If any one of the required users/groups (infovista, ivusers) must belong to the user directories (LDAP, NIS, etc.), your system administrator must refer to the createinfovistauser.sh script (located in the root CD-ROM) to manually create them on the directory system and with the proper privileges mapping before the installation. These are remote users.

> During installation, if the InfoVista Server 3.2 SP2 installer does not detect the mandatory infovista user, it creates it locally during the first phases of the installation. This is a local user.

> Once the InfoVista Server 3.2 SP2 installation is complete, each individual ivuser must be declared as being part of the infovista group.

Associating privileges with the infovista user [Solaris 10 only]

If your system administrator declares the users/groups as remote users, he can grant certain rights to the infovista user. This guarantees that the infovista user can use other InfoVista products such as the InfoVista Server. The script createinfovistauser.sh implements the appropriate commands.

NOTE To ensure that InfoVista applications recognize correctly the files created by the ivuser, we recommend that you set the ‘umask’ as follows:/usr/bin/umask -S u=rwx,g=rwx,o=

NOTE At the end of the installation process, the InfoVista Server 3.2 SP2 installer automatically runs the setprivs.sh script to grant the declared users the necessary execute/write/read privileges on the related directories.Each time you install a hotfix, you must run the setprivs.sh script again.

NOTE After an operating system upgrade to Solaris 10, InfoVista recommends that you reinstall the InfoVista Server 3.2 SP2 application in order to redefine the user identities and file rights. This allows you to work from a clean user environment.



Preparing the installation menuUse the Installation menu to provide the following information:

When you are satisfied that the information is correct, select option 10 Perform the installation (default selection) and press the Return key.

PERL INSTALLATION The Perl Integration Toolkit component installs a Perl scripting-language extension, which allows you to include InfoVista commands in Perl scripts.

Install InfoVista Perl API on a client

1 Ensure Perl 5.6.1 is installed in the directory <install dir>/perldist/5.6.1If necessary, the Perl 5.76.1 package is available in the redist directory of the installation package.

2 Install the SDK component from the InfoVista installation package.3 Copy the content of directory <install dir>/essentials/sdk/perl/5.6 into the

Perl installation directory.

N° Installation Menu Description

1 User Name Any string of characters

2 Company Name Any string of characters

3 License key If you have a license key, enter it here.If not, enter the evaluation key EVAL, which allows you to use the software for 30 days. Then apply to InfoVista for a new key. See section A.

4 Number of servers A minimum of 2GB of RAM is required for each server. See "Upgrading to InfoVista Server version 3.2" on page 32.

5 Installation directory Use the default directory:/opt/InfoVista/Essentials/.

6 Database paths Use the default directories:/opt/InfoVista/Essentials/data/manager.db

/opt/InfoVista/Essentials/data/collector.db

> This section is not available in case of multi-instance configuration.

7 Log directory Use the default directory:/opt/InfoVista/Essentials/log

8 Installation type full means both the server and client are installed with documentation and InfoVista libraries.

9 Quit

10 Perform the installation



OBJECTSTORE CONFIGURATION ObjectStore is the embedded database used by InfoVista. There may be more than one copy of ObjectStore on your system. The installation procedure prompts you to configure the copy which are used with InfoVista:The default copy of ObjectStore to configure is in /opt/InfoVista/Essentials

Is this the copy that you want to configure? Reply Yes.

CREATE LINKS TO OBJECTSTORE LIBRARIES ObjectStore uses shared libraries on your system. For ObjectStore applications and utilities to work, the dynamic linker must be able to find them. In answer to this question.Do you want to create links to ObjectStore libraries in /usr/lib? Reply Yes.

TRANSACTION LOG The installation procedure prompts you for a directory and filename which are used for logging transactions. Enter a transaction log pathname. By default:/opt/InfoVista/Essentials/log/transac.log

You may be asked to initialize this file. When it is initialized, the ObjectStore Server is up and running.After installation, do not delete the transac.log file (to gain space on your hard disk, for example). InfoVista needs the file to operate correctly.

SCHEMA DATABASE The installation procedure prompts you for a directory used for storing the Program Schema Databases. By default:/opt/InfoVista/Essentials/lib

Do not change this default directory value. This would prevent ObjectStore for running correctly.

OBJECTSTORE SERVER DAEMON ObjectStore includes a daemon which must be running for any application to access an ObjectStore database. It is best to accept an automatic server start and shutdown. See the previous sections "Tuning the ObjectStore server" on page 28 and "Tuning the file system" on page 21.

VISTACOCKPIT AGENT INSTALLATION Each InfoVista Server can be fully integrated with a VistaCockpit agent. VistaCockpit provides access to server status (logs, signals etc.) from a centralized console.The InfoVista VistaCockpit Management Agent installation includes the installation of the InfoVista Recovery agent. To install an InfoVista VistaCockpit Management Agent, you must ensure that a VistaCockpit Management Server is accessible on the network.Enter the hostname and port number of the machine where the InfoVista VistaCockpit Management Server is installed. (Setup asks you to confirm these parameters).

MODIFYING ADVANCED SERVER SETTINGS The installer asks if you wish to modify the default values of the advanced server settings. Reply No to leave the settings at their default values. Reply Yes to modify them.For each InfoVista Server endpoint, you can set a port number. If you leave the default (“Automatic”), the system randomly chooses an appropriate endpoint.

NOTE If you use a multiple IV Server instance configuration, it is no longer mandatory to specify the endpoint, except if you manage your servers with VistaCockpit.



> Manager Endpoint (Port): the IP port number used to access the InfoVista Manager. By default, this value is automatically generated by InfoVista.

> Collector Endpoint (Port): the IP port number used to access the InfoVista Collector. By default, this value is automatically generated by InfoVista.

> Browser Endpoint (Port): The IP port number used to access the InfoVista Browser. By default, this value is automatically generated by InfoVista.

Modify the advanced settings

1 Accept or modify the manager, collector and browser endpoints. The default value for these settings must always be Automatic.

2 A summary of the server configuration is displayed. It is possible to modify it at this stage.

UPDATING YOUR ENVIRONMENT Finally, the procedure lists the modifications that you should make to particular environment variables, for example:> PATH=$PATH:/opt/InfoVista/Essentials/bin

> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/InfoVista/Essentials/lib:/usr/openwin/lib

> OS_ROOTDIR=/opt/InfoVista/Essentials


NOTE With InfoVista Server 3.2, you can connect to a server with a connection string using the instance name in the case of a multi-server installation. See the InfoVista Server Administration Guide, ‘Communicating with the server’ for additional information.



Installing multiple IV Servers on one machine (Solaris)You can install multiple servers on a single Solaris machine. This feature has the following benefits:> Possibility of using a single machine to host multiple servers. Port use, database

location and specific log files can all be managed for each separate server.> Valid Manager, Collector and Browser end points for each server are proposed

during the setup.> The following sections explain the relevant prerequisites and procedures.

PREREQUISITES To install multiple InfoVista Servers on a single machine, it must be equipped at least with 2 processors and 4 GB of RAM per server. The following table summarizes the necessary hardware as a function of the number of server instances you want to install.

Install multiple servers (first installation)

1 Select option 4 from the Installation menu to set the number of servers you wish to install. The number displayed indicates the number of servers already installed. Change this number to take into account the total number of servers you intend to install. For example if you have 1 server currently installed and you wish to add 2 more, the number entered here is “3”.

2 Select option 10 to proceed with the installation.3 Follow the installation as for a first-time installation. If a VistaCockpit Management

Agent is already installed, you do not need to re-install another one.4 When you reach the question:

Do you want to modify the multi-server configuration (yes/no)?Either:Type yes.For each server, you are requested either to validate or modify the default values endpoints for each InfoVista Server and its related services.Or:Type no to use default server naming and endpoints.By default they are: iv1, iv2, etc. (automatic endpoints)


2 4 GB 2

3 6 GB 3

4 8 GB 4

etc. etc. etc.

NOTE With IV Server 3.2, you can add IV Server instances without using the setup. See the Administraton Guide ‘Adding a new IV Server instance’ for instructions.






PARAMETER DEFINITION You define these parameters in the file <install directory>/etc/<hostname>_server_parameters.

Once you have made these changes to the file, you must restart IVServer and ObjectStore to take the modifications into account:

Restart IV Server and ObjectStore

1 /etc/init.d/InfoVista stop

2 /etc/rc2.d/S80ostore4 stop

3 /etc/rc2.d/S80ostore4 start

4 /etc/init.d/InfoVista start


EXAMPLE If you have 4 IVServer Instances running:Restricted File DB Access: UserCache Manager Ping Time: 3600

Cache Manager Ping Time In Transaction: 3600

RPC Timeout: 3600Log File: /opt/InfoVista/Essentials/data/ostxn.log

Max AIO Threads: 8

N Message Buffers: 12



Installation directoriesAfter installation or upgrade, the following directories are created or upgraded in the /opt/InfoVista/Essentials directory.


/bin InfoVista binary executables. and the ObjectStore configuration tool.

/data ObjectStore databases.

/doc Online documentation.

/etc Resources used by the ObjectStore executables.

/init Contains InfoVista sub-init script started by the /etc/init.d/InfoVista main init script.

/lib Resources used by the executables.

/log InfoVista log files.

/mibs MIB files

/migration Scripts and executables needed to migrate a manager from version 2.3.

/sdk Programming extensions for Perl and C. HTML documentation is included for the Perl API.

/perldist Perl software package

/registry Product information used by the hotfix installer.

/vistacockpit Directory reserved for VistaCockpit 2.0 (not yet released)

/VViews VistaView XML files.

InfoVista Server 3.2 SP2 Starting the InfoVista Server and client 30


Starting the InfoVista Server and client

After you install InfoVista Server, check that the server and client function correctly.

Starting the serverThe InfoVista Server is started automatically after installation. If you experience problems, make sure that these services are running.

Restart InfoVista Servers manuallyThis command stops then starts all services (including the Port Mapper) on all InfoVista Servers installed on the machine:/etc/init.d/InfoVista start (starts all services)

These commands stop then start the specified services on all InfoVista Servers installed on the machine:/etc/init.d/InfoVista start manager

/etc/init.d/InfoVista start collector

/etc/init.d/InfoVista start browser

Restart services for a specific InfoVista instance (multiple installations)This following command stops then starts all services on one InfoVista Server installed on the machine:/etc/init.d/InfoVista start iv1 (starts all services on “iv1”)

The following command stops then starts the specified services on “iv1”:/etc/init.d/InfoVista start iv1 manager

/etc/init.d/InfoVista start iv1 collector

/etc/init.d/InfoVista start iv1 browser

Stop InfoVista services> Proceed as above and replace the command “stop”. For example, to stop the

browser on the server “iv5” enter:/etc/init.d/InfoVista stop iv5 browser

EXAMPLE ps -ef | grep ivserverivserver -m manager.db (the InfoVista Manager)ivserver -m manager.db -c collector.db (the InfoVista Collector)ivserver -m manager.db -b collector.db (the InfoVista Browser)ivserver -portmapper (the InfoVista Port Mapper)ps -ef | grep os

osserver (ObjectStore server)oscmgr6 (ObjectStore Cache Manager)



Starting an InfoVista clientThe InfoVista Server software is installed by default in: /opt/InfoVista/Essentials/bin

To start the client, execute: ./ivreport &By default, the connection parameters are:

During a client connection attempt, the server license key is checked against the all known MAC addresses on an NIC (Network Interface Card).

Server Name Name of the system running the InfoVista Server. If the server is the local system (the same system as the client), you can leave this parameter blank.


Password Blank. Change this password after startup.

NOTE In the case of multi-server installations, you need to specify the server instance (for example ‘iv1@hostname’).

InfoVista Server 3.2 SP2 Upgrading to InfoVista Server version 3.2 32


Upgrading to InfoVista Server version 3.2

> When going from InfoVista Server 3.x to 3.2, there is no need for a migration of data. This is an automatic upgrade that modifies the database schema, attributes, and model. It does not impact the data.

> When going from InfoVista Server 2.3 to InfoVista Server 3.2, the user must perform manually a database migration. The objective is to recreate a new database that is compatible with version 3.2 while conserving your data.

> See the InfoVista Server Administraton Guide for information about database migration.


the installation procedure. Refer to the ‘ObjectStore Management Guide’ for details.

> RAWFS are no more supported by InfoVista 3.2. It is recommended to remove any rawfs partition before installing InfoVista 3.2. Even if it is still possible to create RAWFS partition with ObjectStore, InfoVista 3.2 services will not start.



Upgrading to Solaris 10Whereas InfoVista Server version 3.1 works on Solaris 8, InfoVista Server 3.2 SP2 is only compatible with Solaris 9 and Solaris 10.Therefore, the whole upgrade process may require intermediate steps to ensure the mandatory InfoVista Server version/Solaris version compatibility. The following schema highlights the respective paths according to all possible cases, including the mandatory migration in case of IV version 2.3.



Example. Upgrade from IV Server 3.1 SP1/Solaris 8 to IV Server 3.2 SP2/Solaris 10

1 Upgrade Solaris 8 to Solaris 10.2 Upgrade the InfoVista Server version 3.1 SP1 to version 3.2 SP2.Once the operating system is upgraded, execute the command setprivs.sh then restart all the processes. Do not forget to create a user in the infovista group for using the InfoVista applications.



Uninstalling InfoVistaThere is now an integrated uninstall script with InfoVista provided on the CD-Rom. Note that this script can uninstall versions 2.3 SP2 or higher.

Backup InfoVista databases> Backup the two database files (manager.db and collector.db). You must redirect

the backup files to a separate directory from the InfoVista <install_dir>. Use this command:<install_dir>/bin/osbackup -f backup_file_pathname manager_pathname collector_pathname

Uninstall InfoVista on Solaris platforms

1 Launch the uninstall.sh from the CD-Rom../uninstall.shThe uninstall script lists the currently installed components:• InfoVista Server installation directory• The Recovery Agent option (2.3 SP2 or higher installation)• The InfoVista Cockpit Agent

2 You are asked to agree with the above information. Enter “yes”.3 The following question appears:

Are you sure you want to remove everything, including database?

• Answer “no” to check the removal of each element one by one.• Answer “yes” to remove everything automatically (including databases).

4 If you choose the step by step uninstallation, a confirmation is requested for the following components:• The Cockpit Agent• InfoVista Server (all services are shut down first then IV Server files are

removed).• The log directory in the /Essentials directory.• ObjectStore (for a complete removal, you must answer yes to this removal).• DCE (daemons, services and files).

NOTE During the automatic uninstallation, if you answer “No” to the following question: ‘WARNING: Any database file in <install_dir>/data will be deleted! Continue?’, the uninstallation exits and the installation remains incomplete.

35

3 Installation (Linux)

InfoVista Server and client work with systems running under Linux RedHat AS4.

See:"Product details and prerequisites" on page 36"Performing a first-time installation" on page 38"Starting the InfoVista Server and client" on page 46"Moving to InfoVista Server version 3.2" on page 48"Uninstalling InfoVista" on page 49


Installation Guide - Chapter 3 Installation (Linux)

Product details and prerequisites


INFOVISTA SERVER SOFTWARE PACKAGE The InfoVista Server software requires a license key. This determines the period of time you can access the server.> For an evaluation or demonstration period, use the key EVAL which gives server

access for a period of 30 days starting from your first connection.> For an extended evaluation or an unlimited period, you need a license key

provided by InfoVista. See "Getting and setting a license key" on page 50”.

SOFTWARE REQUIREMENTS You can install the InfoVista Server and client on systems:> Running RedHat AS4 under kernel 2.6.9-42.EL.smp. > With Xvfb installed.Download and install the RPM from https://rhn.redhat.com:

> rpm -i xorg-x11-Xvfb-6.8.2-1.EL.13.25.x86_64.rpm

> With a specific 64-bit version of the standard C++ library. Download and install the RPM from https://rhn.redhat.com:> rpm -i compat-libstdc++-33-3.2.3-47.3.x86_64.rpm

> With an LVM volume for databases (for specific settings, see "Tuning the file system" on page 38.)

> The /tmp directory must be mounted as tmpfs type (for specific settings "Tuning the file system" on page 38.)

On Linux, if the CD-ROM is mounted with a mount option other than UDFS, the InfoVista Server installation cannot work. In this case, change the option to UDFS:>mount -F udfs -o nosuid,ro /vol/dev/dsk/c0t2d0/iv_cd /cdrom/iv_cd

NOTE If you are using an evaluation key, you cannot connect to the InfoVista Server after the evaluation period. However, collected data remains and polling continues. You can access it again after you enter a new server license key.




HARDWARE REQUIREMENTS (SERVER) Memory, processor and disk requirements can vary depending on how you use InfoVista, notably in terms of database sizes.Always install IV Server on a dedicated machine. As a general rule, the following are the minimum requirements:

Refer to Appendix C of this guide for more details regarding the memory cache settings.

PERL INSTALLATION InfoVista 3.2 supports Perl 5.6.1 which is on the CD-ROM. See the Release notes for details on installing the Perl Software Development Kit.


Minimum RAM 2 GB

Processor 900 MHz

Swap Double the RAM

Database disk space

Dependent on number of devices polled (6 GB minimum configuration)




A first-time installation includes the following tasks:> installation of InfoVista software,> installation of two bundled InfoVista libraries (VistaView for Core and VistaView for

InfoVista Tuning).

Begin the installation

1 Insert the InfoVista CD into your CD-ROM drive.2 Login as root.3 Change directory to the CD-ROM drive (for example: cd /cdrom/cdrom0)4 Execute the command: ./setup and follow the instructions on the screen.

Tuning the file systemDatabase backups require LVM volume management and ext3 filesystem.Mounting /tmp as tmpfs is mandatory to obtain proper ObjectStore performance.

Tune the file system

1 For Database partitions, use the ext3 filesystem on Logical LVM volume with free PE Database (manager and collector) backup on Linux only work if they reside on an ext3 file systems on a logical volume (LV) part of an LVM volume group (VG) with free physical extend (PE).

Volume Group (VG) is an aggregate of several partitions and/or disks. VGs are subdivided in units called Physical Extend (PE).Logical Volumes are made of a certain number of PE and support the file system (i.e. ext3)You need a good amount of Free PE (PE not used in an LV): at least 10% of the projected databases size (Manager and Collector) in order to make snapshots during backups.



To check if there is free space, use ‘vgdisplay’ (as root) to display the volume group:# vgdisplay

In the example above, there is 10.18GB of free space (check Free PE/Size line). This would allow you to backup databases up to 100 GB total).Refer to RedHat documentation for LVM volume creation.If you do not set LVM volume(s) prior to installing IV Server, make sure that you stop the product (and ObjectStore) before you work with database volumes.

2 Make sure the /tmp is mounted using tmpfs type and uses the size option.The /tmp folder is highly used by ObjectStore cache and the sizing requirements vary depending on the number of IV Server instances and the RAM available on the machine, according to this table:

Volume groupVG Name VG1System ID Format lvm2Metadata Areas 3Metadata Sequence No 240VG Access read/writeVG Status resizableMAX LV 0Cur LV 5Open LV 5Max PV 0Cur PV 3Act PV 3VG Size 410.18 GBPE Size 4.00 MBTotal PE 105006Alloc PE / Size 102400 / 400.00 GBFree PE / Size 2606 / 10.18 GBVG UUID 4W398B-mNyf-29mQ-9IhZ-MyzN-Jlvp-2z62rJ

Server/RAM < 384MB <= 512MB <= 1GB <= 2GB > 2GB

Manager 16 MB 48 MB 64 MB 80 MB 128 MB

Collector 48 MB 128 MB 192 MB 256 MB 384 MB

Browser 32 MB 64 MB 192 MB 256 MB 384 MB



Following previous example, here is an example of the corresponding /etc/fstab:

You apply the settings for /tmp prior to installing IV Server. If not, make sure you stop the product completely before you apply any change.

Restart IV Server and ObjectStore

1 Edit /etc/fstab and change /tmp settings/etc/init.d/InfoVista stop

2 Remove all files in /tmp3 Unmount /tmp (if applicable)4 Mount /tmp

/etc/init.d/InfoVista start



Preparing the installation menuUse the Installation menu to provide the following information:

When you are satisfied that the information is correct, select option 10 Perform the installation (default selection) and press the Return key.

PERL INSTALLATION The Perl Integration Toolkit component installs a Perl scripting-language extension, which allows you to include InfoVista commands in Perl scripts.

Install InfoVista Perl API on a client

1 Ensure Perl 5.6.1 is installed in the directory <install dir>/perldist/5.6.1If necessary, the Perl 5.76.1 package is available in the redist directory of the installation package.

2 Install the SDK component from the InfoVista installation package.3 Copy the content of directory <install dir>/essentials/sdk/perl/5.6 into the

Perl installation directory.

N° Installation Menu Description

1 User Name Any string of characters

2 Company Name Any string of characters

3 License key If you have a license key, enter it here.If not, enter the evaluation key EVAL, which allows you to use the software for 30 days. Then apply to InfoVista for a new key. See section A.

4 Number of servers A minimum of 2GB of RAM is required for each server. See "Moving to InfoVista Server version 3.2" on page 48.

5 Installation directory Use the default directory:/opt/InfoVista/Essentials/.

6 Database paths Use the default directories:/opt/InfoVista/Essentials/data/manager.db

/opt/InfoVista/Essentials/data/collector.db

> This section is not available in case of multi-instance configuration.

7 Log directory Use the default directory:/opt/InfoVista/Essentials/log

8 Installation type full means both the server and client are installed with documentation and InfoVista libraries.

9 Quit

10 Perform the installation



OBJECTSTORE CONFIGURATION ObjectStore is the embedded database used by InfoVista. There may be more than one copy of ObjectStore on your system. The installation procedure prompts you to configure the copy which are used with InfoVista:The default copy of ObjectStore to configure is in /opt/InfoVista/Essentials

Is this the copy that you want to configure? Reply Yes.

CREATE LINKS TO OBJECTSTORE LIBRARIES ObjectStore uses shared libraries on your system. For ObjectStore applications and utilities to work, the dynamic linker must be able to find them. In answer to this question.Do you want to create links to ObjectStore libraries in /usr/lib?

> Reply Yes.

TRANSACTION LOG The installation procedure prompts you for a directory and filename which are used for logging transactions. Enter a transaction log pathname. By default:/opt/InfoVista/Essentials/log/transac.log

You may be asked to initialize this file. When it is initialized, the ObjectStore Server is up and running.After installation, do not delete the transac.log file (to gain space on your hard disk, for example). InfoVista needs the file to operate correctly.

SCHEMA DATABASE The installation procedure prompts you for a directory used for storing the Program Schema Databases. By default:/opt/InfoVista/Essentials/lib

Do not change this directory value. This prevents ObjectStore from running correctly.

OBJECTSTORE SERVER DAEMON ObjectStore includes a daemon which must be running for any application to access an ObjectStore database. It is best to accept an automatic server start and shutdown. See the previous sections "Tuning the ObjectStore server" on page 44 and "Tuning the file system" on page 38.

VISTACOCKPIT AGENT INSTALLATION Each InfoVista Server can be fully integrated with a VistaCockpit agent. VistaCockpit provides access to server status (logs, signals etc.) from a centralized console.The InfoVista VistaCockpit Management Agent installation includes the installation of the InfoVista Recovery agent. To install an InfoVista VistaCockpit Management Agent, you must ensure that a VistaCockpit Management Server is accessible on the network.Enter the hostname and port number of the machine where the InfoVista VistaCockpit Management Server is installed. (Setup asks you to confirm these parameters).

MODIFYING ADVANCED SERVER SETTINGS The installer asks if you wish to modify the default values of the advanced server settings. Reply No to leave the settings at their default values. Reply Yes to modify them.For each InfoVista Server endpoint, you can set a port number. If you leave the default (“Automatic”), the system randomly chooses an appropriate endpoint.



> Manager Endpoint (Port): the IP port number used to access the InfoVista Manager. By default, this value is automatically generated by InfoVista.

> Collector Endpoint (Port): the IP port number used to access the InfoVista Collector. By default, this value is automatically generated by InfoVista.

> Browser Endpoint (Port): The IP port number used to access the InfoVista Browser. By default, this value is automatically generated by InfoVista.

Modify the advanced settings

1 Accept or modify the manager, collector and browser endpoints. The default value for these settings must always be Automatic.

2 A summary of the server configuration is displayed. It is possible to modify it at this stage.

UPDATING YOUR ENVIRONMENT Finally, the procedure lists the modifications that you should make to particular environment variables, for example:> PATH=$PATH:/opt/InfoVista/Essentials/bin

> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/InfoVista/Essentials/lib:/usr/openwin/lib

> OS_ROOTDIR=/opt/InfoVista/Essentials

Installing multiple IV Servers on one machine (Linux)You can install multiple servers on a single Linux machine. This feature has the following benefits:> Possibility of using a single machine to host multiple servers. Port use, database

location and specific log files can all be managed for each separate server.> Valid Manager, Collector and Browser end points for each server are proposed

during the setup.> The following sections explain the relevant prerequisites and procedures.

PREREQUISITES To install multiple InfoVista Servers on a single machine, it must be equipped at least with 2 processors and 4 GB of RAM per server. The following table summarizes the necessary hardware as a function of the number of server instances you want to install.

NOTE If you use a multiple IV Server instance configuration, it is no longer mandatory to specify the endpoint, except if you manage your servers with VistaCockpit.


NOTE With InfoVista Server 3.2, you can connect to a server with a connection string using the instance name in the case of a multi-server installation. See the InfoVista Server Administration Guide, ‘Communicating with the server’ for additional information.



Install multiple servers (first installation)

1 Select option 4 from the Installation menu to set the number of servers you wish to install. The number displayed indicates the number of servers already installed. Change this number to take into account the total number of servers you intend to install. For example if you have 1 server currently installed and you wish to add 2 more, the number entered here is “3”.

2 Select option 10 to proceed with the installation.3 Follow the installation as for a first-time installation. If a VistaCockpit Management

Agent is already installed, you do not need to re-install another one.4 When you reach the question:

Do you want to modify the multi-server configuration (yes/no)?Either:Type yes. For each server, you are requested either to validate or modify the default values endpoints for each InfoVista Server and its related services.Or:Type no to use default server naming and endpoints. By default they are: iv1, iv2, etc. (automatic endpoints)




PARAMETER DEFINITION You define these parameters in the file <install directory>/etc/<hostname>_server_parameters.


2 4 GB 2

3 6 GB 3

4 8 GB 4

etc. etc. etc.

NOTE With IV Server 3.2, you can add IV Server instances without using the setup. See the Administration Guide ‘Adding a new IV Server instance’ for instructions.



Once you have made these changes to the file, you must restart IV Server and ObjectStore to take the modifications into account.


Installation directoriesAfter installation or upgrade, the following directories are created or upgraded in the/opt/InfoVista/Essentials directory.

EXAMPLE If you have 4 IV Server Instances running:Restricted File DB Access: User

Cache Manager Ping Time: 3600

Cache Manager Ping Time In Transaction: 3600RPC Timeout: 3600

Log File: /opt/InfoVista/Essentials/data/ostxn.log

Max AIO Threads: 8N Message Buffers: 12


bin InfoVista binary executables. and the ObjectStore configuration tool.

doc User documentation in PDF format.

etc Resources used by the ObjectStore executables.

init InfoVista sub-init script started by the /etc/init.d/InfoVista main init script.

java Java applications used by external pollers (like for the CCM protocol)

jdk Contains a Sun Java Developer Kit

lib64 64-bit resources and binary executables

log InfoVista log files.

mibs MIB files

psi Contains files used the PSI protocol.

sdk Programming extensions for Perl and C. HTML documentation is included for the Perl API.

registry Product information used by the hotfix installer.

vistacockpit Directory reserved for VistaCockpit 2.0 (not yet released)

VViews VistaView XML files.



Starting the InfoVista Server and client

After you install InfoVista Server, check that the server and client function correctly.

Starting the serverThe InfoVista Server is started automatically after installation. If you experience problems, make sure that these services are running.

Restart InfoVista Servers manuallyThis command stops then starts all services (including the Port Mapper) on all InfoVista Servers installed on the machine:/etc/init.d/InfoVista start (starts all services)

These commands stop then start the specified services on all InfoVista Servers installed on the machine:/etc/init.d/InfoVista start manager

/etc/init.d/InfoVista start collector

/etc/init.d/InfoVista start browser

Restart services for a specific InfoVista instance (multiple installations)This following command stops then starts all services on one InfoVista Server installed on the machine:/etc/init.d/InfoVista start iv1 (starts all services on “iv1”)

The following command stops then starts the specified services on “iv1”:/etc/init.d/InfoVista start iv1 manager

/etc/init.d/InfoVista start iv1 collector

/etc/init.d/InfoVista start iv1 browser

Stop InfoVista services> Proceed as above and replace the command “stop”. For example, to stop the

browser on the server “iv5” enter:/etc/init.d/InfoVista stop iv5 browser

EXAMPLE ps -ef | grep ivserverivserver -m manager.db (the InfoVista Manager)ivserver -m manager.db -c collector.db (the InfoVista Collector)ivserver -m manager.db -b collector.db (the InfoVista Browser)ivserver -portmapper (the InfoVista Port Mapper)ps -ef | grep os

osserver (ObjectStore server)oscmgr6 (ObjectStore Cache Manager)



Starting an InfoVista clientThe InfoVista Server software is installed by default in: /opt/InfoVista/Essentials/bin

To start the client, execute: ./ivreport &

By default, the connection parameters are:

During a client connection attempt, the server license key is checked against the all known MAC addresses on an NIC (Network Interface Card).

Server Name Name of the system running the InfoVista Server. If the server is the local system (the same system as the client), you can leave this parameter blank.


Password Blank. Change this password after startup.

NOTE In the case of multi-server installations, you need to specify the server instance (for example ‘iv1@hostname’).



Moving to InfoVista Server version 3.2

> When going from InfoVista Server 3.x to 3.2 SP2 on a Linux platform, you must perform manually a remote database migration. The purpose is to create a new database that is Linux-compatible.

> See the InfoVista Server Administration Guide for information about database migration.


the installation procedure. Refer to the ‘ObjectStore Management Guide’ for details.

> RAWFS are no more supported by InfoVista 3.2. It is recommended to remove any rawfs partition before installing InfoVista 3.2. Even if it is still possible to create RAWFS partition with ObjectStore, InfoVista 3.2 services will not start.





Uninstalling InfoVistaThere is now an integrated uninstall script with InfoVista provided on the CD-Rom. Note that this script can uninstall versions 2.3 SP2 or higher.

Backup InfoVista databases> Backup the two database files (manager.db and collector.db). You must redirect

the backup files to a separate directory from the InfoVista <install_dir>. Use this command:<install_dir>/bin/osbackup -f backup_file_pathname manager_pathname collector_pathname

Uninstall InfoVista on Linux platforms

1 Launch the uninstall.sh from the CD-Rom../uninstall.shThe uninstall script lists the currently installed components:• InfoVista Server installation directory• The Recovery Agent option (2.3 SP2 or higher installation)• The InfoVista Cockpit Agent

2 You are asked to agree with the above information. Enter “yes”.3 The following question appears:

Are you sure you want to remove everything, including database?

• Answer “no” to check the removal of each element one by one.• Answer “yes” to remove everything automatically (including databases).

4 If you choose the step by step uninstallation, a confirmation is requested for the following components:• The Cockpit Agent• InfoVista Server (all services are shut down first then IV Server files are

removed).• The log directory in the /Essentials directory.• ObjectStore (for a complete removal, you must answer yes to this removal).

NOTE During the automatic uninstallation, if you answer “No” to the following question: ‘WARNING: Any database file in <install_dir>/data will be deleted! Continue?’, the uninstallation exits and the installation remains incomplete.

50

A Getting and setting a license key

This section gives practical details about how to obtain and set your InfoVista Server license key.

"License keys - an overview" on page 51"Using license keys" on page 52

InfoVista Server 3.2 SP2 License keys - an overview 51

Installation Guide - Appendix A Getting and setting a license key

License keys - an overview

Each InfoVista Server is protected by a license key. This key allows you to install the server and use it for a period of time that depends on the type of key. It is linked to the MAC address of the InfoVista Server system.The InfoVista Server is distributed as two functional versions: the Production version and the Workshop version. The key for the Production version is different from the key for the Workshop version.

Production versionThe Production version is essentially a platform used to run and access reports. It allows you to create Instances from existing Vistas, create reports from existing Report Templates, and modify existing Report Templates, but not to create new ones.

Workshop versionThe Workshop version is a development platform that has the same functionality and performance as the Production version, but that additionally allows you to create new Report Templates (and their associated Vistas, Graph Templates, Indicators, and Formulas).

Add-on InfoVista libraryEach add-on VistaView for InfoVista is also protected by a license key. This key allows you to install the VistaView and use it for a period of time that depends on the type of key. For more details see the section below "Entering a new VistaView license key" on page 53.

InfoVista Server 3.2 SP2 Using license keys 52


Using license keys

Installing the server

Install the server

1 When you first receive your software package, install it using the Evaluation Key, “EVAL”. This allows you to use the server for a 30-day trial period on any machine and to use any VistaView for 30 days.

2 Apply for Unlimited Keys (see "Requesting license keys" on page 52). These keys give you unlimited use of the server and the InfoVista libraries, installed on a specific system.

3 If you need to move the InfoVista Server and libraries to another system or upgrade the existing one, apply for Replacement Unlimited Keys (follow the procedure below).

Installing the clientWhen you install the client, use the same key as for the server: either EVAL or the unlimited key.

Installing a VistaView1 If you install add-on libraries, you automatically have free access to them for 30

days.2 After this period, apply for an Unlimited Key.

Requesting license keysTo obtain a license key for InfoVista Server, go to the following URL and follow the instructions:

http://www.infovista.com/services/customer_support/license_key/default.asp

InfoVista Server 3.2 SP2 Using license keys 53


Entering a new license key (ivserver)

Enter a new license key (Windows environment)

1 On the server system, select: Start/Programs/InfoVista/Set License Key

2 Enter your new license key.3 Click Set Key.

Enter a new license key (Sun environment)

1 On the server system, login as root.2 Change directory to: /opt/InfoVista/Essentials/bin 3 Execute ./ivsetkey4 Enter your new license key.5 Click Set Key.

Entering a new VistaView license key

Enter a new VistaView license key

1 Start the InfoVista graphic client and connect to the server.2 In the main window, expand the Libraries node.3 Double-click the Library corresponding to the new VistaView. The library property

sheet opens.4 Enter the VistaView license key in the License field.5 Click OK to save the modification and close the property sheet.

54

B Compatibility Matrix

This section provides the cross-compatibility between the latest versions of the InfoVista Server software, whenever you are using an heterogeneous InfoVista environment.

"Connecting to 3.2 SP2 from former client versions" on page 55

InfoVista Server 3.2 SP2 Connecting to 3.2 SP2 from former client versions 55

Installation Guide - Appendix B Compatibility Matrix

Connecting to 3.2 SP2 from former client versions

The following tables reads as follows:> OK means that the client IV instance, or IVCmd commands, connect to the IV

server instance.> N/A means that the IV client instance, or IVCmd commands, cannot connect to the

IV server. The connection is rejected.

Server 3.1 Server 3.1 SP1 Server 3.2 Server 3.2 SP2Client 3.1 OK OK N/A OKClient 3.1 SP1 OK OK N/A OK

Client 3.2 OK OK OK OK

Client 3.2 SP2 OK OK OK OK

56

C General Settings

This appendix provides general settings which address the Windows, Solaris and Linux environments.

"Cache settings" on page 57"Address space settings" on page 57

InfoVista Server 3.2 SP2 57

Installation Guide - Appendix C General Settings

Cache settingsDefault cache settings are calculated during the InfoVista Server startup according to the available memory. The following table provides the reciommended values according to the available RAM.

Address space settingsThe following table provides the address space settings according to the Operating System. Do not change these values unless you are performing an upgrade with preset different values.> Use the IV Report graphical user interface to change the value.> Consult your InfoVista Technical Support prioir to modifying space setting> The new values will be effective when you restart the IV ServerFor durther details regarding the Address space settings, refer to the Database Setup Family description in the InfoVista 3.2 Administration Guide.

Total RAM Recommended cache settings

Manager Collector Browser

Minimum< 384 Mbytes 16 Mbytes 48 Mbytes 32 Mbytes

<= 512 Mbytes 48 Mbytes 128 Mbytes 64 Mbytes

Recommended

<= 1024 Mbytes 64 Mbytes 192 Mbytes 192 Mbytes

<= 2048 MBytes 80 Mbytes 256 Mbytes 256 Mbytes

> 2048 Mbytes 128 Mbytes 384 Mbytes 384 Mbytes

Solaris OS_AS_START = 0x90000000OS_AS_SIZE = 0x60000000

Windows OS_AS_START = 0x12000000OS_AS_SIZE = 0x40000000

Linux OS_AS_START = 0x90000000OS_AS_SIZE = 0x60000000

58

InfoVista Server 3.2 SP2 Installation Guide Index

Index

Ccompatibility, between versions . . . . . . . . . . . . . . 6

Ddefault directories (Windows) . . . . . . . . . . . . . . . . 9

FFile system tuning . . . . . . . . . . . . . . . . . . . . . . .

Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21, 38first-time installation . . . . . . . . . . . . . . . . . . . . . .

Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . 27, 43Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

IInfoVista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

uninstalling (Solaris) . . . . . . . . . . . . . . . 34, 49uninstalling (Windows). . . . . . . . . . . . . . . . . 16

installation (Solaris) . . . . . . . . . . . . . . . . . . . . . .directories . . . . . . . . . . . . . . . . . . . . . . . 29, 45installation menu . . . . . . . . . . . . . . . . . . 21, 38modifying advanced server settings . . . 25, 42ObjectStore configuration . . . . . . . . . . . 25, 42prerequisites . . . . . . . . . . . . . . . . . . . . . 27, 43transaction log . . . . . . . . . . . . . . . . . . . . 25, 42updating your environment . . . . . . . . . . 26, 43VistaCockpit Management Agent . . . . . 25, 42

installation (Windows). . . . . . . . . . . . . . . . . . . . .before installing . . . . . . . . . . . . . . . . . . . . . . . 7default directories . . . . . . . . . . . . . . . . . . . . . 9directories . . . . . . . . . . . . . . . . . . . . . . . . . . 13finishing the installation . . . . . . . . . . . . . . . . 10first-time installation. . . . . . . . . . . . . . . . . . . . 8selecting components to install . . . . . . . . . . . 8selecting program folder . . . . . . . . . . . . . . . 10Server software . . . . . . . . . . . . . . . . . . . . . . . 6software protection . . . . . . . . . . . . . . . . . . . . 6VistaCockpit Management Agent . . . . . . . . 10

LLicence keys . . . . . . . . . . . . . . . . . . . . . . . . . . .

installing a VistaView . . . . . . . . . . . . . . . . . 52installing the client. . . . . . . . . . . . . . . . . . . . 52using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

License key . . . . . . . . . . . . . . . . . . . . . . . . . . . .Production version . . . . . . . . . . . . . . . . . . . 51Workshop version . . . . . . . . . . . . . . . . . . . . 51

Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .file system tuning . . . . . . . . . . . . . . . . . . . . 38installation . . . . . . . . . . . . . . . . . . . . . . . . . . 38installation directories . . . . . . . . . . . . . . . . . 45multiple IV Servers . . . . . . . . . . . . . . . . . . . 43ObjectStore server tuning . . . . . . . . . . . . . . 44prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 36

Mmodifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

advanced server settings (Solaris) . . . . 25, 42

OObjectStore . . . . . . . . . . . . . . . . . . . . . . . . . . . .

configuration (Solaris) . . . . . . . . . . . . . . 25, 42ObjectStore server daemon, configure. . . . . 25, 42

PPerl version . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . 19, 37Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

prerequisites (Solaris) . . . . . . . . . . . . . . . . . 27, 43Server hardware requirements . . . . . 6, 19, 37

Processes, for server . . . . . . . . . . . . . . . . . . 30, 46Production version, License key. . . . . . . . . . . . . 51

RRedHat AS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Sselecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

components to install (Windows) . . . . . . . . . 8program folder (Windows). . . . . . . . . . . . . . 10

Server, InfoVista. . . . . . . . . . . . . . . . . . . . . . . . .

59

InfoVista Server 3.2 SP2 Installation Guide Index

hardware requirements (Solaris) . . . . . . 19, 37hardware requirements (Windows) . . . . . . . . 6software installation (Windows) . . . . . . . . . . . 6software protection (Solaris) . . . . . . . . . 18, 36Solaris processes . . . . . . . . . . . . . . . . . 30, 46

software protection. . . . . . . . . . . . . . . . . . . . . . .add-on VistaViews. . . . . . . . . . . . . . . . . . . . 51mechanisms . . . . . . . . . . . . . . . . . . . . . 51, 55production version . . . . . . . . . . . . . . . . . . . . 51Server software (Solaris) . . . . . . . . . . . . 18, 36workshop version. . . . . . . . . . . . . . . . . . . . . 51

Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .users and groups. . . . . . . . . . . . . . . . . . . . . 22

Solaris processes, for server . . . . . . . . . . . . 30, 46start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

client (Solaris) . . . . . . . . . . . . . . . . . . . . 31, 47client (Windows) . . . . . . . . . . . . . . . . . . . . . 14server (Windows). . . . . . . . . . . . . . . . . . . . . 14

Ttransaction log (Solaris) . . . . . . . . . . . . . . . . 25, 42troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . .

Windows Event Viewer . . . . . . . . . . . . . . . . 15Windows services . . . . . . . . . . . . . . . . . . . . 15

Uuninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . .

InfoVista (Solaris) . . . . . . . . . . . . . . . . . 34, 49InfoVista (Windows). . . . . . . . . . . . . . . . . . . 16

Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .file system tuning. . . . . . . . . . . . . . . . . . 21, 38

updating your environment (Solaris). . . . . . . 26, 43upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

installation directories . . . . . . . . . . . . . . 29, 45using Licence keys . . . . . . . . . . . . . . . . . . . . . . . 52

VVistaCockpit Management Agent . . . . . . . . . . . . .

installation (Solaris) . . . . . . . . . . . . . . . . 25, 42installation (Windows) . . . . . . . . . . . . . . . . . 10

WWorkshop version, License key . . . . . . . . . . . . . 51

Remarks

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

ERRORS DETECTED

SUGGESTED IMPROVEMENTS

Please send this completed form to:

InfoVista SA6 rue de la Terre de Feu

91952 Courtaboeuf cedex

France

If you prefer, you may send your remarks via E-mail to [email protected]

Thank you for your cooperation.

InfoVista Server 3.2 SP2 Installation Guide 21 December 2006

mailto:[email protected]

mailto:[email protected]

Documents

InfoVista Server 3.2 SP2 Installation Guide