EMC P/N 300-002-867 manual Documentation Conventions, Preface

Page 6

Preface

Documentation Conventions

Several conventions may be used in this document as shown in Table 2.

Table 2: Documentation Conventions

CONVENTION	EXPLANATION

sample code	Indicates code fragments and examples in Courier font

keyword	Indicates commands, keywords, literals, and operators in bold

%	Indicates C shell prompt

#	Indicates C shell superuser prompt

<parameter>	Indicates a user-supplied value or a list of non-terminal items in
	angle brackets

[option]	Indicates optional terms in brackets

/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 (/). Users of the Windows operating systems should substitute back slashes (\) for forward slashes.

Also, if there are figures illustrating consoles in this document, they represent the consoles as they appear in Windows. Under UNIX, the consoles appear with slight differences. For example, in views that display items in a tree hierarchy such as the Topology Browser, a plus sign displays for Windows and an open circle displays for UNIX.

Finally, unless otherwise specified, the term InCharge Manager is used to refer to EMC Smarts programs such as Domain Managers, Global Managers, and adapters.

vi	EMC Smarts Application Connectivity Manager User’s Guide

Image 6

Contents Application Connectivity Monitor USER’S GuideLast Update 8/1/05 Contents Contents IndexPrerequisites PrefaceIntended Audience Document OrganizationDocumentation Conventions PrefaceDocumentation Conventions Additional Resources Application Connectivity Monitor Installation DirectoryCommand Line Programs Application Connectivity Monitor ProductsDo cume nt at io n EMC PowerlinkTechnical Support C S m a r t s D o c u m e n t a t i o nTe c h n i c a l S u p p o r t Preface Explanation of Fault Analysis Topology Created by ACMW n Faults Diagnosed by ACMExplanation of Fault Analysis L f u n c t i o nAnalysis Scenarios Single Application and Single TCP CheckApplication Monitored by One Check I l S e r v e r D o w n 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 I l S e r v e r D e g r a d e dNotification Properties Of Degraded Problem Single Application and Two TCP ChecksA l y s i s S c e n a r i o s Application Monitored by Two Checks B S e r v e r D o w nNotifications Properties Of Malfunction Problem Two Applications on a Single System B S e r v e r D e g r a d e dSMTPService HTTPService Host2.example.com Notification Properties Of Down Problem B S e r v e r D e g r a d e d Impact Analysis with Business Impact Manager Host Unresponsive Affects ApplicationsExplanation 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 the Properties of a Notification Viewing Analysis Results and Application TopologyViewing Application Topology in Maps Opening an Applications MapP T e r m i n o l o g y Topology Elements Displayed in an Application Map Applications Hosted By SystemIndex Index