Skip Navigation Links | |
Exit Print View | |
SPARC SuperCluster T4-4 Zones With Oracle Database on Database Domains Configuration Guide |
Planning to Set Up Zones on Database Domains
Understanding Domain Configurations
Determining the Cores Available for Domains and Zones
Cores Available for Domains and Zones
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
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
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 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 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
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 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
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)
Creating Additional Links on the IB Storage Network for Zones
Create Additional Links on the IB Storage Network for Zones
Before running the Java OneCommand, you must set up public key authentication on the ZFS storage controllers for every SPARC T4-4 server where you are setting up zones on the Database Domains.
To log in remotely using the CLI, use an ssh client. If you have not configured other users to administer the appliance, you must log in as root. When you log in, the CLI prompt consists of the hostname, followed by a colon, followed by a greater-than sign:
% ssh root@zfs-controller1-hostname Password: Last login: Mon Oct 13 15:43:05 2009 from kiowa.sf.fishpo zfs-controller-hostname:>
where zfs-controller1-hostname is the host name for the first ZFS storage controller.
zfs-controller1-hostname:> configuration preferences keys zfs-controller1-hostname:configuration preferences keys> create zfs-controller1-hostname:configuration preferences key (uncommitted)> set type=DSA zfs-controller1-hostname:configuration preferences key (uncommitted)> set key="DSA-key-text" key = DSA-key-text == (uncommitted) zfs-controller1-hostname:configuration preferences key (uncommitted)> set comment="fw-log1" comment = fw-log1 (uncommitted) zfs-controller1-hostname:configuration preferences key (uncommitted)> commit zfs-controller1-hostname:configuration preferences keys> show Keys: NAME MODIFIED TYPE COMMENT key-000 10/12/2009 10:54:58 DSA fw-log1
The DSA-key-text is the key text itself (usually hundreds of characters), without spaces.
zfs-controller1-hostname:> exit
Note - You do not have to repeat this procedure for the second ZFS storage controller. When you set up the public key authentication on the first ZFS storage controller, it appears when you log in to the second ZFS storage controller.
% ssh root@zfs-controller1-hostname hostname
where zfs-controller1-hostname is the host name for the first ZFS storage controller.
You should be able to log in to the ZFS storage controller successfully and see the CLI prompt.