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
# dladm show-ib
Output similar to the following appears:
LINK HCAGUID PORTGUID PORT STATE PKEYS net24 21280001FCBEBC 21280001FCBEBE 2 up FFFF net22 21280001FCC0EC 21280001FCC0EE 2 up 8503,8504,FFFF net23 21280001FCBEBC 21280001FCBEBD 1 up 8503,8504,FFFF net21 21280001FCC0EC 21280001FCC0ED 1 up FFFF
In the example output shown in the previous step, the lines that show the network links associated with the 8503 PKEY are shown in bold. The network links are shown in the LINK column (net22 and net23 in the example output).
# zonecfg -z zone_management_hostname zonecfg:zone_management_hostname> add anet zonecfg:zone_management_hostname:anet> set linkname=first_net_link zonecfg:zone_management_hostname:anet> set lower-link=first_net_link zonecfg:zone_management_hostname:anet> set pkey=8503 zonecfg:zone_management_hostname:anet> end zonecfg:zone_management_hostname> add anet zonecfg:zone_management_hostname:anet> set linkname=second_net_link zonecfg:zone_management_hostname:anet> set lower-link=second_net_link zonecfg:zone_management_hostname:anet> set pkey=8503 zonecfg:zone_management_hostname:anet> end zonecfg:zone_management_hostname> exit
where:
zone_management_hostname is the management host name (or Admin Name that was shown in Oracle Exadata Deployment Assistant) for this zone
first_net_link is the first network link shown in the output from Step 2
second_net_link is the second network link shown in the output from Step 2
For example:
# zonecfg -z zone_management_hostname zonecfg:zone_management_hostname> add anet zonecfg:zone_management_hostname:anet> set linkname=net22 zonecfg:zone_management_hostname:anet> set lower-link=net22 zonecfg:zone_management_hostname:anet> set pkey=8503 zonecfg:zone_management_hostname:anet> end zonecfg:zone_management_hostname> add anet zonecfg:zone_management_hostname:anet> set linkname=net23 zonecfg:zone_management_hostname:anet> set lower-link=net23 zonecfg:zone_management_hostname:anet> set pkey=8503 zonecfg:zone_management_hostname:anet> end zonecfg:zone_management_hostname> exit
# zoneadm -z zone_management_hostname reboot
For example:
# zoneadm -z ssc01zdbadm02 reboot
# zlogin zone_management_hostname
For example:
# zlogin ssc01zdbadm02
# ipadm create-ip first_net_link # ipadm create-ip second_net_link
where:
first_net_link is the first network link shown in the output from Step 2
second_net_link is the second network link shown in the output from Step 2
For example:
# ipadm create-ip net22 # ipadm create-ip net23
# ipadm show-addr
Output similar to the following appears:
ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 net13/v4 static ok 169.254.182.77/24 stor_ipmp0/v4 static ok 192.168.28.2/22 bondeth0/v4 static ok 10.129.119.1/20 bondib0/v4 static ok 192.168.10.1/22 bondib1/v4 static ok 192.168.10.2/22 bondmgt0/v4 static ok 10.129.104.1/20 lo0/v6 static ok ::1/128
In the ADDR column for this line, the subnet is shown as 192.168.28.2, with a subnet mask of 22.
# ipadm create-ipmp -i first_net_link,second_net_link ipmp_group # ipadm create-addr -T static -a ip_address/22 ipmp_group/v4
where:
first_net_link is the first network link shown in the output from Step 2
second_net_link is the second network link shown in the output from Step 2
ipmp_group is the name of the IPMP group that you are creating
ip_address is an unused IP address from the same subnet as the stor_ipmp0 interface that you picked in Step 8
For example:
# ipadm create-ipmp -i net22,net23 stor_ipmp0 # ipadm create-addr -T static -a 192.168.28.101/22 stor_ipmp0/v4
# ipadm set-ifprop -p standby=on -m ip second_net_link
where second_net_link is the second network link shown in the output from Step 2.
For example:
# ipadm set-ifprop -p standby=on -m ip net23
# ipmpstat -g
The second network interface should appear in parenthesis in the output. For example:
# ipmpstat -g GROUP GROUPNAME STATE FDT INTERFACES stor_ipmp0 stor_ipmp0 ok -- net22 (net23)