EMC Ionix Service Assurance Management Suite · PDF fileEvent Explorer, FarPoint, FirstPass,...

EMC® Ionix™

Service Assurance Management SuiteVersion 8.1 Service Pack 2

Installation and Migration GuideP/N 300-012-732REV A01

EMC Ionix SAM Suite Version 8.1 Service Pack 2 Installation and Migration Guide2

Copyright © 1996-2011 EMC Corporation. All rights reserved. Published in the USA.

Published August, 2011

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.

EMC2, EMC, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Connectrix, CopyCross, CopyPoint, CX, Dantz, Data Domain, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, VMAX, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and the RSA logo, are registered trademarks or trademarks of EMC Corporation in the United States and other countries. Vblock is a trademark of EMC Corporation in the United States.

VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions.

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

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.

CONTENTS

Chapter 1 Overview

Suite contents ............................................................................... 16Default installation directories................................................. 17

Product and release compatibility.................................................. 18 Installation tasks overview ............................................................ 19 Migration tasks overview ............................................................... 21 Uninstallation tasks overview ........................................................ 23

Chapter 2 Requirements

Operating system requirements..................................................... 26 Hardware requirements ................................................................. 28 Web Console and Business Dashboard requirements..................... 30

Java Web Start requirements for Web Console.......................... 31Web browser requirements for the ITOI Adapter for UIM/O ....... 32

Chapter 3 Installing the Service Assurance Management Suite

Before installation ......................................................................... 34Determine the location of the EMC Ionix Broker........................ 34

Install the Service Assurance Management Suite ........................... 34Installing the Service Assurance Manager Server ..................... 35Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both................................................................ 41Installing the ITOI Adapter for UIM/O ....................................... 46Support for FIPS 140-2 in SAM 8.1.2 ........................................ 47Enabling FIPS 140 mode on a new installation ......................... 48Enabling FIPS 140 mode after upgrade .................................... 50Disabling FIPS 140 mode ......................................................... 50Launching SAM 8.1.2 Web Console, Dashboard and NOTIF ...... 50Where to go next...................................................................... 52

Chapter 4 Upgrading the Service Assurance Management Suite

Before upgrade.............................................................................. 54 Upgrade the Service Assurance Management Suite........................ 54

Upgrade the Service Assurance Manager Server....................... 55

EMC Ionix SAM Suite Version 8.1 Service Pack 2 Installation and Migration Guide 3

Contents

Upgrade Service Assurance Manager Console, or the ITOps NOTIF Editor, or both.......................................................................... 60Upgrading to add the ITOI Adapter for UIM/O ........................... 65

Upgrading from SAM 8.1.1 to SAM 8.1.2 in FIPS mode ................... 66 Manually merging configuration files ............................................. 67

Where to go next...................................................................... 67

Chapter 5 Performing a Migration

Overview of migration tasks........................................................... 70Migrating custom patches........................................................ 71Determining current version of software................................... 71

Perform the migration procedure ................................................... 72Migration to a different server with the same operating system 72Migration to the same server with the same operating system ..................................................................... 77Migration to a different server with a different operating system ..................................................................... 83

Migrating previous NOTIF versions to version 8.1.2 ........................ 88Prerequisites ........................................................................... 88Notes on the SAM 7.x to 8.1.2 migration process ..................... 88Migrate previous NOTIF version to ITOps NOTIF 8.1.2 ............... 89

Verify the EMC Ionix version level................................................... 91

Chapter 6 Verifying the Installation

Obtain and install a temporary license file ..................................... 94 Start EMC Ionix products ............................................................... 94

Starting services on UNIX......................................................... 95Starting services on Windows .................................................. 96

Start EMC Ionix programs............................................................... 96Starting programs on UNIX....................................................... 97Starting programs on Windows .............................................. 100

Start ITOps NOTIF......................................................................... 103 Verify the EMC Ionix product status.............................................. 105 Verifying FIPS 140 mode status.................................................... 106 Where to go next ......................................................................... 106

Chapter 7 Uninstalling Service Assurance Management Suite

Before uninstallation ................................................................... 110Remove manually installed services ...................................... 110Determine order for removing products (UNIX only)................ 110

4 EMC Ionix SAM Suite Version 8.1 Service Pack 2 Installation and Migration Guide

Contents

Uninstall when the same product suite is installed twice (Windows only) ...................................................................................... 111

Uninstalling Service Assurance Management Suite ...................... 112Uninstall using Wizard mode ................................................. 113Uninstall using CLI mode ....................................................... 114Uninstall using unattended mode .......................................... 115Disabling ITOps NOTIF............................................................ 116

Appendix A Manually Installing Services

Overview ..................................................................................... 120 Service Assurance Management Suite services ............................ 121

EMC Ionix Broker ................................................................... 121Service Assurance Manager (Global Manager) ....................... 121Business Impact Manager server ........................................... 122Adapter Platform.................................................................... 123Business Dashboard.............................................................. 123Syslog Adapter ...................................................................... 124SNMP Trap Adapter................................................................ 125ITOI Adapter for UIM/O .......................................................... 126

Appendix B Procedures for CD/DVD-ROMs

Mounting a CD/DVD-ROM on UNIX systems.................................. 128 Loading a CD/DVD-ROM on Windows........................................... 130

Appendix C Understanding the sm_edit Utility

The sm_edit utility ....................................................................... 132

Appendix D License Migration Procedure

Prerequisites ............................................................................... 136 Migrate permanent license and set up FLEXnet license server ...... 137 Access to FLEXnet license server using SM_LICENSE .................... 140


Contents


Title Page

TABLES

1 Interoperability chart ..................................................................................... 182 Deployment requirement for the ITOI Adapter for UIM/O ................................ 193 Installation requirements and tasks............................................................... 194 Migration requirements and tasks ................................................................. 215 Uninstallation requirements and tasks .......................................................... 236 Supported operating system for the suite ...................................................... 267 Required operating system patches .............................................................. 278 Typical hardware for the equipment tiers ....................................................... 289 Required disk space for the Service Assurance Manager Server ..................... 2810 Required disk space for the Service Assurance Manager console ................... 2911 CPU, memory, data disk space requirements ................................................. 2912 Server setup command syntax for Wizard mode ............................................. 3613 Server setup command syntax for CLI-mode................................................... 3814 Navigation keys ............................................................................................. 3915 Server setup command syntax for unattended mode...................................... 4016 Console setup command syntax for Wizard mode .......................................... 4217 Console setup command syntax for CLI-mode ................................................ 4418 Console setup command syntax for unattended mode................................... 4519 Setup command syntax for Wizard mode ....................................................... 5620 The setup command syntax for CLI-mode ....................................................... 5721 Server setup command syntax for unattended mode...................................... 5922 Setup command syntax for Wizard mode ....................................................... 6123 The setup command syntax for CLI-mode ....................................................... 6324 Console setup command syntax for unattended mode................................... 6325 Migration scenarios ....................................................................................... 7026 Mounting the CD/DVD-ROM for UNIX operating systems............................... 12827 Changing to the CD/DVD-ROM directory in UNIX operating systems.............. 129


Tableses


PREFACE

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

Contact your EMC representative if a product does not function properly or does not function as described in this document.

Note: This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document.

AudienceThis document is part of the EMC Ionix 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 Service Assurance Management Suite installation directoryIn this document, the term BASEDIR represents the location where EMC Ionix software is installed:

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

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

The <productsuite> represents the EMC Ionix product suite to which the product belongs. For example, on UNIX operating systems, EMC Ionix Service Assurance Management Suite is, by default, installed to /opt/InCharge/SAM/smarts. On Windows operating systems, this product is, by default, installed to: C:\InCharge\SAM\smarts. This location is referred to as BASEDIR/smarts.

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


Preface

The EMC Ionix ITOps System Administration Guide provides more information about the directory structure of EMC Ionix software.

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

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

◆ Global Console

◆ Business Dashboard

◆ SAM Native Adapters:

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

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

◆ XML Adapter

◆ ITOI Adapter for UIM/O

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

Help for command line programs

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

EMC Ionix documentation

Readers of this guide may find the following related documentation helpful:

◆ EMC Ionix ITOps Documentation Catalog

◆ EMC Ionix ITOps System Administration Guide

◆ EMC Ionix ITOps ICIM Reference

◆ EMC Ionix ITOps ASL Reference Guide


Preface

◆ EMC Ionix ITOps Perl Reference Guide

◆ EMC Ionix ITOps Dynamic Modeling Tutorial

◆ EMC Ionix ITOps MODEL Reference Guide

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

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

◆ EMC Ionix Service Assurance Management Suite Release Notes

◆ EMC Ionix Service Assurance Management Suite Third-Party Copyright Read Me

◆ EMC Ionix Service Assurance Manager Introduction

◆ EMC Ionix Service Assurance Management Suite Installation and Migration Guide

◆ EMC Ionix Service Assurance Management Suite Deployment Guide

◆ EMC Ionix Service Assurance Manager Configuration Guide

◆ EMC Ionix Service Assurance Manager Operator 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 Service Assurance Manager Notification Adapters User Guide

◆ EMC Ionix Service Assurance Manager Adapter Platform User Guide

◆ EMC Ionix ITOI Adapter for Unified Infrastructure Manager/Operations Configuration Guide

◆ EMC Ionix XML Adapter User Guide

◆ EMC Ionix ITOps Quick Start Guide

◆ EMC Ionix ITOps Notification Module User Guide


Preface

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

Conventions used in this documentEMC uses the following conventions for special notices:

DANGER indicates a hazardous situation which, if not avoided, will result in death or serious injury.

WARNING indicates a hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

NOTICE is used to address practices not related to personal injury.

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

IMPORTANT

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


Preface

Typographical conventions

EMC uses the following type style conventions in this document:

Pathname conventions

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

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, and utilities• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys,

file systems, and notifications

Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages

Used in procedures for:• Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and

menus• What the 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

Courier bold Used for specific user input, such as commands

Courier italic Used in procedures for:• Variables on the 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 enclose content that the user must specify, such as x or y or z

... Ellipses indicate nonessential information omitted from the example


Preface

Graphical conventions

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

Manager

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

Where to get helpEMC support, product, and licensing information can be obtained as follows:

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

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC Sales Representative for details about obtaining a valid support agreement or with questions about your account.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]


http://Powerlink.EMC.com

CHAPTER 1Overview

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

This chapter consists of the following topics:

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

Overview 15

Overview

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

◆ Service Assurance Manager

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

• Global Manager

• EMC Ionix Broker

• EMC Ionix 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 Ionix 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 Ionix 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 either the SAM server or Adapter Platform server, or both. The internal event and notification processing features of the standard SAM Adapter Platform are replaced by ITOps NOTIF.


Overview

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 the 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 Ionix application. It requires the SAM Adapter Platform.

◆ EMC Ionix ITOI Adapter for Unified Infrastructure Manager/Operations

The EMC Ionix ITOI Adapter for Unified Infrastructure Manager/Operations (referred to as the ITOI Adapter for UIM/O) provides integration between the EMC Ionix Unified Infrastructure Manager/Operations (herein referred to as UIM/O) and the Service Assurance Management Suite. The adapter retrieves alerts from UIM/O, creates notifications from the alerts, and sends the notifications to the Global Manager.

◆ XML Adapter

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

Default installation directories

The EMC Ionix Service Assurance Management Suite is distributed on two CD/DVD-ROMs:

◆ Service Assurance Manager Server Suite

◆ Service Assurance Manager Console Suite

Suite contents 17

Overview

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 EMC online support® website. The Service Assurance Manager Server is installed by default to the following subdirectories under the InCharge root directory:

◆ /opt/InCharge/SAM (for UNIX)

◆ C:\InCharge\SAM (for Windows)

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

◆ /opt/InCharge/CONSOLE (for UNIX)

◆ C:\InCharge\CONSOLE (for Windows)

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

Table 1 Interoperability chart (1 of 2)

EMC Ionix product suite Versions

EMC Ionix Server Manager (EISM) 1.1.0.x, 2.0, 3.0

EMC Ionix Application Connectivity Monitor (ACM) 2.3

EMC Ionix IP Management Suite 6.5.x, 7.0.3, 7.0.4, 8.1.2 (8.1 SP2)

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

EMC Ionix MPLS Management Suite (MPLS) 2.1, 3.0, 4.0

EMC Ionix Multicast Manager (MCAST) 1.2, 2.0, 2.1

EMC Ionix Network Protocol Management Suite (NPM) 2.1, 3.0, 3.1

EMC Ionix Optical Transport Management Suite (OTM) 5.0, 5.1


Overview

Table 2 on page 19 lists the deployment requirement for the ITOI Adapter for UIM/O version 8.1.2.

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

EMC Ionix Service Assurance Management Adapter Suite

1.1, 1.2, 1.3

EMC Ionix Service Assurance Management Suite 7.2.x, 8.0.x, 8.1

EMC Ionix Storage Insight for Availability (SIA) 2.1, 2.3, 2.3.1

EMC Ionix VoIP Management Suite 3.0, 4.0

Table 1 Interoperability chart (2 of 2)


Table 2 Deployment requirement for the ITOI Adapter for UIM/O


EMC Ionix Unified Infrastructure Manager/Operations 2.1

Table 3 Installation requirements and tasks (1 of 2)

Before you install:

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 that you will install from the Service Assurance Management Suite.

EMC Ionix ITOps System Administration Guide “Obtain and install a temporary license file” on page 94

Determine if the products are supported on your platform.

“Operating system requirements” on page 26

Determine if your system meets the hardware requirements.

“Hardware requirements” on page 28

Installation tasks overview 19

Overview

Installation method:

Install the Service Assurance Manager Server. Choose one of the following installation methods:• “Install the Service Assurance Manager

Server using Wizard mode” on page 35• “Install Service Assurance Manager

Server by using the CLI mode” on page 38, UNIX only

• “Install Service Assurance Manager Server by using the unattended mode” on page 39

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

Install the ITOI Adapter for UIM/O. • “Installing the ITOI Adapter for UIM/O” on page 46

After you install:

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

EMC Ionix ITOps System Administration Guide

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 Ionix ITOps System Administration Guide describes the procedures to use.


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

• “Starting services on UNIX” on page 95• “Starting services on Windows” on

page 96

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

Table 3 Installation requirements and tasks (2 of 2)


Overview

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

Table 4 Migration requirements and tasks (1 of 2)

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 that you will install.


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

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

Installation and migration:

Install the Service Assurance Manager Server. Choose one of the following installation methods:• “Install the Service Assurance Manager

Server using Wizard mode” on page 35• “Install Service Assurance Manager

Server by using the CLI mode” on page 38, UNIX only

• “Install Service Assurance Manager Server by using the unattended mode” on page 39

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

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

Migration tasks overview 21

Overview

After you install:

Save your license in the appropriate 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 Ionix Service Assurance Management Adapter Suite.


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

• “Starting services on UNIX” on page 95• “Starting services on Windows” on

page 96

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

Table 4 Migration requirements and tasks (2 of 2)

Before you migrate:


Overview

Uninstallation tasks overviewTo uninstall Service Assurance Management Suite, you must satisfy or perform the tasks listed in Table 5 on page 23.

Table 5 Uninstallation requirements and tasks

Before you uninstall:

Review uninstall prerequisites • “Remove manually installed services” on page 110

• “Determine order for removing products (UNIX only)” on page 110

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

• “Uninstall the FLEXnet License Server” on page 111

• “Uninstall the FLEXnet License Server” on page 111

Uninstallation:

Uninstall the Service Assurance Management Suite • “Uninstall using Wizard mode” on page 113

• “Uninstall using CLI mode” on page 114

• “Uninstall using unattended mode” on page 115

• “Disabling ITOps NOTIF” on page 116

Uninstallation tasks overview 23

Overview


CHAPTER 2Requirements

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


◆ Operating system requirements ....................................................................... 26◆ Hardware requirements.................................................................................... 28◆ Web Console and Business Dashboard requirements ....................................... 30

Requirements 25

Requirements

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

Table 6 Supported operating system for the suite

Operating system Supported version

Red Hat Enterprise Linux RHEL AS 4, RHEL 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(use of Solaris T-Serieshardware is not recommended)

9, 64-bit10, 64-bitSun zone 10

Windows Windows 2003 Enterprise Edition R2Windows 2003 Enterprise Edition SP2Windows 2008 Enterprise EditionWindows 2008 Enterprise Edition SP2Windows 2008 Enterprise Edition R2Windows XP Professional SP2 (Console only)Windows XP Professional SP3 (Console only)Windows Vista (Console only)Windows 7 (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 3Red Hat Enterprise Linux 5 (64-bit)

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


Requirements

Note: While the Service Assurance Manager Server requires the 64-bit version of the operating system for all platforms, the Console must be installed either on a 32-bit or a 64-bit platform.

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

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 Ionix software.

Table 7 Required operating system patches

Operating system Patches

Red Hat Enterprise Linux AS 4

compat-libstdc++-33-3.2.3

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

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

114344-36 Security Vulnerability patch

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 restart your system: set ip:do_tcp_fusion = 0.

Windows Server 2003 Enterprise Edition

Hotfix KB927493

Hotfix KB947369

Operating system requirements 27

Requirements

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

Table 8 on page 28 lists typical hardware for several equipment tiers and operating systems. Table 9 on page 28 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 9 on page 28 lists disk space requirements for installing the Service Assurance Manager Server.

Table 8 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 9 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 2.7 GB


Requirements

Table 10 on page 29 lists disk space requirements for installing the Service Assurance Manager console.

Table 11 on page 29 lists minimum requirements for CPUs, memory, and data disk space that is 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.

Table 10 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

1.6 GB

Table 11 CPU, memory, data disk space requirements

EMC Ionix 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 Ionix 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

ITOI Adapter for UIM/O 1 256 MB 50 MB

XML Adapter 1 256 MB See the following Note.

Hardware requirements 29

Requirements

For the XML Adapter, disk space depends on the size of the output that 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.

If you are installing multiple products, then your system must meet the products’ total memory and data disk space requirements. Table 9 on page 28 defines required disk space and Table 11 on page 29 lists CPU, memory, and data disk space requirements.

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

◆ EMC Ionix Web Console

or

◆ EMC Ionix 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, 3.5, 3.6, 4.0, and 5.0

• Browser that supports Java JRE 1.6.x

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 in the Oracle website.


Requirements

◆ Java 2 Platform Standard Edition 6.0, which includes the 1.6.x Web browser plug-in must be installed on the client workstation.

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

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

For all platforms, download it from the Sun Microsystems website.

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.

Note: In SAM 8.1.2, Red Hat Enterprise Linux AS 4 and AS 5 uses JRE version 1.6.0_13. Windows Server 2003, Windows Server 2008, Solaris 9, and Solaris 10, uses JRE version 1.6.0_26.

Java Web Start requirements for Web Console

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

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

◆ For UNIX, contact your system administrator to install and configure Java Web Start or follow the instructions provided in the Sun Microsystems website.

◆ For Windows, on the client machine, depending upon the type of browser, after you launch the Web Console, use an automatic installer or follow the instructions provided in the Sun Microsystems website.

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.

Web Console and Business Dashboard requirements 31

Requirements

When launching the Web Console from the browser (using the globalConsoleCached.html and JRE 1.6.13), an exception may be raised stating that the JAR resource in the JNLP file is not signed by the same certificate. Launch the Web Console from http://<servername>:8080/webconsole/ to download the correct (JRE 1.6_25) version.

Web browser requirements for the ITOI Adapter for UIM/O

The following web browsers are required for the ITOI Adapter for UIM/O:

◆ Internet Explorer 6.0 with Service Pack 1, 7.0, and 8.0

◆ Firefox 3.5, 3.6, 4.0, and 5.0

Only browsers running on Windows operating systems are supported. For Windows, the browser must be JavaScript enabled. The EMC Ionix ITOI Adapter for Unified Infrastructure Manager/Operations Configuration Guide describes a recommended configuration task for both browsers and Firefox addons.

In addition, Java Standard Edition 6.0, which includes the 1.6.x Web browser plug-in, must be installed on the client workstation. If your client workstation does not have the JRE 1.6, you must obtain it and install it. For all platforms, download it from the Oracle website, http://www.oracle.com.


CHAPTER 3Installing the Service Assurance Management Suite

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


◆ Before installation............................................................................................ 34◆ Install the Service Assurance Management Suite .............................................. 34

Installing the Service Assurance Management Suite 33

Installing the Service Assurance Management Suite

Before installationBefore installing EMC Ionix Service Assurance Management Suite, determine the location of the EMC Ionix Broker. “Determine the location of the EMC Ionix Broker” on page 34 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 Ionix Broker

You must specify the location of the EMC Ionix Broker during installation of the EMC Ionix software. Typically, this location is chosen during the design of the EMC Ionix 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 SuiteThis section describes how to install Service Assurance Management Suite into a new directory structure. The Service Assurance Management Suite is distributed on the following CD/DVD-ROMs:

◆ Service Assurance Manager Server Suite

Note: The following products can be installed as services: EMC Ionix Broker, EMC Ionix Service Assurance Manager Server, EMC Ionix Business Impact Manager, EMC Ionix Service Assurance Manager Adapter Platform Server, EMC Ionix SNMP Trap Adapter, ITOI Adapter for UIM/O, EMC Ionix Syslog Adapter, EMC Ionix ITOps Notification Module.

◆ Service Assurance Manager Console Suite



Note: The following products can be installed as services: EMC Ionix Servlet Engine, ITOps NOTIF Editor.

The Service Assurance Management Suite is also available for download from EMC online support.

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

◆ Insert the CD/DVD-ROM into the optical drive of the host system. Appendix Appendix B, “Procedures for CD/DVD-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/DVD, there may be a delay of several minutes between the InstallShield preparation screen and the EMC Ionix splash screen/installation dialogs. During this time, the java.exe process is running. Be patient. Do not eject/reinsert the CD/DVD to start a second install process.

Installing the Service Assurance Manager Server

This section describes the steps for installing the Service Assurance Manager Server.

Install the Service Assurance Manager Server 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 Ionix software and the host where you log in must be configured to run the X Window System. Before starting the installation program by using the Wizard mode, verify that the X Window System is running.

Running the Wizard modeTo install the Service Assurance Manager server:

Install the Service Assurance Management Suite 35


1. Run the Setup command appropriate for the operating system listed in Table 12 on page 36.

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

2. Click OK in the Warning dialog box.

If stopping services is necessary, specific instructions prompts appear 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 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/InCharge (on UNIX)

• C:\InCharge (on Windows)

Table 12 Server setup command syntax for Wizard mode

Operating system Setup command

Linux ./setup-SAM-8_1_2_0-linux64.bin (for Linux RHEL AS4)./setup-SAM-8_1_2_0-linux-rhAS50-64.bin (for Linux RHEL 5)

Solaris ./setup-SAM-8_1_2_0-sol64.bin

Windows setup-SAM-8_1_2_0-win64.exe



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.

The Services Selection screen appears.

8. Select the products that you want to install as services and click Next. If you do not install services at this point, you must 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, the EMC Ionix products start automatically when the system starts up. If the system is stopped and restarted, the EMC Ionix products restart automatically. The EMC Corporation recommends that EMC Ionix products should be installed as services whenever possible. If any of the products that are being installed can be started as services, these products are displayed in the services selection screen.

9. Specify the EMC Ionix 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.2.0.x version, migrate your existing repository directory. Type the path to your existing SAM 7.2.0.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.

Install Service Assurance Manager Server by using the CLI modeThe CLI 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 mode

To start the CLI mode, invoke the appropriate Setup command listed in Table 13 on page 38.

User selections and navigation in CLI mode

During the installation and uninstallation processes, there will be 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 13 Server setup command syntax for CLI-mode

Operating system Executable





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

To navigate between each step, use the keys defined in Table 14 on page 39.

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

Install Service Assurance Manager Server by using the unattended modeThe unattended 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 14 Navigation keys

Key Operation

1 Next, continue to the next step

2 Previous, go back to the previous step

3 Cancel, terminate the program

5 Redisplay, repeat the step

0 Accept the marked ([X]} menu choice



Running the unattended mode

From a command line shell, run the appropriate Setup command listed in Table 15 on page 40.

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:

INSTALL_SOLARIS -options /opt/home/SAM_SUITE-response.txt

Modifying the response file

Each suite has a response file located on the CD/DVD-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 the 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/DVD-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:

Table 15 Server setup command syntax for unattended mode


Linux ./setup-SAM-8_1_2_0-linux64.bin -options <path>/<suite>-response.txt (for Linux RHEL AS4)./setup-SAM-8_1_2_0-linux-rhAS50-64.bin -options<path>/<suite>-response.txt (for Linux RHEL 5)

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

Windows setup-SAM-8_1_2_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.



1. Copy the response file from the CD/DVD-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:

• 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 Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using Wizard mode

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

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

Running Wizard mode

To install the Service Assurance Manager Console:



1. Run the Setup command appropriate for the operating system listed in Table 16 on page 42.


2. Click OK in the Warning dialog box.

If stopping services is necessary, specific instructions prompts appear later in the installation process.




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

• C:\InCharge (on Windows)

Table 16 Console setup command syntax for Wizard mode


Linux ./setup-CONSOLE-8_1_2_0-linux.bin (for Linux RHEL AS4)./setup-CONSOLE-8_1_2_0-linux-rhAS50.bin (for Linux RHEL 5)

Solaris ./setup-CONSOLE-8_1_2_0-sol.bin

Windows setup-CONSOLE-8_1_2_0-win.exe



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 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 must 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 Ionix products start automatically when the system starts up. If the system is stopped and restarted, the EMC Ionix products restart automatically. EMC Corporation recommends that EMC Ionix products be installed as services whenever possible. If any of the products that are being installed can be started as services, these products are displayed in the services selection screen.

10. Specify the EMC Ionix 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 52 provides information on post-installation tasks.

Install Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using CLI mode

The CLI 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 mode

To start the CLI mode, invoke the appropriate Setup command listed in Table 17 on page 44.

Refer to “User selections and navigation in CLI mode” on page 38 for more information on prompts that appear for steps and menus during installation and uninstallation.

To navigate between each step, use the keys defined in Table 14 on page 39.

Table 17 Console setup command syntax for CLI-mode






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

Install Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using unattended mode

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

Running unattended mode


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_2_0-sol.bin -options /opt/home/SAM_CONSOLE_SUITE-response.txt


The Console suite has a response file located on the CD/DVD-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.

Table 18 Console setup command syntax for unattended mode


Linux ./setup-CONSOLE-8_1_2_0-linux.bin -options <path>/<suite>-response.txt (for Linux RHEL AS4)./setup-CONSOLE-8_1_2_0-linux-rhAS50.bin -options <path>/<suite>-response.txt (for Linux RHEL 5)

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

Windows setup-CONSOLE-8_1_2_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.



By default, the response file includes settings that support the installation of all products from the CD/DVD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to the following settings:



◆ Perform an upgrade






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


3. Save the file.

Installing the ITOI Adapter for UIM/O

The ITOI Adapter for UIM/O is installed as part of the Service Assurance Management Suite. The ITOI Adapter for UIM/O must reside on the same host as the Global Manager.

Follow the procedure to install the Service Assurance Management Suite as described in “Installing the Service Assurance Manager Server” on page 35.

◆ Run one of the server setup commands for any of the installation modes (Wizard, CLI, or unattended).

◆ Ensure that in the Services Selection screen, the service for the ITOI Adapter for UIM/O is selected.



After installation, before you start the adapter as described in Chapter 6, “Verifying the Installation,” you must configure authentication credentials for accessing the UIM/O appliance and the Global Manager, and configure your web browser. The EMC Ionix ITOI Adapter for Unified Infrastructure Manager/Operations Configuration Guide provides configuration instructions.

Note: The client tool scripts for the ITOI Adapter for UIM/O are installed when the Global Console for Service Assurance Management Suite Version 8.1 Service Pack 2 is installed. Consult “Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both” on page 41 for instructions.

Support for FIPS 140-2 in SAM 8.1.2

The Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. government computer security standard governing cryptographic modules. FIPS 140 is required for any software purchased by the U.S government and U.S military. This release specifically addresses U.S Government accounts which require FIPS 140 compliance.

A configuration parameter, SM_FIPS140, has been introduced for FIPS 140 in the runcmd_env.sh file. The SAM administrator can enable or disable this parameter as required. The default value of this parameter is FALSE.

FIPS 140 mode allows you to use SNMP V1, SNMPV2C, SNMP V3, with SHA and AES 128 protocols. FIPS 140 does not support the DES privacy protocol or the MD5 authentication protocol. When you discover an SNMPv3 device, you need to select the option “V3” in the “Add Agent” window. The “Authentication Protocol” option lists only SHA and not MD5, and the “Privacy Protocol” option lists only AES and not DES. This is because MD5 and DES are not supported in FIPS 140 mode. When you discover SNMPv3 devices with MD5 and DES protocol as seed, the devices go to the Pending List and display as “Invalid” or “Unsupported SNMP V3 protocol.”

FIPS 140 mode cannot be enabled or disabled after a server is started. FIPS 140 enabled domains can work only with the SAM 8.1.2 Global Console.



Non-FIPS 140 mode broker will not be able to communicate with a FIPS 140- enabled IP or SAM server. Trying to establish such a connection will result in the IP or SAM server going into a DEAD state after couple of minutes. Communication should always happen between FIPS 140-enabled brokers and servers. Inter-domain and FIPS 140 broker communication happens only when the Broker, IP server, SAM server, and the SAM Console are all in FIPS 140 mode, else the application will not be operational.

This section covers the following scenarios for FIPS 140:

◆ “Enabling FIPS 140 mode on a new installation” on page 48

◆ “Enabling FIPS 140 mode after upgrade” on page 50

◆ “Disabling FIPS 140 mode” on page 50

◆ “Verifying FIPS 140 mode status” on page 106

◆ “Launching SAM 8.1.2 Web Console, Dashboard and NOTIF” on page 50

Enabling FIPS 140 mode on a new installation

When you install SAM 8.1.2, FIPS 140 is not enabled by default. You must enable FIPS 140 on a clean installation or an upgrade, before the servers are started, using the following steps:

1. Back up the imk.dat, brokerConnect.conf, serverConnect.conf and clientConnect.conf files from the existing installation. These files are located in the <BASEDIR>/local/conf folder.

The backup is necessary in case you need to disable FIPS 140 mode and remove FIPS 140-2 encryption.

2. Run the following command at the command line prompt:

sm_rebond --upgrade --basedir=/opt/InCharge/SAM/smarts

The path must be set to the default install path. Regardless of the FIPS 140 state, the sm_rebond command must be invoked from the BASEDIR where the software is installed, not from any other product installation area which also has the sm_rebond utility.



3. When prompted, type a password to regenerate the imk.dat file. The default password is Not a secret.

SAM 8.1.1 does not use a FIPS 140-2 approved encryption algorithm to protect the imk.dat. file. Hence, while upgrading from SAM 8.1.1 to SAM 8.1.2, the imk.dat file needs to be regenerated in order to run in the FIPS 140 mode.

4. Download and install the Unlimited Strength Jurisdiction Policy Files using the following steps:

a. Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html, and download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6 from the Additional Resources section.

b. Extract the local_policy.jar and US_export_policy.jar files from the downloaded zip file.

c. Go to the <BASEDIR>/smarts/jre/lib/security directory, and then backup the existing policy files in this path.

d. Overwrite the local_policy.jar and US_export_policy.jar files to the <BASEDIR>smarts/jre/lib/security directory.

5. Set the value for the environment variable, SM_FIPS140 to TRUE in the runcmd_env.sh file. This file is located in the <BASEDIR>/smarts/local/conf directory.

If you install the server as a service on Linux and Solaris platforms, the services will start automatically after you issue the sm_rebond command. First stop the services, modify SM_FIPS140=TRUE in the runcmd_env.sh file, and then manually start the services.



Enabling FIPS 140 mode after upgrade

“Upgrading from SAM 8.1.1 to SAM 8.1.2 in FIPS mode” on page 66 provides the procedure.

Disabling FIPS 140 mode

To disable FIPS 140:

1. Replace the imk.dat, brokerConnect.conf, serverConnect.conf and clientConnect.conf files in the <BASEDIR>/local/conf folder, with the copies saved from prior to ““Enabling FIPS 140 mode on a new installation” on page 48”. If you do not have a copy of these files saved, contact technical support.

2. Set the value for the SM_FIPS140 parameter to FALSE in the runcmd_env.sh file. This file is located under <BASEDIR>/smarts/local/conf/runcmd_env.sh

3. Restart all processes, such as the domain, broker and console.

RPS files started under FIPS mode cannot be re-used in non-FIPS mode. Domains will need to be started either from scratch or pre FIPS RPS files can be used in cases where topologies have not changed. Restoring from older RPS files may not be productive as it will not contain any recent topology.

You do not need to remove the Unlimited Strength Jurisdiction Policy Files.

Launching SAM 8.1.2 Web Console, Dashboard and NOTIF

This section provides the steps to enable FIPS 140 for the SAM Console, Dashboard and NOTIF post an installation in the non-FIPS 140 mode:

1. Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html, and download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6 from the Additional Resources section.

2. Extract the local_policy.jar and US_export_policy.jar files from the downloaded zip file.

3. Go to the <BASEDIR>/smarts/jre/lib/security directory, and backup the existing policy files in this path.



4. Overwrite the local_policy.jar and US_export_policy.jar files to the <BASEDIR>/smarts/jre/lib/security directory.

5. Co-mandatory step: Change “sun.security.rsa.SunRsaSign” to “com.rsa.jsafe.provider.JsafeJCE” and “com.sun.net.ssl.internal.ssl.Provider” to “com.rsa.jsse.JsseProvider”in the java.security file located under:

• For SAM Web Console:

<BASEDIR>/CONSOLE/smarts/jre/lib/security

• For NOTIF:

<BASEDIR>/SAM/smarts/jre/lib/security

• For Dashboard, NOTIF Editor and JNLP, the JRE must be available in a pre-determined location in the user’s computer.

6. Co-mandatory step for Web Console, Dashboard and JNLP: The "com.smarts.fips_mode=true" parameter must be added in the corresponding webconsole.properties file (located under <BASEDIR>/InCharge/CONSOLE/smarts/tomcat/webapps/webconsole folder) or dashboard.properties file (located under <BASEDIR>/InCharge/CONSOLE/smarts/tomcat/webapps/templates).

This is a co-mandatory step for setting up a FIPS 140-compliant Tomcat web server for Web console and Dashboard. For client consoles that do not run Tomcat, Step 6 is not required.

7. Co-mandatory step for NOTIF: Replace "com.netmg.notif.gui.NotifApplication" with "-Dcom.smarts.fips_mode=true com.netmg.notif.gui.NotifApplication" in the NotifGui.bat or NotifGui.sh file. This file is located under the <BASEDIR>/CONSOLE/smarts/notif/editor/ or <BASEDIR>/SAM/smarts/notif/editor directory.

8. Set the value for the parameter SM_FIPS140 to TRUE in the runcmd_env.sh file, which is located under:

<BASEDIR>/CONSOLE/smarts/local/conf folder

or

Use "-Dcom.smarts.fips_mode=true" as a command line parameter for the sm_gui command.



Where to go next

After the installation is finished, you may need to complete the following tasks:

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

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


CHAPTER 4Upgrading the Service Assurance Management Suite

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


◆ Before upgrade ................................................................................................ 54◆ Upgrade the Service Assurance Management Suite .......................................... 54◆ Upgrading from SAM 8.1.1 to SAM 8.1.2 in FIPS mode...................................... 66◆ Manually merging configuration files................................................................ 67

Upgrading the Service Assurance Management Suite 53

Upgrading the Service Assurance Management Suite

Before upgradeThe user who performs the upgrade must either be superuser, on UNIX platforms, or have administrative privileges on Windows platforms. The installation program shuts down if the user does not have the appropriate privileges.

Note: You can upgrade to Service Assurance Management Suite version 8.1.2 from Service Assurance Management Suite version 8.1.1 and version 8.1.0.x only.

The installer will detect all services that are running from an existing Service Assurance Management Suite installation and will stop them automatically.

If the broker is running on the host with a Service Assurance Management Suite, then it will have to be stopped during an upgrade. The broker has to be stopped to prevent the impact on all the other applications running on the system.

On Unix platforms, if sm_service is running from the Service Assurance Management Suite , it will have to be stopped during an upgrade. If sm_service is stopped, then all sm_services running on the host and sm_services that do not run from Service Assurance Management Suite will be stopped.

Perform the following tasks before upgrading :

◆ “Uninstall the FLEXnet License Server” on page 111.

Upgrade the Service Assurance Management SuiteThis section describes how to upgrade Service Assurance Management Suite from a previous version of the EMC Ionix Service Assurance Management Suite. You can upgrade to Service Assurance Management Suite version 8.1.2 from Service Assurance Management Suite version 8.1.1 and version 8.1.0.x only.

The Service Assurance Management Suite is distributed on CD/DVD-ROM and is also available for download from EMC online support.

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



◆ Insert the CD/DVD-ROM into the optical drive of the host system. “Procedures for CD/DVD-ROMs” on page 127 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/DVD, there may be a delay of several minutes between the InstallShield preparation screen and the EMC Ionix splash screen/installation dialogs. During this time, the java.exe process is running. Please be patient. Do not eject/reinsert the CD/DVD to start a second install process

Before upgrading to Service Assurance Management Suite version 8.1.2, all the temporary test patches must be manually uninstalled. The installer detects the temporary test patches and prompts you to manually uninstall them. The installer will not proceed with the upgrade until all the temporary test patches are uninstalled.

Upgrade the Service Assurance Manager Server

This section describes the steps for upgrading the Service Assurance Manager Server.

Upgrade Service Assurance Manager Server 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 Ionix 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.

Upgrade using Wizard mode

To upgrade using wizard mode:

Upgrade the Service Assurance Management Suite 55


1. Run the Setup command appropriate for the operating system:


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.




5. Select Upgrade existing suite from the Installation Type screen and click Next.

Note: If you are adding additional components to your existing Service Assurance Management suite installation, select the Add additional features option from the Installation Type screen.

6. Select the suite to upgrade:

• If the installation program detects a single installation of the suite, it is selected.

• If the installation program detects multiple installations of the suite, select the suite to upgrade. Click Next.

7. If the installation has a patch installed, the patch will be uninstalled automatically at the end of the upgrade.

8. All previously installed products are selected by default, the installer will not proceed if they are unselected, click Next.

Table 19 Setup command syntax for Wizard mode




Windows setup-SAM-8_1_2_0-win64.exe



9. The installer detects services that are installed on your system. Click, Stop All Services and refresh the list to confirm the status of the service.

10. Click Next and review the list of products that will be installed and the target installation directory. The total amount of disk space required for the selected products is provided so that you can verify that adequate disk space is available. Click Next. The installation progress screen displays:

After this step you will not be able to cancel installation.11. Review the report and note its location for later reference. To continue, click Next.

The Installation Summary displays informational messages such as successful confirmations, error messages, and warnings.

12. All files that have been customized before upgrade will be copied to <BASEDIR>/smarts/.local.bkp.<version> directory. Custom changes have to be manually merged with the new versions of the files in the <BASEDIR>/smarts directory using sm_edit utility.

Upgrade Service Assurance Manager Server 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.

Upgrade using CLI mode

To start the CLI mode, invoke the setup command with the console option.

Table 20 The setup command syntax for CLI-mode






User selections and navigation in CLI mode

During the upgrade process, 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.


To navigate between each step, use these keys defined in Table 14 on page 39.

Upgrade Service Assurance Manager Server by using the unattended modeThe unattended 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.



Running the unattended mode


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

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


Each suite has a response file located on the CD/DVD-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 the 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/DVD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to change settings to:




Table 21 Server setup command syntax for unattended mode


Linux ./setup-SAM-8_1_2_0-linux64.bin -options <path>/<suite>-response.txt (for Linux RHEL AS4)./setup-SAM-8_1_2_0-linux-rhAS50-64.bin -options<path>/<suite>-response.txt (for Linux RHEL 5)

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

Windows setup-SAM-8_1_2_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.





• Set -W INSTALL_TYPE.INSTALL_CHOICE=UPGRADE



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


3. Save the file.

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

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

Upgrade Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using Wizard mode

Wizard 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 Ionix 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 mode

To upgrade the Service Assurance Manager Console:

1. Run the Setup command appropriate for the operating system:

The InstallShield wizard dialog box displays and closes. The InstallShield wizard dialog box displays and closes. The Shutdown EMC Ionix 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.




5. Select Upgrade existing suite from the Installation Type screen and click Next.

Note: If you are adding additional components to your existing Service Assurance Management suite 8.1 installation, select the Add additional features option from the Installation Type screen.

6. Select the suite to upgrade:

• If the installation program detects a single installation of the suite, it is selected.

• If the installation program detects multiple installations of the suite, select the suite to upgrade.

Table 22 Setup command syntax for Wizard mode




Windows setup-CONSOLE-8_1_2_0-win.exe



Click Next. The Upgrade Product screen is displayed.

7. Select the product or products you wish to upgrade and click Next. If the suite contains additional uninstalled products, you may add them at this time.

8. If you upgrade the Global Console, select the upgrade type in the Global Console Selection:

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

• Global Console, click Next.

9. If the installation has an earlier version of hotfix installed, the patch will be uninstalled automatically at the end of the upgrade.

10. All previously installed products are selected by default, the installer will not proceed if they are unselected, click Next.

11. The installer detects services that are installated on your system. Click, Stop All Services and refresh the list to confirm the status of the service.

12. Click Next and review the list of products that will be installed and the target installation directory. The total amount of disk space required for the selected products is provided so that you can verify that adequate disk space is available. Click Next. The installation progress screen displays:

After this step you will not be able to cancel installation.13. Review the report and note its location for later reference. To continue, click Next.

The Installation Summary displays informational messages such as successful confirmations, error messages, and warnings.

14. Reconcile the custom modified files manually into the upgraded installation directory. Custom modified files are located in the smarts/.local.bkp.<version> directory.

Upgrade Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using CLI mode

CLI 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 mode

To upgrade using the CLI mode, invoke the setup command with the console option.

Upgrade Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using unattended mode

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

Running unattended mode


Table 23 The setup command syntax for CLI-mode



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

Table 24 Console setup command syntax for unattended mode


Linux ./setup-CONSOLE-8_1_2_0-linux.bin -options <path>/<suite>-response.txt (for Linux RHEL AS4)./setup-CONSOLE-8_1_2_0-linux-rhAS50.bin -options <path>/<suite>-response.txt (for Linux RHEL 5)

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

Windows setup-CONSOLE-8_1_2_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.



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

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


The Console suite has a response file located on the CD/DVD-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/DVD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to the following settings:



◆ Perform an upgrade




• Set -W INSTALL_TYPE.INSTALL_CHOICE=UPGRADE



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


3. Save the file.



Upgrading to add the ITOI Adapter for UIM/O

You can add the ITOI Adapter for UIM/O to an existing Service Assurance Management Suite installation when you upgrade to SAM 8.1.2.

Follow the procedure to upgrade the Service Assurance Management Suite as described in “Upgrade the Service Assurance Manager Server” on page 55.

◆ Run one of the server setup commands for any of the upgrade modes (Wizard, CLI, or unattended).

◆ Select the Upgrade existing suite option from the Installation Type screen.

◆ Ensure that in the Feature Selection screen, the ITOI Adapter for UIM/O is selected.

◆ Ensure that in the Services Selection screen, the service for the ITOI Adapter for UIM/O is selected.

After the upgrade,

◆ Before you start the adapter, you must configure authentication credentials for accessing the UIM/O appliance and the Global Manager, and configure your web browser. The EMC Ionix ITOI Adapter for Unified Infrastructure Manager/Operations Configuration Guide provides configuration instructions.

◆ Start the adapter as described in Chapter 6, “Verifying the Installation.”

Note: The client tool scripts for the ITOI Adapter for UIM/O are installed when the Global Console for Service Assurance Management Suite Version 8.1 Service Pack 2 is installed. Consult “Upgrade Service Assurance Manager Console, or the ITOps NOTIF Editor, or both” on page 60 for instructions.



Upgrading from SAM 8.1.1 to SAM 8.1.2 in FIPS modeSAM 8.1.1 does not use a Federal Information Processing Standard (FIPS 140-2) approved encryption algorithm to protect the imk.dat file. Further, the SAM 8.1.1 imk.dat file uses MD5, which is not a FIPS-approved algorithm. Hence, while upgrading from SAM 8.1.1 to SAM 8.1.2, the imk.dat file needs to be regenerated in order to run in the FIPS mode.

In order to convert an existing installation to FIPS, use the sm_rebond (in non-FIPS mode) first to get everything re-encoded in a FIPS compatible way. The steps are as follows:

1. Run the following command at the command line prompt:

sm_rebond --upgrade --basedir=/opt/InCharge/SAM/smarts

The path must be set to the default install path. Regardless of the FIPS 140 state, the sm_rebond command must be invoked from the BASEDIR where the software is installed, not from any other product installation area which also has the sm_rebond utility.

2. When prompted, type a password to regenerate the imk.dat file. The default password is Not a secret.

3. Download and install the Unlimited Strength Jurisdiction Policy Files using the following steps:

a. Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html, and download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6 from the Additional Resources section.

b. Extract the local_policy.jar and US_export_policy.jar files from the downloaded zip file.

c. Go to the <BASEDIR>/smarts/jre/lib/security directory, and then backup the existing policy files in this path.

d. Overwrite the local_policy.jar and US_export_policy.jar files to the <BASEDIR>smarts/jre/lib/security directory.

4. Set the value for the environment variable, SM_FIPS140 to TRUE in the runcmd_env.sh file. This file is located in the <BASEDIR>/smarts/local/conf directory.



Manually merging configuration filesDuring an upgrade, all configuration files are backed up in the <BASEDIR>/smarts/.local.bkp.<version> directory. The <BASEDIR>/local folder will be cleared after an upgrade.

You will have to manually merge all the old customization.

The rps, clientConnect.conf, serverConnect.conf, runcmd_env.sh and imk.dat files will remain in the <BASEDIR>/local folder and don't need to be manually merged.

Where to go next

“Performing a Migration” on page 69 describes tasks for verifying the proper installation of the software and starting services.

Manually merging configuration files 67



CHAPTER 5Performing a Migration

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


◆ Overview of migration tasks ............................................................................. 70◆ Perform the migration procedure ...................................................................... 72◆ Migrating previous NOTIF versions to version 8.1.2........................................... 88◆ Verify the EMC Ionix version level ..................................................................... 91

Performing a Migration 69

Performing a Migration

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

◆ EMC Ionix Service Assurance Management Suite 7.2.0.x

◆ EMC Ionix Service Assurance Management Suite 8.0.0.x

Migration procedures apply to three different migration scenarios shown in Table 25 on page 70.

If you do not have a previous version or if you chose to start with version 8.1.2 and discard any previous version settings, configurations, or repositories, you can use procedures found in the EMC Ionix Service Assurance Management Suite Installation and Migration Guide.

Table 25 Migration scenarios

Migration scenario Example

“Migration to a different server with the same operating system” on page 72

Migrating from EMC Ionix Service Assurance Manager Product 7.2.0.x or 8.0.0.x on one server to Service Assurance Management Suite 8.1.2 on a different server running the same operating system.

“The EMC Ionix Service Assurance Management Suite Installation and Migration Guide provides information on uninstalling the Service Assurance Management Suite.” on page 77

Migrating from EMC Ionix Service Assurance Manager Product 7.2.0.x or 8.0.0.x on a server to Service Assurance Management Suite 8.1.2 on the same server running the same operating system.

“Migration to a different server with a different operating system” on page 83

Migrating from EMC Ionix Service Assurance Manager Product 7.2.0.x or 8.0.0.x on one server to Service Assurance Management Suite 8.1.2 on a different server running a different operating system.



Migrating custom patches

Migration requires that you consider any customizations made in the existing installation. Customizations such as modified configuration files and custom adapters need to be evaluated in order to complete the migration. “Where to get help” on page 14 provides instructions on contacting technical support for assistance in migrating custom patches for releases earlier than 8.1.2.

Service Assurance Management Suite 8.1.2 can be migrated from EMC Ionix Service Assurance Management Suite 7.2.0.x or 8.0.0.x.

If your current Service Assurance Management Suite installation is not at this version, you must first install the appropriate Service Pack to bring it to this version level before starting the 8.1.2 installation.

Determining current version of software

To determine your existing application and platform version level, perform the following:

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

sm_server --version

Note: The BASEDIR here is existing version of SAM.

2. EMC Ionix displays the following:

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

Operating System <Build>

For example:

winnt-i386_64BIT/200100SAM_SUITE: V8.1.2.0/64(105547), 18-Mar-2011 07:56:52 Copyright 1995-2011, EMC Corporation - Build 19Foundation V9.0.0.1/64(105051), 25-Feb-2011 14:59:13 Copyright 1995-2011, EMC Corporation - Build 168

Note: The output of the sm_server --version command is enhanced to include the operating system (OS) and build platform ID details. It helps in determining build versus running-on OS mismatches.

Overview of migration tasks 71


Note: Issuing the --version command from the SAM suite gives the version of SAM server, while issuing the command from the Console or selecting About > Help from Global console lists the version of Console suite. Product versions vary and do not always match the software platform version number. For example, if you select About from the Help menu in the Global Console, you may see a different number.

Perform the migration procedureThe following migration procedure is divided into the following scenarios:

◆ “Migration to a different server with the same operating system” on page 72

◆ “The EMC Ionix Service Assurance Management Suite Installation and Migration Guide provides information on uninstalling the Service Assurance Management Suite.” on page 77

◆ “Migration to a different server with a different operating system” on page 83

Before starting any of the processes, read the prerequisites of that scenario to make sure you comply with that scenario’s conditions and results.

Migration to a different server with the same operating system

Prerequisites To perform this type of migration, the following conditions must be met:

◆ You are migrating from a 7.2.0.x or 8.0.0.x Service Assurance Management Suite. If you have any other version, you must install the Service Pack to bring you to this version.

◆ If you use secret phrase encryption, you must know the secret phrase used for encryption in your EMC Ionix deployment. The secret phrase is part of the EMC Ionix security feature.

◆ If you installed any Service Assurance Management patches after the most recent Service Pack, review the BASEDIR/SAM/smarts/setup/info/manifest.md5 file.

Installing a Service Assurance Management patch installs files containing code fixes in the local directory structure. The manifest.md5 file provides a list of files that have been modified by the installation of any Service Assurance Management patch and their md5sum. To distinguish patch files from custom



files, compare the md5sum on the file installed to the md5sum of file in the manifest.md5 file. If values do not match, a file has been modified and must be evaluated for merging.

Files you may have modified are stored in the BASEDIR/SAM/local/conf directory, the BASEDIR/SAM/local/rules directory, or the BASEDIR/SAM/local/script directory. Files located in these directories must also be compared with the manifest.md5 file.

◆ If Professional Services created or modified any files, you must identify the files that were modified and decide if they must be migrated to the 8.1.2 release.

◆ You must migrate to a 64-bit version of the operating system.

Note: The system in which the Service Assurance Management Suite has been migrated should have the same protocol stack support as that of source system. If the source system supports IPv6, then system in which the migration will be performed should also support IPv6.

Migration process

The migration process is as follows:

1. Install the 8.1.2 Service Assurance Management Suite on the new server.

During the installation process, you are prompted:

• If you want to install services. It is strongly suggested that you do. If you do not install services at this point, you must install them manually later in the process (Step 7 on page 76).

2. After installation, all repository files (<domain_name>.rps) from the BASEDIR/SAM/smarts/local/repos/icf directory of a previous installation has to be copied into the BASEDIR/SAM/smarts/local/repos/icf directory of the 8.1.2 installation.

3. At the conclusion of the installation process, if you have changed your secret phrase from the default, run the sm_rebond utility in the 8.1.2 installation of the Service Assurance Management Suite to change the secret phrase used for encryption to match the one used in the rest of your deployment:

a. From a command line, go to:

C:\InCharge\SAM\smarts\bin (Windows)

or

Perform the migration procedure 73


/opt/InCharge/SAM/smarts/bin (UNIX)

b. Type the following command:

sm_rebond --basedir=InCharge\SAM\smarts

Note: This path assumes you used the default installation path. If you initially installed the application to a different path, use that path.

4. Follow the instructions for changing the secret phrase.

The EMC Ionix ITOps System Administration Guide provides additional information on this process.

If you do not know your secret phrase, contact EMC Customer Service and resolve this before continuing.

Note: In addition to changing the secret phrase, this utility is supposed to stop and restart any services running in the suite for which you changed the secret phrase.

5. Reconcile your file changes.

The following steps provide information on transferring modified files from a 7.2.0.x or 8.0.0.x installation to the new 8.1.2 installation:

Note: This process only applies to modified files under the 7.2.0.x or 8.0.0.x /local hierarchy.

• Files that have not changed between the base 7.2.0.x or 8.0.0.x and the 8.1.2 Service Assurance Manager releases but have been customized in your installation can be safely copied to the 8.1.2 installation. To check if the files have changed in 8.1.2 version, you can compare the files in the 7.2 or 8.0 <BASEDIR> to the file in 8.1.2 <BASEDIR>.

• Files that have changed between the 7.2.0.x or 8.0.0.x and the 8.1.2 Service Assurance Manager release, and that have been modified (under BASEDIR/smarts/local), must be compared to determine if the changes need to be made to the 8.1.2 versions of the file.



a. Versions of configuration files you have modified.

The Service Assurance Manager 8.1.2 includes many configuration changes. Configuration files that you manually modified must be carefully merged.

In addition, you can safely migrate any of the following:

– Saved consoles

– Saved maps

– Custom map background images

– ASL hook scripts

– ASL filters

– Custom tool scripts (client, server, and automatic)

b. User-modifiable files under BASEDIR/smarts/local that changed between the 7.2.0.x or 8.0.0.x and 8.1.2 releases of Service Assurance Management Suite.

Compare 7.2.0.x or 8.0.0.x and 8.1.2 user-modifiable files to identify differences that may affect operation of the suite:

– Files that changed between Service Assurance Manager 7.2.0.x or 8.0.0.x.

– Files located in the BASEDIR/smarts/local/ rules and script directories have change significantly and must be merged carefully to the 8.1.2 installation location.

User-modifiable files are files located in the BASEDIR/smarts/local conf, script, and rules directories.

Note: Many files related to the configuration of Service Assurance Manager have changed from previous releases and only the versions included with 8.1.2 should be used.

c. Files that were modified by a patch.

Files applied by a patch after applying a Service Pack are installed in the /local directory. However, the Service Assurance Management Suite 8.1.2 release has incorporated the changes in all previous patches. Therefore, you do not need to migrate these files from the 7.2.0.x or 8.0.0.x /local directories unless you customized them after applying the patch.



Note: You cannot copy the changed file from 7.2.0.x or 8.0.0.x directory. You can only make the change through the sm_edit utility on the 8.1.2 version of each file.

If a patch was installed after the last 7.2.0.x or 8.0.0.x Service Pack, you need to identify the user-modifiable files that were modified by that patch. Review the BASEDIR/SAM/smarts/setup/info/manifest.md5 file to determine which files were modified. These files are identified in each patch Readme file in a way similar to the following example:

Changed Components:rules/ics/show-impact.slactions/server/show-impact.cmd (Windowsactions/server/show-impact.sh (Unix)

The applicable files were installed by a patch after the 7.2.0.x or 8.0.0.x Service Pack was applied.

Note: To distinguish user modified files from patch files you can uninstall the patch. The uninstaller will remove only the files in which md5sum matches the md5sum value in manifest.md5 file. If the md5sum is different the file will not be removed. Files that remain after the local patch uninstall are the files that have not been modified. When patch uninstall is not possible, the md5sums of files in local need to be compared to values in manifest.md5 file.

6. Migrate your 7.2.0.x or 8.0.0.x license file. Appendix Appendix D, “License Migration Procedure,”provides additional information.

7. If you did not install services during the installation, you need to install them at this point. Appendix Appendix A, “Manually Installing Services,”provides instructions on how to install services.

8. If you installed the Broker during the Service Assurance Management Suite installation, for each server registered with the Broker, you need to use the sm_edit utility to edit the SM_BROKER_DEFAULT variable in the runcmd_env.sh file in each of those server’s BASEDIR/smarts/local/conf directory with the hostname (and port) of the machine running the Broker.

Note: If the Broker host is resolved using a DNS name, this step is not necessary.



9. Start the Service Assurance Management Suite. It is important that you also start the Service Assurance Manager Adapter Platform. “Verify the EMC Ionix version level” on page 91 provides additional information.

10. When you are satisfied that the Service Assurance Management Suite 8.1.2 is running and all services are functioning properly, you should uninstall version 7.2.0.x or 8.0.0.x of the Service Assurance Management Suite from the BASEDIR of the server where 7.2.0.x or 8.0.0.x Service Assurance Management Suite was installed. This will prevent conflicts if the 7.2.0.x or 8.0.0.x version of Service Assurance Management Suite is started up by mistake while 8.1.2 is running.

The EMC Ionix Service Assurance Management Suite Installation and Migration Guide provides information on uninstalling the Service Assurance Management Suite.

Migration to the same server with the same operating system

Prerequisites To perform this form of migration, the following conditions must be met:

◆ You are migrating from a 7.2.0.x or 8.0.0.x Service Assurance Management Suite version. If you have any other version, you must install the Service Pack to bring you to one of these versions.

◆ You cannot install version 8.1.2 of the Service Assurance Management Suite in the same directory as version 7.2.0.x or 8.0.0.x of the Service Assurance Management Suite.


◆ If you installed any Service Assurance Management patches after the most recent Service Pack, review the BASEDIR/SAM/smarts/setup/info/manifest.md5 file.

Installing a Service Assurance Management patch installs files containing code fixes in the local directory structure. The manifest.md5 file provides a list of files that have been modified by the installation of any Service Assurance Management patch and their md5sum. To distinguish patch files from custom files, compare the md5sum on the file installed to the md5sum of file in the manifest.md5 file. If values do not match, a file has been modified and must be evaluated for merging.



Files you may have modified are stored in the BASEDIR/SAM/local/conf directory, the BASEDIR/SAM/local/rules directory, or the BASEDIR/SAM/local/script directory. Files located in these directories must also be compared with the RP.MANIFEST file.

◆ If Professional Services created or modified any files, you must identify the files that were modified and decide if they can be migrated to the 8.1.2 release.

◆ You need to consider the impact on the system if you reboot your Service Assurance Management Suite server during the migration process. This applies only if you are running Windows 2003 Enterprise Edition, SP2 for your server’s operating system.

◆ Run BASEDIR\smarts\bin>sm_service.exe show on Windows systems or BASEDIR/smarts/bin>sm_service.exe show --cmdline on UNIX systems from your 7.2.0.x or 8.0.0.x server to get a listing of all installed services. Save the output.

Example:

C:\InCharge\IP\smarts\bin>sm_service.exe show ic-sam-server

For each service you have installed, you will see output similar to:

sm_service install --force --name=ic-broker "--description=SMARTS InCharge Broker" --env=SM_CLIENTCONNECT=brokerConnect.conf --startmode=runonce C:\InCharge\SAM\smarts\bin\brstart.exe "--port=426" "--restore=C:\InCharge\SAM/smarts/local/repos /broker/broker.rps" "--output"

Migration process


1. Install the 8.1.2 Service Assurance Management Suite. “Install the Service Assurance Management Suite” on page 34 provides detailed information on installing the Service Assurance Management Suite.

During the installation process, you are prompted:

• If you want to install services. It is strongly suggested that you do. If you do not install services at this point, you must install them manually later in the process (Step 7 on page 76).

• For the location of the previous 7.2.0.x or 8.0.0.x installation. Enter the path of the SAM BASEDIR from where the migration is taking place, for example <BASEDIR>\SAM. After installation, all repository files (<domain_name>.rps) from



the BASEDIR/SAM/smarts/local/repos/icf directory of a previous installation will be copied into the BASEDIR/SAM/smarts/local/repos/icf directory of the 8.1.2 installation, by the installer.

2. At the conclusion of the installation process, if you have changed your secret phrase from the default, run the sm_rebond utility in the 8.1.2 installation of the Service Assurance Management Suite to change the secret phrase used for encryption to match the one used in the rest of your deployment:



or






The EMC Ionix ITOps System Administration Guide provides detailed information about this process.








• Files that have not changed between the base 7.2.0.x or 8.0.0.x and the 8.1.2 Service Assurance Manager releases but have been customized in your installation can be safely copied to the 8.1.2 installation. To check if the files have changed in 8.1.2 version, you can compare the files in the 7.2 or 8.0 <BASEDIR> to the file in 8.1.2 <BASEDIR>.





– Saved consoles

– Saved maps



– ASL filters

– Custom tool scripts (client, server, and automatic)












If a patch was installed after the last 7.2.0.x or 8.0.0.x Service Pack, you need to identify the user-modifiable files that were modified by that patch. Review the BASEDIR/SAM/smarts/setup/info/manifest.md5 file to determine which files were modified. These files are identified in each patch Readme file in a way similar to the following example:

Changed Components:rules/ics/show-impact.slactions/server/show-impact.cmd (Windowsactions/server/show-impact.sh (Unix)


Note: To distinguish user modified files from patch files you can uninstall the patch. The uninstaller will remove only the files in which md5sum matches the md5sum value in manifest.md5 file. If the md5sum is different the file will not be removed. Files that remain after the local patch uninstall are the files that have not been modified. When patch uninstall is not possible, the md5sums of files in local need to be compared to values in manifest.md5 file.

5. Migrate your 7.2.0.x or 8.0.0.x license file. Appendix Appendix D, “License Migration Procedure,” provides additional information.



6. If you are installing the 8.1.2 Broker during the Service Assurance Management Suite installation to a location different than the 7.2.0.x or 8.0.0.x broker, for each server registered with the Broker, you need to use the sm_edit utility to edit the SM_BROKER_DEFAULT variable in the runcmd_env.sh file in each of those server’s BASEDIR/smarts/local/conf directory with the hostname (and port) of the machine running the broker.


7. Start the Service Assurance Management Suite. It is important that you also start the Service Assurance Manager Adapter Platform. Appendix Appendix A, “Manually Installing Services,” provides additional information.

8. When you are satisfied that the Service Assurance Management Suite 8.1.2 is running and all services are functioning properly, you should uninstall version 7.2.0.x or 8.0.0.x of the Service Assurance Management Suite from the BASEDIR of the server where 7.2.0.x or 8.0.0.x Service Assurance Management Suite was installed.

For Windows only, if you use the Windows “Add/Remove Programs” capability at this point, you will be incorrectly uninstalling version 8.1.2 instead of 7.2.0.x or 8.0.0.x. Therefore, you must uninstall the 7.2.0.x or 8.0.0.x application using the uninstaller.exe from the 7.2.0.x or 8.0.0.x BASEDIR.

This will prevent conflicts if the 7.2.0.x or 8.0.0.x version of Service Assurance Management Suite is started up by mistake while 8.1.2 is running. The EMC Ionix Service Assurance Management Suite Installation and Migration Guide provides additional information.

Note: Uninstall will display errors if services were installed by the installation program when they installed 7.2.0.x or 8.0.0.x, but the services were removed by hand, since the uninstall process will try to remove them and they will not be there.



Migration to a different server with a different operating system

Prerequisites To perform this form of migration, the following conditions must be met:

◆ You are migrating from a 7.2.0.x or 8.0.0.x version of Service Assurance Management Suite. If you have any other version, you must install the Service Pack to bring you to one of these versions.


◆ If you installed any Service Assurance Management patches after the most recent Service Pack, review the BASEDIR/SAM/smarts/setup/info/RP.MANIFEST file.

Installing a Service Assurance Management patch installs files containing code fixes in the local directory structure. The RP.MANIFEST file provides a list of files that have been modified by the installation of any Service Assurance Management patch. To distinguish patch files from custom files, compare the time stamp on the file installed to the time stamp of the file in the RP.MANIFEST file. If dates do not match, a file has been modified and must be evaluated for merging. Time stamps in the RP.MANIFEST file are in epoch format and must be manually converted into date format.

Files you may have modified are stored in the BASEDIR/SAM/local/conf directory, the BASEDIR/SAM/local/rules directory, or the BASEDIR/SAM/local/script directory. Files located in these directories must also be compared with the RP.MANIFEST file.

◆ If Professional Services created or modified any files, you must identify the files that were modified and decide if they can be migrated to the 8.1.2 release.

Note: The system in which the Service Assurance Management Suite has been migrated should have the same protocol stack support as that of source system. If the source system supports IPv6, then system in which the migration will be performed should also support IPv6.



Migration process


1. Install the 8.1.2 Service Assurance Management Suite.

Note: During the installation process, you will be asked if you want to install services. It is strongly suggested that you do. If you do not install services at this point, you must install them manually later in the process (step 8 ).

2. After installation, all repository files (<domain_name>.rps) from the BASEDIR/SAM/smarts/local/repos/icf directory of a previous installation has to be copied into the BASEDIR/SAM/smarts/local/repos/icf directory of the 8.1.2 installation.

3. At the conclusion of the installation process, if you have changed your secret phrase from the default, run the sm_rebond utility in the 8.1.2 installation of the Service Assurance Management Suite to change the secret phrase used for encryption to match the one used in the rest of your deployment.



or






The EMC Ionix ITOps System Administration Guide provides additional information.








• Files that have not changed between the base 7.2.0.x or 8.0.0.x and the 8.1.2 Service Assurance Manager releases but have been customized in your installation can be safely copied to the 8.1.2 installation.





– Saved consoles

– Saved maps



– ASL filters

– Tool scripts (client, server, and automatic)












If a patch was installed after the last 7.2.0.x or 8.0.0.x Service Pack, you need to identify the user-modifiable files that were modified by that patch. Review the BASEDIR/SAM/smarts/setup/info/RP.MANIFEST file to determine which files were modified. These files are identified in each patch Readme file in a way similar to the following example:

Changed Components:rules/ics/show-impact.slactions/server/show-impact.cmd (Windows)actions/server/show-impact.sh (Unix)


6. After you have addressed the reconciliation process in step 5 , you need to determine if you are changing your operating system from Windows to UNIX or from UNIX to Windows as part of this migration. If you are, run the UNIX command



line utility, dos2unix or unix2dos, against all the files that were involved in the reconciliation process. Your UNIX man page on these UNIX utilities provides additional information.

7. Migrate your 7.2.0.x or 8.0.0.x license file. Appendix Appendix D, “License Migration Procedure,” provides additional information.

8. If you did not install services during the installation, you need to install them at this point. Appendix Appendix A, “Manually Installing Services,” provides detailed instructions.

9. For each server registered with the Broker, you need to use the sm_edit utility to edit the SM_BROKER_DEFAULT variable in the runcmd_env.sh file in each of those server’s BASEDIR/smarts/local/conf directory with the hostname (and port) of the machine running the broker.


10. Start the Service Assurance Management Suite. It is important that you also start the Service Assurance Manager Adapter Server. “Start EMC Ionix products” on page 94 provides additional information.

11. When you are satisfied that the Service Assurance Management Suite 8.1.2 is running and all services are functioning properly, you should uninstall version 7.2.0.x or 8.0.0.x of the Service Assurance Management Suite from the BASEDIR of the server where 7.2.0.x or 8.0.0.x Service Assurance Management Suite was installed. This will prevent conflicts if the 7.2.0.x or 8.0.0.x version of Service Assurance Management Suite is started up by mistake while 8.1.2 is running. The EMC Ionix Service Assurance Management Suite Installation and Migration Guide provides information on uninstalling the Service Assurance Management Suite.



Migrating previous NOTIF versions to version 8.1.2

Prerequisites

Before you migrate a previous NOTIF version to ITOps NOTIF 8.1.2, you must meet the following requirements on the Adapter Platform/SAM server where you want to migrate your pre-ITOps NOTIF 8.1.2 configuration:

◆ The EMC Ionix Service Assurance Management Suite 8.1.2 (which

includes ITOps NOTIF 8.1.2) must be installed and running.

Note: The EMC Ionix Service Assurance Management Suite Migration Guide provides information on how to migrate a SAM 7.x system to SAM 8.1.2.

◆ ITOps NOTIF 8.1.2 must be enabled on the Adapter Platform/SAM server.

Note: The EMC Ionix ITOps Notification Module User Guide provides information on how to enable ITOps NOTIF.

Notes on the SAM 7.x to 8.1.2 migration process

During the SAM 7.x to 8.1.2 migration process, the repository files (<domain_name>.rps) are copied from the SAM 7.x installation to SAM 8.1.2 in the new SAM 8.1.2 directory location. (Repository files are located in the BASEDIR/smarts/local/repos/directory.) Therefore, after you migrate your SAM 7.x system to SAM 8.1.2, there will still be NOTIF objects in the repository on your SAM 8.1.2 system.

Note: These NOTIF objects in the repository are not yet in effect on the SAM 8.1.2 system.

Although there are instructions in the EMC Ionix Service Assurance Management Suite Migration Guide to copy over customized files from the BASEDIR/smarts/local/ directories that changed between the 7.x and 8.1.2 releases of Service Assurance Management Suite, existing NOTIF users should not copy over customized NOTIF files from the /local directories on the 7.x system. (User-modifiable files are files located in the BASEDIR/smarts/local/conf, /script, and /rules directories.)



IMPORTANT

Do not copy over NOTIF files from the /local directories in your SAM 7.x system to the SAM 8.1.2 system.

In particular, existing NOTIF users should not copy over the following NOTIF files from the SAM 7.x system to the SAM 8.1.2 system:

◆ local/rules/ics/Notif-init.asl

◆ local/rules/ics/Notif-dxa-nl-hook.asl

◆ local/rules/ics/Notif-dxa-analysis-hook.asl

◆ local/conf/ics/Notif.import

◆ local/conf/ics/Notif-Settings.import

Migrate previous NOTIF version to ITOps NOTIF 8.1.2

To migrate your previous NOTIF version to ITOps NOTIF 8.1.2:

1. Start the SAM server or SAM Adapter Platform Server using the migrated repository files.

2. If FIPS mode is enabled, replace com.netmg.notif.gui.NotifApplication with -Dcom.smarts.fips_mode=true com.netmg.notif.gui.NotifApplication in the NotifGui.bat or NotifGui.sh file. This file is located under the <BASEDIR>/CONSOLE/smarts/notif/editor/ or <BASEDIR>/SAM/smarts/notif/editor directory.

Else, proceed to Step 3.

3. Execute the NotifMigrate.bat file (for Windows systems) or the NotifMigrate.sh file (for UNIX systems) in the BASEDIR/smarts/notif/editor directory on the SAM 8.1.2 Adapter Platform/SAM server where you want to migrate your pre-ITOps NOTIF 8.1 configuration.

NotifMigrate.bat or the NotifMigrate.sh utility connects to a running SAM or Adapter platform server, uses its repository to search for any existing NOTIF objects, and saves these objects in the migrated.ncf file in the supplied configuration directory. An .ncf file is an ITOPs NOTIF configuration file. The generated migrated.ncf file will be saved to BASEDIR/smarts/local/conf/<configDirectory>. The utility will later delete the older NOTIF objects in the running server

Migrating previous NOTIF versions to version 8.1.2 89


NotifMigrate.sh or NotifMigrate.bat utility requires parameters to execute the following command:

./NotifMigrate.sh <broker> <domain> <user> <pwd> <configDirectory>

Note: The configuration directory (<configDirectory>) for SAM server is ics and for SAM Adapter Platform Server is icoi.

For example:

./NotifMigrate.sh localhost:426 INCHARGE-OI admin changeme icoi

This executable program will search for NOTIF objects in the SAM 8.1.2 repository and convert them to an .ncf file. An .ncf file is an ITOps NOTIF configuration file. The generated *.ncf file is then saved to the BASEDIR/smarts/local/conf/<directoryname> directory on the Adapter Platform/SAM server.

4. Use sm_edit to add “export SM_JAVA_ENABLED=YES” line in the runcmd_env.sh file.

5. Select the Remote > Manage Connections menu option in the ITOps NOTIF Editor to add a connection to the migrated server.

6. Select Remote > Edit a Server's Settings > Connect to Server menu option in the ITOps NOTIF Editor to select the migrated server and click Ok. Enter the password of the server if prompted and select Activate ITOps NOTIF and click Ok.

7. Restart the migrated Adapter Platform/SAM server.

Note: When the servers are restarted, they will read, and load the NOTIF configuration objects from all the ncf files located in local/conf/ics or local/conf/icoi directory. If the same directories are used in step 1 , the configuration objects from migrated.ncf file will be read and loaded during server startup.

8. When the ics or icoi configuration directories are not used in Step 1, then perform the following steps to push the NOTIF configurations into the SAM Server or SAM Adapter Platform Server.

1. Launch the ITOps NOTIF Editor on the Adapter Platform/SAM server by selecting Start > Programs > InCharge > ITOps NOTIF Editor.



2. Select the File > Open Configuration menu option in the ITOps NOTIF Editor.

The Open Notif Config File dialog box appears, showing the *.ncf file that was generated in the BASEDIR/smarts/local/conf/<directoryname> directory on the Adapter Platform/SAM server.

Click Open and the pre-ITOps NOTIF 8.1.2 configuration displays in the ITOps NOTIF Editor.

Note: The EMC Ionix ITOps Notification Module User Guide provides information on how to open, create, merge, and save configurations using the ITOps NOTIF Editor.

3. Click, Remote > Push to Server to push the configuration into the server. To reload the server select Remote > Reload Server.

Verify the EMC Ionix version levelTo determine your existing application and platform version level:

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

sm_server --version

or

To verify the license, verify the SM_LICENSE parameter in the runcmd_env.sh file at the following location:

BASEDIR/smarts/local/conf/runcmd_env.sh

2. EMC Ionix displays version information using the following syntax:

<Application Suite> V<Application version> <Date and time of build> - <Build number> Copyright <Date>, EMC CorporationFoundation V<Platform version> <(InternalBuildNumber)> <Date and time of build> - <Build <number> Copyright <Date>, EMC Corporation

where <Application Suite> is in the format <Major Release>.<Minor Release>.<SmartPack>.<Rolling Patch>

For example:

Verify the EMC Ionix version level 91


SAM_CONSOLE_SUITE: winnt-i386/200100 SAM_CONSOLE_SUITE: V8.1.2.0(104617), 07-Feb-2011 13:09:49 Copyright 1995-2011, EMC Corporation - Build 8 Foundation V7.2.0.1(104571), 05-Feb-2011 14:53:27 Copyright 1995-2011, EMC Corporation - Build 164

SAM SERVER SUITE: solaris2.8-sparc_64BIT/21000SAM_SUITE: V8.1.2.0/64(104618), 07-Feb-2011 14:24:21 Copyright

1995-2011, EMC Corporation - Build 8Foundation V7.2.0.1/64(104571), 05-Feb-2011 14:51:49 Copyright

1995-2011, EMC Corporation - Build 164


CHAPTER 6Verifying the Installation

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


◆ Obtain and install a temporary license file........................................................ 94◆ Start EMC Ionix products .................................................................................. 94◆ Start EMC Ionix programs ................................................................................. 96◆ Start ITOps NOTIF ........................................................................................... 103◆ Verify the EMC Ionix product status ................................................................ 105◆ Verifying FIPS 140 mode status ...................................................................... 106◆ Where to go next ............................................................................................ 106

Verifying the Installation 93

Verifying the Installation

Obtain and install a temporary license fileThe EMC Corporation will send a temporary license to you by e-mail. Copy the license file, smarts.lic, to the BASEDIR/smarts/local/conf directory on the system where the EMC Ionix software is installed. If the evaluation license has a different name, rename it to smarts.lic.

◆ If multiple EMC Ionix 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 Ionix 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 Ionix software is installed so that it specifies the full path and filename of a single smarts.lic file. When multiple EMC Ionix 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 Ionix 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 sending an e-mail to [email protected] with your request.

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

Start EMC Ionix productsThe following sections describe methods for starting EMC Ionix services.

EMC Ionix recommends installing Managers and adapters as services. If you installed the products as services, you must start them for the first time. These services start automatically when you restart the system, but the following sections describe additional methods to start EMC Ionix services.

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

Appendix A, “Manually Installing Services,” and the EMC Ionix ITOps System Administration Guide provides detailed information.



Starting services on UNIX

Verify the status of the service daemon before starting a service.

Verifying the status of the service daemon

Use 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

If the sm_serviced process does not respond, the process is not running. Start the service by typing the following 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 Ionix services

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

Start EMC Ionix products 95


Example of starting a service

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>

For Windows type:

# BASEDIR\smarts\bin\sm_service start ic-trap-receiver

Starting services on Windows

To start an EMC Ionix service from the Windows desktop:

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

2. Select Services.

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

4. Select Start from the menu.

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

Start EMC Ionix programsYou can start EMC Ionix 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 Ionix ITOps System Administration Guide provides a complete description of the command syntax. “Manually Installing Services” on page 119 provides more information on manually installing a product as a service.



Starting programs on UNIX

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

Starting the EMC Ionix Broker

To start the EMC Ionix Broker, type the following command:

./brstart --port=426 --output

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

▼ ./brstart --port=426--output --daemon--backup=/opt/InCharge/SAM/smarts/local/

repos/broker/test-broker.rps--restore=/opt/InCharge/SAM/smarts/local/

repos/broker/test-broker.rps ▲

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

Starting Service Assurance Manager Server

To start the Service Assurance Manager Server, type the following command:

▼ sm_server--name=INCHARGE-SA--broker=localhost:426--config=ics--ignore-restore-errors--output --daemon ▲


Starting SAM Adapter Platform Server

To start the SAM Adapter Platform Server, type the following command:

▼ sm_server--name=INCHARGE-OI--broker=localhost:426--config=icoi--ignore-restore-errors--output --daemon ▲

Start EMC Ionix programs 97


Starting SNMP Trap Adapter

To start the SNMP Trap Adapter, type the following command:

▼ sm_trapd--name=TRAP-INCHARGE-OI--server=INCHARGE-OI--broker=localhost:426--config=icoi--port=162--model=sm_actions--rules=icoi-trapd/trap_mgr_parse.asl--output --daemon ▲


Starting SNMP Trap Adapter (when NOTIF is running on Adapter platform server)

To start the SNMP Trap Adapter when NOTIF is running on Adapter platform server, type the following command:

▼ sm_trapd--name=TRAP-INCHARGE-OI--server=INCHARGE-OI--broker=localhost:426--config=icoi--port=162--model=sm_actions--rules=icoi-trapd/Notif-trap_mgr_parse.asl--output--daemon ▲


Starting Syslog Adapter

To start the Syslog Adapter, type the following command:

▼ sm_adapter--name=SYSLOG-INCHARGE-OI--broker=localhost:426--server=INCHARGE-OI--tail=/var/log/syslog--model=sm_system--model=sm_actions--outputicoi-syslog/syslog_mgr.asl ▲




Starting Syslog Adapter (when NOTIF is running on adapter platform server)

To start the Syslog Adapter when notif is running on adapter platform server, type the following command:

▼ sm_adapter--name=SYSLOG-INCHARGE-OI--broker=localhost:426--server=INCHARGE-OI--tail=/var/log/syslog--model=sm_system--model=sm_actions--outputicoi-syslog/Notif-syslog_mgr.asl▲


Starting Business Impact Manager

To start the Business Impact Manager, type the following command:

▼ sm_server--name=INCHARGE-MBIM--broker=localhost:426--config=bim--ignore-restore-errors--output--daemon ▲


Starting ITOI Adapter for UIM/O

To start the ITOI Adapter for UIM/O, type the following command:

▼./sm_server--name=ITOI-Adapter-UIMO--config=uima--java--port=0 --ignore-restore-errors --output--daemon ▲




SAM 8.1.2 Console crashes when running commands on a Linux platform since the FIPS library fails to load. SELinux prevents the shared libraries, libcryptocme2.so and libccme_base.so from loading because of the existence of text relocation in the library.

The following workarounds are available to avoid the SAM 8.1.2 Console crash:

◆ Run the following commands to change the file context for the shared libraries, libcryptocme2.so and libccme_base.so to textrel_shlib_t:

chcon -t textrel_shlib_t libcryptocme2.sochcon -t textrel_shlib_t libccme_base.so

◆ Set the parameter setenforce to 0 to run SELinux in permissive mode.

◆ Navigate to Edit /etc/selinux/config and set the parameter SELINUX to Disabled.

Starting programs on Windows

To start a program on Windows, invoke the command with the appropriate options from the BASEDIR\smarts\bin directory.

Starting the EMC Ionix Broker

To start the EMC Ionix Broker, type the following command:

▼ brstart.exe --port=426--output--backup=C:\InCharge\SAM\smarts\local\repos\

broker\test-broker.rps--restore=C:\InCharge\SAM\smarts\local\repos\

broker\test-broker.rps ▲


Starting Service Assurance Manager Server

To start the Service Assurance Manager Server, type the following command:

▼ sm_server.exe--name=INCHARGE-SA--broker=localhost:426



--config=ics--ignore-restore-errors--output ▲


Starting SAM Adapter Platform Server

To start the SAM Adapter Platform Server, type the following command:

▼ sm_server.exe--name=INCHARGE-OI--broker=localhost:426--config=icoi--ignore-restore-errors--output ▲


Starting SNMP Trap Adapter

To start the SNMP Trap Adapter, type the following command:

▼ sm_trapd.exe--name=TRAP-INCHARGE-OI--server=INCHARGE-OI--broker=localhost:426--config=icoi--port=162--model=sm_actions--rules=icoi-trapd/trap_mgr_parse.asl--output ▲


Starting SNMP Trap Adapter (when NOTIF is running on Adapter platform server)

To start the SNMP Trap Adapter when NOTIF is running on Adapter platform server, type the following command:

▼ sm_trapd.exe--name=TRAP-INCHARGE-OI--server=INCHARGE-OI--broker=localhost:426--config=icoi--port=162--model=sm_actions--rules=icoi-trapd/Notif-trap_mgr_parse.asl



--output--daemon ▲


Starting Syslog Adapter

To start the Syslog Adapter, type the following command:

▼ sm_adapter.exe--name=SYSLOG-INCHARGE-OI--broker=localhost:426--server=INCHARGE-OI--tail=/var/log/syslog--model=sm_system--model=sm_actions--outputicoi-syslog/syslog_mgr.asl ▲


Starting Syslog Adapter (when NOTIF is running on Adapter Platform Server)

To start the Syslog Adapter when NOTIF is running on Adapter Platform Server, type the following command:

▼ sm_adapter.exe--name=SYSLOG-INCHARGE-OI--broker=localhost:426--server=INCHARGE-OI--tail=/var/log/syslog--model=sm_system--model=sm_actions--outputicoi-syslog/Notif-syslog_mgr.asl ▲


Starting Business Impact Manager

To start the Business Impact Manager, type the following command:

▼ sm_server.exe--name=INCHARGE-MBIM--broker=localhost:426--config=bim--ignore-restore-errors--output ▲




Starting ITOI Adapter for UIM/O

To start the ITOI Adapter for UIM/O, type the following command:

▼ sm_server.exe--name=ITOI-Adapter-UIMO--config=uima--java--port=0 --ignore-restore-errors --output ▲


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=YESexport SM_JAVA_ENABLED

2. Configure the SNMP Trap Adapter to use the Notif-trap_mgr_parse.asl script instead of the default trap_mgr_parse.asl script so that ITOps NOTIF processes SNMP traps.

For example:

./sm_trapd --name=TRAP-OI --server=INCHARGE-OI --config=icoi--port=162 --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.

Start ITOps NOTIF 103


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 --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 > 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 server or Adapter Platform server. Select Remote > Edit a server's settings in the ITOps NOTIF Editor. The Connect to a Server dialog box appears, showing the list of available Adapter Platform and SAM server connections.

6. Choose a server from the list of available server connections in the Connect to a Server dialog box and click OK.

If server connections are not displayed, perform the following to populate the list of server connections:

a. Click More in the Connect to a Server dialog box. The Manage Connections dialog box appears where you can add server connections.

b. Click Add 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 appears that shows 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 server or 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 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 Ionix 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 Ionix 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.

Note: More than one log file may be generated due to changes in the foundation code supporting internationalization. The EMC Ionix ITOps System Administration Guide provides additional information on log files.

Verify the EMC Ionix product status 105


If only one log file per server is desired, use sm_edit to update the BASEDIR/smarts/local/conf/runcmd_env.sh file. To get a single log file, set the following environment variables:

export SM_LOCALE=en_US (or appropriate locale code)export SM_ENCODING_OUTPUT=UTF-8

Verifying FIPS 140 mode statusTo check if the installation is running in FIPS-140 mode, run the following command in the dmctl mode:

get SM_System::SM-System::FIPS

The value for this parameter must be TRUE.

You can also check for the status of FIPS 140, in the log files located in the <BASEDIR>/smarts/local/logs. When the broker and server starts on FIPS 140 mode, the following information is written in the broker and server log files:

RSA BSAFE: MES 3.2.4 26-November-2010/64(0), FIPS: RSA BSAFE Crypto-C Micro Edition FIPS 140-2 Module 3.0.0.0/64(0), May 31 2008 13:19:56

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

1. Configure the Adapter Platform. The EMC Ionix Service Assurance Manager Adapter Platform User Guide provides detailed information.

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

3. Install permanent licenses. The EMC Ionix ITOps System Administration Guide provides detailed information.

4. Configure security. The EMC Ionix ITOps System Administration Guide provides detailed information.

5. Start the Global Console. The EMC Ionix Service Assurance Manager Operator Guide provides detailed information.



6. Configure the Global Manager to receive notifications from the Domain Managers. The EMC Ionix Service Assurance Manager Configuration Guide provides additional information.

Where to go next 107



CHAPTER 7Uninstalling Service Assurance Management Suite

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


◆ Before uninstallation...................................................................................... 110◆ Uninstalling Service Assurance Management Suite......................................... 112

Uninstalling Service Assurance Management Suite 109

Uninstalling Service Assurance Management Suite

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

◆ “Remove manually installed services” on page 110

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

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

◆ “Uninstall the FLEXnet License Server” on page 111

Remove manually installed services

Services 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 Ionix suites from the same server, the EMC Ionix suite that was installed first must be uninstalled last. During the installation of the first EMC Ionix suite, the EMC Ionix 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.

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 Ionix 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 Ionix product suite to uninstall.

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

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

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

If you uninstall EMC Ionix products without uninstalling the FLEXnet License Server, a message appears that the FLEXnet (lmgrd) service is still running. Keep in mind that an EMC Ionix 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

Before uninstallation 111


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 Ionix product suites use InstallShield software to install and uninstall product suites. For UNIX, invoke the uninstallation program from the system prompt. For Windows, 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 mode

Wizard mode provides a graphical user interface to the uninstallation 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 Ionix software and the host where you log in must be configured to run the X Window System. Before starting the installation program by using the Wizard mode, verify that the X Window System is running. To uninstall using wizard mode:

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 appears, click it and restart your system. 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 Ionix 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 mode

To uninstall an EMC Ionix product or product suite:

1. Type the following command and press Enter:

# BASEDIR/_uninst/uninstaller.bin -console

During the uninstallation processes, a series of steps and menus prompt. 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 reinstall 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 mode

The unattended mode enables you to automate the removal of EMC Ionix product suites. To uninstall using unattended mode:

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

The ITOps NOTIF application cannot be uninstalled separately from SAM 8.1.2 because the ITOps NOTIF processor is included as part of the SAM 8.1.2 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 > 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 appears that shows 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.




APPENDIX AManually Installing Services

This appendix consists of the following sections:

◆ Overview........................................................................................................ 120◆ Service Assurance Management Suite services............................................... 121

Manually Installing Services 119

Manually Installing Services

OverviewIf you did not install services when you installed the EMC Ionix products suite, you can install services manually. Services are programs that are generally intended to run continuously. Components installed as services start automatically when once they are started not installed as services (manual processes or disabled processes), require you to issue commands to start and stop them as necessary.

EMC Corporation recommends that EMC Ionix products should 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 Ionix ITOps System Administration Guide provides a complete description of the command syntax.



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

EMC Ionix Broker

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

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

broker/broker.rps--output ▲

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

--port=426 --restore=C:\InCharge\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/InCharge/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-sam-server--startmode=runonce --description="EMC Ionix Service Assurance Manager

Server"/opt/InCharge/SAM/smarts/bin/sm_server--name=INCHARGE-SA

Service Assurance Management Suite services 121


--config=ics--port=0--ignore-restore-errors--output ▲

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

Server"C:\InCharge\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/InCharge/SAM/smarts/bin/sm_service install --startmode=runonce--name=MBIM--description=”EMC Ionix MBIM – Maintenance and Business Impact

Manager Server”/opt/InCharge/SAM/smarts/bin/sm_server--name=INCHARGE-MBIM--config=bim--port=0--ignore-restore-errors--output▲

Windows ▼C:\InCharge\SAM\smarts\bin\sm_service.exe install --startmode=runonce--name=MBIM--description=”EMC Ionix MBIM – Maintenance and Business Impact

Manager Server”C:\InCharge\SAM\smarts\bin\sm_server.exe--name=INCHARGE-MBIM--config=bim--port=0--ignore-restore-errors--output▲




Adapter Platform

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

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


Business Dashboard

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



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


Syslog Adapter

Before you configure the Syslog Adapter, identify the location of the SYSFILE you want the adapter to tail and parse and ensure that sm_service install command line for the ic-syslog-adapter identifies this location. The EMC Ionix Service Assurance Manager Adapter Platform User Guide provides more information on configuring the Syslog Adapter.

UNIX ▼ /opt/InCharge/SAM/smarts/bin/sm_service install --force--unmanaged--name=ic-syslog-adapter--startmode=runonce--description="EMC Ionix Syslog Adapter"/opt/InCharge/SAM/smarts/bin/sm_adapter--name=SYSLOG-INCHARGE-OI--rserver=INCHARGE-OI--tail=/var/log/syslog--model=sm_system--model=sm_actions--output

icoi-syslog/syslog_mgr.asl ▲

Windows ▼ C:\InCharge\SAM\smarts\bin\sm_service.exe install--force--name=ic-syslog-adapter--description="EMC Ionix Syslog Adapter"--startmode=runonceC:\InCharge\SAM\smarts\bin\sm_adapter.exe--name=SYSLOG-INCHARGE-OI--rserver=INCHARGE-OI--tail=/var/log/syslog--model=sm_system--model=sm_actions--output

icoi-syslog/syslog_mgr.asl ▲




SNMP Trap Adapter

UNIX ▼ /opt/InCharge/SAM/smarts/bin/sm_service install--force--unmanaged--name=ic-trapd-receiver--startmode=runonce --description="EMC Ionix SNMP Trap Adapter"/opt/InCharge/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:\InCharge\SAM\smarts\bin\sm_service.exe install--force--name=ic-trapd-receiver--startmode=runonce --description="EMC Ionix SNMP Trap Adapter"C:\InCharge\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 ▲




ITOI Adapter for UIM/O

UNIX ▼ /opt/InCharge/SAM/smarts/bin/sm_service install --force--unmanaged--name=ic-itoi-adapter-uimo --description="EMC Ionix ITOI Adapter for UIM/O"--startmode=runonce /opt/InCharge/SAM/smarts/bin/sm_server --name=ITOI-Adapter-UIMO--config=uima--java--port=0 --ignore-restore-errors --output ▲

Windows ▼ C:\InCharge\SAM\smarts\bin\sm_service install --force--unmanaged--name=ic-itoi-adapter-uimo--description="EMC Ionix ITOI Adapter for UIM/O"--startmode=runonce C:\InCharge\SAM\smarts\bin\sm_server.exe --name=ITOI-Adapter-UIMO--config=uima--java--port=0 --ignore-restore-errors --output ▲



APPENDIX BProcedures for CD/DVD-ROMs

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

This chapter consists of the following sections:

◆ Mounting a CD/DVD-ROM on UNIX systems .................................................... 128◆ Loading a CD/DVD-ROM on Windows.............................................................. 130

Procedures for CD/DVD-ROMs 127

Procedures for CD/DVD-ROMs

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

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

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

Table 26 Mounting the CD/DVD-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.



3. Change to the CD/DVD-ROM directory by typing the appropriate command from Table 27 on page 129.

Table 27 Changing to the CD/DVD-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.

Mounting a CD/DVD-ROM on UNIX systems 129


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

1. Insert the CD/DVD-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/DVD-ROM.

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


APPENDIX CUnderstanding the sm_edit Utility

This appendix contains the following information:

◆ The sm_edit utility.......................................................................................... 132

Understanding the sm_edit Utility 131

Understanding the sm_edit Utility

The sm_edit utilityAs part of the EMC Ionix deployment and configuration process, you need to modify certain files. User-modifiable files include configuration files, rule set files, templates, and files (such as seed files and security configuration files) that contain encrypted passwords. Original versions of these files are installed into appropriate subdirectories under the BASEDIR/smarts/ directory.

Examples:

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

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

Original versions of files should not be altered. If a file requires modification, it must be stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories.

Examples:

A modified dxa-sam.conf file on UNIX should be saved to /opt/InCharge/SAM/smarts/local/conf/ics

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

Ionix software is designed to first search for user-modifiable files in BASEDIR/smarts/local or one of its subdirectories. If a modified version of a file is not found in the local area, Ionix software then searches appropriate nonlocal directories.

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

To invoke the sm_edit utility from the command line, specify the path and the name of the file to edit under BASEDIR/smarts. If multiple Ionix products are running on the same host, invoke sm_edit from the bin directory of the product suite with the files to edit.



Example:

To edit the configuration file for the Global Manager, invoke the sm_edit utility as follows:

# /opt/InCharge/SAM/smarts/bin>sm_edit conf/ics/dxa-sam.conf

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

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

The sm_edit utility 133



APPENDIX DLicense Migration Procedure

This appendix describes how to migrate an existing 7.2.0.x or 8.0.0.x license file as part of migrating to EMC Ionix version 8.1.2 and includes the following topics:

◆ Prerequisites.................................................................................................. 136◆ Migrate permanent license and set up FLEXnet license server......................... 137◆ Access to FLEXnet license server using SM_LICENSE ....................................... 140

License Migration Procedure 135

License Migration Procedure

PrerequisitesThis section provides the procedure for migrating the license server. The EMC Ionix ITOps System Administration Guide provides complete information about EMC Ionix licensing, including how to obtain license files, deployment considerations, and troubleshooting.

Before you begin, you need to be aware of the following considerations:

◆ You can use your existing 7.2.0.x or 8.0.0.x license file provided that you have not: acquired more features, increased the number of licenses, or changed machines (host IDs).

If you have acquired more features, increased the number of licenses, or changed machines, then you must obtain a new license file. The EMC Ionix ITOps System Administration Guide provides instructions to obtain a permanent license file.

◆ You will need to use the FLEXnet 11.9.0.0 license server provided with EMC Ionix version 8.1.2 software. The setup instructions are described in the following subsection.

FLEXnet software is backward-compatible. For example, a newer license manager daemon (lmgrd) will work with older vendor daemons and older FLEXnet-licensed products. So a FLEXnet 11.9.0.0 license server provided with EMC Ionix version 8.1.2 software will work with FLEXlm 9.2 license files distributed for EMC Ionix version 7.2.0.x or 8.0.0.x software, but not the other way round.

This license migration procedure is similar to the procedure used to set up licensing for a new installation with the following differences:

◆ You can reuse your existing license file for step 3 .

◆ You stop the old license server in step 6 and uninstall it in step 8 .

◆ If you set up the new FLEXnet license server on the same system as the old license server, you do not need to modify the SM_LICENSE variable for your other EMC Ionix software installations.

Note: For the following procedure, you need administrative privileges for both the EMC Ionix software and the systems on which the software is running.



Note: In this discussion, a temporary license file is referred to as smarts.lic and a permanent license file is referred to as <host_id>.smarts.lic. These are the names of the license files when they are generated and sent to you by the EMC Corporation. If you install a license server with the install_license script described later, you should be aware that the script changes the permanent license filename from <host_id>.smarts.lic to smarts.lic.

Migrate permanent license and set up FLEXnet license server

On the system where the EMC Ionix Broker resides, perform these steps to migrate the permanent license file and set up the new server:

1. If you have not already installed the 8.1.2 software, do so. Install the software on the same system in a different directory than the older software.

If you installed the software on a different system, you need a new license file.

2. If you previously used a temporary license (copied smarts.lic to the BASEDIR/smarts/local/conf directory), you need to delete it because it will cause the install_license script to fail later in step 5

3. Copy your existing permanent license file, <host_id>.smarts.lic, from the old installation directory to the new BASEDIR directory on the system where the license server will run.

Typically, this location should be the same host and BASEDIR as for the EMC Ionix Broker. By default, BASEDIR is /opt/InCharge/<productsuite> for UNIX and C:\InCharge\<productsuite> for Windows.

If you obtained a new permanent license file, save the attachment to a file named <host_id>.smarts.lic in your BASEDIR directory on the system where the license server will run.

Do not save the permanent license file (<host_id>.smarts.lic) to the BASEDIR/smarts/local/conf directory. The install_license script will fail if it finds a permanent license file in this directory. Also, do not save a permanent license file to the BASEDIR/smarts/script or BASEDIR/smarts/conf directory.

Migrate permanent license and set up FLEXnet license server 137


Later, as the result of step 5 , the install_license script installs the permanent license file into the BASEDIR/smarts/local/conf directory.

4. If necessary, you may need to change the port for the FLEXnet license server (which will be installed in step 5 ). For example, if the default port, 1744, is used by another process, the FLEXnet license server can run on a different port. Do not make any changes to the permanent license file unless you need to change the port.

Use any text editor to open the <host_ID>.smarts.lic file. The first line of the permanent license file, labelled SERVER, contains the hostname, host ID, and port of the license server, as shown in the following example:

SERVER this_host 8323fcbf 1744

Change the port number from the default (“1744”) on the SERVER line and save the file.

The EMC Ionix ITOps System Administration Guide for instructions contains information on deploying the FLEXnet license server on the opposite side of a firewall from your other Ionix software installations.

5. Install the FLEXnet license server using the install_license script. By default, this file is located in the BASEDIR/smarts/script directory.

You must run the install_license script on the same system where the license server runs. This script requires superuser privileges (user ID 0) for UNIX, and administrator privileges for Windows. You must specify the full path to the permanent license file.

For example, the command on UNIX systems is:

▼ # /opt/InCharge/SAM/smarts/script>install_license.sh install <path to license file>/<host_ID>.smarts.lic ▲

On Windows systems, for example, the command is:

▼ C:\InCharge\SAM\smarts\script>install_license.cmd install <path to license file>\<host_ID>.smarts.lic ▲

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

In addition to installing the FLEXnet license server, the install_license script performs other functions such as configuring the license server to start when the system reboots. The EMC Ionix ITOps System Administration Guide provides additional information.



6. Stop the old license server. Use the same command in step 7 except substitute stop for start.

7. Start the FLEXnet license server. The FLEXnet license server runs as a daemon on UNIX and as a service on Windows and automatically starts the vendor daemon for EMC Ionix. Issue the command appropriate for your platform.

Solaris:

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

Linux:

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

Windows:

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

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

2. Select Services.

3. Select the FLEXlm License Manager service.

4. Right-click and select Start.

5. Verify that the new FLEXlm license server started by checking your EMC Ionix Manager log file. To do so, start your EMC Ionix Manager and view the EMC Ionix Manager log file for two messages that indicate success:

• ICF-N-LICENSEDFEATURE-Enabling

• ICF-N-RESTOREFINISH-PersistenceManager: restore finished

The log filename is based upon the EMC Ionix Manager’s name (for example, INCHARGE-SA.log) and the log file is located in the BASEDIR/smarts/local/logs directory.

The installation guide that accompanied your product suite includes instructions on starting your EMC Ionix Manager.

Note: On the system where the FLEXnet license server and EMC Ionix Broker reside, for a permanent license file, you do not need to edit the SM_LICENSE variable in the runcmd_env.sh file for that product suite, because by default the install_license script adds the SM_LICENSE variable with the appropriate values. If other product suites were already deployed on the same system, you do not need to

Migrate permanent license and set up FLEXnet license server 139


manually edit the SM_LICENSE variable in the runcmd_env.sh file for those product suites if the new FLEXnet license server is set up on the same system as the old license server. If the new FLEXnet license server is set up on a different system than the old license server or if you installed other 8.1.2 product suites on the same system, you need to manually edit the SM_LICENSE variable in the runcmd_env.sh file for those product suites. “Access to FLEXnet license server using SM_LICENSE” on page 140 provides additional information. For example, if the Service Assurance Management Suite and IP Management Suite reside on System1 and the install_license script is invoked from the /opt/InCharge/SAM/smarts/script directory, the script modifies the variable, but you will have to modify the variable for the 8.1 IP Management Suite.

8. Uninstall the old license server using the install_license script.

For example, Command on UNIX systems is:

# /opt/InCharge/SAM/smarts/script>install_license.sh uninstall

Command on Windows systems is:

C:\InCharge\SAM\smarts\script>install_license.cmd uninstall

Access to FLEXnet license server using SM_LICENSE

Note: If you set up the new FLEXnet license server on the same system as the old license server, you do not need to modify the SM_LICENSE variable for other EMC Ionix software installations. You can skip this task.

When you install EMC Ionix software on more than one system, you must ensure that the EMC Ionix software on each system can connect to the FLEXnet license server in order to be able to check out licenses. For the system where you installed the FLEXnet license server, the SM_LICENSE variable is added automatically by the install_license script. For other EMC Ionix software installations, you need to modify the variable.

To set up licensing for other product suites or the Global Console, you need to set the SM_LICENSE variable to specify the <port>@<lic_host> of the FLEXnet license server.



Use the sm_edit utility to edit the SM_LICENSE variable in the runcmd_env.sh file. The runcmd_env.sh file resides in the BASEDIR/smarts/local/conf directory of the product suite.

Perform the following steps:

1. For UNIX, invoke sm_edit from the BASEDIR/smarts/bin directory:

% sm_edit conf/runcmd_env.sh

To open runcmd_env.sh on Windows, invoke sm_edit utility as follows:

C:\>sm_edit conf\runcmd_env.sh

For example on Windows, type:

C:\InCharge\SAM\smarts\bin>sm_edit conf\runcmd_env.sh

2. Set the SM_LICENSE variable to <port>@<lic_host> of the FLEXnet license server.

The runcmd_env.sh file should resemble the following:

SM_BROKER_DEFAULT=localhost:426SM_LICENSE=1744@SYSTEM1 SM_SNMP_BUG_COMPATIBLE=TRUESM_INCOMING_PROTOCOL=1,0SM_OUTGOING_PROTOCOL=1,0

3. Save the runcmd_env.sh file and close it.

4. Any EMC Ionix program within a product suite started after this point will use the applicable environment variables specified in the runcmd_env.sh file. EMC Ionix programs that are already running need to be restarted for any new environment variable to take effect. The installation guide that accompanied your product suite provides information on starting services.

Access to FLEXnet license server using SM_LICENSE 141



Date post:	22-Mar-2018
Category:	Documents
Upload:	dinhdien
View:	227 times
Download:	0 times

EMC Ionix Service Assurance Management Suite · PDF fileEvent Explorer, FarPoint, FirstPass,...

Documents