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
Follow these procedures if you need to delete any VNETs that you added using the addvnet-wrapper.sh script and you created VNETs accidentally that are not needed.
Note - Do not delete VNETs that are used by zones. Doing so results in a failed zone.
See Preparing to Configure Zones on Database Domains for the location of the rmvnet.sh script.
ldm ls -l -p DB-domain | grep '^VNET'
where DB-domain is the name of the Database Domain that you added the VNETs to. For example, if the name of the Database Domain that you added the VNETs to is ssc01dbadmin02-01, you would type the following:
ldm ls -l -p ssc01dbadmin02-01 | grep '^VNET' VNET|name=mgnet0|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=mgnet1|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
rmvnet.sh -n vnet-name DB-domain
where:
vnet-name is the name of the VNET that you want to remove. If you want to remove more than one VNET, type the name of each VNET that you want to remove, separated by commas.
DB-domain is the name of the Database Domain from which you are removing the VNETs.
For example, assume you have the following setup:
The names of the VNETs that you want to remove are z1mgnet0 and z1mgnet1.
The name of the Database Domain that you are removing the VNETs from is ssc01dbadmin02-01.
Then you would type the following:
rmvnet.sh -n z1mgnet0,z1mgnet1 ssc01dbadmin02-01
rmvnet.sh -p 'beginning-term+' DB-domain
where:
beginning-term is the term at the beginning of the VNET names for the VNETs that you want to remove (for example, all VNETs with names that begin with z1).
domain-name is the name of the Database Domain from which you are removing the VNETs.
For example, assume you have the following setup:
You want to remove all VNETs with names that begin with z1 (in the output from Step 2, that would be z1mgnet0 and z1mgnet1).
The name of the Database Domain that you are removing the VNETs from is ssc01dbadmin02-01.
Then you would type the following:
rmvnet.sh -p 'z1+' ssc01dbadmin02-01
ldm ls -l -p DB-domain | grep '^VNET'
where DB-domain is the name of the Database Domain that you removed the VNETs from. For example, if the name of the Database Domain that you removed the VNETs from is ssc01dbadmin02-01, type the following:
ldm ls -l -p ssc01dbadmin02-01 | grep ‘^VNET' VNET|name=mgnet0|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=mgnet1|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
The VNETs that you removed should not appear in the list.