Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2390425.1
Update Date:2018-05-07
Keywords:

Solution Type  Technical Instruction Sure

Solution  2390425.1 :   Monitoring of ZFS Storage Appliance in Exalogic using Central Agent in EM 13c  


Related Items
  • Exalogic Elastic Cloud X4-2 Eighth Rack
  •  
  • Oracle Exalogic Elastic Cloud Software
  •  
Related Categories
  • PLA-Support>Eng Systems>Exalogic/OVCA>Oracle Exalogic>MW: Exalogic Core
  •  




In this Document
Goal
Solution
 Recommended Versions
 ZFS Monitoring Procedures
References


Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.0 and later
Exalogic Elastic Cloud X4-2 Eighth Rack - Version X4 to X4 [Release X4]
Linux x86-64
Oracle Virtual Server x86-64

Goal

This MOS Note provides information on how to monitor ZFS storage appliance in Exalogic by the customer through their instance of EM 13c. 

Solution

To monitor ZFS storage appliance in Exalogic by the customer through their instance of EM 13c, we recommend the use of the ZFSSA plugin 13c on an EM 13c agent.

Using ZFSSA plugin 12.1 (12.1.0.5, 12.1.0.6, or 12.1.0.7) on Exalogic Control vServer with EM agent 12.1.0.5 does not work. There are two major points to note for monitoring ZFS in Exalogic:

  1. The support for TLS v1.0 is removed in ZFS running software version 2013.1.7.x or higher, so TLS v1.2 is required to monitor ZFS with version 2013.1.7.x or higher. EM 12c does not support TLS v1.2. Therefore, EM 13c is required to monitor ZFS in Exalogic.

  2. OL5 is not supported in EM 13c, and Exalogic Control vServer is based on OL5. So, the EM 13c agent is not supported to be installed on Exalogic Control vServer.

Due to these two restrictions, monitoring ZFS from the EM agent on the OL5-based Exalogic Control vServer does not work. The recommended approach for customer to monitor ZFS in Exalogic is to use the EM 13c central agent with EM 13c OMS.

Recommended Versions

  • OMS: 13.2.0.0.0
  • Central Agent (with OMS install): 13.2.0.0.0
  • ZFSSA Plugin: 13.2.4.0.0

ZFS Monitoring Procedures

Assumption: EMCC 13c is installed and the Exalogic ZFS is accessible.

  1. Deploy the "Oracle ZFS Storage Appliances" plugin (13.2.4.0.0) to both OMS and the central agent

    a. Select the top menu "Setup > Extensibility > Plug-ins", expand "Servers, Storage and Network" section and check if the "Oracle ZFS Storage Appliances (13.2.4.0.0)" is available

    b. If it is not available, then go to menu "Setup > Extensibility > Self Update", click on "Plug-ins" link in the table, and then select the ZFSSA plugin (13.2.4.0.0) and click on "Download" button to download it

    c. If it is available (or available after downloading it in Step b) on the Plug-ins page, select the ZFSSA (13.2.4.0.0) plugin row and select "Deploy On > Management Server..." menu item.

    d. After the deployment is successful, select "Deploy On > Management Agent ..." menu. Then follow the popup UI to select the central agent on the OMS host and select "Deploy" button.

  2. Discover the ZFSSA target

    a. Select the top menu "Setup > Add Target > Add Targets Manually", and click on "Add Targets Declaratively" button

    b. In the popup window, select the host on the OMS server (central agent) and target type "Oracle ZFS Storage Appliance", and click on the "Add ..." button
    Step 2 (b).png

    c. Enter ZFS monitoring properties, e.g. target name, credentials, and storage server name / IP and ports, and click on "Test Connection" button

    d. If the test is successful, click on "OK" to save the target.

    Step 2 (d).png

  3. Check the ZFSSA target status and home page to make sure it is properly monitored - it may take a while to be able to access the target as the target population takes some time. If you see dataset-related popup errors on the All Metrics page of the ZFSSA target for some specific metric, like this:
    Step 3.png

    then you can do the following to fix it:

    a. Select the top menu "Enterprise > Job > Library", and select "Create Library Job" type "Oracle ZFSSA Manage Analytics Datasets", and click on "Go" button.

    b. Then in General tab, enter the job name and add the targets to apply the job; in Parameters tab, specify operation "create" with the comma-separated datasets, e.g. 'arc.accesses[share],mem.heap[application=mgmt],mem.heap[application]'; in Credentials tab, specify the ZFSSA credential and agent host credential. Click on "Save to Library" button the save the library job.

    Step 3 (b).png

    c. Select the newly created job library from the list and click on "Submit" button - you may need to specify the agent host credential again, and click "Submit" button

    d. Click on the job name link in the top confirmation message (the job was created successfully) to monitor the job status.

    e. After the job is done, go back to the target All Metrics page for that metric to make sure the dataset error is no longer observed. If the "Collection Schedule" is disabled for the metric, click on the Edit icon to enable it.

    Step 3 (e).png

For details on ZFSSA monitoring using ZFSSA plugin, refer to the ZFSSA Admin Guide at: http://download.oracle.com/otn/java/oem/zfs/v21/EMCC_Admin_101515_final.pdf

NOTE: The ZFS Storage appliance loses its association with the Exalogic system using the procedure in this document. This is a known issue with this approach, but does not affect monitoring functionality. This integration is supported on Exalogic for customer OMS deployments of 13c.

 

References

<NOTE:1502322.1> - Exalogic Virtualization Release FAQs
<NOTE:1492609.1> - Exalogic EMCC/EMOC Master Note
http://download.oracle.com/otn/java/oem/zfs/v21/EMCC_Admin_101515_final.pdf

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback