Agent execution is controlled by the cron
daemon on each server. The main steps of a monitoring cycle are as follows.
/opt/SUNWstade/bin/rasagent
) should be running at any one time./var/opt/SUNWstade/DATA
. These reports are compared from one run of the agent to the next to generate health-related events. /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.Monitoring Devices Using Event Log
Aggregating Events Using Fault Signature Analysis
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.
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.