emc smarts adapter for infovista vf2 1.2 user guide...emc corporation corporate headquarters:...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC SmartsAdapter for InfoVista VF2

1.2

User GuideP/N 300-006-666

REV A01

EMC Smarts Adapter for InfoVista VF2 User Guide2

Copyright © 2006 – 2008 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com

All other trademarks used herein are the property of their respective owners.

Contents

Preface......................................................................................................................... 5

Chapter 1 Introduction Overview.................................................................................................................. 10 Process flows ........................................................................................................... 11

Topology process flow..................................................................................... 11Conversion of InfoVista VF2 traps to notifications process flow .............. 12

Deployment configurations................................................................................... 13 Display of InfoVista VF2 reports from the Global Console .............................. 15

How client tools retrieve reports.................................................................... 15

Chapter 2 Configuring the Adapter Deployment Prerequisites ............................................................................................................ 18 Modifying EMC Smarts configuration files........................................................ 19 Location of InfoVista VF2 Adapter configuration files ..................................... 20 Summary of configuration tasks .......................................................................... 21 Configuring the adapter ........................................................................................ 22

Configuring adapter configuration parameters........................................... 22Configuring adapter security.......................................................................... 23

Configuring the IP Availability Manager............................................................ 24Configuring the serverConnect.conf file ....................................................... 24

Configuring the Global Manager ......................................................................... 25Importing the configureInfoVistaTools2.xml file ........................................ 25Configuring the JAR file variable................................................................... 25Editing the infovista2.properties file ............................................................. 26

Configuring the Global Console........................................................................... 28Editing the client tool files............................................................................... 28Editing the client tool scripts .......................................................................... 28

Configuring the Adapter Platform....................................................................... 31Modifying the trap_mgr.conf file................................................................... 31

Verifying the installation........................................................................................ 32Manually exporting topology......................................................................... 32Manually importing topology into the InfoVista VF2 server .................... 33

Automating topology export ................................................................................ 34Editing the runExportImport script............................................................... 34Editing the sm_sched utility ........................................................................... 35Running the sm_sched utility ......................................................................... 36

EMC Smarts Adapter for InfoVista VF2 User Guide 3

Configuring Report Communications on the InfoVista Server ........................ 37Configuring Communications for Trap reports ........................................... 37Configuring Communications for Vista TroubleShooter (VTS) reports... 38

Chapter 3 Using the Global Console Viewing an InfoVista VF2 report........................................................................... 40 Viewing and responding to notifications............................................................. 41

Appendix A InfoVista VF2 and EMC Smarts Classes

Appendix B Related Information SAM Adapters Suite and Report Manager installation directory................... 46 EMC Smarts SAM Adapters Suite and Report Manager products.................. 47 EMC Smarts SAM Adapters Suite and Report Manager documentation....... 48

EMC Smarts Service Assurance Management Suite.................................... 48 Related documentation .......................................................................................... 49

Appendix C Understanding the sm_edit Utility

Index .......................................................................................................................... 53


Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

This document describes the configuration and operation of the EMC Smarts Adapter for InfoVista VF2 (InfoVista VF2 Adapter).

Audience This document is intended for individuals responsible for configuring and using the adapter.

Conventions used inthis document

EMC uses the following conventions for notes and cautions.

Note: A note presents information that is important, but not hazard-related.

IMPORTANT!An important notice contains information essential to the operation of the software.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.


Preface

Typographical conventionsEMC uses the following conventions in this guide:

Pathname conventionsDirectory pathnames are shown with forward slashes (/). Users of the Windows operating systems should substitute back slashes (\) for forward slashes.

Graphical conventionsIf there are figures illustrating consoles in this document, they represent the consoles as they appear in Windows. Under UNIX, the consoles appear with slight differences. For example, in views that display items in a tree hierarchy such as the Topology Browser, a plus sign appears for Windows and an open circle displays for UNIX.

Normal font In running text:• Interface elements (for example, button names, dialog box names) outside of

procedures• Items that the user selects outside of procedures• Java classes and interface names• Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, filenames, functions, menu names, utilities

• Pathnames, URLs, filenames, directory names, computer names, links, groups, service keys, file systems, environment variables (for example, command line and text), notifications

Bold In procedures:• Names of dialog boxes, buttons, icons, menus, fields, and maps• Selections from the user interface, including menu items, and field entries• Key names• Window names• Code examples• Commands• User interface tabs

Italic Used for:• Full publications titles referenced in textIn procedures:• Directory paths• Filenames• Scripts• Important/unique words• URLs• Utilities• Variables

Courier Used for:• System output• User entry

< > Angle brackets used to enclose parameter or variable values supplied by the user.

[ ] Square brackets used to indicate optional values.

| Vertical bar used to indicate alternate selections. The bar means “or”.

{ } Braces used to indicate content that you must specify (that is, x or y or z).

... Ellipses used to indicate nonessential information omitted from the example.

% Used to indicate a C shell prompt.

# Used to indicate a C shell superuser prompt.

▼▲ Used to indicate a command is wrapped over one or more lines. The command must be typed as one line.


Preface

Smarts ManagerUnless otherwise specified, the term Smarts Manager is used to refer to EMC Smarts programs such as Domain Managers, Global Managers, and adapters.

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink™ website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Sales and customer service contacts — For the list of EMC sales locations, please access the EMC home page at:

http://EMC.com/contact


http://powerlink.emc.com

Preface


1

This chapter provides a brief overview of the InfoVista VF2 Adapter. It contains the following information:

◆ Overview ......................................................................................................................... 10◆ Process flows....................................................................................................................11◆ Deployment configurations.......................................................................................... 13◆ Display of InfoVista VF2 reports from the Global Console...................................... 15

Introduction

Introduction 9

Introduction

OverviewThe InfoVista VF2 Adapter integrates with the InfoVista VistaFoundation 2 (VF2) suite of products to:

◆ Export topology from EMC Smarts IP Availability Managers to the InfoVista VF2 VistaDiscovery product.

◆ Provide access to InfoVista VF2 performance-related reports from an EMC Smarts Global Console.

◆ Map traps received from InfoVista VF2 to notifications for view in the Global Console.

The adapter imports topology from InfoVista and converts VF2 performance traps for display as notifications.


Introduction

Process flowsThis section describes process flows for importing topology from InfoVista VF2 and converting traps to notifications.

Topology process flow Figure 1 shows the topology process flow for InfoVista VF2. The adapter imports Layer 2 and Layer 3 physical and logical topology from the IP Availability Manager and then creates a file for export to the InfoVista VF2 VistaDiscovery product, which sends the data to the VistaMart product. The VistaMart product initiates data collection for reports on the imported topology elements. The file identifies the topology elements and the associated topology objects, EMC Smarts classes and relationships.

The InfoVista VF2 Adapter exports the following EMC Smarts classes to InfoVista VF2:

◆ Firewall

◆ Host

◆ Interface

◆ Router

◆ Switch

◆ Unitary Computer System

“InfoVista VF2 and EMC Smarts Classes” on page 43 provides a comparison of InfoVista VF2 and EMC Smarts classes.

Figure 1 InfoVista VF2 Adapter topology process flow

InfoVista VF2

VistaDiscovery

File

IP Availability Manager

Adapter for InfoVista VF2

InfoVista VF2

VistaMart

Topology

Process flows 11

Introduction

Conversion of InfoVista VF2 traps to notifications process flow Figure 2 shows the process flow for conversion of SNMP traps from an InfoVista VF2 server into notifications for display in the Global Console.

The SNMP Trap Adapter receives traps from the InfoVista VF2 server, and invokes an ASL hook script from the InfoVista VF2 Adapter to identify the topological element, the InfoVista VF2 report, and the source InfoVista VF2 server. The SNMP Trap Adapter creates notifications and reports and sends them to the Global Manager.

The adapter provides the Trap Adapter with client tools for configuring reports for display in the Global Console.

Figure 2 Conversion of traps to notifications process flow

Global ManagerAdapter for InfoVista VF2

Client Tools

InfoVista VF2 Server

Traps

SNMPTrap Adapter

Notifications

Global Console

Notifications

ASL HookscriptAdapter Platform


Introduction

Deployment configurationsInfoVista VF2 deployments may involve different configurations on several different hosts. Figure 3 shows an example deployment on five different systems (host computers):

◆ System 1 includes an EMC Smarts Broker; Service Management Suite elements, including the Global Manager, Adapter Platform, and SNMP Trap Adapter; and an InfoVista VF2 Adapter

◆ System 2 includes a Global Console and another InfoVista VF2 Adapter

◆ System 3 includes an IP Availability Manager

◆ System 4 includes an InfoVista VF2 Adapter and the InfoVista VF2 VistaDiscovery product

◆ System 5 includes two InfoVista VF2 servers and the InfoVista VF2 VistaMart product

Note: One instance of the InfoVista VF2 Adapter must be co-resident with the InfoVista VF2 VistaDiscovery product. Another instance of the adapter may optionally be co-resident with the Service Assurance Management products.

Deployment configurations 13

Introduction

Figure 3 Example InfoVista deployment

System 2

System 1

Broker

SNMP Trap Adapter

Service Assurance Adapter Platform

Server

Service Assurance Manager(Global Manager)

System 3

Topology and

Events to SAM

EMC Smarts InfoVista VF2

Adaptersm_ems Syslog

Adapter

SAM Adapter Platform

Notifications


Adapter

InfoVista VF2 VistaDiscovery

Availability Manager

Gets topology

Import and provisioninfo. from export

and XML files

Creates export file

InfoVista VF2 Server2

InfoVista VF2 Server1

InfoVista VF2 VistaMart

System 4

System 5

InfoVista VF2 TrapsReporting

data

Global Console

Notifications

Discovery and reporting data


Adapter

Uses hook script to identify trap


Introduction

Display of InfoVista VF2 reports from the Global ConsoleThe InfoVista VF2 Adapter supports display of trap and performance-related InfoVista VF2 reports in a Global Console. The following reports are available:

◆ Trap reports (available for traps received from InfoVista VF2)

◆ Performance reports (include trend analysis and performance statistics)

◆ TroubleShooter reports (rapid analysis and diagnosis of performance problems)

At the Global Console, you can request creation of a report, request access to related reports, or view reports you have already created.

How client tools retrieve reportsWhen you right-click a notification, map icon, or topology browser object from the Client Tools menu in the Global Console, the tool launches a web browser.

The following types of reports are available when you select:

◆ A client tool for a notification that originated as an InfoVista VF2 trap, the client tool formats the information into an InfoVista VF2 Portal SE Reporting URL for the topological object or notification and launches a browser for viewing the report.

◆ The List Performance Reports tool, the client tool launches a server-based script on the Global Manager. This script invokes an SQL query against the InfoVista VF2 VistaMart product. The Global Manager returns the report URL for viewing in a browser.

◆ VTS: Create Report, VTS: Access Related Reports or VTS: View My Reports, the client tool formats the Portal SE URL for the appropriate report and opens the browser with that URL.

Display of InfoVista VF2 reports from the Global Console 15

Introduction


2

This chapter explains how to configure the InfoVista VF2 Adapter deployment. It contains the following information:

◆ Prerequisites.................................................................................................................... 18◆ Modifying EMC Smarts configuration files ............................................................... 19◆ Location of InfoVista VF2 Adapter configuration files............................................. 20◆ Summary of configuration tasks.................................................................................. 21◆ Configuring the adapter................................................................................................ 22◆ Configuring the IP Availability Manager ................................................................... 24◆ Configuring the Global Manager................................................................................. 25◆ Configuring the Global Console .................................................................................. 28◆ Configuring the Adapter Platform .............................................................................. 31◆ Verifying the installation ............................................................................................... 32◆ Automating topology export........................................................................................ 34◆ Configuring Report Communications on the InfoVista Server ............................... 37

Configuring theAdapter Deployment

Configuring the Adapter Deployment 17

Configuring the Adapter Deployment

PrerequisitesTo deploy and configure the adapter, you should be familiar with InfoVista VF2.

The following software should be installed before you configure the adapter:

◆ InfoVista VistaFoundation 2 software. The InfoVista documentation includes complete requirements.

◆ The EMC Smarts Adapter for InfoVista VF2. The EMC Smarts SAM Adapters Suite and Report Manager Installation Guide includes detailed installation information.

◆ Other required EMC Smarts applications:

• EMC Smarts Global Console, EMC Smarts Global Manager, and EMC Smarts Service Assurance Manager Adapter Platform. The EMC Smarts Service Assurance Management Suite Installation Guide provides detailed information about installing these EMC Smarts products.

• EMC Smarts IP Availability Manager. The EMC Smarts IP Management Suite Installation Guide provides detailed information about installing the Availability Manager.



Modifying EMC Smarts configuration filesTo edit EMC Smarts configuration files, use the EMC Smarts sm_edit utility. For example, to open and modify the default infovista2.conf file on UNIX, use the following command from BASEDIR/smarts/bin:

# ./sm_edit conf/infovista2/infovista2.conf

“Understanding the sm_edit Utility” on page 51 provides information about the sm_edit utility.

Note: In this guide, the BASEDIR varies according to the EMC Smarts product being configured. Each section indicates the relevant BASEDIR.

Modifying EMC Smarts configuration files 19


Location of InfoVista VF2 Adapter configuration filesThe original configuration files for the InfoVista VF2 Adapter deployment are installed into the locations listed in Table 1.

Table 1 Configuration files for the InfoVista VF2 Adapter

EMC Smarts product

EMC Smarts directory (below BASEDIR/smarts/

EMC Smarts configuration file(s) Description

InfoVista VF2 Adapter (must be co-resident with VistaDiscovery)

conf clientConnect.conf The client security configuration file, used to provide authentication information to the Availability Manager. Modify this file for the InfoVista VF2 Adapter that resides with the InfoVista VF2 VistaDiscovery product.

conf/infovista2 infovista2.conf Configuration file for the InfoVista VF2 Adapter.

conf/infovista2 sched.conf Default control file, sched.conf. Used with the sm_sched utility to automate the topology transfer process.

script/server/infovista2 runExportImport A sample script that can be used to automate the transfer of topology between EMC Smarts and InfoVista VF2 when used with a scheduling utility like sm_sched.

EMC Smarts Service Assurance Manager (Global Manager)

conf/ics configureInfoVistaTools2.xml XML definition of InfoVista VF2 tools used by the Global Manager. Import this file using the sm_config command to configure the client tools related to the InfoVista VF2 Adapter.

conf/infovista2 infovista2.properties Properties file for the VistaMart Oracle database and identifies the Portal SE Server used for reporting.

actions/server/infovista2 getDataForReport A script that creates a JVM and launches a JAVA program. The script contains the ORA_JAR_LOCATION variable.

EMC Smarts Service Assurance Manager Adapter Platform

conf/icoi trap_mgr.infovista2.conftrap_mgr.conf

The trap_mgr.infovista2.conf file is used to define and map incoming InfoVista VF2 traps to Service Assurance notifications. The content must be appended to the trap_mgr.conf file.

EMC Smarts IP Availability Manager

conf serverConnect.conf The server security configuration file, used to validate connections.

EMC Smarts Global Console(s)

actions/client/infovista2 viewTrapReportshowVistaReportvtsCreateReportvtsAccessRelatedReportvtsViewMyReport

Client tool scripts for retrieving reports from the InfoVista VF2 Server. Client tools are invoked from the Global Console by an operator.



Summary of configuration tasksTo configure the InfoVista VF2 Adapter:

1. “Configuring the adapter” on page 22

2. “Configuring the IP Availability Manager” on page 24

3. “Configuring the Global Manager” on page 25

4. “Configuring the Global Console” on page 28

5. “Configuring the Adapter Platform” on page 31

6. “Verifying the installation” on page 32

7. “Automating topology export” on page 34

8. “Configuring Report Communications on the InfoVista Server” on page 37

Summary of configuration tasks 21


Configuring the adapterAt the host where the InfoVista VF2 Adapter is installed with the InfoVista VF2 VistaDiscovery product, do the following tasks:

◆ Change the configuration parameters in the infovista2.conf file to match the names of your Global Manager and Availability Manager, as described in “Configuring adapter configuration parameters” on page 22.

◆ Configure the client security configuration file for topology transfer from the Availability Manager(s), as described in “Configuring adapter security” on page 23.

Configuring adapter configuration parametersFor the InfoVista VF2 Adapter that is co-resident with the InfoVista VF2 VistaDiscovery product, edit the infovista2.conf file to reflect your deployment.

The configuration parameters for the InfoVista VF2 Adapter are specified in the infovista2.conf file, located in the BASEDIR/smarts/conf/infovista2 directory. Table 2 lists the configuration parameters of infovista2.conf file.

Use the sm_edit utility to modify this file; for example, at BASEDIR/smarts/conf/infovista2, issue the following command:

# ./sm_edit conf/infovista2/infovista2.conf

Note: After you modify the infovista2.conf file, you do not start the InfoVista VF2 Adapter with the sm_service command; no service is available for this adapter.

Table 2 Configuration parameters for the InfoVista VF2 Adapter

Variable Default value Description

SAM_SERVER_NAME INCHARGE-SA Defines the name of the EMC Smarts Service Assurance Manager (Global Manager).

DOMAIN_MANAGER_NAMES INCHARGE-AM Defines the names of the IP Availability Managers from which topology objects will be exported.

EXPORT_FILE_NAME iv2input.txt Defines the export file created with EMC Smarts Availability Manager(s) topology, used in conjunction with the iv2command.xml file when importing data to InfoVista VF2 product suite. By default, the export file is written to the BASEDIR/smarts/local/conf/infovista2 directory.



Configuring adapter securityThe security configuration files, clientConnect.conf and serverConnect.conf, allow you to set up secure connections between the components in a deployment. By default, the configuration option settings in the clientConnect.conf file and the serverConnect.conf file allows minimally secure connections between the components.

Note: When creating new users, the serverConnect.conf file and the clientConnect.conf file must be modified to authenticate them with usernames and passwords. The InCharge System Administration Guide provides additional information on modifying these files.

You configure the clientConnect.conf file on the host where the adapter is co-resident with the InfoVista VF2 VistaDiscovery product. In the clientConnect.conf file, you create a entry for the system user ID running the InfoVista VF2 Adapter with a corresponding EMC Smarts username and password. For example:

infovista2 : INCHARGE-AM : admin : changeme

where:

◆ infovista2 is the system user ID running the InfoVista VF2 Adapter.

◆ INCHARGE-AM is the Availability Manager name.

◆ admin is the EMC Smarts login username.

◆ changeme is the EMC Smarts login password.

Configuring the adapter 23


Configuring the IP Availability ManagerTo configure the IP Availability Manager for your deployment, configure the serverConnect.conf file.

Note: BASEDIR for the IP Availability Manager is opt/InCharge6/IP/.

Configuring the serverConnect.conf fileYou configure the serverConnect.conf file on the Availability Manager to support communications with the InfoVista VF2 Adapter.

The entry must correspond to the EMC Smarts username and password specified in the clientConnect.conf file for the system user ID running the InfoVista VF2 Adapter. The EMC Smarts user must be given All privileges. For example,

INCHARGE-AM : admin : changeme : ALL

where:

◆ INCHARGE-AM is the Availability Manager name.

Note: Use an * to indicate all managers.

◆ admin is the EMC Smarts login username.

◆ changeme is the EMC Smarts login password.

◆ ALL is the privileges granted this user.

The EMC Smarts System Administration Guide provides additional information about security configurations.



Configuring the Global ManagerTo configure the Global Manager for your deployment:

◆ Import the configureInfoVistaTools2.xml file to the Global Manager, as described in “Importing the configureInfoVistaTools2.xml file” on page 25.

◆ Configure the value for the ORA_JAR_LOCATION variable, as described in “Configuring the JAR file variable” on page 25.

◆ Specify settings in the infovista2.properties file for the VistaMart Oracle database and the Portal SE Server used for reporting, as described in “Editing the infovista2.properties file” on page 26.

Note: BASEDIR for the Global Manager is opt/InCharge6/SAM/.

Importing the configureInfoVistaTools2.xml fileConfigure the Global Manager by importing an XML definition file of InfoVista VF2 client tolls from the adapter.

To import the configureInfoVistaTools2.xml file to the Global Manager, invoke the sm_config command from the BASEDIR/smarts/bin directory. For example:

▼# ./sm_config -s <global_manager> import --force configureInfoVistaTools2.xml▲

Note: ▼ ▲ Indicates that the command must be typed as one line.

The EMC Smarts Service Assurance Manager Configuration Guide provides details about importing XML files to the Global Manager.

Configuring the JAR file variableModify the ORA_JAR_LOCATION variable in the getDataForReport.sh file (for UNIX) and the getDataForReport.cmd file (for Windows) setting to match your deployment. The ORA_JAR_LOCATION variable defines the location of the JAR file that supports execution of SQL commands to the InfoVista VF2 VistaMart Oracle database. These commands are used by the sm_iv2java program. Before configuring the JAR file setting, you may find it helpful to read the “Background information about the JAR file” on page 26.

Configuring the JAR fileAt BASEDIR/smarts/bin, issue the following command:

For UNIX:

# ./sm_edit actions/server/infovista2/getDataForReport.sh

For Windows:

# ./sm_edit actions/server/infovista2/getDataForReport.cmd

Configuring the Global Manager 25


Table 3 lists the default values for this setting.

Background information about the JAR fileWhen you select an InfoVista VF2 Performance Reports request:

◆ The client shell script calls to the Global Manager to run the getDataForReport.asl script.

◆ The getDataForReport.asl script, in turn, runs the script command found in the BASEDIR/smarts/actions/server/infovista2/getDataForReport file.

◆ The getDataForReport.asl script runs the BASEDIR/smarts/bin/sm_iv2java program which in turn creates a JVM and launches a JAVA program labeled com.smarts.infovista2.QueryVistaMart.

◆ The --jar parameter in the getDataForReport file identifies which JAR files are needed by the sm_iv2java program to support running the com.smarts.infovista2.QueryVistaMart.class file.

◆ The JAVA com.smarts.infovista2.QueryVistaMart program uses an ojdbc14.jar file to support execution of SQL commands to the InfoVista VF2 VistaMart Oracle database.

◆ The ORA_JAR_LOCATION specifies the full path and name of the ojdbc14.jar in the getDataForReport file.

Note: The ojdbc14.jar file is installed with the InfoVista VF2 VistaMart product suite under a subdirectory labeled “oracle”. If the Global Manager does not reside on the host with the InfoVista VF2 VistaMart installation, the ojdbc14.jar file must be copied to or made available to the Global Manager. If the ojdbc14.jar file is copied to the BASEDIR/smarts/classes directory of the Global Manager, the ORA_JAR_LOCATION may be assigned BASEDIR/smarts/local/classes/ojdbc14.jar on UNIX and BASEDIR\smarts\local\classes\ojdbc14.jar on Windows.

Editing the infovista2.properties fileThe infovista2.properties file contains the property settings for the VistaMart Oracle database and identifies the Portal SE Server used for reporting. The JAVA com.smarts.infovista2.QueryVistaMart program loads the infovista2.properties file to obtain the InfoVista VF2 VistaMart Oracle database driver parameters. The Portal SE server that is used to return performance reports is also designated in the file.

You modify the settings listed in Table 4 to match your configuration. Use the sm_edit utility to modify the infovista2.properties file.

At e BASEDIR/smarts/bin, issue the following command:

# ./sm_edit /smarts/conf/infovista2/infovista2.properties

In the infovista2.properties file, modify the following sections:

Table 3 Default values for ORA_JAR_LOCATION variable

Variable name Default value (if different) Description

ORA_JAR_LOCATION UNIX:/opt/InfoVista/VistaMart/oracle/ojdbc14.jar

Windows:C:\Program Files\InfoVista\VistaMart\oracle\ojdbc14.jar

Full path name to InfoVista VF2 VistaMart Oracle JDBC jar.



# ---- BEGIN - ORACLE driver connection propertiesiv.dbUsername=scottiv.dbPassword=tigeriv.dbHost=oracle.domain.comiv.dbSid=orasidiv.dbPort=1521# ---- END - ORACLE driver connection properties

# --- BEGIN - InfoVista PortalSE propertiesiv.ivPortalSEHost = iv.domain.comiv.ivPortalSEPort = 80iv.subdir=online# ----- END - InfoVista PortalSE properties

Table 4 lists default settings for the VistaMart Oracle database properties and Portal SE Server.

Table 4 Properties for the VistaMart Oracle database and Portal SE Server

Property name Default value Description

iv.dbUsername scott Defines the InfoVista VF2 VistaMart Oracle username.

iv.dbPassword tiger Defines the InfoVista VF2 VistaMart Oracle password.

iv.dbHost oracle.domain.com Defines the InfoVista VF2 VistaMart Oracle host.

iv.dbSid orasid Defines the InfoVista VF2 VistaMart Oracle SID.

iv.dbPort 1521 Defines the InfoVista VF2 VistaMart Oracle listener port.

iv.ivPortalSEHost iv.domain.com Defines the InfoVista VF2 Portal SE host.

iv.ivPortalSEPort 80 Defines the InfoVista VF2 Portal SE port.

iv.subdir online Defines the InfoVista VF2 Portal SE subdirectory.

Configuring the Global Manager 27


Configuring the Global ConsoleEdit the client tools files to match your browser and InfoVista VF2 configurations, as described in “Editing the client tool files” on page 28.

Note: BASEDIR for the Global Console is opt/InCharge6/SAM/.

Editing the client tool files

Client tools are invoked on the host where the Global Console is running, so the associated tool scripts must be installed on that host. The tool scripts are located in the BASEDIR/smarts/actions/client/infovista2 directory.

Table 5 lists the client tools and their associated script names.

Note: On UNIX, some of the files end with the extension .sh. On Windows, the files end with the extension .cmd.

Editing the client tool scripts

For each Global Console, edit the client tool scripts to reflect your configuration.

At BASEDIR/smarts/bin, issue the following command:

# ./sm_edit actions/client/infovista2/showVistaReport.sh

Table 6, Table 7, and Table 8 list the parameters that you can set for each script.

Table 5 Client tools script names

Client tool name (menu display name) Script name (.sh/.cmd)

IV2: Trap Report

Note: Only available for InfoVista VF2-received traps.

viewTrapReport

IV2: List Performance Reports showVistaReport

VTS: Create Report vtsCreateReport

VTS: Access Related Reports vtsAccessRelatedReport

VTS: View My Reports vtsViewMyReport



showVistaReport script

ViewTrapReport script

Table 6 Configuration parameters for showVistaReport script

Variable name Default value Description

BROWSER UNIX:/opt/misc/netscape/netscape-4.79-28/netscape

Windows:C:\Program Files\Internet Explorer\IEXPLORE.EXE

Set to the Global Console client's Internet browser location.

Table 7 Configuration parameters for viewTrapReport script


VPSE_HOSTNAME UNIX: localhostWindows: (no default)

Vista Portal SE Host

VPSE_WEB_PORT UNIX: 80Windows: (no default)

Vista Portal SE Port

VPSE_LOGIN (no default) Vista Portal SE User Login

VPSE_PASSWORD (no default) Vista Portal SE Password

IV_SERVER_SUBDIRECTORY UNIX: smartsWindows: (no default)

Vista Portal SE Subdirectory


Windows:C:\Program Files\Internet Explorer\IEXPLORE.EXE

Set to the Global Console client's Internet browser location

Configuring the Global Console 29


vtsCreateReport, vtsAccessRelatedReports, and vtsViewMyReports scripts

The EMC Smarts Service Assurance Manager Configuration Guide provides additional client tools information.

Table 8 Configuration parameters for vtsCreateReport, vtsAccessRelatedReports, and vtsViewMyReports scripts


VPSE_HOSTNAME UNIX: localhostWindows: (no default)

Vista Portal SE Host

VPSE_WEB_PORT UNIX: 80Windows: (no default)

Vista Portal SE Port

VPSE_LOGIN UNIX: smartsWindows: (no default)

Vista Portal SE User Login

VPSE_PASSWORD UNIX: changemeWindows: (no default)

Vista Portal SE Password


Windows: C:\Program Files\Internet Explorer\IEXPLORE.EXE

Set to the Global Console client's Internet browser location.



Configuring the Adapter PlatformConfigure the SNMP Trap Adapter of the Adapter Platform to support traps processing.

In addition to using the InfoVista VF2 Adapter’s infovista2Trap.asl script, as described in “Conversion of InfoVista VF2 traps to notifications process flow” on page 12, the SNMP Trap Adapter uses its own trap_mgr.conf file to translate the incoming traps into Service Assurance notifications. In order for the SNMP Trap Adapter to translate InfoVista VF2 traps, you must modify the trap_mgr.conf file.

Note: BASEDIR for the Adapter Platform is opt/InCharge6/SAM/.

Modifying the trap_mgr.conf fileOn the host where the EMC Smarts Adapter Platform is installed, append the content of the trap_mgr.infovista2.conf file to the trap_mgr.conf file. Both files are located in the BASEDIR/smarts/conf/icoi directory.

1. At BASEDIR/smarts/bin, issue the following command:

# ./sm_edit /smarts/conf/icoi/trap_mgr.infovista2.conf

2. Open the SNMP Trap Adapter’s trap_mgr.conf file.

# ./sm_edit /smarts/conf/icoi/trap_mgr.conf

3. Copy the contents of the trap_mgr.infovista2.conf file to the end of the trap_mgr.conf file.

4. Save and close the files.

The SNMP Trap Adapter parses the InfoVista VF2 trap. The trap components are translated into a notification of the following format:

# EventName:$V2$|InfoVista|$V5$|$V7$|$SYS$|$V11$|$V10$|$V12$

Table 9 shows how the InfoVista VF2 trap components are mapped to notifications.

The EMC Smarts Service Assurance Manager Adapter Platform User Guide provides additional information about the SNMP Trap Adapter and trap processing.

Table 9 Parsed trap data

InfoVista VF2 trap componentService Assurance notification mapping

INSTANCE_NAME $V2$

IV_NOTIF_TAG InfoVista

INSTANCE_ID $V5$

REPORT_TEMPLATE_WID $V7$

IV_SERVER $SYS$

M_PORT $V11$

C_PORT $V10$

B_PORT $V12$

Configuring the Adapter Platform 31


Verifying the installationYou should manually verify the adapter installation to ensure that it is processing data correctly. To verify the installation:

◆ Run the sm_infovista2 command to manually create an export file and verify the adapter’s configuration, as described in “Configuring the Global Console” on page 28.

◆ Run the InfoVista VF2 VistaDiscovery user interface or the InfoVista VF2 launchserver.cmd tool to import the export file, as described in “Manually importing topology into the InfoVista VF2 server” on page 33.

Perform these tasks to verify the adapter’s configuration before you configure the automated scheduling process for topology transfer, as described in “Manually importing topology into the InfoVista VF2 server” on page 33.

Manually exporting topologyOn the host where the InfoVista VF2 Adapter resides with the InfoVista VF2 VistaDiscovery product, invoke the sm_infovista2 command to start the InfoVista VF2 Adapter and export the topology from the Availability Managers. The topology is saved in the export file as defined in the infovista2.conf file. After the adapter exports the topology, it exits.

The sm_infovista2 command uses the following syntax:

# BASEDIR/smarts/bin> sm_infovista2 [options ...]

The options in Table 10 are available for the sm_infovista2 command.

For example, on UNIX, you can issue the sm_infovista2 command with a new value for the Domain Manager. The command also records important information to its log file.

▼# /opt/InCharge6/SAM/smarts/bin> sm_infovista2 -D DOMAIN_MANAGER_NAME=INCHARGE-AM5 --output ▲

Note: After you create the export file, you can either import the exported topology into the VistaDiscovery server manually, using the VistaDiscovery user interface, or automate the complete topology transfer by using the sm_sched utility and the runExportImport script.

Table 10 sm_infovista2 options

Option Description

--broker=<location> Alternate EMC Smarts broker location as <host>:<port>.

--output[=<file>] Redirect output (stdout and stderr). The file name is <file>. If a file name is omitted, the default name is infovista2.log. The log file is placed in the BASEDIR/smarts/local/logs directory.

-D config_param=value config_param=value

The -D option enables you to specify values for the configuration parameters described in Table 2 from the command line. When specified with the -D option, the values overwrite the values that exist in the infovista2.conf file.One space is required after -D and to separate multiple parameter-value pairs.



Manually importing topology into the InfoVista VF2 serverAs a part of the verification process, you manually import the file you have just created into the VistaDiscovery server for distribution to other InfoVista VF2 servers through the VistaMart provisioning framework. To do so manually, invoke the InfoVista VF2 launchserver.cmd tool. The InfoVista VF2 VistaDiscovery User’s Guide provides detailed information.

Verifying the installation 33


Automating topology exportOnce your verification is complete, you can automate the topology transfer process on the InfoVista VF2 Adapter that resides with the InfoVista VF2 VistaDiscovery product. You can:

◆ Edit the runExportImport script to modify its parameters, as described in “Editing the runExportImport script” on page 34.

◆ Edit the control file, sched.conf, to set the time interval and to specify the runExportImport script, as described in “Editing the sm_sched utility” on page 35.

◆ Run the sm_sched utility to schedule the runExportImport script to run at a specific interval, as described in “Running the sm_sched utility” on page 36.

Editing the runExportImport scriptThe runExportImport script is located in the BASEDIR/smarts/script/server/infovista2 directory. For UNIX, the file is runExportImport.sh and, for Windows, the file is runExportImport.cmd.

Before using the runExportImport script, edit the values for the parameters in Table 11 to match your configuration.

To open and modify the default runExportImport.sh file on UNIX, issue the following command form BASEDIR/SMARTS/bin:

# ./sm_edit script/server/infovista2/runExportImport.sh

Table 11 Configuration parameters for the runExportImport script

Variable Default value Description

IV2_DIR UNIX: /opt/InfoVista/VistaDiscoveryWindows: C:\Program Files\InfoVista\VistaDiscovery

Defines the root directory of InfoVista VF2 VistaDiscovery product installation.

INCHARGE_DIR UNIX: /opt/InCharge6/SAM/smartsWindows: C:\InCharge\SAM\smarts

Defines the root directory of InfoVista VF2 Adapter installation.

IVM_USER UNIX: administratorWindows: (no default)

Defines the InfoVista VF2 VistaMart username.

IVM_PWD (no default) Defines the InfoVista VF2 VistaMart password.

IVM_ORAHOST (no default) Defines the InfoVista VF2 VistaMart Oracle host.

IVM_ORAPORT (no default) Defines the InfoVista VF2 VistaMart Oracle port.

IVM_ORASID (no default) Defines the InfoVista VF2 VistaMart Oracle SID.

IVM_ZONE UNIX: DefaultWindows: (no default)

Defines the InfoVista VF2 VistaMart zone.



Editing the sm_sched utilityThe sm_sched utility uses a control file to store configuration options and settings for the scheduled events. For the InfoVista VF2 Adapter, sm_sched reads the control file, sched.conf, located in the BASEDIR/smarts/conf/infovista2 directory. The sm_sched utility runs all of the jobs listed in the control file beginning two minutes from the time it is issued and repeats the jobs at the interval times specified. Up to 20 jobs may be performed simultaneously; if you have more than 20 jobs, the additional jobs are queued until the others are completed.

ProcedureAt BASEDIR/smarts/bin, issue the following command:

# ./sm_edit conf/infovista2/sched.conf

The sched.conf file lists a number of jobs, or tasks, to be performed when the control file is called by the sm_sched utility. A job is a line that consists of two items: a time interval and a command. Each job is on an individual line within the control file using the following syntax:

<time interval> <command>

A line beginning with whitespace or the # character is treated as a comment line and is ignored by the utility.

The time interval has the syntax of hh:mm:ss and represents the interval of time that needs to elapse (the hours, minutes, and seconds) before the job is run. For example, “24:00:00”, represents an interval of twenty-four hours. An empty field has a value of zero so “24::” also represents 24 hours.

Note: On UNIX systems, cron is usually used to schedule commands. If you desire, use cron to schedule the runExportImport script following the guidelines in this section.

After the time interval, add the runExportImport script to the sched.conf file. The script will be issued at a UNIX or Windows command prompt.

For example, to run the runExportImport script at the interval of every 30 minutes, add the following as one line to the sched.conf file:

◆ For UNIX, add:

00:30:00 BASEDIR/smarts/local/script/server/tsinfovista2/runExportImport.sh

◆ For Windows, add:

00:30:00 BASEDIR\smarts\local\script\server\tsinfovista2\runExportImport.cmd

Automating topology export 35


Running the sm_sched utilityAt BASEDIR/smarts/bin, issue the following command:

% ./sm_sched BASEDIR/smarts/local/conf/infovista2/sched.conf

The syntax for running the sm_sched utility is as follows:

sm_sched [options...]s sBASEDIR/smarts/local/conf/infovista2/<control-file>

Where <control-file> is sched.conf or the file name of the file listing the jobs you want executed.

For the InfoVista VF2 Adapter, you must specify the path, BASEDIR/smarts/local/conf/infovista2. If you do not specify a path and a file name, it is assumed you want to use the default control file, sched.conf, located in the BASEDIR/smarts/local/conf directory.

The available options are listed in Table 12.

Results from the sm_sched utilityJobs listed in the control file are expected to execute without feedback. Should there be any output from the job commands, it is written to a log file labeled sm_sched.log located in BASEDIR/smarts/local/logs directory. Items logged by the sm_sched utility are done so with a Warning severity.

Since the purpose of the sm_sched utility is to continuously schedule jobs, it normally does not exit. Table 13 lists two conditions that would cause the sm_sched utility to exit (and return an exit value).

Table 12 Command-line options for the sm_sched utility

Option DescriptionDefault value

--maxjobs=<n> Defines the maximum number of jobs to be run simultaneously. Additional jobs listed in the control file are queued until one of the currently running jobs finishes.

20

--retries=<n> Defines the number of retries to attempt for each job. The job is canceled after <n> consecutive failures and no further attempt is made. If <n> is 0, then there is no limit to the number of retries.

3

--maxfails=<n> Defines the failure limit. The job is canceled after <n> failures. If <n> is 0, then there is no limit on the number of failures allowed.

100

Table 13 sm_sched exit return codes

Return code value Description

0 The utility has no further jobs to run.

non-zero A problem occurred, preventing the utility from starting up or the utility could not find a file that was scheduled to run.


Configuring Report Communications on the InfoVista ServerConfigure the InfoVista server to support the following reports:

◆ Trap

◆ TroubleShooter

Configuring Communications for Trap reportsTo configure the InfoVista server to send Trap reports:

1. On the InfoVista server, go to ${PortalSeHome}/controls/portalsesetup.xml.

2. Enter the following lines:

<SubDirectory name="smarts"><Formats>html,png,pdf,explain</Formats><History>3</History><AutoRefresh mode="mixed" requestloginifneeded="false"></AutoRefresh></SubDirectory>

3. Go to ${PortalSeHome}/controls/security.policy.

4. Locate the following lines and then enter the login name for the variable, <smartsAdapterUser >.

permission com.infovista.portalse.security.UsersPermission"smarts", <"smartsAdapterUser">;

Note: To ensure that SNMP traps are correctly processed, the Report ID or WID must be sent in VARBIND7.

Configuring Report Communications on the InfoVista Server 37


Configuring Communications for Vista TroubleShooter (VTS) reportsTo configure the InfoVista server to send TroubleShooter reports:

1. On the InfoVista server, go to /opt/InfoVista/PortalSE/controls/portalsesetup.xml.

2. Locate the following section, and enter appropriate values for the [CDATA] variables listed in Table 14.

<SubDirectory name="smarts"><Formats>html,png,pdf,explain</Formats><History>3</History><IncludeSubDirectories></IncludeSubDirectories><AutoRefresh mode="online" requestloginifneeded="true"><ServerLogins><ServerLogin><Server><![C[Server name where portal is running]]></Server> EndPoints Info<User><![CDATA[administrator]]></User><Password><![CDATA[Password]]></Password></ServerLogin></ServerLogins></AutoRefresh></SubDirectory>

InfoVista login variablesTable 14 defines InfoVista login variables.

Table 14 InfoVista login variables

Variable Description Example

[Server name where portal is running] Defines the VTS Portal SE is the server name where the Portal is running.

[VTS PortalSE:3000:3001:3002]

Note: 3000, 3001, 3002 are the Infovista End points information.

[Administrator] Defines user ID for the InfoVista administrator.

[administrator]

[Password] Defines the administrator Password. [password]


3

Once the InfoVista VF2 Adapter is installed and configured, you can view InfoVista VF2 reports and notifications in the Global Console. Reports are available for topology objects that have been exported from EMC Smarts to InfoVista VF2 and for any notifications that relate to these objects.

Note: As with any tool, the EMC Smarts Global Manager administrator can permit or deny access to these tools by any user.

This chapter contains the following information:

◆ Viewing an InfoVista VF2 report.................................................................................. 40◆ Viewing and responding to notifications.................................................................... 41

Using the GlobalConsole

Using the Global Console 39

Using the Global Console

Viewing an InfoVista VF2 reportTo invoke any InfoVista VF2 Report client tool:

1. Select and right-click one of the following:

• A notification in the Notification Log Console

• A map icon in the Map Console

• A managed object in the topology tree of the Topology Browser Console

2. From the pop-up menu, select Client Tools and then one of the following InfoVista VF2 reports:

• IV2: Trap Report


• IV2: List Performance Reports

• VTS: Create Report

• VTS: Access Related Reports

• VTS: View My Reports

A browser window opens, displaying the report you selected. If a report is not available, a message indicates that the report is not available.

Table 15 lists the available reports and associated scripts.

Table 15 Client tools and corresponding script names

Client tool menu display name Script name (.sh/.cmd)

IV2: Trap Report


viewTrapReport

IV2: List Performance Reports showVistaReport

VTS: Create Report vtsCreateReport

VTS: Access Related Reports vtsAccessRelatedReport

VTS: View My Reports vtsViewMyReport



Viewing and responding to notificationsYou can use the Global Console to view and respond to notifications that originate from InfoVista VF2. You can acknowledge, own, and escalate these notifications. In addition, you can invoke InfoVista-related client tools on the notifications.

Note: Do not run Performance Reports from InfoVista Trap notifications.

The EMC Smarts Service Assurance Manager Operator Guide provides complete information about responding to notifications and using the Global Console.

Viewing and responding to notifications 41

A

Table 16 lists the EMC Smarts classes which can be exported by the InfoVista VF2 Adapter, their corresponding InfoVista VF2 classes (called “Vistas”), and whether the EMC Smarts classes are imported by default by the VistaDiscovery product.

InfoVista VF2 and EMCSmarts Classes

Table 16 InfoVista VF2 classes and corresponding EMC Smarts classes

Vista name EMC Smarts class (for export) Imported by default?

Router Firewall Yes

Router Router Yes

LAN Switch Switch Yes

ATM Switch Switch Yes

Server Host Yes

SNMP Node Unitary Computer System Yes

WAN Interface Interface Yes

LAN Interface Interface Yes

Resource Group Service Offering No

Note: The InfoVista VF2 VistaDiscovery Custom Integration documentation provides additional information.

InfoVista VF2 and EMC Smarts Classes 43

InfoVista VF2 and EMC Smarts Classes


B

This appendix includes the following information:

◆ SAM Adapters Suite and Report Manager installation directory........................... 46◆ EMC Smarts SAM Adapters Suite and Report Manager products......................... 47◆ EMC Smarts SAM Adapters Suite and Report Manager documentation.............. 48◆ Related documentation ................................................................................................. 49

Related Information

Related Information 45

Related Information

SAM Adapters Suite and Report Manager installation directoryIn this document, the term BASEDIR represents the location where EMC Smarts software is installed.

◆ For UNIX, this location is: /opt/InCharge<n>/<productsuite>.

◆ For Windows, this location is: C:\InCharge<n>\<productsuite>.

The <n> represents the software platform version number. The <productsuite> represents the EMC Smarts product suite to which the product belongs. For example, on UNIX operating systems, the EMC Smarts SAM Adapters Suite and Report Manager is, by default, installed to /opt/InCharge7/SAM.Adapters/smarts. On Windows operating systems, this product is, by default, installed to: C:\InCharge7\SAM.Adapters\smarts. This location is referred to as BASEDIR/smarts.

Optionally, you can specify the root of BASEDIR to be something other than /opt/InCharge7 (on UNIX) or C:\InCharge7 (on Windows), but you cannot change the <productsuite> location under the root directory.

For more information about the directory structure of EMC Smarts software, refer to the EMC Smarts System Administration Guide.


Related Information

EMC Smarts SAM Adapters Suite and Report Manager productsThe SAM Adapters Suite and Report Manager offers the following products:

◆ EMC Smarts Adapter for BMC Patrol

◆ EMC Smarts Adapter for Concord eHealth

◆ EMC Smarts Adapter for HP-OVO/U

◆ EMC Smarts Adapter for InfoVista VF2

◆ EMC Smarts Adapter for Microsoft Operations Manager 2005

◆ EMC Smarts Adapter for Microsoft System Center Operations Manager 2007

◆ EMC Smarts Adapter for NetIQ AppManager

◆ EMC Smarts Adapter for Remedy ARS

◆ EMC Smarts SQL Data Interface Adapter

◆ EMC Smarts Adapter for SiteScope

◆ EMC Smarts Report Manager

EMC Smarts SAM Adapters Suite and Report Manager products 47

Related Information

EMC Smarts SAM Adapters Suite and Report Manager documentationThe following documents are relevant to the SAM Adapters Suite and Report Manager:

◆ EMC Smarts Adapter for BMC Patrol User Guide

◆ EMC Smarts Adapter for Concord eHealth User Guide

◆ EMC Smarts Adapter for HP-OVO/U User Guide

◆ EMC Smarts Adapter for InfoVista VF2 User Guide

◆ EMC Smarts Adapter for Microsoft Operations Manager User Guide

◆ EMC Smarts Adapter for System Center Operations Manager 2007 User Guide

◆ EMC Smarts Adapter for NetIQ AppManager User Guide

◆ EMC Smarts Adapter for Remedy ARS User Guide

◆ EMC Smarts SQL Data Interface Adapter User Guide

◆ EMC Smarts Adapter for SiteScope User Guide

◆ EMC Smarts Report Manager User Guide

◆ EMC Smarts SAM Adapters Suite and Report Manager Installation Guide

◆ EMC Smarts Adapters Event-to-Notification Tutorial

EMC Smarts Service Assurance Management SuiteThe following documents are relevant to users of the EMC Smarts Service Assurance Management Suite:

◆ EMC Smarts Service Assurance Manager Introduction

◆ EMC Smarts Service Assurance Management Suite Deployment Guide

◆ EMC Smarts Service Assurance Management Suite Installation Guide

◆ EMC Smarts Service Assurance Manager Operator Guide

◆ EMC Smarts Service Assurance Manager Configuration Guide

◆ EMC Smarts Service Assurance Manager Dashboard Configuration Guide

◆ EMC Smarts Business Impact Manager User Guide

◆ EMC Smarts Report Manager User Guide

◆ EMC Smarts Service Assurance Manager Failover System User Guide

◆ EMC Smarts Service Assurance Manager Adapter Platform User Guide

◆ EMC Smarts Service Assurance Manager Notification Adapters User Guide

◆ EMC Smarts XML Adapter User Guide

Refer to the EMC Smarts Documentation Catalog for documentation resources provided with other EMC Smarts product suites.


Related Information

Related documentationIn addition to this document, EMC Corporation provides a Help system for command line programs as well as product documentation.

Help for command line programsDescriptions of command line programs are available as HTML pages. The index.html file, which provides an index to the various commands, is located in the BASEDIR/smarts/doc/html/usage directory.

EMC Smarts documentationReaders of this guide may find the following related documentation helpful. It can be found in the BASEDIR/smarts/doc/pdf directory:

Note: These documents are updated periodically. Electronic versions of the updated manuals are available on the Powerlink website:http://Powerlink.EMC.com.

◆ EMC Smarts Documentation Catalog

◆ EMC Smarts System Administration Guide

◆ EMC Smarts ICIM Reference

◆ EMC Smarts Common Information Model Infrastructure Models Chart

◆ EMC Smarts Common Information Model Application⁄Business Models Chart

◆ EMC Smarts ASL Reference Guide

◆ EMC Smarts Perl Reference Guide

Suggestions forsearching PDF files

You may search across multiple PDF files using the Adobe Reader software.

1. If the documentation is not accessible to all users of the EMC Smarts product suite, copy the contents of the BASEDIR/smarts/doc/pdf directory to a central location, such as a shared drive on your LAN, that operators and others may view.

2. To search throughout the documentation library, open the Acrobat Reader software.

a. Choose Edit > Search, and enter a word or phrase.

b. Select All PDF Documents in, in the Where would you like to search option, and type the pathname of the location where the PDF documents reside.

If you have more than one EMC Smarts product suite installed, you can set up cross-product document searches by copying files from the BASEDIR/smarts/doc/pdf directory for each product suite into this common documentation directory path.

Related documentation 49

http://Powerlink.EMC.com

Related Information


C

As part of the EMC Smarts deployment and configuration process, you will need to modify certain files. User modifiable files include configuration files, rule set files, templates, and files (such as seed files, and security configuration files) containing encrypted passwords. Original versions of these files are installed into appropriate subdirectories under the BASEDIR/smarts/ directory. For example, on UNIX operating systems the original versions of Global Manager configuration files are installed to /opt/InCharge7/SAM/smarts/conf/ics.

Original versions of files should not be altered. If a file requires modification, it must be stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories. For example, a modified ics.conf file should be saved to /opt/InCharge7/SAM/smarts/local/conf/ics. EMC Smarts software is designed to first search for user modifiable files in BASEDIR/smarts/local or one of its subdirectories. If a modified version of a file is not found in the local area, EMC Smarts software then searches appropriate non-local directories.

Note: Original versions of files may be changed or updated as part of an EMC Smarts software upgrade. However, files located in BASEDIR/smarts/local are always retained during an upgrade.

To facilitate proper file editing, EMC Corporation provides the sm_edit utility with every EMC Smarts product suite. When used to modify an original version of a file, this utility automatically creates a local copy of the file and places it in the appropriate location under BASEDIR/smarts/local. This ensures that the original version of the file remains unchanged. In both UNIX and Windows environments, you can invoke sm_edit from the command line. Optionally, you can configure Windows so that sm_edit is automatically invoked when user-modifiable files are double-clicked in Windows Explorer.

To invoke the sm_edit utility from the command line, specify the path and the name of the file you want to edit under BASEDIR/smarts. If multiple EMC Smarts products are running on the same host, you should ensure that you invoke sm_edit from the bin directory of the product suite whose files you wish to edit. For example, to edit the configuration file for the Global Manager, you invoke the sm_edit utility as follows:

# /opt/InCharge7/SAM/smarts/bin>sm_edit conf/ics/ics.conf

In this example, the sm_edit utility automatically creates a local copy of the ics.conf file in the /opt/InCharge7/SAM/smarts/local/conf/ics directory and opens the file in a text editor. If a local version of the file already exists, the sm_edit utility opens the local version in a text editor. In addition, sm_edit creates any necessary subdirectories.

Understanding thesm_edit Utility

Understanding the sm_edit Utility 51

Understanding the sm_edit Utility

For more information about how to properly edit user modifiable files and how to use the sm_edit utility, refer to the EMC Smarts System Administration Guide.


Index

AAdapter Platform 31Availability Manager 11

BBASEDIR 46Broker location 32BROWSER 29, 30

CClasses for export 11, 43Client tool 20

Configuring 28clientConnect.conf 20, 23Configuration files 20Configuration parameters 22configureInfoVistaTools2.xml file 20, 25Control file 34

Default 36Create an export file 32cron 35

DDOMAIN_MANAGER_NAMES 22

EExport file 22EXPORT_FILE_NAME 22Exporting topology 10

GgetDataForReport script 20Global Console

Displaying reports 40Global Manager 22

IINCHARGE_DIR 34InfoVista VF2

Classes 43

VistaMart 25InfoVista VF2 Adapter

Configuration file 22Configuring 17Export file 22Overview 10

InfoVista VF2 Trapsee Trap

infovista2.conf file 20, 22infovista2.properties file 20, 26IV_SERVER_SUBDIRECTORY 29IV2_DIR 34iv2command.xml file 22iv2input.txt 22IVM_ORAHOST 34IVM_ORAPORT 34IVM_ORASID 34IVM_PWD 34IVM_USER 34IVM_ZONE 34

Llaunchserver.cmd tool 33Log file

For sm_infovista2 command 32For sm_sched utility 36

MMap Console

Invoking tools 40

NNotification Log Console

Invoking tools 40

Oojdbc14.jar file 26ORA_JAR_LOCATION variable 25Oracle database properties 27


Index

PProperty setting

InfoVista VF2 Portal SE server 26InfoVista VF2 VistaMart 26

RReporting 15

Configuring client tools 28Displaying reports 40Types of reports 40

runExportImport script 20, 34

SSAM_SERVER_NAME 22sched.conf file

Control file 34, 35Default control file 20Syntax 35

SecurityclientConnect.conf 23serverConnect.conf 23

serverConnect.conf 20, 23showVistaReport 20sm_config command 25sm_infovista2 command 32sm_sched utility 34

Log file 36Syntax 36

sm_sched.log file 36SNMP Trap Adapter 12

Configuring trap processing 31

TTime interval

Automate transfer process 35Topology

Create an export file 32EMC Smarts classes for export 11, 43Export file name 22InfoVista VF2 classes for import 43Reports available for 39

Topology Browser ConsoleInvoking tools 40

Trap 10, 12trap_mgr.conf file 20, 31trap_mgr.infovista2.conf file 20, 31

VviewTrapReport 20VPSE_HOSTNAME 29, 30VPSE_LOGIN 29, 30VPSE_PASSWORD 29, 30VPSE_WEB_PORT 29, 30vtsAccessRelatedReport 20vtsCreateReport 20vtsViewMyReport 20

XXML file 20

configureInfoVistaTools2.xml file 25iv2command.xml file 22
