Oracle Enterprise Manager System Monitoring Plug-in
Table 1: Reports
Reports accessed via a target instance differ when they are accessed via the Reports tab within Oracle Enterprise Manager Grid Control. All instance reports are available under the Reports tab, Storage category and Network Attached Storage sub-category. When accessed with this route, Reports have configurable time spans for graph display where these are applicable.
All system reports can be cloned and customized by administrators.
Several metrics can have custom thresholds set within Oracle Enterprise Manager Grid Control. The alerts received are contained within the product and are not set as Alerts and Thresholds on the Sun Storage 7000 Appliance itself. The table below shows the metrics that have thresholds set with their default values:
Table 2: Metrics
For the most part, alerts and thresholds for the appliance should be managed by the Storage Administrator, they have many more statistics available to them within the Sun Storage 7000 Appliance User Interface. Further, the Storage Administrator will have real-time indications of performance issues as opposed to the slower polling interval required by Oracle Enterprise Manager Grid Control.
Metrics, Reports, and information presented on charts can take up to 60 minutes to populate as the polling intervals for relatively static information is long. Be patient for the complete reports to populate. Further, do to differing polling cycles between statistics, some information may populate prior to other information.
Follow instructions provided within the Oracle Enterprise Manager documentation to un-deploy a plug-in. At a high level, the Oracle Enterprise Manager Grid Control administrator must:
Once completed, communicate with the Sun Storage 7000 Storage Administrator(s) and have them run the "Unconfigure Oracle Enterprise Manager Monitoring"workflow.
A Sun Storage 7000 Administrator has an advantage of real-time appliance analytics that, like Oracle Enterprise Manager Grid Control, can be viewed in various time-spans dating back to the start of the time when the system was configured to be monitored by Oracle Enterprise Manager Grid Control. Some data sets are available from the first power on of the appliance itself.
The most common use of the Oracle Enterprise Manager Grid Control plug-in (besides simple capacity monitoring and high-level information collection) will be the analysis of application performance degradation. Using the information within Oracle Enterprise Manager Grid Control, print or deliver the information to the Sun Storage 7000 Administrator that you believe is the leading indicator of the Sun Storage 7000 Appliance being a root cause or related to a performance degradation in an application.
Once that information is presented to the Storage Administrator, they can start the analysis process by entering the "Oracle Enterprise Manager"worksheet. This worksheet displays a "down to the second"view of the data that you presented to them, as opposed to the much coarser view of the data available to Oracle Enterprise Manager Grid Control (often a 10 or 20 minute collection cycle).
From the worksheet, or other data sets available to the Storage Administrator, they can root cause down to the hardware component or software component level if they believe there is an issue in the hardware. In the event of a pure resource contention issue, they have deep levels of client access information available to them with how and when individual clients are accessing a system along with the resources they are accessing (network interfaces, logical resources such as shares and more).
Once initial communication is complete, the Storage Administrator should complete the analysis of the problem and return with a way to resolve a disruption in Quality of Service or with data from the system indicating that the problem is likely not associated with the Sun Storage 7000 Appliance.
There is a direct mapping of information displayed within Oracle Enterprise Manager Grid Control to datasets and information collected in the target Sun Storage 7000 Appliances. Storage Administrators should ensure that the following datasets on the Sun Storage 7000 Appliance remain enabled or notify the Oracle Enterprise Manager Grid Control administrator that they will start receiving errors when they are disabled:
Table 3: Metric Information
From the above list, information that is collected via "System Attributes from Workflow"indicate items that cannot be "enabled / disabled"by an administrator, they are simply collected via scripts that are called on each Sun Storage 7000 Appliance.
There are a variety of reasons that a monitored instance in the Oracle Enterprise Manager Grid Control may not be returning information properly. These issues are typically associated with mis-configuration, incorrect permissions or changing configuration within one of the products.
Table 4: Symptoms and Resolutions
There are also a set of common configuration problems when the "Metric Collection Error". In most cases, Metric Collection Errors contain two parts, a short string followed by a longer Java Stack Trace. Do not concern yourself with the Java Stack Trace, this will be used by Sun Services if there is a more complex problem. The first string should contain enough information to isolate the problem. Common Metric Collection problems are as follows:
Table 5: Metric Collection Errors
For detailed debug information, use the audit log on the target Sun Storage 7000 Appliance to determine actions that occurred with the workflows. Creation and deletion of artifacts (or the failure to create or delete an artifact) are traced in the audit log.
Debugging why an agent is not properly collecting statistics from a Sun Storage 7000 Appliance can be more difficult and should only be done by service personnel.
Most problems (other than version mismatches) will occur during collection of metrics or collection response information. Look for the following logs on the agent host. The agent host may differ from the management station location. In the following file locations, %AGENT_LOCATION% indicates the home directory of the agent, typically similar to "/export/home/oracle/OracleHomes/agent10g", an * indicates there may be several files with additional extensions.
When interacting with Sun Services or Developers within your own help desk, please include the sun_storage_7000_pipe.log* files and emagent.trc* files for their use.