EMC Smarts Adapter for Alcatel-Lucent 5620 SAM …...Overview 5 CHAPTER 1 Overview This chapter...

EMC® Smarts®

Adapter for Alcatel-Lucent 5620 SAM EMSVersion 3.4

Installation GuideP/N 302-004-788REV 02

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide2

Copyright © 2006 - 2019 Dell Inc. or its subsidiaries. All rights reserved. Published in the USA.

Published July 2019

Dell 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. Dell 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 Dell software described in this publication requires an applicable software license.

Dell, EMC, and other trademarks are registered trademarks or trademarks of Dell Inc. or its subsidiaries in the United States and other countries. 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 EMC Online Support (https://support.emc.com).

http://support.emc.com

CONTENTS

Chapter 1 Overview

Adapter for Alcatel-Lucent 5620 SAM EMS ......................................................... 6 Product and release compatibility .......................................................................... 6 Installation tasks overview ..................................................................................... 6 Migration ................................................................................................................ 7 Uninstallation tasks overview................................................................................. 8 Product description................................................................................................. 8 New features and changes ...................................................................................... 8

New features in Foundation 9.6 ....................................................................... 9New features in ASAM Patches..................................................................... 11

Chapter 2 Requirements

Operating system requirements ............................................................................ 14Access requirement ........................................................................................ 15

Software requirements.......................................................................................... 16Third-party software....................................................................................... 16EMC Smarts software .................................................................................... 16

Licensing .............................................................................................................. 16

Chapter 3 Installing the Adapter

Before installation ................................................................................................ 20Determine the location of the EMC Smarts Broker ....................................... 20

Install the Adapter for Alcatel-Lucent 5620 SAM EMS ...................................... 20Install using Wizard mode.............................................................................. 21Install using CLI mode................................................................................... 23Install using unattended mode........................................................................ 24Where to go next ............................................................................................ 25If your system is not patched completely....................................................... 25

Chapter 4 Performing a Migration

Migrating to version 3.4 ....................................................................................... 28Migrating emsConfig.import parameters ....................................................... 28Migrating ASA-Filter.conf parameters .......................................................... 29Migrating ASA-Alarm.conf parameters......................................................... 30Migrating AggregateAlarms.conf parameters................................................ 31Migrating DevicesNotInEffect.conf parameters ............................................ 31

Migration for multiple-Adapter deployment ........................................................ 31Migrating to the new version ......................................................................... 31Reverting to the previous version................................................................... 33

Chapter 5 Verifying the Installation

Obtain and install a temporary license file ........................................................... 36 Start EMC Smarts services................................................................................... 36

Starting services on UNIX ............................................................................. 36Starting services on Windows ........................................................................ 37

Start EMC Smarts programs................................................................................. 37

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide 3

Contents

Starting programs on UNIX ........................................................................... 37Starting programs on Windows...................................................................... 38

Service and program startup options .................................................................... 38 Verify the EMC Smarts product status ................................................................. 38

Chapter 6 Uninstalling the Adapter

Before uninstallation ............................................................................................ 40Extracting JVM file ........................................................................................ 40Remove manually installed services .............................................................. 40Determine order for removing products (UNIX only) ................................... 41Uninstall when the same product software is installed twice (Windows only) .. 41Detect and stop EMC Smarts programs ......................................................... 41Uninstall the FLEXnet License Server........................................................... 44

Uninstalling the Adapter for Alcatel-Lucent 5620 SAM EMS ............................ 45Uninstall using Wizard mode......................................................................... 45Uninstall using CLI mode .............................................................................. 46Uninstall using unattended mode ................................................................... 47

Appendix A Manually Installing Services

Overview .............................................................................................................. 50 Adapter for Alcatel-Lucent 5620 SAM EMS services ......................................... 50

EMC Smarts Broker ....................................................................................... 50Adapter for Alcatel-Lucent 5620 SAM EMS ................................................ 51

Appendix B Procedures for CD-ROMs

Mounting a CD-ROM on UNIX systems............................................................. 54 Loading a CD-ROM on Windows........................................................................ 54

Appendix C Getting help

Where to get help.................................................................................................. 56

4 EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide

CHAPTER 1Overview

This chapter describes the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS product, compatibility with other EMC Smarts products, and installation tasks.

This chapter consists of the following topics:

• Adapter for Alcatel-Lucent 5620 SAM EMS ...................................................................... 6• Product and release compatibility........................................................................................ 6• Installation tasks overview .................................................................................................. 6• Migration ............................................................................................................................. 7• Uninstallation tasks overview.............................................................................................. 8• Product description .............................................................................................................. 8• New features and changes ................................................................................................... 8

Overview 5

Overview

Adapter for Alcatel-Lucent 5620 SAM EMS The product is available for download from the EMC support website, https://support.emc.com.

Product and release compatibilityThe EMC® Smarts® Adapter for Alcatel-Lucent 5620 SAM EMS (ASAM) requires the installation of the Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server. Supported versions of the Nokia NFM-P are from 17.9 to 18.6.

Note: The Adapter must be installed on a different host from the Alcatel-Lucent 5620 SAM EMS server, and may be on different hosts from the EMC Smarts Domain Managers.

The EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS version 3.4 is compatible with the versions of these products in Table 1 on page 6.

Table 1 Interoperability chart

EMC Smarts product Versions

IMPORTANT

Ensure that the latest patch for the product listed in Table 1 on page 6 is applied. The EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes provides more detailed information.

Installation tasks overviewTable 2 on page 6 summarizes the installation tasks for the Adapter:

IP Manager (IP) - required 9.4.2.x, 9.5.x.x, 9.6.x.x

MPLS Manager (MPLS) - optional 9.4.2.x, 9.5.x.x, 9.6.x.x

Multicast Manager (MCAST) - optional 8.1.5

Network Protocol Manager (NPM) - optional 9.4.2.x, 9.5.x.x,9.6.x.x

Service Assurance Manager (SAM) - required 9.4.2.x, 9.5.x.x, 9.6.x.x (with latest patch)

Table 2 Adapter for Alcatel-Lucent 5620 SAM EMS installation requirements and tasks (page 1 of 2)

Before you install:

Review the important release issues for the Adapter for Alcatel-Lucent 5620 SAM EMS.

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes

Determine if the products are supported on your platform.

“Operating system requirements” on page 14


Overview

Ensure that the latest patch for the Adapter for Alcatel-Lucent 5620 SAM EMS is applied. The patch software and patch documentation that provides instructions to upgrade deployments are available from the EMC support website, https://support.emc.com.

MigrationThere is no automated migration path for EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS. “Performing a Migration” on page 27 provides information for performing manual migration of configuration files.

Installation method:

Install the Adapter for Alcatel-Lucent 5620 SAM EMS.

Choose one of the following installation methods:• “Install using Wizard mode” on page 21• UNIX only, “Install using CLI mode” on

page 23• “Install using unattended mode” on page 24

After you install:

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

BASEDIR/smarts/local/conf directory.• Permanent license—Use the procedures described

in the EMC Smarts System Administration Guide.

“Obtain and install a temporary license file” on page 36.

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

• “Starting services on UNIX” on page 36• “Starting services on Windows” on page 37

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

Table 2 Adapter for Alcatel-Lucent 5620 SAM EMS installation requirements and tasks (page 2 of 2)

Before you install:

Migration 7

Overview

Uninstallation tasks overviewTo uninstall the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS, perform the tasks listed in Table 3 on page 8

Table 3 Adapter for Alcatel-Lucent 5620 SAM EMS uninstallation requirements and tasks

Before you uninstall:

• “Remove manually installed services” on page 40

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

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

• “Detect and stop EMC Smarts programs” on page 41

• “Uninstall the FLEXnet License Server” on page 44

Uninstallation:

• “Uninstall using Wizard mode” on page 45• “Uninstall using CLI mode” on page 46• “Uninstall using unattended mode” on page 47

:

Product descriptionThe EMC® Smarts® Adapter for Alcatel-Lucent 5620 SAM EMS provides a link from the Alcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following EMC Smarts Domain Managers:

• IP Availability Manager

• MPLS Topology Manager

• Network Protocol Managers (Manager for BGP, Manager for OSPF, Manager for IS-IS)

• Multicast Manager

The Adapter sends topology queries by XML streams to the EMS, where they are processed. Near real-time events are passed from the EMS by Java Message Service (JMS), also in XML format, to the Adapter. Based on the events, the Adapter creates notifications in the Adapter Platform. The Adapter Platform creates notifications for display in the Service Assurance Global Console.

New features and changesThe Adapter for Alcatel-Lucent 5620 SAM EMS provides the following new features:

Review uninstall prerequisites:

Uninstall the Adapter for Alcatel-Lucent 5620 SAM EMS:


Overview

• Smarts Adapter for Alcatel-Lucent 5620 SAM version 3.4.0.0 includes support for Nokia 7210 Service Access Switch in satellite mode. This is qualified on NFM-P version 17.9.

Note: ASAM 3.4 Adapter is also qualified against Nokia NFM-P 18.6 with SR 7 and SR 14 devices.

New features in Foundation 9.6

This release of the Adapter for Alcatel-Lucent 5620 SAM EMS is based upon foundation 9.6. Documentation explaining Foundation 9.6 features is listed in the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes. Here are highlights of changes related to Foundation 9.6:

Internationalization

Any information that the Foundation 9.6 manages is now manipulated, stored and retrieved in a language-aware manner. The internationalization functionality of the foundation covers broad areas of logging, locale awareness, legacy character encoding and Unicode encoding, string externalization, and utilities and programming interfaces for application enablement of these same features.

In this release, the foundation has been internationalized and is functionally localized to American English. Localization to the other target languages, as dictated by the EMC globalization policy and customer requirements, will be undertaken at a future date.

The name of the log files in the IP Manager reflects these changes in foundation software. Log files have the following syntax: <name>_<locale>_<encoding>.log. For example, MYDOMAINMANAGER_en_US_UTF-8.log. The System Administration Guide provides complete information about locale and log files.

ICIM Ref 1.10

Foundation 9.6 has been updated to support ICIM Reference 1.10.

New SmRestartableDomainManager class

You can now use SmRestartableDomainManager in place of SmRemoteDomainManager with minimal changes to accommodate it. The benefit of using the SmRestartableDomainManager is that your application does not need to write code to check the status of the remote server and to try to reconnect if the server shuts down and is restarted.

The SmRestartableDomainManager has the ability to reconnect with the remote domain manager when the remote server comes back up.

New MODEL operations to retrieve description text

There are a number of API operations that have been re-implemented as MODEL operations. These MODEL operations retrieve description texts. The texts that are retrieved will be in the locale that was set either by the initial connection or by the locale set by the most recent call to the setRemoteLocale API operation. For earlier versions of foundation software, whose protocol is incapable of specifying locales, the locale is set to en_US.

If these operations are run outside of the context of a remote session, then the effective locale is CI_Locale::DEFAULT.

The operations are:

New features and changes 9

Overview

• getPropDescription — retrieve the description of the MODEL property

• getEventDescription — retrieve the description of the MODEL event

• getOpDescription — retrieve the description of the MODEL event

• getClassDescription — retrieve the description of the MODEL class

These MODEL operations are described in the EMC Smarts MODEL Reference Guide .

New command line option in sm_adapter

A new option, alarmInterval, has been added to sm_adapter. You can use the alarmInterval option with a subscriber front end ( --subscribe or --subscribeProp). Setting alarmInterval causes the front end to generate a message on its own if no new updates have been received in the last <alarmInterval> seconds. You can use this feature to have your script wake up after periods of inactivity. However, in order to use alarmInterval, your script must recognize a message type of Timer_Alarm.

--alarmInterval=secs

New ICF Core classes

A new ICF-Core.mdl has been added. The ICF Core model defines base classes for managed element, configuration, setting, instrumentation, product, software feature, and hierarchical group. These classes inherit CMP core classes, and are used by ICIM core and ICF framework.

The ICF Core classes are described further in the EMC Smarts ICIM Reference.

Changes in Application Program Interfaces (APIs)

Code based on Java, Perl, or C API needs to be modified to point to IP Manager and retested to check for other changes. The Perl Reference Guide provides more information.

Changes in sm_server --version

The operating system (OS) name that the product is running on and OS version identifier have been added to the output of the sm_server --version command.

icim-core split

The icim-core subsystem now depends on a new subsystem, called cmp-core. It contains four new classes which are now the super classes for ICIM-Core:

• CORE_ManagedObject

• CORE_Collection

• CORE_MetaObject

• CORE_AbstractIndication

In addition, the relationship "MemberOf" in CORE_MetaObject has been renamed to "MetaMemberOf".

relationshipset MetaMemberOf, CORE_Collection, MetaConsistsOf

The reverse relationship in CORE_Collection has been modified accordingly.

relationshipset MetaConsistsOf, CORE_MetaObject, MetaMemberOf


Overview

The new classes in the cmp-core subsystem are described in the ICIM Reference.

New features in ASAM Patches

For the latest enhancements provided by 3.3.0.x patches, consult the patch documentation on the EMC support website, https://support.emc.com.

New features and changes 11

Overview


CHAPTER 2Requirements

This chapter describes the operating system requirements and hardware requirements for the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS.


• Operating system requirements ......................................................................................... 14• Software requirements ....................................................................................................... 16• Licensing............................................................................................................................ 16

Requirements 13

Requirements

Operating system requirementsAdapter for Alcatel-Lucent 5620 SAM EMS Version 3.4 requires the 64-bit version of the operating system for all platforms. Ensure that hardware hosting the Adapter for Alcatel-Lucent 5620 SAM EMS runs a 64-bit operating system and is patched to the latest patch levels recommended by the manufacturer.

Table 4 Supported operating system for the Adapter for Alcatel-Lucent 5620 SAM EMS

Operating system Supported version

• AS 6• AS 7.2, 7.3

(64-bit operating system version only; for AMD64/EM64T chipsets)

• 2012, x64• 2016, x64

Recommended patch levels

Table 5 on page 15 summarizes the operating system patches required for the Adapter for Alcatel-Lucent 5620 SAM EMS:

Red Hat Enterprise Linux

Windows Server


Requirements

Verify that your operating systems are patched to the levels recommended by the manufacturer. The following patch levels have been identified as critical to the proper functioning of the EMC Smarts software. The installation program will stop if it does not detect the required patches. Verify that the operating system is patched to the level described below.

Table 6 on page 15 lists disk space requirements for installing the Adapter for Alcatel-Lucent 5620 SAM EMS:

Note: For multiple-adapter deployments, EMC recommends adding 400 MB additional disk space per Adapter.

Access requirement

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

Table 5 Required operating system patches

Operating system Patches

Red Hat Enterprise Linux 6Red Hat Enterprise Linux 7

When installing on a 64-bit Linux platform, both 64-bit and 32-bit libraries are required.• glibc-2.2.4-32.i686• glibc-2.2.4-32.x86_64• glibc-common-2.2.4-32• compat-libstdc++-33-3.2.3-47.x86_64• compat-libstdc++-33-3.2.3-47.3.i686• redhat-lsb-4.1-24.e17.x86_64Additionally, for Service Assurance Manager Console:On Red Hat Enterprise Linux 7:• libstdc++-4.4.6-3.e16.i686• libXi-1.3-3.e16.i686• libXext-1.1-3.e16.i686• libXtst-1.0.99.2-3.e16.i686• libXrender-0.9.5-1.e16.i686On Red Hat Enterprise Linux 6:• libstdc++-4.4.6-3.el6.i686.rpm• libstdc++-4.4.6-3.el6.i686.rpm• libXi-1.3-3.el6.i686.rpm• libXext-1.1-3.el6.i686.rpm• libXtst-1.0.99.2-3.el6.i686.rpm

Table 6 Required disk space for the Adapter for Alcatel-Lucent 5620 SAM EMS

Platform Disk space

Red Hat Enterprise Linux AS 6 and 7 1.25 GB

Windows Server 2012, x64 and Windows Server 2016, x64 1.25 GB

Operating system requirements 15

Requirements

Software requirementsFollowing are the software requirements for the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS.

Third-party software

The Adapter requires the installation of the Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server. Supported versions of the Alcatel-Lucent 5620 Service SAM EMS server are 6.1 through 17.9.

Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server versions 10.x and higher require that the ASAM 5620 Adapter is at 3.2.0.12 or higher.

The Adapter must be installed on a different host from the Alcatel-Lucent 5620 SAM EMS server, and may be on different hosts from the EMC Smarts Domain Managers.

EMC Smarts software

The Adapter requires the installation of:

• EMC Smarts IP Manager

• EMC Smarts Service Assurance Manager, including the Adapter Platform, Global Manager and Global Console

In addition, your deployment may include one or more of the following products that are supported for use with the Adapter:

• EMC Smarts MPLS Manager

• EMC Smarts Network Protocol Manager

• EMC Smarts Multicast Manager

Table 1 on page 6 lists the interoperable software versions. Ensure that any appropriate Service Pack or patch for the product is applied.

IMPORTANT

You must have root or administrative privileges on the local host to perform this installation.

LicensingTo use the Adapter for Alcatel-Lucent 5620 SAM EMS, the following licenses are required.

EMC Corporation

For the Adapter for Alcatel-Lucent 5620 SAM EMS, you must obtain a license.

For each EMC Smarts Domain Manager deployed in your Adapter installation, you must obtain the following licenses:


Requirements

• The regular Domain Manager license

• A special Adapter for Alcatel-Lucent 5620 SAM EMS license to allow access by the Adapter for Alcatel-Lucent 5620 SAM EMS

The EMC Smarts System Administration Guide provides information on obtaining and installing licenses.

Alcatel-Lucent Corporation

You must obtain the following licenses:

• The Alcatel-Lucent 5620 SAM EMS license

• The Alcatel-Lucent 5620 SAM-O license

To obtain or update your product license, open a Service Request in the Service Center. The license will be sent through email.

Licensing 17

Requirements


CHAPTER 3Installing the Adapter

This chapter describes how to install the Adapter for Alcatel-Lucent 5620 SAM EMS.


• Before installation.............................................................................................................. 20• Install the Adapter for Alcatel-Lucent 5620 SAM EMS ................................................... 20

Installing the Adapter 19

Installing the Adapter

Before installationPerform the following task before installing the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS.

• “Determine the location of the EMC Smarts Broker” on page 20.

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.

Note: By default, generic commands are provided for a UNIX platform. When entering commands, please adjust for your local practice. For example, When entering a command in a UNIX environment, place “./” directly in front of the command (with no space between it and the command). For example:./sm_edit alcatel-sam/emsConfig.importWhen entering a command in a Windows environment, do not use “./”, but change the direction of any directory path slashes. For example:sm_edit alcatel-sam\emsConfig.import

Determine the location of the EMC Smarts Broker

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

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

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

Install the Adapter for Alcatel-Lucent 5620 SAM EMSThis section describes how to install the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS into a new directory structure. The Adapter for Alcatel-Lucent 5620 SAM EMS is available for download from the EMC support website, https://support.emc.com.

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

• If you are using CD media, insert the CD-ROM into the optical drive of the host system. “Procedures for CD-ROMs” on page 53 describes how to access the optical drive for various operating systems.

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



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

Install using Wizard mode

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

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

Running Wizard mode

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

Table 7 Setup command syntax for Wizard mode

Operating system Setup command

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

Note: If your operating system is not patched to the correct level, the following message is displayed: “ERROR: Required OS patch is missing.” “If your system is not patched completely” on page 25 provides more information.

2. Click OK in the Warning dialog box.

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

3. Click Next in the Welcome screen.

Next is disabled if you do not have administrative privileges and a message also appears. To install, you must restart the installation with the 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 product, the Installation Type screen displays.

Select Install the product to a new directory.

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

Linux AS6 ./setup-ASAM-3_4_0_0-linux-rhAS60-64.bin

Linux AS7 ./setup-ASAM-3_4_0_0-linux-rhAS70-64.bin

Windows setup-ASAM-3_4_0_0-win64.exe

Install the Adapter for Alcatel-Lucent 5620 SAM EMS 21


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

7. In the Setup screen, select:

• Complete to install all ASAM products. Click Next.

• Custom to install a specific ASAM product. Click Next.

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

b. Click Next.

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

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

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

9. Specify the EMC Smarts Broker.

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

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

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

Click Next to continue.

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

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

12. See “Where to go next” on page 25 for post-installation tasks.

Install using CLI mode

CLI mode provides a text-based method for invoking the installation program. This mode is intended for UNIX platforms with non-graphics consoles. The CLI mode follows the same process as the wizard mode but uses text rather than graphics.

Running CLI mode

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

Table 8 Setup command syntax for CLI-mode

Operating system Executable

User selections and navigation in CLI mode

During the installation and uninstallation processes, you are prompted with a series of steps and menus:

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

• For selections in menus, accept the default selections or type the number of the item and press Enter. The default values are indicated in brackets or as predefined 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 these keys.

Table 9 Navigation keys

Key Operation

See “Where to go next” on page 25 for post-installation tasks.

Linux AS6 setup-ASAM-3_4_0_0-linux-rhAS60-64.bin -console

Linux AS7 ./setup-ASAM-3_4_0_0-linux-rhAS70-64.bin -console

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



Install using unattended mode

Unattended mode is supported for all operating system but separate response files are needed for UNIX and Windows systems. This method reads the selections and settings for the installation from a user-modifiable file, which enables users to easily duplicate the installation on many computer systems. Manual intervention is not necessary after you execute the setup command.

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

Running unattended mode

Run the Setup command from a command line shell.

Table 10 Setup command syntax for unattended mode

Operating system Executable

For example, to start the unattended installation of the Adapter for Alcatel-Lucent 5620 SAM EMS on Windows when the response file is located in C:\, run:

./setup-ASAM-3_4_0_0-win64.exe -options C:\ALCATEL_SAM-response.txt

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

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

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

• Support Windows operating systems

• Specify a different Broker location

To modify the response file:

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

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

• Specify the target directory.

Linux AS6 # setup-ASAM-3_4_0_0-linux-rhAS60-64.bin -options <path>/ALCATEL_SAM-response.txt

Linux AS7 ./setup-ASAM-3_4_0_0-linux-rhAS70-64.bin options <path>/ALCATEL_SAM-response.txt

Windows setup-ASAM-3_4_0_0-win64.exe -options <path>\ALCATEL_SAM-response.txt



• Select a directory for the process log file.

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

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

• Specify the location of the Broker.

3. Save the file.

Where to go next

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

• “Migrating to version 3.4” on page 28 describes additional tasks if you are migrating from a previous version of the product.

• “Verifying the Installation” on page 35 describes verifying the proper installation of the software and starting services.

If your system is not patched completely

For installation of the Adapter to complete successfully, your system must be fully patched, as outlined in Table 5 on page 15.

If the system detects that a patch is missing, it displays the message, “ERROR: Required OS

patch is missing.” In response to this message:

1. Click OK.

2. Consult the Operating System Information window for a list of the missing patches.

3. Install the one or more patches.

4. Continue with the installation.




CHAPTER 4Performing a Migration

This chapter describes steps for migrating from previous a version of EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS. It includes an optional procedure for migration in a multiple-Adapter deployment.


• Migrating to version 3.4 .................................................................................................... 28• Migration for multiple-Adapter deployment ..................................................................... 31

Performing a Migration 27

Performing a Migration

Migrating to version 3.4If the Adapter was previously deployed, EMC Corporation recommends that you install the new Adapter version to a new location. Then, migrate any customized values for the following files from the old version to the new version:

• emsConfig.import

• ASA-Filter.conf

• ASA-Alarm.conf

• AggregateAlarms.conf

• DevicesNotInEffect.conf

• displayNames.conf

The EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide provides important configuration instructions for the samOss.jar file.

IMPORTANT

If any other file has been changed, please contact EMC. Do not try to customize any other configuration file.

The EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide provides detailed information about configuration parameters.

Note: If your deployment includes multiple Adapters, use the procedure in “Migration for multiple-Adapter deployment” on page 31 to minimize down time.

Migrating emsConfig.import parameters

This section lists parameters that have been changed since version 2.1.

Removed parameters

The following parameters in version 2.1 were removed:

• OSPFConfigurationErrorAlarmTimeout

• AdapterCompatabilityMode

• IESAfterVPLS

• MulticastQTag

Note: Do not migrate these parameters to the file in the new installation.



Added parameters

Table 11 on page 29 lists the parameters that have been added to the emsConfig.import file.

Table 11 Added parameters

Parameter Adapter version when added

All other parameters are common to all versions.

The EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide provides information about configuring the emsConfig.import parameters.

Procedure

Copy and paste any customized parameter values from the file in the old installation area to the file in the new installation area. Do not copy and paste the entire file.

Migrating ASA-Filter.conf parameters

Specify the items that will be included in the JMS messages received from the Alcatel-Lucent 5620 SAM EMS.

The following is a snippet from the current default JMS filter in the ASA-Filter.conf file:

# This file contains Alcatel events or classes #(packageName.ClassName) that will be included in the #JMS.

# The maximum size of JMS topic is 100K (total from all #sessions). To use *include*, instead of

# *exclude* is to reduce the risk of the topic being full #so quickly.apipe.Apipeapipe.L2AccessInterface

Create7210NetworkConnections 3.3.0.0

CreateIESSAPs

CreateVLLSAPs

CreateVPLSSAPs

CreateVPRNSAPs

JmsConnectionMode 3.0.0.1

IGMPNetworkDiscoveryEnabled 3.0.0.0 (and 2.1.0.3)

MulticastTreeDiscoveryEnabled

UnmanageWhenInMaintenance 3.0.0.0

NeighborDownThresholdForRouterDown

RouterDownCheckInterval

FibDiscoveryEnabled 2.1.0.2

EMSReconnectInterval 2.1.0.0

MissedKeepAliveMessages

RestartTimeAfterTerminateClient

VPLSRTPrefix

Migrating to version 3.4 29


The migration process for the ASA-Filters.conf file differs, depending on which Adapter version you are migrating from.

Adapter version 2.1.0.1 or later

This file is inclusive, specifying the items to receive.

1. In the old installation, compare the files in the default conf/alcatel-sam/ASA-Filter.conf and the customized local/conf/alcatel-sam/ASA-Filter.conf to determine what was customized. For example, lines were added.

2. If there are any customizations in the old file, do the following:

• Added line—Copy to the file in the new installation.

• Deleted line—Delete from the file in the new installation.

Adapter version 2.1.0.0 or earlier

This file is exclusive, specifying the items that will not be received.

1. In the old installation, compare the files in the default conf/alcatel-sam/ASA-Filter.conf and the customized local/conf/alcatel-sam/ASA-Filter.conf to determine what was customized. For example, lines were added.

2. If there are any customizations in the old file, do the following:

• Added line—Delete from the file in the new installation, so the item will be excluded.

Note: You may find that the item does not exist in the new installation.

• Deleted line—Copy to the file in the new installation, so the item will be included. In this case, please notify EMC.

Migrating ASA-Alarm.conf parameters

This file is specifies the parameters for importing alarms. It also specifies which alarms are not imported.

1. In the old installation, compare the files in the default conf/alcatel-sam/ASA-Alarm.conf and the customized local/conf/alcatel-sam/ASA-Alarm.conf to determine what was customized. For example, lines were added.

2. If there are any customizations, do the following:

• Added line—Copy to the file in the new installation.

• Deleted line—Delete from the file in the new installation.

Migrating AggregateAlarms.conf parameters

This file has not been changed. If you have customized this file, copy it to the new installation area.

Migrating DevicesNotInEffect.conf parameters

This file has not been changed. If you have customized this file, copy it to the new installation area.



Migration for multiple-Adapter deploymentWhen your deployment includes multiple Adapter servers on one system, you can use this optional migration procedure to provide for either of the following:

• A procedure that preserves the previous version.

• The ability to migrate one Adapter server at a time without the need to shut down an entire deployment.

This procedure is appropriate for full software versions and patches. Use of this procedure will minimize down time.

IMPORTANT

With this procedure, you retain concurrent patch versions, allowing you to restart from either version, as required for your deployment. After your evaluation is complete, retain one version and remove the other version, following the procedure in “Uninstalling the Adapter” on page 39.

Migrating to the new version

This section summarizes the migration steps.

Assumptions

The following assumptions are relevant for this procedure:

• A previous version of the Adapter is installed in the default ASAM_BASEDIR location.

• The Adapter service is running.

Procedure

To migrate the Adapter to a new version in a multiple-Adapter deployment, follow these steps for each installation of the Adapter:

1. Create a new install location. The default location is /opt/InCharge/ASAM. Retain this location and create a new location, as follows:

/opt/InCharge/<New Unique Directory Name>/ASAM

Where <New Unique Directory Name> represents the new version of the Adapter. For example, to upgrade to version 3.4.0.0, you might name the directory as follows:

InCharge/ASAM3400/

2. In the new installation directory, install the Adapter, as described in “Installing the Adapter” on page 19.

3. Also in the new installation directory, install the patch, as described in the Patch Notes.

4. In the original installation directory, stop the Adapter server. If the Adapter is running as a service, use the stop command to stop the server. For example,

sm_service stop ic-alcatel-sam

5. Migrate services to the new installation:

Migration for multiple-Adapter deployment 31


a. In the original installation directory, if the Adapter service is manually installed, manually uninstall the service, as follows:

UNIX

sm_service remove ic-alcatel-sam

Windows

C:\InCharge\ASAM\smarts\bin> sm_service.exe remove ic-alcatel-sam

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

b. In the new installation directory, manually install the service in the new directory. For example, issue the following command to install the service:

UNIX

bin/sm_service install --force --unmanaged --startmode=runonce--name=ic-asam--description=”EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS”--env=SM_JAVA_ENABLED=YES/opt/InCharge/<New Unique Directory Name>/ASAM/smarts/bin/sm_server--name=ASAM--config=alcatel-sam--java--subscribe=default--output--ignore-restore-errors

Windows

C:\InCharge\ASAM\smarts\bin> sm_service.exe install--force--unmanaged--startmode=runonce--name=ASAM--description="EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS"--env=SM_JAVA_ENABLED=YESC:\InCharge\<New Unique Directory Name>\ASAM\smarts\bin\sm_server.exe--name=ic-asam--config=alcatel-sam--java--output--ignore-restore-errors

6. Complete the migration process, as described in “Migrating to version 3.4” on page 28.

7. Migrate the .rps file from the original installation directory, InCharge/ASAM/smarts/local/repos/icf

to the new directory, as follows:

InCharge/<New Unique Directory Name>/ASAM/smarts/local/repos/icf

8. In the new installation directory, start the Adapter server.



9. Perform a full discovery.

IMPORTANT

Do not remove or uninstall the older version of the Adapter until your evaluation is complete.

Reverting to the previous version

Use this procedure to revert to (roll back to) the previously installed version:

1. In the new installation directory, stop the Adapter.

2. Migrate services to the old installation:

a. In the new installation directory, if the Adapter service is manually installed, manually uninstall the service:

UNIX

sm_service uninstall --force --unmanaged --startmode=runonce --name=ic-asam--description=EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS”--env=SM_JAVA_ENABLED=YES/opt/InCharge/<New Unique Directory Name>/ASAM/smarts/bin/sm_server--name=ic-asam--config=alcatel-sam--java--subscribe=default--output--ignore-restore-errors

Windows

C:\InCharge\ASAM\smarts\bin> sm_service.exe uninstall--force--unmanaged--startmode=runonce--name=ic-asam--description="EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS"--env=SM_JAVA_ENABLED=YESC:\InCharge\<New Unique Directory Name>\ASAM\smarts\bin\sm_server.exe--name=ic-asam--config=alcatel-sam--java--output--ignore-restore-errors

b. In the original installation directory, manually install the service, as described in “Manually Installing Services” on page 49.

3. In the original installation directory, start the Adapter server.

4. Perform a full discovery.

Migration for multiple-Adapter deployment 33



CHAPTER 5Verifying the Installation

This chapter describes tasks for confirming proper installation of the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS.


• Obtain and install a temporary license file ........................................................................ 36• Start EMC Smarts services ................................................................................................ 36• Start EMC Smarts programs.............................................................................................. 37• Service and program startup options ................................................................................. 38• Verify the EMC Smarts product status .............................................................................. 38

Verifying the Installation 35

Verifying the Installation

Obtain and install a temporary license fileTo obtain a temporary (evaluation) license, complete a Support Request (SR) form, which you can find on the EMC support website, http://support.emc.com.

Your EMC account team will send you a temporary (evaluation) <license_name>.lic file through email. Copy the license file to the BASEDIR/smarts/local/conf directory on the host system where you have installed the EMC Smarts software.

• If multiple products run on the same host, copy the license file to the BASEDIR/smarts/local/conf directory for each product.

• If a product runs on multiple hosts, copy the license file to the BASEDIR/smarts/local/conf directory on each host where the software is installed.

Edit the SM_LICENSE variable in runcmd_env.sh on each host where EMC Smarts software is installed to specify the full path and file name of a single license file. When multiple products are installed on the same host, each product will include a runcmd_env.sh in its BASEDIR/smarts/local/conf directory.

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

Temporary licenses are time-limited. At the end of the trial period, the software will no longer start. The trial license has an expiration date.

Start EMC Smarts servicesEMC Corporation recommends installing Managers as services. If you installed the products as services, you must start them for the first time. These services start automatically upon system reboot, the following sections describe how to start EMC Smarts services.

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.

Linux

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

/etc/init.d/ic-serviced status

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

/etc/init.d/ic-serviced start

Starting EMC Smarts 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 (UNIX)

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

For UNIX, type:

./sm_service start ic-asam

Starting services on Windows

To start an EMC Smarts service from the Windows desktop, follow these steps:

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

2. Select Services.

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

4. Choose Start from the menu.

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

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

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

Starting programs on UNIX

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

Starting the EMC Smarts Broker

./brstart --port=426 --output

Starting a Manager

/sm_server --name=<server_name> --config=<config_directory>--port=0--ignore-restore-errors--output

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

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

Start EMC Smarts programs 37


Starting programs on Windows

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

Starting the EMC Smarts Broker

brstart --port=426 --output

Starting a Manager

sm_server --name=<server_name> --config=<config_directory>--port=0--ignore-restore-errors--output

Service and program startup optionsTable 12 on page 38 lists service names, server names, and configuration directories for EMC Smarts products.

• “Manually Installing Services” on page 49 provides the default service and program parameters used for the service install commands.

• The EMC Smarts System Administration Guide provides information regarding the sm_server, sm_adapter, and sm_trapd programs.

Table 12 Default names and configuration directories for services and programs

Product Service name Server nameConfig directory

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

./brcontrol

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

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

EMC Smarts Broker ic-broker n/a n/a

Adapter for Alcatel-Lucent 5620 SAM EMS

ic-asam ASAM /alcatel-sam


CHAPTER 6Uninstalling the Adapter

This chapter describes how to uninstall the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS.


• Before uninstallation.......................................................................................................... 40• Uninstalling the Adapter for Alcatel-Lucent 5620 SAM EMS.......................................... 44

Uninstalling the Adapter 39

Uninstalling the Adapter

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

• “Extracting JVM file” on page 40

• “Remove manually installed services” on page 40

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

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

• “Detect and stop EMC Smarts programs” on page 41

• “Uninstall the FLEXnet License Server” on page 44

Extracting JVM file

To uninstall the product software completely, you must extract the _jvm.zip (in Windows) and _jvm.tar (in Linux) files manually before uninstalling the product software.

If uninstaller does not find the _jvm.zip/_jvm.tar folder in any of the directories, then you may encounter errors in uninstallation. To avoid the errors, complete the following procedure.

To extract the _jvm.tar or _jvm.zip, perform these steps:

For Linux:

1. Navigate to the /opt/InCharge/<product>.

2. Extract the _jvm.tar file, by invoking the following command:

sudo tar -xvf _jvm.tar

For Windows:

1. Navigate to the C:\InCharge\<product>.

2. Right-click on the _jvm.zip file, and then select Extract.

After uninstallation, if the _jvm.tar/_jvm.zip folder are present in the install location, then remove it manually.

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

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



Determine order for removing products (UNIX only)

When uninstalling EMC Smarts products from the same server, the product that was installed first must be uninstalled last. During the installation of the first product, the EMC Smarts Service Database is created and the other products subsequently access it. Uninstalling the product 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 software was installed first by perform this check:

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

• 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 product was installed first.

Uninstall when the same product software is installed twice (Windows only)

If you installed the same product to different locations on the same host system, do not use Add/Remove Programs to uninstall. Uninstall the EMC Smarts product as follows:

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

C:\BASEDIR\_uninst\uninstaller.exe

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

2. Complete the uninstallation beginning with step 2 as described in “Uninstall using Wizard mode” on page 45.

Detect and stop EMC Smarts programs

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

Detecting EMC Smarts programs

The sm_plist utility identifies all EMC Smarts programs that are running for any product on your machine. You can use the sm_plist utility whenever you need to identify EMC Smarts programs that are running (for example, before applying a service pack or patch and uninstalling the product software).

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

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

2. Start the sm_plist utility:

For UNIX, type

# ./sm_plist.sh BASEDIR2

For Windows, type

cscript sm_plist.vbs BASEDIR2

Before uninstallation 41


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

Stopping active EMC Smarts programs (UNIX)

To stop active EMC Smarts programs (UNIX):

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

# ./sm_service stop --all

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

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

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

Based on the location of the Broker, go to the appropriate step, as indicated in Table 13 on page 42:

Table 13 Next steps for detecting and stopping programs

The Broker is on the And this displays Do this

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

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

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

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

# ./dmquit --server=<servername>

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

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

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

• Detect the processes using the following command:

# ps -ef | grep “sm_”

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

Same host “Error attaching to Broker” message

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

List of servers registered with the Broker Go to Step 3.

Different host List of servers registered with the Broker



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

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

# kill <pid>

Stopping active EMC Smarts programs (Windows)

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

1. Select Settings > Control Panel.

2. At the Control Panel, select Administrative Tools.

3. At the Administrative Tools folder, select Services.

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

Note: Do not stop the Broker service.

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

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

brcontrol -b <host>:<port>

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

dmquit --server=<servername>

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

brquit --broker=localhost:<port>

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

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

11. Select the Processes tab.

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

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

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

Before uninstallation 43


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

Uninstall the FLEXnet License Server

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

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

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

To stop and uninstall the FLEXnet License Server:

1. Stop the FLEXnet License Server.

Linux

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

Windows

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

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

• Select Services.

• Select the FLEXnet License Server service.

• Right-click and choose Stop.

2. 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 the Adapter for Alcatel-Lucent 5620 SAM EMSEMC Smarts product software uses InstallShield software to install and uninstall products. For UNIX, you invoke the uninstallation program from the system prompt. For Windows, you use the Add/Remove Programs, except when the same product 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 Smarts software and the host where you log in must be configured to run the X Window System. Before starting the installation program using the Wizard mode, verify that the X Window System is running.

1. Invoke the uninstaller program:

For UNIX, type:

BASEDIR/_uninst/uninstaller.bin

For Windows, use Add/Remove Programs:

a. Click Start > Settings > Control Panel.

b. Double-click Add/Remove Programs.

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

d. Click Change/Remove.

2. Click Next in the Welcome screen to continue.

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

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

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

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

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

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

6. Examine any remaining directories if you plan to re-install EMC Smarts and save customized files located in the /local directory. Depending upon the product, 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

Uninstalling the Adapter for Alcatel-Lucent 5620 SAM EMS 45


Uninstall using CLI mode

To uninstall an EMC Smarts product:

1. Type the following command and press Enter:

# BASEDIR/_uninst/uninstaller.bin -console

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

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

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

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 re-install the product and save customized files located in the /local directory. Depending upon the product, 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.<product>.<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 Smarts products.

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

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

BASEDIR/_uninst/uninstaller.bin -silent

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

BASEDIR\_uninst\uninstaller.exe -silent



Note: Type each command as one line.

2. Examine any remaining directories if you plan to re-install the product and save customized files located in the /local directory. Depending upon the product, 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.

Uninstalling the Adapter for Alcatel-Lucent 5620 SAM EMS 47



APPENDIX AManually Installing Services

This appendix consists of the following sections:

• Overview............................................................................................................................ 50• Adapter for Alcatel-Lucent 5620 SAM EMS services ...................................................... 50

Manually Installing Services 49

Manually Installing Services

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

EMC Corporation recommends that EMC Smarts products be installed as services whenever possible. Typical reasons to install products as services include the following conditions:

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

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

To manually install a product as a service, use the sm_service install command with the appropriate set of options.

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

Adapter for Alcatel-Lucent 5620 SAM EMS servicesThis section provides the default service parameters for the Adapter for Alcatel-Lucent 5620 SAM EMS.

EMC Smarts Broker

UNIX /opt/InCharge/SAM/smarts/bin/sm_service install--force--startmode=runonce--name=ic-broker--description="EMC Smarts Broker"--env=SM_CLIENTCONNECT=brokerConnect.conf/opt/InCharge/IP/smarts/bin/brstart --port=426--restore=/opt/InCharge/IP/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 Smarts Broker"--env=SM_CLIENTCONNECT=brokerConnect.confC:\InCharge\IP\smarts\bin\brstart.exe--port=426 --restore=C:\InCharge\IP\smarts\local\repos\broker\broker.rps

Note: Indicates that this command must be typed as one line.



Adapter for Alcatel-Lucent 5620 SAM EMS

UNIX sm_service install --force --unmanaged --startmode=runonce --name=ic-asam--description=”EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS”--env=SM_JAVA_ENABLED=YES/opt/InCharge/ASAM/smarts/bin/sm_server--name=ASAM--config=alcatel-sam--java--subscribe=default--output--ignore-restore-errors

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

Windows C:\\InCharge\ASAM\smarts\bin> sm_service.exe install--force--unmanaged--startmode=runonce--name=ic-asam--description="EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS"--env=SM_JAVA_ENABLED=YESC:\InCharge\ASAM\smarts\bin\sm_server.exe--name=ASAM--config=alcatel-sam--java--output--ignore-restore-errors

Adapter for Alcatel-Lucent 5620 SAM EMS services 51



APPENDIX BProcedures for CD-ROMs

As a reference, this appendix includes commands and examples for working with a CD-ROM to install the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS.

This appendix consists of the following sections:

• Mounting a CD-ROM on UNIX systems .......................................................................... 54• Loading a CD-ROM on Windows ..................................................................................... 54

Procedures for CD-ROMs 53

Procedures for CD-ROMs

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

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

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

Table 14 Mounting the CD-ROM for UNIX operating systems

Operating System Commands and Examples

mount <DEVICE>

Example:mount /dev/cdrom /mnt/cdrom

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

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

Operating System Command

cd /cdrom/<product>-<os><version>/suite

cd /mnt/cdrom/suite

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

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

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

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

If you want to run CLI mode or Unattended mode on a Windows system, you need to disable the AutoPlay or AutoRun feature. To do so, press and hold the Shift key for approximately 10 seconds while inserting the CD/DVD-ROM into the optical drive.

Linux

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

Linux If Automount is running:

If Automount is not running:

where: <product> is the product, for example, SAM or IP.<os> is the operating system, for example LINUX, or WIN.<version> is the software version, for example, 12.


APPENDIX CGetting help

This appendix provides the following topics:

? Where to get help............................................................................................................... 56

Getting help 55

Getting help

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, go to EMC Online Support at:

https://support.emc.com

Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. 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.


http://support.emc.com

Date post:	19-Mar-2020
Category:	Documents
Upload:	others
View:	5 times
Download:	0 times

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM …...Overview 5 CHAPTER 1 Overview This chapter...

Documents