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.
Topology
and
Events
Availability
Manager
Global
Console
Administrator
Role
Operator Monitoring Role
Service Assurance
Manager
(Global Manager)
Topology
and Events
|
|
|
|
|
|
|
Unitary Computer |
|
|
|
| SAM Adapter |
|
System |
|
|
|
|
| |
| dxa- | Platform |
| |||
Topology |
|
| ||||
| am.conf | Aggregate |
| |||
|
| |||||
and |
|
|
|
|
| |
|
|
|
| Notifications |
| |
UCS:UnresponsiveSymptom |
|
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
|
|
Unitary
Computer System
Topology and
Notifications
Application
Connectivity Monitor
Figure 1: Application Connectivity Monitor Architecture and Integration
Availability Manager
To transfer (export) events and topology from Availability Manager to either the Global Manager or the Adapter Platform, no configuration changes are necessary for Availability Manager.
Availability Manager must be installed and functional. The Domain Manager is used to perform discovery.
Adapter Platform
To transfer notifications and topology from:
•Adapter Platform to the Global Manager, no configuration changes are necessary in the Adapter Platform’s configuration file.
8 | EMC Smarts Application Connectivity Monitor Configuration Guide |