emc ionix service assurance management suite … notif editor, or both.....40 where to go...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

EMC® Ionix™

Service Assurance Management SuiteVersion 8.1

Installation GuideP/N 300-010-066

REV A03

EMC Ionix Service Assurance Management Suite Version 8.1 Installation Guide2

Copyright © 1996 - 2010 EMC Corporation. All rights reserved.

Published June 2010

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 regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

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 Ionix Service Assurance Management Suite Version 8.1 Installation Guide 3

Preface

Chapter 1 OverviewSuite contents..................................................................................... 16

Default installation directories .................................................18Product and release compatibility.................................................. 19Installation tasks overview.............................................................. 20Migration tasks overview ................................................................ 21Uninstallation tasks overview......................................................... 22

Chapter 2 RequirementsOperating system requirements ..................................................... 24Hardware requirements................................................................... 26Web Console and Business Dashboard requirements ................. 29

Java Web Start requirements for Web Console ......................30

Chapter 3 Installing the Service Assurance Management SuiteBefore installation ............................................................................. 32

Determine the location of the EMC Smarts Broker ...............32Install the Service Assurance Management Suite ........................ 33

Installing the Service Assurance Manager Server .................34Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both....................................................40Where to go next .........................................................................46

Chapter 4 Performing a Migration

Contents


Contents

Overview of migration tasks........................................................... 48

Chapter 5 Verifying the InstallationObtain and install a temporary license file ................................... 50Start EMC Smarts services............................................................... 51

Starting services on UNIX......................................................... 51Starting services on Windows .................................................. 52

Start EMC Smarts programs ........................................................... 53Starting programs on UNIX...................................................... 53Starting programs on Windows ............................................... 54

Start ITOps NOTIF ........................................................................... 55Verify the EMC Smarts product status .......................................... 58............................................................................................................. 59

Chapter 6 Uninstalling Service Assurance Management SuiteBefore uninstallation ........................................................................ 62

Remove manually installed services ....................................... 62Determine order for removing products (UNIX only) ......... 62Uninstall when the same product suite is installed twice (Windows only) .......................................................................... 63Detect and stop EMC Smarts programs.................................. 63Uninstall the FLEXnet License Server ..................................... 67

Uninstalling Service Assurance Management Suite.................... 69Uninstall using Wizard mode................................................... 69Uninstall using CLI mode ......................................................... 70Uninstall using unattended mode ........................................... 71

Disabling ITOps NOTIF................................................................... 73

Appendix A Manually Installing ServicesOverview............................................................................................ 76Service Assurance Management Suite services............................ 77

EMC Smarts Broker................................................................... 77Service Assurance Manager (Global Manager)..................... 78Business Impact Manager server ............................................. 79Adapter Platform....................................................................... 80Business Dashboard .................................................................. 81Syslog Adapter........................................................................... 82SNMP Trap Adapter ................................................................. 83

Appendix B Procedures for CD-ROMs

5EMC Ionix Service Assurance Management Suite Version 8.1 Installation Guide

Contents

Mounting a CD-ROM on UNIX systems ....................................... 86Loading a CD-ROM on Windows................................................... 88


Contents


Title Page

1 Interoperability chart ...................................................................................... 192 Installation requirements and tasks.............................................................. 203 Migration requirements and tasks................................................................ 214 Uninstallation requirements and tasks ........................................................ 225 Supported operating system for the suite ................................................... 246 Required operating system patches.............................................................. 257 Typical hardware for the equipment tiers ................................................... 268 Required disk space for the Service Assurance Manager server ............. 269 Required disk space for the Service Assurance Manager console ........... 2710 CPU, memory, data disk space requirements............................................. 2711 Server setup command syntax for Wizard mode....................................... 3412 Server setup command syntax for CLI-mode ............................................. 3713 Navigation keys............................................................................................... 3814 Server setup command syntax for unattended mode................................ 3915 Console setup command syntax for Wizard mode.................................... 4116 Console setup command syntax for CLI-mode .......................................... 4317 Navigation keys............................................................................................... 4418 Console setup command syntax for unattended mode............................. 4519 Next steps for detecting and stopping programs ....................................... 6520 Mounting the CD-ROM for UNIX operating systems............................... 8621 Changing to the CD-ROM directory in UNIX operating systems ........... 87

Tables


Tables


Preface

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

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

Audience This document is part of the Service Assurance Management Suite documentation set, and is intended for use by system administrators and integrators responsible for installing the EMC Ionix Service Assurance Management Suite.

EMC Ionix ServiceAssurance

Management Suiteinstallation directory

In this document, the term BASEDIR represents the location where EMC Ionix software is installed.

For UNIX, this location is:

◆ /opt/InCharge<n>/<productsuite> (for the Service Assurance Manager Server)

◆ /opt/InCharge<n>/CONSOLE (for the Service Assurance Manager Console)

For Windows, this location is:

◆ C:\InCharge<n>\<productsuite> (for the Service Assurance Manager Server)

◆ C:\InCharge<n>\CONSOLE (for the Service Assurance Manager Console)

10 EMC Ionix Service Assurance Management Suite Version 8.1 Installation Guide

Preface

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

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

The EMC Smarts System Administration Guide provides information about the directory structure of the EMC Smarts software.


Management Suite

The EMC Ionix Service Assurance Management Suite includes the following products:

◆ Service Assurance Manager (Global Manager) and Maintenance and Business Impact Manager

◆ Global Console

◆ Business Dashboard and Web Console

◆ ITOps Notification Module (ITOps NOTIF)

◆ SAM Native Adapters:

• Service Assurance Manager Notification Adapters (E-Mail Notifier Adapter, Script Notifier Adapter, SNMP Trap Notifier Adapter, Log File Notifier Adapter)

• Adapter Platform (Adapter Platform server, Syslog Adapter, SNMP Trap Adapter, sm_ems command-line interface)

• XML Adapter

Relateddocumentation

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


Preface

EMC Ionix documentationReaders of this guide may find the following related documentation helpful:

◆ 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

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


Management Suitedocumentation

The following documents are relevant to users of the EMC Ionix Service Assurance Management Suite:

◆ EMC Ionix Service Assurance Manager Introduction

◆ EMC Ionix Service Assurance Management Suite Deployment Guide

◆ EMC Ionix Service Assurance Management Suite Installation Guide

◆ EMC Ionix Service Assurance Manager Operator Guide

◆ EMC Ionix Service Assurance Manager Configuration Guide

◆ EMC Ionix Service Assurance Manager Dashboard Configuration Guide

◆ EMC Ionix Business Impact Manager User Guide

◆ EMC Ionix Service Assurance Manager Failover System User Guide

◆ EMC Ionix ITOps Notification Module User Guide

◆ EMC Ionix ITOps Notification Module Cisco Syslog Processing Adapter Installation and User Guide

The EMC Smarts Documentation Catalog provides documentation resources for other EMC Smarts product suites.

message URL http://Powerlink.EMC.com




Preface

Conventions used inthis document

EMC uses the following conventions for special notices.

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

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment.

IMPORTANT!An important notice contains information essential to software or hardware operation.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system calls, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text


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

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

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

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

http://Powerlink.EMC.com

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

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

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

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

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

... Ellipses indicate nonessential information omitted from the example

http://Powerlink.EMC.com


Preface

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

http://EMC.com/contact

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.

Overview 15

1

This chapter describes the EMC Ionix Service Assurance Management Suite products, compatibility with other EMC Smarts products, and installation tasks.

This chapter consists of the following topics:

◆ Suite contents...................................................................................... 16◆ Product and release compatibility ................................................... 19◆ Installation tasks overview............................................................... 20◆ Migration tasks overview ................................................................. 21◆ Uninstallation tasks overview.......................................................... 22

Overview


Overview

Suite contentsThe EMC® Ionix® Service Assurance Management Suite includes the following products:

◆ Service Assurance Manager

The EMC Smarts Service Assurance Manager product includes the following components:

• Global Manager

• EMC Smarts Broker

• EMC Smarts MBIM — Maintenance and Business Impact Manager Server

• Generic notification adapters such as Log File, SNMP Trap, Script, and email

Note: 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.

◆ ITOps Notification Module

The ITOps Notification Module (ITOps NOTIF) augments EMC Ionix solutions with event management features that are configured through a graphical user interface (the ITOps NOTIF Editor). ITOps NOTIF enables the user to easily optimize the flow of events and notifications sent through any EMC Ionix system. ITOps NOTIF can be installed on a SAM server and/or an

Suite contents 17

Overview

Adapter Platform server. The internal event and notification processing features of the standard SAM Adapter Platform are replaced by ITOps NOTIF.

Note: ITOps NOTIF functionality and architecture is discussed in the EMC Ionix ITOps Notification Module User Guide.

◆ ITOps Notification Module Cisco Syslog Processing Adapter

The ITOps Notification Module Cisco Syslog Processing Adapter (referred to as the ITOps NOTIF Cisco Syslog Adapter) replaces the log file processing features of the standard Syslog Adapter. The ITOps NOTIF Cisco Syslog Adapter processes log file information into useful notifications, with or without the use of ASL scripts.

Note: The EMC Ionix ITOps Notification Module Cisco Syslog Processing Adapter Installation and User Guide provides additional information on this adapter.

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

◆ XML Adapter

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


Overview

Default installation directoriesThe EMC Ionix Service Assurance Management Suite is distributed on two CD-ROMs:

◆ Service Assurance Manager Server Suite

◆ Service Assurance Manager Console Suite

Note: The Service Assurance Manager Server can only be installed on a 64-bit processor and runs as a 64-bit application. The Service Assurance Manager Console can be installed on a 64-bit processor, but runs as a 32-bit application.

The suite is also available for download from the Powerlink® website. The Service Assurance Manager Server is installed by default to the following subdirectories under the InCharge8 root directory:

◆ /opt/InCharge8/SAM (for UNIX)

◆ C:\InCharge8\SAM (for Windows)

The Service Assurance Manager Console is installed by default to the following subdirectories under the InCharge8 root directory:

◆ /opt/InCharge8/CONSOLE (for UNIX)

◆ C:\InCharge8\CONSOLE (for Windows)

Product and release compatibility 19

Overview

Product and release compatibilityThe Service Assurance Management Suite is compatible with the versions of these products in Table 1 on page 19.

Table 1 Interoperability chart

EMC Smarts product suite Versions

EMC Server Configuration Manager 5.0

EMC Server Manager 1.1

EMC Smarts Application Connectivity Monitor 2.2

EMC Smarts Application Discovery Manager 6.0

EMC Smarts IP Management Suite 6.5.x, 7.0.3.x

Note: When running 6.5.3.x, SAM 8.0 performance enhancements are not realized.

EMC Smarts IPv6 Management Suite 2.0

EMC Smarts IT Performance Reporter 2.0

EMC Smarts MPLS Management Suite 2.2

EMC Smarts Multicast Manager 1.2

EMC Smarts Network Protocol Management Suite 2.0.1.0

EMC Smarts Optical Transport Management Suite 5.0

EMC Smarts Service Assurance Management Adapter Suite 1.2.0.7 or higher

EMC Ionix Service Assurance Management Suite 7.0, 7.1, 7.2, 8.0

EMC Smarts Storage Insight for Availability 2.1

EMC Smarts VoIP Availability Management Suite 3.0


Overview

Installation tasks overviewTo install the Service Assurance Management Suite, you need to satisfy or perform the tasks listed in Table 2 on page 20.

Table 2 Installation requirements and tasks (page 1 of 2)

Before you install:

The Broker and FLEXnet license should be installed, configured, and operated.

EMC Smarts System Administration Guide for license information

Review the important release issues for the Service Assurance Management Suite.

EMC Ionix Service Assurance Management Suite Release NotesEMC Ionix ITOps Notification Module Release Notes

Obtain an evaluation or permanent license for the products you will install from the Service Assurance Management Suite.

EMC Smarts System Administration Guide for license information“Obtain and install a temporary license file” on page 50

Determine if the products are supported on your platform. “Operating system requirements” on page 24

Determine if your system meets the hardware requirements.

“Hardware requirements” on page 26

Installation method:

Install the Service Assurance Manager Server. Choose one of the following installation methods:• “Install using Wizard mode” on page 34• “Install using CLI mode” on page 37, UNIX only• “Install using unattended mode” on page 38

Install the Service Assurance Manager Console. • “Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both” on page 40

Installation tasks overview 21

Overview

After you install:

Save your license in the proper location:• Evaluation license — Save smarts.lic to the

BASEDIR/smarts/local/conf directory. If your evaluation license has a different name, rename it to smarts.lic.

• Permanent license — The EMC Smarts System Administration Guide describes the procedures to use.

EMC Smarts System Administration Guide

If you installed the products as services, start them for the first time.

• “Starting services on UNIX” on page 51• “Starting services on Windows” on page 52

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

Table 2 Installation requirements and tasks (page 2 of 2)


Overview

Migration tasks overviewTo migrate to Service Assurance Management Suite, you need to satisfy or perform the tasks listed in Table 3 on page 21.

Table 3 Migration requirements and tasks

Before you migrate:

Review the release notes for important issues. EMC Ionix Service Assurance Management Suite Release Notes

Obtain a permanent license for the products you will install. EMC Smarts System Administration Guide for license information

Determine if the products are supported for your platform. “Operating system requirements” on page 24

Determine if your system meets the hardware requirements. “Hardware requirements” on page 26

Installation and migration:

Install the Service Assurance Manager Server. Choose one of the following installation methods:• “Install using Wizard mode” on page 34• UNIX only, “Install using CLI mode” on page 37• “Install using unattended mode” on page 38

Install the Service Assurance Manager Console. “Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both” on page 40

Migrate configuration and repository files. “Overview of migration tasks” on page 48

After you install:

Save your license in the proper location:• Evaluation license — Save smarts.lic to the

BASEDIR/smarts/local/conf directory. If your evaluation license has a different name, rename it to smarts.lic.

• Permanent license — Use the procedures described in the EMC Smarts System Administration Guide.

EMC Smarts System Administration Guide

If you installed the products as services, start them for the first time. • “Starting services on UNIX” on page 51• “Starting services on Windows” on page 52

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

Uninstallation tasks overview 23

Overview

Uninstallation tasks overviewTo uninstall Service Assurance Management Suite, you need to satisfy or perform the tasks listed in Table 4 on page 22.

Table 4 Uninstallation requirements and tasks

Before you uninstall:

Review uninstall prerequisites: • “Remove manually installed services” on page 62• “Determine order for removing products (UNIX

only)” on page 62• “Uninstall when the same product suite is installed

twice (Windows only)” on page 63• “Detect and stop EMC Smarts programs” on

page 63• “Uninstall the FLEXnet License Server” on page 67

Uninstallation:

Uninstall the Service Assurance Management Suite: • “Uninstall using Wizard mode” on page 69• “Uninstall using CLI mode” on page 70• “Uninstall using unattended mode” on page 71• “Disabling ITOps NOTIF” on page 73

Requirements 23

2

This chapter describes the operating system requirements and hardware requirements for the EMC Service Assurance Management Suite.


◆ Operating system requirements....................................................... 24◆ Hardware requirements .................................................................... 26◆ Web Console and Business Dashboard requirements .................. 29◆ Web Console and Business Dashboard requirements .................. 29

Requirements


Requirements

Operating system requirementsTable 5 on page 24 summarizes the operating system platforms that are supported by each product in the EMC Service Assurance Management Suite.

Table 5 Supported operating system for the suite

Operating system Supported version

Red Hat Enterprise Linux AS 4, AS 5

Note: The SAM server must be installed on a 64-bit operating system. The SAM Console can be installed on either a 32-bit operating system or a 64-bit operating system.

Solaris 9, 10, Solaris 10 native Sun Zones

Windows Windows 2003 Enterprise Edition R2Windows 2003 Enterprise Edition SP2Windows 2008 Enterprise EditionWindows XP Professional SP2 (console only)Windows Vista (console only)

Note: The SAM server must be installed on a 64-bit Operating System. The SAM Console can be installed on either a 32-bit operating system or a 64-bit operating system.

VMware ESX Server 3.5.x Windows Server 2003 Enterprise Edition SP2Windows 2008 Enterprise EditionRed Hat Enterprise Linux AS 4 Update 3

Operating system requirements 25

Requirements

Recommended patch levelsTable 6 on page 25 summarizes the operating system patches required for the Service Assurance Management Suite.

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 6 Required operating system patches

Operating system Patches

Red Hat Enterprise Linux AS 4

compat-libstdc++-296-2.96-138.i386.rpm installed at: /usr/lib directory

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

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

111722-04 libm patch

118305-09 (patch that fixes an ACK storm bug in Solaris that prevents it from transmitting TCP urgent data packet)

118335-06 (patch that fixes a Sockfs bug)

Solaris 10 119963-08 C++ patch120011-14 (TCP/IP patch)

Note: EMC Corporation recommends editing /etc/system to include the following line; then reboot your system: set ip:do_tcp_fusion = 0.

Windows Server 2003 Enterprise Edition

Hotfix KB927493

Hotfix KB947369


Requirements

Hardware requirementsThe hardware requirements for the EMC Service Assurance Management Suite are as follows.

Table 7 on page 26 lists typical hardware for several equipment tiers and operating systems. Table 8 on page 26 represents the minimum hard disk storage requirements.

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

Table 8 on page 26 lists disk space requirements for installing the Service Assurance Manager server.

Table 7 Typical hardware for the equipment tiers

Operating system

Platform equipment tier

Small (1–2 low end CPUs, 2 GB RAM)

Medium (2 CPUs, 4 GB RAM)

Large (2 CPUs, 4 GB RAM)

Extra large(2–4 CPUs, 4–8 GB RAM)

Red Hat Enterprise Linux

Any vendor, 1-2 Xeon 2.8 GHz

Any vendor, 2 Xeon 2.8 GHz



Solaris UltraSPARC-T1 (T2000)

UltraSPARC-T2 (T5220)

SPARC64 VII (M40000)

SPARC64 VII (M4000)

Windows Server 2003 Enterprise Edition

Any vendor, 1-2 Xeon 2.8 GHz




Table 8 Required disk space for the Service Assurance Manager server

Platform Disk space

Solaris 9 and 10 730 MB

Red Hat Enterprise Linux AS 4 and 5 475 MB

Windows Server 2003 Enterprise Edition SP2, 2008 550 MB

Hardware requirements 27

Requirements

Table 9 on page 27 lists disk space requirements for installing the Service Assurance Manager console.

Table 10 on page 27 lists minimum requirements for CPUs, memory, and data disk space used by the software for writable files such as logs, repository files, and output files.

Note: CPU means the number of physical CPU cores and not the number of CPUs displayed when hyperthreading is activated.

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

Table 9 Required disk space for the Service Assurance Manager console

Platform Disk space

Solaris 9 and 10 485 MB

Red Hat Enterprise Linux AS 4 and 5 365 MB

Windows 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition SP2, Windows Server 2008, Windows Vista, and Windows XP

300 MB

Table 10 CPU, memory, 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 Not applicable

Global Console, Web Console, and Business Dashboard

1 256 MB 150 MB

EMC Smarts Service Assurance Manager Adapter Platform

1 512 MB 100 MB each

Syslog Adapter 1 256 MB 50 MB each

SNMP Trap Adapter 1 256 MB 50 MB each

XML Adapter 1 256 MB See Note below


Requirements

If you are installing more than one product, then your system must meet the products’ total memory and data disk space requirements. Table 8 on page 26 defines required disk space and Table 10 on page 27 lists CPU, memory, and data disk space requirements.

Web Console and Business Dashboard requirements 29

Requirements

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

◆ EMC Smarts Web Console

or

◆ EMC Smarts Business Dashboard

Note: Tomcat Servlet Engine version 6.0.18 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 want to use the Web Console, require the following software:

◆ One of the following Web browsers:

• Internet Explorer 6.0 with Service Pack 1

• Internet Explorer 7.0

• Firefox 2

• Browser that supports Java JRE 1.5.x or Java JRE 1.6

Note: Only browsers running on Linux, Solaris, and Windows operating systems are supported.

◆ 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 (or 6.0) which includes the 1.5.x (1.6.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.


Requirements

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

• For all platforms, download it from the Sun Microsystems website 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 Tomcat Servlet Engine is installed and 8080 refers to the default port for Tomcat.

The EMC Ionix Service Assurance Manager Dashboard Configuration Guide provides information about using the Web Console.

Installing the Service Assurance Management Suite 31

3

This chapter describes how to install the EMC Service Assurance Management Suite.


◆ Before installation .............................................................................. 32◆ Install the Service Assurance Management Suite ......................... 33

Installing theService AssuranceManagement Suite


Installing the Service Assurance Management Suite

Before installationBefore installing EMC Service Assurance Management Suite, determine the location of the EMC Smarts Broker. “Determine the location of the EMC Smarts Broker” on page 32 provides additional information.

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.

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.

Install the Service Assurance Management Suite 33


Install the Service Assurance Management SuiteThis section describes how to install Service Assurance Management Suite into a new directory structure. The Service Assurance Management Suite is distributed on two CD-ROMs, one CD-ROM containing the:

◆ Service Assurance Manager Server Suite

Note: The following products can be installed as services: EMC Smarts Broker, EMC Smarts Service Assurance Manager Server, EMC Smarts Business Impact Manager, EMC Smarts Service Assurance Manager Adapter Platform Server, EMC Smarts SNMP Trap Adapter, EMC Smarts Syslog Adapter.

◆ Service Assurance Manager Console Suite

Note: The following product can be installed as services: EMC Smarts Servlet Engine.

The Service Assurance Management Suite is also available for download from Powerlink.

Before starting the installation, you must do one of the following:

◆ Insert the CD-ROM into the optical drive of the host system. Appendix B, “Procedures for CD-ROMs,” describes how to access the optical drive for various operating systems.

◆ Copy the download to the host system where you will perform the installation.

Note: 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. Be patient. Do not eject/reinsert the CD to start a second install process.



Installing the Service Assurance Manager ServerThis section describes the steps for installing the Service Assurance Manager Server.

Install using Wizard modeWizard mode provides a graphical user interface to the installation program for UNIX and Windows platforms.

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 in must be configured to run the X Window System. Before starting the installation program using the Wizard mode, verify that the X Window System is running.

Running Wizard modeTo install the Service Assurance Manager server:

1. Run the Setup command appropriate for the operating system listed in Table 11 on page 34.

The InstallShield wizard dialog box appears and closes. The Shutdown EMC Smarts Programs dialog box and the Welcome screen appear.

2. Click OK in the Warning dialog box.

If stopping services is necessary, you will be prompted with specific instructions later in the installation process.

3. Click Next in the Welcome screen.

Next is disabled if you do not have administrative privileges and a message also appears. To install, you must restart the installation with appropriate privileges.

Table 11 Server setup command syntax for Wizard mode

Operating system Setup command

Linux # ./setup-SAM-8_1_0_0-linux64.bin# ./setup-SAM-8_1_0_0-linux-rhAS50-64.bin # (for Linux A5 platforms)

Solaris # ./setup-SAM-8_1_0_0-sol64.bin

Windows setup-SAM-8_1_0_0-win64.exe



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

Select Install the product to a new directory.

Note: This screen does not appear 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/InCharge8 (on UNIX)

• C:\InCharge8 (on Windows)

If you specify a directory, the directory name cannot contain spaces. If the specified directory does not exist, it will be created. If you do not have write privileges, an error message appears.

7. In the Setup screen, select:

• Complete to install the Service Assurance Manager Server. Click Next.

• Custom to install a specific product. Click Next:

a. Clear products that you do not want to install (by default, all products are selected).

b. Click Next.

8. The Services Selection screen appears. Select the products that you want to install as services and click Next. If you do not install services at this point, you will need to install them manually later.

If you have an older version of a service running on the host, you must stop that service before installing a new version of the service.



Note: When installed as services, EMC Smarts products start automatically when the system starts up. 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. Specify the EMC Smarts Broker:

• If you are installing the Broker as a service, specify the port. The hostname defaults to localhost.

• If the Broker is already running on this host, keep the default values.

• If the Broker is running on another host, specify the hostname of that system and the port the Broker uses.

Click Next to continue.

10. If you want to migrate from an earlier 7.x version, you can migrate your existing repository directory, including subdirectories and your existing configuration files. Type the path to your existing SAM 7.x installation, for example, BASEDIR/SAM.


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 and the Installation Progress screen appears.

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. “Where to go next” on page 46 provides details on post-installation tasks.



Install using CLI modeCLI mode provides a text-based method for invoking 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, invoke the appropriate Setup command listed in Table 12 on page 37.

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,” type y or Y; to reply “no,” type 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 5 to repeat the prompt and select the correct value. Arrow keys and the Backspace key are not supported.

Table 12 Server setup command syntax for CLI-mode

Operating system Executable

Linux ./setup-SAM-8_1_0_0-linux64.bin -console./setup-SAM-8_1_0_0-linux-rhAS50-64.bin -console (for Linux A5 platforms)

Solaris ./setup-SAM-8_1_0_0-sol64.bin -console



To navigate between each step, use the keys defined in Table 13 on page 38.

“Where to go next” on page 46 provides details on post-installation tasks.

Install using unattended modeUnattended mode is supported for all operating systems but separate response files are needed for UNIX and Windows systems. This method 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. Manual intervention is not necessary after you execute the Setup command.

Note: The unattended install mode does not automatically copy repository files if you are migrating from a previous version of the software. You must manually copy the repository and configuration files after installation to complete the migration.

Table 13 Navigation keys

Key Operation

1 Next, continue to the next step

2 Previous, go back to the previous step

3 Cancel, terminate the program

5 Redisplay, repeat the step

0 Accept the marked ([X]} menu choice



Running unattended modeFrom a command line shell, run the appropriate Setup command listed in Table 14 on page 39.

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

./setup-SAM-8_1_0_0-sol64.bin -options /opt/home/SAM_SUITE-response.txt

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 settings to:

◆ Support Windows operating systems

◆ Specify a different Broker location

To modify the 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 14 Server setup command syntax for unattended mode


Linux # ./setup-SAM-8_1_0_0-linux64.bin -options <path>/<suite>-response.txt # ./setup-SAM-8_1_0_0-linux-rhAS50-64.bin <path>/<suite>-response.txt (for Linux A5 platforms)

Solaris # ./setup-SAM-8_1_0_0-sol64.bin -options <path>/<suite>-response.txt

Windows setup-SAM-8_1_0_0-win64.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_SUITE, IP_NETWORK_SUITE, MPLS_SUITE, or SAM_SUITE.



2. Using a text 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.

Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both

This section describes the steps for installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both the Service Assurance Manager Console and the ITOps NOTIF Editor.

Install using Wizard modeWizard mode provides a graphical user interface to the installation program for UNIX and Windows platforms.


Running Wizard modeTo install the Service Assurance Manager Console:



1. Run the Setup command appropriate for the operating system listed in Table 15 on page 41.

The InstallShield wizard dialog box displays and closes. The Shutdown EMC Smarts Programs dialog box and the Welcome screen appear.

2. Click OK in the Warning dialog box.

If stopping services is necessary, you will be prompted with specific instructions later in the installation process.

3. Click Next in the Welcome screen.

Next is disabled if you do not have administrative privileges and a message also appears. To install, you must restart the installation with appropriate privileges.

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

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/InCharge8 (on UNIX)

• C:\InCharge8 (on Windows)

If you specify a directory, the directory name cannot contain spaces. If the specified directory does not exist, it will be created. If you do not have write privileges, an error message appears.

Table 15 Console setup command syntax for Wizard mode

Operating system Setup command

Linux # ./setup-CONSOLE-8_1_0_0-linux.bin

Solaris # ./setup-CONSOLE-8_1_0_0-sol.bin

Windows setup-CONSOLE-8_1_0_0-win.exe



7. In the Setup screen, select one of the following:

• Complete to install all Service Assurance Manager Console components. Click Next.

• Custom to install a specific product. Click Next.

a. Clear products that you do not want to install (by default, all products are selected). From this screen, you may choose to install either the Global Console or the ITOps NOTIF Editor.

b. Click Next.

8. In the type of Global Console installation screen, select:

• Global Console, Web Console, and Business Dashboard. Click Next.

• Global Console. Click Next.

9. The Services Selection screen appears. Select the products that you want to install as services and click Next. If you do not install services at this point, you will need to install them manually later.

If you have an older version of a service running on the host, you must stop that service before installing a new version of the service.

Note: When installed as services, EMC Smarts products start automatically when the system starts up. 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. Specify the EMC Smarts Broker:

• If the Broker is already running on this host, keep the hostname default value and change the Broker port accordingly if it is not running on port 426.

• If the Broker is running on another host, specify the hostname of that system and the port the Broker uses.




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 and the Installation Progress screen appears.

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. “Where to go next” on page 46 provides information on post-installation tasks.

Install using CLI modeCLI mode provides a text-based method for invoking 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, invoke the appropriate Setup command listed in Table 16 on page 43.

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,” type y or Y; to reply “no,” type n or N. Do not press Delete; this causes the process to terminate with an error message.

Table 16 Console setup command syntax for CLI-mode


Linux ./setup-CONSOLE-8_1_0_0-linux.bin -console

Solaris ./setup-CONSOLE-8_1_0_0-sol.bin -console



◆ 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 defined in Table 17 on page 44.

“Where to go next” on page 46 provides details on post-installation tasks.

Install using unattended modeUnattended mode is supported for all operating systems but separate response files are needed for UNIX and Windows systems. This method 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. Manual intervention is not necessary after you execute the Setup command.

Table 17 Navigation keys

Key Operation

1 Next, continue to the next step

2 Previous, go back to the previous step

3 Cancel, terminate the program

5 Redisplay, repeat the step

0 Accept the marked ([X]} menu choice



Running unattended modeFrom a command line shell, run the appropriate Setup command listed in Table 18 on page 45.

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

./setup-CONSOLE-8_1_0_0-sol.bin-options /opt/home/SAM_CONSOLE_SUITE-response.txt

Modifying the response fileThe Console suite has a response file located on the CD-ROM in the /utils directory. Its naming convention is SAM_CONSOLE_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 settings to:

◆ Support Windows operating systems

◆ Specify a different Broker location

To modify the 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 a text editor, modify the values for the command line options in the response file:

Table 18 Console setup command syntax for unattended mode


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

Solaris # ./setup-CONSOLE-8_1_0_0-sol.bin -options <path>/<suite>-response.txt

Windows setup-CONSOLE-8_0_1_0-win.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_SUITE, IP_NETWORK_SUITE, MPLS_SUITE, SAM_SUITE, or SAM_CONSOLE_SUITE.



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

Where to go nextAfter the installation is finished, you may need to complete the following tasks:

◆ Chapter 4, “Performing a Migration,” describes additional tasks if you are migrating from a previous version of the suite.

◆ Chapter 5, “Verifying the Installation,” describes tasks for verifying the proper installation of the software and starting services.

Performing a Migration 47

4

This chapter describes steps for migrating from previous a version of EMC Service Assurance Management Suite.


◆ Overview of migration tasks ............................................................ 48

Performing a Migration


Performing a Migration

Overview of migration tasksService Assurance Management Suite 8.1 can be migrated from the following older version:

◆ EMC Ionix Service Assurance Management Suite 7.x

Note: The EMC Ionix Service Assurance Management Suite Migration Guide provides instructions on migrating from Service Assurance Management Suite 7.x.

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 8.1 installation.

To determine your existing version level, perform the following:

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

sm_server --version

2. EMC Smarts displays the following:

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

Note: The EMC Ionix ITOps Notification Module Version 8.1 Release Notes provide information on migrating an existing NOTIF configuration to the current ITOps NOTIF release. These release notes provide information on upgrading configurations from previous NOTIF releases to ITOps NOTIF version 8.1.

Verifying the Installation 49

5

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


◆ Obtain and install a temporary license file .................................... 50◆ Start EMC Smarts services ................................................................ 51◆ Start EMC Smarts programs............................................................. 53◆ Start ITOps NOTIF............................................................................. 55◆ Verify the EMC Smarts product status............................................ 58◆

◆

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 the evaluation license has a different name, rename it to smarts.lic.

◆ If multiple EMC Smarts product suites run on the same system, copy the license file to the BASEDIR/smarts/local/conf directory for each suite smarts.lic.

◆ If EMC Smarts product suites run on multiple systems, copy the license file to the BASEDIR/smarts/local/conf directory on each system where the 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.

The EMC Smarts System Administration Guide provides information on licensing or instructions for obtaining and installing a permanent license.

Start EMC Smarts services 51


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

EMC Corporation recommends installing Ionix Managers 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.

Starting services on UNIXVerify the status of the service daemon before starting a service.

Verifying the status of the service daemonUse the ic-serviced command to check the status of the service daemon. The path to the ic-serviced command varies by operating system.

Solaris

On Solaris systems, type the following command to verify the status of the service daemon:

/etc/init.d/ic-serviced status

IIf the sm_serviced process does not respond, the process is not running. Start the service by typing the command:

/etc/init.d/ic-serviced start

Linux

On Linux systems, type the following command to verify the status of the service daemon:

/etc/init.d/ic-serviced status

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

/etc/init.d/ic-serviced start

Starting EMC Smarts servicesTo start or stop, use the sm_service utility. Type the command from the BASEDIR/smarts/bin directory:



./sm_service start <service_name> [<service_name> ...]

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

Example of starting a service (UNIX)

The following example shows how to start the <product> service. Invoke the sm_service utility from the BASEDIR/smarts/bin directory:

For UNIX, type:

./sm_service start <service name>

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

Start EMC Smarts programs 53


Start EMC Smarts programsYou can start EMC Smarts programs from the terminal when the program is not intended to be long-running or to perform testing. EMC Corporation does not recommend using this method in a production environment.

The EMC Smarts System Administration Guide provides a complete description of the command syntax.

Starting programs on UNIXTo start a program on UNIX, invoke the command with the appropriate options from the BASEDIR/smarts/bin directory.

Starting the EMC Smarts Broker./brstart --port=426 --output

Starting a Ionix Manager▼ ./sm_server --name=<server_name>

--config=<config_directory>--port=0--ignore-restore-errors--output ▲

To run the program in the background, use the daemon option.

Note: ▼▲ indicates the command must be typed on one line.



Starting programs on WindowsTo start a program on Windows, invoke the command with the appropriate options from the C:\BASEDIR\smarts\bin directory.

Starting the EMC Smarts Brokerbrstart --port=426 --output

Starting a Ionix Manager▼ sm_server --name=<server_name>

--config=<config_directory>--port=0--ignore-restore-errors--output ▲

Note: ▼▲ indicates the command must be typed on one line.

Start ITOps NOTIF 55


Start ITOps NOTIF To start ITOps NOTIF:

1. Set an environment variable in the BASEDIR directory path to ensure that Java can be successfully started for ITOps NOTIF. In BASEDIR/smarts/local/conf/runcmd_env.sh, add the following line:

SM_JAVA_ENABLED=YES

2. Configure the SNMP Trap Adapter to use the Notif-trap_mgr_parse.asl script instead of the default trap_mgr_parse.asl script in order for ITOps NOTIF to process SNMP traps.

For example:

./sm_trapd --name=TRAP-OI --server=INCHARGE-OI --config=icoi--port=9013 --model=sm_actions --output--rules=icoi-trapd/Notif-trap_mgr_parse.asl --daemon

Note: The --daemon option only works on UNIX systems, not Microsoft Windows systems.

Any customizations made by the customer to the original trap_mgr_parse.asl file in the BASEDIR/smarts/rules/icoi-trapd directory must be incorporated into the Notif-trap_mgr_parse.asl file in the BASEDIR/smarts/rules/icoi-trapd directory.

3. Configure the Syslog Adapter to use the Notif-SysLog_mgr.asl script instead of the default SysLog_mgr.asl script in order for ITOps NOTIF to process Cisco system log files.

For example:

./sm_adapter.exe --NTsErViCeNaMe=ic-syslog-adapter --name=SYSLOG-OI --server=INCHARGE-OI --tail=/var/log/syslog --model=sm_system --model=sm_actions --output icoi-syslog/Notif-SysLog_mgr.asl

Note: One or more adapters can feed a single ITOps NOTIF server.

4. Launch the ITOps NOTIF Editor by selecting Start > Programs > InCharge 8 > ITOps NOTIF Editor.



Note: You can also launch the editor by double-clicking the NotifGui.bat file (for Windows systems) or the NotifGui.sh file (for UNIX systems) in the BASEDIR/smarts/notif/editor directory.

5. Use the ITOps NOTIF Editor to connect to the running SAM or Adapter Platform server. Select Remote > Edit a server's settings in the ITOps NOTIF Editor.

6. The Connect to a Server dialog box displays, showing the list of available Adapter Platform and SAM server connections. Choose a server from the list of available server connections in the Connect to a Server dialog box and click OK.

If no available server connections are displayed, do the following to populate the list of server connections:

a. Click the More button in the Connect to a Server dialog box. This launches the Manage Connections dialog box where you can add server connections.

b. Click the Add button in the Manage Connections dialog box.

The Input dialog box displays.

c. Enter a connection reference name (for example, “Remote ITOps NOTIF OI server”) in the Input dialog box and click OK.

d. Fill in the new connection record in the right pane of the Manage Connections dialog box.

e. Click OK to save the connection setup.

The Remote Server Settings dialog box displays, showing the server's current settings.

7. Select the Activate ITOps NOTIF checkbox, and then click OK.

Note: You can also change other server settings in the Remote Server Settings dialog box if necessary.

8. Restart your SAM/Adapter Platform server.

Note: Server setting changes made in the ITOps NOTIF Editor Remote Server Settings dialog box are persistent. When you change server settings in the Remote Server Settings dialog box and click OK, the changes are saved to the Notif_Settings.import file that is generated and

Start ITOps NOTIF 57


saved to the BASEDIR/smarts/local/conf/<icoi or ics> directory in the Adapter Platform or SAM server where ITOps NOTIF is running. Server setting changes made in the ITOps NOTIF Editor are preserved even if the repository is deleted. For example, if the repository is erased because you used the --norestore option for server startup, the server uses the last saved settings from the ITOps NOTIF Editor saved in BASEDIR/smarts/local/conf/<icoi or ics>/Notif_Settings.import.

Note: The EMC Ionix ITOps Notification Module User Guide includes information on how to use the ITOps NOTIF Editor.



Verify the EMC Smarts product statusYou can determine the current state of the products in the suite that register with the Broker by typing the following command from the BASEDIR/smarts/bin directory:

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

59


Uninstalling Service Assurance Management Suite 61

6

This chapter describes how to uninstall the EMC Service Assurance Management Suite.


◆ Before uninstallation.......................................................................... 62◆ Uninstalling Service Assurance Management Suite ..................... 69◆ Disabling ITOps NOTIF .................................................................... 73◆ Uninstalling Service Assurance Management Suite ..................... 69◆ Disabling ITOps NOTIF .................................................................... 73

Uninstalling ServiceAssurance

Management Suite


Uninstalling Service Assurance Management Suite

Before uninstallationThis section describes tasks you should complete before uninstalling EMC Smarts software:

◆ “Remove manually installed services” on page 62

◆ “Determine order for removing products (UNIX only)” on page 62

◆ “Uninstall when the same product suite is installed twice (Windows only)” on page 63

◆ “Detect and stop EMC Smarts programs” on page 63

◆ “Uninstall the FLEXnet License Server” on page 67

Remove manually installed servicesServices that you manually installed with sm_service command are not removed by the uninstallation program. You must remove these services manually before uninstalling the product suite.

To remove a service, invoke sm_service from the BASEDIR/smarts/bin directory:

1. Use sm_service to list installed services.

./sm_service show

2. Remove the manually installed service.

./sm_service remove ic-<service_name>

where <service_name> is the name of the service. For example, ic-am-server or ic-sam-server.

Determine order for removing products (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 created 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.

Before uninstallation 63


You can determine what product suite was installed first by perform this check:

1. Use a text editor to open the ic-serviced script.

• For Solaris, ic-serviced is located in the /etc/init.d directory

• For Linux, ic-serviced is located in the /etc/init.d directory

2. Find the value of the SMHOME variable.

The value of SMHOME indicates which suite was installed first.

Uninstall when the same product suite is installed twice (Windows only)If you installed the same product suite to different locations on the same host system, do not use Add/Remove Programs to uninstall. Uninstall the EMC Smarts product suite as follows:

1. Use the command prompt to invoke Wizard mode for uninstallation program.

C:\BASEDIR\_uninst\uninstaller.exe

where BASEDIR is the location of the EMC Smarts product suite to uninstall.

2. Complete the uninstallation beginning with step 2. “Uninstall using Wizard mode” on page 69 provides additional information.

Detect and stop EMC Smarts programsBefore upgrading or uninstalling your suite, you must stop all EMC Smarts services, EMC Smarts scheduled jobs, and any other process that uses programs or libraries running from the EMC Smarts suite.

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 applying a service pack or patch and uninstalling the product suite).



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, type:

# ./sm_plist.sh <BASEDIR2>

For Windows, type:

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)To stop 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 19 on page 65:

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

• To stop any server 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 19 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 running EMC Smarts services. These services start with the words “EMC Smarts,” “EMC Ionix,”“InCharge,” or “Smarts.” For each of these services, right-click the service and then select Stop.

Note: Do not stop the Broker service.

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

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

brcontrol -b <host>:<port>

7. Stop any EMC Smarts server 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 appears.

10. Click Task Manager. The Windows Task Manager appears.

11. Select the Processes tab.

CAUTION!Allow up to 30 minutes before performing the next step. EMC Smarts servers with large topologies can take considerable time to stop while saving the topology to the repository. Stopping processes prematurely may corrupt your repository file.



12. In the Processes tab, look in the column labeled Image Name for sm_server. Right-click each sm_server, 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, and so on. Right-click each instance, and then select End Process.

Note: Do not shut down any sm_authority or sm_logger processes The sm_authority and sm_logger processes are child processes of a EMC Smarts server. The child processes will stop when the parent process stops.

Uninstall the FLEXnet License ServerWhen 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:

1. Stop the FLEXnet License Server.

Solaris:

# /etc/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 select Stop.

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

In UNIX, type:

# BASEDIR/smarts/script/install_license.sh uninstall

In Windows, type:

BASEDIR\smarts\script\install_license.cmd uninstall



Uninstalling Service Assurance Management SuiteEMC Smarts product suites use InstallShield software to install and uninstall product suites. For UNIX, you invoke the uninstallation program from the system prompt. For Windows, you use the Add/Remove Programs, except when the same product suite is installed in multiple locations on the same host system. 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.

Uninstall using Wizard modeWizard mode provides a graphical user interface to the uninstallation program for UNIX and Windows platforms.


1. Invoke the uninstaller program:

For UNIX, type:

# BASEDIR/_uninst/uninstaller.bin

For Windows, use Add/Remove Programs:

a. Click Start > Settings > Control Panel.

b. Double-click Add/Remove Programs.

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

d. Click Change/Remove.

2. Click Next in the Welcome screen to continue.

3. In the Product Selection screen, click Next to uninstall the entire suite of products (by default, all products are selected) or clear 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 appears.

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.

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:

• /local

• /bin

• /setup

Uninstall using CLI modeTo uninstall an EMC Smarts product or product suite:

1. Type the following command and press Enter:

# 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 (checkmarks) 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,” type y or Y; to reply “no,”type 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:

• /local

• /bin

• /setup

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 modeThe unattended mode enables you to automate the removal of EMC Smarts product suites.

1. Invoke the uninstallation program with appropriate options for the operating system:

• On UNIX systems, use the uninstaller.bin program:



BASEDIR/_uninst/uninstaller.bin -silent

• On Windows system, use the uninstaller.exe program:

BASEDIR\_uninst\uninstaller.exe -silent

Note: Type each command as one line.

2. 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:

• /local

• /bin

• /setup

The log files from the uninstallation 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.

Disabling ITOps NOTIF 73


Disabling ITOps NOTIFThe ITOps NOTIF application cannot be uninstalled separately from SAM 8.1 because the ITOps NOTIF processor is included as part of the SAM 8.1 server application. However, you can disable ITOps NOTIF on a server by performing the following steps:

1. Start the ITOps NOTIF Editor by selecting Start > Programs > InCharge 8 > ITOps NOTIF Editor.

Note: You can also launch the editor by double-clicking the NotifGui.bat file (for Windows systems) or the NotifGui.sh file (for UNIX systems) in the BASEDIR/smarts/notif/editor directory.

2. Use the ITOps NOTIF Editor to connect to the running SAM or Adapter Platform server. Select Remote > Edit a server's settings and choose a server in the Connect to a Server dialog box.

The Remote Server Settings dialog box displays, showing the server's current settings.

3. In the Remote Server Settings dialog box, clear the Activate ITOps NOTIF checkbox, and then click OK.

4. Configure the SNMP Trap Adapter to use the default trap_mgr_parse.asl script instead of the Notif-trap_mgr_parse.asl script.

For example:

./sm_trapd --name=TRAP-OI --server=INCHARGE-OI --config=icoi--port=9013 --model=sm_actions --output--rules=icoi-trapd/trap_mgr_parse.asl --daemon

Note: The --daemon option only works on UNIX systems, not Microsoft Windows systems. Any customer specializations made to the Notif-trap_mgr_parse.asl file in the BASEDIR/smarts/rules/icoi-trapd directory must be incorporated into the trap_mgr_parse.asl file in the BASEDIR/smarts/rules/icoi-trapd directory.

5. Configure the Syslog Adapter to use the default SysLog_mgr.asl script instead of the Notif-SysLog_mgr.asl script.

For example:



./sm_adapter.exe --NTsErViCeNaMe=ic-syslog-adapter --name=SYSLOG-OI --server=INCHARGE-OI --tail=/var/log/syslog --model=sm_system --model=sm_actions --output icoi-syslog/SysLog_mgr.asl

Note: One or more adapters can feed a single ITOps NOTIF server.

6. Restart your SAM or Adapter Platform server.

Manually Installing Services 75

A

This chapter consists of the following sections:

◆ Overview............................................................................................. 76◆ Service Assurance Management Suite services ............................. 77

Manually InstallingServices


Manually Installing Services

OverviewIf you did not install services when you installed the EMC Smarts products suite, 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.

EMC Corporation recommends that EMC Smarts products be installed as services whenever possible. 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 manually install a product as a service, use the sm_service install command with the appropriate set of options.

The EMC Smarts System Administration Guide provides a complete description of the command syntax.

Service Assurance Management Suite services 77


Service Assurance Management Suite servicesThis section provides default service parameters for the EMC Ionix Service Assurance Management Suite.

EMC Smarts Broker

UNIX ▼ /opt/InCharge8/SAM/smarts/bin/sm_service install--force--startmode=runonce--name=ic-broker--description="EMC Smarts Broker"--env=SM_CLIENTCONNECT=brokerConnect.conf/opt/InCharge8/SAM/smarts/bin/brstart

--port=426--restore=/opt/InCharge8/SAM/smarts/local/repos/

broker/broker.rps--output ▲

Windows ▼ C:\InCharge8\SAM\smarts\bin\sm_service.exe install --force--startmode=runonce--name=ic-broker--description="EMC Smarts Broker"--env=SM_CLIENTCONNECT=brokerConnect.confC:\InCharge8\SAM\smarts\bin\brstart.exe

--port=426 --restore=C:\InCharge8\SAM\smarts\local\repos\

broker\broker.rps ▲

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



Service Assurance Manager (Global Manager)

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

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

Windows ▼ C:\InCharge8\SAM\smarts\bin\sm_service.exe install--force--name=ic-sam-server--startmode=runonce --description="EMC Smarts Service Assurance Manager

Server"C:\InCharge8\SAM\smarts\bin\sm_server.exe--name=INCHARGE-SA--config=ics--port=0--ignore-restore-errors--output ▲

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



Business Impact Manager server

UNIX /opt/InCharge8/SAM/smarts/bin/sm_service install --startmode=runonce--name=MBIM--description=”EMC Smarts MBIM – Maintenance and Business Impact Manager Server”/opt/InCharge8/SAM/smarts/bin/sm_server--name=INCHARGE-MBIM--config=bim--port=0--ignore-restore-errors--output

Windows C:\InCharge8\SAM\smarts\bin\sm_service.exe install --startmode=runonce--name=MBIM--description=”EMC Smarts MBIM – Maintenance and Business Impact Manager Server”C:\InCharge8\SAM\smarts\bin\sm_server.exe--name=INCHARGE-MBIM--config=bim--port=0--ignore-restore-errors--output




Adapter Platform

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

Windows ▼ C:\InCharge8\SAM\smarts\bin\sm_service.exe install--force--name=ic-icoi-server--startmode=runonce --description="EMC Smarts SAM Adapter Platform Server"C:\InCharge8\SAM\smarts\bin\sm_server.exe--name=INCHARGE-OI--config=icoi--port=0--ignore-restore-errors--output ▲




Business Dashboard

UNIX ▼ /opt/InCharge8/CONSOLE/smarts/bin/sm_service install--force--unmanaged--name=ic-business-dashboard--startmode=runonce --description="EMC Smarts Servlet Engine"/opt/C:/InCharge8/CONSOLE/smarts/bin/sm_tomcat--outputstart ▲

Windows ▼ C:\InCharge8\CONSOLE\smarts\bin\sm_service.exe install--force--name=ic-business-dashboard--startmode=runonce --description="EMC Smarts Servlet Engine"C:\InCharge8\CONSOLE\smarts\bin\sm_tomcat.exe--outputstart ▲




Syslog Adapter

UNIX ▼ /opt/InCharge8/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-syslog-adapter--startmode=runonce--description="EMC Smarts Syslog Adapter"/opt/C:/InCharge8/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 ▲

Windows ▼ C:\InCharge8\SAM\smarts\bin\sm_service.exe install--force--name=ic-syslog-adapter--startmode=runonce--description="EMC Smarts Syslog Adapter"C:\InCharge8\SAM\smarts\bin\sm_adapter.exe--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 Adapter

UNIX ▼ /opt/InCharge8/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-trapd-receiver--startmode=runonce --description="EMC Smarts SNMP Trap Adapter"/opt/InCharge8/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 ▲

Windows ▼ C:\InCharge8\SAM\smarts\bin\sm_service.exe install--force--name=ic-trapd-receiver--startmode=runonce --description="EMC Smarts SNMP Trap Adapter"C:\InCharge8\SAM\smarts\bin\sm_trapd.exe--name=TRAP-INCHARGE-OI--server=INCHARGE-OI--config=icoi--port=162--seed=seedfile--model=sm_actions--output--rules=icoi-trapd\trap_mgr_parse.asl ▲


Procedures for CD-ROMs 85

B

As a reference, this chapter includes commands and examples for working with a CD-ROM to install or upgrade the EMC Service Assurance Management Suite.

This chapter consists of the following sections:

◆ Mounting a CD-ROM on UNIX systems........................................ 86◆ Loading a CD-ROM on Windows ................................................... 88

Procedures forCD-ROMs


Procedures for CD-ROMs

Mounting a CD-ROM on UNIX systemsUse the following procedure to find the instructions appropriate for your operating system:

1. Insert the CD-ROM into the optical drive.

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

3. Change to the CD-ROM directory by typing the appropriate command from Table 21 on page 87.

Table 20 Mounting the CD-ROM for UNIX operating systems

Operating system Commands and examples

Solaris # mount -o ro -F hsfs <DEVICE> /mnt

Example:# mount -o ro -F hsfs /dev/dsk/c0t6d0s0 /mnt

Linux # mount <DEVICE>

Example:# mount /dev/cdrom /mnt/cdrom

where <DEVICE> is the mount point for the optical drive.

Mounting a CD-ROM on UNIX systems 87


Table 21 Changing to the CD-ROM directory in UNIX operating systems

Operating system Command

Solaris If Volume Manager (VM) is running:# cd /cdrom/<suite>-<os><version>/suite

If VM is not running:# cd /mnt/suite

Linux If Automount is running:# cd /cdrom/<suite>-<os><version>/suite

If Automount is not running:# cd /mnt/cdrom/suite

where <suite> is the product suite, for example, SAM_SUITE or IP_SUITE.<os> is the operating system, for example SOLARIS, LINUX, WIN.<version> is the software version, for example, 701 or 71.



Loading a CD-ROM on WindowsThe installation program starts automatically on Windows systems when AutoPlay or AutoRun is enabled:

1. Insert the CD-ROM into the optical drive. If AutoPlay or AutoRun is enabled, the installation program starts automatically using the Wizard mode.

2. If the installation program does not start, use Windows Explorer to locate the CD-ROM.

3. Locate the \suite directory on the CD-ROM and double-click the setup executable.

emc ionix service assurance management suite … notif editor, or both.....40 where to go...

Documents