VMware Smart Assurance Adapter for Alcatel-Lucent 5620 …...The Adapter for Alcatel-Lucent 5620 SAM...

VMware Smart Assurance Adapter forAlcatel-Lucent 5620 SAM EMSInstallation Guide

VMware Smart Assurance 10.1.0

You can find the most up-to-date technical documentation on the VMware website at:

https://docs.vmware.com/

If you have comments about this documentation, submit your feedback to

[email protected]

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

Copyright © 2019 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide

VMware, Inc. 2


mailto:[email protected]

http://pubs.vmware.com/copyright-trademark.html

Contents

1 Overview 5Adapter for Alcatel-Lucent 5620 SAM EMS 5

Product and release compatibility 5

Installation tasks overview 6

Uninstallation tasks overview 7

Product description 7

New features and changes 7

New features in Foundation 10.1 8

New features in ASAM Patches 10

2 Requirements 11Operating system requirements 11

Recommended patch levels 11

Access requirement 12

Software requirements 12

Third-party software 13

VMware Smart Assurance software 13

3 Installing the Adapter 14Before installation 14

Determine the location of the VMware Smart Assurance Broker 14

Install the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS 15

Install using CLI mode 15

Install using unattended mode 15

Where to go next 16

If your system is not patched completely 17

4 Performing a Migration 18Migrating to version 3.5 18

Migrating emsConfig.import parameters 18

Migrating ASA-Filter.conf parameters 20

Migrating ASA-Alarm.conf parameters 20

Migrating AggregateAlarms.conf parameters 21

Migrating DevicesNotInEffect.conf parameters 21

Migration for multiple-Adapter deployment 21

Migrating to the new version 21

Reverting to the previous version 23

VMware, Inc. 3

5 Verifying the Installation 24Start VMware Smart Assurance services 24

Starting services on UNIX 24

Start VMware Smart Assurance programs 25

Starting programs on UNIX 26

Service and program startup options 26

Verify the VMware Smart Assurance product status 26

6 Uninstalling the Adapter 28Before uninstallation 28

Remove manually installed services 28

Determine order for removing products (UNIX only) 28

Detect and stop VMware Smart Assurance programs 29

Uninstalling the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS 31

Uninstall using CLI mode 31

Uninstall using unattended mode 31

7 Manually Installing Services 33Overview 33

Adapter for Alcatel-Lucent 5620 SAM EMS services 33

VMware Smart Assurance Broker 33

Adapter for Alcatel-Lucent 5620 SAM EMS 34

8 Getting help 35Where to get help 35


VMware, Inc. 4

Overview 1This chapter describes the Alcatel-Lucent 5620 SAM EMS product, compatibility with other VMwareSmart Assuranceproducts, and installation tasks.

This chapter includes the following topics:

n Adapter for Alcatel-Lucent 5620 SAM EMS

n Product and release compatibility

n Installation tasks overview

n Uninstallation tasks overview

n Product description

n New features and changes

Adapter for Alcatel-Lucent 5620 SAM EMS

The product is available for download from the VMware support website, support.vmware.com.

Product and release compatibility

The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS (ASAM) requires theinstallation of the Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server. Support is from NFM-P 17.9 to NFM-P 19.6 for the Alcatel-Lucent 5620 Service SAM EMS server.

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 VMware Smart Assurance Domain Managers.

The Adapter for Alcatel-Lucent 5620 SAM EMS version 3.5 is compatible with the versions of theseproducts in Interoperability chart.

Table 1-1. Interoperability chart

VMware Smart Assurance product Versions

IP Manager (IP) - required 9.5.x.x, 9.6.x.x, 10.0.x.x, 10.1.x.x

MPLS Manager (MPLS) - optional 9.5.x.x, 9.6.x.x, 10.0.x.x, 10.1.x.x

Multicast Manager (MCAST) - optional 8.1.5, 10.1.x.x

VMware, Inc. 5

https://www.vmware.com/support.html

Table 1-1. Interoperability chart (continued)

VMware Smart Assurance product Versions

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

Service Assurance Manager (SAM) - required 9.5.x.x, 9.6.x.x, 10.0.x.x, 10.1.x.x (with latestpatch)

Important Ensure that the latest patch for the product listed in Interoperability chart is applied. TheVMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes provides moredetailed information.

Installation tasks overview

Adapter for Alcatel-Lucent 5620 SAM EMS installation requirements and tasks summarizes theinstallation tasks for the Adapter:

Table 1-2. Alcatel-Lucent 5620 SAM EMS installation requirements and tasks

Before you install:

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

VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes

Determine if the products are supported onyour platform.

Operating system requirements

Installation method:

Install the VMware Smart Assurance Adapterfor Alcatel-Lucent 5620 SAM EMS.

Choose one of the following installation methods:

n UNIX only, Install using CLI mode

n Install using unattended mode

After you install:

Save your license in the proper location:

n Evaluation license—Save smarts.lic to theBASEDIR/smarts/local/conf directory.

n Permanent license—Use the proceduresdescribed in the VMware SmartAssurance System Administration Guide.

Obtain and install a temporary license file

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

n Starting services on UNIX

Verify the current state of the products andBroker.

“Verify the VMware Smart Assurance product status”

Note Ensure that the latest patch for the VMware Smart Assurance Adapter for Alcatel-Lucent 5620SAM EMS is applied. The patch software and patch documentation that provides instructions to upgradedeployments are available from the VMware support website, support.vmware.com.


VMware, Inc. 6


Uninstallation tasks overview

To uninstall the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS, perform the taskslisted in Adapter for Alcatel-Lucent 5620 SAM EMS uninstallation requirements and tasks

Table 1-3. VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS uninstallationrequirements and tasks

Before you uninstall:

Review uninstall prerequisites: n Remove manually installed services

n Determine order for removing products (UNIX only)

n Detect and stop VMware Smart Assurance programs

Uninstallation:

Uninstall the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS:

n Uninstall using CLI mode

n Uninstall using unattended mode

Product description

The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS provides a link from theAlcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following VMwareSmart Assurance Domain Managers:

n IP Availability Manager

n MPLS Topology Manager

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

n Multicast Manager

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

New features and changes

The Adapter for Alcatel-Lucent 5620 SAM EMS provides the following new features:

n Smarts Adapter for Alcatel-Lucent 5620 SAM version 3.5 includes support for Nokia 7210 ServiceAccess Switch in satellite mode. This is qualified on NFM-P version 17.9.

n Support for CMG-a8 gateway server in ASAM.

n Support for NFM-P 18.12 version on RHEL 7.2 in SMARTS.

n Support for VPRN Ipsec interface is available on ASAM 3.5, this feature is qualified on NFM-P 17.12SP 15


VMware, Inc. 7

n RHEL 7.6 support for NFM-P Adapter

n ASAM 3.5 is also qualified against NFM-P 19.6 GA

n Note ASAM 3.5 Adapter is also qualified against Nokia NFM-P 19.6 with SR 7 and SR 14 devices.

New features in Foundation 10.1

This release of the Adapter for Alcatel-Lucent 5620 SAM EMS is based upon foundation 10.1.Documentation explaining Foundation 10.1 features is listed in the VMware Smart Assurance Adapter forAlcatel-Lucent 5620 SAM EMS Release Notes. Here are highlights of changes related to Foundation10.1:

Internationalization

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

In this release, the foundation has been internationalized and is functionally localized to AmericanEnglish. Localization to the other target languages, as dictated by the VMware globalization policy andcustomer 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 havethe following syntax: <name>_<locale>_<encoding>.log. For example,MYDOMAINMANAGER_en_US_UTF-8.log. The System Administration Guide provides completeinformation about locale and log files.

ICIM Ref 1.10

Foundation 10.1 has been updated to support ICIM Reference 1.10.

New SmRestartableDomainManager class

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

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

New MODEL operations to retrieve description text


VMware, Inc. 8

There are a number of API operations that have been re-implemented as MODEL operations. TheseMODEL operations retrieve description texts. The texts that are retrieved will be in the locale that was seteither by the initial connection or by the locale set by the most recent call to the setRemoteLocale APIoperation. 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 isCI_Locale::DEFAULT.

The operations are:

n getPropDescription — retrieve the description of the MODEL property

n getEventDescription — retrieve the description of the MODEL event

n getOpDescription — retrieve the description of the MODEL event

n getClassDescription — retrieve the description of the MODEL class

These MODEL operations are described in the VMware Smart Assurance 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 asubscriber front end ( --subscribe or --subscribeProp). Setting alarmInterval causes the front end togenerate 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, inorder 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 classesinherit CMP core classes, and are used by ICIM core and ICF framework.

The ICF Core classes are described further in the VMware Smart Assurance 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 checkfor 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 beenadded to the output of the sm_server --version command.

icim-core split


VMware, Inc. 9

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

n CORE_ManagedObject

n CORE_Collection

n CORE_MetaObject

n 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

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 10.1 patches, consult the patch documentation on the VMwareDocs website, docs.vmware.com.


VMware, Inc. 10


Requirements 2This chapter describes the operating system requirements and hardware requirements for the Alcatel-Lucent 5620 SAM EMS.


n Operating system requirements

n Software requirements

Operating system requirements

Adapter for Alcatel-Lucent 5620 SAM EMS Version 10.1 requires the 64-bit version of the operatingsystem for all platforms. Ensure that hardware hosting the Adapter for Alcatel-Lucent 5620 SAM EMSruns a 64-bit operating system and is patched to the latest patch levels recommended by themanufacturer.

Table 2-1. Supported operating system for the Adapter for Alcatel-Lucent 5620 SAM EMS

Operating system Supported version

Red Hat Enterprise Linux n RHEL 6.9, RHEL 6.10

n RHEL 7.4, 7.5, and RHEL 7.6

Recommended patch levels

Required operating system patches summarizes the operating system patches required for the Adapterfor Alcatel-Lucent 5620 SAM EMS:

Note 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 VMware SmartAssurance software. The installation program will stop if it does not detect the required patches. Verifythat the operating system is patched to the level described below.

VMware, Inc. 11

Table 2-2. Required operating system patches

Operating system Patches

HP-UX 11.11 Apply the latest Standard HP-UX Patch bundle that the HP patch assessment toolrecommends

Red Hat Enterprise Linux 6

Red Hat Enterprise Linux 7

When installing on a 64-bit Linux platform, both 64-bit and 32-bit libraries arerequired.

n glibc-2.2.4-32.i686

n glibc-2.2.4-32.x86_64

n glibc-common-2.2.4-32

n compat-libstdc++-33-3.2.3-47.x86_64

n compat-libstdc++-33-3.2.3-47.3.i686

n redhat-lsb-4.1-24.e17.x86_64

Additionally, for Service Assurance Manager Console:

On Red Hat Enterprise Linux 7:

n libstdc++-4.4.6-3.e16.i686

n libXi-1.3-3.e16.i686

n libXext-1.1-3.e16.i686

n libXtst-1.0.99.2-3.e16.i686

n libXrender-0.9.5-1.e16.i686

On Red Hat Enterprise Linux 6:

n libstdc++-4.4.6-3.el6.i686.rpm

n libstdc++-4.4.6-3.el6.i686.rpm

n libXi-1.3-3.el6.i686.rpm

n libXext-1.1-3.el6.i686.rpm

n libXtst-1.0.99.2-3.el6.i686.rpm

Required disk space for the Adapter for Alcatel-Lucent 5620 SAM EMS lists disk space requirements forinstalling the Adapter for Alcatel-Lucent 5620 SAM EMS:

Table 2-3. Required disk space for the Adapter for Alcatel-Lucent 5620 SAM EMS

Platform Disk space

HP-UX 11.11 650 MB

Red Hat Enterprise Linux AS 6 and 7 1.25 GB

Note For multiple-adapter deployments, VMware recommends adding 400 MB additional disk space perAdapter.

Access requirement

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

Software requirements


VMware, Inc. 12

Following are the software requirements for the VMware Smart Assurance Alcatel-Lucent 5620 ServiceAware Manager (SAM) EMS.

Third-party software

The Adapter requires the installation of the Alcatel-Lucent 5620 Service Aware Manager (SAM) EMSserver. Alcatel-Lucent 5620 Service SAM EMS server support is from NFM-P 17.9 to NFM-P 19.6.

Note Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server versions 17.9 and higher requirethat the ASAM 5620 Adapter is at 3.3.0.1 or higher.

The Adapter must be installed on a different host from the Alcatel-Lucent 5620 SAM EMS server, andmay be on different hosts from the VMware Smart Assurance Domain Managers.

VMware Smart Assurance software

The Adapter requires the installation of:

n VMware Smart Assurance IP Manager

n VMware Smart Assurance Service Assurance Manager, including the Adapter Platform, GlobalManager and Global Console

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

n VMware Smart Assurance MPLS Management Suite

n VMware Smart Assurance Network Protocol Management Suite

n VMware Smart Assurance Multicast Manager

Interoperability chart lists the interoperable software versions. Ensure that any appropriate ServicePack or patch for the product is applied.

Important You must have root or administrative privileges on the local host to perform thisinstallation.


VMware, Inc. 13

Installing the Adapter 3This chapter describes how to install the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAMEMS.


n Before installation

n Install the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS

Before installation

Perform the following task before installing the VMware Smart Assurance Adapter for Alcatel-Lucent 5620SAM EMS.

n Determine the location of the VMware Smart Assurance Broker .

The user performing the installation must be superuser (User ID 0) on UNIX platforms. Theinstallation 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 nospace between it and the command). For example:

./sm_edit alcatel-sam/emsConfig.import

Determine the location of the VMware Smart Assurance Broker

You must specify the location of the VMware Smart Assurance Broker during installation of the VMwareSmart Assurance software. Typically, this location is chosen during the design of the VMware SmartAssurance software deployment and before any installation begins.

Consult with your deployment planner or check the build guide that documents your deployment todetermine 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 willautomatically install the Broker if it is not already on the host.

VMware, Inc. 14

Install the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS

This section describes how to install the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAMEMS into a new directory structure. The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAMEMS is available for download from the VMware support website, support.vmware.com.

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

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

Install using CLI mode

CLI mode provides a text-based method for invoking the installation program. This mode is intended forUNIX platforms with non-graphics consoles.

Running CLI mode

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

Table 3-1. Setup command syntax for CLI-mode

Operating system Executable

Linux RHEL 6.9, RHEL 6.10, RHEL 7.4,RHEL7.5, and RHEL 7.6

setup-ASAM-3_5_0_0-linux64.bin -i console

User selections and navigation in CLI mode

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

n For prompts, accept the default value or select another choice. The default values are indicated inbrackets. To accept the default value, press Enter. To reply “yes,” type y or Y; to reply “no,” type n orN.

n For selections in menus, accept the default selections or type the number of the item and pressEnter. The default values are indicated in brackets or as predefined selections in menus. An X isused to indicate the selected item. When you are finished making selections, press Enter.

If you incorrectly type an entry, type back to repeat the prompt and select the correct value. Arrowkeys and the Backspace key are not supported.

To navigate between each step, use these keys.

See Where to go next for post-installation tasks.

Install using unattended mode


VMware, Inc. 15


Unattended mode is supported for all operating system but separate response files are needed for UNIXsystems. 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 isnot necessary after you execute the setup command.

Running unattended mode

Run the Setup command from a command line.

Table 3-2. Setup command syntax for unattended mode

Operating system Executable

RHEL 6.9, RHEL 6.10 setup-ASAM-3_5_0_0-linux64.bin -i silent -f <path>/ASAM_SUITE-response.txt

RHEL 7.4, 7.5, and RHEL7.6

setup-ASAM-3_5_0_0-linux64.bin -i silent -f <path>/ASAM_SUITE-response.txt

Modifying the response file

Each 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 theprogram in unattended mode. The command line options are organized by process flow.

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

n Specify a different Broker location

To modify the response file:

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

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

n Specify the target directory.

n Select a directory for the process log file.

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

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

n Specify the location of the Broker.

c Save the file.

Where to go next


VMware, Inc. 16

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

n Chapter 5 Verifying the Installation describes verifying the proper installation of the software andstarting services.

If your system is not patched completely

For installation of the Adapter to complete successfully, your system must be fully patched.

If the system detects that a patch is missing, it displays the message, “ERROR: Required OS patch ismissing.” 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.


VMware, Inc. 17

Performing a Migration 4This chapter describes steps for migrating from a previous version of VMware Smart Assurance Adapterfor Alcatel-Lucent 5620 SAM EMS. It includes an optional procedure for migration in a multiple-Adapterdeployment.


n Migrating to version 3.5

n Migration for multiple-Adapter deployment

Migrating to version 3.5

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

n emsConfig.import

n ASA-Filter.conf

n ASA-Alarm.conf

n AggregateAlarms.conf

n DevicesNotInEffect.conf

n displayNames.conf

The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS User Guide providesimportant configuration instructions for the samOss.jar file.

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

The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS User Guide providesdetailed information about configuration parameters.

Note If your deployment includes multiple Adapters, use the procedure in Migration for multiple-Adapter deployment to minimize down time.

Migrating emsConfig.import parameters

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

VMware, Inc. 18

Removed parametersThe following parameters in version 2.1 were removed:

n OSPFConfigurationErrorAlarmTimeout

n AdapterCompatabilityMode

n IESAfterVPLS

n MulticastQTag

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

Added parametersTable Added parameters lists the parameters that have been added to the emsConfig.import file.

Table 4-1. Added parameters

Parameter Adapter version when added

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

All other parameters are common to all versions.

The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS User Guide providesinformation about configuring the emsConfig.import parameters.

Procedure


VMware, Inc. 19

Copy and paste any customized parameter values from the file in the old installation area to the file in thenew 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 SAMEMS.

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

apipe.L2AccessInterface

The migration process for the ASA-Filters.conf file differs, depending on which Adapter version you aremigrating 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 thecustomized local/conf/alcatel-sam/ASA-Filter.conf to determine what was customized. Forexample, lines were added.

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

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

n 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 thecustomized local/conf/alcatel-sam/ASA-Filter.conf to determine what was customized. Forexample, lines were added.

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

n 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.n Deleted line—Copy to the file in the new installation, so the item will be included. In this case,

please notify VMware.

Migrating ASA-Alarm.conf parameters


VMware, Inc. 20

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 thecustomized local/conf/alcatel-sam/ASA-Alarm.conf to determine what was customized. Forexample, lines were added.

2 If there are any customizations, do the following:

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

n 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 deployment

When your deployment includes multiple Adapter servers on one system, you can use this optionalmigration procedure to provide for either of the following:

n A procedure that preserves the previous version.

n The ability to migrate one Adapter server at a time without the need to shut down an entiredeployment.

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

Important With this procedure, you retain concurrent patch versions, allowing you to restart fromeither version, as required for your deployment. After your evaluation is complete, retain one versionand remove the other version, following the procedure in Chapter 6 Uninstalling the Adapter.

Migrating to the new version

This section summarizes the migration steps.

Assumptions

The following assumptions are relevant for this procedure:

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

n The Adapter service is running.

Procedure


VMware, Inc. 21

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

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

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

InCharge/ASAM3300/

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

InCharge/ASAM3400/

2 In the new installation directory, install the Adapter, as described in Chapter 3 Installing the Adapter.

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, usethe stop command to stop the server. For example,

sm_service stop ic-alcatel-sam

5 Migrate services to the new installation:

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

UNIX

sm_service remove ic-alcatel-sam

tC:\InCharge\ASAM\smarts\bin> sm_service.exe remove ic-alcatel-sams

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=”VMware Smart Assurance 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▲


VMware, Inc. 22

6 Complete the migration process, as described in Migrating to version 3.5.

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

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 theservice:

UNIX

./sm_service remove ic-asam

b In the original installation directory, manually install the service, as described in Chapter 7Manually Installing Services.

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

4 Perform a full discovery.


VMware, Inc. 23

Verifying the Installation 5This chapter describes tasks for confirming proper installation of the VMware Smart Assurance Adapterfor Alcatel-Lucent 5620 SAM EMS.


n Start VMware Smart Assurance services

n Start VMware Smart Assurance programs

n Service and program startup options

n Verify the VMware Smart Assurance product status

Start VMware Smart Assurance services

VMware, Inc. recommends installing Managers as services. If you installed the products as services, youmust start them for the first time. These services start automatically upon system reboot, the followingsections describe how to start VMware Smart Assurance 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-servicedcommand 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

VMware, Inc. 24

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

/etc/init.d/ic-serviced start

HP-UX

On HP-UX systems, type the following command to verify the status of the service daemon:

/sbin/init.d/ic-serviced status

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

/sbin/init.d/ic-serviced start

Starting VMware Smart Assurance 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 theBASEDIR/smarts/bin directory:

For UNIX, type:

./sm_service start

ic-asam

Start VMware Smart Assurance programs

You can start VMware Smart Assurance programs from the terminal when the program is not intended tobe long-running or to perform testing. VMware, Inc. does not recommend using this method in aproduction environment.


VMware, Inc. 25

The VMware Smart Assurance System Administration Guide provides a complete description of thecommand 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 VMware Smart Assurance Broker

./brstart --port=426 --output

Starting a Manager

t ./sm_server --name=<server_name>

--config=<config_directory>

--port=0

--ignore-restore-errors

--output s

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

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

Service and program startup options

Default names and configuration directories for services and programs lists service names, server names,and configuration directories for VMware Smart Assurance products.

n Chapter 7 Manually Installing Services provides the default service and program parameters used forthe service install commands.

n The VMware Smart Assurance System Administration Guide provides information regarding thesm_server, sm_adapter, and sm_trapd programs.

Table 5-1. Default names and configuration directories for services and programs

Product Service name Server name Config directory

VMware Smart Assurance Broker ic-broker n/a n/a

Adapter for Alcatel-Lucent 5620 SAM EMS ic-asam ASAM /alcatel-sam

Verify the VMware Smart Assurance product status


VMware, Inc. 26

You can determine the current state of the products that register with the Broker by typing the followingcommand from the BASEDIR/smarts/bin directory:

./brcontrol

This command displays a list of VMware Smart Assurance Managers and adapters registered with theBroker, their states (RUNNING, DEAD, UNKNOWN), process IDs, port numbers, and the last time thattheir states changed.

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


VMware, Inc. 27

Uninstalling the Adapter 6This chapter describes how to uninstall the Alcatel-Lucent 5620 SAM EMS.


n Before uninstallation

n Uninstalling the VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS

Before uninstallation

This section describes tasks you should complete before uninstalling VMware Smart Assurance software.

n Remove manually installed services

n Determine order for removing products (UNIX only)

n Detect and stop VMware Smart Assurance programs

Remove manually installed services

Services that you manually installed with sm_service command are not removed by the uninstallationprogram. 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>

Determine order for removing products (UNIX only)

VMware, Inc. 28

When uninstalling VMware Smart Assurance products from the same server, the product that wasinstalled first must be uninstalled last. During the installation of the first product, the VMware SmartAssurance Service Database is created and the other products subsequently access it. Uninstalling theproduct installed first will also uninstall the Service Database which will disable the sm_service commandfor 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.

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

n For HP-UX, ic-serviced is located in the /sbin/init.d directory

2 Find the value of the SMHOME variable.

The value of SMHOME indicates which product was installed first.

Detect and stop VMware Smart Assurance programs

Before upgrading or uninstalling your product, you must stop all VMware Smart Assurance services,VMware Smart Assurance scheduledjobs, and any other process that uses programs or libraries runningfrom the VMware Smart Assurance product.

Detecting VMware Smart Assurance programs

The sm_plist utility identifies all VMware Smart Assurance programs that are running for any product onyour machine. You can use the sm_plist utility whenever you need to identify VMware Smart Assuranceprograms that are running (for example, before applying a service pack or patch and uninstalling theproduct software).

To use the utility, invoke itfrom the BASEDIR/smarts/script directory. The utility displays active programsin a window:

1 Go to the BASEDIR/smarts/script directory.

2 Start the sm_plist utility:

For UNIX, type

# .

/sm_plist.sh

BASEDIR2

cscript sm_plist.vbs

BASEDIR2

Stopping active VMware Smart Assurance programs (UNIX)


VMware, Inc. 29

To stop active VMware Smart Assurance programs (UNIX):

1 Stop active VMware Smart Assurance services using the sm_service utility from BASEDIR/smarts/bin:

# ./sm_service stop --all

2 Determine if any VMware Smart Assurance services are still running by using the brcontrol utility fromBASEDIR/smarts/bin:

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

Table 6-1. Next steps for detecting and stopping programs

The Broker is on the And this displays Do this

Same host “Error attaching toBroker” message

The VMware Smart Assurance Broker is not running. Go to Step 4.

List of serversregistered with theBroker

n The Broker or service daemon did not shut down.

n If any servers are still running on the host, these did not shut down.

Go to Step 3.

Different host List of serversregistered with theBroker

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

3 Stop any VMware Smart Assurance server that is still running. If the Broker is on the host, stop thelocal Broker:

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

# ./dmquit --server=

<servername>

# ./brquit --broker=localhost:

<port>

4 Determine if any other VMware Smart Assurance processes are still running and shut the processesdown:

n Detect the processes using the following command:

# ps -ef | grep sm_

# kill

<pid>


VMware, Inc. 30

Uninstalling the VMware Smart Assurance Adapter forAlcatel-Lucent 5620 SAM EMS

VMware Smart Assurance product software uses InstallAnywhere software to install and uninstallproducts. For UNIX, you invoke the uninstallation program from the system prompt. Failure to use theappropriate method will result in an unstable system and/or inconsistent product directories. Do notmanually delete the installed product directories.

Uninstall using CLI mode

To uninstall an VMware Smart Assurance product:

1 Type the following command and press Enter:

#

BASEDIR

/_uninst/uninstaller -i console

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

3 If necessary, the installation program will prompt to restart your computer. Press Enter to restart.

4 Examine any remaining directories if you plan to re-install the product and save customized fileslocated in the /local directory. Depending upon the product, some or all of the following subdirectorieswill remain in the BASEDIR/smarts directory after uninstallation because they contain user-modifiedfiles:

n /local

n /bin

n /setup

The installation log file is a text file with the naming conventionUninstall.<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 VMware Smart Assurance products.

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

n On UNIX systems, use the uninstaller program:

BASEDIR

/_uninst/uninstaller -i -silent


VMware, Inc. 31

2 Examine any remaining directories if you plan to re-install the product and save customized fileslocated in the /local directory. Depending upon the product, some or all of the following subdirectorieswill remain in the BASEDIR/smarts directory after uninstallation because they contain user-modifiedfiles:

n /local

n /bin

n /setup

The log files from the uninstallation are located in the BASEDIR/smarts/setup/logsdirectory. Ifthe uninstallation process fails, the log files are located in the /tmp directory. A non-zerostatus indicates a failure.


VMware, Inc. 32

Manually Installing Services 7This chapter includes the following topics:

n Overview

n Adapter for Alcatel-Lucent 5620 SAM EMS services

Overview

If you did not install services when you installed the VMware Smart Assurance products, you may installservices 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 asnecessary.

VMware, Inc. recommends that VMware Smart Assurance products be installed as services wheneverpossible. Typical reasons to install products as services include the following conditions:

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

n Multiple instances of a single product component running as a service are required. Duringinstallation, 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 installcommand with the appropriateset of options.

The VMware Smart Assurance System Administration Guide provides a complete description of thecommand syntax.

Adapter for Alcatel-Lucent 5620 SAM EMS services

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

VMware Smart Assurance Broker

UNIX

t/opt/InCharge/SAM/smarts/bin/sm_service install

--force

--startmode=runonce

VMware, Inc. 33

--name=ic-broker

--description="VMware Smart Assurance 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 s

Adapter for Alcatel-Lucent 5620 SAM EMS

UNIX

sm_service install --force --unmanaged --startmode=runonce \

'--name=ic-asam' \

'--description=VMware Smart Assurance 5620 SAM EMS Adapter' \

'--env=SM_JAVA_ENABLED=YES' \

'/opt/InCharge/ASAM/smarts/bin/sm_server' \

'--name=ASAM' \

'--config=alcatel-sam' \

'--subscribe=default' \

'--ignore-restore-errors' \

'--output' \

'--java=maxheapsize=1024m'


VMware, Inc. 34

Getting help 8This chapter includes the following topics:

n Where to get help

Where to get help

VMware support, product, and licensing information can be obtained as follows:

Product information

support.vmware.com

For documentation, release notes, software updates, or information about VMware products, go toVMware Online Support at:

docs.vmware.com

Technical support

Go to VMware Online Support. You will see several options for contacting VMware Technical Support.Note that to open a service request, you must have a valid support agreement. Contact your VMwaresales representative for details about obtaining a valid support agreement or with questions about youraccount.

VMware, Inc. 35



VMware Smart Assurance Adapter for Alcatel-Lucent 5620 …...The Adapter for Alcatel-Lucent 5620 SAM...

Documents

Transcript of VMware Smart Assurance Adapter for Alcatel-Lucent 5620 …...The Adapter for Alcatel-Lucent 5620 SAM...