1. Owner's Guide
  2. Preinstallation
  3. Using the Deployment Assistant

4 Using the Deployment Assistant

This chapter describes how to use the Deployment Assistant. The information that you enter in it is used to create the Recovery Appliance configuration files. These files work with installation utility to automate the installation process.

Overview of Oracle Exadata Deployment Assistant

OEDA is used to create configuration files and then implement the configuration on your engineered system.

OEDA is used for Oracle Exadata Database Machine, Oracle Zero Data Loss Recovery Appliance, and Oracle SuperCluster. Starting with Oracle Exadata System Software release 19.1.0, there is a new Web-based interface for OEDA. However, the overall process, described here, is the same regardless of whether you use the Web-based or Java-based user interface.

  • Before your engineered system arrives, do the following:
    1. Work with your network and database administrators to evaluate the current network settings, such as current IP address use and network configuration.
    2. Define the settings for the rack, such as network configuration and backup method.
    3. Download the latest version of OEDA from Oracle Technology Network.
    4. Unzip and run the configuration script on a supported platform, and select the type of system to configure.
    5. Go through every page in OEDA and supply values for all required fields. You cannot advance to the next page if you do not supply all of the required values. You must provide naming details and DNS, NTP, and networking details.

    6. At the end of the dialogue with OEDA, configuration files are generated on the client. The files are also listed at the bottom of the InstallationTemplate.html file that is generated by OEDA. Depending on your engineered system and configuration, OEDA generates all or some of the following files:

      • databasemachine.xml
      • CustomerName-rackname.xml
      • CustomerName-rackname-preconf_GUID.csv
      • CustomerName-rackname-InstallationTemplate.html
      • CustomerName-rackname-platinum.csv
      • CustomerName-rackname-checkip.sh
      • CustomerName-rackname.zip
      • pkey_GUID.csv and pkey_racknamehostname_GUID.csv — if you enabled InfiniBand partitioning for your virtual environments

      The CustomerName-hostname.zip file contains all the generated files.

    7. Review the InstallationTemplate.html file to check the entire configuration and verify all information was entered correctly.
  • Shortly before your engineered system arrives, or is scheduled to be configured, validate the network configuration, as directed by Oracle. See Verifying the Network Configuration Prior to Configuring the Rack.
  • After your engineered system arrives, the configuration files are copied to a database server, and the validation and installation is completed. See unresolvable-reference.html#GUID-01C85D18-A5AE-4285-97C3-DE246FC0BE79.

Accessibility Note: If you are using Oracle Exadata Deployment Assistant with assistive technology (for accessibility) on Windows, you need to enable Java Access Bridge.

Considerations and Requirement for Using OEDA

Review this information before using Oracle Exadata Deployment Assistant (OEDA).

  • ZDLRA Rack ships with the Oracle Linux operating system installed on the servers.

  • The rack name is used to generate host names for all components. For example, if you specify dbm0 for the rack name:

    • The database server host names are like dbm0db01
    • The storage server host names are like dbm0cel01
    • The InfiniBand Network Fabric switch names are like dbm0sw-iba1
    • The RoCE Network Fabric switch names are like dbm0sw-rocea1

    In you have multiple racks, then, each ZDLRA Rack name should be a unique name that identifies the machine. Oracle recommends using dm01 for the first ZDLRA Rack, dm02 for the second, dm03 for the third, and so on. Up to eight ZDLRA Racks can be cabled together without additional InfiniBand switches.

  • The backup method and redundancy protection levels you use determine how to size the Oracle Automatic Storage Management (Oracle ASM) disk groups that are created during installation.

    • If you configure internal backups, then the database backups are created on disk in the Fast Recovery Area in the RECO disk group for the database. The Fast Recovery Area also contains Archived Redo Logs and Flashback Log Files. The division of disk space between the DATA disk group and the RECO disk group is 40% and 60%, respectively.

    • If you configure external backups, then database backups are created on disk or tape media that is external to currently deployed Recovery Appliance. The Fast Recovery Area contains only objects such as Archived Redo Logs and Flashback Log Files.

  • A valid time zone name is required when installing Recovery Appliance. Time zone values provided for Recovery Appliance and Oracle Linux comes from the Time Zone Database. You must specify a valid time zone name for each server using the TZ environment variable. The variable value is of the form Area/Location. For example, America/New_York is a valid TZ value; EST, EDT, and UTC-4 are invalid values.

Related Topics

OEDA Browser-based User Interface

The Web-based interface for Oracle Exadata Deployment Assistant (OEDA) is available starting with the release October 2018 of OEDA. OEDA Web is available for Linux, OSX and Windows.

You can use this interface to enter configuration details for new racks and also import configuration files from the old OEDA interface. Use the Menu button to import and save configurations.

To use the Web-based version of OEDA, perform the following steps.

  1. Download the latest OEDA release from My Oracle Support note 888828.1.

    Extract the contents of the downloaded compressed file. When you extract the contents, it creates a directory based on the operating system, such as linux-x64, macosx-x64, or windows-i586, to store the extracted files. This is referred to as the OEDA_HOME directory.

  2. Install the software.

    Before you can use the Web-based interface, you must install and run the Web Application Server. In the created directory, locate and run the installOedaServer program. You do not have to be logged in as an administrator user to run this program. Use one of the following commands, where the -p option specifies the port number to use:

    • On Linux, Apple, and UNIX:

      ./installOedaServer.sh -p 7072

    • On Microsoft Windows:

      installOedaServer.cmd -p 7072

    Note:

    The examples use port number 7072. However, you can specify any unused port number. It is not recommended to use port numbers less than 1024.

    The installOedaServer program starts the latest version of the OEDA Web Server on the local system.

  3. Access the local OEDA Web Server.

    Once the OEDA Web Server is running, you can access the Web-based application by opening a browser and entering the following URL:

    http://localhost:port_number/oeda

    In the URL, port_number is the network port number that you specified when starting the installOedaServer program. For example, 7072.

The following topics describe the OEDA Web interface:

Using the Browser-based Version of Oracle Exadata Deployment Assistant

Use the deployment assistant for initial configuration, and when adding to an existing deployment. You can import an existing configuration when adding new racks or components.

Have the following available before running the deployment assistant:

  • IP addresses
  • Machine names
  • DNS information
  • NTP information for the rack

The following options are available from the OEDA Menu drop-down list:

  • About: View information about the web interface software.
  • New: Start a new configuration.
  • Import: Import an existing configuration file. The file format is XML.
  • Save: Save the current configuration to an XML file.
  • Diagnostics: Creates a ZIP file that can be used to troubleshoot and diagnosis issues with the OEDA web interface.
  • Preferences: Specify your preferences for how the web interface behaves.
  • Validate: Check the current configuration for completeness and correctness.
  • CheckIp: Checks the IP addresses.
  • Exit: Exit OEDA

The following list describes the configuration information you specify in OEDA:

  1. Select the hardware for the deployment on the Select Hardware page. Also provide customer information on this page.
  2. Enter the management network and private network information on the Rack Networks page.
  3. Specify the user and group configuration on the Users and Groups page. You can choose between Default, Role Separated, or a Custom configuration.
  4. Define the clusters on the Define Clusters page for each cluster.
  5. Define the disk group layout on the Diskgroups page.
  6. Specify the Oracle Database home information for each Oracle home on the Create Database Home page.

  7. Enter the client and backup network information on the Cluster Networks page.

    If an ingest network or replication network is needed, specify their information on the Cluster Networks page.

  8. Configure the email alerts, SNMP alerts, Auto Service Request, Oracle Config Manager, and Enterprise Manager alerting on the Alerting page.
  9. Answer the configuration questionnaire and provide additional information about the deployment in the text field on the Comments page. Information entered in this field appears at the bottom of the InstallationTemplate.html file.
  10. Click Save and Download to create the configuration files. You are prompted to choose a location in which to save a ZIP file to your local computer.
  11. Copy the ZIP file to a directory on the first database server in Oracle Exadata Rack. Use a subdirectory of /u01, such as the /u01/oeda directory. These files are used by the field engineer to configure the Oracle Exadata Rack.

Hardware Selection Page

The hardware selection page identifies the number of racks that you want to deploy at the same time, and the number of storage servers within each rack. Recovery Appliance supports a flexible configuration. From the a minimum configuration X5 through X9M, you can add up to 15 storage servers; up to 11 storage servers for X4.

Note:

Multiple racks must be cabled together according to the Engineered Systems Extending and Multi-Rack Cabling Guide.

The following table describes the hardware choices.

Table 4-1 Hardware Selection Page

Hardware Selection Field Description

Select interconnected hardware to deploy

Lists the available hardware configurations for a rack. Each rack can have 3 to 18 storage servers (cells), depending on your hardware version. Choose one or more racks. You can choose the same type of rack multiple times.

This is your deployment

Lists the hardware selected for your site.

X9M, X8M, X8, or X7 hardware: To deploy two full racks (18 storage servers) and one minimally configured rack (3 storage servers) at the same time:

  1. From the Select Engineered System area, choose the option for Zero Data Loss Recovery Appliance

  2. In the Select Rack area, use the drop-downs ZDLRA Server and Capacity.
    • X9M
    • X8M
    • X8-2
    • X7-2
    • X6-2
    • X5-2
    • X4-2

  3. Select the + (Add selected rack) button.

    The Rack Details page appears.

  4. Fill in details about the rack being deployed.

Choose Operating System Page

Select the operating system to install on the servers in the rack.

For ZDLRA racks, your choices are:

  • All Linux Physical: All compute nodes installed with Oracle Linux without Oracle VMs.

Rack Networks Page

Provide the information necessary to configure the administration and private networks on the rack.

Each compute node and storage server has two network interfaces for administration. One network provides management access to the operating system through the Ethernet interface, and the other network provides access to the Integrated Lights Out Manager (ILOM) through the ILOM Ethernet interface. Default administration network host names are usually changed to meet corporate naming standards or compatibility with existing systems.

In the upper right corner of the Admin Network section is a line that displays the Total IP Addresses that will be configured for the rack. This value is based on the hardware you selected on the Hardware page.

You provide the following information on this page:

Admin Network

Supply values for the following fields.

  • Default gateway for database servers: A check box that indicates that the gateway IP address is the default gateway for the database servers.

  • Gateway: Sets the IP address for the gateway. This field cannot be empty.

  • Start IP Address: Assigns the starting IP address for the administration network of the servers and switches. This field cannot be empty.

    Oracle Exadata Deployment Assistant (OEDA) generates a pool of consecutive IP addresses based on the specified Start IP Address. If consecutive IP addresses are not available, then specific IP addresses can be modified during the configuration process.

    Note:

    These addresses are also assigned to the ILOM ports on the database and storage servers

  • Subnet Mask: Sets the IP address mask for the subnet. You can choose a subnet mask from the drop-down list which contains supported values from 255.0.0.0 to 255.255.255.252

  • Domain Name: Sets the network domain name. Use lowercase letters for the name. This field cannot be empty.

    The domain name specified on this page is used as the domain for all networks. If different domains are used for the client and backup networks, then specify the administration network on this page. The client and backup networks can be changed on the Cluster Networks page.

  • Separate ILOM Network: A check box that indicates that ILOM uses a network that is different from the administration network. If you check this option, you must specify the following additional information for the ILOM network:

    • Gateway

    • Start IP Address

    • Subnet Mask

    • Domain Name

Advanced

If you click the Advanced button in the upper right corner of this page, you can select the following options:

  • Enable Vlan — Allows you to create VLANs on database servers and storage servers for the admin network, ILOM, client and the backup access network. If you select this option, then the following additional fields are visible on the Admin Network page:

    • Vlan — Specifies the VLAN identifier. The value must be a positive integer.

      Note:

      • If your system will use more than 10 VIP addresses in the cluster and you have VLAN configured for the Oracle Clusterware client network, then you must use 3 digit VLAN ids.

      • Do not use 4 digit VLAN ids because the VLAN name can exceed the 15 character operating system interface name limit.

      • If VLAN tagging is to be used, then it must be enabled by the customer after the initial deployment.

        See the My Oracle Support note Enabling VLAN Tagging in Recovery Appliance (Doc ID 2047411.1) for details.

Modify Masks

If you click the button Modify Masks, it opens a pop-up window where you can enter the following information:

  • Compute Name Mask — There is a preview field at the bottom of this window that shows how the generated administration names will appear based on the values you specify for the following fields:

    Note:

    In the following fields, the name prefix can contain alphanumeric characters. The percent signs (%) in the names are replaced by the numbers entered into the Start ID field. At least one percent sign is required in each mask field. If you use more than one percent sign in a mask field, the symbols must be contiguous. For example, you can use test%%-ilom, but not test%new%-ilom.

    • Compute Name Mask: The string used to generate administration names for each database server in this rack. The default string is {Rack Prefix}adm%%, which results in names such as dbm0adm01, dbm0adm02, and so on. This field cannot be empty.

    • Compute Name Start Id: The starting value to use when generating the database server administration names. The default value is 1. This field cannot be empty.

  • Compute ILOM Mask — There is a preview field at the bottom of this section that shows how the generated administration names will appear based on the values you specify for the following fields:

    • Compute ILOM Mask: The string used to generate administration names for each database server ILOM in this rack. The default string is {Compute Name Mask}%-ilom, which results in names such as dbm0adm01–ilom, dbm0adm02–ilom, and so on. This field cannot be empty.

    • ILOM Name Start Id: The starting value to use when generating the ILOM administration names. The default value is the same value as Compute Name Start Id. This field cannot be empty.

      Note:

      Oracle recommends using the same starting IDs for the servers and server ILOMs.

  • Storage Name Mask — There is a preview field at the bottom of this section that shows how the generated administration names will appear based on the values you specify for the following fields:

    • Storage Name Mask: The string used to generate administration names for each storage server. The default string is {Rack Prefix}celadm%%, which results in names such as dbm0celadm01, dbm0celadm02, and so on. This field cannot be empty.

    • Storage Name Start Id: The starting value to use when generating the storage server network names. The default value is 1. This field cannot be empty.

  • Storage ILOM Mask — There is a preview field at the bottom of this section that shows how the generated server names will appear based on the values you specify for the following fields:

    • Storage ILOM Mask: The string used to generate administration names for each storage server ILOM in this rack. The default string is {Storage Name Mask}%-ilom, which results in names such as dbm0celadm01–ilom, dbm0celadm02–ilom, and so on. This field cannot be empty.

    • Storage Name Start Id: The starting value to use when generating the ILOM network names. The default value is the same value as Storage Name Start Id. This field cannot be empty.

      Note:

      Oracle recommends using the same starting IDs for the servers and server ILOMs.

  • Switches and PDUs

    • Cisco Switch — The string used to generate the administration name for the Cisco Management Switch in this rack. The default value is {Rack Prefix}sw-adm%, which results in names such as dbm0sw-adm1.

    • RDMA Network Fabric Spine Switch — The string used to generate the administration names for the spine switch, if your rack is configured with one. The default value is {Rack Prefix}sw-ibs%, which results in names such as dbm0sw-ibs1.

    • RDMA Network Fabric Leaf Switch — The string used to generate the administration names for the lower RDMA Network Fabric Leaf switch in this rack. The default value is {Rack Prefix}sw-typea%, which results in names such as dbm0sw-iba1 or dbm0sw-rocea0.

    • RDMA Network Fabric Leaf Switch — The string used to generate the administration names for the upper RDMA Network Fabric Leaf switch in this rack. The default value is {Rack Prefix}sw-typeb%, which results in names such as dbm0sw-ibb1 or dbm0sw-roceb0.

    • PDU-A — The string used to generate the administration names for Power Distribution Unit (PDU) A in this rack. The default value is {Rack Prefix}sw-pdua%, which results in names such as dbm0sw-pdua1.

    • PDU-B — The string used to generate the administration names for Power Distribution Unit (PDU) B in this rack. The default value is {Rack Prefix}sw-pdub%, which results in names such as dbm0sw-pdub1.

After you have entered the custom network name masks, click the Save button at the bottom of the page. To undo your changes, you can either close the window or click the Cancel button at the bottom of the page.

Admin network Review and Edit

After you save the input provided for the admin network, the Admin network Review and Edit section appears above the Private Network section. Here you can view all the IP addresses and administration names that will be configured for your rack, and modify them if needed. If you make any modifications to the administration name or their IP addresses, click the Update button when you have finished to save your changes.

If you are connected to the same network on which the rack will be deployed, you can check the validity of the network configuration data. Click the Lookup IP button at the bottom of this section. OEDA will display any invalid IP addresses.

Private Network

Provide the information necessary to configure the private network on the rack.

In the upper right corner of the Private Network section is a line that displays the Total IP Addresses that will be configured for the rack. This value is based on the hardware you selected on the Hardware page.

  • Enable active bonding — Specifies whether active bonding should be enabled for only the private network on compute nodes. By default this option is selected.

  • Start IP Address: Assigns the starting IP address for the private network of the servers. This field cannot be empty.

    OEDA generates a pool of consecutive IP addresses based on the specified Start IP Address. If consecutive IP addresses are not available, then specific IP addresses can be modified during the configuration process.

  • Subnet Mask: Sets the IP address mask for the subnet. You can choose a subnet mask from the drop-down list. The list contains supported values from 255.255.240.0 to 255.255.255.252

  • Domain Name: Sets the network domain name. The default value is the domain name value entered for the Admin Network. Use lowercase letters for the name. This field cannot be empty.

If you click the Modify Masks button, it opens a popup window where you can modify the generated names for the database and storage server private names. There are preview fields at the bottom of this window that shows how the generated private names will appear based on the values in the name mask fields. The default strings used to generate the private names are:

  • Compute private name mask: {Rack prefix}adm%%-priv, which results in names such as dbm0adm01–priv, dbm0adm02–priv, and so on

  • Cell private name mask: {Rack Prefix}celadm%%-priv, which results in names such as dbm0celadm01–priv, dbm0celadm02–priv, and so on.

After you have entered the custom private network name masks, click the Save button at the bottom of the page. To undo your changes, you can either close the window or click the Cancel button at the bottom of the page.

After you have entered the private network configuration information, click the Save button at the bottom of the page.

Private network Review and Edit

After you save the input provided for the private network, the Private network Review and Edit section appears above the User(s) and Groups section. Here you can view all the IP addresses and private host names that will be configured for your rack, and modify them if needed. If you make any modifications to the private host names or their IP addresses, click the Update button at the bottom of this section when you have finished to save your changes.

Users and Groups

Provide information about the operating system users to use when installing Oracle software. The user information you provide is saved in a collection, which can be referenced later in the configuration process.

The first selection is the type of users you want to define. Your options are:

  • Default: Use the default user configuration. This option creates a single operating system user to own the Oracle Grid Infrastructure and Oracle Database software.

If you plan to have multiple installations of Oracle software on your rack that require different operating system users, then, after you have entered the user information, you can click the Add group (+) button. The information you entered is saved with the label UserCollection-1_id. A new section appears on the page where you can enter information for an additional group of software installation users with distinct names and permissions. The new user information collection is automatically assigned the label UserCollection-2_id.

If you want to remove a user information collection, click the Delete Group (-) button next to the ID of the group you want to remove.

After you have entered all the user information, click the Save button at the lower right side of the page to continue.

Default User Information

For ZDLRA racks, the Default option is selected automatically, and the only values you can modify are the User Id and Group Id.

  • User Name: The operating system user name for the database software owner. This field cannot be empty. The default value is oracle.

  • User Id: The operating system identification number for this user. This field cannot be empty. The default value is 1001.

  • Home Directory: The user home directory. This field cannot be empty. The default value is /home/oracle.

  • User Type: This field is not available if you select the Default option. The named user will be created as the Grid and Database software owner.

  • Group Name: The name of the operating system group that will be the DBA group. All the operating system privileges necessary for managing the Oracle Database software are granted to this group. This field cannot be empty. The default value is dba.

  • Group Id: The operating system identification number for this group. This field cannot be empty. The default value is 1001.

  • Group Type: This field is not available if you select the Default option. The named group will be created as a DBA GROUP group.

  • Group Name: The name of the operating system group that will be the installation owner group. All the operating system privileges necessary for installing the Oracle Grid Infrastructure and Oracle Database software are granted to this group. This field cannot be empty. The default value is oinstall.

  • Group Id: The operating system identification number for this group. This field cannot be empty. The default value is 1002.

  • Group Type: This field is not available if you select the Default option. The named group will be created as an OINSTALL group.

Save

After you have entered all the information for the racks being configured, click the Apply button. Be sure to go to the Menu and select Save.

Define Clusters

More than one cluster can be defined for a hardware racks. Larger environments support multiple clusters. Each cluster requires a minimum of two physical or virtual compute nodes, and three storage cells. You cannot mix physical and virtual compute nodes in the same cluster.

Provide the information for the first cluster and assign nodes to the cluster using the Add Node (>) button to move selected nodes or the Add All Nodes (>>) button to assign all available nodes to the cluster. If you want to add a second cluster, then click the Add Cluster (+) button next to the cluster name tab.

Provide the following information for each cluster in the rack:

  • Cluster Name: Is the cluster name, which must be unique across your enterprise. The cluster name is case-insensitive, must be at least one character long and no more than 15 characters in length, must be alphanumeric, cannot begin with a numeral, and may contain hyphens (-). Underscore characters (_) are not allowed. This field cannot be empty.
  • Inventory Location: Is the Oracle inventory (oraInventory) directory path. The default value is /u01/app/oraInventory.
  • Grid Home Owner: Use the drop-down list to select the collection of user information previously created on the Users page. By default, the first user collection is selected.
  • Grid Infrastructure Home Location: Is the Oracle Grid Infrastructure directory path, which typically includes the software release number. The default value is /u01/app/release_number/grid, for example, /u01/app/18.2.0.0/grid. This value is automatically set depending on the value selected for Cluster Version. You can overwrite the default value.

  • Cluster Version: After you select the nodes to assign to this cluster, you will be able to select the cluster version from the drop-down list. The list contains all supported versions of the Oracle Grid Infrastructure. Choose any of the supported values.

  • Base Directory: Is the base directory for the Oracle Grid Infrastructure software. The default value is /u01/app/grid.

After you assign nodes to the cluster, you can modify the default values for each cluster, if needed. The following customer information fields appear below the Available Machines list:

  • Customer Name: Is the customer name. The default value is the value you provided earlier on the Hardware page in the Customer Details section.
  • Application: Is the application name or description. The default value is the value you provided earlier on the Hardware page in the Customer Details section.
  • Region: Is the geographical location of the rack. The default value is the value you provided earlier on the Hardware page in the Customer Details section.
  • Time zone: Is the time zone in which the rack is located. The default value is the value you provided earlier on the Hardware page in the Customer Details section.
  • DNS Servers: Are the IP addresses for the DNS servers. The default values are the values you provided earlier on the Hardware page in the Customer Details section.
  • NTP Servers: Are the IP addresses for the NTP servers. The default values are the values you provided earlier on the Hardware page in the Customer Details section.

Diskgroups

Define the Oracle ASM disk groups and their sizes for each cluster in the rack.

If you specified more than one cluster, use the tabs at the top of this page to select each cluster and provide the disk group information.

For ZDLRA racks, the following information is used:

  • Diskgroup name: Automatically set to CATALOG and DELTA
  • Diskgroup Type: Automatically set to CATALOG and DELTA
  • Redundancy: The CATALOG disk group is configured to use HIGH redundancy. For the DELTA disk group, you can choose either HIGH or NORMAL (default). HIGH reduces the usable space.
  • Size: The CATALOG disk group has a size of Default, and the DELTA disk group has a size of 95%.
  • Size Type: The disk group sizes are specified as percent.

After you have entered the values for the disk groups and clicked Save, the following fields are then populated with the estimated values:

  • CATALOG disk group — The usable space and raw size are set to default.
  • DELTA disk group — The values depends on the hardware selected.

Database Home

Provide information for configuring the Oracle Database software installation.

For ZDLRA hardware, you should accept all default values for Oracle Database software installation:

  • Select Cluster: The cluster on which to deploy the Oracle Database software. This is a drop-down list that is populated with the cluster names specified on the Clusters page. By default, the first cluster is selected.
  • Database Home Name: A name given to the Oracle Database software installation. This name identifies the program group associated with a particular home and the Oracle services installed on this home. The Oracle home name must be between 1 to 127 characters long, and can include only alphanumeric characters and underscores. This field cannot be empty. The default value is DbHome_1.
  • Database Home Version: The version of the Oracle Database software to install in the cluster. Choose the value from the drop-down list. The most recent version is selected by default.
  • Database Home Location: A directory path where the Oracle Database software will be installed. This value is set automatically based on the value specified for the Database Home Version. For example, if you select version 12.1.0.2 DBBP13, then the Database Home Location is set to /u01/app/oracle/product/12.1.0.2/dbhome_1. After specifying the Database Home Version, you can type over the default value to use a different location, if needed. This field cannot be empty.
  • Base Directory: The Oracle Base directory location. The Oracle Database binary home is located underneath the Oracle base path. You can use the same Oracle base directory for multiple installations of Oracle software. If different operating system users install Oracle software on the same system, then you must create a separate Oracle base directory for each installation owner. This field cannot be empty. The default value is /u01/app/oracle.

When you have finished configuring the Oracle home information, click Apply and then Save from the Menu.

Database

Provide information about the databases to create in the specified database home directories.

  • Database Name: Is the name of the database you want to create in the database home. The database name (DB_UNIQUE_NAME) portion is a string of no more than 30 characters that can contain alphanumeric, underscore (_), dollar ($), and pound (#) characters, but must begin with an alphabetic character. No other special characters are permitted in a database name. The DB_NAME parameter for a database is set to the first 8 characters of the database name. The domain portion of the global database name (DB_DOMAIN) uses the value you provided for the domain when configuring the networks. The values for DB_UNIQUE_NAME.DB_DOMAIN in its entirety must be unique within the enterprise. This field cannot be empty.

    DB_UNIQUE_NAME is filled in from previous domain name selection and does not change. The database name field must be unique across the enterprise Recovery Appliances. The resulting Database Name pulls previously entered domain name and appends to user selected DB_UNIQUE_NAME.

  • Database Home: Is the name of the Database Home in which you want to create the database. This value is automatically populated with the first home specified on the Database Home page.

When you have finished configuring the database configuration information, click Save from the Menu.

Cluster Networks

For ZDLRA racks, configure the Ingest and Replication networks.

Applications access the database servers or compute nodes through the client Ethernet network using Single Client Access Name (SCAN) and Oracle RAC Virtual IP (VIP) addresses. Oracle databases running in Oracle VM guests on Oracle Exadata Database Machine are accessed through the client Ethernet network as defined in this section. Client network configuration in both the management domain (dom0) and user domains (domUs) is done automatically when the OEDA installation tool creates the first user domain during initial deployment.

In the upper right corner of the Cluster Networks page is a line that displays the Total IP Addresses that will be configured for the rack. This value is based on the hardware you selected on the Hardware page. At the top of the section are tabs, each designating one of the clusters you specified on the Clusters page.

Advanced

At the very top of the Cluster Networks section, before any network configuration details, there is a button for Advanced configuration. If you click this button, the Advanced options window appears. Depending on the system configuration entries that you have made so far, you may see the following options:

  • Enable Vlan: Select this option if there is a need for virtual deployments on the rack to access additional virtual local area networks (VLANs) on the network, such as enabling network isolation across user domains.

    If you select this option, then in the client or ingest network configuration details, an additional field appears:

    • Vlan: Specify the VLAN identifier. The VLAN ID is a numeric value between 1 and 4095. You also need to select the Bonded option to enable VLAN. If the Backup or Replication network uses VLAN, then the Client or Ingest network must also be configured to use VLAN. If the VLAN ID field is empty, then VLAN is not enabled.

    Note:

    For all networks, you are responsible for configuring VLAN on the switch.

Admin Network

For some Exadata rack configurations, at the top of the Cluster Networks section, on the right side, is a check box Enable Admin network. You can use this to optionally configure an Admin network inside the virtual compute servers. If you select this option, you must specify the network configuration by using the following:

  • Default gateway for database servers: Select this option if the gateway IP address is the default gateway for all database servers

  • Defines Domain hostname for database servers: Select this option if you want the name used for the Admin network on a virtual compute server to be used as the host name for the virtual compute server. If you do not select this option, then the virtual compute server uses the network name assigned to the client network as the host name.

  • Gateway: Sets the IP address for the gateway for the client network. This field cannot be empty.

  • Start IP Address: Specify the first IP address that will be used for client access to the database servers. This value is filled in automatically, based on the value supplied for the gateway. OEDA generates a pool of consecutive IP addresses based on the specified Start IP Address. If consecutive IP addresses are not available, then specific IP addresses can be modified using the Modify Masks button. This field cannot be empty.

  • Subnet Mask: Specify the IP address mask for the subnet. You can choose a subnet mask from the drop-down list which contains supported values from 255.0.0.0 to 255.255.255.252.

  • Domain Name: Specify the network domain name for client connections. Use lowercase letters for the name. This field cannot be empty. For Exadata Cloud configurations, this value is provided for you.

After you have specified all the configuration details for the Admin network, click the Apply button at the bottom of the section, or click Modify Masks to customize the network configuration.

Modify Masks

If you click the Modify Masks button, it opens a pop-up window where you can modify the generated names for the client or ingest network. There are preview fields at the bottom of each section that show how the generated network names will appear based on the values in the name mask fields. The default strings used to generate the network names are:

  • Client Access Details:

    • Name:

      • ZDLRA racks: Enter {Rack prefix}ingest%%, which results in names such as {Rack prefix}ingest01, {Rack prefix}ingest02, and so on

    • Start id: Specify the number to start with when generating sequential names.

  • Vip details:

    • Name:

      • ZDLRA racks: Enter {Rack prefix}ingest%%-vip, which results in names such as {Rack prefix}ingest01–vip, {Rack prefix}ingest02–vip, and so on

    • Start id: Specify the number to start with when generating sequential names.

  • Scan details: The configuration details for the single client access network (SCAN) listener

    • Name: Enter the name of the listener. The default value is {Rack prefix}-scan1.

    • Port: Specify the network port which the SCAN listener monitors for incoming connection requests. The default value is 1521.

After you have completed the modifications to the client or ingest network configuration, click the Apply button at the bottom of the Client Network Masks window. To undo your changes, you can either close the window or click the Cancel button at the bottom of the Client Network Masks window.

Client Network or Ingest Network

Provide the following information to configure either the Client networks for Exadata or the Ingest networks for ZDLRA racks.

For Exadata racks and ZDLRA racks:

  • Default gateway for database servers: Select this checkbox if the gateway IP address is the default gateway for all database or compute servers.

  • Default hostname for database servers: Select this checkbox if the network names define the host names for the database or compute servers.

  • Network Media: Select the network cable type, either Optical or Copper.

  • Bonded: For X7 or later racks and Exadata Cloud, only bonded networks are supported.

    For X6 and earlier racks of Exadata and ZDLRA, or Exadata Cloud, select this option if using a bonded network.

  • LACP: Check this option to enable the Link Aggregation Control Protocol (LACP) on the network.

  • Gateway: Sets the IP address for the gateway for the network. This field cannot be empty.

  • Start IP Address: Set the first IP address that will be used for access to the database servers on this network. This value is filled in automatically, based on the value supplied for the gateway. OEDA generates a pool of consecutive IP addresses based on the specified Start IP Address. If consecutive IP addresses are not available, then specific IP addresses can be modified using the Modify Masks button. This field cannot be empty.

  • Subnet Mask: Set the IP address mask for the subnet. You can choose a subnet mask from the drop-down list which contains supported values from 255.0.0.0 to 255.255.255.252.

  • Domain Name: Set the network domain name for client or ingest connections. Use lowercase letters for the name. This field cannot be empty. For Exadata Cloud configurations, this value is provided for you.

After you have specified all the configuration details for the client or ingest network configuration, click the Apply button at the bottom of the section.

Client network or Ingest network Review and Edit

After you save the input provided for the client or ingest network, the Client network Review and Edit or Ingest network Review and Edit section appears. Here you can view all the host names and IP addresses that will be configured for client access to the database servers in the rack. You can modify any of the settings if needed. If you make any modifications to the administration name or their IP addresses, click the Apply button when you have finished to save your changes.

If you are connected to the same network on which the rack will be deployed, you can check the validity of the network configuration data. Click the Lookup IP Address button at the bottom of this section. OEDA will display any invalid IP addresses.

Backup Network or Replication Network

In the upper right corner of the Backup Network section for Exadata is the option Enable Backup network. For ZDLRA racks, this option is labeled Enable replication network. If you select this option, it enables the configuration of a network dedicated to backups or replication.

In the upper right corner of the Backup Network or Replication Network section is a line that displays the Total IP Addresses that will be configured for each cluster. At the top of the section are tabs, each designating one of the clusters you specified on the Clusters page.

Provide the following information to configure the backup network or replication network for each cluster:

  • Shared client network port: (Not available for Exadata Cloud) Select this option if the client and backup networks use the same physical network cables. This option requires that both networks have VLAN enabled and share the same network interface cards (NIC). If this option is not selected, then you must use one set of cables for the client network and a separate set of cables for the backup network.

  • Network Media: (For Exadata X6 racks and earlier and ZDLRA racks) Select the network cable type, either Optical or Copper.

  • Bonded: (Not available on X7 or later racks or Exadata Cloud) Select this option to use network bonding. For X7 or later racks for Exadata and ZDLRA, and Exadata Cloud, only bonded networks are supported.

  • LACP: Check this option to enable the Link Aggregation Control Protocol (LACP) on the network.

  • Gateway: Set the IP address for the gateway for the network. This field cannot be empty.

  • Start IP Address: Set the first IP address that will be used for the network. This value is filled in automatically, based on the value supplied for the gateway. OEDA generates a pool of consecutive IP addresses based on the specified Start IP Address. If consecutive IP addresses are not available, then specific IP addresses can be modified using the Modify Masks button. This field cannot be empty.

  • Subnet Mask: Set the IP address mask for the subnet. You can choose a subnet mask from the drop-down list which contains supported values from 255.0.0.0 to 255.255.255.252.

  • Domain Name: (Not available for Exadata Cloud) Set the network domain name for network connections. Use lowercase letters for the name. This field cannot be empty.

After you have specified all the configuration details for the network configuration, click the Apply button at the bottom of the section.

If you click the Modify Masks button, it opens a pop-up window where you can modify the generated names for the network. There is a preview field at the bottom of the window that shows how the generated network names will appear based on the values in the name mask fields. The default strings used to generate the network names are:

  • Client Access Details:

    • Name:

      • ZDLRA racks: Enter {Rack prefix}ingest%%, which results in names such as {Rack prefix}ingest01, {Rack prefix}ingest02, and so on

    • Start id: Set the number to start with when generating sequential names.

  • Vip details:

    • Name:

      • ZDLRA racks: Enter {Rack prefix}ingest%%-vip, which results in names such as {Rack prefix}ingest01–vip, {Rack prefix}ingest02–vip, and so on

    • Start id: Set the number to start with when generating sequential names.

  • Scan details: Are the configuration details for the single client access network (SCAN) listener.

    • Name: Specify the name of the listener. The default value is {Rack prefix}-scan1.

    • Port: Specify the network port which the SCAN listener monitors for incoming connection requests. The default value is 1521.

After you have completed the modifications to the backup or replication network configuration, click the Apply button at the bottom of the Backup Network Masks or Replication Network Masks page. To undo your changes, you can either close the window or click the Cancel button at the bottom of the window. The buttons might be out of view are require scrolling down in the window to see.

After you have specified all the configuration details for the backup or replication network configuration, click the Apply button at the bottom of the Backup Network or Replication Network section.

Backup or Replication network Review and Edit

If you enabled the Backup network or the Replication network option, then this section appears after you save the input provided for the network. Here you can view all the host names and IP addresses that will be configured for the network. You can modify any of the settings if needed. If you make any modifications, then click the Update button when you have finished to save your changes.

If you are connected to the same network on which the rack will be deployed, you can check the validity of the network configuration data. Click the Lookup IP Address button at the bottom of this section. OEDA will display any invalid IP addresses.

Alerting

In this section you configure alerting

You use the following methods for receiving or handling alerts:

  • Email with Simple Mail Transfer Protocol (SMTP)

  • Simple Network Management Protocol (SNMP)

  • Oracle Auto Service Request (ASR)

  • Oracle Configuration Manager

  • Oracle Enterprise Manager

For ZDLRA, you must configure at least one of the following alerting options:

  • Oracle ASR

  • SMTP or SNMP alerting

  • Oracle Configuration Manager

  • Oracle Platinum Services

The alerting options include:

  • Enable Email Alerting: Enables alerts to be delivered automatically through email.

    • Name: Sets the SMTP email user name that appears in the alert notifications, for example, Oracle Exadata Database Machine. This field cannot be empty.

    • Email Address: Sets the SMTP email address that sends alert notifications, for example, dm0db01@example.com. This field cannot be empty.

    • SMTP Server: Sets the SMTP email server used to send alert notifications, for example, mail.example.com. This field cannot be empty.

    • Port: Sets the SMTP email server port used to send alert notifications, for example, 25 or 465. This field cannot be empty.

    • Send Email Alerts to: Sets the email address for the recipients of the alerts. You can click the Add Email (+) button to add additional recipients. You can use the Remove Email (-) button to remove an email address that you added.

  • Enable SNMP Alerting: Enables using SNMP to deliver alerts.

    • SNMP Server: Sets the SNMP server host name, for example, snmp.example.com. This field cannot be empty.

      Note:

      Additional SNMP targets may be defined after installation of the Exadata rack. Refer to the ALTER CELL CellCLI command or the ALTER DBSERVER DBMCLI command.

    • Port: Sets the SNMP email server port used to send alert notifications. The default value is 162. This field cannot be empty.

    • Community: Sets the SNMP server community. The default value is public. This field cannot be empty.

  • Enable ASR Alerting: Enables Oracle Auto Service Request (ASR). Oracle ASR is designed to automatically open service requests when specific rack hardware faults occur.

    Oracle recommends that you install Oracle ASR Manager on an external, standalone server. The server must be installed have connectivity to the Exadata servers or Recovery Appliance nodes and an outbound Internet connection using HTTPS or an HTTPS proxy. This server must run an Oracle Solaris or Linux operating system.

    • ASR Manager Request: The host name of the Oracle ASR Manager server. This field cannot be empty.

    • HTTP Proxy Host: If you want to enable an HTTP proxy to upload to Oracle ASR, then specify the proxy server host name.

    • Contact Name: The name of the technical contact person for the rack. This field cannot be empty.

    • Contact Email: The e-mail address of the technical contact for the rack. This field cannot be empty.

    • HTTP Proxy User: If you want to enable an HTTP proxy to upload to Oracle ASR, then specify the proxy server user name.

    • Port: If you want to enable an HTTP proxy to upload to Oracle ASR, then specify the HTTP proxy server port number.

    • My Oracle Support Account Name: The email address of the My Oracle Support account. This field cannot be empty.

  • Enable OCM Alerting: Enables Oracle Configuration Manager to collect configuration information.

    Oracle Configuration Manager is used to collect configuration information and upload it to an Oracle repository, for access when needed by Oracle Support Services.

    • MOS Email Address: The My Oracle Support account (email address) to receive updates from My Oracle Support. This field cannot be empty.

    • HTTP Proxy Host: If you use an HTTP proxy to upload configuration information to the Oracle repository, then specify the proxy server host name. The proxy server may be between the following:

      • Database (compute) servers and Oracle (applicable when you do not have Oracle Support Hub)

      • Database (compute) servers and Oracle Support Hub (applicable when you have only Oracle Support Hub)

      • Oracle Support Hub and Oracle

      If passwords are needed, then provide them during installation.

    • Support Hub Hostname: The Support Hub server host name. Oracle Support Hub allows Oracle Configuration Manager instances to connect to a single internal port (the Oracle Support Hub), and upload configuration data. This eliminates the need for each individual Oracle Configuration Manager instance in the database servers to access the Internet. This field cannot be empty.

    • HTTP Proxy User: If you want to enable an HTTP proxy to upload configuration information to the Oracle repository, then specify the HTTP proxy server user name.

    • Hub User Name: The Oracle Support Hub operating system user name. This field cannot be empty.

    • Port: If you want to enable an HTTP proxy to upload configuration information to the Oracle repository, then specify the HTTP proxy server port number. The default value is 80.

  • Enable EM Alerting: Enables alerts in Oracle Enterprise Manager.

    Oracle Enterprise Manager Cloud Control or Oracle Enterprise Manager Grid Control is used to monitor the rack. When Oracle Enterprise Manager agents are installed on the rack, they can send information to the Oracle Management Server. If you do not have an existing Oracle Management Server, then install a new Oracle Management Server on a separate host.

    • EM Home Base Location: The base directory for the Oracle Enterprise Manager agents installed on the database or compute servers. The default value is /u01/app/oracle/product/EMbase. This field cannot be empty.

    • OMS HTTPS Upload Port: The port the Oracle Enterprise Manager agent should use to upload information to the Oracle Management Server. The default value is 4900. This field cannot be empty.

    • OMS Host Name: The name of the server or host where the Oracle Management Server repository is installed. This field cannot be empty.

Tape Library Connectivity

On ZDLRA racks only, you can configure network connection information for tape backups.

You can configure the tape library for ZDLRA only if you use Oracle Secure Backup as the media manager for tape backups. You can manually configure other media managers as clients only.

  • Use Tape: Select this option if you plan to use Oracle Secure Backup as the media manager for tape backups. Then you can enter the configuration details.

  • Vip IP Address: The IP address of the VIP.

  • Vip Name: The alphanumeric name of the VIP. The default value is osbadminvip.{domain_name}.

    If you are connected to the same network on which the rack will be deployed, you can check the validity of the tape library address information. Click the Lookup IP button at the bottom of this section. OEDA will display any invalid IP addresses.

  • Number of tape libraries: The number of tape libraries available to the ZDLRA rack. The default is 1. All tape libraries must be hosted in the same domain. If you select a value greater than 1, a new tab appears for each tape library. You can enter the configuration details for each tape library on the separate tabs.

  • ACLS ACS API: Use the Automated Cartridge System Library Software (ACSLS) API for the tape library. Fill out the following additional fields:

    • ACSLS Server: The name of the server running ACSLS

    • ACS ID: The ACS identification number

  • ACSLS FC-SCSI: Use the Automated Cartridge System Library Software (ACSLS) FC-SCSI for the tape library. Fill out the following additional fields:

    • ACSLS Server: The name of the server running ACSLS

    • Logical Library ID: The logical library identification number

  • SCSI: Use SCSI to communicate with the tape library. The Simple SAN tape library has no configuration fields. This is the default option.

Comments

Enter any additional information about the deployment in the text field.

For Oracle Exadata Rack, this section contains a list of questions about the configuration to help ensure a smooth installation and configuration process for your rack. You can type in the answers in the text field.

For all deployments, you can provide additional comments about your environment or the deployment in this field.

When you have finished providing the information, click Save and Download. You are prompted to save a ZIP file containing the deployment and configuration files. The main configuration files are:

Note:

Do not edit or modify any of the generated files.

  • Customer_name-rack_prefix.xml: This is the main configuration file used by the installation process.

  • Customer_name-rack_prefix-checkip.sh: A script you run on the installed rack to verify all the IP addresses you specified in OEDA are available and ready for deployment.

  • Customer_name-rack_prefix-InstallationTemplate.html: This file is an HTML report of all the data captured in the web user interface. The questions and answers from the Comments section of OEDA appear at the bottom of this file.

  • Customer_name-rack_prefix-platinum.csv: This file is used when first imaging of the nodes in the rack by Oracle Advanced Customer Support.

  • Customer_name-rack_prefix-preconf_pkey.csv: If you configured InfiniBand partitioning, this file is created. This file is used when PKEY security is enabled in the interconnect.