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)
Set Up Public Key Authentication for ZFS Storage Controllers
Creating Additional Links on the IB Storage Network for Zones
Create Additional Links on the IB Storage Network for Zones
See Preparing to Configure Zones on Database Domains for the location of the addvnet-wrapper.sh script.
ldm list
See Locate the Control Domain for instructions on locating the control domain.
addvnet-wrapper.sh DB-domain num-zone
where:
DB-domain is the name of the guest domain.
num-zone is the number of zones that you are setting up on the Database Domains in this particular SPARC T4-4 server.
For example, if you have the following setup:
The name of the guest domain is ssc01dbadmin02-01.
You will be setting up 4 zones on the Database Domains on this SPARC T4-4 server.
Then you would type the following command:
addvnet-wrapper.sh ssc01dbadmin02-01 4 Adding VNETs on ssc01dbadmin02-01 -----| Okay Info: found active ldom configuration F8_1_1_ML11242013214449 Info: will add new ldom configuration F8_1_1_ML11242013214449 Adding ldom configuration --------/ Okay INFO: ssh into ssc01dbadmin02-01 for post-vnet operations INFO: Renamed link net24 to zonenet24 INFO: Renamed link net25 to zonenet25 INFO: Renamed link net26 to zonenet26 INFO: Renamed link net27 to zonenet27
Viewed from the Hypervisor perspective, using the ldm command, the VNETs that you added start with z, followed by a nonnegative integer, followed by mgnet, and ending with either a 0 or a 1 (for example, z0mgnet1).
Viewed from the Solaris perspective, using the dladm command, the network created is in the form of zonenetxx, where xx are consecutive numbers (such as zonenet12, zonenet13, and so on). Once a zone is deployed, the network picked for that particular zone or instance is mapped to zonbnetxx (such as zonbnet12, zonbnet13, and so on) to indicate that they are locked and used for the respective zone.
If you destroy a zone using the instructions in Delete a Template Zone From a Database Domain, the net pool is freed and renamed back to zonenetxx (such as zonenet12, zonenet13, and so on) so that any future addition of zones using zone tools can pick those VNETs.
ldm ls -l -p DB-domain | grep ‘^VNET'
where DB-domain is the name of the Database Domain with zones that you added the VNETs to. For example, if the name of the Database Domain with zones that you added the VNETs to is ssc01dbadmin02-01, type the following:
ldm ls -l -p ssc01dbadmin02-01 | grep ‘^VNET' VNET|name=mngnet0|dev=network@0|service=mng-primary-net1@primary|mac-addr=00:14:4f:fa:f8:e8|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=0 VNET|name=mngnet1|dev=network@1|service=mng-primary-net00@primary|mac-addr=00:14:4f:fb:a0:cd|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=1 VNET|name=z0mgnet0|dev=network@2|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:da:06|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=2 VNET|name=z0mgnet1|dev=network@3|service=mng-primary-net1@primary|mac-addr=00:14:4f:f8:a8:06|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=3 VNET|name=z1mgnet0|dev=network@4|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:83:cc|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=4 VNET|name=z1mgnet1|dev=network@5|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:26:ab|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=5
Go to Running the Java OneCommand.