EMC Ionix Service Assurance Management Suite · 2020-06-19 · EMC® Ionix™ Service Assurance Management Suite Version 9.0 Installation and Migration Guide P/N 300-012-983 REV A02

EMC® Ionix™

Service Assurance Management SuiteVersion 9.0

Installation and Migration GuideP/N 300-012-983REV A02

EMC Ionix Service Assurance Management Suite Version 9.0 Installation and Migration Guide2

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

Published February, 2012

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

Preface

Chapter 1 Overview

Suite contents............................................................................................. 16Default installation directories .............................................................. 18

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

Chapter 2 Requirements

Operating system requirements .................................................................. 24 Hardware requirements............................................................................... 25 Web Console and Business Dashboard requirements .................................. 27

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

Chapter 3 Installing the Service Assurance Management Suite

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

Install the Service Assurance Management Suite......................................... 32Installing the Service Assurance Manager Server................................... 33Installing the Service Assurance Manager Console, or the ITOps NOTIF Editor, or both ....................................................................................... 38Installing the ITOI Adapter for UIM/O..................................................... 42Support for FIPS 140-2 in SAM 9.0......................................................... 42Enabling FIPS 140 mode on a new installation ...................................... 43Disabling FIPS 140 mode ...................................................................... 44Launching SAM 9.0 Web Console, Global Console, Dashboard and NOTIF .. 45Where to go next ................................................................................... 46

Chapter 4 Perform a Migration

Overview of migration tasks ........................................................................ 48Migration prerequisites ......................................................................... 48Migrating to Service Assurance Management Suite ............................... 48Determining current version of software ................................................ 48Install and migrate on a different host ................................................... 49Install and migrate on the same host..................................................... 50

Overview of customization migration .......................................................... 52 Customization migration scenarios ............................................................. 54

Migrating customizations on the same host .......................................... 54Migrating customizations on a different host......................................... 55

Custom file migration use cases.................................................................. 57 Three-way merge utility ............................................................................... 59

EMC Ionix Service Assurance Management Suite Version 9.0 Installation and Migration Guide 3

Contents

Use cases for content block comparison ............................................... 60Configuration migration process logs .................................................... 61Known limitation ................................................................................... 61

Migrating previous NOTIF versions to version 9.0......................................... 62Prerequisites......................................................................................... 62Notes on the SAM 7.x to 9.0 migration process ..................................... 62Migrate previous NOTIF version to ITOps NOTIF 9.0................................ 63

Verify the EMC Ionix version level ................................................................ 65

Chapter 5 Verifying the Installation

Obtain and install a temporary license file................................................... 68Events and attributes for license expiry alert ......................................... 69

Start EMC Ionix products............................................................................. 69Starting services on UNIX ...................................................................... 70Starting services on Windows................................................................ 71

Start EMC Ionix programs ............................................................................ 71Starting programs on UNIX .................................................................... 71Starting programs on Windows.............................................................. 74

Start ITOps NOTIF ........................................................................................ 77 Verify the EMC Ionix product status ............................................................. 79 Verifying FIPS 140 mode status ................................................................... 80 Collect system information.......................................................................... 81 Where to go next ......................................................................................... 85

Chapter 6 Uninstalling Service Assurance Management Suite

Before uninstallation................................................................................... 88Remove manually installed services...................................................... 88Determine order for removing products (UNIX only) ............................... 88Uninstall when the same product suite is installed twice (Windows only) ... 89

Uninstalling Service Assurance Management Suite...................................... 90Uninstall using Wizard mode................................................................. 90Uninstall using CLI mode....................................................................... 91Uninstall using unattended mode ......................................................... 92Disabling ITOps NOTIF ........................................................................... 93

Appendix A Manually Installing Services

Overview..................................................................................................... 96 Service Assurance Management Suite services ........................................... 96

EMC Ionix Broker ................................................................................... 96Service Assurance Manager (Global Manager) ....................................... 97Business Impact Manager server........................................................... 97Adapter Platform ................................................................................... 98Business Dashboard ............................................................................. 98Syslog Adapter...................................................................................... 99SNMP Trap Adapter ............................................................................. 100ITOI Adapter for UIM/O ........................................................................ 100

Appendix B Procedures for CD/DVD-ROMs

Mounting a CD/DVD-ROM on UNIX systems ............................................... 104 Loading a CD/DVD-ROM on Windows ........................................................ 105

4 EMC Ionix Service Assurance Management Suite Version 9.0 Installation and Migration Guide

Contents

Appendix C Understanding the sm_edit Utility

The sm_edit utility .................................................................................... 108

Appendix D License Migration Procedure

Prerequisites............................................................................................. 110 Migrate permanent license and set up FLEXnet license server.................... 111 Access to FLEXnet license server using SM_LICENSE.................................. 114

Appendix E Custom migration sample outputs

Getting help on the usage of customization migration utility ..................... 116 Running customization migration utility in same host................................ 116 Extracting files needed for migration from old installation ......................... 120 Using archive extracted from the old installation on the new host.............. 122 Conflict file output .................................................................................... 127

Appendix F Customization migration utility file examples

Previous installation base file contents ..................................................... 130 Previous installation base local file contents ............................................. 130 New installation base file contents............................................................ 130

Content block 1 :................................................................................. 130Content block 2:.................................................................................. 131Content block 3:.................................................................................. 131


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............................................................................... 205 Uninstallation requirements and tasks........................................................................ 216 Supported operating system for the suite.................................................................... 247 Required operating system patches ............................................................................ 258 Typical hardware for the equipment tiers..................................................................... 259 Required disk space for the Service Assurance Manager Server................................... 2610 Required disk space for the Service Assurance Manager consoles............................... 2611 CPU, memory, data disk space requirements............................................................... 2612 Server setup command syntax for Wizard mode .......................................................... 3313 Server setup command syntax for CLI-mode ................................................................ 3514 Navigation keys........................................................................................................... 3615 Server setup command syntax for unattended mode ................................................... 3716 Console setup command syntax for Wizard mode........................................................ 3817 Console setup command syntax for CLI-mode ............................................................. 4018 Console setup command syntax for unattended mode ................................................ 4119 Custom file migration use cases.................................................................................. 5720 Content block comparison use cases .......................................................................... 6021 Log file and description............................................................................................... 6122 Mounting the CD/DVD-ROM for UNIX operating systems ............................................ 10423 Changing to the CD/DVD-ROM directory in UNIX operating systems ........................... 104


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.

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

◆ Companion User Interface (CUI)


Preface

◆ 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

◆ 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


Preface

◆ 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 Notification Module User Guide

◆ EMC Ionix Service Assurance Management Suite Troubleshooting Guide

◆ EMC Ionix Service Assurance Manager Companion User Interface Installation and Configuration Guide

◆ EMC Ionix Service Assurance Manager Companion User Interface Online Help

◆ EMC Ionix Service Assurance Manager Companion User Interface Open Source License and Copyright Information for GPLv3 as Included with a Distribution of SLES 11

◆ EMC Ionix Service Assurance Management Suite Documentation Portfolio

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.


Preface

IMPORTANT

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

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.

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.

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

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

Preface


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......................................................................................... 20◆ Uninstallation tasks overview.................................................................................. 21

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

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.

◆ Companion User Interface

EMC Ionix Service Assurance Manager Companion User Interface (SAM Companion UI) supplements existing functionality in SAM, EMC Ionix Network Configuration Manager (NCM) and Watch4net Automated Performance Grapher (APG).

The SAM Companion UI is a VMware®-based appliance, that is, a virtual machine. The EMC Ionix Service Assurance Manager Companion User Interface Installation and Configuration Guide provides detailed information about installing and configuring the SAM Companion UI.

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


Overview

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

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.

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.

Suite contents 17

Overview

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

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

EMC Ionix product suite Versions

EMC Ionix Server Manager (EISM) 3.0, 9.0

EMC Ionix Application Connectivity Monitor (ACM) 2.3

EMC Ionix IP Management Suite 7.0.x, 8.1.x, 9.0

EMC Ionix MPLS Management Suite (MPLS) 4.0.x, 9.0

EMC Ionix Multicast Manager (MCAST) 2.1.x

EMC Ionix Network Protocol Management Suite (NPM) 3.1.x

EMC Ionix Optical Transport Management Suite (OTM) 5.1

EMC Ionix Service Assurance Management Adapter Suite

1.3

EMC Ionix Service Assurance Management Suite 8.1.x, 9.0

EMC Ionix Storage Insight for Availability (SIA) 2.3.x

EMC Ionix VoIP Management Suite 4.0


Overview

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

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

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

EMC Ionix product suite Versions

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 68

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

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

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 33• “Install Service Assurance Manager Server by

using the CLI mode” on page 35, UNIX only

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

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

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

After you install:

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

EMC Ionix ITOps System Administration Guide

Installation tasks overview 19

Overview

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

Save your license in the proper location:• Evaluation license — Save <license_name>.lic to the

BASEDIR/smarts/local/conf directory.

Note: In this discussion, a temporary license file is referred to as <license_name>.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 70• “Starting services on Windows” on page 71

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

Table 3 Installation requirements and tasks (2 of 2)

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. EMC Ionix ITOps System Administration Guide

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

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

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 33• “Install Service Assurance Manager Server by

using the CLI mode” on page 35, UNIX only

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

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

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


Overview

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

After you install:

Save your license in the appropriate location:• Evaluation license — Save <license_name>.lic to the

BASEDIR/smarts/local/conf directory. • 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 70• “Starting services on Windows” on page 71

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

Table 4 Migration requirements and tasks (2 of 2)

Before you migrate:

Table 5 Uninstallation requirements and tasks

Before you uninstall:

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

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

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

• “Uninstall the FLEXnet License Server” on page 89

• “Uninstall the FLEXnet License Server” on page 89

Uninstallation:

Uninstall the Service Assurance Management Suite • “Uninstall using Wizard mode” on page 90• “Uninstall using CLI mode” on page 91• “Uninstall using unattended mode” on

page 92• “Disabling ITOps NOTIF” on page 93

Uninstallation tasks overview 21

Overview


CHAPTER 2Requirements

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


◆ Operating system requirements .............................................................................. 24◆ Hardware requirements........................................................................................... 25◆ Web Console and Business Dashboard requirements .............................................. 27

Requirements 23

Requirements

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

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.

Table 6 Supported operating system for the suite

Operating system Supported version

Red Hat Enterprise Linux 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 10, 64-bitSun zone 10

Windows Windows Server 2008 Enterprise Edition SP2Windows Server 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 4.x Windows 2008 Enterprise Edition R2Red Hat Enterprise Linux 5.4


Requirements

Recommended patch levelsTable on page 25 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.

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

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

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.

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 (M4000)

SPARC64 VII (M4000)

Hardware requirements 25

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 26 lists disk space requirements for installing the Service Assurance Manager Server.

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

Table 10 Required disk space for the Service Assurance Manager consoles

Table 11 on page 26 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.

Table 9 Required disk space for the Service Assurance Manager Server

Platform Disk space

Solaris 10 730 MB

Red Hat Enterprise Linux AS5 475 MB

Windows Server 2008 R2 2.7 GB

Platform Disk space

Solaris 10 485 MB

Red Hat Enterprise Linux AS 5 365 MB

Windows Server 2008 R2, 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.


Requirements

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

For the XML Adapter, disk space depends on the size of the output 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 26 defines required disk space and Table 11 on page 26 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

Tomcat Servlet Engine version 6.0.30 or above 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, 7.0, 8.0, 9.0

• Firefox 2, 3.5, 3.6, 4.0, and 5.0

• Google Chrome 12.0

• Safari 3.0

• Browser that supports Java JRE 1.6.x

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.

Web Console and Business Dashboard requirements 27

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.

In SAM 9.0, Red Hat Enterprise Linux AS 5, Windows Server 2008 R2, 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 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.


Requirements

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.

The Installation Guide may not be updated for patch or service pack releases. For the most up-to-date information about a release, refer to the Release Notes.

Web Console and Business Dashboard requirements 29

Requirements


CHAPTER 3Installing the Service Assurance Management Suite

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


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

Installing the Service Assurance Management Suite 31

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 32 provides additional information.

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

Determine the location of the EMC 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

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

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

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:

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

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.

Table 12 Server setup command syntax for Wizard mode

Operating system Setup command

Linux ./setup-SAM-9_0_0_0-linux-rhAS50-64.bin

Solaris ./setup-SAM-9_0_0_0-sol64.bin

Windows setup-SAM-9_0_0_0-win64.exe

Install the Service Assurance Management Suite 33


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.

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)

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.

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

Table 13 Server setup command syntax for CLI-mode

Operating system Executable

Linux ./setup-SAM-9_0_0_0-linux-rhAS50-64.bin <setup_file> -console

Solaris ./setup-SAM-9_0_0_0-sol64.bin -console



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.

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

“Where to go next” on page 46 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.

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

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:

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.

Table 15 Server setup command syntax for unattended mode


Linux ./setup-SAM-9_0_0_0-linux-rhAS50-64.bin -options<path>/<suite>-response.txt

Solaris ./setup-SAM-9_0_0_0-sol64.bin -options <path>/<suite>-response.txt

Windows setup-SAM-9_0_0_0-win64.exe -options <path>\<suite>-response.txt

where <path> is the fully qualified path to the response file and <suite> is the product suite, for example, NPM_SUITE, IP_NETWORK_SUITE, MPLS_SUITE, or SAM_SUITE.



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 modeWizard 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 38.

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.

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

Table 16 Console setup command syntax for Wizard mode

Operating system Setup command

Linux ./setup-CONSOLE-9_0_0_0-linux-rhAS50.bin

Solaris ./setup-CONSOLE-9_0_0_0-sol.bin

Windows setup-CONSOLE-9_0_0_0-win.exe



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)

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.

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 46 provides information on post-installation tasks.

Install Service Assurance Manager Console, or the ITOps NOTIF Editor, or both using 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 17 on page 40.

Refer to “User selections and navigation in CLI mode” on page 36 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 36.

“Where to go next” on page 46 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.

Table 17 Console setup command syntax for CLI-mode


Linux ./setup-CONSOLE-9_0_0_0-linux-rhAS50.bin./<setup_file> -console

Solaris ./setup-CONSOLE-9_0_0_0-sol.bin -console



Running unattended mode

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

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

Modifying the response file

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:

◆ Support Windows operating systems

◆ Specify a different Broker location

To modify the response file:

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.

Table 18 Console setup command syntax for unattended mode


Linux ./setup-CONSOLE-9_0_0_0-linux-rhAS50.bin -options <path>/<suite>-response.txt

Solaris ./setup-CONSOLE-9_0_0_0-sol.bin -options <path>/<suite>-response.txt

Windows setup-CONSOLE-9_0_0_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.



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

◆ 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 5, “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.

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

Support for FIPS 140-2 in SAM 9.0

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 and SAM 9.0 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 43

◆ “Disabling FIPS 140 mode” on page 44

◆ “Verifying FIPS 140 mode status” on page 80

◆ “Launching SAM 9.0 Web Console, Global Console, Dashboard and NOTIF” on page 45

Enabling FIPS 140 mode on a new installation

When you install SAM 9.0, FIPS 140 is not enabled by default. You must enable FIPS 140 on a clean installation, 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.



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.

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 43”. 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 9.0 Web Console, Global 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. To enable FIPS mode for the Global Console, 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 4, “Perform a Migration,” describes additional tasks if you are migrating from a previous version of the suite.

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


CHAPTER 4Perform a Migration

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


◆ Overview of migration tasks .................................................................................... 48◆ Overview of customization migration ...................................................................... 52◆ Customization migration scenarios ......................................................................... 54◆ Custom file migration use cases.............................................................................. 57◆ Three-way merge utility ........................................................................................... 59◆ Migrating previous NOTIF versions to version 9.0..................................................... 62◆ Verify the EMC Ionix version level ............................................................................ 65

Perform a Migration 47

Perform a Migration

Overview of migration tasksThis chapter provides migration instructions for the previous version of SAM to SAM 9.0.

Migration prerequisites

The following are requirements for migration:

◆ You can only perform a migration on the same host if:

• The operating system hosting the previous version is 64-bit. If the previous host is 32-bit, you must migrate to a different host.

• The operating system is supported. See “Operating system requirements” on page 24.

• There is enough disk space and memory on the host so both versions of the Service Assurance Management Suite can co-exist. See “Hardware requirements” on page 25.

Migrating to Service Assurance Management Suite

If you have a previous version of Service Assurance Management Suite installed and want to migrate to the current version, two methods exist:

◆ Install and migrate on a different host

◆ Install and migrate on the same host

Make sure you read the sections “Install and migrate on a different host” on page 49 and “Install and migrate on the same host” on page 50 in their entirety before proceeding.

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

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-x86-64/206110SAM_SUITE: V9.0.0.0/64(111370), 15-Nov-2011 21:57:04 Copyright 1995-2011, EMC Corporation - Build 145DMT V9.0.1.1/64(111109), 05-Nov-2011 02:08:07 Copyright 1995-2011, EMC Corporation - Build 15


Perform a Migration

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.

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.

Install and migrate on a different host

If you want to run the new version of Service Assurance Management Suite before decommissioning the previous version, you must:

1. Install the new version of Service Assurance Management Suite on a different host.

2. Migrate any customized configuration file changes to the new installation.

Detailed instructions are described in “Procedure to migrate SAM on a different host” on page 49.

Because the two installations are on different hosts, you can run both installations in parallel. You have the option of:

◆ Having both installations connect to the same Global Manager and Broker.

Managers registered with the same Broker must have unique names. In this scenario, stop and rename the services for the previous SAM version and, when you install SAM 9.0, the installation program will use the default server names.

◆ Having multiple instances of the Global Manager and Broker with each instance assigned to a different version of SAM.

Procedure to migrate SAM on a different hostTo migrate the old version of Service Assurance Management Suite to the new version on a different host, satisfy or perform the following tasks.

1. Review the important release issues for Service Assurance Management Suite version 9.0, as described in the EMC Ionix Service Assurance Management Suite Release Notes.

2. Determine if the products that you are installing for the Service Assurance Management Suite are supported for your platform. Chapter 2, “Requirements,” provides more information.

3. On the new host, mount the CD-ROM. Appendix B, “Procedures for CD/DVD-ROMs,” provides more information.

4. Install the new version of Service Assurance Management Suite on the new host. Chapter 3, “Installing the Service Assurance Management Suite,” provides more information.

Overview of migration tasks 49

Perform a Migration

5. Uninstall any TTPs if they exist in your old installation.

6. Run the custom migration tool (sm_migrate) to copy customizations from the earlier SAM installation to the new SAM installation. “Overview of customization migration” on page 52 explains how the migration utility works. “Migrating customizations on a different host” on page 55 provides sample commands for migrating your old Service Assurance Management Suite file to the new installation.

7. Evaluate your security settings. “Migration of security configuration files” on page 58 provides more information.

8. Evaluate environment variables in the old runcmd_env.sh file. “Migration of security configuration files” on page 58 provides more information.

9. Evaluate your custom code. Review the “Custom file migration use cases” on page 57 to plan your post-migration steps. The sm_migrate utility migrated all custom code introduced by you under <BASEDIR>/smarts/local in the new installation. It also made a backup copy of the files under <BASEDIR>/smarts/.local.bkp.version. Review the output of sm_migrate utility and evaluate if you would like to keep your custom code in the new installation.

10. Check your rps files in <BASEDIR>/smarts/local/repos/icf. The rps files from previous installations will appear with the old version number appended to the file name. To use the rps file, remove the version number in the file name and run the server normally.

11. If you installed the products as services, start them for the first time. “Starting services on UNIX” on page 70 or “Starting services on Windows” on page 71 provide more information.

12. Verify the current state of the products and Broker. “Verify the EMC Ionix product status” on page 79 provides more information.

13. Decommission the previous version of Service Assurance Management Suite. For instructions, refer to Chapter 6, “Uninstalling Service Assurance Management Suite,” for the previous software version.

Install and migrate on the same host

To migrate from a previous version of Service Assurance Management Suite on the same host to the current version, you must:

1. Stop the old services for the previous version of Service Assurance Management Suite. For UNIX, keep the service daemon (the sm_serviced component) running.

2. Install the 9.0 Service Assurance Management Suite and specify a directory name different from the one used for older SAM release installations.

3. Migrate any customized configuration file changes to the new installation.

Detailed instructions are described in “Procedure to migrate SAM on the same host” on page 51.


Perform a Migration

Procedure to migrate SAM on the same hostTo install the current version of Service Assurance Management Suite on the same host as the previous version, you need to satisfy or perform the following tasks.

1. Review the important release issues for Service Assurance Management Suite version 9.0, as described in the EMC Ionix Service Assurance Management Suite Release Notes.

2. Determine if the products that you are installing for the Service Assurance Management Suite are supported for your platform. “Operating system requirements” on page 24 provides more information.

3. Determine if there is enough disk space and memory on the host so both versions of the suite can co-exist. “Hardware requirements” on page 25 provides more information.

4. Remove all manually installed SAM services from the previous version. “Remove manually installed services” on page 88 provides more information. For UNIX, keep the service daemon (the sm_serviced component) running.

5. Mount the CD-ROM as described in Appendix B, “Procedures for CD/DVD-ROMs,”.

6. Install the 9.0 Service Assurance Management Suite on the same host as described in Chapter 3, “Installing the Service Assurance Management Suite,”.

• Specify a 9.0 directory name that is different from the previous version, so both versions of the suite can co-exist.

• Install products as services. Services installed for the 9.0 Service Assurance Management Suite overwrite the old services removed in step 4 . (If you need to run the old Managers, you need to manually install services for them with unique names and start them.)

7. Uninstall any TTPs if they exist in your installation.

8. Run the custom migration tool (sm_migrate) to copy customizations from the earlier SAM installation to the new SAM installation. “Overview of customization migration” on page 52 explains how the migration utility works. “Migrating customizations on the same host” on page 54 provides sample commands for migrating your old Service Assurance Management Suite file to the new installation.

9. Evaluate your security settings. “Migration of security configuration files” on page 58 provides more information.

10. Evaluate environment variables in the old runcmd_env.sh file. “Migration of security configuration files” on page 58 provides more information.

11. Evaluate your custom code. Review the “Custom file migration use cases” on page 57 to plan your post-migration steps. The sm_migrate utility migrated all custom code introduced by you under <BASEDIR>/smarts/local in the new installation. It also made a backup copy of the files under <BASEDIR>/smarts/.local.bkp.version. Review the output of sm_migrate utility and evaluate if you would like to keep your custom code in the new installation.

12. Check your rps files in <BASEDIR>/smarts/local/repos/icf. The rps files from previous installations will appear with the old version number appended to the file name. To use the rps file, remove the version number in the file name and run the server normally.

Overview of migration tasks 51

Perform a Migration

13. If you installed the products as services, start them for the first time. “Starting services on UNIX” on page 70 or “Starting services on Windows” on page 71provide more information.

14. Verify the current state of the products and Broker. “Verify the EMC Ionix product status” on page 79 provides more information.

15. Decommission the previous version of Service Assurance Management Suite. For instructions, refer to Chapter 6, “Uninstalling Service Assurance Management Suite,” for the previous software version.

Overview of customization migration

If TTPs (Temporary Test Patch) are installed on a previous installation of SAM, you must first uninstall the TTP and then run the utility. Else, TTP files will be treated as files modified by you and copied to the local directory in the new installation area. When migrating a customized file from an old installation to a new installation, if a file with the same name exists in the Local directory of the new installation, the Customization Migration Utility does not modify or overwrite it. Instead, the file is migrated into the Local directory of the new installation with the old version number appended to the file name.

The customization migration utility allows you to migrate customizations from an existing installation to a new installation of the product. The migration can be carried out on the same host or between two different hosts. The utility also supports cross-platform migration. Once the product is installed, you need to explicitly invoke the utility to migrate the customizations. The utility allows you to migrate all customizations made under the local directory of an old installation.

The customization migration utility is capable of three major functions, which include:

◆ Copying all non-binary files from the <BASEDIR>/smarts/local folder that have been modified or introduced by you in the previous version of the product into the <BASEDIR>/smarts/.local.bkp<version> directory of the new installation. For the files that have been modified from their original version, the utility also takes a copy of the files from the <BASEDIR>/smarts folder. The original and the local versions of the files from the old installation are needed for merging the changes you have made into the new installation.


Perform a Migration

Under smarts/.local.bkp.<version> directory you can find files with the following extensions:

• .custom - files from the <BASEDIR>/smarts/local folder introduced by you and are not part of the default installation

• .local - files from the <BASEDIR>/smarts/local folder that are part of the default installation and have been modified from their original version, using sm_edit.

• .base - the <BASEDIR>/smarts version of these files with .local extension

“Custom file migration use cases” on page 57 provide details.

◆ Copying all files you have added into the <BASEDIR>/smarts/local folder of the new installation. This allows for an easy and automatic migration of all custom code to the new installation, so that no manual step is required for moving the files from the backup directory.

All files, customized or newly introduced in the existing installation, must be present under the <BASEDIR>/smarts/local folder only.

◆ Merging .asl, .import, .conf, .xml, .sh and .cmd files modified by you into the new installation. This is an optional function and you may skip it. In order to merge the configurations from the existing into the new installation, the utility uses files from:

• Original base installation (previous installation with <file_name>.base extension)

• Local directory of the previous installation (files you have modified with a <file_name>.local extension)

• New installation (with <file_name> extension)

The clientConnect.conf, serverConnect.conf, brokerConnect.conf, runcmd_env.sh and .imk.dat files will not be merged. These files are backed up in the smarts/local.bkp.<version> directory of the new installation. A copy of the files with the version extension is also saved in the <BASEDIR/smarts/local folder of the new installation. If required, you must manually migrate these files from any of these directories. “Migration of security configuration files” on page 58 provides details.

Overview of customization migration 53

Perform a Migration

Customization migration scenariosThis section covers the following migration scenarios:

◆ “Migrating customizations on the same host” on page 54

◆ “Migrating customizations on a different host” on page 55

This version of the product does not support an in-place upgrade from an older version.

Migrating customizations on the same host

Use the following steps to migrate customizations on the same host:

1. Go to the <BASEDIR>/smarts/bin folder.

2. Type the following command to invoke the customization migration utility:

▼./sm-perl sm-migrate.pl --old=<previous_installation_upto_and_including_smarts directory> --new=<new_installation_upto_and_including_smarts directory> ▲

▼ ▲ indicates the command must be typed as one line.

For example:

c:\InCharge\SAM\smarts\bin>sm_perl sm_migrate.pl --old=c:\Incharge\sam\smarts --new=c:\Incharge\sam\smarts

The utility carries out the following steps:

• Verifies presence of existing installations in specified directories

• Determines the files that must be copied

• Copies the files over to <BASEDIR>/smarts/.local.bkp.<old_version> directory.

3. Copy any files introduced by you under the <BASEDIR>/smarts/local folder of the new installation.

4. Optional step: Press [y] or any other key to start the file merge utility (sm_merge utility), and then press [Enter]. The utility is invoked individually for each of the files that requires a three-way merge. “Three-way merge utility” on page 59 provides details. Once the utility completes merging the files, a message is displayed indicating successful completion of the process.

or

Press [n] to skip the invokation of the file merge utility.

5. Review the files (merged, auto-merged and .conflict) after the migration is over. Take appropriate actions as mentioned in the 'User Action' column in “Custom file migration use cases” on page 57.


Perform a Migration

Migrating customizations on a different host

Use the following steps to migrate customizations on remote hosts:

1. Prepare to archive the customizations made in the previous installation into a tar file by copying the following files:

• Perl packages: Copy migrateperlpkg.zip from the <BASEDIR>/smarts/perl folder in the new installation to the <BASEDIR>/smarts/local folder of the previous installation. For Linux and Solaris, use the unzip migrateperlpkg.zip command, and on Windows use the WinZip software to extract the contents in the zipped file to the <BASEDIR>/smarts/local folder.

• sm_migrate.pl utility: Copy this file from the <BASEDIR>/smarts/bin folder of new the installation to the <BASEDIR>/smarts/bin folder of your previous installation.

2. Go to the <BASEDIR>/smarts/bin folder of your previous installation, and run the following command to get an archive of the customizations:

▼./sm-perl sm-migrate.pl --old=<previous_installation_upto_and_including_smarts directory>--tar=<tar_file_that_contains_the_customizations> ▲


For example:

c:\InCharge\SAM\smarts\bin>sm_perl sm_migrate.pl--old=c:\InCharge\SAM\smarts --tar=c:\InCharge\SAM\smarts\backup.tar

The utility carries out the following functions:

• Verifies the presence of an existing installation in the directory specified

• Determines the files that must be copied

• Lists the files which are modified by you. The utility skips files which were introduced by patch, but not modified by you.

• Archives the backup directory into the specified tar file

“Extracting files needed for migration from old installation” on page 120 provides an example.

3. Transfer the tar file created in step 2 to the host with the 9.0 installation.

4. Go to the <BASEDIR>/smarts/bin folder of your new installation, and type the following command to migrate the customizations from the previous installation, to your new installation:

▼ ./sm-perl sm-migrate.pl--tar=<tar_file_that_contains_the_customizations> --new=<new_installation_upto_smarts> ▲


Customization migration scenarios 55

Perform a Migration

For example:

c:\InCharge\SAM\smarts\bin>sm_perl sm_migrate.pl--tar=c:\InCharge\SAM\smarts\backup.tar --new=c:\InCharge\SAM\smarts

The utility carries out the following steps:

• Verifies the presence of the new installation in the directory specified and existence of the specified tar file

• Reads the tar file and determines the files that must be copied

• Copies the files from the tar archive into a backup directory under <BASEDIR>/smarts/.local.bkp.<old_version>.

• Lists the files which are modified by you.

“Using archive extracted from the old installation on the new host” on page 122 provides an example.

5. Copy any files introduced by you under the <BASEDIR>/smarts/local folder of the new installation.

6. Optional step: Press [y] or any other key to start the file merge utility (sm_merge utility), and then press [Enter]. The utility is invoked individually for each of the files that may require a three-way merge. “Three-way merge utility” on page 59 provides details. Once the utility completes merging the files, a message is displayed indicating successful completion of the process.

or

Press [n] to skip the invokation of the file merge utility.

7. Review the files (merged, auto-merged and .conflict) after the migration is over. Take appropriate actions as mentioned in the 'User Action' column in “Custom file migration use cases” on page 57.


Perform a Migration

Custom file migration use cases The use cases for custom file migration and resulting backup and merge activities are described in Table 19 on page 57.

<file_name> indicates the version of the file present in the <BASEDIR> of the new installation.

Table 19 Custom file migration use cases (page 1 of 2)

Use case Backup action Merge Action

User action

Old installation New installation: <BASEDIR>/smarts/.local.bkp<version>

New_installation: <BASEDIR>/smarts/local

There is a local copy of a file and changes were introduced by you. The file is also used in the new installation.

Back up the base and the local copies of the file. The base copy is backed up with "base" extension and local copy will be backed up with "local" extension as shown:<file_name>.base<file_name>.local.

Run sm_merge for:• <file_name>.base• <file_name>.local• <file_name>

Merge Outcome:• Changes made by you are

merged into the new file and placed in local <New_installation>/smarts/local/<file_name>.conf

• If the changes made by you could not be merged without a conflict, a .conflict file is generated and placed <New_installation>/smarts/local/<file_name>.conflict

• Since the three-way merge utility works at a string level and not at a code level for files such as .asl, .xml, .cmd and .sh, the merge result of these files is appended with .automerge extension. Review the files, and if the changes are acceptable save the file without .automerge extension.

• Files with .import and .conf extension are not appended with an automerge extension on successful merge.

• For conflict files, review the conflict file, manually resolve the conflict and save the file without a .conflict extension.

“Conflict file output” on page 127 provides an example.

The local copy of the file was introduced by a patch and later modified by you. File exists in the new base, but does not exist in the old base.

Back up the local copy of the file. The local copy will be backed up with "local" extension, as <file_name>.local.

Sm_merge utility will compare <file_name>.local and <file_name>.

Merge Outcome:<file_name>.conflict

Review the conflict file, manually resolve the conflict and save the file without a .conflict extension.“Conflict file output” on page 127 provides an example.

There is a local copy of the file and changes were introduced by you, but the file is no longer used in the new release

Backup the base and the local copies of the file. The base copy is backed up with "base" extension and local copy will be backed up with ‘local’ extension as shown:<file_name>.base<file_name>.local

No merge The files remain in the backup directory. Determine if the customization is still relevant to the new installation.

Custom file migration use cases 57

Perform a Migration

Migration of security configuration filesThe security configuration files (clientConnect.conf, serverConnect.conf, brokerConnect.conf, runcmd_env.sh and .imk.dat) will not be merged. These files will be backed up and copied to the local directory in the new installation with their old version extension.

If in the old installation you did not change the site secret and the files remained encrypted with the default key, you can go ahead and reuse the same files by removing the version extension. If you have changed the site secret and encrypted the file with a non-default key, you need to recreate and encrypt them again. Use the sm_rebond command to encrypt the files.

The EMC Ionix ITOps System Administration Guide provides complete information about these security files and encryption.

Evaluate environment variables in the old runcmd_env.sh file. The sm_migrate utility migrated the old runcmd_env.sh file to <BASEDIR>/smarts/local in the new installation and appended the old installation name to the file, for example runcmd_env.sh.<oldinstallversion>. Copy any custom contents to the corresponding new runcmd_env.sh file.

The local copy of the file was introduced by a patch and changes were made by you. File does not exist in either new or old base.

Backup the local copy of the file. The local copy will be backed up with "local" extension, as <file_name>.local.

No merge Determine if the customization is still relevant to the new installation

There is a local copy of the file and changes were made by you. The file is also used in the new version and there is already a local copy of the file in the new local.

Backup the local copy of the file. The local copy will be backed up with "local" extension, as <file_name>.local.

No merge The sm_merge gives precedence to the files in new_local. No changes will be made to the files already under new_local. Key exceptions to the rule are covered in the “Migration of security configuration files” on page 58.

There is a local copy of the file and custom code was introduced by you. This code does not exist in either the old or the new base.

Back up the local copy of the file. The local copy will be backed up with "custom" extension, as <file_name>.custom.

No merge.Copy the files (without the .custom extension) from New Installation: <BASEDIR>/smarts/.local.bkp<version> to New installation: <BASEEDIR>/smarts/local

Determine whether these custom files are still needed in your new installation.

Table 19 Custom file migration use cases (page 2 of 2)

Use case Backup action Merge Action

User action

Old installation New installation: <BASEDIR>/smarts/.local.bkp<version>

New_installation: <BASEDIR>/smarts/local


Perform a Migration

Migration of dynamic model filesThe dynamic model files (files with .mdl and .ldm extension) are copied over to the corresponding location in the new installation. Remove the .ldm file from the local directory of the new installation. Recompile the .mdl file before it is used in the new installation. A new .ldm file will be generated once you recompile the .mdl file.

The EMC Ionix ITOps Dynamic Modeling Tutorial explains the concepts and methods of dynamic modeling.

Three-way merge utilityThe three-way merge utility helps incorporate configuration changes (made in the .conf, .import .asl, .xml, .sh and .cmd files) from a previous installation into a new installation of a product. The utility performs a three-way merge on each of the files that you have modified.

The utility uses <file_name>.base, <file_name>.local and <file_name>, and finds the largest sequence of lines which is common to all three files (this sequence need not necessarily be continuous lines). This is called the longest common subsequence (LCS). Then, for each of the three files, it finds groups of lines in between two consecutive lines in the LCS. These groups are referred to as ‘content blocks.’ The utility compares these content blocks and takes the merge decision as per Table 19 on page 57.

Three-way merge utility 59

Perform a Migration

Use cases for content block comparison

The scenarios for comparison of content blocks during the three-way merge process are described in Table 20 on page 60. In this table, X, Y and Z, represent the content blocks, one from each of the three files.

During this process, modifications done on each of the files in the previous installation are merged into the new installation. The utility identifies the files to be copied and copies them into a predefined new folder in the new installation with an appropriate suffix. Table 19 on page 57 provides details on the files which will be copied:

Table 20 Content block comparison use cases

Scenario Content block comparison Result

XYY• Content block in the <file_name>.base

looks like X• Content block in <file_name>.local looks

like Y• Content block in the <file_name> looks

like Y

The following content blocks are picked up:• Content block in <file_name>.base = X

AllowPrivateIPAsName FALSE

• Content block in <files_name>.local = YAllowPrivateIPAsName TRUE

• Content block in <file_name> = YAllowPrivateIPAsName TRUE

Result: Y Since the <file_name>.local version and the <file_name> version of the content blocks match, the Y version is picked.

XYX • Content block in the <file_name>.base

looks like X• Content block in the <file_name>.local

looks like Y• Content block in <file_name> looks like X

The following content blocks are picked up:• Content block in <file_name>.base = X

ERXIfExcludeSysPattern router*

• Content block in <files_name>.local = YERXIfExcludeSysPattern *

• Content block in <file_name> = XERXIfExcludeSysPattern router*

Result : Y This is the case where the file modified by you (Y) is preserved and is written to new_local.

X Y Z • Content block in the <file_name>.base

looks like X• Content block in the <file_name>.local

looks like Y• Content block in the <file_name> looks

like Z. This is the case where a .conflict file is created

The following blocks sections are picked up:• Content block in <file_name>.base = X

#Enable/Disable discovery of VLANs PropagateVRIfAlias FALSE

• Content block in <files_name>.local = Y#Enable/Disable discovery of Router PropagateVRIfAlias TRUE

• Content block in <file_name> = Z#Enable/Disable discovery of Multicast # New install changesPropagateVRIfAlias FALSE

Result: Conflict All three content blocks will be written into a .conflict file.


Perform a Migration

The utility performs the following functions:

◆ Automated analysis of the differences between any two files (for example, File A and File B), while also considering the parent file.

◆ Incorporates the changes done to the parent file in File A and File B, and automatically merges the two changes. This type of merge is used in revision control systems.

◆ It maintains a record of the conflicts encountered during the merge process in a .conflict file.

In case the utility is unable to merge the files due to some conflict, it creates a .conflict file for each file. The .conflict file provides details of the files which were not completely merged by the three-way utility. Each conflicting instance is recorded in the .conflict file as shown in the sample output “Conflict file output” on page 127. You can review the .conflict files to spot the conflicts, and manually resolve the differences.

Configuration migration process logs

Table 21 on page 61 lists the logs files that are created for the customization migration process. These files are available under the <BASEDIR>/smarts/setup/logs directory:

Known limitation

In certain cases, the three-way merge utility may flag lines with certain source code control tags (such as $Id) as conflicts. You may need to manually verify and merge the files just like any other conflict file.

Table 21 Log file and description

Log file name Description

Config_migration_copy.log Logs information about files which were modified during the previous installation, and those which were backed up in the new installation.

Config_migration_merge.log Logs information about the files on which three-way merge was performed. It also mentions whether the merge process was successful or if any conflicts arose during the process.

<file_name>.conf.MergeLog<file_name>.asl.MergeLog<file_name>.import.MergeLog<file_name>.xml.MergeLog<file_name>.sh.MergeLog<file_name>.cmd.MergeLog

For each type of file (.conf, .import .asl, xml, .sh and .cmd) merge logs are created. These logs record the lines which the three-way merge process copied from the previous installation, lines which were retained as-is, and those where conflicts were observed.

Three-way merge utility 61

Perform a Migration

Migrating previous NOTIF versions to version 9.0

Prerequisites

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

◆ The EMC Ionix Service Assurance Management Suite 9.0 (which

includes ITOps NOTIF 9.0) must be installed and running.

The “Notes on the SAM 7.x to 9.0 migration process” on page 62 provides information on how to migrate a SAM 7.x system to SAM 9.0.

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

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

Notes on the SAM 7.x to 9.0 migration process

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

These NOTIF objects in the repository are not yet in effect on the SAM 9.0 system.

Although the “Overview of customization migration” on page 52provides information on copying over customized files from the BASEDIR/smarts/local/ directories that changed between the 7.x and 9.0 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.)

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


Perform a Migration

In particular, existing NOTIF users should not copy over the following NOTIF files from the SAM 7.x system to the SAM 9.0 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 9.0

To migrate your previous NOTIF version to ITOps NOTIF 9.0:

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

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

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

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

Migrating previous NOTIF versions to version 9.0 63

Perform a Migration

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.

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 9.0 configuration displays in the ITOps NOTIF Editor.

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.


Perform a Migration

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:

SAM_CONSOLE_SUITE: winnt-x86-32/206110SAM_CONSOLE_SUITE: V9.0.0.0/32(111370), 15-Nov-2011 21:57:03 Copyright

1995-2011, EMC Corporation - Build 145DMT V9.0.1.1/32(111109), 05-Nov-2011 02:08:25 Copyright 1995-2011, EMC

Corporation - Build 15

SAM SERVER SUITE: winnt-x86-64/206110SAM_SUITE: V9.0.0.0/64(111370), 15-Nov-2011 21:57:04 Copyright

1995-2011, EMC Corporation - Build 145DMT V9.0.1.1/64(111109), 05-Nov-2011 02:08:07 Copyright 1995-2011, EMC

Corporation - Build 15

Verify the EMC Ionix version level 65

Perform a Migration


CHAPTER 5Verifying 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............................................................... 68◆ Start EMC Ionix products......................................................................................... 69◆ Start EMC Ionix programs ........................................................................................ 71◆ Start ITOps NOTIF .................................................................................................... 77◆ Verify the EMC Ionix product status ......................................................................... 79◆ Verifying FIPS 140 mode status ............................................................................... 80◆ Collect system information...................................................................................... 81◆ Where to go next ..................................................................................................... 85

Verifying the Installation 67

Verifying the Installation

Obtain and install a temporary license fileYour EMC account team will send you a temporary (evaluation) license file (for example, smarts.lic) through email. Copy the license file to the BASEDIR/smarts/local/conf directory on the system where you have installed the EMC Ionix software.

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

◆ 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 to specify the full path and file name of a single license 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.

If the temporary license file has a different name or extension, do not rename it. Instead, ensure that the name entered for the SM_LICENSE variable matches that of the license file.

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 emailing [email protected] with your request.

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

The trial license has an expiration date for each feature. The system generates an event in the IP Management Suite, 30 days before the expiration of the trial license. The event indicates the number of days remaining before the expiration of a license for a given feature.

For illustrative purposes, the following example is an excerpt of a <license_name>.lic file for EMC Ionix software version 9.0:

FEATURE DMC_CORR sm_lmgrd92 9.0 04-dec-2012 uncounted 123456789ABC \HOSTID=DEMO SN=DO315530889 START=4-nov-2008FEATURE AD_PEM sm_lmgrd92 9.0 04-dec-2012 uncounted 123456789ABC \HOSTID=DEMO SN=DO315530889 START=4-nov-2012FEATURE AP_ICSRV sm_lmgrd92 9.0 04-dec-2012 uncounted 123456789ABC \HOSTID=DEMO SN=DO315530889 START=4-nov-2012FEATURE DMC_DECS sm_lmgrd92 9.0 04-dec-2012 uncounted 123456789ABC \HOSTID=DEMO SN=DO315530889 START=4-nov-2012A temporary license file is not user-modifiable, and it consists of a list of applications or features; each line begins with the FEATURE keyword. Each FEATURE line includes the feature name, the vendor daemon name (sm_lmgrd92), the feature version, the expiration date, the number of concurrent licenses that is “uncounted” in this case, the authentication signature for the feature, the HOSTID=DEMO value that indicates that the feature is not bound to any particular host, the serial number (SN) to identify the FEATURE line, and a start date.



Events and attributes for license expiry alert

“Events and attributes for license expiry alert” section in Chapter 6, Configuration Settings, in the EMC Ionix IP Management Suite Reference Guide provides more information about the events and attributes for license expiry alert.

You can request an extension to your temporary license by emailing [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.

You will not be able to start new domain after a license expires. New devices can be added to the topology and discovery can be performed during the grace period, but new domains cannot be started using the same license. A fresh license is required to start new domain servers. You can extend the grace period on your license by a year. A special request asking for additional grace period on the AP_SYSTEM_VOLUME license feature has to be sent. Discovery and auto-discovery depends on this AP_SYSTEM_VOLUME license feature.

A new domain cannot be started even with this special license file. For example, if the licence is expiring on 9/15/2011, and five domains are pointing towards the license server, then even after expiry, the five domains will continue to work till 9/15/2012. However, if we start a new domain server after 9/15/2011 and it is pointing towards the same license file, it will not work. You will need to a new license to start a new domain server. Also, if your temporary license expires and if you are within the grace period, you will not be able to either restart existing domain managers if they are stopped, or add any new device in the existing topology.

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.

Start EMC Ionix products 69


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.

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.

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 95 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 ▲

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

Start EMC Ionix programs 71


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 ▲

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 ▲


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 ▲

▼▲ indicates the comsmand must be typed on one line.

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

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

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

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

For example:

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

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

Start ITOps NOTIF 77


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

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.

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.

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.

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.

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.

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

Verify the EMC Ionix product status 79


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

Common issues

Domain registers with the broker, but appears DEAD after a few minutes

The domain is in FIPS 140 mode but the broker is not.

Domain is not able to register with the broker

The Broker is in FIPS 140 mode but the domain is not.

Broker or Domain log entry

CI-N-EWHILE-While executing function "queue_work”CI-EFLOWID-For flow CI_FlowTCP_U [Flow in negotiations Accepted physical flow] PHYSICAL @0x0000000000a38db . *:v4:44445 KS N/A, KR N/A . Open fd=10, conn August 17, 2011 3:27:43 PM EDT, disc N/A, . 127.0.0.1:44445 -> 127.0.0.1:58347, tmo 0 00:00:15 N/S 1/0 CI-EWHILE-While executing function ""CI_FlowTLS_U::handshake”” CI-BSAFE-error:1407609C:SSLroutines:SSL23_GET_CLIENT_HELLO:http request: ; in file "s23_srvr.c" at line 746

The entry might also appear as: SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol.

This may be because the Domain (or Broker) is in FIPS 140 mode but the client is not. It may also be that the client is a non-Ionix client (for example a load balancer’s HTTP check). In that case, switch the load balancer to HTTPS check.

Client error

CI-E-EWHILE-While executing function ""CI_FlowTLS_U::handshake””CI-BSAFE-error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number: ; in file "s3_pkt.c" at line 553CI-TLSPE-TLS protocol error

This may be because the Domain or Broker is not FIPS 140 capable but the client is operating in FIPS 140 mode.

Log errors

[July 11, 2011 5:09:41 PM EDT +385ms] t@31 PollingQueue #8CI-E-EDECRYPT-Cannot decrypt.CI-EDECRYPT-Cannot decrypt.[July 11, 2011 5:09:41 PM EDT +386ms] t@31 PollingQueue #8IA-E-ERROR_EXECUTING_ACTION-Error executing action MA-PerlScript-sihou513a.CI-EDECRYPT-Cannot decrypt.

This may be because the Imk.dat version or the password does not match between domains. Ensure that the password and the version matches across all installs that interoperate.



Error on startup of domain or other tools

[August 8, 2011 8:29:07 PM EDT +466ms] t@3916876800 <Primary Thread>CI-F-EBLACKSTRING_CONTEXT-While creating the contextCRPT-CRYPTO_MD5_INIT_FAILED-Failed to initialize the context for MD5 algorithm

This may be because you are trying to use a v1 imk.dat file in FIPS 140 mode. Ensure that you use v2.1 for FIPS 140 compatibility.

Collect system informationThe sm_getinfo.pl script is used to collect data to help in troubleshooting problems. The script creates a backup copy (in .tar file format) of all essential files and customizations. The output file may be too large to easily transfer to EMC Customer Support using email. To resolve this problem, parameters are added that allow customers to selectively gather a subset of the data stored by the previous version of sm_getinfo utility. In addition, the sm_getinf.pl script captures system information in a generated log file named smgetinfo-versions.log<date>.

Use the sm_getinfo script to back up the current configuration, including all user-modified files.

1. Run the sm_getinfo.pl from the BASEDIR/smarts/bin directory:

For UNIX:

./sm_perl sm_getinfo.pl

For Windows:

sm_perl sm_getinfo.pl

2. The sm_getinfo.pl utility creates three files:

• A compressed archive file is created in the BASEDIR/smarts/local/logs directory. The name of the archive file includes the name of the server and the date.

• Version information is listed in a file named smgetinfo-versions.log.<date> in the BASEDIR/smarts/local/logs/smgetinfo_files directory.

• MANIFEST in BASEDIR/smarts/local/logs

3. The sm_getinfo.pl utility creates a manifest file that lists all programs and files it will archive.

• Type Yes to archive all files.

• Type No to not archive any files.

• Edit the manifest file to remove files you do not want archived. Type Yes to archive list of files.

Collect system information 81


Data collected by sm_getinfo.plThis topic provides the command line syntax, a description of the parameter options, an example of usage for each option, and supported platforms.

Command line syntax

sm_getinfo| --server <smarts-server-name> --pid <smarts-server-process-id> | --log [<num-of-latest-logs>]| --repos [--latest]| --core | --all| --version|--help|--smmonitor "<sm_monitor options>"

If no option is specified, the sm_getinfo.pl script will store the following information:

◆ The latest log file for each server and related audit/archive files in BASEDIR/smarts/local/logs. If a server name is specified, only the files corresponding to the server will be collected. To avoid generating too large tar file, any log file larger than 700MB will be excluded and its information will be logged in smgetinfo-versions.log<date>.

◆ The latest repository file in BASEDIR/smarts/local/repos. If a server name is specified, only the repository file for the server will be archived. Any repository file larger than 700MB will be excluded and its information will be logged in smgetinfo-versions.log<date>.

◆ The local files that are not in logs and repos directories and changed since last TTP and patch/HF .

◆ The new local files that are not in logs and repos directories and added since last TTP and patch/HF.

◆ All local files except the files in logs and repos directories if no patch/HF or TTP is installed.

◆ All files in BASEDIR/smarts/setup/info and BASEDIR/smarts/setup/logs.

◆ Core files (Unix/Linux) or dump files (Windows) generated by Smarts software, and the corresponding logs. On Linux/Unix, some lib files related to the cores are also collected.

◆ EMC Ionix ITOI (Smarts) patch or TTP version information. Additionally, it verifies MD5 checksum for the installed TTP files and the files listed in manifest.md5 under BASEDIR/smarts/setup/info.

◆ The data collected by sm_monitor. If a server name is specified, only the files corresponding to the server will be collected.

◆ The data generated by SHM.

◆ System environment information

The following EMC type style conventions are used in the Command Line Syntax:

<> Angle brackets for parameter values (variables) supplied by user.[ ] Square brackets for optional entries.| Vertical bar symbol for alternate selections.



Parameter Options

--server |<smarts-server-name> --pid <smarts-server-process-id>

| -s <smarts-server-name> -p <smarts-server-process-id>

Specifies the Smarts server name and pid against which the sm_getinfo will collect information. To dump core file for a running server on Linux/Unix, the pid option must be provided. Also, the server name is required to invoke sm_monitor tool.

--log [<num-of-latest-logs>] | -l [<num-of-latest-logs>]

For each Smarts server, collects and stores a specified number of latest logs or all generated log files in the BASEDIR/smarts/local/logs directory. Note that whenever collecting a log, the related .audit and .archive files should be collected as well. If a server name is specified, only the files corresponding to the server will be collected. To avoid generating too large tar file, any log file larger than 700MB will be excluded and its information will be logged in smgetinfo-versions.log<date>.

--repos [--latest] | -r [-t]

For each Smarts server, collects and stores the latest repository file or all repository files. If a server name is specified by -server option or in the smgetinfo_conf.txt file, only the file corresponding to the server will be collected. Any repository file larger than 700MB will be excluded and its information will be logged in smgetinfo-versions.log<date>.

--core | -c

Collects and stores the core files (Unix/Linux) or dump files (Windows) generated by Smarts software, and the corresponding logs.

Commands

--all | -a

All data and files in BASEDIR/smarts/local and BASEDIR/smarts/setup directories will be collected and stored. If --all option is specified, the other options will be ignored except --server and --pid.

--help | -h

Print usage information and exit.

--version | -v

Print version information and exit.

--smmonitor "<sm_monitor options>" | -m "<sm_monitor options>"

Specifies the options for running sm_monitor, which will override the default options -

"-m run-all -z".

Approximately two cycles are run to collect the required information. The collected information is output to the BASEDIR/local/logs/SM-Monitor-<domain_manager> directory.

Collect system information 83


Examples

To gather the five latest logs, type:

On Unix/Linux:

./sm_perl sm_getinfo.pl --logs 5

On Windows:

sm_perl sm_getinfo.pl --logs 5

To gather the latest repository data and core files, type:

On Unix/Linux:

./sm_perl sm_getinfo.pl --repos --latest --core

On Windows:

sm_perl sm_getinfo.pl --repos --latest --core

To gather the entire BASEDIR/smarts/local directory, type:

On Unix/Linux:

./sm_perl sm_getinfo.pl --all

On Windows:

sm_perl sm_getinfo.pl --all

To invoke sm_monitor, type:

On Unix/Linux:

./sm_perl sm_getinfo.pl -s <DM_NAME> -m ""-m correlation -z"

On Windows:

sm_perl sm_getinfo.pl -s <DM_NAME> -m ""-m mem"

Supported Platforms

The sm_getinfo utility is supported on multiple platforms including Windows, Solaris, and Linux.



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 85



CHAPTER 6Uninstalling Service Assurance Management Suite

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


◆ Before uninstallation............................................................................................... 88◆ Uninstalling Service Assurance Management Suite.................................................. 90

Uninstalling Service Assurance Management Suite 87

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 88

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

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

◆ “Uninstall the FLEXnet License Server” on page 89

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 Programs and Features 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 90 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.

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

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.

Before uninstallation 89


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 Programs and Features, 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 Programs and Features:

a. Click Start > Settings > Control Panel.

b. Open the list of programs.

c. Double-click Programs and Features.

d. From the programs window, select the appropriate service for your product suite.

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

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.

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

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 9.0 because the ITOps NOTIF processor is included as part of the SAM 9.0 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.

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

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

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................................................................................................................. 96◆ Service Assurance Management Suite services ....................................................... 96

Manually Installing Services 95

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 ▲

▼▲ 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--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 ▲

▲▼ 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▲

Service Assurance Management Suite services 97


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 ▲

▲▼ indicates that this csommand must be typed as one line.

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 the EMC Ionix Service Assurance Management Suite.

This chapter consists of the following sections:

◆ Mounting a CD/DVD-ROM on UNIX systems ........................................................... 104◆ Loading a CD/DVD-ROM on Windows .................................................................... 105

Procedures for CD/DVD-ROMs 103

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 22 on page 104.

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

Table 22 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.

Table 23 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.



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.

Loading a CD/DVD-ROM on Windows 105



APPENDIX CUnderstanding the sm_edit Utility

This appendix contains the following information:

◆ The sm_edit utility ................................................................................................ 108

Understanding the sm_edit Utility 107

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.


APPENDIX DLicense Migration Procedure

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

◆ Prerequisites......................................................................................................... 110◆ Migrate permanent license and set up FLEXnet license server................................ 111◆ Access to FLEXnet license server using SM_LICENSE.............................................. 114

License Migration Procedure 109

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, 8.0.0.x, or 8.1.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 9.0 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 9.0 software will work with FLEXlm 9.2 license files distributed for EMC Ionix version 7.2.0.x, 8.0.0.x, or 8.1.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.

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

In this discussion, a temporary license file is referred to as <license_name>.lic and a permanent license file is referred to as <host_id>.<license_name>.lic. 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>.<license_name>.lic to <license_name>.lic.



Migrate permanent license and set up FLEXnet license serverOn 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 9.0 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 <license_name>.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>.<license_name>.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>.<license_name>.lic in your BASEDIR directory on the system where the license server will run.

Do not save the permanent license file (<host_id>.<license_name>.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.

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

Migrate permanent license and set up FLEXnet license server 111


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>.<license_name>.lic ▲

On Windows systems, for example, the command is:

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

▼ ▲ 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.

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 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 9.0 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 114 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 9.0 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

Migrate permanent license and set up FLEXnet license server 113


Access to FLEXnet license server using SM_LICENSE

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.


APPENDIX ECustom migration sample outputs

This section provides sample outputs for the following:

◆ Getting help on the usage of customization migration utility ................................. 116◆ Running customization migration utility in same host............................................ 116◆ Extracting files needed for migration from old installation ..................................... 120◆ Using archive extracted from the old installation on the new host.......................... 122◆ Conflict file output ................................................................................................ 127

Custom migration sample outputs 115

Custom migration sample outputs

Getting help on the usage of customization migration utilityYou can invoke the utility with the --help option to get information on the usage of customization migration utility. Provided below is a sample.

<BASEDIR>\smarts\bin>sm_perl sm_migrate.pl --help==================================================================*The sm_migrate tool attempts to migrate all customizations that are

part of the local directory in your old installation to a backup directory in your new installation.

*Thereafter, it attempts a three way merge between the old base, the file in the old local directory and the file in the new installation for .asl, conf, .import, .xml, .cmd and .sh files.

==================================================================Usage : sm_perl sm_migrate.pl <options>Options:Required: Exactly 2 out of the following 3: --new=<dir> New Install location upto <.../smarts> Also -n <dir> --old=<dir> Old Install location upto <.../smarts> Also -o <dir> --tar=<file> Tar file containing the old files Also -t <file>Optional: --help Print Help Message Also -h==================================================================*The utility runs in three modes:

1. SAME_HOST: sm_perl sm_migrate.pl --old=<dir> --new=<dir>This is used to migrate customizations when new installation andold installation are on the same host.

2. DIFF_HOST_OLD: sm_perl sm_migrate.pl --old=<dir> --tar=<file>This is used to backup and create a tar of the customizations inthe old installation when the two installation are on differenthosts.

3. DIFF_HOST_NEW: sm_perl sm_migrate.pl --tar=<file> --new=<dir>This is used to migrate the customizations from a tar file in thenew installation when the two installation are on different hosts.

==================================================================

Running customization migration utility in same hostProvided below is a sample of the output for the running customization migration utility in the same host.

==================================================================For migrating customizations in the SAME_HOST mode

./sm_perl sm_migrate.pl --old=/opt/user/InCharge/SAM/smarts --new=/opt/user/InCharge/SAM/smarts

We will first identify your customizations and take a backup-----------------------------------------------------------------Directories Entered: Old Install Location: </opt/user/InCharge/SAM/smarts> New Install Location: </opt/user/InCharge/SAM/smarts>

Running in SAME_HOST mode



Old Version: <8.1.1.2> Backup of old configurations will be under </opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2> New Version: <9.0.0.0>-----------------------------------------------------------------We see that /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2 alreadyexists. We will attempt to create a backup before we proceed

Determining what files to copy...

Writing XML listing files to copy...

Parsing XML listing files to copy and copying files...

We have completed copying the old installation files..

These files have been modified by you in the previous installation (Version:8.1.1.2)and will be considered for merging================== Modified Conf Files============================

/opt/user/InCharge/SAM/smarts/local/conf/serverConnect.conf/opt/user/InCharge/SAM/smarts/local/conf/brokerConnect.conf/opt/user/InCharge/SAM/smarts/local/conf/clientConnect.conf/opt/user/InCharge/SAM/smarts/local/conf/ics/hello13.conf/opt/user/InCharge/SAM/smarts/local/conf/ics/hello2.conf/opt/user/InCharge/SAM/smarts/local/conf/ics/hello4.conf/opt/user/InCharge/SAM/smarts/local/conf/ics/hello5.conf================== Modified ASL Files=============================

/opt/user/InCharge/SAM/smarts/local/rules/maps/hello22.asl/opt/user/InCharge/SAM/smarts/local/rules/maps/hello25.asl/opt/user/InCharge/SAM/smarts/local/rules/maps/hello24.asl/opt/user/InCharge/SAM/smarts/local/rules/maps/hello20.asl

/opt/user/InCharge/SAM/smarts/local/rules/discovery/ic-fortigate-health.asl================== Modified Import Files==========================

/opt/user/InCharge/SAM/smarts/local/conf/discovery/DISCOVERY_FORTINET.import/opt/user/InCharge/SAM/smarts/local/conf/beacon/hello17.import/opt/user/InCharge/SAM/smarts/local/conf/beacon/hello19.import==================================================================We will attempt to merge customizations from your previousinstallation with the files in the new installation.

Reconciled version of the files containing your customizations will be placed directly into your new local directory for immediate use. If the changes in the files cannot be reconciled, we will create .conflict files under local. These files will require manual conflict esolution.

If you have already modified some of the files in your local, we will not modify those files.

You can find logs for all merge utility actions in.../smarts/setup/logs

Press 'n' to skip FileMergeUtiltyPress any other key to start FileMergeUtilty...[y]

Running file merge utility for files listed in XML...

file /opt/user/InCharge/SAM/smarts/local/conf/serverConnect.confalready exist in new installSkipping Merge Utility for/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/server

Running customization migration utility in same host 117


Connect.conf.local as you have already modified it in new install

file /opt/user/InCharge/SAM/smarts/local/conf/brokerConnect.confalready exist in new installSkipping Merge Utility for/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/brokerConnect.conf.local as you have already modified it in new install

file /opt/user/InCharge/SAM/smarts/local/conf/clientConnect.confalready exist in new installSkipping Merge Utility for/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/clientConnect.conf.local as you have already modified it in new install

***Skipping call to Merge utility for hello13.conf. This file does not exist in the new install

file /opt/user/InCharge/SAM/smarts/local/conf/ics/hello2.confalready exist in new installSkipping Merge Utility for/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/ics/hello2.conf.local as you have already modified it in new install

***Calling Merge utility for hello4.conf***==================================================================./sm_mergeBase: /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/ics/hello4.conf.baseModified: /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/ics/hello4.conf.localNewBase: /opt/user/InCharge/SAM/smarts/local/conf/ics/hello4.conf==================================================================Merge process for this file Completed but with conflict

Skipping Merge Utilityforopt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/ics/hello5.conf.local as It's Contents are completely matching with newinstall file /opt/user/InCharge/SAM/smarts/conf/ics/hello5.conf

***Calling Merge utility for hello22.asl***==================================================================./sm_mergeBase:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/maps/hello22.asl.baseModified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/maps/h

ello22.asl.localNewBase:/opt/user/InCharge/SAM/smarts/local/rules/maps/hello22.asl==================================================================Merge process for this file is completedSkipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/maps/hello25.asl.local as It's Contents are completely matching with newinstall file /opt/user/InCharge/SAM/smarts/rules/maps/hello25.asl

***Calling Merge utility for hello24.asl***==================================================================./sm_mergeBase: /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/maps/hello24.asl.baseModified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/maps/h

ello24.asl.localNewBase: /opt/user/InCharge/SAM/smarts/local/rules/maps/hello24.asl==================================================================Merge process for this file Completed but with conflict Skipping Merge

Utility for/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/maps/



hello20.asl.local as It's Contents are completely matching with newinstall file /opt/user/InCharge/SAM/smarts/rules/maps/hello20.asl

***Calling Merge utility for ic-fortigate-health.asl***==================================================================./sm_mergeBase:Modified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/rules/discovery/ic-fortigate-health.asl.localNewBase:/opt/user/InCharge/SAM/smarts/local/rules/discovery/ic-fortigate-health.asl==================================================================***Calling Merge utility for DISCOVERY_FORTINET.import***==================================================================

./sm_mergeBase:Modified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/discovery/DISCOVERY_FORTINET.import.localNewBase:/opt/user/InCharge/SAM/smarts/local/conf/discovery

/DISCOVERYFORTINET.import==================================================================file /opt/user/InCharge/SAM/smarts/local/conf/beacon/hello17.importalready exist in new installSkipping Merge Utility for/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/beacon/hello17.import.local as you have already modified it in new install

***Calling Merge utility for hello19.import***==================================================================./sm

_mergeBase:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/beacon/hello19.import.baseModified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.1.2/conf/beacon/hello19.import.localNewBase:/opt/user/InCharge/SAM/smarts/local/conf/beacon/hello19.import==================================================================Merge process for this file Completed but with conflict

We have completed the file three-way merge...

The following files could not be completely merged due to unresolved conflicts

======================= CONFLICT Files ======================/opt/user/InCharge/SAM/smarts/local/conf/ics/hello4.conf/opt/user/InCharge/SAM/smarts/local/rules/maps/hello24.asl/opt/user/InCharge/SAM/smarts/local/rules/discovery/ic-fortigate-health.asl/opt/user/InCharge/SAM/smarts/local/conf/discovery/DISCOVERY_FORTINET.import/opt/user/InCharge/SAM/smarts/local/conf/beacon/hello19.import================================================================

The following files were merged successfully

======================= Merged Files ======================/opt/user/InCharge/SAM/smarts/local/rules/maps/hello22.asl================================================================

The following files were added by you in previous installVersion:<8.1.1.2>. These files needs to be manually copied or merged innew Install from backup folder .../smarts/.local.bkp.8.1.1.2

======================= User Files ======================

Running customization migration utility in same host 119


/opt/user/InCharge/SAM/smarts/local/conf/Files_to_Copy.xml/opt/user/InCharge/SAM/smarts/local/conf/runcmd_env.sh/opt/user/InCharge/SAM/smarts/local/conf/imk.dat/opt/user/InCharge/SAM/smarts/local/conf/ics/hello7.conf/opt/user/InCharge/SAM/smarts/local/conf/ics/hello6.conf/opt/user/InCharge/SAM/smarts/local/conf/ics/hello9.conf/opt/user/InCharge/SAM/smarts/local/l10n/spool/README_spool.txt================================================================1. The backup of the customizations in the previous install is at

../smarts/.local.bkp.<8.1.1.2>.Please note that the files introduced by you are in backup directory with a '.custom' suffix and we haven't merged them. These may require manual copy or merge.

2. Please check the files listed under 'CONFLICT FILES' listed above. It is essential that you verify these files,edit them manually and remove the '.conflict' suffix before you put them to use.

3. The successfully merged .asl, .sh, .cmd and .xml files have an '.automerge' suffix. It is strongly recommended that you verify these files and remove the '.automerge' suffix before you put them to use.

4. Please note the we have not merged runcmd_env.sh , imk.dat , brokerConnect.conf, clientConnect.conf and serverConnect.conf. They need to be manually merged.

We have completed the Customization Migration. Will exit now...==================================================================

Extracting files needed for migration from old installationProvided below is a sample of the output post running the customization migration utility in DIFF_HOST_OLD mode:

DIFF_HOST_OLD mode: This involves invoking the customization migration utility by specifying the --old and --tar option to get a backup of the customizations made in the previous installation, into a tar file specified by you.

==================================================================./sm_perl sm_migrate.pl --old=/opt/user/InCharge/SAM/smarts--tar=/opt/user/InCharge/SAM/smarts/backup.tar

We will first identify your customizations and take a backup-----------------------------------------------------------------Directories Entered: Old Install Location: </opt/user/InCharge/SAM/smarts> Tar File Location :

</opt/user/InCharge/SAM/smarts/backup.tar>

Running in DIFF_HOST_OLD mode

Old Version: <8.1.2.0> Backup of old configurations will be under </opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0>-----------------------------------------------------------------We see that /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0already exists. We will attempt to create a backup before we proceedDetermining what files to copy...Writing XML listing files to copy...

Parsing XML listing files to copy and copying files...

We have completed copying the old installation files..



We will now attempt to tar the old files backup.

Found OS: Unix/Linux/SolWill convert all files to dos format before creating tar../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/SAX/Intro.pod../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/PatAct/ActionTempl.pm../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/PatAct/MatchName.pm../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/Parser/PerlSAX.pm../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/Handler/Sample.pm../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/Handler/Subs.pm../.local.bkp.8.1.2.0/perl/5.8.8/lib/XML/Handler/CanonXMLWriter.pm../.local.bkp.8.1.2.0/logs/sm_serviced_en_US_UTF-8.log../.local.bkp.8.1.2.0/examples/dynamic-model/example2/model/hello15.mdl.local../.local.bkp.8.1.2.0/l10n/spool/README_spool.txt.custom../.local.bkp.8.1.2.0/conf/runcmd_env.sh.custom../.local.bkp.8.1.2.0/conf/imk.dat.custom../.local.bkp.8.1.2.0/conf/Files_to_Copy.xml.custom../.local.bkp.8.1.2.0/conf/ics/hello7.conf.custom../.local.bkp.8.1.2.0/conf/ics/hello6.conf.custom../.local.bkp.8.1.2.0/conf/ics/hello9.conf.custom../.local.bkp.8.1.2.0/conf/clientConnect.conf.local../.local.bkp.8.1.2.0/conf/serverConnect.conf.local../.local.bkp.8.1.2.0/conf/brokerConnect.conf.local../.local.bkp.8.1.2.0/conf/ics/hello2.conf.local../.local.bkp.8.1.2.0/conf/ics/hello4.conf.local../.local.bkp.8.1.2.0/conf/ics/hello13.conf.local../.local.bkp.8.1.2.0/conf/ics/hello5.conf.local../.local.bkp.8.1.2.0/rules/maps/hello22.asl.local../.local.bkp.8.1.2.0/rules/maps/hello25.asl.local../.local.bkp.8.1.2.0/rules/maps/hello24.asl.local../.local.bkp.8.1.2.0/rules/maps/hello20.asl.local../.local.bkp.8.1.2.0/conf/beacon/hello17.import.local../.local.bkp.8.1.2.0/conf/beacon/hello19.import.local../.local.bkp.8.1.2.0/conf/clientConnect.conf.base../.local.bkp.8.1.2.0/conf/serverConnect.conf.base../.local.bkp.8.1.2.0/conf/brokerConnect.conf.base../.local.bkp.8.1.2.0/conf/ics/hello2.conf.base../.local.bkp.8.1.2.0/conf/ics/hello4.conf.base../.local.bkp.8.1.2.0/conf/ics/hello13.conf.base../.local.bkp.8.1.2.0/conf/ics/hello5.conf.base../.local.bkp.8.1.2.0/rules/maps/hello22.asl.base../.local.bkp.8.1.2.0/rules/maps/hello25.asl.base../.local.bkp.8.1.2.0/rules/maps/hello24.asl.base../.local.bkp.8.1.2.0/rules/maps/hello20.asl.base../.local.bkp.8.1.2.0/conf/beacon/hello17.import.base../.local.bkp.8.1.2.0/conf/beacon/hello19.import.base../setup/info/OldsysVerInfo

We have completed creation of the tar of</opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0> in</opt/user/InCharge/SAM/smarts/backup.tar>.

Please Note: You need to copy this tar file into the 'smarts' directory of the new installation and execute the sm_migrate.pl from there specifying this tar in the --tar option

==================================================================

Extracting files needed for migration from old installation 121


Using archive extracted from the old installation on the new hostProvided below is a sample of the output post running the customization migration utility in DIFF_HOST_NEW mode:

DIFF_HOST_NEW mode: This involves invoking the customization migration utility by specifying the --new and --tar option to run the migration on a new host for migrating the customizations from the previous installation from the tar file obtained by using the DIFF_HOST_OLD mode.

==================================================================./sm_perl sm_migrate.pl --tar=/opt/user/InCharge/SAM/smarts/backup.tar --new=/opt/user/InCharge/SAM/smarts

We will first identify your customizations and take a backup

-----------------------------------------------------------------

Directories Entered:

Tar File Location : </opt/user/InCharge/SAM/smarts/backup.tar>

New Install Location: </opt/user/InCharge/SAM/smarts>

Running in DIFF_HOST_NEW mode

New Version: <9.0.0.0>

-----------------------------------------------------------------

Read /opt/user/InCharge/SAM/smarts/backup.tar successfully

Extracted /opt/user/InCharge/SAM/smarts/backup.tar successfully

-----------------------------------------------------------------

Old Version: <8.1.2.0>

Backup of old configurations will be under

</opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0>

-----------------------------------------------------------------

Determining what conf files have been copied...

We will now try to convert all files into UNIX format...

Writing XML listing of extracted .conf files...

We have completed copying the old installation files.

We will now invoke the merge Utility.

These files have been modified by you in the previous installation (Version:8.1.2.0) and will be considered for merging



================== Modified Conf Files============================

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/

serverConnect.conf


clientConnect.conf


brokerConnect.conf

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/ics/

hello13.conf


hello2.conf


hello5.conf


hello4.conf

================== Modified ASL Files=============================

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/

hello24.asl


hello25.asl


hello20.asl


hello22.asl

================== Modified Import Files==========================

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/beacon/

hello17.import

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/beacon/

hello19.import

==================================================================We will attempt to merge customizations from your previous installation with the files in the new installation.

Reconciled version of the files containing your customizations will be placed directly into your new local directory for immediate use.

Using archive extracted from the old installation on the new host 123


If the changes in the files cannot be reconciled, we will create .conflict files under local. These files will require manual conflict resolution.

If you have already modified some of the files in your local, we will not modify those files.

You can find logs for all merge utility actions in .../smarts/setup/logs

Press 'n' to skip FileMergeUtilty

Press any other key to start FileMergeUtilty...[y]

Running file merge utility for files listed in XML...

file /opt/user/InCharge/SAM/smarts/local/conf/serverConnect.conf already exist in new install

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/

serverConnect.conf.local as you have already modified it in new install file /opt/user/InCharge/SAM/smarts/local/conf/clientConnect.conf already exist in new install

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/clientConnect.conf.local as you have already modified it in new install

file /opt/user/InCharge/SAM/smarts/local/conf/brokerConnect.conf already exist in new install

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/brokerConnect.conf.local as you have already modified it in new install

***Skipping call to Merge utility for hello13.conf. This file does not exist in the new install

file /opt/user/InCharge/SAM/smarts/local/conf/ics/hello2.conf already exist in new install

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/ics/

hello2.conf.local as you have already modified it in new install

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/ics/

hello5.conf.local as It's Contents are completely matching with new install file /opt/user/InCharge/SAM/smarts/conf/ics/hello5.conf

***Calling Merge utility for hello4.conf***

==================================================================./sm_merge

Base: /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/ics/

hello4.conf.base

Modified: /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/ics/

hello4.conf.local

NewBase: /opt/user/InCharge/SAM/smarts/local/conf/ics/hello4.conf

================================================================= Merge process for this file Completed but with conflict



***Calling Merge utility for hello24.asl***

==================================================================./sm_merge

Base: /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/

hello24.asl.base

Modified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/hello24.asl.local

NewBase:/opt/user/InCharge/SAM/smarts/local/rules/maps/hello24.asl

==================================================================Merge process for this file Completed but with conflict

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/

hello25.asl.local as It's Contents are completely matching with new install file /opt/user/InCharge/SAM/smarts/rules/maps/hello25.asl

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/hello20.asl.local as It's Contents are completely matching with new install file /opt/user/InCharge/SAM/smarts/rules/maps/hello20.asl

***Calling Merge utility for hello22.asl***

==================================================================./sm_merge

Base:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/hello22.asl.base

Modified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/rules/maps/hello22.asl.local

NewBase:/opt/user/InCharge/SAM/smarts/local/rules/maps/hello22.asl

==================================================================Merge process for this file is completed

file /opt/user/InCharge/SAM/smarts/local/conf/beacon/hello17.import already exist in new install

Skipping Merge Utility for /opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/beacon/

hello17.import.local as you have already modified it in new install

***Calling Merge utility for hello19.import***

==================================================================./sm_merge

Base:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/beacon/hello19.import.base

Modified:/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/beacon/hello19.import.local

Using archive extracted from the old installation on the new host 125


NewBase:/opt/user/InCharge/SAM/smarts/local/conf/beacon/hello19.import

==================================================================Merge process for this file Completed but with conflict

We have completed the file three-way merge...

The following files could not be completely merged due to unresolved conflicts

======================= CONFLICT Files ======================

/opt/user/InCharge/SAM/smarts/local/conf/ics/hello4.conf

/opt/user/InCharge/SAM/smarts/local/rules/maps/hello24.asl

/opt/user/InCharge/SAM/smarts/local/conf/beacon/hello19.import

================================================================

The following files were merged successfully

======================= Merged Files ======================

/opt/user/InCharge/SAM/smarts/local/rules/maps/hello22.asl

================================================================

The following files were added by you in previous install Version:<8.1.2.0>

These files needs to be manually copied or merged in new Install from backup folder .../smarts/.local.bkp.8.1.2.0

======================= User Files ======================


runcmd_env.sh.custom

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/imk.dat.custom

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/conf/Files_to_Copy.xml.custom


hello6.conf.custom


hello9.conf.custom


hello7.conf.custom

/opt/user/InCharge/SAM/smarts/.local.bkp.8.1.2.0/l10n/spool/

README_spool.txt.custom

==================================================================



1. The backup of the customizations in the previous install is at ../smarts/.local.bkp.<8.1.2.0>

Please note that the files introduced by you are in backup directory with a '.custom' suffix and we haven't merged them. These may require manual copy or merge.

2. Please check the files listed under 'CONFLICT FILES' listed above. It is essential that you verify these files,edit them manually and remove the '.conflict' suffix before you put them to use.

3. The successfully merged .asl, .sh, .cmd and .xml files have an '.automerge' suffix. It is strongly recommended that you verify these files and remove the '.automerge' suffix before you put them to use.

4. Please note the we have not merged runcmd_env.sh , imk.dat , brokerConnect.conf, clientConnect.conf and serverConnect.conf. They need to be manually merged.

5. You can find Customization Migration logs under directory ../smarts/setup/logs .

We have completed the Customization Migration. Will exit now...

========================================================

Conflict file outputProvided below is a sample of the conflict file output, displaying conflicts encountered during the file merge process using three-way merge utility.

==================================================================

<--------------------------START CONFLICT------------------------?

?-------------Previous Install Base Version: 4.0.0.0--------------?

# skipLDPDiscovery = TRUE

?--------------Previous Install Local Version : 4.0.0.0-----------?

skipLDPDiscovery = FALSE

?----------------New Install Base Version : 9.0.0.0---------------?

# skipLDPDiscovery = FALSE

?------------------END CONFLICT---------------------------------?\

==================================================================

Conflict file output 127



APPENDIX FCustomization migration utility file examples

This section provides sample outputs for the following:

◆ Previous installation base file contents ................................................................. 130◆ Previous installation base local file contents ......................................................... 130◆ New installation base file contents........................................................................ 130

Customization migration utility file examples 129

Customization migration utility file examples

Previous installation base file contents============Previous Install Base File Content ============IgnoreIPForPersistentMgmtState FALSEAllowPrivateIPAsName FALSEDiscoverCiscoTrunkPortVLANs TRUE #Enable/Disable discovery of VLANs

PropagateVRIfAlias FALSEifVirtualTypePattern-.1.3.6.1.4.1.9.1.507 135|136ERXIfExcludeSysPattern router*

===============File End==================================

Previous installation base local file contents=========Previous Install Base Local File Content ==========IgnoreIPForPersistentMgmtState FALSEAllowPrivateIPAsName TRUE # you modified it DiscoverCiscoTrunkPortVLANs TRUE #Enable/Disable discovery of Router #you modified it PropagateVRIfAlias TRUE # you modified it ifVirtualTypePattern-.1.3.6.1.4.1.9.1.507 135|136ERXIfExcludeSysPattern * # you modied it

===============File End====================================

New installation base file contents================New Install Base File ======================IgnoreIPForPersistentMgmtState FALSEAllowPrivateIPAsName TRUE # New install changesDiscoverCiscoTrunkPortVLANs TRUE #Enable/Disable discovery of Multicast # New install changes

PropagateVRIfAlias FALSEifVirtualTypePattern-.1.3.6.1.4.1.9.1.507 135|136ERXIfExcludeSysPattern router*===================File End==========================

In the three files above, the largest sequence of lines common to all are:

IgnoreIPForPersistentMgmtState FALSEDiscoverCiscoTrunkPortVLANs TRUEifVirtualTypePattern-.1.3.6.1.4.1.9.1.507 135|136

The following content blocks are picked up for comparison for the previous installation base file:

Content block 1 :

AllowPrivateIPAsName FALSE

It is the line which is found in between the common lines listed below. These lines are present in all the three files:

IgnoreIPForPersistentMgmtState FALSE DiscoverCiscoTrunkPortVLANs TRUE



Content block 2:

#Enable/Disable discovery of VLANs PropagateVRIfAlias FALSE

It is the line which is found in between the common lines listed below. These lines are present in all the three files:

IgnoreIPForPersistentMgmtState FALSE ifVirtualTypePattern-.1.3.6.1.4.1.9.1.507 135|136

Content block 3:

ERXIfExcludeSysPattern router*

It is the set of lines from, ifVirtualTypePattern-.1.3.6.1.4.1.9.1.507 135|136 till the end of the file.

Similarly, as illustrated above, the three-way merge utility will collect all the content blocks from the base local of the previous installation and the new installation base files. It then compares the corresponding content blocks of all the three files; that is, starting off with content block 1 of the previous installation base, base local and new installation base file.

It proceeds to compare content block 2 and content block 3 and so on. It takes merge decisions as per Table 20 on page 60. “Use cases for content block comparison” on page 60provides details.

New installation base file contents 131



Documents

EMC Ionix Service Assurance Management Suite · 2020-06-19 · EMC® Ionix™ Service Assurance Management Suite Version 9.0 Installation and Migration Guide P/N 300-012-983 REV A02