EMC P/N 300-002-867 manual A l y s i s S c e n a r i o s S t U n r e s p o n s i v e

Page 15

A n a l y s i s S c e n a r i o s

H o s t U n r e s p o n s i v e

An Unresponsive problem indicates that the system on which the application is running cannot be reached through the network.

To diagnose System Unresponsive in this scenario, Application Connectivity Monitor receives a host1.example.com UnresponsiveSymptom from IP Availability Manager. In addition, ACM may observe SlowSymptom or TimedOutSymptoms events in response to TCP checks.

Application Connectivity Monitor must receive an UnresponsiveSymptom from IP Availability Manager to diagnose an Unresponsive problem.

M a i l S e r v e r D e g r a d e d

A Degraded problem indicates that the application is not performing as expected. This means that the application is responding to TCP checks, but not within the expected time period.

To diagnose Degraded in this scenario, Application Connectivity Monitor observes a SlowSymptom event for a TCP check to SMTPService. A SlowSymptom event occurs when an application responds to the TCP check but the response time exceeds the threshold.

Figure 2 shows the Notification Properties dialog for the SMTPService Degraded problem. Application Connectivity Monitor diagnosed a Degraded problem with 100% certainty because it observed the SlowSymptom event in response to a TCP check.

EMC Smarts Application Connectivity Manager User’s Guide

5

Image 15

Contents USER’S Guide Application Connectivity MonitorLast Update 8/1/05 Contents Index ContentsDocument Organization PrefaceIntended Audience PrerequisitesDocumentation Conventions PrefaceDocumentation Conventions Application Connectivity Monitor Products Application Connectivity Monitor Installation DirectoryCommand Line Programs Additional ResourcesC S m a r t s D o c u m e n t a t i o n EMC PowerlinkTechnical Support Do cume nt at io nTe c h n i c a l S u p p o r t Preface Topology Created by ACM Explanation of Fault AnalysisL f u n c t i o n Faults Diagnosed by ACMExplanation of Fault Analysis W nSingle Application and Single TCP Check Analysis ScenariosApplication Monitored by One Check I l S e r v e r D o w n I l S e r v e r D e g r a d e d A l y s i s S c e n a r i o s S t U n r e s p o n s i v eSingle Application and Two TCP Checks Notification Properties Of Degraded ProblemApplication Monitored by Two Checks B S e r v e r D o w n A l y s i s S c e n a r i o sNotifications Properties Of Malfunction Problem B S e r v e r D e g r a d e d Two Applications on a Single SystemSMTPService HTTPService Host2.example.com Notification Properties Of Down Problem B S e r v e r D e g r a d e d Host Unresponsive Affects Applications Impact Analysis with Business Impact ManagerExplanation of Fault Analysis DNSServer Down Propagates to Business Elements Explanation of Fault Analysis Viewing Analysis Results and Application Topology Analysis Results Displayed as NotificationsAbout Notifications Viewing Analysis Results and Application Topology Viewing the Properties of a NotificationViewing Application Topology in Maps Opening an Applications MapP T e r m i n o l o g y Applications Hosted By System Topology Elements Displayed in an Application MapIndex Index