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
# crsctl stop crs -f # crsctl disable crs
# zoneadm -z zone_management_hostname halt
where zone_management_hostname is the management host name (or Admin Name that was shown in Oracle Exadata Deployment Assistant) for this zone. For example:
# zoneadm -z ssc01zdbadm02 halt
# ipmpstat -g
Output similar to the following appears. Locate the line in the output for the bondeth0 interface, highlighted in the following example output:
GROUP GROUPNAME STATE FDT INTERFACES bondmgt0 bondmgt0 ok -- net0 (net1) bondib1 bondib1 ok -- bondib1_0 (bondib1_1) bondib0 bondib0 ok -- bondib0_0 (bondib0_1) bondeth0 bondeth0 ok -- net4 (net7) stor_ipmp0 stor_ipmp0 ok -- stor_ipmp0_0 (stor_ipmp0_1)
In the example output above, those entries would be net4 and net7.
# dladm show-phys | grep ixgbe
Output similar to the following appears. Locate the lines in the output for the two entries that you noted in Step b, highlighted in the following example output:
net5 Ethernet unknown 0 unknown ixgbe3 net1 Ethernet up 1000 full ixgbe1 net6 Ethernet unknown 0 unknown ixgbe4 net0 Ethernet up 1000 full ixgbe0 net4 Ethernet up 10000 full ixgbe2 net7 Ethernet up 10000 full ixgbe5
# zonecfg -z zone_management_hostname zonecfg: zone_management_hostname> select anet linkname=net_device#1 zonecfg: zone_management_hostname:anet> set vlan-id=VLAN_ID zonecfg: zone_management_hostname:anet> set lower-link=net_device#1 zonecfg: zone_management_hostname:anet> end zonecfg: zone_management_hostname> select anet linkname=net_device#2 zonecfg: zone_management_hostname:anet> set vlan-id=VLAN_ID zonecfg: zone_management_hostname:anet> set lower-link=net_device#2 zonecfg: zone_management_hostname:anet> end zonecfg: zone_management_hostname> verify zonecfg: zone_management_hostname> commit 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
VLAN_ID is a VLAN ID that you provide
net_device#1 is the first client network device that you saw in the output in Step b
net_device#2 is the second client network device that you saw in the output in Step b
For example:
# zonecfg -z ssc01zdbadm02 zonecfg: ssc01zdbadm02> select anet linkname=net4 zonecfg: ssc01zdbadm02:anet> set vlan-id=13 zonecfg: ssc01zdbadm02:anet> set lower-link=net4 zonecfg: ssc01zdbadm02:anet> end zonecfg: ssc01zdbadm02> select anet linkname=net7 zonecfg: ssc01zdbadm02:anet> set vlan-id=13 zonecfg: ssc01zdbadm02:anet> set lower-link=net7 zonecfg: ssc01zdbadm02:anet> end zonecfg: ssc01zdbadm02> verify zonecfg: ssc01zdbadm02> commit zonecfg: ssc01zdbadm02> exit
# zoneadm -z zone_management_hostname reboot
For example:
# zoneadm -z ssc01zdbadm02 reboot
# crsctl enable crs # crsctl start crs