Application Connectivity Monitor 2.0 CONFIGURATION GUIDE P/N 300-002-868 REV A01 OL-8950-01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.
Copyright 1996-2005 by EMC Corporation (“EMC”). All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The Software and all intellectual property rights related thereto constitute trade secrets and proprietary data of EMC and any third party from whom EMC has received marketing rights, and nothing herein shall be construed to convey any title or ownership rights to you.
Contents 1 2 Preface vii Purpose Intended Audience Prerequisites Document Organization Documentation Conventions Application Connectivity Monitor Installation Directory Application Connectivity Monitor Products Additional Resources Command Line Programs Documentation Technical Support EMC Powerlink vii vii vii viii viii ix x x x x xi xi Introduction 1 About Application Connectivity Monitor Managing Applications with Application Connectivity Monitor Define the Application Discover the Software Infra
Contents Firewall Deployment Considerations Installing the Software License Reminder Integrating Application Connectivity Monitor Availability Manager Adapter Platform ACM Domain Manager Global Manager Starting and Stopping the Components Manually Validating Your Integration Modifying Files With the sm_edit Utility 3 Creating and Configuring Application Signatures Using the Application Signature Configuration Interface Creating Application Signatures Modifying Application Signatures Deleting Application
A Working With Groups and Settings Opening the Polling and Thresholds Console Layout of the Polling and Thresholds Console Polling and Thresholds Console Toolbar Buttons How Managed Elements Are Assigned to Groups Modifying the Properties of a Group Method for Adding or Removing Settings Method for Modifying the Priority of Groups Method for Editing Matching Criteria Method for Modifying the Parameters of a Setting Creating New Groups 35 35 36 37 38 38 39 39 39 40 41 Wildcards Used By EMC Smarts Software
Contents vi EMC Smarts Application Connectivity Monitor Configuration Guide
Preface Purpose This document provides an overview of important features in EMC Smarts Application Connectivity Monitor, and instructions for configuring Application Connectivity Monitor. Intended Audience This guide is intended for administrators and integrators who are responsible for deploying and configuring Application Connectivity Monitor. Prerequisites This guide assumes you have the administrative privileges and the necessary experience to properly deploy and configure network management software.
Preface Document Organization This guide consists of the following chapters. Table 1: Document Organization CHAPTER/APPENDIX DESCRIPTION 1. INTRODUCTION Provides an overview of the important features of Application Connectivity Monitor that should be configured. 2. DEPLOYING APPLICATION CONNECTIVITY MONITOR Discusses how to deploy Application Connectivity Monitor. 3. CREATING AND CONFIGURING APPLICATION SIGNATURES Details how to create and configure application signatures. 4.
Application Connectivity Monitor Installation Directory Table 2: Documentation Conventions (continued) CONVENTION EXPLANATION /InCharge Indicates directory path names in italics yourDomain Indicates a user-specific or user-supplied value in bold, italics File > Open Indicates a menu path in italics ▼▲ Indicates a command is wrapped over one or more lines. The command must be typed as one line. Directory path names are shown with forward slashes (/).
Preface Optionally, you can specify the root of BASEDIR to be something other than /opt/InCharge6 (on UNIX) or C:\InCharge6 (on Windows), but you cannot change the location under the root directory. For more information about the software directory structure, refer to the EMC Smarts System Administration Guide.
Te c h n i c a l S u p p o r t • EMC Smarts Application Connectivity Monitor Installation Guide • EMC Smarts Application Connectivity Monitor Configuration Guide • EMC Smarts Application Connectivity Monitor User’s Guide Technical Support For questions about technical support, call your local sales office or service provider. For service, call one of the following numbers: United States: 800.782.4362 (SVC.4EMC) Canada: 800.543.4782 (543.4SVC) Worldwide: 508.497.
Preface xii EMC Smarts Application Connectivity Monitor Configuration Guide
1 Introduction This chapter provides a brief overview of important features in EMC Smarts Application Connectivity Monitor. It includes the following sections: • About Application Connectivity Monitor • Managing Applications with Application Connectivity Monitor • Application Signature Configuration Interface See Creating and Configuring Application Signatures on page 17 for detailed information about using the Application Signature Configuration Interface.
Introduction Application Connectivity Monitor operates in conjunction with Availability Manager and Service Assurance Manager. Availability Manager provides the network topology for Application Connectivity Monitor. Service Assurance Manager collects the results of the deployment’s root-cause analysis, and presents those results to network operations personnel through its Global Console.
Application Signature Configuration Interface D i s c o ve r t h e S o f t w a r e I n f ra st r u c t u r e Perform an initial discovery of network topology with Availability Manager and import the topology and connectivity analysis into Application Connectivity Monitor. Then, use Application Connectivity Monitor to discover the software infrastructure. • The application signatures automate the process of discovering the topology and the relationships between the elements.
Introduction A p p li c a t i o n S i g n a tu re s Conceptually, applications have characteristics or attributes that uniquely differentiate one application from another; together, these characteristics constitute a signature for a given application. Using the mechanism of Application signatures, we can then further qualify an application to reference particular instances of that application.
2 Deploying Application Connectivity Monitor This chapter describes how to deploy Application Connectivity Monitor, and includes the following sections: • Planning the Deployment • License Reminder • Integrating Application Connectivity Monitor Planning the Deployment As you prepare to deploy Application Connectivity Monitor, you should gather and document information about your network infrastructure and the applications that depend on that infrastructure.
Deploying Application Connectivity Monitor P r i v i le g e s R eq u i r em e n t If you are integrating Application Connectivity Monitor, you must either: • Be a superuser (User ID 0) on UNIX platforms. • Have administrative privileges on Windows platforms. S u p p o r t e d P r o d u c t V e r s i o n s a n d R e q u i r e m en t s Application Connectivity Monitor requires: • EMC Smarts Application Connectivity Monitor. Components: ACM Domain Manager. • Service Assurance Management Suite 6.
License Reminder • EMC Smarts Service Assurance Management Suite Installation Guide • EMC Smarts IP Management Suite Installation Guide If Service Assurance Management Suite 6.2 is installed, you will need to install SmartPack 2. Apply SmartPack 2 to Service Assurance before configuring communications between Service Assurance and Application Connectivity Monitor. See the EMC Smarts SmartPack Read Me First document that came with your software for additional information.
Deploying Application Connectivity Monitor Whenever you modify a configuration file, you must stop and restart the component for the changes to take effect. For a Global Manager, you can reload the configuration file while it is still running. For information about the sm_edit utility, see Modifying Files With the sm_edit Utility on page 14. Global Console Administrator Role Operator Monitoring Role Topology and Events Service Assurance Manager (Global Manager) dxa-sam-from-acm.
Integrating Application Connectivity Monitor • Adapter Platform to the ACM Domain Manager, no changes are necessary in the Adapter Platform’s configuration file. To receive events and topology from an underlying source, you need to uncomment DomainType entries in the Adapter Platform’s configuration file, icoi.conf. At minimum, you need to uncomment the entry for Availability Manager. In addition, you need to comment out the entry for Availability Manager that uses the dxa-sysip.conf file.
Deploying Application Connectivity Monitor For more information about the Adapter Platform, see the EMC Smarts Service Assurance Manager Adapter Platform User’s Guide. For more information about DomainType entries and configuring settings for system defaults, see the EMC Smarts Service Assurance Manager Configuration Guide. A C M D o m a in M a n ag e r ACM Domain Manager discovers and monitors applications. • It receives topology from the Standard Probe.
Integrating Application Connectivity Monitor 5 In the Add Source dialog, select "Adapter Platform" and enter the name of the Adapter Platform server that is being used (for example, IC-OI) in the element name field. Click OK. Global Manager To receive events and topology from an underlying source, you must modify the Global Manager’s configuration file, ics.conf.
Deploying Application Connectivity Monitor ## # ## # ## DomainType { ConfFile MinimumCertainty SmoothingInterval HookScript = Name } = "dxa-perf.conf"; = 0.24; = 65; "ics/dxa-sample-hook.asl"; = "INCHARGE-PM"; DomainType definition for INCHARGE-OI. DomainType { ConfFile = "dxa-oi.conf"; MinimumCertainty = 0.24; SmoothingInterval = 65; HookScript = "ics/dxa-sample-nl-hook.asl"; Name = "INCHARGE-OI"; } DomainType definition for INCHARGE-ACM. DomainType { ConfFile = "dxa-sam-from-acm.
Integrating Application Connectivity Monitor S t a r t i n g a n d S to p p i n g t h e C o m p o n e n t s M a n u a l l y Note: To use the sm_service utility to start a service or install a service, you must have root or administrative privileges on the local host. Services for Application Connectivity Monitor run automatically after your system reboots. If, for any reason, you need to start or stop a service manually, use the sm_service utility.
Deploying Application Connectivity Monitor ▼▲ Indicates the command must be typed as one line. V a l i d a ti n g Y o u r I n te g r a t i o n To verify the integration of your ACM Domain Manager, perform these tasks: • Use a text editor to review the ACM Domain Manager’s log file. The log file is located on the host running the component in the BASEDIR/smarts/local/logs directory. A common log error is “cannot access” for improper access between components.
Integrating Application Connectivity Monitor Original versions of files should not be altered. If a file requires modification, it must be stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories. For example, a modified ics.conf file should be saved to /opt/InCharge6/SAM/smarts/local/conf/ics. EMC Smarts software is designed to first search for user modifiable files in BASEDIR/smarts/local or one of its subdirectories.
Deploying Application Connectivity Monitor 16 EMC Smarts Application Connectivity Monitor Configuration Guide
3 Creating and Configuring Application Signatures The Application Signature Configuration Interface that is included with Application Connectivity Monitor enables administrators and integrators to create and configure application signatures. Application Connectivity Monitor uses the signatures to discover and monitor applications in the managed topology.
Creating and Configuring Application Signatures The tab enables administrators and integrators to access the Application Signature Configuration Interface through which they can enable and configure application signatures. Signatures can also be deleted, when necessary. To access the Application Signature Configuration Interface, perform the following steps. 1 From the Global Console, select Configure > Domain Manager Administration Console.
Using the Application Signature Configuration Interface The table at the top of the tab (see Figure 2) shows the list of application signatures that are available in the ACM Domain Manager. Each row in the table corresponds to an application signature and each column in the row corresponds to a field in the application signature. Enabled signatures (those already deployed) appear in normal font; disabled signatures appear in grayed italic font.
Creating and Configuring Application Signatures The application signature is created in the ACM Domain Manager and is enabled. It is then used to discover the application: • When discovery is manually invoked with Discover All • When the next discovery cycle is initiated • When a new system is added to the topology of the ACM Domain Manager Enabled Autodetect application signatures can be launched on demand for a given system.
Using the Application Signature Configuration Interface Table 4: Application Signature Fields (continued) FIELD NAME DESCRIPTION REQUIRED/OPTIONAL Port Number The port number on which the application should be actively listening. The same port number can be used for multiple signatures. However, when the same port is used for multiple signatures, the request strings and response patterns must be mutually exclusive.
Creating and Configuring Application Signatures Table 4: Application Signature Fields (continued) FIELD NAME DESCRIPTION REQUIRED/OPTIONAL Monitoring Action The monitoring action to be used to monitor the discovered application. The default is tcpAction. The values for parameters in the monitoring action can be specified by clicking the Customize… button. See Specifying Monitoring Action Parameters on page 24 for additional information.
Using the Application Signature Configuration Interface M o d i f yi n g A p p l i c a ti o n S i g n a tu r e s The Application Signature tab is also used for modifying an existing application signature. The table at the top of the Application Signature tab will show a list of application signatures registered in the server. Each row in the table corresponds to an application signature. To modify an existing application signature, perform the following steps.
Creating and Configuring Application Signatures 4 The Application Signature Configuration Interface displays a warning message to make sure that you want to delete the selected application signature. Click Yes to delete the signature. Specifying Monitoring Action Parameters Monitoring actions are scripts or programs that are associated with application signatures: one per signature. The actions monitor the availability and health of applications.
Specifying System Name Patterns To specify the parameters for a Monitoring Action, perform the following steps. 1 Access the Application Signature tab. 2 Enter a new application signature or select an existing signature from the list at the top of the tab. 3 At the Monitoring Action field, select the tcpAction. 4 Click the Customize… button to display the parameters. 5 Enter values for the parameters as necessary. The parameters marked in red are required.
Creating and Configuring Application Signatures Figure 4: Customize System Match Patterns Note: If you do not specify patterns, the default for System Name Pattern is “*”. This means that the system will apply the application signature on all systems added to the ACM Domain Manager’s topology. U s e A l l S y s te m s M a tc h ed b y Pa tt e rn To use this option: 26 1 Specify the System names pattern and click the Apply button. (The example in the figure shows the System names pattern default “*”.
The Standard Discovery Probe U s e O n l y S e l ec te d S ys t em s To use this option: 1 Specify the System names pattern(s) and click the Apply button. (The example in the figure shows the System names pattern default “*”.) For additional information about matching patterns and the use of wildcard characters in patterns, see Wildcards Used By EMC Smarts Software on page 43. 2 Select Use on selected systems.
Creating and Configuring Application Signatures The Standard Probe creates basic topology for: • The Software Service object (represents the discovered application). • The TCP endpoint through which the Software Service can be accessed. • A Software Element Check object that is instrumented with a specified monitoring action (tcpAction). The Standard Probe also creates the following relationships: • Creates “Accessed Via” relationship with the target class instance for the TCP Endpoint Instance.
R e m o v i n g To p o l o g y E l e m e n t s • port: the port number of the server. For autodetect signatures, this can be left blank. The information is taken from the detection information. If you explicitly provide this parameter in the dialog, the entered value overrides the default one (the detection port). • requestString: the request string to send to the server. • matchPattern: the pattern against which the server response is to be matched. • timeout: the timeout for the action in milliseconds.
Creating and Configuring Application Signatures S ce n a ri o s f o r R e m o v i n g El e m e n ts The following provide some scenarios for the removal of topology elements. • A software service that was previously discovered is no longer of concern or interest. • Change the application signature for the software service. • Right click on the service and select Delete. • Use DiscoverAll and verify that the software service object is not redetected. • A system is removed from Availability Manager.
4 Groups and Settings A setting is a collection of parameters common to a particular type of analysis (for example, Oracle Database). A component called a group contains zero or more settings and is related to managed elements in your network based on matching criteria. Each member of a group is configured according to parameters defined in the group’s settings. In this way, different threshold values can be applied to different groups of devices.
Groups and Settings Threshold Groups Application Connectivity Monitor provides the following threshold groups: • Software Service Groups Software Service Groups The Software Service Groups applies settings to all elements of the SoftwareService class except elements of the InChargeService class. Table 5 describes the Software Service Groups included with Application Connectivity Monitor.
Default Threshold Groups and Settings Table 6: Parameters for Software Service Thresholds PARAMETER UNIT OR TYPE DESCRIPTION Check_MaxResponseTime Seconds The maximum response time for a check. The actual response time for a check is compared against this threshold to determine if the check is running slow. Check_Sensitivity Percentage (%) The percentage of samples during a set time period (StatisticsWindow) that must violate the Check_MaxResponseTime threshold to trigger an event.
Groups and Settings Default Polling Groups and Settings This section describes the default polling groups included with Application Connectivity Monitor and the settings that can be applied to each polling group.
Wo r k i n g W i t h G r o u p s a n d S e t t i n g s Working With Groups and Settings The configuration of a Domain Manager applies parameters to defined sets of managed elements. • A group is composed of settings and members. • A setting is composed of one or more related parameters. • A member is an element of the managed topology that belongs to a group. Using the Polling and Thresholds Console, you can perform the following configuration tasks: • Modify the properties of existing groups.
Groups and Settings To open the Polling and Thresholds Console, follow these steps: 1 Attach to the Domain Manager with the Global Console. The Topology Browser Console opens. 2 In the Topology Browser Console, select Configure > Domain Manager Administration Console. The Domain Manager Administration Console Console opens. 3 In the Domain Manager Administration Console, select Edit > Polling and Thresholds. The Polling and Thresholds Console opens.
Wo r k i n g W i t h G r o u p s a n d S e t t i n g s Figure 5: Polling and Thresholds Console—Example P o l li n g a n d T h r e sh o l d s C o n s o l e T o o l b a r B u t to n s The toolbar of the Polling and Thresholds Console provides quick access to the commands described in Table 9.
Groups and Settings Table 9: Polling and Thresholds Console Toolbar Buttons BUTTON DESCRIPTION Reconfigure polling and thresholds groups Delete selected item H o w M a n a g e d E l e m e n t s A r e A s si g n e d t o G r o u p s When a Domain Manager performs discovery, it automatically assigns each managed element to a group based on: • Matching criteria defined for the group • Priority of the group, which determines membership when an element meets the matching criteria for more than one group A ma
Wo r k i n g W i t h G r o u p s a n d S e t t i n g s M e th o d f o r A d d i n g o r R e m o v i n g S et ti n g s A group’s settings determine what parameters are applied to the managed elements that are members of the group. The Settings tab is divided into two sections: Current Settings and Available Settings. The Current Settings section lists the settings that are applied to the group. The Available Settings section lists additional available settings.
Groups and Settings • Value is any combination of text, integers, and wildcards that is matched against the value of the attribute in the managed element. The Value field for a matching criterion is not case-sensitive. If the value of a managed element’s attribute matches a matching criterion, the managed element is eligible to become a member of the group. When more than one matching criterion is specified, a managed element must match all criteria to become a member of the group.
Wo r k i n g W i t h G r o u p s a n d S e t t i n g s Changing the Parameters of a Setting 1 Select the setting in the left panel of the Polling and Thresholds Console. The parameters of a setting are listed in the right panel of the console. 2 Change the value of a parameter using one of the following methods: For a drop-down menu, click the menu and select a value.
Groups and Settings Copying an Existing Group 1 Right-click the Polling or Threshold group that you want to copy. 2 Select Copy from the pop-up menu to display the Copy Group dialog. 3 In the dialog, type a name and an optional description for the new group and click OK. The new group contains the same settings and thresholds as the group you copied. 4 Edit the settings, matching criteria, and priority of the new group. Change the value of any thresholds or parameters as necessary.
A Wildcards Used By EMC Smarts Software This appendix describes the wildcards used by EMC Smarts software. The wildcards can be used for pattern matching in noted instances. A wildcard pattern is a series of characters that are matched against incoming character strings. You can use these patterns when you define pattern matching criteria. Matching is done strictly from left to right, one character or basic wildcard pattern at a time. Basic wildcard patterns are defined in Table 10.
Wildcards Used By EMC Smarts Software Note: Spaces are interpreted as characters and are subject to matching even if they are adjacent to operators like "&". Table 10: Basic Wildcard Patterns CHARACTER DESCRIPTION Note: Spaces specified before or after wildcard operators are interpreted as characters and are subject to matching. 44 ? Matches any single character. For example, server?.smarts.com matches server3.smarts.com and serverB.smarts.com, but not server10.smarts.com.
Special characters for compound wildcard patterns are summarized below. Table 11: Compound Wildcard Patterns CHARACTER DESCRIPTION & “And Also” for a compound wildcard pattern. If a component basic wildcard pattern is preceded by & (or is the first basic wildcard pattern in the compound wildcard pattern), it must successfully match. Example: *NY*&*Router* matches all strings which contain NY and also contain Router. Example: <1-100>&*[02468] matches even numbers between 1 and 100 inclusive.
Wildcards Used By EMC Smarts Software 46 EMC Smarts Application Connectivity Monitor Configuration Guide
Index A D Adapter Platform Add to topology 10 DomainType Entries 9 Adding or removing a setting 39 Adding or removing matching criteria 40 Application Connectivity Monitor About 1 Integrating 7 Managing Applications with 2 Application Signature Configuration Interface 3, 17 Application Signatures 4 Monitoring Actions 4 Using 17 Application Signature tab 17 Application signatures 4, 19 Application Name Prefix 21 Class 21 Creating 19 Deleting 23 disabled 19 discovery 20 Enable 20 enabled 19 Modifying 23 Mon
Index Global Manager 11 Validating Your Integration 14 IP Management Suite 6 J Java Runtime Environment 6 L License Reminder 7 M Managing Applications Automated Root-Cause and Impact Analysis 3 Define the Application 2 Discover the Software Infrastructure 3 Managing Applications with Application Connectivity Monitor 2 Matching Pattern 43 Matching criteria Adding or removing 40 Changing 40 Modifying Application Signatures 23 Monitoring Actions 4, 24 O Operator Wildcard 44 P Pattern 43 Pattern matching
W Wildcard 43 Chart of operators 44 Window Interaction with Sensitivity and Thresholds 33 EMC Smarts Application Connectivity Monitor Configuration Guide 49
Index 50 EMC Smarts Application Connectivity Monitor Configuration Guide
