JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SPARC SuperCluster T4-4 Zones With Oracle Database on Database Domains

Configuration Guide

search filter icon
search icon

Document Information

Using This Documentation

Product Notes

Related Documentation

Feedback

Access to Oracle Support

Planning to Set Up Zones on Database Domains

Important Cautions

Naming Conventions

Understanding Domain Configurations

Determining the Cores Available for Domains and Zones

Cores Available for Domains and Zones

Memory Available for Domains

Zones and Cluster Planning for Database Domains

Guidelines for Planning the Number of Zones and Clusters

Guidelines for Planning the Storage Server Disk Group Layout

Planning the Exadata Storage Server Disk Group Layout

Understanding an Example Scenario

Recording Your Existing and Planned Configuration Information

Recording Your Existing Configuration

Recording Your Zone Configuration Information

Recording Your Cluster Configuration Information

Recording Your Exadata Storage Server Disk Group Layout

Understanding Network Considerations

Understanding the Networking Setup Before Zone Creation

Host Management Network Before Zone Creation

Client Access Network Before Zone Creation

InfiniBand Network Before Zone Creation

Understanding the Networking Setup After Zone Creation

Host Management Network After Zone Creation

Client Access Network After Zone Creation

InfiniBand Network After Zone Creation

Understanding the Network Setup for Clusters

Preparing to Configure Zones on Database Domains

Prepare to Configure Zones

Existing Network Worksheet

Update the Base Software

Determine the Repository Location

Install or Update Packages From the Remote Repository

Install or Update Files From the Local Repository

Verify Configuration Tool Installation

Creating Configuration Files Using OEDA

Verify Exadata Storage Server Disk Space for Additional Zones

Creating Configuration Files Using OEDA: Manual Procedures

Oracle Exadata Deployment Assistant Overview

Set Up the OEDA

Start the OEDA

Complete the Customer Details Page

Complete the Hardware Selection Page

Complete the Define Customer Networks Page

Complete the Administration Network Page

Complete the Client Ethernet Network Page

Complete the IB Network Page

Complete the Identify Compute Node OS and Enable Capacity-on-Demand Configuration Page

Review the Information in the Management and Private Networks Page

Complete the Define Clusters Page

Set Zone Default Configurations

Complete the Cluster Page

Complete the Cluster Review and Edit SCAN, Client, VIP and Optional Backup Networks Page

Verify Remaining Configuration Information

Generate the Configuration Files

Creating Configuration Files Using OEDA: Automated Procedures

Locate the Necessary Files to Set Up Zones

Set Up the OEDA

Start the OEDA

Import the Most Recent OEDA Configuration File

Review Existing Configuration Information

Review the Information in the Identify Compute Node Operating System Page

Review the Information in the Management and Private Networks Page

Complete the Define Clusters Page

Set Zone Default Configurations

Complete the Cluster Page

Complete the Cluster Review and Edit SCAN, Client, VIP and Optional Backup Networks Page

Verify Remaining Configuration Information

Generate the Configuration Files

Creating the Template Zone on Each Database Domain

Create a Template Zone on a Database Domain

Delete a Template Zone From a Database Domain

Creating VNETs

Determining if Additional VNETs Are Needed for a Database Domain

Determine if Additional VNETs Are Needed (CPU-to-Database Domain Mapping)

Determine if Additional VNETs Are Needed (Software Commands)

Locate the Control Domain

Create VNETs for Zones

Delete VNETs

Running the Java OneCommand

Set Up Public Key Authentication for ZFS Storage Controllers

Set Up the Java OneCommand

Run the Java OneCommand

NTP Issue

Creating Additional Links on the IB Storage Network for Zones

Create Additional Links on the IB Storage Network for Zones

Setting Up VLAN Tagging for Zones

Set Up VLAN Tagging for Zones

Index

Complete the IB Network Page

  1. Complete the fields in the IB Network page.
    image:Graphic showing the IB Network page.
    Field
    Entry
    Starting IP Address for Pool
    Type the starting IP address for this cluster.
  2. In the Sample first IB Name field, click the Modify... button.

    The Private (IB) Network Format Masks page is displayed.


    image:Graphic showing the Private (IB) Network Format Masks page.
  3. Modify the host names in this page for the zones in this cluster.
    1. In the Compute Private Details area, modify the information in the Name field that was automatically populated.

      The Compute Private Details area will be populated with a name that was automatically generated, based on the Database Machine Name prefix that you entered earlier. However, this automatically-generated name does not provide necessary zone-specific information, so you should change the name in this field to reflect information on this cluster.

      For example, if you entered ssc01r1 for the Database Machine prefix in the Customer Details page, you should see this entry in the Name field in the Compute Private Details area:

      ssc01r1db%%-priv

      The name that you enter in this field will be used as the host name for the IB network for zones that are part of this cluster. You should use the same naming convention for this field as you did for the administration network page. The following is an example format for this field:

      cluster-namez#db#cn%-priv

      For example:

      ssc01r1z1db1cn%-priv


      Note - There is a valid configuration where you would have a cluster where the zones reside on different Database Domains on the SPARC T4-4 servers (for example, a two-node cluster where the first zone resides on the first Database Domain on the first SPARC T4-4 server, and the second zone resides on the second Database Domain on the second SPARC T4-4 server). In this case, enter the Database Domain number for the first zone in this field for now - you will make manual modifications for the zone on the second Database Domain later on in this process.


    2. In the Cell Private Details area, modify the information in the Name field that was automatically populated.

      The Name field in the Cell Private Details area will automatically populate, depending on the Database Machine Prefix that you chose earlier. For example, if you used ssc01r1 as the Database Machine Prefix, then the following information will automatically populate in the Name field in the Cell Private Details area:

      ssc01r1cel%%-priv

      However, this field is meant for the Exadata Storage Servers, so zone naming information should not be used in this area. You must change this field so that the format matches the host name for the IB network that has already been assigned to your Exadata Storage Servers, where the % in the field denotes a numerical wild card that will be automatically assigned.

      For example, if the host names for the IB network for your Exadata Storage Servers are supercluster-namecelESS-number-priv (for example, ssc01cel01-priv), then you would delete the necessary text in this field until you have this:

      ssc01cel%%-priv

      The following table provides information on how the fields in this screen should be populated once you have made all the necessary changes.


      Component/Cluster
      Correct Entry
      Compute Private Details Name and Starting ID
      Should have a value that applies to the zones in this particular cluster
      Cell Private Details Name and Starting ID
      Should have a value that applies to the Exadata Storage Servers
    3. Click the Save button to exit the Private (IB) Network Format Masks page.

      The main IB Network page is displayed, showing the results of the changes you made in the Private (IB) Network Format Masks page.

  4. In the main IB Network page, click Next.

    The Backup Network page is displayed.

  5. Complete the fields in the optional Backup Network page, if necessary.

    When you have completed this page, click Next. The Identify Compute Node OS and Enable Capacity-on-Demand Configuration page is displayed.

  6. Complete the fields in the Identify Compute Node OS and Enable Capacity-on-Demand Configuration page.

    Go to Complete the Identify Compute Node OS and Enable Capacity-on-Demand Configuration Page.