Oracle® Big Data Appliance

Configuration Worksheets

Release 2 (2.1)

E40654-03

May 2013

The Oracle Big Data Appliance Configuration Worksheets identify the information and decisions required when installing Oracle Big Data Appliance racks and expansion kits. This document contains the following sections:

- Configuration Process Overview

- Installation Types

- Network Configuration Worksheets

- Server Group 1 Worksheets

- Server Group 2 Worksheets

- Server Group 3 Worksheets

- Sample Installation Template

- Documentation Accessibility

1 Configuration Process Overview

The configuration worksheets will help you plan your installation of Oracle Big Data Appliance with the network and database administrators and your Oracle representative. It is important that you complete the worksheets and provide them to your Oracle representative before receiving Oracle Big Data Appliance racks or expansion kits to avoid delaying the installation.

Your Oracle representative uses the information entered in these worksheets to create an Installation Template. Use the Installation Template to confirm that the configuration settings of your Oracle Big Data Appliance were entered correctly. You can make site-specific adjustments to the Installation Template in consultation with your Oracle representative. Some settings cannot be changed after the appliance is operational, so make your decisions carefully.

Note:

- Oracle Big Data Appliance uses Cloudera's Distribution including Apache Hadoop (CDH). A Hadoop cluster on Oracle Big Data Appliance is called a CDH cluster.

- The terms appliance and rack refer to both Oracle Big Data Appliance and Oracle Big Data Appliance X3-2.

To configure Oracle Big Data Appliance:

1. Read this document and the Oracle Big Data Appliance Owner's Guide to understand the networking requirements.

2. Identify your current management network.

3. Identify your current client access network.

4. If you have multiple appliances, then choose between connecting them into a single CDH cluster or creating one or more independent CDH clusters on each appliance. You can configure a cluster across multiple racks.
A cluster must have at least six servers. In larger clusters, the number of servers must be a multiple of 3.

5. Open the Oracle Big Data Appliance Configuration Worksheets in Adobe Reader or Adobe Acrobat. The document is in editable form.

Note:
Do not use a PDF reader such as Foxit or Preview to edit the file. It may corrupt the file, such that other programs cannot read it.

6. Complete one copy of the Network Configuration Worksheets for each rack or expansion kit being configured.

7. Complete one copy of the Server Group worksheets for each new cluster. For example, if you are configuring a single rack with one new CDH cluster and one extension to an existing cluster, then complete just the Server Group 1 Worksheets. If you are configuring a single rack with two new CDH clusters, then complete both the Server Group 1 Worksheets and Server Group 2 Worksheets, and so on.

8. Give the completed configuration worksheets to your Oracle representative. The information in these worksheets is used to generate an Installation Template, which your Oracle representative will give to you.

9. Verify that the information in the Installation Template is correct. To make any adjustments, contact your Oracle representative.

10. Configure your existing network to use the new IP addresses and host names supplied in the Installation Template.

11. Run the preinstall-checkip.sh script that your Oracle representative gives to you. This script checks your existing network for conflicts with the IP addresses listed in the Installation Template.

Note:
Correct any network problems discovered by preinstall-checkip.sh before installation begins. Network problems can cause extensive delays. See the Oracle Big Data Appliance Owner's Guide.

12. Review the network and IP address requirements described in the Oracle Big Data Appliance Owner's Guide.

13. Run the network connections to the planned location for Oracle Big Data Appliance.

14. Inform your Oracle representative when you have completed these steps.

Note:
The network administrator should be available on-site during the installation of Oracle Big Data Appliance (1 to 2 days). Otherwise, a problem with the customer network may cause extended delays.

See Also:

- Oracle Big Data Appliance Owner's Guide for more information about the configuration settings

- Oracle Big Data Appliance Site Checklists for site preparations before installation

2 Installation Types

You use the Oracle Big Data Appliance Configuration Worksheets for a full rack, starter rack, or expansion kit. You must identify the hardware and the desired configuration of the servers. The installation type controls the possible server layout options:

- Full Rack – 18 servers
Configured as a single group of 18 servers, two groups of 9 servers each, two groups of 6 and 12 servers, or three groups of 6 servers

- Starter Rack – 6 servers
Configured only as a single group of 6 servers

- Starter Rack and Kit – 12 servers
Configured as a single group of 12 servers or two groups of 6 servers

- First Expansion Kit – 6 servers
Configured only as a single group of 6 servers

- Second Expansion Kit – 6 servers
Configured only as a single group of 6 servers

- Two Expansion Kits – 12 servers
Configured as a single group of 12 servers or two groups of 6 servers

Table 1 Server Group Configuration

Installation Type

Server Layout

3 Network Configuration Worksheets

The network configuration worksheets identify the naming conventions for the hardware and the IP addresses used on your network:

- General Properties for the Rack

- Network Properties for the Rack

- Network Properties for the Servers

- Network Properties for the Switches

- Network Properties for the PDUs

- Advanced Network Configuration

3.1 General Properties for the Rack

In Table 2, enter the names for the hardware components and other basic information.

Using Standardized Host Names

The rack name is used in the assignment of standardized host names for all Oracle Big Data Appliance servers. The host name for all servers is in this format:

racknameNodeNN.domain

In this syntax:

- NN is the position number of the server node in the rack (01 to 18).

- domain is the domain name.

For multirack clusters, Oracle recommends that the racks be named clusternameM, where M is the index of the rack in the cluster. You enter the cluster name in the Server Group worksheets.

For example, if the cluster name is bda and the domain name is example.com, then the fully qualified host name of the server at the bottom of the first rack is bda1node01.example.com. For the top server in the third rack of this cluster, the host name is bda3node18.example.com.

The host names must have fewer than 38 characters, which can be ASCII letters (a to z and A to Z), numbers (0 to 9), and hyphens (-) only. Do not begin or end the name with a hyphen. You use the host names to address the servers over the client network interface.

The host names on the other networks have the following formats. You use these formats when connecting over the other networks:

- For short host names over the administration network:
racknameNodeNN-adm

- For the private InfiniBand network host names:
racknameNodeNN-priv

- For the Oracle Integrated Lights Out Manager (ILOM) host names:
racknameNodeNN-ilom

- For the switch host names:
racknamesw-ibN

In this syntax:

- NN is the position number of the server in the rack (01 to 18).

- N is 1, 2, or 3, depending on the switch location in the rack.

Oracle recommends for a cluster of multiple racks that rackname be clusternameM, where M is the index of the rack in the cluster.

Using Customized Host Names

You can change the suffixes used for the different network interfaces.

To assign a unique host name to each server, provide your Oracle representative with a list of all individual host names. You must also enter the rack name, domain name, and time zone fields in Table 2.

Table 2 General Rack Configuration Worksheet

Property

Example

Setting

Customer NameFoot 1

Example Inc

Rack NameFootref 1: For a cluster of multiple racks, enter the primary rack name first.

bda1

Server Base Name

node

Admin Access Suffix

-adm

Private Name Suffix

-priv

ILOM Name Suffix

-ilom

Switch Base Name

sw

Time ZoneFootref 1

America/New York

Domain NameFootref 1

example.com

Are you connecting this rack to another rack through the InfiniBand fabric, such as another Oracle Big Data Appliance rack or an Oracle Exadata Database Machine?

no

Footnote 1 Required. All other properties in this worksheet have default values.

3.2 Network Properties for the Rack

In Table 3, enter up to four IP addresses for the Domain Name System (DNS) and Network Time Protocol (NTP) servers, and up to four search domains. By default, these values are used for both the client and administrative networks.

If these networks are isolated on your system and use different DNS and NTP servers, or different domains, or both, then complete Table 3 for the client network and Table 6 for the administrative network.

Table 3 Network Configuration Worksheet for the Rack

Property

Setting

DNS Servers (1 to 4)

NTP Servers (1 to 4)

Search Domains (1 to 4)

3.3 Network Properties for the Servers

In Table 4, enter the network properties for the individual servers.

Each server in the appliance is assigned an IP address for the administrative 1 gigabit Ethernet (1 GbE) network, the private InfiniBand network, the 10 GbE client access network, and Oracle ILOM. The IP addresses of the servers are assigned sequentially beginning with the first IP address for node01.

If you cannot allocate sequential IP addresses on a network, then provide your Oracle representative with a list of IP addresses instead of just the starting IP address.

The Oracle ILOM IP addresses are on the administrative network. The administrative and Oracle ILOM IP addresses must be on the same subnet and use the same netmask and gateway.

For starter racks and expansion kits, the IP addresses on the administrative network cannot be in the range of 192.168.1.1 to 18 or 192.168.1.101 to 118. This restriction provides for the future installation of an expansion kit.

Table 4 Network Configuration Worksheet for the Servers

Property

Setting

Administrative Network: First of 6, 12, or 18 x N sequential IP addresses, where N is the number of racks being configured.

For example, if you configure three racks in a cluster, then enter the first of 54 (18 x 3) sequential IP addresses.

Administrative Network and ILOM Netmask

Administrative Network and ILOM Gateway

Private InfiniBand Network: First of 6, 12, or 18 x N sequential IP addresses, where N is the number of racks being configured.

Optional: Defaults to 192.168.10.1Foot 1

Private InfiniBand Network Netmask

Optional: Defaults to 255.255.255.0Footref 1

Client Network: First of 6, 12, or 18 x N sequential IP addresses, where N is the number of racks being configured.

Client Network Netmask

Client Network Gateway

ILOM Network: First of 6, 12, or 18 x N sequential IP addresses, where N is the number of racks being configured.

Footnote 1 If you are connecting this rack to another rack through the InfiniBand fabric, see the following note.

Note:
If you are connecting this rack to another rack through the InfiniBand fabric, then ensure that:

- The InfiniBand IP addresses of all servers are unique, including the servers in other Oracle engineered systems.

- All InfiniBand IP addresses are on the same network.
For example, if you connect an Oracle Big Data Appliance rack to Oracle Exadata Database Machine, then you must use the same netmask on the InfiniBand networks for both systems. Moreover, after you apply this netmask to the InfiniBand IP addresses of the Exadata database servers, the Exadata storage servers, and the Oracle Big Data Appliance servers, all IP addresses are in the same subnet.

3.4 Network Properties for the Switches

In Table 5, enter the IP addresses of the Cisco Catalyst Ethernet switch and the first of three Sun InfiniBand switches. For Sun Fire X4270 M2-based racks only, enter an address for the keyboard-video-mouse (KVM) switch. The IP addresses of the switches are on the administrative network.

Complete Table 5 only for new racks, and not for expansion kits.

Table 5 Network Configuration Worksheet for the Switches

Property

Setting

KVM Switch IP (Sun Fire X4270 M2-based racks only): One IP address, multiplied by the number of racks.

For example, if you configure three racks in a cluster, then enter the first of three consecutive IP addresses.

Cisco Switch IP: One IP address, multiplied by the number of racks.

InfiniBand Switch IP: First of three sequential IP addresses, multiplied by the number of racks in the cluster.

For example, if you configure three racks in a cluster, then enter the first of nine consecutive IP addresses.

3.5 Network Properties for the PDUs

In Table 6, enter the IP addresses for the two power distribution units (PDUs). The IP addresses of the PDUs are on the administrative network.

Complete Table 6 only for new racks, and not for expansion kits.

Table 6 Network Configuration Worksheet for the PDUs

Property

Setting

PDU A: One IP address, multiplied by the number of racks.

For example, if you configure three racks in a cluster, then enter the first of three consecutive IP addresses.

PDU B: One IP address multiplied by the number of racks.

3.6 Advanced Network Configuration

In Table 6, you can provide configuration details for the administrative network, if they are different from the values you specified in Table 3. In most installations, the administrative and client networks share the same domains, DNS and NTP servers, and so forth. When that is the case, you can leave all or part of Table 6 blank, and allow the values you specified in Table 3 to be used for both the administrative and client networks.

The administrative network does not require access to DNS servers, although Oracle Big Data Appliance uses them if they are available. However, at least one NTP server must also be accessible.

Table 7 Advanced Network Configuration Worksheet

Property

Setting

Administrative Domain

Are the administrative host names in the DNS?

Administrative DNS Servers (1 to 4)

Administrative NTP Servers (1 to 4)

Administrative Search Domains (1 to 4)

4 Server Group 1 Worksheets

Complete the following spreadsheets to configure and activate the optional software components for server group 1 on Oracle Big Data Appliance:

- Installed Components for Server Group 1

- Auto Service Request for Server Group 1

- Users and Groups for Server Group 1

- Cloudera Manager Email Alerts for Server Group 1

- Oracle Enterprise Manager Cloud Control for Server Group 1

See Also:
Oracle Big Data Appliance Owner's Guide for a description of the software configuration options

4.1 Installed Components for Server Group 1

In Table 8, identify the applications to activate and configure.

Optional Software

Oracle Big Data Connectors and Oracle NoSQL Database are optional components. You must activate them now if you plan to use them. Otherwise, you can save disk space for other uses by not activating them.

Oracle NoSQL Database Community Edition is included in the license for Oracle Big Data Appliance. Oracle NoSQL Database Enterprise Edition requires a separate license You must have this license to install Enterprise Edition on Oracle Big Data Appliance.

Disk space allocated to Oracle NoSQL Database is not available for the Hadoop Distributed File System (HDFS). When you configure Oracle NoSQL Database, you have a choice between a smaller and a larger amount of total disk space to allocate for its use, which is proportional to the size of the cluster:

- Full rack (18 servers): 54 or 108 TB

- Half rack (9 servers): 27 or 54 TB

- Starter rack with one in-rack extension (12 servers): 36 or 72 TB

- Starter rack (6 servers): 18 or 36 TB

Oracle Big Data Connectors requires a separate license. You must have this license to install the connectors on Oracle Big Data Appliance. If you have a license, then you can decide whether to configure Oracle Data Integrator agent during the initial software installation, so that it is up and running immediately.

Table 8 Software Components Configuration Worksheet for Server Group 1

Property

Example

Setting

This group of servers is

Note: If you are adding this server group to an existing cluster, then leave blank all other configuration settings for the group.

a new Hadoop or NoSQL DB cluster

CDH Cluster NameFoot 1

bda

Are Oracle Big Data Connectors licensed?

Yes

Configure Oracle Data Integrator agent?

No

Install Oracle NoSQL Database?

Enterprise Edition

Total disk space to allocate for Oracle NoSQL Database (in terabytes)

0

Footnote 1 Required. All other properties in this worksheet have default values.

4.2 Auto Service Request for Server Group 1

In Table 9, enter the configuration settings for Auto Service Request (ASR).

ASR monitors the health of Oracle Big Data Appliance hardware and automatically submits a service request when it detects a fault. Although you can opt out of this program, Oracle recommends that you enable ASR.

Before Oracle Big Data Appliance can be configured for ASR, ASR Manager must be configured to run on a separate server outside of Oracle Big Data Appliance. Software on Oracle Big Data Appliance must be able to connect to ASR Manager and route to the Internet, either directly or through a proxy, to send event information that automatically opens service requests.

Table 9 Auto Service Request Configuration Worksheet for Server Group 1

Property

Example

Setting

Enable Auto Service Request?

Yes

ASR Manager host address

asr-host.example.com

ASR Manager port number

162

ASR Server root password: Leave blank only if you will be available during the installation to provide it.

4.3 Users and Groups for Server Group 1

The installation software defines users, groups, and passwords. If you do not provide the passwords in Table 10 for the configuration files, then you must enter them manually during the installation.

The Oracle IDs must match those of a connected Oracle Exadata Database Machine to support the network file system (NFS) protocol between the two systems.

Table 10 Users and Groups Configuration Worksheet for Server Group 1

Description

Example

Value

Cloudera Manager admin passwordFoot 1

root operating system passwordFootref 1

oracle operating system passwordFootref 1

oracle user ID

1000

oinstall group ID

1001

dba group ID

1002

MySQL Database administration passwordFootref 1

MySQL Database password for Oracle Data IntegratorFootref 1

Footnote 1 Required for all racks. Leave blank only if you will be available during the installation.

4.4 Cloudera Manager Email Alerts for Server Group 1

In Table 11, provide information about the email server (SMTP) on the network. The user name and password fields appear only when authentication is set to yes.

This information enables Cloudera Manager to send email alerts when it detects a problem in the CDH cluster. If this information is omitted, then no email alerts will be sent.

Table 11 Email Configuration Worksheet for Server Group 1

Property

Example

Value

Email Server host address

router.example.com

Email Server port number

25

Email Server uses authentication?

Yes

Email Server user name

smtp.user

Email Server password

Does the email server use SSL?

Yes

Email alert recipients

admin@example.com

4.5 Oracle Enterprise Manager Cloud Control for Server Group 1

In Table 12, provide information about Oracle Enterprise Manager installed with the system monitoring plugin for Oracle Big Data Appliance.

For Enterprise Manager to monitor the appliance, the agents must be deployed and validated on Oracle Big Data Appliance.

The Cloud Control user must have sufficient privileges to perform administrative emcli commands. Typically, this user is sysman.

The Agent Registration password is part of the security setup of Enterprise Manager. To obtain the password in Enterprise Manager, click Setup at the top right of the window, Security, and then Registration Passwords.

Table 12 Enterprise Manager Configuration Worksheet for Server Group 1

Property

Example

Value

Enable Enterprise Manager?

Yes

Cloud Control host

oem-host.example.com

OMS port

14487

Cloud Control user name

sysman

Cloud Control password

Cloud Control management agent registration password

5 Server Group 2 Worksheets

Configure the following worksheets for server group 2 if you are creating multiple clusters on Oracle Big Data Appliance:

- Installed Components for Server Group 2

- Auto Service Request for Server Group 2

- Users and Groups for Server Group 2

- Cloudera Manager Email Alerts for Server Group 2

- Oracle Enterprise Manager Cloud Control for Server Group 2

Note:
Leave these worksheets blank if you are configuring a single group.

5.1 Installed Components for Server Group 2

In Table 13, identify the applications to activate and configure.

Table 13 Software Components Configuration Worksheet for Server Group 2

Property

Setting

This group of servers is

Note: If you are adding this server group to an existing cluster, then leave blank all other configuration settings for the group.

CDH Cluster NameFoot 1

Are Oracle Big Data Connectors licensed?

Configure Oracle Data Integrator agent?

Install Oracle NoSQL Database?

Total disk space to allocate for Oracle NoSQL Database (in terabytes)

Footnote 1 Required. All other properties in this worksheet have default values.

5.2 Auto Service Request for Server Group 2

In Table 14, enter the configuration settings for Auto Service Request (ASR).

Table 14 Auto Service Request Configuration Worksheet for Server Group 2

Property

Setting

Enable Auto Service Request?

ASR Manager host address

ASR Manager port number

ASR Server root password: Leave blank only if you will be available during the installation to provide it.

5.3 Users and Groups for Server Group 2

In Table 15, enter passwords for the users defined during installation. Otherwise, you must enter them manually during the installation process.

The Oracle IDs must match those of a connected Oracle Exadata Database Machine to support the network file system (NFS) protocol between the two systems.

Table 15 Users and Groups Configuration Worksheet for Server Group 2

Description

Value

Cloudera Manager admin passwordFoot 1

root operating system passwordFootref 1

oracle operating system passwordFootref 1

oracle user ID

oinstall group ID

dba group ID

MySQL Database administration passwordFootref 1

MySQL Database password for Oracle Data IntegratorFootref 1

Footnote 1 Required for all racks. Leave blank only if you will be available during the installation.

5.4 Cloudera Manager Email Alerts for Server Group 2

In Table 16, provide information about the email server (SMTP) on the network. The user name and password fields appear only when authentication is set to yes.

Table 16 Email Configuration Worksheet for Server Group 2

Property

Value

Email Server host address

Email Server port number

Email Server uses authentication?

Email Server user name

Email Server password

Does the email server use SSL?

Email alert recipients

5.5 Oracle Enterprise Manager Cloud Control for Server Group 2

In Table 17, provide information about Oracle Enterprise Manager installed with the system monitoring plugin for Oracle Big Data Appliance.

Table 17 Enterprise Manager Configuration Worksheet for Server Group 2

Property

Value

Enable Enterprise Manager?

Cloud Control host

OMS port

Cloud Control user name

Cloud Control password

Cloud Control management agent registration password

6 Server Group 3 Worksheets

Complete the following worksheets if you are creating three clusters on Oracle Big Data Appliance:

- Installed Components for Server Group 3

- Auto Service Request for Server Group 3

- Users and Groups for Server Group 3

- Cloudera Manager Email Alerts for Server Group 3

- Oracle Enterprise Manager Cloud Control for Server Group 3

Note:
Leave these worksheets blank if you are configuring only one or two groups.

6.1 Installed Components for Server Group 3

In Table 18, identify the applications to activate and configure.

Table 18 Software Components Configuration Worksheet for Server Group 3

Property

Setting

This group of servers is

Note: If you are adding this server group to an existing cluster, then leave blank all other configuration settings for the group.

CDH Cluster NameFoot 1

Are Oracle Big Data Connectors licensed?

Configure Oracle Data Integrator agent?

Install Oracle NoSQL Database?

Total disk space to allocate for Oracle NoSQL Database (in terabytes)

Footnote 1 Required. All other properties in this worksheet have default values.

6.2 Auto Service Request for Server Group 3

In Table 19, enter the configuration settings for Auto Service Request (ASR).

Table 19 Auto Service Request Configuration Worksheet for Server Group 3

Property

Setting

Enable Auto Service Request?

ASR Manager host address

ASR Manager port number

ASR Server root password: Leave blank only if you will be available during the installation to provide it.

6.3 Users and Groups for Server Group 3

In Table 20, enter passwords for the users defined during installation. Otherwise, you must enter them manually during the installation process.

The Oracle IDs must match those of a connected Oracle Exadata Database Machine to support the network file system (NFS) protocol between the two systems.

Table 20 Users and Groups Configuration Worksheet for Server Group 3

Description

Value

Cloudera Manager admin passwordFoot 1

root operating system passwordFootref 1

oracle operating system passwordFootref 1

oracle user ID

oinstall group ID

dba group ID

MySQL Database administration passwordFootref 1

MySQL Database password for Oracle Data IntegratorFootref 1

Footnote 1 Required for all racks. Leave blank only if you will be available during the installation.

6.4 Cloudera Manager Email Alerts for Server Group 3

In Table 21, provide information about the email server (SMTP) on the network. The user name and password fields appear only when authentication is set to yes.

Table 21 Email Configuration Worksheet for Server Group 3

Property

Value

Email Server host address

Email Server port number

Email Server uses authentication?

Email Server user name

Email Server password

Does the email server use SSL?

Email alert recipients

6.5 Oracle Enterprise Manager Cloud Control for Server Group 3

In Table 22, provide information about Oracle Enterprise Manager installed with the system monitoring plugin for Oracle Big Data Appliance.

Table 22 Enterprise Manager Configuration Worksheet for Server Group 3

Property

Value

Enable Enterprise Manager?

Cloud Control host

OMS port

Cloud Control user name

Cloud Control password

Cloud Control management agent registration password

7 Sample Installation Template

This section provides an example of an Installation Template.

7.1 Network Configuration

General

Property

Value

Customer Name

Example Inc

Rack Name

bda1

Region

America

Timezone

America/New_York

Domain

example.com

Property

Value 1

Value 2...

DNS Server

172.16.100.45

NTP Server

172.16.215.62

Search Domains

example.com

us.example.com

Server Network Info

Type

Netmask

Gateway

Administrative - eth0

255.255.255.0

10.18.113.1

Private - bondib0

255.255.255.0

Client Access - bondeth0

255.255.255.0

10.18.114.1

BDA will not be connected to any other racks via InfiniBand.

Server Position

eth0 hostname

eth0 IP address

bondib0 IP hostname

...

-admin.example.com

-example.com

01

bda1node01-adm

10.18.113.10

bda1node01-priv

...

02

bda1node02-adm

10.18.113.11

bda1node02-priv

...

03

bda1node03-adm

10.18.113.12

bda1node03-priv

...

...

...

...

...

...

17

bda1node17-adm

10.18.113.26

bda1node17-priv

...

18

bda1node18-adm

10.18.113.27

bda1node18-priv

...

Switches

Type

Hostname

IP Address

KVM Switch

bda1sw-kvm

Cisco Switch

bda1sw-ip

10.18.113.144

NM2-36p Spine Switch

bda1sw-ib1

10.18.113.145

NM2-GW Leaf Switch 1

bda1sw-ib2

10.18.113.146

NM2-GW Leaf Switch 2

bda1sw-ib3

10.18.113.147

PDUs

Type

Hostname

IP Address

PDU A

bda1-pdu1

10.18.113.151

PDU B

bda1-pdu2

10.18.113.152

Advanced Network Configuration

Property

Value 1

Value 2...

Property

Value

Administrative Domain

admin.example.com

Administrative hosts

are listed in DNS servers.

Admin DNS Servers, if different

Admin NTP Servers, if different

Admin Search Domains, if different

7.2 Software Configuration

Server Group 1 (6 Servers)

Cluster bda

Property

Value

Oracle Big Data Connectors

are being licensed

Oracle Data Integrator Agent

will be installed

Oracle NoSQL Database

will be installed with 54 TB total diskspace - Community Edition

Property

Value

Oracle Auto Service Requests

will be configured

Oracle ASR server

asr-host.example.com:162

Oracle ASR Server root password

password

Property

Value

Cloudera Manager admin password

password

root operating system password

password

oracle operating system password

password

MySQL administration password

password

MySQL password for Oracle Data Integrator

password

Property

Value

Property

Value

Property

Value

oracle user ID

1000

oinstall group ID

1001

dba group ID

1002

Property

Value

Email server (SMTP) host

router.example.com:25   does not use SSL

Email server (SMTP) user name

smtp.user

Email server (SMTP)

password

Email alert recipients

admin@example.com

Property

Value

Oracle Enterprise Manager

will be configured

Oracle Cloud Control server

oem-host.example.com:14487

Oracle Cloud Control server user name

sysman

Oracle Cloud Control server password

password

Oracle Cloud Control registration password

password

8 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Big Data Appliance Configuration Worksheets, Release 2 (2.1)

E40654-03

Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Cloudera, Cloudera CDH, and Cloudera Manager are registered and unregistered trademarks of Cloudera, Inc.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.