Owners Manual

Dell Integrated Systems for Oracle Database 2.0 - Owner’s Guide 1.1

Oracle Private A: /etc/sysconfig/network-scripts/ifcfg-eth5

Oracle Private B: /etc/sysconfig/network-scripts/ifcfg-eth7

NOTE: For the preassigned IP addresses for the private interfaces in the database nodes,

see the

3.1.3 Static IP addresses of Database and DAAD

nodes section.

During Oracle grid installation, select the above two preconfigured network interfaces for

the private interconnect.

4.3 Management server configuration

The management server comes preinstalled with the following setup:

 Windows Server 2012 R2 Standard Edition (SE) as the base physical OS.

 Two Hyper-V VMs:

- WinVM: This is a Windows-based VM that is preinstalled with Windows Server

2012 R2 SE as the guest OS. This VM is created primarily for installing

management software at the customer site.

- LinVM: This is a Linux-based VM that is preinstalled with Oracle Linux 6.6

running the Red Hat Compatible Kernel as the guest OS. This VM is primarily

used for the configuration of the DISOD components before it is shipped out

to the customer. It also provides for a Linux-based environment to remotely

access any of the DISOD hardware components, if needed.

Refer to Appendix

B DISOD authentication settings

for the default authentication settings.

NOTE: For information about installation and configuration of the various management

software in order to manage and monitor DISOD solution rack, see

Dell

Integrated Systems for Oracle Database –Oracle Enterprise Manager Integration Guide

4.3.1 Base physical OS configuration settings

The base OS on the management server is preconfigured with the following settings:

 Windows Server 2012 R2 64-bit is preinstalled with Hyper-V feature enabled.

 OS partition is set to the maximum HDD available disk space of 497 GB.

 All firewalls (Public, Private, and Domain) are disabled.

 Computer name is set to:

dMan-

where,

is the unique Service Tag of the management server and

dMan indicates DISOD Management.

 Two Hyper-V VMs with names WinVM and LinVM are created.

 For network configuration details, see the

3.1.2 Management server network

configuration

section.