## Monitoring Cycle:

Agent execution is controlled by the `cron` daemon on each server. The main steps of a monitoring cycle are as follows.

1. Verify that the agent is alone. If the previous run of the agent has not finished, allow it to finish. Only one instance of the monitoring agent (`/opt/SUNWstade/bin/rasagent`) should be running at any one time.
2. Load and execute all appropriate device modules used to generate instrumentation reports and generate health-related events.
   Instrumentation reports are generated by probing the device for all relevant information and saving this information in a report stored in `/var/opt/SUNWstade/DATA`. These reports are compared from one run of the agent to the next to generate health-related events.
   Events are also created by relaying information found in logfiles. For example, all errors and warnings found in`/var/adm/messages.t3` will be translated into a Log Event event without further analysis. Most events are generated because a rule or policy in the software concluded that a problem exists, but if the storage array indicates issues in the `syslog` file, an event is immediately generated.

### Related Topics

Monitoring Devices Using Event Log

1. Send these events to the master agent, if the events were generated by a slave. Or, send the events to all interested parties if the agent is the master agent. The master agent is responsible for generating its own events and collecting events from the slaves. Events can also be aggregated on the master before dissemination.

### Related Topics

Aggregating Events Using Fault Signature Analysis

1. Store Instrumentation reports for future comparison.

Event logs are accessible from the GUI under Monitor->Logs. The Storage Automated Diagnostic Environment software updates the state database with the necessary statistics. Some events require that a certain threshold be attained before an event is generated. For example, having the CRC count of a switch port going up by one is not sufficient to trigger an event, since a certain threshold is required.

The Storage Automated Diagnostic Environment supports email thresholds that can be used to prevent the generation of multiple emails about the same component of the same device. By keeping track of how many events were already sent in a specified timeframe, redundant email alerts can be prevented. Other Providers (non-Email) do not support this feature.

2. Send the events and/or alarms to the interested parties.

Events are sent only to those recipients that have been set up for notification. The types of events can be filtered, so that only pertinent events are sent to individuals.
Note: The Email provider and the Sun Network Storage Command Center (NSCC, by way of the Net Connect Provider) receives notification of all events.

### Related Topics

- Local Notification (Email/Scripts)
- Add an Email or Pager Notification Address
- Creating a Customized Event Filter