Oracle Exalogic Elastic Cloud X2-2 One-Eighth Rack
 
Oracle Exalogic Elastic Cloud X2-2 Full Rack
 
Oracle Exalogic Elastic Cloud X2-2 Half Rack
 
Oracle Exalogic Elastic Cloud X2-2 Qtr Rack
 
Oracle Exalogic Elastic Cloud Software
 
Oracle Exalogic Elastic Cloud X2-2 Hardware
 

PLA-Support>Database Technology>Engineered Systems>Oracle Exalogic>MW: Exalogic Core
 

In this Document

Goal

Fix

Purpose

Scope and Application

Procedure

Identify the current storage node

Locate and review ZFS Storage Appliance wide settings for the FTP service to ensure it is enabled

Locate and review settings on the storage project named common

Review FTP settings for each of the shares (common/images and common/patches) to confirm settings and note the URL for each file system

Applies to:

Goal

This document illustrates how to configure the ZFS Storage Appliance (ZFSSA) to allow the content of a filesystem defined as a ZFS Share to be accessed via FTP, such that individual firmware and appliance kit updates within EECS Patch Set Updates (PSU's) and EECS Upgrades are accessible via FTP as required during the update process.

Fix

Purpose

During the course of applying updates to an Exalogic System, as part of either a Patch Set Update (PSU) or Exalogic Elastic Cloud Software (EECS) Upgrade (for example: Upgrading EECS 1.x to 2.x), it is necessary to apply updates to components such as ILOM firmware for IB network switches (NM2-GW, NM2-36P), compute nodes and ZFS Storage Heads as well as upgrade the storage appliance kit software on each storage head.

The application of such updates requires access, via FTP, to various software packages shipped within the distributed media for the PSU or EECS Upgrade and this document provides a step-by-step illustration of how the patch media can be copied to a location within ZFS shared storage that can then be made accessible via FTP.

Scope and Application

The document is provided for use by system administrators of Exalogic Systems. Some rudimentary familiarity with Exalogic Systems and ZFS Storage concepts, though not required, may prove beneficial to understanding the steps provided.

Procedure

Identify the current storage node

Use a browser to access the Shares screen of each of the two storage heads in turn.

The URL to enter in the browser will be of the format:

https://<storage-head-hostname-or-ip>.<your-domain>:215/#shares/shares

For example:

Locate and review ZFS Storage Appliance wide settings for the FTP service to ensure it is enabled

1. Within the ZFS Storage Appliance Browser User Interface (BUI) of the currently active storage node:
   
   
   • Select Configuration from the top row of menu choices
   • Select Services from the second row of sub-menu choices
   • In the Data Services section, f there is no GREEN power icon displayed to the left of the FTP entry, click on the FTP link to review settings:
     
   • On the FTP settings page, review settings and click on the power icon just below the title to start the FTP service:
     

Locate and review settings on the storage project named common

1. Within the ZFS Storage Appliance Browser User Interface (BUI) of the currently active storage node:
   
   
   • Select Shares from the top row of menu choices
   • Select Projects from the second row of sub-menu choices
   • Click on the magnifying glass icon, enter common in the text area and press ENTER to filter the rows display to only those including the name common:
     
   • Within the row returned for the common project, click on the pencil icon to edit the properties for the project:
     
2. Review FTP Protocol settings for the common project and ensure that Share Mode is set to Read/Write at the project level
   
   
   • Click on the Protocols menu
   • Review settings within the FTP section
     
     Ensure that Read/Write is selected as the value for the Share Mode drop down menu:
     
   
   
   • NOTE:
     
     Enabling FTP at the project level defines FTP settings that will be inherited by all file systems within the project. For the common project this includes both the common/patches and common/images file systems, where the media for PSU and EECS Upgrades will be stored and accessed during the update process.
     
     Allowing Read/Write access to these file systems through FTP is optional, but is recommended as it provides the additional flexibility of being able to use FTP client tools (e.g. FileZilla etc.) as a convenient way to upload media downloaded from Oracle locations (such as eDelivery.oracle.com) to intermediary machines that may not be able to mount NFS file systems directly.

Review FTP settings for each of the shares (common/images and common/patches) to confirm settings and note the URL for each file system

1. Access the main Appliance Kit BUI page of the currently active storage head (https://<storage-head-hostname-or-ip>.<your-domain>:215/)
   
   
   • Select Shares from the top row of menu choices
   • Select Shares from the second row of sub-menu choices
   • Click on the magnifying glass icon, enter common in the text area and press ENTER to filter the rows displayed to only those including the name common:
     
2. In turn, highlight each of the rows for each of the two file systems of interest in the common project (images and patches) and click on the pencil icon:
   
3. Click on Protocols sub-menu item and review the FTP Section for each entry:
   
4. Click on the FTP link displayed to confirm access to the file system via FTP, using the browser as an FTP client
   
   
   • You will need to log in using the credentials for the root user of the storage appliance (e.g. root/mypasswd)
     
   • Once successful access has been validated from the browser, make a note of the URL prefix for FTP access to each file system, as these will need to be used later on various command lines while performing firmware and appliance kit updates.

This solution has no attachment