Smarts Service Assurance Management Suite - Dell EMC · Service Assurance Management Suite 7.0 Installation Guide ... Linux, and Windows ... EMC Smarts Adapter for TIBCO Rendezvous,

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

EMC® Smarts®

Service Assurance Management Suite7.0

Installation GuideP/N 300-004-042

REV A02

EMC Smarts Service Assurance Management Suite Installation Guideii

Copyright ©1996–2006 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.

EMC Smarts Service Assurance Management Suite Installation Guide iii

Preface........................................................................................................................... vii

Chapter 1 OverviewSuite products................................................................................... 1-2

EMC Smarts Service Assurance Management Suite ........... 1-2EMC Smarts product and version compatibility......................... 1-3Installation tasks .............................................................................. 1-4Add products to existing installation tasks.................................. 1-6Uninstallation tasks ......................................................................... 1-8

Chapter 2 Service Assurance Management Suite RequirementsMigration from previous versions................................................. 2-2Operating system requirements .................................................... 2-3Hardware requirements.................................................................. 2-5Web Console and Business Dashboard requirements ................ 2-9

Java Web Start requirements for Web Console .................. 2-10

Chapter 3 Installing the Service Assurance Management SuiteBefore installation ............................................................................ 3-2

Installation requirements......................................................... 3-2Determine the location of the EMC Smarts Broker ............. 3-3Detect and stop EMC Smarts programs ................................ 3-3Backing up your configuration............................................... 3-7Choose an operating mode for the installation program.... 3-7

Install the EMC Smarts Service Assurance Management Suite ......................................................................... 3-10

Mounting the CD-ROM ......................................................... 3-10

Contents

EMC Smarts Service Assurance Management Suite Installation Guideiv

Contents

Inserting the CD-ROM........................................................... 3-10Performing the installation ................................................... 3-10Using wizard mode................................................................ 3-11Using CLI-Mode ..................................................................... 3-14Using unattended (silent) mode........................................... 3-16

Chapter 4 Adding Products to an InstallationBefore installation ............................................................................ 4-2

Installation requirements ........................................................ 4-2Determine the location of the EMC Smarts Broker ............. 4-3Detect and stop EMC Smarts programs................................ 4-3Stopping active EMC Smarts programs (Windows) ........... 4-6Choose an operating mode for the installation program ... 4-7

Install new products to an existing EMC Smarts Service Assurance Management Suite installation................................... 4-9

Mounting the CD-ROM........................................................... 4-9Inserting the CD-ROM............................................................. 4-9Performing the installation ..................................................... 4-9Using wizard mode................................................................ 4-10Using CLI-Mode ..................................................................... 4-13Using unattended (Silent) mode .......................................... 4-14

Chapter 5 Uninstalling Service Assurance Management SuiteBefore uninstallation ....................................................................... 5-3

Detect and stop EMC Smarts programs................................ 5-3Uninstall the Service Assurance Management Suite.................. 5-8

Uninstall using Wizard-Mode ................................................ 5-8Uninstall using CLI mode ....................................................... 5-9Uninstall using Unattended mode....................................... 5-10Uninstall from the Control Panel (Windows only) ........... 5-11

Chapter 6 Verifying the InstallationObtain and install a temporary license file .................................. 6-2Start EMC Smarts products............................................................ 6-3Start EMC Smarts services.............................................................. 6-4

Starting services on UNIX....................................................... 6-4Starting services on Windows ................................................ 6-5

Verify the EMC Smarts product status ......................................... 6-6Where to go next .............................................................................. 6-7

vEMC Smarts Service Assurance Management Suite Installation Guide

Contents

Appendix A Manually Installing ServicesBroker .............................................................................................. A-3Service Assurance Manager ......................................................... A-4

SAM Server (Global Manager)/BIM.................................... A-4SAM Adapter Platform .......................................................... A-4Business Dashboard................................................................ A-5Syslog Adapter ........................................................................ A-5SNMP Trap Adapter............................................................... A-5

Appendix B UNIX Procedures for CD-ROMsMounting the CD-ROM ................................................................. B-2

Appendix C Manually Starting ProductsStart products in native mode (UNIX only) .............................. C-2

Appendix D Understanding the sm_edit Utility

EMC Smarts Service Assurance Management Suite Installation Guidevi

Contents

EMC Smarts Service Assurance Management Suite Installation Guide vii

Preface

This document provides instructions for installing EMC Smarts Service Assurance Management Suite products on Solaris, HP-UX, Linux, and Windows platforms.

Audience for this guideThis guide is intended for administrators and integrators who are responsible for installing the EMC Smarts Service Assurance Management Suite.

EMC Smarts Service Assurance Management Suite 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, EMC Smarts Service Assurance Management Suite is, by default, installed to /opt/InCharge7/SAM/smarts. On Windows operating systems, this product is, by default, installed to: C:\InCharge7\SAM\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.

viii EMC Smarts Service Assurance Management Suite Installation Guide

Preface

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

EMC Smarts Service Assurance Management Suite productsEMC Corporation offers the following product suites:

◆ EMC Smarts Service Assurance Management Suite

◆ EMC Smarts Service Assurance Management Adapter Suite

EMC Smarts Service Assurance Management SuiteThe EMC Smarts Service Assurance Management Suite includes the following products:

◆ Service Assurance Manager (Global Manager), includes Business Impact Manager (BIM) and Failover System

◆ Global Console

◆ Business Dashboard

◆ SAM Native Adapters:

• Service Assurance Manager Notification Adapters (E-Mail Notifier Adapter, Script Notifier Adapter, SNMP Trap Notifier Adapter, EMC Smarts Adapter for TIBCO Rendezvous, Log File Notifier Adapter)

• Adapter Platform (Adapter Platform server, Syslog Adapter, and SNMP Trap Adapter)

• XML Adapter

EMC Smarts Service Assurance Management Adapter SuiteThe EMC Smarts Service Assurance Management Adapter Suite includes the following products:

◆ SQL Data Interface Adapter

◆ Report Manager

◆ SAM third-party adapters:

• 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 NetIQ AppManager

EMC Smarts Service Assurance Management Suite Installation Guide ix

Preface

• EMC Smarts Adapter for Remedy ARS

• EMC Smarts Adapter for SiteScope

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

◆ EMC Smarts Dynamic Modeling Tutorial

◆ EMC Smarts MODEL Reference Guide

EMC Smarts Service Assurance Management Suite documentationThe 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

http://Powerlink.EMC.com

x EMC Smarts Service Assurance Management Suite Installation Guide

Preface

◆ EMC Smarts Service Assurance Management Suite Migration Guide

◆ EMC Smarts Service Assurance Manager Operator’s Guide

◆ EMC Smarts Service Assurance Manager Configuration Guide

◆ EMC Smarts Service Assurance Manager Dashboard Configuration Guide

◆ EMC Smarts Business Impact Manager User’s Guide

◆ EMC Smarts Report Manager User’s Guide

◆ EMC Smarts Service Assurance Manager Failover System User’s Guide

The following documents are relevant to Service Assurance Manager adapters:

◆ EMC Smarts SAM Adapters Suite and Report Manager Installation Guide

◆ EMC Smarts Service Assurance Manager Adapter Platform User’s Guide

◆ EMC Smarts Service Assurance Manager Notification Adapters User’s Guide

◆ EMC Smarts SQL Data Interface Adapter User’s Guide

◆ EMC Smarts Adapter for Remedy ARS User’s Guide

◆ EMC Smarts Adapter for Concord eHealth User’s Guide

◆ EMC Smarts Adapter for NetIQ AppManager User’s Guide

◆ EMC Smarts Adapter for InfoVista VF2 User’s Guide

◆ EMC Smarts XML Adapter User’s Guide

◆ EMC Smarts Adapter for BMC Patrol User’s Guide

◆ EMC Smarts Adapter for Microsoft Operations Manager User’s Guide

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

◆ EMC Smarts Adapter for SiteScope User’s Guide

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

Suggestions for searching PDF filesYou may search across multiple PDF files using the Adobe Acrobat Reader software.

EMC Smarts Service Assurance Management Suite Installation Guide xi

Preface

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.

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

2. In the Where would you like to search option, select All PDF Documents in 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.

Conventions used in this guideEMC 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.

xii EMC Smarts Service Assurance Management Suite Installation Guide

Preface

Typographical conventionsEMC uses the following conventions in this guide:

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.

EMC Smarts Service Assurance Management Suite Installation Guide xiii

Preface

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 displays for Windows and an open circle displays for UNIX.

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 helpEMC 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

% 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.

http://powerlink.emc.com

xiv EMC Smarts Service Assurance Management Suite Installation Guide

Preface

Overview 1-1

1

This chapter describes the EMC Smarts Service Assurance Management Suite products and their compatibility with other EMC® Smarts® products. In addition, this chapter provides checklists for installation and uninstallation tasks.

◆ Suite products.....................................................................................1-2◆ EMC Smarts product and version compatibility...........................1-3◆ Installation tasks.................................................................................1-4◆ Add products to existing installation tasks....................................1-6◆ Uninstallation tasks ...........................................................................1-8

The product suite is distributed on a CD-ROM and is installed in the /SAM subdirectory under the InCharge7 root directory.

Overview

1-2 EMC Smarts Service Assurance Management Suite Installation Guide

Overview

Suite productsThis section describes the suite products and their compatibility with other EMC Smarts products. In addition, this chapter provides checklists for complete installation, installation of additional products, and uninstallation tasks.

EMC Smarts Service Assurance Management SuiteThe suite contains the following:

◆ Service Assurance Manager: The EMC Smarts Service Assurance Manager product includes the following components: the Global Manager, EMC Smarts Broker, EMC Smarts Business Impact Manager, EMC Smarts Service Assurance Manager Failover System, and generic notification adapters such as Log File, SNMP Trap, Script, and E-Mail. Some components, such as Business Impact Manager, require licensing.

◆ Global Console: The Global Console product is the graphical interface for all EMC Smarts products.

Global Console functionality can also be deployed as a Web Console or a Business Dashboard.

◆ Adapter Platform: The SAM Adapter Platform product provides functionality to import and normalize topology and events from outside the EMC Smarts domain.

◆ Syslog Adapter: The Syslog Adapter product reads and processes system log (Syslog) messages. It requires the SAM Adapter Platform.

◆ SNMP Trap Adapter: The SNMP Trap Adapter product reads SNMP traps and forwards traps to any EMC Smarts application. It requires the SAM Adapter Platform.

◆ EMC Smarts Adapter for TIBCO Rendezvous: The TIBCO Rendezvous Adapter product forwards notifications as TIBCO Rendezvous messages.

◆ XML Adapter: The XML Adapter product imports and exports topology from any EMC Smarts application.

EMC Smarts product and version compatibility 1-3

Overview

EMC Smarts product and version compatibilityThe Service Assurance Management Suite is compatible with the versions of the products listed in the EMC Smarts Service Assurance Management Suite 7.0 interoperability chart shown in Table 1-1.

Table 1-1 Interoperability Chart

EMC Smarts Product Suite

EMC Smarts Application Connectivity Monitor 1.0, 2.1.1

EMC Smarts Application Discovery Manager 5.1

EMC Smarts Application Services Management Suite 1.0

EMC Smarts ATM/Frame Relay Availability Management Suite 2.0.1

EMC Smarts IP Management Suite 6.5.1, 6.5.2, 6.5.3, 7.0

EMC Smarts MPLS Management Suite 1.3.1

EMC Smarts Multicast Manager 1.1

EMC Smarts Network Protocol Management Suite 2.0

EMC Smarts Optical Transport Management Suite 2.0.0.1

EMC Smarts Service Assurance Management Adapter Suite 1.0

EMC Smarts Service Assurance Management Suite 6.5.1, 6.5.2, 6.5.3, 7.0

EMC Smarts Storage Insight for Availability 1.0.0.2

EMC Smarts XD Manager for ATM/FR-to-IP AM 2.0

EMC Smarts XD Manager OTM-to-IP AM 1.0.0.1


Overview

Installation tasksTo install the Service Assurance Management Suite, satisfy the requirements and perform the tasks listed in Table 1-2.

Table 1-2 EMC Smarts Service Assurance Management Suite installation requirements and tasks

Tasks Go to:

Before you install the EMC Smarts Service Assurance Management Suite

Satisfy all requirements to install the suite. “Service Assurance Management Suite Requirements” on page 2-1“Before installation” on page 3-2

Check the Broker configuration. “Determine the location of the EMC Smarts Broker” on page 3-3

Detect and stop EMC Smarts programs. “Detect and stop EMC Smarts programs” on page 3-3

Choose an operating mode for the installation program. “Choose an operating mode for the installation program” on page 3-7

installation method:

Mount the CD-ROM. “Mounting the CD-ROM” on page 3-10

Install using your chosen mode of operation:• Wizard Mode• CLI Mode• Unattended (Silent) Mode

• “Using wizard mode” on page 3-11• “Using CLI-Mode” on page 3-14• “Using unattended (silent) mode” on page 3-16

After you install:

Save your EMC Smarts evaluation license, smarts.lic, to the BASEDIR/smarts/local/conf directory. Edit the SM_LICENSE variable in the runcmd_env.sh file so that the variable specifies the full path name to the smarts.lic file.

“Obtain and install a temporary license file” on page 6-2

Start the suite products for the first time. “Start EMC Smarts products” on page 6-3

Verify the current state of the products and Broker. “Verify the EMC Smarts product status” on page 6-6

Install your permanent EMC Smarts license. EMC Smarts System Administration Guide

Installation tasks 1-5

Overview

Configure EMC Smarts installations to your desired level of security. Although default encryption is enabled during the 7.0 installation process, EMC Corporation highly recommends that you configure a greater level of security for your deployment.

EMC Smarts System Administration Guide

Configure the Global Manager. EMC Smarts Service Assurance Manager Configuration Guide

Configure the Domain Manager(s) and initiate Discovery See documentation for your product suite.

Table 1-2 EMC Smarts Service Assurance Management Suite installation requirements and tasks (continued)

Tasks Go to:


Overview

Add products to existing installation tasksTo install additional products to an existing installation of the Service Assurance Management Suite, satisfy the requirements and perform the tasks listed in Table 1-3.

Table 1-3 Installing additional products to an existing EMC Smarts Service Assurance Management Suite requirements and tasks

Tasks Go to:

Before you install the EMC Smarts Service Assurance Management Suite

Satisfy all requirements to install the suite. “Service Assurance Management Suite Requirements” on page 2-1“Before installation” on page 4-2

Check the Broker configuration. “Determine the location of the EMC Smarts Broker” on page 4-3

Detect and stop EMC Smarts programs. “Detect and stop EMC Smarts programs” on page 4-3

Choose an operating mode for the installation program. “Choose an operating mode for the installation program” on page 4-7

installation method:

Mount the CD-ROM. “Mounting the CD-ROM” on page 4-9

Install using your chosen mode of operation:• Wizard Mode• CLI Mode• Unattended (Silent) Mode

• “Using wizard mode” on page 4-10• “Using CLI-Mode” on page 4-13• “Using unattended (Silent) mode” on page 4-14

After you install:

Save your EMC Smarts evaluation license, smarts.lic, to the BASEDIR/smarts/local/conf directory. Edit the SM_LICENSE variable in the runcmd_env.sh file so that the variable specifies the full path name to the smarts.lic file.

“Obtain and install a temporary license file” on page 6-2

Start the suite products for the first time. “Start EMC Smarts products” on page 6-3

Verify the current state of the products and Broker. “Verify the EMC Smarts product status” on page 6-6

Install your permanent EMC Smarts license. EMC Smarts System Administration Guide

Add products to existing installation tasks 1-7

Overview

Configure EMC Smarts installations to your desired level of security. Although default encryption is enabled during the 7.0 installation process, EMC Corporation highly recommends that you configure a greater level of security for your deployment.

EMC Smarts System Administration Guide

Configure the Global Manager. EMC Smarts Service Assurance Manager Configuration Guide

Configure the new products that were added to the existing installation EMC Smarts Service Assurance Manager Configuration Guide

Table 1-3 Installing additional products to an existing EMC Smarts Service Assurance Management Suite requirements and tasks (continued)

Tasks Go to:


Overview

Uninstallation tasksTo uninstall the EMC Smarts Service Assurance Management Suite, satisfy the requirements and perform the tasks listed in the Service Assurance Management Suite uninstallation requirements and tasks table shown in Table 1-4.

Table 1-4 EMC Smarts Service Assurance Management Suite uninstallation requirements and tasks

Tasks Go to:

Before you uninstall the EMC Smarts Service Assurance Management Suite

Detect and stop EMC Smarts programs “Detect and stop EMC Smarts programs” on page 5-3

Uninstallation method:

Uninstall the EMC Smarts Service Assurance Management Suite using one of these methods or modes:• Windows Control Panel method• Wizard Mode• CLI Mode• Unattended (Silent) Mode

• “Uninstall using Wizard-Mode” on page 5-8• “Uninstall using CLI mode” on page 5-9• “Uninstall using Unattended mode” on page 5-10• “Uninstall from the Control Panel (Windows only)”

on page 5-11

Service Assurance Management Suite Requirements 2-1

2

This chapter describes the operating system and hardware requirements for the Release 7.0 of the EMC Smarts Service Assurance Management Suite. It also provides Web Console and Business Dashboard requirements.

◆ Migration from previous versions...................................................2-2◆ Operating system requirements.......................................................2-3◆ Hardware requirements ....................................................................2-5◆ Web Console and Business Dashboard requirements ..................2-9

Service AssuranceManagement Suite

Requirements


Service Assurance Management Suite Requirements

Migration from previous versionsService Assurance Management Suite 7.0 can be migrated from the following older versions:

◆ EMC Smarts Service Assurance Management Suite 6.2 SP3

◆ EMC Smarts Service Assurance Management Suite 6.5 SP3

Note: See the EMC Smarts Service Assurance Management Suite Migration Guide for instructions on migrating from Service Assurance Management Suite 6.2 SP3 or 6.5 SP3.

If your current Service Assurance Management Suite installation is not at either of these version levels, you must first install the appropriate SmartPack to bring it to either of these levels before starting the 7.0 installation.

To determine your existing 6.x version level, perform the following:

1. From the Service Assurance Manager BASEDIR/smarts/bin/, enter the following command:

sm_server --version

2. EMC Smarts displays the following:

V<Number> <Date> <Build> Copyright <Date> EMC Corporation

Note: Product versions vary and do not always match the software platform version number. For example, if you select About from the Help menu in the Global Console, you may see a different number.

Operating system requirements 2-3


Operating system requirementsTable 2-5 summarizes the operating system platforms that are supported by each product in the EMC Smarts Service Assurance Management Suite.

Recommended patch levelsTable 2-6 on page 2-4 summarizes the operating system patches required by the EMC Smarts product suite.

Table 2-5 Supported operating systems for EMC Smarts Service Assurance Management Suite

EMC Smarts product

Platform

Solaris HP-UX Linux Windows VMWare ESX 2.5

EMC Smarts Service Assurance Manager

8, 9, 10 11.11 Red Hat Enterprise Linux AS 3, 4

Windows 2003 Enterprise Edition SP1 and R2

Windows 2003 Enterprise Edition, SP1 and R2Red Hat Enterprise Linux AS 3 Update 5

EMC Smarts Business Impact Manager

8, 9, 10 11.11 Red Hat Enterprise Linux AS 3, 4.

Windows 2003 Enterprise Edition, SP1 and R2


Global Console 8, 9, 10 11.11 Red Hat Enterprise Linux AS 3, 4.

Windows 2003 Enterprise Edition, SP1 and R2Windows XP Professional SP2


EMC Smarts Business Dashboard

8, 9, 10 11.11 Red Hat Enterprise Linux AS 3, 4.

Windows 2003 SP1 and R2Windows XP Professional SP2


SAM Adapters 8, 9, 10 11.11 Red Hat Enterprise Linux AS 3, 4.

Windows Enterprise Edition 2003 SP1 and R2




CAUTION!Verify that your operating systems are patched to the levels recommended by the manufacturer. The following patch levels have been identified as critical to the proper functioning of the EMC Smarts software.

Table 2-6 Required operating system patches

Operating system Patches

Solaris 8 108434-22 C++ runtime library (32-bit)

180435-22 C++ runtime library (64-bit)

111721-04 libm patch

Solaris 9 111711-16 C++ runtime library (32-bit)

111712-16 C++ runtime library (64-bit)

111722-04 libm patch

Solaris 10 119963-08 C++ patch

HP-UX Apply the latest Standard HP-UX Patch bundle that the HP patch assessment tool recommends.

Linux libstdc++-2.96-124.7.2 (when the Global Console is accessed on Linux systems)

Hardware requirements 2-5


Hardware requirementsFollowing are the hardware requirements for EMC Smarts Service Assurance Management Suite.

Table 2-7 represents the minimum hardware requirements and Table 2-8 on page 2-6 represents the minimum hard disk space requirements

If you are for installing more than one product, then your system must meet the products’ total memory and data disk space requirements.

Table 2-7 Hardware Requirements for the SAM Suite

Platform Product Hardware

Solaris 8, 9, and 10 Global Console, Web Console, Business Dashboard, XML Adapter

Sun Blade 100

All other products Sun Fire v240

HP-UX 11.11 Global Console, Web Console, Business Dashboard, XML Adapter

b2600

All other products HPrp4480-8

Red Hat Enterprise Linux AS, 3, 4

Global Console, Web Console, Business Dashboard, XML Adapter

Pentium III, 1.6 GHz

All other products 2xPentium 4, 2 GHz

Windows 2003 Enterprise Edition SP1 and R2

Global Console, Web Console, Business Dashboard, XML Adapter


All other products 2xPentium 4, 2 GHz

Windows XP Professional SP2

Global Console, Web Console, Business Dashboard




Required disk space for the Service Assurance Management Suite shown in Table 2-8 lists disk space requirements for installing all products in the Service Assurance Management Suite.

CPU, memory, and data disk space requirements as shown in Table 2-9 lists minimum requirements for CPUs, memory, and data disk space used by the software for writeable files such as logs, repository files, and output files.

Note: CPU means the number of physical CPU cores; not the number of CPU's displayed when hyperthreading is activated.

If you are installing more than one product, then your system must meet the products’ total memory and data disk space requirements (disk space (Table 2-8) plus RAM plus data disk space for a product (Table 2-9))..

Table 2-8 Required disk space for the EMC Smarts Service Assurance Manager Suite

Platform Disk Space

Solaris 8, 9, and 10 600 MB

HP-UX 11.11 650 MB

Red Hat Enterprise Linux AS 3, 4 400 MB

Windows 2003 Enterprise Edition SP1 and R2 350 MB

VMWare ESX 2.5 running Red Hat Enterprise Linux AS 3, 4 400 MB

VMWare ESX 2.5 running Windows 2003 Enterprise Edition SP1 350 MB

Table 2-9 CPU, memory, and data disk space requirements

EMC Smarts product CPUsMemory (RAM) Data disk space

Service Assurance Manager 2 512 MB 100 MB each

Global Console 1 256 MB N/A

Global Console, Web Console, and Business Dashboard

1 256 MB 150 MB

Service Assurance Manager Adapter Platform

1 512 MB 100 MB each

Hardware requirements 2-7


Note: For the XML Adapter, disk space depends on the size of the output you wish to export. Each output file can range from 0 to 200 MB. If, for example, the XML Adapter communicates with five Service Assurance Global Managers and each output file is 200 MB, then 1 gigabyte (GB) is required.

Additional HP-UX requirements

This section lists additional requirements for HP-UX 11.11.

Use the HP-UX system administration manager tool to verify that the following parameters in Table 2-10 on page 2-8 are set accordingly. Use “Choose Kernel Configuration,” “Choose Configurable Parameter” to get to the definition page. The necessary procedures are described in the HP-UX System Administration Tasks manual.

If necessary, make changes. Then, rebuild the kernel and reboot the system. You may want to contact your system administrator if you need additional help.

Note: You can also use the HPjconfig tool that checks kernel parameter values as well as patches. The kernel parameter values required for SMARTS software usually exceed the minimum values recommended by HPjconfig. You should use the larger of the two values—either the value based on the formula below or the value recommended by HPjconfig.

Syslog Adapter 1 256 MB 50 MB each

SNMP Trap Adapter 1 256 MB 50 MB each

EMC Smarts Adapter for TIBCO Rendezvous

1 256 MB N/A

XML Adapter 1 256 MB See Note below

Table 2-9 CPU, memory, and data disk space requirements (continued)

EMC Smarts product CPUsMemory (RAM) Data disk space



Table 2-10 on page 2-8 summarizes HP-UX parameter requirements and their values.

Formulas are provided as follows.

◆ The process data size limit kernel parameter (maxdsiz) must be set to at least 2 GB (or the maximum memory).

The value of this parameter is in decimal bytes. If it is below 2 GB (2147483648 bytes), increase it, rebuild the kernel, and restart the system.

◆ The max_thread_proc parameter must be set to at least 256, and the ncallout and nkthread parameters are calculated as follows.

In the formulas, “nSMARTS” is the total number of Smarts Managers and Consoles running simultaneously on the machine and “nproc” is a varying system parameter displayed by HP-UX System Administration Manager. It represents the maximum number of processes on the machine.

◆ The ncallout value must be equal to at least the calculated result, although the HP-UX System Administration Manager default is almost always sufficient.

ncallout = nproc + 10*nSMARTS

◆ The nkthread value must be equal to at least the calculated result:

nkthread = 2*nproc + max_thread_proc*nSMARTS

(The max_thread_proc parameter must be at least 256.)

Table 2-10 HP-UX parameters and values

Parameter Value

maxdsiz at least 2 GB (or the maximum memory)

max_thread_proc at least 256

ncallout nproc + 10*nSMARTS

nkthread 2*nproc + max_thread_proc*nSMARTS

Web Console and Business Dashboard requirements 2-9


Web Console and Business Dashboard requirementsThe EMC Smarts Global Console can also be deployed as either:

◆ EMC Smarts Web Console

◆ EMC Smarts Business Dashboard

Note: Jakarta Tomcat Servlet Engine version 5.5.X is installed as part of the Web Console/Business Dashboard. The Tomcat Servlet Engine serves the files used by the Web applications.

Users who display Business Dashboard viewlets in a Web browser, or wish to use the Web Console, require the following software.

◆ One of the following Web browsers:

• Internet Explorer 6.0 with Service Pack 1

• Netscape Navigator 8.0

• Firefox 1.5.x

• Browser that supports Java JRE 1.5.x

◆ For Windows, the browser must be JavaScript enabled.

Also, a list of specific versions of browsers that are supported on different platforms can be found at http://java.sun.com/products/plugin.

◆ Java™ 2 Platform Standard Edition 5.0 which includes the 1.5.x Web browser plug-in must be installed on the client workstation.

If you are running any version prior to 1.5, when you try to start up and run the Dashboard or web console, the applets inside the sample views shipped with the software do not display properly.

If your client workstation does not have this version of JRE, you must obtain it and install it.

• For the HP-UX platform, download it from the HP-UX web site, http://www.hp.com/go/java.

• For all other platforms, download it from the Sun Microsystems web site at http://java.sun.com/javase/downloads/index.jsp.

If the JRE is not installed on your client workstation, you will be prompted to install it when you launch the Web Console or Business Dashboard.



Java Web Start requirements for Web ConsoleJava Web Start is optional and can be invoked when the Web Console is executed.

Java Web Start must be installed and properly configured on the client machine.

◆ For UNIX, contact your system administrator to install and configure Java Web Start or follow the instructions provided on the Sun Microsystems web page, http://java.sun.com/j2se/1.5.0/install.html.

◆ For Windows, on the client machine, depending upon the type of browser, after you launch the Web Console, you are either prompted to use an automatic installer or directed to follow the instructions provided on the Sun Microsystems web page, http://java.sun.com/j2se/1.5.0/install.html.

To launch the Java Web Start version of the Web Console and use the automatic installer, point your browser to the following URL:

http://<Tomcat_host>:8080/webconsole/globalConsoleCached.html

where <Tomcat_host> refers to the name of the machine where the Jakarta Tomcat Servlet Engine is installed and 8080 refers to the default port for Tomcat.

For information about using the Web Console, see the EMC Smarts Service Assurance Manager Dashboard Configuration Guide.

Installing the Service Assurance Management Suite 3-1

3

This chapter describes instructions if you are installing this product suite or individual products for the first time.

◆ Before installation ..............................................................................3-2◆ Install the EMC Smarts Service Assurance Management Suite 3-10

The basic installation steps are the same for all supported UNIX and Windows platforms.

Installing the ServiceAssurance Management

Suite


Installing the Service Assurance Management Suite

Before installationThis section explains the requirements that must be met before installing the EMC Smarts Service Assurance Management Suite.

◆ See “Installation requirements” on page 3-2 for an explanation of administrator access and JAVA JRE requirements.

◆ “Determine the location of the EMC Smarts Broker” on page 3-3.

◆ “Detect and stop EMC Smarts programs” on page 3-3.

◆ “Choose an operating mode for the installation program” on page 3-7

Installation requirementsBefore beginning, you must satisfy the following requirements:

◆ Access requirement: The user performing the installation must either be superuser (User ID 0) on UNIX platforms or have administrative privileges on Windows platforms. The installation program will halt if the user does not have the appropriate privileges.

◆ JRE requirement: Version 1.4.2_06 or later of the Java Runtime Environment (JRE) must be installed on the system to run the installation program. The installation program attempts to detect that a compatible JRE version has been installed on your system. If necessary, download the required J2SE JRE version:

• Solaris: http://java.sun.com.

• HP-UX: http://www.hp.com/products1/unix/java/index.html

• Linux: http://java.sun.com.

• Windows: http://java.sun.com.

For UNIX or Windows, if a compatible JRE version is installed and the installation program cannot locate it, you must specify the location when you execute the installation program. Based on the operating mode of the installation program that is used when installing or upgrading the suite, there may be additional requirements. These requirements are included in the procedures for the specific modes.

Before installation 3-3


Determine the location of the EMC Smarts BrokerYou must specify the location of the EMC Smarts Broker during installation of the EMC Smarts software. Typically, this location is chosen during the design of the EMC Smarts software deployment and before any installation begins.

Consult with your deployment planner or check the build guide that documents your deployment to determine the name of the host where the Broker was installed and the port that the Broker uses.

If the location is the same host where you are installing this suite, then the installation program will automatically install the Broker if it is not already on the host.

Detect and stop EMC Smarts programsBefore installing or uninstalling your suite, you must stop all EMC Smarts services, EMC Smarts scheduled jobs, and any other process that uses programs or libraries in any EMC Smarts installation area.

WARNING

For new installations or uninstallations on UNIX, do not stop the EMC Smarts service daemon process, sm_serviced. However, when adding new products to an existing installation, you must stop sm_serviced.

When you install or uninstall suites, all EMC Smarts product suites on the same host must be shut down. If the Broker is on the host, it too must be shut down. This will prevent EMC Smarts applications from starting and new connections from being established while the Broker is down. Inform any users who may be affected and, if necessary, schedule the installation or uninstallation for a period of low utilization.

Detecting EMC Smarts programsThe sm_plist utility identifies all EMC Smarts programs that are running for any product suite on your machine. You can use the sm_plist utility whenever you need to identify EMC Smarts programs that are running (for example, before an installation or uninstallation, or applying another SmartPack or Rolling Patch).



To use the utility, invoke it from the BASEDIR/smarts/script directory. The utility displays active programs in a window.

1. Go to the BASEDIR/smarts/script directory.

2. Start the sm_plist utility:

For UNIX, enter

# ./sm_plist.sh BASEDIR2

For Windows, enter

cscript sm_plist.vbs BASEDIR2

Where BASEDIR is the directory where the sm_plist utility is installed and BASEDIR2 represents the location of any EMC Smarts product suite.

Stopping active EMC Smarts programs (UNIX)

1. Stop active EMC Smarts services using the sm_service utility from BASEDIR/smarts/bin:

# ./sm_service stop --all

Note: sm_serviced waits 30 minutes after sending a shutdown request to a process. If the process is still running after 30 minutes, sm_serviced terminates it.

2. Determine if any EMC Smarts services are still running by using the brcontrol utility from BASEDIR/smarts/bin:

# ./brcontrol -b <host>:<port>



Based on the location of the Broker, go to the appropriate step, as indicated in Table 3-11 on page 3-5.

3. Stop any EMC Smarts manager that is still running. If the Broker is on the host, stop the local Broker:

• To stop any manager that is still running, use the dmquit utility from BASEDIR/smarts/bin:

# ./dmquit --server=<servername>

• To stop the local Broker from BASEDIR/smarts/bin:

# ./brquit --broker=localhost:<port>

4. Determine if any other EMC Smarts processes are still running and shut the processes down:

• Detect the processes using the following command:

# ps -ef | grep “sm_”

If a list is displayed, note the process ID (pid) of these active EMC Smarts processes.

WARNING

Do not stop or kill the EMC Smarts service daemon process, sm_serviced.

• Shut down these EMC Smarts processes (except sm_serviced) using the following command:

# kill <pid>

Table 3-11 Next steps for detecting and stopping programs

The Broker is on the And this displays. Do this

Same host “Error attaching to broker” message

The EMC Smarts broker is not running. Go to Step 4.

List of servers registered with the Broker

• The Broker or service daemon did not shut down.• If any servers are still running on the host, these did not shut down.Go to Step 3.

Different host List of servers registered with the Broker

• If any servers are still running on the host where you will install the EMC Smarts software, these did not shut down. Go to Step 3.



Stopping active EMC Smarts programs (Windows)

To stop a service from the Windows desktop, use the Microsoft Management Console.

1. Select Settings > Control Panel.

2. At the Control Panel, select Administrative Tools.

3. At the Administrative Tools folder, select Services.

4. At the Services window, locate any EMC Smarts services. These services start with the words “EMC Smarts,” “InCharge,” or “Smarts.” For each of these services, right-click the service and then select Stop.

5. Repeat Step 4 until all EMC Smarts services are stopped.

6. Open a command prompt and determine if any EMC Smarts Managers are still running by using the brcontrol utility from BASEDIR\smarts\bin:

brcontrol -b <host>:<port>

7. Stop any EMC Smarts Manager that is still running using the dmquit utility from BASEDIR/smarts/bin:

dmquit --server=<servername>

8. If the Broker is installed on the same host, use the brquit utility from BASEDIR/smarts/bin to stop it:

brquit --broker=localhost:<port>

9. Press Ctrl+Alt+Delete. The Windows Security dialog box opens.

10. Click Task Manager. The Windows Task Manager opens.

11. Select the Processes tab.

CAUTION!Allow up to 30 minutes before performing Step 12. EMC Smarts Managers with large topologies can take a considerable amount of time to stop while saving the topology to the repository. Stopping processes prematurely may corrupt your repository files.

12. In the Processes tab, look in the column labeled Image Name for sm_server. For each sm_server, right-click it and then select End Process.



13. In the Processes tab, look for other Image Names that start with sm_, for example, sm_notify, sm_adapter, sm_beacon, etc. For each instance, right-click it and then select End Process.

Backing up your configuration

Back up your current suite configuration, including all customizations, using the smgetinfo utility. This utility collects version information and saves the /conf, /local, /rules, and /setup directories to an archive file.

For all platforms, to collect information about installed products and components, the Perl interpreter (version 5.0 or later) must be installed.

For Windows, WinZip is required. If WinZip is not installed in its default directory, set the variable ZIPPER to point to the WinZip directory.

To run the smgetinfo utility:

1. Ensure that the value for SM_HOME is set to BASEDIR.


3. Execute the appropriate command:

For UNIX enter

./smgetinfo

or

sh smgetinfo

For Windows enter

smgetinfo.cmd

The name and location of the resulting .tar or .zip archive file is displayed.

4. Archive the file for later use, if necessary.

Choose an operating mode for the installation program

Use one of the following modes supported by the installation program:



◆ Wizard mode is a Java-based Graphical User Interface (GUI).

◆ Command Line Interface (CLI) mode (UNIX only) is a text-based method intended to support systems with non-graphics consoles.

◆ Unattended (Silent) mode reads the selections and settings for the installation from a user-modifiable file, which enables users to easily duplicate the installation on many computer systems.

Use the following decision tree to choose the appropriate mode for the installation program.

Figure 3-1 Choose an operating mode for the installation program

Will the deployment require multiple installations?

No

Yes Use Unattended (Silent) mode

Windows

UNIX

Are all of these available?X Windows displayFixed ports for communication through firewallsSpecial access to production systems

Use the Wizard mode

What is the operating system?

Start

Yes to all

No

Use CLI mode (recommended) or

Unattended (Silent) mode

Use any mode:Wizard mode is recommended



Note: On UNIX systems, Wizard mode uses the X Window System to display the installation wizard. The host on which you install the EMC Smarts software and the host where you log on must be configured to run the X Windows System. Before starting the installation program using the Wizard mode, verify that the X Window System is running.



Install the EMC Smarts Service Assurance Management SuiteThis section describes how to install the 7.0 EMC Smarts Service Assurance Management Suite into a new directory structure.

Note: On the Windows 2003 (Enterprise Edition) platforms, EMC Smarts products do not install properly and EMC Smarts services do not start properly when installed to a directory path containing spaces. Therefore, the directory names used in BASEDIR cannot contain spaces.

Mounting the CD-ROMMount the CD-ROM and change to the CD-ROM directory using established procedures for your environment. The procedure for mounting the CD-ROM differs based on the operating system.

UNIXIf necessary, see Appendix B for typical commands and examples.

Inserting the CD-ROM1. Insert the CD-ROM into the CD-ROM drive. If autoplay is

enabled, the installation program starts automatically using the Wizard mode.

2. If necessary, change the directory to the CD-ROM. Use Windows Explorer to access the CD-ROM drive and locate the /suite directory.

Performing the installationTo perform the installation, use the procedure for the installation program mode that you selected:

◆ For Wizard mode, go to “Using wizard mode” on page 3-11.

◆ For CLI mode, go to “Using CLI-Mode” on page 3-14.

◆ For Unattended (Silent) mode, go to “Using unattended (silent) mode” on page 3-16.

Install the EMC Smarts Service Assurance Management Suite 3-11


Using wizard modeThe following text explains the use of Wizard mode for Windows or Unix operating systems.

Satisfy wizard mode requirements (UNIX Only)On UNIX systems, wizard mode uses the X Window System to display the installation wizard. The host on which you install the EMC Smarts software and the host where you log on must be configured to run the X Windows System. Before starting the installation program using the wizard mode, verify that X Window System is running.

Running wizard mode1. Execute the Setup command from Table 3-12 on page 3-11. The

InstallShield wizard dialog box displays and closes. The Shutdown Programs dialog box and the Welcome screen then display.

IMPORTANT!When you insert the installation CD, there may be a delay of several minutes between the InstallShield preparation screen and the EMC® Smarts® splash screen/installation dialogs. During this time, the java.exe process is running. Please be patient. Do not eject/reinsert the CD to start a second install process.

Table 3-12 Setup command syntax for wizard-mode

Operating system Execute:

Solaris # ./setup-solaris.bin

HP-UX # ./setup-hpux.bin

Linux # ./setup-linux.bin

Windows setup-winnt.exe

If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to specify the path to where Java is installed. For example, <local_java_dir> can be:• Windows: C:\Program Files\Java\j2re1.5 • UNIX: /opt/java/j2re1.5



2. If you have not already done so, find and stop the active EMC Smarts services. For installations or uninstallations, do not stop the EMC Smarts service daemon process, sm_serviced. However, when adding additional products to an existing installation, you must stop sm_serviced. Click OK in the Warning dialog box when you have stopped all EMC Smarts services.

3. Click Next in the Welcome screen to continue.

Next is disabled if:

• You do not have administrative privileges for the products you are attempting to install. An error message also displays.

• Your system failed the requirements check. If this occurs, review the check results by clicking Get System Information. Then, cancel the installation setup program, and upgrade your system.

4. Read and accept the EMC Corporation end user license agreement and click Next.

5. If the installation program detects an existing installation of the same suite, the Installation Type screen displays.

Select Install the product to a new directory.

Note: This screen does not display if you are installing the suite for the first time on the system.

6. Click Next to accept the default installation directory or type your preferred directory and click Next.

The default installation directory is /opt/InCharge7 (on UNIX) or C:\InCharge7 (on Windows).

If you specify a directory, be sure to use forward slashes (“/”) for both UNIX and Windows directories. If the specified directory does not exist, it will be created. If you do not have write privileges, an error message displays.

Note: On the Windows 2003 (Enterprise Edition) platform, EMC Smarts products do not install properly and EMC Smarts services do not start properly when installed to a directory path containing spaces. Therefore, the directory names used in BASEDIR cannot contain spaces.

7. In the Setup screen, select one of the options, then click Next:

• Complete to install the entire suite.



• Global Console to install the java-based console without installing any other applications. Select this if you are installing the Global Console on a server separate from where you’ve installed EMC Smarts Service Assurance Management Suite.

Note: If you are installing the entire Service Assurance Management Suite, you will have another opportunity to install the Global Console as part of the suite installation in Step 8.

• Custom to install a specific product.

In the Product Selection screen that follows afterwards, deselect products that you do not wish to install (by default, all products are selected). Click Next.

8. If you selected Complete or Custom in Step 7, select the type of Global Console installation. You can select the Global Console or the Global Console, Web Console, and Business Dashboard.

9. The Services Selection screen displays. Select the products that you wish to install as services and click Next. If a product is not selectable (displays as gray text), click Back to return to the Product Selection screen and select the product.

Note: When installed as services, EMC Smarts products run when the system is running. If the system is stopped and restarted, the EMC Smarts products restart automatically. EMC Corporation recommends that EMC Smarts products be installed as services whenever possible. If any of the products being installed can be started as services, these products are displayed in the services selection screen.

10. Choose a location to install an EMC Smarts Broker or specify the location of an existing broker. Click Next to continue.

11. Review the list of products that will be installed and the target installation directory. At the bottom of the list, the total amount of disk space required for the selected products is provided so that you can verify that adequate disk space is available. To install the products, click Next.

Note: A screen will display for a short period of time, letting you know that a runtime patch is being installed. This requires no user intervention and will only take a few seconds.

12. The Installation Progress screen is displayed.



Note: During the installation, a screen is displayed asking you to specify the location of the respository file to be migrated. Leave blank if you are not migrating from a 6.x installation. If you are doing this 7.0 installation as the first step of a migration process, enter the path to the 6.x repository files.

Note: At the end of the installation process before clicking the Finish button, a screen displays reminding you to install any third-party SAM adapters. If you are, you need to insert the SAM Adapters Suite CD after the Service Assurance Management Suite is installed.

13. Upon completion, the Installation Summary displays informational messages such as successful confirmations, error messages, and warnings. Click Finish to exit the installation. It is not necessary to restart the system after installation.

Investigate any errors or warnings. The log file is a text file with the naming convention Install.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the installation process fails, the log files are located in the /tmp directory.

14. Unmount the CD-ROM after completing the installation. Be sure that no processes are currently accessing the drive.

Where to go nextFor all other post-installation steps, see “Verifying the Installation” on page 6-1.

Using CLI-ModeCLI mode installation is the text-based method of executing the Installation program. This mode is intended for UNIX platforms with non-graphics consoles. The CLI mode follows the same process as the wizard mode but uses text rather than graphics.



Running CLI modeTo start the CLI mode, execute the Setup command with the -console option as shown in Table 3-13 on page 3-15.

User selections and navigation in CLI modeDuring the installation and uninstallation processes, you are prompted with a series of steps and menus:

◆ For prompts, accept the default value or select another choice. The default values are indicated in brackets. To accept the default value, press Enter. To reply “yes,” enter y or Y; to reply “no,” enter n or N. Do not press Delete; this causes the process to terminate with an error message.

◆ For selections in menus, accept the default selections or type the number of the item and press Enter. The default values are indicated in brackets or as pre-defined selections in menus. An X is used to indicate the selected item. When you are finished making selections, type zero (0) and press Enter.

If you incorrectly type an entry, press 4 to repeat the prompt and select the correct value. Arrow keys and the Backspace key are not supported.

Table 3-13 The setup command syntax for CLI-mode

Operating system Executable

Solaris # ./setup-solaris.bin -console

HP-UX # ./setup-hpux.bin -console

Linux # ./setup-linux.bin -console

If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to indicate the path to the Java home directory. For example, <local_java_dir> can be /opt/java/j2re1.5



To navigate between each step, use the keys listed in Table 3-14 on page 3-16.

Where to go nextFor the post-installation steps, see “Verifying the Installation” on page 6-1.

Using unattended (silent) modeUnattended mode reads the commands and settings from a user-modifiable file that you create prior to beginning the process. Manual intervention is not necessary after you execute the setup command.

Modifying the response fileEach suite has a response file located on the CD-ROM in the /utils directory. Its naming convention is <suite>-response.txt.

The response file provides instructions and examples of command line options that are passed to the program in unattended mode. The command line options are organized by process flow. The process flow is almost identical to that of the Wizard mode.

By default, the response file includes settings that support the installation of all products from the CD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to change any of these settings: for example, to support Windows operating systems or specify a different Broker location.

For unattended operation, modify a response file:

1. Copy the response file from the CD-ROM /utils directory to a directory on your system, for example, the /tmp directory.

Table 3-14 Navigation keys

Key Operation

1 Next, continue to the next step

2 Previous, go back to the previous step

3 Cancel, terminate the program

4 Redisplay, repeat the step

0 Accept the marked ([X]} menu choice



2. Using any editor, modify the values for the command line options in the response file:

• Specify the target directory.

• Select a directory for the process log file.

• Select the products to install. Ensure that the property value for the product is set to true.

• Select the products to start as services. Ensure that the property value for the product is set to true.

• Specify the location of the Broker.

3. Save the file.

Running unattended modeExecute the Setup command from a command-line shell using the syntax in Table 3-15 on page 3-17.

For example, to start the unattended installation on Solaris for the EMC Smarts Service Assurance Management Suite when the response file is located in /opt/home, execute:

▼ # ./setup-solaris.bin -options /opt/home/SAM_SUITE-response.txt ▲

Table 3-15 The setup command syntax for unattended mode


Solaris # ./setup-solaris.bin -options <path>/<suite>-response.txt

HP-UX # ./setup-hpux.bin -options <path>/<suite>-response.txt

Linux # ./setup-linux.bin -options <path>/<suite>-response.txt

Windows setup-winnt.exe -options <path>\<suite>-response.txt

Where: <path> is the fully qualified path to the response file and <suite> is the product suite, for example, NPM, IP, MPLS, or SAM.If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to indicate the path to the Java home directory. For example, <local_java_dir> can be:• Windows: C:\Program Files\Java\j2re1.5• UNIX: /opt/java/j2re1.5



Note: ▼ ▲ Indicates that this command must be typed as one line. Separate each option with a space when typing the command.

Where to go nextFor post-installation steps, see “Verifying the Installation” on page 6-1.

Adding Products to an Installation 4-1

4

This chapter describes instructions if you are installing additional products into an existing product suite.

◆ Before installation ..............................................................................4-2◆ Install new products to an existing EMC Smarts Service Assurance

Management Suite installation ........................................................4-9

The basic installation steps are the same for all supported UNIX and Windows platforms.

Adding Products to anInstallation


Adding Products to an Installation

Before installationThis section explains the requirements that must be met before installing additional products into an existing EMC Smarts Service Assurance Management Suite.

◆ See “Installation requirements” on page 4-2 for an explanation of administrator access and JAVA JRE requirements.

◆ “Determine the location of the EMC Smarts Broker” on page 4-3.

◆ “Detect and stop EMC Smarts programs” on page 4-3.

Installation requirementsBefore beginning, you must satisfy the following requirements:

◆ Access requirement: The user performing the installation must either be superuser (User ID 0) on UNIX platforms or have administrative privileges on Windows platforms. The installation program will halt if the user does not have the appropriate privileges.

◆ JRE requirement: Version 1.4.2_06 or later of the Java Runtime Environment (JRE) must be installed on the system to run the installation program. The installation program attempts to detect that a compatible JRE version has been installed on your system. If necessary, download the required J2SE JRE version:

• Solaris: http://java.sun.com.

• HP-UX: http://www.hp.com/products1/unix/java/index.html

• Linux: http://java.sun.com.

• Windows: http://java.sun.com.

For UNIX or Windows, if a compatible JRE version is installed and the installation program cannot locate it, you must specify the location when you execute the installation program. Based on the operating mode of the installation program that is used when installing or upgrading the suite, there may be additional requirements. These requirements are included in the procedures for the specific modes.



Determine the location of the EMC Smarts BrokerYou must specify the location of the EMC Smarts Broker during installation of the EMC Smarts software. Typically, this location is chosen during the design of the EMC Smarts software deployment and before any installation begins.

Consult with your deployment planner or check the build guide that documents your deployment to determine the name of the host where the Broker was installed and the port that the Broker uses.

If the location is the same host where you are installing this suite, then the installation program will automatically install the Broker if it is not already on the host.


WARNING









For UNIX, enter


For Windows, enter



Stopping active EMC Smarts programs (UNIX)

1. Stop active EMC Smarts services using the sm_service utility from BASEDIR/smarts/bin:













4. Determine which EMC Smarts processes are running using the following command:

# ps -ef | grep *sm_*

Review the list that appears:

• If sm_serviced is the only process running, continue with Step 5.

• If multiple processes including sm_serviced are still running, wait 30 minutes and repeat this step. If the multiple processes are still running after this step is repeated, then continue with Step 5.

5. Stop sm_serviced. Stopping sm_serviced will stop all of the services that were automatically and manually started. The script is stored in a system-specific location: /etc/init.d on Solaris and Linux; and /sbin/init.d on HP-UX. Issue the command:











# <system-dependent path>/ic-serviced stop



# ps -ef | grep *sm_*


• Shut down these EMC Smarts processes using the following command:

# kill <pid>

Stopping active EMC Smarts programs (Windows)

To stop a service from the Windows desktop, use the Microsoft Management Console.




















Choose an operating mode for the installation program

Use one of the following modes supported by the installation program:

◆ Wizard mode is a Java-based Graphical User Interface (GUI).

◆ Command Line Interface (CLI) mode (UNIX only) is a text-based method intended to support systems with non-graphics consoles.

◆ Unattended (Silent) mode reads the selections and settings for the installation from a user-modifiable file, which enables users to easily duplicate the installation on many computer systems.

Use the following decision tree to choose the appropriate mode for the installation program.



Figure 4-2 Choose an operating mode for the installation program

Note: On UNIX systems, Wizard mode uses the X Window System to display the installation wizard. The host on which you install the EMC Smarts software and the host where you log on must be configured to run the X Windows System. Before starting the installation program using the Wizard mode, verify that the X Window System is running.

Will the deployment require multiple installations?

No

Yes Use Unattended (Silent) mode

Windows

UNIX

Are all of these available?X Windows displayFixed ports for communication through firewallsSpecial access to production systems

Use the Wizard mode

What is the operating system?

Start

Yes to all

No

Use CLI mode (recommended) or

Unattended (Silent) mode

Use any mode:Wizard mode is recommended

Install new products to an existing EMC Smarts Service Assurance Management Suite installation 4-9


Install new products to an existing EMC Smarts Service Assurance Management Suite installation

This section describes the process for installing additional products for 7.0 EMC Smarts Service Assurance Management Suite.

This process should only be considered if you are adding additional 7.0 products to an existing 7.0 SAM directory.

Mounting the CD-ROMMount the CD-ROM and change to the CD-ROM directory using established procedures for your environment. The procedure for mounting the CD-ROM differs based on the operating system.

UNIXIf necessary, see Appendix B for typical commands and examples.

Inserting the CD-ROM1. Insert the CD-ROM into the CD-ROM drive. If autoplay is

enabled, the installation program starts automatically using the Wizard mode.

2. If necessary, change the directory to the CD-ROM. Use Windows Explorer to access the CD-ROM drive and locate the /suite directory.

Performing the installationTo add additional products to an existing installation, use the procedure for the program mode that you selected:

◆ For Wizard mode, go to “Using wizard mode” on page 4-10.

◆ For CLI mode, go to “Using CLI-Mode” on page 4-13.

◆ For Unattended (Silent) mode, go to “Using unattended (Silent) mode” on page 4-14.



Using wizard modeThe following text explains the use of wizard mode for Windows or Unix operating systems.

Satisfy wizard mode requirements (UNIX Only)On UNIX systems, wizard mode uses the X Window System to display the installation wizard. The host on which you install the EMC Smarts software and the host where you log on must be configured to run the X Windows System. Before starting the installation program using the wizard mode, verify that X Window System is running.

Running wizard mode1. Execute the Setup command from Table 4-17 on page 4-10. The

InstallShield wizard dialog box displays and closes. The Shutdown Programs dialog box and the Welcome screen then display.

IMPORTANT!When you insert the installation CD, there may be a delay of several minutes between the InstallShield preparation screen and the EMC® Smarts® splash screen/installation dialogs. During this time, the java.exe process is running. Please be patient. Do not eject/reinsert the CD to start a second install process.

Table 4-17 Setup command syntax for wizard-mode

Operating system Execute:

Solaris # ./setup-solaris.bin

HP-UX # ./setup-hpux.bin

Linux # ./setup-linux.bin

Windows setup-winnt.exe

If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to specify the path to where Java is installed. For example, <local_java_dir> can be:• Windows: C:\Program Files\Java\j2re1.5 • UNIX: /opt/java/j2re1.5



2. If you have not already done so, find and stop the active EMC Smarts services. For installations or uninstallations, do not stop the EMC Smarts service daemon process, sm_serviced. However, when adding additional products to an existing installation, you must stop sm_serviced. Click OK in the Warning dialog box when you have stopped all EMC Smarts services.

For information on stopping the active EMC Smarts services, see “Detect and stop EMC Smarts programs” on page 4-3.


Next is disabled if:

• You do not have administrative privileges for the products you are attempting to install. An error message also displays.

• Your system failed the requirements check. If this occurs, review the check results by clicking Get System Information. Then, cancel the installation setup program, and upgrade your system.

4. Read and accept the EMC Corporation end user license agreement and click Next.

5. If the installation program detects an existing installation of the same suite, the Installation Type screen displays.

• Add additional products

• Install products to a new directory

Select Add additional products, then click Next.

6. In the Installation Type screen, you have two options:

• Complete to install the entire suite.

• Custom to install a specific product.

Select Custom, then click Next.

7. In the Product Selection screen, select the specific product to be added to the existing EMC Smarts Service Assurance Management Suite (By default, all products are selected). Click the Next button.

8. In the Services Selection screen, select the products that you wish to install as services and click Next. If a product is not selectable (displays as gray text), click Back to return to the Product Selection screen and select the product.



CAUTION!On a UNIX operating system, selecting services in Services Section screen will not install the services. You must manually install services for any additional products. This step is included in Step 14 on page 4-13.

Note: When installed as services, EMC Smarts products run when the system is running. If the system is stopped and restarted, the EMC Smarts products restart automatically. EMC Corporation recommends that EMC Smarts products be installed as services whenever possible. If any of the products being installed can be started as services, these products are displayed in the services selection screen.

9. In the Installed SMARTS Services screen, the services installed on the server are displayed along with their status. If any services show a status other than Stopped, stop the services before preceding further.

If any processes are still running, you must repeat the procedure. See “Detect and stop EMC Smarts programs” on page 4-3.

WARNING


10. Review the list of products that will be installed and the target installation directory. At the bottom of the list, the total amount of disk space required for the selected products is provided so that you can verify that adequate disk space is available. To install the products, click Next and the Installation Progress screen displays.

11. A screen is displayed asking you to specify the location of the respository file to be migrated. Since you are not performing a migration, leave blank and click Next.

12. Upon completion, the Installation Summary displays informational messages such as successful confirmations, error messages, and warnings. Click Finish to exit the installation. It is not necessary to restart the system after installation.



Investigate any errors or warnings. The log file is a text file with the naming convention Install.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the installation process fails, the log files are located in the /tmp directory.

13. Unmount the CD-ROM after completing the installation. Be sure that no processes are currently accessing the drive.

14. If this process was performed on a UNIX operating system, you need to install the services that you selected in Step 7 on page 4-11 manually by entering the appropriate sm_service install command for each additional service that you are adding to the application. See Appendix A, page A-1.

Where to go nextFor all other post-installation steps, see “Verifying the Installation” on page 6-1.

Using CLI-ModeCLI mode installation is the text-based method of executing the Installation program. This mode is intended for UNIX platforms with non-graphics consoles. The CLI mode follows the same process as the wizard mode but uses text rather than graphics.

Running CLI modeTo start the CLI mode, execute the Setup command with the -console option as shown in Table 4-18 on page 4-13.

Table 4-18 The setup command syntax for CLI-mode


Solaris # ./setup-solaris.bin -console

HP-UX # ./setup-hpux.bin -console

Linux # ./setup-linux.bin -console

If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to indicate the path to the Java home directory. For example, <local_java_dir> can be /opt/java/j2re1.5



User selections and navigation in CLI modeDuring the installation and uninstallation processes, you are prompted with a series of steps and menus:

◆ For prompts, accept the default value or select another choice. The default values are indicated in brackets. To accept the default value, press Enter. To reply “yes,” enter y or Y; to reply “no,” enter n or N. Do not press Delete; this causes the process to terminate with an error message.

◆ For selections in menus, accept the default selections or type the number of the item and press Enter. The default values are indicated in brackets or as pre-defined selections in menus. An X is used to indicate the selected item. When you are finished making selections, type zero (0) and press Enter.


To navigate between each step, use the keys listed in Table 4-19 on page 4-14.

Where to go nextFor the post-installation steps, see “Verifying the Installation” on page 6-1.

Using unattended (Silent) modeUnattended mode reads the commands and settings from a user-modifiable file that you create prior to beginning the process. Manual intervention is not necessary after you execute the setup command.

Table 4-19 Navigation keys

Key Operation

1 Next, continue to the next step

2 Previous, go back to the previous step

3 Cancel, terminate the program

4 Redisplay, repeat the step

0 Accept the marked ([X]} menu choice



Modifying the response fileEach suite has a response file located on the CD-ROM in the /utils directory. Its naming convention is <suite>-response.txt.

The response file provides instructions and examples of command line options that are passed to the program in unattended mode. The command line options are organized by process flow. The process flow is almost identical to that of the Wizard mode.

By default, the response file includes settings that support the installation of all products from the CD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to change any of these settings: for example, to support Windows operating systems or specify a different Broker location.

For unattended operation, modify a response file:

1. Copy the response file from the CD-ROM /utils directory to a directory on your system, for example, the /tmp directory.

2. Using any editor, modify the values for the command line options in the response file:

• Specify the target directory.

• Select a directory for the process log file.

• Select the products to install. Ensure that the property value for the product is set to true.

• Select the products to start as services. Ensure that the property value for the product is set to true.

• Specify the location of the Broker.

3. Save the file.

Running unattended modeExecute the Setup command from a command-line shell using the syntax in Table 4-20 on page 4-15.



Solaris # ./setup-solaris.bin -options <path>/<suite>-response.txt

HP-UX # ./setup-hpux.bin -options <path>/<suite>-response.txt



For example, to start the unattended installation on Solaris for the EMC Smarts Service Assurance Management Suite when the response file is located in /opt/home, execute:

▼ # ./setup-solaris.bin -options /opt/home/SAM_SUITE-response.txt ▲

Note: ▼ ▲ Indicates that this command must be typed as one line. Separate each option with a space when typing the command.

Where to go nextFor post-installation steps, see “Verifying the Installation” on page 6-1.

Linux # ./setup-linux.bin -options <path>/<suite>-response.txt

Windows setup-winnt.exe -options <path>\<suite>-response.txt

Where: <path> is the fully qualified path to the response file and <suite> is the product suite, for example, NPM, IP, MPLS, or SAM.If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to indicate the path to the Java home directory. For example, <local_java_dir> can be:• Windows: C:\Program Files\Java\j2re1.5• UNIX: /opt/java/j2re1.5



Uninstalling Service Assurance Management Suite 5-1

5

This chapter describes uninstalling the product suite or individual products. After uninstalling, your customized files remain saved in BASEDIR/smarts/local.

◆ Before uninstallation..........................................................................5-3◆ Uninstall the Service Assurance Management Suite ....................5-8

WARNING

For UNIX only, when uninstalling EMC Smarts suites from the same server, the EMC Smarts suite that was installed first must be uninstalled last.

During the installation of the first EMC Smarts suite, the EMC Smarts Service Database is also installed and the other suites subsequently access it. Uninstalling the suite installed first will also uninstall the Service Database which will disable the sm_service command for those products, prevent their proper operation and uninstallation, and interrupt products running as services.

Perform this check by looking at the value of the SMHOME variable in /etc/init.d/ic-serviced (or /sbin/init.d/ic-serviced for HP-UX). The suite listed in SMHOME is the suite that should be uninstalled last.

WARNING

EMC Smarts product suites use standard installation software to install and uninstall product suites. You must use the uninstaller command for UNIX. For Windows, you must use the Add/Remove

Uninstalling ServiceAssurance

Management Suite


Uninstalling Service Assurance Management Suite

Programs to uninstall EMC Smarts software. Failure to use the appropriate method will result in an unstable system and/or inconsistent product directories. Do not manually delete the installed product directories.

The uninstall process is not a rollback! It removes all product suite files, not simply files that changed as a result of a new product installation. If you need a full rollback procedure, contact EMC Smarts technical support.

WARNING

If you install additional services manually by selecting Custom from the Installation Type screen, you can only uninstall those services manually. They do not uninstall when you perfom a standard uninstallation.

Before uninstallation 5-3


Before uninstallationThe following section covers the preparation for the uninstallation process:

◆ “Detecting EMC Smarts programs” on page 5-3

◆ “Stopping active EMC Smarts programs (UNIX)” on page 5-4

◆ “Stopping active EMC Smarts programs (Windows)” on page 5-5

◆ “Uninstall the FLEXnet License Server” on page 5-6


WARNING









For UNIX, enter


For Windows, enter



Stopping active EMC Smarts programs (UNIX)1. Stop active EMC Smarts services using the sm_service utility from

BASEDIR/smarts/bin:























# ps -ef | grep “sm_”


WARNING

Do not stop or kill the EMC Smarts service daemon process, sm_serviced.

• Shut down these EMC Smarts processes (except sm_serviced) using the following command:

# kill <pid>

Stopping active EMC Smarts programs (Windows)To stop a service from the Windows desktop, use the Microsoft Management Console.




















Uninstall the FLEXnet License ServerThe FLEXnet License Server is used by EMC Smarts products for license management. The FLEXnet software is provided as part of any EMC Smarts software distribution. To install a FLEXnet License Server and set up permanent licenses for your EMC Smarts products, see the EMC Smarts System Administration Guide.

When uninstalling all of your EMC Smarts products and suites that use a specific FLEXnet License Server, you must also uninstall the FLEXnet License Server.



Note: If any EMC Smarts products will remain in your network and use the FLEXnet License Server, do not uninstall either the license server or the EMC Smarts product suite where the permanent license file resides.

If you uninstall EMC Smarts products without uninstalling the FLEXnet License Server, a message displays that the FLEXnet (lmgrd) service is still running. Keep in mind that an EMC Smarts application will not start if it is unable to contact the license server.

To stop and uninstall the FLEXnet license server, perform these steps:

1. Stop the FLEXnet license server.

Solaris

# /etc/init.d/SMARTS-License stop

HP-UX

# /sbin/init.d/SMARTS-License stop

Linux

# /etc/init.d/SMARTS-License stop

Windows

To manually start the license server on Windows, do the following as administrator:

• Select Start > Settings > Control Panel > Administrative Tools.

• Select Services.

• Select the FLEXnet License Server service.

• Right-click and choose Stop.

2. Execute the install_license script with the uninstall command from the BASEDIR/smarts/script directory.

UNIX

# BASEDIR/smarts/script>install_license.sh uninstall

Windows

BASEDIR\smarts\script>install_license.cmd uninstall



Uninstall the Service Assurance Management SuiteThe following section covers the uninstallation process for the following modes:

◆ “Uninstall using Wizard-Mode” on page 5-8

◆ “Uninstall using CLI mode” on page 5-9

◆ “Uninstall using Unattended mode” on page 5-10

◆ “Uninstall from the Control Panel (Windows only)” on page 5-11

Uninstall using Wizard-ModeUse Wizard mode to uninstall a complete suite or individual products from the local server.

1. Execute the the following command:

UNIX:

# BASEDIR/_uninst/uninstaller.bin

Windows:

# BASEDIR/_uninst/uninstaller.exe


3. In the Product Selection screen, click Next to uninstall the entire suite of products (by default, all products are selected) or deselect products that should remain installed.

4. Review the list of products that will be uninstalled and the target installation directory. Once you click Next, you cannot cancel the uninstallation process.

If necessary, click Back to return to the Product Selection screen to revise your selections.

To uninstall the products, click Next; the Uninstallation Progress screen displays.

5. Upon completion, the Uninstallation Summary displays informational messages such as successful confirmations, error messages, and warnings. If Next displays, your system needs to be rebooted. Click it and then reboot your system. Otherwise, click Finish to exit the uninstallation.

Uninstall the Service Assurance Management Suite 5-9


The log file is a text file with the naming convention Uninstall.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the uninstallation process fails, the log files are located in the /tmp directory.

6. Examine any remaining directories if you plan to re-install EMC Smarts and save customized files located in the /local directory. Depending upon the suite, some or all of the following subdirectories will remain in the BASEDIR/smarts directory after uninstallation because they contain user-modified files:

• /classes

• /local

• /bin

• /setup

Uninstall using CLI modeTo uninstall an EMC Smarts product or product suite using CLI-Mode, perform the following procedure:

1. Execute the following command:

# BASEDIR/_uninst/uninstaller.bin -console

During the uninstallation processes, you are prompted with a series of steps and menus. You can either accept the default value or select another choice. The default values are indicated in brackets or as pre-defined selections (check marks) in menus. To accept the default value, press Enter.

When replying to a prompt, you can either accept the default value or select another choice. To reply “yes,” enter y or Y; to reply “no,” enter n or N. Do not press Delete; this causes the process to terminate with an error message.

For selections in menus, you can accept default selections or type the number of the item and press Enter. An X displays next to the item. When you are finished making selections, type zero (0) and press Enter.




2. Upon completion, the Uninstallation Summary displays informational messages such as successful confirmations, error messages, and warnings. Press Enter to continue.

3. If necessary, the Installation Program will prompt to restart your computer. Press 1 to restart immediately or press 2 to restart later.

4. If you chose not to restart your computer, press 3 to finish.

5. Examine any remaining directories if you plan to re-install the suite and save customized files located in the /local directory. Depending upon the suite, some or all of the following subdirectories will remain in the BASEDIR/smarts directory after uninstallation because they contain user-modified files:

• /classes

• /local

• /bin

• /setup

6. The installation log file is a text file with the naming convention Uninstall.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the uninstallation process fails, the log files are located in the /tmp directory.

Uninstall using Unattended modeTo uninstall using unattended operation, stop EMC Smarts services including the service for the License Server. Then use the uninstaller.bin command to uninstall the software.

The log files are located in the BASEDIR/smarts/setup/logs directory. If the uninstallation process fails, the log files are located in the /tmp directory. A non-zero status indicates a failure.

To uninstall all of the products for a suite using unattended uninstallation, execute the following command:

▼# BASEDIR/_uninst/uninstaller.bin -silent -G replaceNewerResponse=”Yes to All” ▲

Note: ▼ ▲ indicates that this command must be typed as one line.

Uninstall the Service Assurance Management Suite 5-11


Uninstall from the Control Panel (Windows only)

Note: If you installed the same suite from two or more directories on your system, do not use Add/Remove Programs; use the uninstaller command instead. Add/Remove Programs does not support multiple instances of the same suite.

To use the Windows Control Panel to uninstall a product suite, perform these steps:

1. Click Start > Settings > Control Panel.

2. Double-click Add/Remove Programs.

3. From the Add/Remove Programs window, select the appropriate service for your product suite.

4. Click Change/Remove.



Verifying the Installation 6-1

6

This chapter includes:

◆ Obtain and install a temporary license file ....................................6-2◆ Start EMC Smarts products ..............................................................6-3◆ Start EMC Smarts services ................................................................6-4◆ Verify the EMC Smarts product status............................................6-6◆ Where to go next ................................................................................6-7

This chapter describes tasks for confirming proper installation for the EMC Smarts Service Assurance Management Suite.

Verifying theInstallation


Verifying the Installation

Obtain and install a temporary license fileTypically, the EMC Corporation will email a temporary license to you. Copy the license file, smarts.lic, to the BASEDIR/smarts/local/conf directory on the system where the EMC Smarts software is installed. If you installed multiple EMC Smarts product suites on the same system, each suite requires a separate copy of smarts.lic.

If you installed an EMC Smarts product suite on multiple systems, copy the license file, smarts.lic, to the BASEDIR/smarts/local/conf directory on each system where EMC Smarts software is installed.

Edit the SM_LICENSE variable in runcmd_env.sh on each system where EMC Smarts software is installed so that it specifies the full path and file name of a single smarts.lic file. When multiple EMC Smarts product suites are installed on the same system, each suite will include a runcmd_env.sh in its BASEDIR/smarts/local/conf directory.

Temporary licenses for EMC Smarts software are time-limited. At the end of the trial period, the software will no longer start. You can request an extension to your temporary license by emailing [email protected] with your request.

For more information on licensing or instructions for obtaining and installing a permanent license, see the EMC Smarts System Administration Guide.

Start EMC Smarts products 6-3


Start EMC Smarts products EMC Smarts recommends installing managers and adapters as services. If you installed the products as services, you must start them for the first time. These services start automatically upon system reboot, but the following sections describe additional methods to start EMC Smarts services.

If you did not install the products as services, you can install them now.

For information on manually installing products as services, see “Manually Installing Services” on page A-1.

For information on starting services, see the procedures “Start EMC Smarts services” on page 6-4.

For more information, see the EMC Smarts System Administration Guide.



Start EMC Smarts servicesThe following sections describe methods for starting EMC Smarts services.

Starting services on UNIX

Starting all EMC Smarts services on UNIXUse the ic-serviced command to check the status of the service daemon by issuing the command:

# <system-dependent path>/ic-serviced status

If the sm_serviced process does not respond, the process is not running. Start the service by issuing the command:

# <system-dependent path>/ic-serviced start

The script is stored in a system-specific location:

◆ Solaris: /etc/init.d

◆ Linux: /etc/init.d

◆ HP-UX: /sbin/init.d

Starting individual EMC Smarts services on UNIX systemsTo start or stop a service manually, use the sm_service utility. Issue the command:

▼# BASEDIR/smarts/bin/sm_service start <service_name> [<service_name> ...]▲

where <service_name> is each service you need to start.

Example: Starting a service for the Business Dashboard (EMC Smarts Servlet Engine)

▲# BASEDIR/smarts/bin/sm_service start ic-business-dashboard▼

Note: ▲▼Indicates that this command must be typed as one line. Separate each option with a space when typing the command.

Start EMC Smarts services 6-5


Starting services on Windows

Starting all EMC Smarts services on WindowsTo restart all of the EMC Smarts services, restart your system.

Starting individual EMC Smarts services on WindowsTo start an EMC Smarts service from the Windows desktop, follow these steps:

1. Select Start > Settings > Control Panel > Administrative Tools.

2. Select Services.

3. Right-click the EMC Smarts service to select it and display a menu.

4. Choose Start from the menu.

Note: Start the Broker service first if it is not running.



Verify the EMC Smarts product statusYou can determine the current state of the products in the suite that register with the Broker by issuing the following command:

BASEDIR/smarts/bin/brcontrol

This command displays a list of EMC Smarts Managers and adapters registered with the broker, their states (RUNNING, DEAD, UNKNOWN), process IDs, port numbers, and the last time that their states changed.

Also check any log files for the products. Typically, these log files are in BASEDIR/smarts/local/logs.

Where to go next 6-7


Where to go nextEMC Smarts products must be configured before they can perform useful analysis and provide information to operators. To continue deploying the EMC Smarts Service Assurance Management Suite, perform the following tasks:

1. Configure the Adapter Platform, as described in the EMC Smarts Service Assurance Manager Adapter Platform User’s Guide.

2. Configure third-party adapters, as described in the guide for a specific adapter.

3. Install permanent licenses, as described in the EMC Smarts System Administration Guide.

4. Configure security, as described in the EMC Smarts System Administration Guide.

5. Start the Global Console, as described in the EMC Smarts Service Assurance Manager Operator’s Guide.

6. Configure the Global Manager to receive notifications from the Domain Managers, as described in the EMC Smarts Service Assurance Manager Configuration Guide.



Manually Installing Services A-1

A

If you did not start components of the product suite as services when you installed the EMC Smarts Service Assurance Manager, you may install services manually. Services are programs that, once started, are generally intended to run continuously. Components installed as services start automatically upon system reboot; those not installed as services (manual processes or disabled processes) require that you issue commands to start and stop them as necessary.

◆ Broker..................................................................................................A-3◆ Service Assurance Manager ............................................................A-4

Typical reasons to install products as services include the following conditions:

◆ During installation of the suite, you choose to start product components manually and now want to run the components as services.

◆ Multiple instances of a single product component running as a service are required. During installation, you can install only a single instance of a product component as a service.

To install a product component as a service, enter the appropriate sm_service install command.

For components that are not installed as services, you need to install them either as services (--startmode=runonce) or manual processes (--startmode=manual) with sm_service, and start them as needed with the sm_service start command. (See “Start EMC Smarts services” on page 6-4 for information.)

Manually InstallingServices

A-2 EMC Smarts Service Assurance Management Suite Installation Guide

Manually Installing Services

For a complete description of the command syntax, see the EMC Smarts System Administration Guide.

Broker A-3


BrokerAn EMC Smarts client application, such as a console or an adapter, utilizes the broker to determine where EMC Smarts servers are running.

The default options for the broker and its values are:

/opt/InCharge7/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-broker--startmode=runonce --description="EMC Smarts Broker"--env=SM_CLIENTCONNECT=brokerConnect.conf/opt/InCharge7/SAM/smarts/bin/brstart--port=426--output--restore=/opt/InCharge7/SAM/smarts/local/repos/broker

/broker.rps

The value for <PORT> is configured during installation.



Service Assurance Manager

SAM Server (Global Manager)/BIMThe Service Assurance Manager Server (that includes EMC Smarts Business Impact Manager, if licensed) monitors and manages multiple distributed domains.

The default options for the SAM Server and their values are:

▲/opt/InCharge7/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-sam-server--startmode=runonce --description="EMC Smarts Service Assurance Manager

Server"/opt/InCharge7/SAM/smarts/bin/sm_server --name=INCHARGE-SA --config=ics --port=0 --ignore-restore-errors --output▼

Note: ▲▼Indicates that this command must be typed as one line. Separate each option with a space when typing the command.

SAM Adapter PlatformThe SAM Adapter Platform provides open integration with third-party applications.

The default options for the SAM Adapter Platform and their values are:

/opt/InCharge7/SAM/smarts/bin/sm_service install --force--unmanaged--name=ic-icoi-server--startmode=runonce --description="EMC Smarts SAM Adapter Platform Server"/opt/InCharge7/SAM/smarts/bin/sm_server --name=INCHARGE-OI --config=icoi --port=0 --ignore-restore-errors

Service Assurance Manager A-5


--output

Business DashboardThe default options for the EMC Smarts Business Dashboard and their values are:

/opt/InCharge7/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-business-dashboard--startmode=runonce --description="EMC Smarts Servlet Engine"/opt/InCharge7/SAM/smarts/bin/sm_tomcat --output start

Syslog AdapterThe EMC Smarts Syslog Adapter tails or parses the contents of any system log file, and generates notifications to the Global Manager based on the contents of the file.

The default options for the Syslog Adapter and their values are:

/opt/InCharge7/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-syslog-adapter--startmode=runonce --description="EMC Smarts Syslog Adapter" /opt/InCharge7/SAM/smarts/bin/sm_adapter --name=SYSLOG-INCHARGE-OI --rserver=INCHARGE-OI --tail=/var/log/syslog --model=sm_system --model=sm_actions --output --rules=icoi-syslog/syslog_mgr.asl

SNMP Trap AdapterThe EMC Smarts SNMP Trap Adapter collects and parses SNMP traps, and generates notifications to the Global Manager based on the contents of the traps.

The default options for the Trap Adapter and their values are:



/opt/InCharge7/SAM/smarts/bin/sm_service install --force--unmanaged--name=ic-trapd-receiver--startmode=runonce --description="EMC Smarts SNMP Trap Adapter"/opt/InCharge7/SAM/smarts/bin/sm_trapd --name=TRAP-INCHARGE-OI --server=INCHARGE-OI --config=icoi --port=162 --seed=seedfile --model=sm_actions --output --rules=icoi-trapd/trap_mgr_parse.asl

UNIX Procedures for CD-ROMs B-1

B

As a reference, this chapter includes UNIX commands and examples used when installing or upgrading the suite.

◆ Mounting the CD-ROM ................................................................... B-2

UNIX Procedures forCD-ROMs

B-2 EMC Smarts Service Assurance Management Suite Installation Guide

UNIX Procedures for CD-ROMs

Mounting the CD-ROM1. Insert the CD-ROM into the CD-ROM drive.

2. If the CD-ROM is automatically mounted, continue to step 3. Otherwise, select the appropriate mount command as shown in Table B-1.

3. Change to the CD-ROM directory by entering the appropriate command from Table B-2.

Table B-1 Mounting the CD-ROM for UNIX operating systems

Operating System Commands and Examples

Solaris Syntax: # mount -o ro -F hsfs <DEVICE> /mntExample: # mount -o ro -F hsfs /dev/dsk/c0t6d0s0 /mnt

HP-UX Syntax: # mount -ocdcase -o ro -F cdfs <DEVICE> /mnt/cdrom

Example: # mount -ocdcase -o ro -F cdfs /dev/cdrom /mnt/cdrom

Linux Syntax: # mount <DEVICE>Example: # mount /dev/cdrom /mnt/cdrom

Where <DEVICE> is the mount point for your CD-ROM drive.

Table B-2 Changing to the CD-ROM Directory in Unix operating systems

Operating System Command

Solaris If Volume Manager (VM) is running: # cd /cdrom/<suite>_<version>_<build>/suiteIf VM is not running: # cd /mnt/suite

HP-UX # cd /mnt/cdrom/suite

Linux If Automount is running: # cd /cdrom/<suite>_<version>_<build>/suiteIf Automount is not running: # cd /mnt/cdrom/suite

Where: <suite> is the product suite, for example, NPM, IP, MPLS, or SAM.<version> is the release version, for example, 1_1_0 or 6_2_0.<build> is a build number, for example, 6219 or 23922.

Manually Starting Products C-1

C

This chapter includes the following sections:

◆ Start products in native mode (UNIX only) .................................. C-2

Manually StartingProducts

C-2 EMC Smarts Service Assurance Management Suite Installation Guide

Manually Starting Products

Start products in native mode (UNIX only)If any products were not installed as services in UNIX, you can manually start them. EMC Corporation does not recommend using this method in a production environment, but it can be useful for testing. To start a product, enter the appropriate sm_server command from Table C-3. For a complete description of the command syntax, see the EMC Smarts System Administration Guide.

Table C-3 Starting EMC Smarts Service Assurance Management Suite Products in Native Mode

Commands for starting EMC Smarts Service Assurance Manager products in native mode

Product Command (▼▲ indicates the command must be typed on one line.)

Broker ▼ # BASEDIR/smarts/bin/brstart --port=426 --output ▲

Global Manager

▼ # BASEDIR/smarts/bin/sm_server --name=INCHARGE-SA --config=ics --port=0 --output --daemon ▲

Understanding the sm_edit Utility D-1

D

As part of the EMC Smarts deployment and configuration process, you 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) that contain encrypted passwords. Original versions of these files are installed into appropriate subdirectories under the BASEDIR/smarts/ directory.

Examples:

• The original versions of the Global Manager configuration files on UNIX are installed to /opt/InCharge7/SAM/smarts/conf/ics

• The original versions of the Console configuration files on Windows are installed on C:\InCharge7\SAM\smarts\conf\console

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.

Examples:

• A modified ics.conf file on UNIX should be saved to /opt/InCharge7/SAM/smarts/local/conf/ics

• A modified properties.conf file on Windows should be saved to C:\InCharge7\SAM\smarts\local\conf\console.

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, Smarts software then searches appropriate nonlocal directories.

Understanding thesm_edit Utility

D-2 EMC Smarts Service Assurance Management Suite Installation Guide

Understanding the sm_edit Utility

To facilitate proper file editing, EMC Corporation provides the sm_edit utility with every 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. 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 to edit under BASEDIR/smarts. If multiple Smarts products are running on the same host, invoke sm_edit from the bin directory of the product suite with the files to edit.

Example:

To edit the configuration file for the Global Manager, 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.

The EMC Smarts System Administration Guide provides additional information about the sm_edit utility.