## About Monitoring Strategy

The following procedure is a typical strategy for monitoring.

1. Monitor the devices.
   To get a broad view of the problem, the site administrator or Sun personnel can review reported information in context. This can be done by:
   - Displaying the device itself
   - Displaying the topology
   - Analyzing the device's event log
2. Isolate the problem.
   For many alarms, information regarding the probable cause and recommended action can be accessed from the alarm view. In most cases, this information enables you to isolate the source of the problem. In cases where the problem is still undetermined, diagnostic tests are necessary.
   You can initiate diagnostics from the command-line interface (CLI) or from the browser interface. From the browser interface, you can execute tests remotely using the slave agents. This feature enables the user to start and control tests from one centralized GUI on the master server, even when the actual diagnostic test is running on a slave server.
   Once the problem is fixed, you can clear the alarms for the device.

### Related Topics

- About the Monitoring Cycle
- About the Event Life-Cycle