Scenarios for Removing Elements | EMC OL-8950-01 specification

Creating and Configuring Application Signatures

Scenarios for Removing Elements

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

•A system is removed from Availability Manager.

•All auto-detected software service objects and their related topology are removed.

•A system is in the topology of Availability Manager, but it is no longer of interest in Application Connectivity Monitor. All software services need to be removed from it.

•Change the associated application signatures to exclude the system from all future discoveries.

•Right click each software service object for the system and select Delete.

When you change the Application Class parameter of an application signature, and invoke DiscoverAll, and a new application is discovered by that signature, the originally discovered application will be removed and the newly discovered application will be created.

For example: A host, flyer, hosts a WebServer application that was discovered by the "AS_WebServer" application signature on port 80.

If you change the signature to specify a different application class (for instance, TelnetService) and then invoke DiscoverAll, the original WebServer application will be removed and a new Software Service of the class TelnetService is created.

This occurs only if, after changing the signature, a new application is discovered. If you change the signature and a new application is not discovered by DiscoverAll, the originally discovered application remains in the topology.

30	EMC Smarts Application Connectivity Monitor Configuration Guide

Image 42

EMC OL-8950-01 manual Scenarios for Removing Elements

Contents

Configuration Guide Application Connectivity Monitor Last Update 7/29/05 Contents Creating and Configuring Application Signatures Groups and SettingsContents Wildcards Used By EMC Smarts Software Index Contents Intended Audience PrefacePurpose Prerequisites Preface Document OrganizationDocumentation Conventions Document Organization Application Connectivity Monitor Installation Directory YourDomain Application Connectivity Monitor Products Command Line ProgramsAdditional Resources Documentation EMC Powerlink Technical SupportTe c h n i c a l S u p p o r t Xii Introduction About Application Connectivity Monitor Managing Applications with Application Connectivity Monitor Define the ApplicationIntroduction Application Signature Configuration Interface Discover the Software InfrastructureAutomated Root- Cause and Impact Analysis Application Signatures Monitoring Actions Deploying Application Connectivity Monitor Planning the Deployment Supported Product Versions and Requirements Installing the SoftwarePrivileges Requirement Firewall Deployment Considerations License Reminder Integrating Application Connectivity MonitorC e n s e R e m i n d e r Availability Manager Adapter Platform A m p l e o f D o m a i n T y p e E n t r i e s = INCHARGE-AM ACM Domain Manager Global Manager A m p l e s o f D o m a i n T y p e E n t r i e s C o n f i g u r i n g t h e G l o b a l M a n a g e r INCHARGE-PM Summary of EMC Smarts Service Names Fault P a r a m e t e r s f o r S e r v i c e sStarting and Stopping the Components Manually Validating Your Integration Modifying Files With the smedit Utility # /opt/InCharge6/SAM/smarts/bin/smedit conf/ics/ics.conf Deploying Application Connectivity Monitor Creating and Configuring Application Signatures Using the Application Signature Configuration Interface Creating and Configuring Application Signatures Application Signature Tab Creating Application Signatures Application Signature Fields Used By EMC Smarts Software on page 43 for Port Number 25 for Smtp Request No Value Response No Value Modifying Application Signatures Deleting Application Signatures Specifying Monitoring Action Parameters Monitoring Action Dialog Specifying System Name Patterns E c i f y i n g S y s t e m N a m e P a t t e r n s Use All Systems Matched by Pattern Customize System Match Patterns Standard Discovery Probe Use Only Selected SystemsE S t a n d a r d D i s c o v e r y P r o b e Standard tcpAction Page Scenarios for Removing Elements Groups and Settings Default Threshold Groups and Settings Threshold Settings Threshold Groups Fault T h r e s h o l d G r o u p s a n d S e t t i n g s Parameters for Software Service Thresholds Default Polling Groups and Settings Polling SettingsPolling Groups Working With Groups and Settings Opening the Polling and Thresholds ConsoleWo r k i n g Wi t h G r o u p s a n d S e t t i n g s Layout of the Polling and Thresholds Console Provides an example of a Polling and Thresholds Console Polling and Thresholds Console Toolbar Buttons Polling and Thresholds Console Toolbar Buttons How Managed Elements Are Assigned to Groups Modifying the Properties of a Group Method for Editing Matching Criteria Method for Adding or Removing SettingsMethod for Modifying the Priority of Groups D i n g o r R e m o v i n g a S e t t i n g Method for Modifying the Parameters of a Setting D i n g o r R e m o v i n g M a t c h i n g C r i t e r i a Creating New Groups Groups and Settings P y i n g a n E x i s t i n g G r o u p E a t i n g a n E m p t y G r o u p Wildcards Used By EMC Smarts Software Server-.smarts.com Compound Wildcard Patterns Example 1-100&*02468 matches even numbers between 1 Wildcards Used By EMC Smarts Software Index Index Page Index