C H A P T E R  6

Feedback Setting Up Array Monitoring

This chapter provides an overview of the array monitoring features. It contains the following sections:


Setting Up Notification for Fault Management

The fault management features of Sun Storage Common Array Manager enables you to monitor and diagnose your arrays and storage environment. Alarm notification can be provided by:

You can also set up Auto Service Request as described in Activating Auto Service Request.

1. In the navigation pane, under General Configuration, choose Notification.

The Notification Setup page is displayed:

2. Enable local email.

a. Enter the name of the SMTP server.

If the host running this software has the sendmail daemon running, you can accept the default server, localhost, or the name of this host in the required field.

b. Specify the other optional parameters, as desired.

c. If you have changed or entered any parameters, click Save.

d. (Optional) Click Test Local Email to test your local email setup by sending a test email.

If you need help on any of the fields, click the Help button.

3. Set up local email notification recipients.

a. Click Administration > Notification > Email.

The Email Notification page is displayed.

b. Click New.

The Add Email Notification page is displayed.

c. Enter an email address for local notification. At least one address is required to begin monitoring events. You can customize emails to specific severity, event type, or product type.

d. Click Save.

4. (Optional) Set up remote notifications by SNMP traps to an enterprise management application.

a. Select SNMP as the provider.

b. Click Save.

5. Perform optional fault management setup tasks:


Configuring Array Health Monitoring

To enable array health monitoring, you must configure the Fault Management Service (FMS) agent, which probes devices. Events are generated with content, such as probable cause and recommended action, to help facilitate isolation to a single field-replaceable unit (FRU).

You must also enable array health monitoring for each array you want monitored.

Configuring the FMS Agent

1. In the navigation pane, expand General Configuration, and select General Health Monitoring.

2. From the General Health Monitoring Setup page, select the types of arrays that you want to monitor from the Categories to Monitor field. Use the shift key to select more than one array type.

3. Specify how often you want to monitor the arrays by selecting a value in the Monitoring Frequency field.

4. Specify the maximum number of arrays to monitor concurrently by selecting a value in the Maximum Monitoring Thread field.

5. In the Timeout Setting section, set the agent timeout settings.

The default timeout settings are appropriate for most storage area network (SAN) devices. However, network latencies, I/O loads, and other device and network characteristics may require that you customize these settings to meet your configuration requirements. Click in the value field for the parameter and enter the new value.

6. When all required changes are complete, click Save.

The configuration is saved.

Enabling Health Monitoring for an Array

1. In the navigation pane, select an array for which you want to display or edit the health monitoring status.

2. Click Array Health Monitoring

The following Array Health Monitoring Setup page is displayed.

3. For the array to be monitored, ensure that the monitoring agent is active and that the Device Category Monitored is set to Yes. If not, go to Configuring Array Health Monitoring

4. Select the checkbox next to Health Monitoring to enable health monitoring for this array; deselect the checkbox to disable health monitoring for the array.

5. Click Save.


Activating Auto Service Request

To complete ASR activation, use the My Oracle Support web site: http://support.oracle.com.

Note: Before activating ASR with My Oracle Support, be sure you have registered the CAM software with ASR by following the instructions in Subscribing to Auto Service Request (ASR).

Note: The Pending ASR Activations menu is only available to My Oracle Support accounts with the administrator privilege on the Support Identifiers associated with your Assets (array devices).

For more information about ASR, go to:
http://oracle.com/asr.

Configuring ASR Client Security

To configure firewalls, you will need information about the security aspects of communication between components in the client environment. Port 443 must be open to the URLs in the following table.

TABLE 6-1 depicts the data collected for case creation, used to determine entitlement.


TABLE 6-1 Data Collected for Case Creation

Data Collected

Destination URL

Port and Description

Activation event

Client registration:

https://transport.oracle.com/v1/queue/registry

Product activation:

https://transport.oracle.com/v1/queue/asr-cam-activation

Port 443; Static Data

collected for purpose

of registration and

activation.

Alarm and messages event

Alarm and administrative messages:

https://transport.oracle.com/v1/queue/asr-cam-messages

Port 443;

Potential case- generating events are sent via the secure transport to trigger case generation.

Event type = alert

Audit event

Audit messages:

https://transport.oracle.com/v1/queue/asr-cam-audit

Port 443; Dynamic

configuration data

collected and sent every

seven days.

Event type = audit

Heartbeat event

Heartbeat messages:

https://transport.oracle.com/v1/queue/asr-cam-heartbeat

Port 443; Dynamic data

periodically collected to

establish a device is

capable of connecting.

Sent every 6 hours.

Event type = daily


 

Feedback