JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle SuperCluster M6-32 Zones With Oracle Database on Database Domains

Configuration Guide

search filter icon
search icon

Document Information

Using This Documentation

Product Notes

Related Documentation

Feedback

Access to Oracle Support

Planning to Set Up Zones on Database Domains

Important Cautions

Naming Conventions

Understanding PDomains

PDomains Overview

PDomain Guidelines

Extended Configuration PDomain Overview

Understanding Extended Configuration PDomains

Base Configuration Overview

Understanding Base Configuration PDomains

Understanding LDoms

Understanding LDom Configurations for Extended Configuration PDomains

Understanding LDom Configurations for Base Configuration PDomains

Determining the Cores Available for LDoms and Zones

Cores Available for Domains and Zones

Example Configuration

Memory Available for LDoms

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 Storage Server Disk Group Layout

Understanding an Example Scenario

Recording Your Existing and Planned Configuration Information

Recording Your Zone Configuration Information

Recording Your Cluster Configuration Information

Recording Your Storage Server Disk Group Layout

Preparing to Configure Zones on Database Domains

Prepare to Configure Zones

Update the Base Software

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 (OEDA)

Example Configuration

Verify Storage Server Disk Space for Additional Zones

Locate the Necessary Files to Set Up Zones

Set Up the OEDA

Start the OEDA

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 Page

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

Creating VNETs

Determining if Additional VNETs Are Needed for a Database Domain

Determine if Additional VNETs Are Needed (Using Specific LDom Information)

Determine if Additional VNETs Are Needed (Using Software Commands)

Locate the Control Domain

Create VNETs for Zones

Delete VNETs

Running the Java OneCommand

Set Up Public Key Authentication for ZFS Storage Controllers

Set Up the Java OneCommand

Run the Java OneCommand

NTP Issue

Creating Additional Links on the IB Storage Network for Zones

Create Additional Links on the IB Storage Network for Zones

Setting Up VLAN Tagging for Zones

Set Up VLAN Tagging for Zones

Index

Set Up VLAN Tagging for Zones

  1. Log in to the nonglobal zone where you want to set up VLAN tagging.
  2. Execute the following commands in the nonglobal zone to stop and disable the automatic startup of the Oracle Clusterware (CRS/HAS) software:
    # crsctl stop crs -f
    # crsctl disable crs
  3. Log out of the nonglobal zone.
  4. Log in to the Database Domain (the global zone) that contains the zones that you created.
  5. Halt the zones that are in this Database Domain:
    # 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 osc01zdbadm02 halt
  6. Identify the client network devices to be used for this VLAN:
    1. Type:
      # 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)
    2. Note the entries for this line under the INTERFACES column.

      In the example output above, those entries would be net4 and net7.

    3. Type:
      # 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
  7. Modify the zone configuration:
    # 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 osc01zdbadm02
    zonecfg: osc01zdbadm02> select anet linkname=net4
    zonecfg: osc01zdbadm02:anet> set vlan-id=13
    zonecfg: osc01zdbadm02:anet> set lower-link=net4
    zonecfg: osc01zdbadm02:anet> end
    zonecfg: osc01zdbadm02> select anet linkname=net7
    zonecfg: osc01zdbadm02:anet> set vlan-id=13
    zonecfg: osc01zdbadm02:anet> set lower-link=net7
    zonecfg: osc01zdbadm02:anet> end
    zonecfg: osc01zdbadm02> verify
    zonecfg: osc01zdbadm02> commit
    zonecfg: osc01zdbadm02> exit
  8. Reboot the zone for the changes to take effect:
    # zoneadm -z zone_management_hostname reboot

    For example:

    # zoneadm -z osc01zdbadm02 reboot
  9. Ping the default gateway to verify that the client network is up.
  10. Log out of the Database Domain (the global zone).
  11. Log in to the nonglobal zone where you set up VLAN tagging.
  12. Execute the following commands in the nonglobal zone to enable and start the automatic startup of the Oracle Clusterware (CRS/HAS) software:
    # crsctl enable crs
    # crsctl start crs