EMC Smarts Application Connectivity Monitor

Transcription

1 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide P/N REV 01

2 Copyright EMC Corporation. All rights reserved. Published in the USA. Published December, 2013 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC 2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation 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 ( 2 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

3 CONTENTS Preface Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Overview About Application Connectivity Monitor... 8 EMC Smarts product and version compatibility... 8 Installation... 8 Requirements Operating system requirements Deprecated Platform support EMC Smarts Application Connectivity Monitor 2.4 is not supported on Red Hat Enterprise Linux AS 3 and 4, and Solaris Hardware requirements Installing Application Connectivity Monitor Getting Started Installation requirements Determine the location of the EMC Smarts Broker Stopping active EMC Smarts programs (UNIX) Choose an operating mode for the installation program Install EMC Smarts Application Connectivity Monitor Mounting the CD-ROM Inserting the CD-ROM Installation Using wizard mode Satisfy Wizard mode requirements (UNIX only) Running Wizard Mode Using CLI mode Install using CLI mode Using unattended (silent) mode Install using unattended mode Migration Migration Upgrade Upgrade Verifying the Installation Obtain and install a temporary license file Start EMC Smarts products Starting services manually Starting services on UNIX Starting services on Windows EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide 3

4 Contents Verify the EMC Smarts product status Where to go next Chapter 7 Appendix A Appendix B Appendix C Appendix D Uninstalling Application Connectivity Monitor Before uninstallation Uninstall the FLEXnet License Server Uninstall Application Connectivity Monitor Uninstall using Wizard mode Uninstall using unattended mode Uninstall from the Control Panel (Windows only) Manually Installing Services Overview Manually installing the Broker Manually installing Application Connectivity Monitor Domain Manager UNIX Procedures for CD/DVD-ROMs Mounting the CD/DVD-ROM Manually Starting Products Start products in native mode (UNIX only) Understanding the sm_edit Utility The sm_edit utility Granting Windows UAC write permissions

5 PREFACE As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC technical support professional if a product does not function properly or does not function as described in this document. This document was accurate at publication time. Go to EMC Online Support ( to ensure that you are using the latest version of this document. Purpose Audience This document provides instructions for installing the EMC Smarts Application Connectivity Monitor product. Application Connectivity Monitor is distributed on a CD-ROM and is installed in the Application Connectivity Monitor subdirectory under the InCharge directory. This guide is intended for administrators and integrators responsible for installing the EMC Smarts Application Connectivity Monitor. EMC Smarts Application Connectivity Monitor documentation The following documents are relevant to users of Application Connectivity Monitor: EMC Smarts Application Connectivity Monitor Release Notes EMC Smarts Application Connectivity Monitor Installation Guide EMC Smarts Application Connectivity Monitor Configuration Guide EMC Smarts Application Connectivity Monitor User s Guide Related documentation The following EMC publications provide additional information: EMC Smarts Documentation Catalog EMC Smarts System Administration Guide EMC Smarts ICIM Reference EMC Smarts Common Information Model Infrastructure Models Chart EMC Smarts Common Information Model Application and Business Models Chart EMC Smarts ASL Reference Guide EMC Smarts Perl Reference Guide Preface 5

6 Preface EMC Smarts Dynamic Modeling Tutorial EMC Smarts MODEL Reference Guide Conventions used in this document EMC uses the following conventions for special notices: NOTICE is used to address practices not related to personal injury. Typographical conventions EMC uses the following type style conventions in this document: Bold Use for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks) Italic Use for full titles of publications referenced in text Monospace Use for: System output, such as an error message or script System code Pathnames, filenames, prompts, and syntax Commands and options Monospace italic Use for variables. Monospace bold Use for user input. [ ] Square brackets enclose optional values Vertical bar indicates alternate selections the bar means or { } Braces enclose content that the user must specify, such as x or y or z... Ellipses indicate nonessential information omitted from the example Where to get help Your comments EMC 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: 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. Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: techpubcomments@emc.com 6 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

7 CHAPTER 1 Overview This chapter consists of following topics: About Application Connectivity Monitor... 8 EMC Smarts product and version compatibility... 8 Installation... 8 Overview 7

8 Overview About Application Connectivity Monitor Application Connectivity Monitor is a software package that automatically discovers TCP-based applications on the network and monitors application connectivity to pinpoint the root cause of application availability problems. Application Connectivity Monitor operates in conjunction with: Availability Manager Availability Manager provides the network topology for Application Connectivity Monitor and identifies system outages or impact of network outages for Application Connectivity Monitor through the Smart Adapter to correlate with application outages. Service Assurance Manager Service Assurance Manager (SAM) collects the results of the deployment s root-cause analysis and presents the results to network operations personnel through its Global Console (Domain Manager). EMC Smarts product and version compatibility Application Connectivity Monitor is compatible with the versions of the products listed in the EMC Smarts Application Connectivity Monitor version 2.4 interoperability chart shown in Table 1 on page 8. Table 1 Interoperability chart Product Suite EMC Smarts Service Assurance Manager EMC Ionix IP Management Suite Version 8.1 Patch 3 or later 9.x.x 8.x.x 9.x.x Installation Table 2 on page 8 provides information about the software and hardware requirements, an overview of the installation tasks, and post-installation tasks. Table 2 EMC Smarts Application Connectivity Monitor installation requirements and tasks Tasks Go to Preinstallation Hardware and software requirements to install the suite. Requirements on page 11 Getting Started on page 16 Check the Broker configuration. Choose an operating mode for the installation program. Determine the location of the EMC Smarts Broker on page 16 Choose an operating mode for the installation program on page 19 8 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

9 Overview Table 2 EMC Smarts Application Connectivity Monitor installation requirements and tasks Tasks Go to Installation Insert the CD-ROM. Mounting the CD-ROM on page 19 Install using your chosen mode of operation: Wizard Mode CLI Mode Unattended (Silent) Mode Using wizard mode on page 20 Using CLI mode on page 23 Using unattended (silent) mode on page 24 Postinstallation Save your EMC Smarts evaluation license, smarts.lic, to the BASEDIR/smarts/local/conf directory. Edit the SM_LICENSE variable in the runcmd_env.sh file so that the variable specifies the full path name to the smarts.lic file. Obtain and install a temporary license file on page 32 Start Application Connectivity Monitor for the first time. Start EMC Smarts products on page 32 Verify the current state of the products and Broker. Install your permanent EMC Smarts license. Verify the EMC Smarts product status on page 34 EMC Ionix System Administration Guide Installation 9

10 Overview 10 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

11 CHAPTER 2 Requirements This chapter consists of following topics: Operating system requirements Hardware requirements Requirements 11

12 Requirements Operating system requirements EMC Smarts Application Connectivity Monitor supports the following operating systems: Red Hat Enterprise Linux AS 5 and 6 Solaris 9 and 10 Windows 2003 Enterprise Edition SP1, SP2, and R2 Windows 2008 Enterprise Edition Deprecated Platform support VMware ESX Server 3.5 and 4.0: Windows 2003 Enterprise Edition SP1, SP2 and R2 Window 2008 Enterprise Edition Red Hat Enterprise Linux AS 5 and 6 EMC Smarts Application Connectivity Monitor 2.4 is not supported on Red Hat Enterprise Linux AS 3 and 4, and Solaris 8. Hardware requirements The following tables lists the minimum hardware requirements for installing Application Connectivity Monitor. Table 3 Platform requirements Platform Platform hardware Solaris Sun Fire 280 Windows Red Hat Linux 2xPentium4, 2 GHz 2XPentium4, 2 GHz Table 4 Disk space Platform Solaris Windows Linux Disk space 350 MB 150 MB 245 MB Table 5 on page 13 lists minimum requirements for CPUs, memory, and data disk space used by the software for writeable files such as logs, repository files, and output files. CPU means the number of physical CPU cores; not the number of CPUs displayed when hyperthreading is activated. 12 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

13 Requirements If you are installing more than one product, your system must meet the products total memory and data disk space requirements (disk space (Table 4 on page 12), RAM, and data disk space for a product (Table 5 on page 13)). Table 5 CPU, memory, and data disk space requirements EMC Smarts product CPUs Memory (RAM) Data disk space Application Connectivity Monitor MB 100 MB each Hardware requirements 13

14 Requirements 14 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

15 CHAPTER 3 Installing Application Connectivity Monitor This chapter consists of following topics: Getting Started Installation The basic installation steps are the same for all supported platforms. 15

16 Getting Started This section explains the mandatory requirements for installing EMC Smarts Application Connectivity Monitor. See: Installation requirements on page 16 for an explanation of administrator access and JAVA JRE requirements. Installation requirements Determine the location of the EMC Smarts Broker on page 16. Choose an operating mode for the installation program on page 19. Before beginning, ensure that you have met the following requirements: Access requirement: 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 halts if the user does not have the appropriate privileges. Based on the operating mode of the installation program used when installing or upgrading the suite, there might be additional requirements. These requirements are included in the procedures for the specific modes. 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 your deployment planner or check the build guide that documents your deployment to determine the name of the host where the Broker was installed and the port that the Broker uses. If the location is the same host where you are installing this suite, then the installation program will automatically install the Broker if it is not already on the host. 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 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> 16 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

17 Based on the location of the Broker, go to the appropriate step, as indicated in Table 10 on page 25 Table 6 Next steps for detecting and stopping programs Location of Result Task Same host Different host Error attaching to Broker message List of servers registered with the Broker List of servers registered with the Broker The EMC Smarts Broker is not running. Go to Step 4. The Broker or service daemon did not shut down. If any servers are still running on the host, these did not shut down. Go to Step 3. 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 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. Do not stop or shutdown 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. 17

18 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. 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. Click 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. 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. 18 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

19 Choose an operating mode for the installation program Use one of the following modes supported by the installation program: Wizard mode is a Java-based Graphical User Interface (GUI). Command Line Interface (CLI) mode (UNIX only) is a text-based method intended to support systems with non-graphics consoles. Unattended (Silent) mode 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. 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 Windows System. Before starting the installation program using the Wizard mode, verify that the X Window System is running. Install EMC Smarts Application Connectivity Monitor This section describes how to install EMC Smarts Application Connectivity Monitor. On the Windows 2003 (Enterprise Edition) platforms, EMC Smarts products do not install correctly and EMC Smarts services do not start correctly when installed to a directory path containing spaces. Do not use spaces in the directory names used in BASEDIR. Mounting the CD-ROM Inserting the CD-ROM Mount the CD-ROM and change to the CD-ROM directory using established procedures for your environment. The procedure for mounting the CD-ROM differs based on the operating system. UNIX If necessary, see the appendix for typical commands and examples. Follow these steps to insert the CD-ROM: 1. Insert the CD-ROM into the CD-ROM drive. If autoplay is enabled, the installation program starts automatically using the Wizard mode. 2. If necessary, change the directory to the CD-ROM. Use Windows Explorer to access the CD-ROM drive and locate the /suite directory. 19

20 Installation To install, use the procedure for the installation program mode that you selected: For Wizard mode, go to Using wizard mode on page 20. For CLI mode, go to Using CLI mode on page 23. For Unattended (Silent) mode, go to Using unattended (silent) mode on page 24. Using wizard mode The content in the following section provides detailed information on using the Wizard mode to install Application Connectivity Monitor to a Windows or UNIX operating system. Satisfy Wizard mode requirements (UNIX only) Running Wizard Mode 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 Windows System. Before starting the installation program using the Wizard mode, verify that X Window System is running. Do the following to run in wizard mode: 1. Execute the Setup command from Table 7. The InstallShield Wizard dialog box appears and closes. The Shutdown Programs dialog box and the Welcome screen then appear. Table 7 Setup command Syntax for Wizard-Mode Operating system Linux Solaris Windows Execute setup-acm-2_4_0_0-linux-64.bin setup-acm-2_4_0_0-sol64.bin setup-acm-2_4_0_0-win64.exe If the installation program cannot find a suitable JVM (Java Virtual Machine), use the option -is:javahome <local_java_dir> to specify the path to where Java is installed. 2. If you have not already done so, find and stop the active EMC Smarts services. (However, for installations or uninstallations, do not stop the EMC Smarts service daemon process, sm_serviced.) Click OK in the Warning dialog box when you have stopped all EMC Smarts services. 3. Click Next in the Welcome screen to continue. Next is disabled if: You do not have administrative privileges for the products you are attempting to install. An error message also appears. 20 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

21 Your system failed the requirements check. If this occurs, review the check results by clicking Get System Information. Then, cancel the installation setup program, and upgrade your system. 4. Read and accept the EMC Corporation end user license agreement and click Next. 5. If the installation program detects an existing installation of the same suite, the Installation Type screen appears. Select Install the product to a new directory. 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) or C:\InCharge (on Windows). On the Windows 2003 (Enterprise Edition) platforms, EMC Smarts products do not install correctly and EMC Smarts services do not start correctly when installed to a directory path containing spaces. Do not use spaces in the directory names used in BASEDIR. If you specify a directory, use forward slashes ( / ) for both UNIX and Windows directories. A new directory is created if the specified directory does not exist. If you do not have write privileges, an error message appears. 7. In the Setup screen, select one of the options, then click Next: Complete to install the entire suite. Custom to install a specific product. In the Product Selection screen that follows, clear products that you do not wish to install (by default, all products are selected). Click Next. 8. If you selected Complete or Custom in step 7, select the type of Global Console installation. You can select the Global Console or Web Console and Business Dashboard. 9. The Services Selection screen appears. Select the products that you wish to install as services and click Next. If a product is not selectable (that is, displayed as dimmed text), click Back to return to the Product Selection screen and select the product. If installed as services, EMC Smarts products run when the system is running. If the system is stopped and restarted, the EMC Smarts products restart automatically. EMC Corporation recommends that EMC Smarts products be installed as services whenever possible. If any of the products being installed can be started as services, these products are displayed in the services selection screen. 10. Select a location to install an EMC Smarts Broker or specify the location of an existing broker. Click Next to continue. 21

22 11. If you are installing the Perl API, read and accept the EMC Corporation Perl API license agreement and click Next. 12. Review the list of products that will be installed and the target installation directory. At the end 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. After you have verified that you have adequate space, click Next. A screen displays for a short period of time, letting you know that a runtime patch is being installed. This does not require user intervention and takes only a few seconds. The Installation Progress screen appears. 13. After completion, the Installation Summary appears informational messages such as successful confirmations, error messages, and warnings. Click Finish to exit the installation. It is not necessary to restart the system after installation. Investigate any errors or warnings. The log file is a text file with the naming convention Install.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the installation process fails, the log files are located in the /tmp directory. 14. Remove the CD-ROM after completing the installation. Be sure that no processes are currently accessing the drive. Where to go next Verifying the Installation on page 31 provides all other post-installation steps. 22 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

23 Using CLI mode 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 Linux Solaris Executable setup-acm-2_4_0_0-linux-64.bin -console setup-acm-2_4_0_0-sol64.bin -console 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 pre-defined selections in menus. An X is used to indicate the selected item. When you are finished making selections, type zero (0) and press Enter. If you incorrectly type an entry, press 5 to repeat the prompt and select the correct value. Arrow keys and the Backspace key are not supported. To navigate between each step, use the keys specified in Table 9 on page 23. Table 9 Navigation keys Key Operation 1 Next, continue to the next step 2 Previous, go back to the previous step 3 Cancel, terminate the program 5 Redisplay, repeat the step 0 Accept the marked ([X]) menu choice Where to go next Verifying the Installation on page 31 provides the post-installation steps. 23

24 Using unattended (silent) mode Modifying the response file Unattended mode reads the commands and settings from a user-modifiable file (response file) that you create prior to beginning the process. Manual intervention is not necessary after you execute the setup command. Each suite has a response file located on the CD-ROM in the /utils directory. Its naming convention is <suite>-response.txt. The response file provides instructions and examples of command line options that are passed to the program in unattended mode. The command line options are organized by process flow. The process flow is almost identical to that of the Wizard mode. By default, the response file includes settings that support the installation of all products from the CD-ROM and configure the Broker location as localhost at port 426. You must edit the response file to change settings to: Support Windows operating systems Specify a different Broker location To modify the response file: 1. Copy the response file from the CD-ROM /utils directory to a directory on your system, for example, the /tmp directory. 2. Using a text editor, modify the values for the command line options in the response file: Specify the target directory. Select a directory for the process log file. Select the products to install. Ensure that the property value for the product is set to true. Select the products to start as services. Ensure that the property value for the product is set to true. Specify the location of the Broker. 3. Save the file. 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. 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. 24 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

25 Running unattended mode Run the Setup command from a command line shell. Table 10 Setup command syntax for unattended mode Operating system Linux Solaris Windows Executable./setup-ACM-2_4_0_0-linux-64.bin./setup-ACM-2_4_0_0-sol64.bin setup-acm-2_4_0_0-win64.exe For example, to start the unattended installation on Solaris for the EMC Smarts Application Connectivity Monitor when the response file is located in /opt/home, execute:./setup-acm-2_4_0_0-sol64.bin -options /opt/home/acm_suite-response.txt This command must be typed as one line. Separate each option with a space when typing the command. Checking the version number From BASEDIR/smarts/bin/, type the following command: sm_server --version The version is displayed in the following format: V<Number> <Date> <Build> Copyright <Date> EMC Corporation For Application Connectivity Monitor 2.4, it displays the following: ACM_SUITE: V /64(129216), 28-Nov :01:24 Copyright , EMC Corporation - Build 15 DMT V /64(128653), 05-Nov :36:31 Copyright , EMC Corporation - Build 1 Product versions vary and do not always match the software foundation version number. For example, if you select About from the Help menu in the Global Console, you may see a different number. The product version number, for example Application Connectivity Monitor 2.4, is displayed during installation on the InstallShield screen. Where to go next Verifying the Installation on page 31 provides post-installation steps. 25

26 26 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

27 CHAPTER 4 Migration This chapter consists of following topic: Migration Migration 27

28 Migration Migration Application Connectivity Monitor must be installed in a new base directory. The default base directory is /opt/incharge/acm. Migration from an earlier version of Application Connectivity Monitor 2.4 is not supported. However, you can copy a customized dxa conf file, which is used to import topology from the Smart Adapter Platform (OI), to the new installation without any change. This is recommended in cases where the customized dxa conf file is required. To preserve the RPS settings and customized application signatures from the previous version of ACM, you must copy the RPS files to the new installation. To migrate the RPS settings, 1. Copy the RPS settings from the previous version of ACM to the new installation. cp <ACM>.rps <BASEDIR>/ACM/smarts/local/repos/icf 2. Start the ACM server using --clean-topology to restore all the settings from the older installation../sm_server --name=<dm_name> --config=asm-ntier --port=0 --subscribe=default --ignore-restore-errors --output --clean-topology This command will restore the RPS settings and not the topology. You must run a full discovery to generate the topology. Donot use --clean-topology for subsequent restarts of ACM server, instead use the sm_service command. 3. Type the following command to restart the services:./sm_service install --force --unmanaged --startmode=runonce\ '--name=ic-acm-server' \ '--description=emc Ionix Application Connectivity Monitor Server'\ '/<BASEDIR>/smarts/bin/sm_server' \ '--name=ic-acm' \ '--config=asm-ntier' \ '--port=0' \ '--subscribe=default' \ '--ignore-restore-errors' \ '--output' You can also import customized application signatures from the previous version of ACM. The "Exporting and importing application signatures" section in the Application Connectivity Monitor Configuration Guide provides information on importing and exporting application signatures. 28 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

29 CHAPTER 5 Upgrade This chapter consists of following topic: Upgrade Upgrade 29

30 Upgrade Upgrade Application Connectivity Monitor version 2.4 does not support an upgrade from the previous version to the current version. 30 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

31 CHAPTER 6 Verifying the Installation This chapter consists of following topics: Obtain and install a temporary license file Start EMC Smarts products Starting services manually Verify the EMC Smarts product status Where to go next Verifying the Installation 31

32 Verifying the Installation Obtain and install a temporary license file Typically, EMC Corporation will a temporary license to you. Copy the license file, smarts.lic, to the BASEDIR/smarts/local/conf directory on the system where the EMC Smarts software is installed. If the evaluation license has a different name, rename it to smarts.lic: If multiple EMC Smarts product suites run on the same system, copy the license file to the BASEDIR/smarts/local/conf directory for each suite smarts.lic. If EMC Smarts product suites run on multiple systems, copy the license file to the BASEDIR/smarts/local/conf directory on each system where the software is installed. Edit the SM_LICENSE variable in runcmd_env.sh on each system where EMC Smarts software is installed so that it specifies the full path and filename of a single smarts.lic file. When multiple EMC Smarts product suites are installed on the same system, each suite will include a runcmd_env.sh in its BASEDIR/smarts/local/conf directory. Temporary licenses for EMC Smarts software are time-limited. At the end of the trial period, the software will no longer start. You can request an extension to your temporary license, or a permenant license by creating a service reuqest through Online Support at: The EMC Smarts System Administration Guide provides information on licensing or instructions for obtaining and installing a permanent license. Start EMC Smarts products EMC Smarts recommends installing managers and adapters as services. If you installed the products as services, you must start them for the first time. These services start automatically upon system reboot, but the following sections describe additional methods to start EMC Smarts services. If you did not install the products as services, you can install them now. Starting services manually Starting services on UNIX This section contains information on manually starting products as services. Verify the status of the service daemon before starting a service. Verifying the status of the service daemon Use the ic-serviced command to check the status of the service daemon. The path to the ic-serviced command varies by operating system. Solaris On Solaris systems, type the following command to verify the status of the service daemon: 32 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

33 Verifying the Installation /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 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. For example, to start the Application Connectivity Monitor service named ic-acm-server: BASEDIR/ACM/smarts/bin/sm_service start ic-acm-server Indicates that this command must be typed as one line. Separate each option with a space when typing the command. 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. Select Start from the menu. Start the Broker service first if it is not running. Starting services manually 33

34 Verifying the Installation Verify the EMC Smarts product status You can determine the current state of the products in the suite that register with the Broker by typing the following command from the BASEDIR/smarts/bin directory:./brcontrol This command displays a list of EMC Smarts Managers and adapters registered with the Broker, their states (RUNNING, DEAD, UNKNOWN), process IDs, port numbers, and the last time that their states changed. Also check any log files for the products. Typically, these log files are in BASEDIR/smarts/local/logs. Where to go next EMC Smarts products must be configured before they can perform useful analysis and provide information to operators. The Application Connectivity Monitor Configuration Guide provides instructions to continue deploying the EMC Smarts Application Connectivity Monitor. 34 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

35 CHAPTER 7 Uninstalling Application Connectivity Monitor This chapter consists of following topics: Before uninstallation Uninstall Application Connectivity Monitor After uninstalling Application Connectivity Monitor, your customized files remain saved in the BASEDIR/smarts/local directory. For UNIX only, when uninstalling EMC Smarts suites from the same server, the EMC Smarts suite that was installed first must be uninstalled last. During the installation of the first EMC Smarts suite, the EMC Smarts Service Database is also installed and the other suites subsequently access it. Uninstalling the suite installed first will also uninstall the Service Database which will disable the sm_service command for those products, prevent their proper operation and uninstallation, and interrupt products running as services. Perform this check by looking at the value of the SMHOME variable in /etc/init.d/ic-serviced (or /sbin/init.d/ic-serviced for HP-UX). The suite listed in SMHOME is the suite that should be uninstalled last. EMC Smarts product suites use standard installation software to install and uninstall product suites. You must use the uninstaller command for UNIX. For Windows, you must use the Add/Remove Programs to uninstall EMC Smarts software. Failure to use the appropriate method will result in an unstable system or inconsistent product directories. Do not manually delete the installed product directories. The uninstall process is not a rollback. It removes all product suite files, not simply files that changed as a result of a new product installation. If you need a full rollback procedure, contact EMC technical support. If you install additional services manually by selecting Custom from the Installation Type screen, you can only uninstall those services manually. They do not uninstall when you perfom a standard uninstallation. Uninstalling Application Connectivity Monitor 35

36 Uninstalling Application Connectivity Monitor Before uninstallation The following sections cover the tasks that must be done before uninstalling Application Connectivity Monitor and includes the following topics: Stopping active EMC Smarts programs (UNIX) on page 36 Stopping active EMC Smarts programs (Windows) on page 37 Uninstall the FLEXnet License Server on page 38 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 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 11 on page 36. Table 11 Steps for detecting and stopping programs Location of the Broker Result Task Same host Different host Error attaching to Broker message List of servers registered with the Broker List of servers registered with the Broker The EMC Smarts Broker is not running. Go to step 4. The Broker or service daemon did not shut down. If any servers are still running on the host, these did not shut down. Go to step 3. 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 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> 36 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

37 Uninstalling Application Connectivity Monitor 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. Do not stop or shutdown 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. 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 Smarts 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. Before uninstallation 37

38 Uninstalling Application Connectivity Monitor 11. Click 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. 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 and suites that use a specific FLEXnet License Server, you must also uninstall the FLEXnet License Server. If any EMC Smarts products will remain in your network and use the FLEXnet License Server, do not uninstall either the license server or the EMC Smarts product suite where the permanent license file resides. If you uninstall EMC Smarts products without uninstalling the FLEXnet License Server, a message appears that the FLEXnet (lmgrd) service is still running. Remember that an EMC Smarts application will not start if it is unable to contact the license server. To stop and uninstall the FLEXnet License Server: 1. Stop the FLEXnet License Server. Solaris: # /etc/init.d/smarts-license stop Linux: # /etc/init.d/smarts-license stop Windows: To manually start the license server on Windows, do the following as administrator: Select Start > Settings > Control Panel > Administrative Tools. Select Services. Select the FLEXnet License Server service. 38 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

39 Uninstalling Application Connectivity Monitor Right-click and select Stop. 2. Run the install_license script with the uninstall command from the BASEDIR/smarts/script directory. In UNIX, type: # BASEDIR/smarts/script>install_license.sh uninstall In Windows, type: BASEDIR\smarts\script>install_license.cmd uninstall Uninstall Application Connectivity Monitor Uninstall using Wizard mode The following section covers the uninstallation process for the following modes: Uninstall using Wizard mode on page 39 Uninstall using unattended mode on page 40 Uninstall from the Control Panel (Windows only) on page 41 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 the uninstaller program: For UNIX, type: BASEDIR/_uninst/uninstaller.bin For Windows, use Add/Remove Programs: a. Select Start > Settings > Control Panel. b. Double-click Add/Remove Programs. c. From the Add/Remove Programs window, select the appropriate service for your product suite. d. Click Change/Remove. 2. Click Next in the Welcome screen to continue. 3. In the Product Selection screen, click Next to uninstall the entire suite of products (by default, all products are selected) or clear products that should remain installed. 4. Review the list of products that will be uninstalled and the target installation directory. Once you click Next, you cannot cancel the uninstallation process. If necessary, click Back to return to the Product Selection screen to revise your selections. Uninstall Application Connectivity Monitor 39

40 Uninstalling Application Connectivity Monitor 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 appears, your system needs to be rebooted. Click it and then reboot your system. Otherwise, click Finish to exit the uninstallation. The log file is a text file with the naming convention Uninstall.<suite>.<productversionNumber>.log. It is located in the BASEDIR/smarts/setup/logs directory. If the uninstallation process fails, the log files are located in the /tmp directory. 6. Examine any remaining directories if you plan to re-install EMC Smarts and save customized files located in the /local directory. Depending upon the suite, some or all of the following subdirectories will remain in the BASEDIR/smarts directory after uninstallation because they contain user-modified files: /local /bin /setup Uninstall using unattended mode The unattended mode enables you to automate the removal of EMC Smarts product suites: 1. Invoke the uninstallation program with appropriate options for the operating system: On UNIX systems, use the uninstaller.bin program: BASEDIR/_uninst/uninstaller.bin -silent On Windows system, use the uninstaller.exe program: BASEDIR\_uninst\uninstaller.exe -silent Type each command as one line. 2. Examine any remaining directories if you plan to re-install the suite and save customized files located in the /local directory. Depending upon the suite, some or all of the following subdirectories will remain in the BASEDIR/smarts directory after uninstallation because they contain user-modified files: /local /bin /setup The log files from the uninstallation are located in the BASEDIR/smarts/setup/logs directory. If the uninstallation process fails, the log files are located in the /tmp directory. A non-zero status indicates a failure. 40 EMC Smarts Application Connectivity Monitor Version 2.4 Installation Guide

41 Uninstalling Application Connectivity Monitor Uninstall from the Control Panel (Windows only) If you have installed the same suite from two or more directories on your system, do not use Add/Remove Programs; use the uninstaller command instead. Add/Remove Programs does not support multiple instances of the same suite. To use the Windows Control Panel to uninstall a product suite, perform these steps: 1. Select Start > Settings > Control Panel. 2. Double-click Add/Remove Programs. 3. From the Add/Remove Programs window, select the appropriate service for your product suite. 4. Click Change/Remove. Uninstall Application Connectivity Monitor 41