Contributors: Doug Archambault, Leo Agranonik, Andrew Babb, Bharat Baddepudi, Michael Belef, Nilesh
Choudhury, Henry Chow, Kevin Closson, Bob Cyphers, Ravindra Dani, Boris Erlikhman, Jaime Figueroa,
Gurmeet Goindi, Roger Hansen, Shrikumar Hariharasubrahmanian, Kevin Jernigan, Sarat Karkarla, Leslie
Keller, Frank Kobylanski, Poojan Kumar, René Kundersma, Robert S. Lee, Sue Lee, Jennifer Leung, Yang
Liu, Juan Loaiza, Barb Lundhild, Catherine Luu, Varun Malhotra, Bagish Mishra, Valarie Moore, Philip
Newlan, Adrian Ng, Dan Norris, Michael Nowak, Bharat Paliwal, Umesh Panchaksharaiah, Hector Pujol,
Sugam Pandey, Dmitry Potapov, Darryl Presley, Vince Pulice, Ashish Ray, Samitha Samaranayake, Richard
Scales, Olly Sharwood, Jia Shi, Kesavan Srinivasan, Mahesh Subramaniam, Michelle Sun, Krishnadev
Telikicherla, Cliff Thomas, Alex Tsukerman, Shreyas Udgaonkar, Kothanda Umamageswaran, Doug Utzig,
James Viscusi, Vern Wagman, Zheren Zhang
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, then 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 agencyspecific 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 about 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 unless otherwise
set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.
Page 3
Contents
1
Preface
Audiencex
Documentation Accessibilityx
Related Documentationx
Conventionsxii
Site Requirements for Oracle Exadata Database Machine and
Oracle Exadata Storage Expansion Rack
1.1General Environmental Requirements1-1
1.1.1General Environmental Requirements for Oracle Exadata Database
Machine X6-2, X6-8, and Later1-1
1.1.2General Environmental Requirements for Oracle Exadata Database
Machine X5-21-1
1.1.3General Environmental Requirements for Oracle Exadata Database
Machine X5-81-4
1.1.4General Environmental Requirements for Oracle Exadata Database
Machine X4-21-5
1.1.5General Environmental Requirements for Oracle Exadata Database
Machine X4-8 with Exadata Storage Server X5-2 Servers1-8
1.1.6General Environmental Requirements for Oracle Exadata Database
Machine X4-8 Full Rack1-10
1.1.7General Environmental Requirements for Oracle Exadata Database
Machine X3-21-11
1.1.8General Environmental Requirements for Oracle Exadata Database
Machine X3-8 Full Rack with Exadata Storage Server X4-2L Servers1-14
1.1.9General Environmental Requirements for Oracle Exadata Database
Machine X3-8 Full Rack with Exadata Storage Server X3-2 Servers1-16
1.1.10General Environmental Requirements for Oracle Exadata Database
Machine X2-21-17
1.1.11General Environmental Requirements for Oracle Exadata Database
Machine X2-8 Full Rack1-18
1.1.12General Environmental Requirements for Oracle Exadata Storage
Expansion Rack X6-2 and later1-20
1.1.13General Environmental Requirements for Oracle Exadata Storage
Expansion Rack X5-21-20
iii
Page 4
1.1.14General Environmental Requirements for Oracle Exadata Storage
Expansion Rack X4-21-22
1.1.15General Environmental Requirements for Oracle Exadata Storage
Expansion Rack X3-21-23
1.1.16General Environmental Requirements for Oracle Exadata Storage
Expansion Rack with Exadata Storage Server with Sun Fire X4270 M2
Servers1-25
1.1.17General Environmental Requirements for Single Servers1-26
1.2Space Requirements1-28
1.2.1Receiving and Unpacking Requirements1-29
1.2.2Maintenance Access Requirements1-33
1.3Flooring Requirements1-34
1.4Electrical Power Requirements1-34
1.4.1PDU Power Requirements1-34
1.4.2Facility Power Requirements1-43
1.4.3Circuit Breaker Requirements1-43
1.4.4Grounding Guidelines1-43
1.5Temperature and Humidity Requirements1-44
1.6Ventilation and Cooling Requirements1-45
1.7Network Connection and IP Address Requirements for Oracle Exadata
Database Machine1-47
1.7.1Network Connection Requirements for Oracle Exadata Database
Machine1-47
1.7.2DNS Configuration for Oracle Exadata Database Machine1-50
1.7.3IP Address Requirements for Oracle Exadata Database Machine1-51
1.7.3.1Calculating the IP Address Requirements when Using Oracle VMs
1-69
1.8Network Connection and IP Address Requirements for Oracle Exadata
Storage Expansion Rack1-72
1.9Ensuring Site is Ready1-75
2
Understanding the Network Requirements for Oracle Exadata
Database Machine
This guide describes Oracle Exadata Database Machine for online transaction
processing (OLTP) and enterprise data warehousing. It includes information about site
planning and configuration, as well as physical, electrical, and environmental
specifications.
This guide is intended for Oracle Exadata Database Machine customers and those
responsible for data center site planning, configuration, and maintenance of Oracle
Exadata Database Machine.
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 that have purchased support 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.
Related Documentation
In addition to the Oracle Exadata Database Machine documentation set, the following
guides contain hardware information for Oracle Exadata Database Machine:
•Oracle Exadata Database Machine System Overview
•Oracle Exadata Database Machine Security Guide
•Oracle Engineered System Safety and Compliance Guide, Compliance Model No.:
ESY27
•Oracle Exadata Database Machine Extending and Multi-Rack Cabling Guide
interface elements associated with an action,
or terms defined in text or the glossary.
placeholder variables for which you supply
particular values.
Monospace type indicates commands within a
paragraph, URLs, code in examples, text that
appears on the screen, or text that you enter.
command run as the
that is run as the
root
oracle
user.
user.
xii
Page 13
1
Site Requirements for Oracle Exadata
Database Machine and Oracle Exadata
Storage Expansion Rack
This chapter describes the site requirements for Oracle Exadata Database Machine,
and Oracle Exadata Storage Expansion Rack.
Note:
For ease of reading, the name "Oracle Exadata Rack" is used when
information refers to both Oracle Exadata Database Machine and Oracle
Exadata Storage Expansion Rack.
Related Topics:
•Site Checklists (page A-1)
1.1 General Environmental Requirements
The following sections describe the general environmental requirements for Oracle
Exadata Racks.
1.1.1 General Environmental Requirements for Oracle Exadata
Database Machine X6-2, X6-8, and Later
For Oracle Exadata Database Machine X6-2 and later environmental requirements,
such as weight, acoustic level, power, cooling, and air flow, use the Oracle Exadata
Configuration Assistant, available on Oracle Technology Network:
1.1.2 General Environmental Requirements for Oracle Exadata
Database Machine X5-2
The environmental requirements for Oracle Exadata Database Machine X5-2 depend
on the size of the system. Table 1-1 (page 1-2) shows the general environmental
requirements for Oracle Exadata Database Machine X5-2. The other sections in this
chapter provide detailed information.
1-1
Page 14
Chapter 1
General Environmental Requirements
Table 1-1 Environmental Requirements for Oracle Exadata Database Machine
X5-2
Environmental
Component
Weight
See Also:
"Flooring
Requirements
(page 1-34)"
Acoustic levels86 db(A)85 db(A)83 db(A)83 db(A)
Power
See Also:
"Electrical Power
Requirements
(page 1-34)"
Oracle Exadata
Database
Machine X5-2
Full Rack
•Extreme
Flash drives:
804.9 kg
(1774 lbs)
•High
capacity
drives: 874.8
kg (1928
lbs))
•Extreme
Flash drives
Maximum:
15.7 kVA
Typical: 11.0
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
15.6 kVA
Typical: 10.9
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X5-2
Half Rack
•Extreme
Flash drives:
525.9 kg
(1160 lbs)
•High
capacity
drives: 560.9
kg (1236 lbs)
•Extreme
Flash drives
Maximum:
8.5 kVA
Typical: 5.9
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
8.4 kVA
Typical: 5.9
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X5-2
Quarter Rack
•Extreme
Flash drives:
366.3 kg
(808 lbs)
•High
capacity
drives: 381.2
kg (841 lbs)
•Extreme
Flash drives
Maximum:
4.2 kVA
Typical: 3.0
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
4.2 kVA
Typical:
2.9kVA
(varies
based on
application
load)
Oracle Exadata
Database
Machine X5-2
Eighth Rack
•Extreme
Flash drives:
366.3 kg
(808 lbs)
•High
capacity
drives: 381.2
kg (841 lbs)
•Extreme
Flash drives
Maximum:
3.5 kVA
Typical: 2.4
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
34 kVA
Typical: 2.4
kVA (varies
based on
application
load)
Air flow front-to-back (subject
to actual data center
environment)
See Also: "Temperature and
Humidity Requirements
(page 1-44)", and
"Ventilation and Cooling
Requirements (page 1-45)"
Extreme Flash drives:
•Max: 16.4 kW (16.7 kVA)
•Typical: 11.5 kW (11.7
kVA)
High capacity drives:
•Max: 16.2 kW (16.6 kVA)
•Typical: 11.4 kW (11.6
kVA)
Extreme Flash drives:
•Max: 55,935 BTU/hour
(59,012 kJ/hour)
•Typical: 39,155 BTU/hour
(41,308 kJ/hour)
High capacity drives:
•Max: 55,410 BTU/hour
(58,457 kJ/hour)
•Typical: 38,787 BTU/hour
(40,920 kJ/hour)
Extreme Flash drives:
•Max: 2590 CFM
•Typical: 1813 CFM
High capacity drives:
•Max: 2565 CFM
•Typical: 1796 CFM
Oracle Exadata Database
Machine X5-8 Half Rack
Extreme Flash drives:
•Max: 9.5 kW (9.7 kVA)
•Typical: 6.7 kW (6.8 kVA)
High capacity drives:
•Max: 9.5 kW (9.7 kVA)
•Typical: 6.6 kW (6.8 kVA)
Extreme Flash drives:
•Max: 32,436 BTU/hour
(34,220 kJ/hour)
•Typical: 22,705 BTU/hour
(23,954 kJ/hour)
High capacity drives:
•Max: 32,323 BTU/hour
(34,101 kJ/hour)
•Typical: 22,626 BTU/hour
(23,871 kJ/hour)
Extreme Flash drives:
•Max: 1502 CFM
•Typical: 1051 CFM
High capacity drives:
•Max: 1496 CFM
•Typical: 1048 CFM
1.1.4 General Environmental Requirements for Oracle Exadata
Database Machine X4-2
The environmental requirements for Oracle Exadata Database Machine X4-2 depend
on the size of the system. Table 1-3 (page 1-6) shows the general environmental
requirements for Oracle Exadata Database Machine X4-2. The other sections in this
chapter provide detailed information.
1-5
Page 18
Chapter 1
General Environmental Requirements
Table 1-3 Environmental Requirements for Oracle Exadata Database Machine
X4-2
Environmental
Component
Weight
See Also:
"Flooring
Requirements
(page 1-34)"
Acoustic levels93 db(A)89 db(A)85 db(A)85 db(A)
Power
See Also:
"Electrical Power
Requirements
(page 1-34)"
Oracle Exadata
Database
Machine X4-2
Full Rack
852.8 kg (1880
lbs)
•High
performance
drives
Maximum:
12.4 kVA
Typical: 8.7
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
11.4 kVA
Typical: 8.1
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X4-2
Half Rack
525.3 kg (1158
lbs)
•High
performance
drives
Maximum:
6.8 kVA
Typical: 4.8
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
6.3 kVA
Typical: 4.4
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X4-2
Quarter Rack
365.6 kg (806
lbs)
•High
performance
drives
Maximum:
3.4 kVA
Typical: 2.5
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
3.2 kVA
Typical: 2.3
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X4-2
Eighth Rack
365.6 kg (806
lbs)
•High
performance
drives
Maximum:
3.1 kVA
Typical: 2.2
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
2.9 kVA
Typical: 2.1
kVA (varies
based on
application
load)
Requirements (page 1-44)", and "Ventilation
and Cooling Requirements (page 1-45)"
Air flow front-to-back (subject to actual data
center environment)
See Also: "Temperature and Humidity
Requirements (page 1-44)", and "Ventilation
and Cooling Requirements (page 1-45)"
IP Addresses
See Also: "Network Connection and IP
Address Requirements for Oracle Exadata
Database Machine (page 1-47)"
Network drops
See Also: "Network Connection and IP
Address Requirements for Oracle Exadata
Database Machine (page 1-47)"
External connectivity
See Also: "Network Connection and IP
Address Requirements for Oracle Exadata
Database Machine (page 1-47)"
•High performance drives
Maximum: 51,200 BTU/hour (54,000 kJ/
hour)
Typical: 36,400 BTU/hour (38,400 kJ/
hour)
•High capacity drives
Maximum: 49,110 BTU/hour (52,000 kJ/
hour)
Typical: 34,400 BTU/hour (36,300 kJ/
hour)
•High performance drives
Maximum: Approximately 2,410 CFM
Typical: Approximately 1,700 CFM
•High capacity drives
Maximum: Approximately 2,280 CFM
Typical: Approximately 1,600 CFM
44 for Ethernet network, assuming single
cluster
Up to 36 for InfiniBand network
Minimum of 5 network drops
16 x 1 GbE Ethernet ports
16 x 10 GbE Ethernet SFP+ ports
12 InfiniBand ports
1.1.7 General Environmental Requirements for Oracle Exadata
Database Machine X3-2
The environmental requirements for Oracle Exadata Database Machine X3-2 depend
on the size of the system. Table 1-6 (page 1-12) shows the general environmental
requirements for Oracle Exadata Database Machine X3-2. The other sections in this
chapter provide detailed information.
1-11
Page 24
Chapter 1
General Environmental Requirements
Table 1-6 Environmental Requirements for Oracle Exadata Database Machine
X3-2
Environmental
Component
Weight
See Also:
"Flooring
Requirements
(page 1-34)"
Acoustic levels87 db(A)84 db(A)81 db(A)81 db(A)
Power
See Also:
"Electrical Power
Requirements
(page 1-34)"
Oracle Exadata
Database
Machine X3-2
Full Rack
871.4 kg (1921
lbs)
•High
performance
drives
Maximum:
12.1 kVA
Typical: 8.6
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
11.1 kVA
Typical: 7.8
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X3-2
Half Rack
543.9 kg (1199
lbs)
•High
performance
drives
Maximum:
6.6 kVA
Typical: 4.7
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
6.1 kVA
Typical: 4.3
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine X3-2
Quarter Rack
368.8 kg (813
lbs)
•High
performance
drives
Maximum:
3.3 kVA
Typical: 2.4
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
3.1 kVA
Typical: 2.2
kVA (varies
based on
application
load)
Oracle Exadata
Database
Machine Eighth
Rack
368.8 kg (813
lbs)
•High
performance
drives
Maximum:
3.0 kVA
Typical: 2.1
kVA (varies
based on
application
load)
•High
capacity
drives
Maximum:
2.8 kVA
Typical: 2.0
kVA (varies
based on
application
load)
Full Rack with Exadata Storage Server
X3-2 Servers
Network drops
See Also: "Network Connection and IP
Address Requirements for Oracle Exadata
Database Machine (page 1-47)"
External connectivity
See Also: "Network Connection and IP
Address Requirements for Oracle Exadata
Database Machine (page 1-47)"
Minimum of 5 network drops
16 x 1 GbE Ethernet ports
16 x 10 GbE Ethernet SFP+ ports
12 InfiniBand ports
1.1.10 General Environmental Requirements for Oracle Exadata
Database Machine X2-2
Chapter 1
The environmental requirements for Oracle Exadata Database Machine X2-2 depend
on the size of the system. Table 1-9 (page 1-17) shows the general environmental
requirements for Oracle Exadata Database Machine X2-2. The other sections in this
chapter provide detailed information.
Table 1-9 Environmental Requirements for Oracle Exadata Database Machine
X2-2
Environmental
Component
Weight
See Also: "Flooring
Requirements
(page 1-34)"
Acoustic levels89 db(A)86 db(A)83 db(A)
Power
See Also: "Electrical
Power Requirements
(page 1-34)"
Cooling
See Also:
"Temperature and
Humidity
Requirements
(page 1-44)", and
"Ventilation and
Cooling Requirements
(page 1-45)"
Oracle Exadata
Database Machine
X2-2 Full Rack
966.6 kg (2131 lbs)602.8 kg (1329 lbs)409.1kg (902 lbs)
Maximum: 14.0 kW
(14.3 kVA)
Typical: 9.8 kW (10.0
kVA) (varies based on
application load)
Maximum: 47,800
BTU/hour (50,400 kJ/
hour)
Typical: 33,400 BTU/
hour (35,300 kJ/hour)
Oracle Exadata
Database Machine
X2-2 Half Rack
Maximum: 7.2 kW
(7.3 kVA)
Typical: 5.1 kW (5.2
kVA) (varies based on
application load)
Maximum: 26,400
BTU/hour (25,950 kJ/
hour)
Typical: 17,400 BTU/
hour (35,300 kJ/hour)
Oracle Exadata
Database Machine
X2-2 Quarter Rack
Maximum: 3.6 kW
(3.7 kVA)
Typical: 2.7 kW
(2.75kVA) (varies
based on application
load)
Air flow front-to-back
(subject to actual data
center environment)
See Also:
"Temperature and
Humidity
Requirements
(page 1-44)", and
"Ventilation and
Cooling Requirements
(page 1-45)"
IP Addresses
See Also: "Network
Connection and IP
Address
Requirements for
Oracle Exadata
Database Machine
(page 1-47)"
Network drops
See Also: "Network
Connection and IP
Address
Requirements for
Oracle Exadata
Database Machine
(page 1-47)"
External connectivity
See Also: "Network
Connection and IP
Address
Requirements for
Oracle Exadata
Database Machine
(page 1-47)"
Oracle Exadata
Database Machine
X2-2 Full Rack
Maximum:
Approximately 2,200
CFM
Typical:
Approximately 1,560
CFM
70 for Ethernet
network, assuming
single cluster
22 for InfiniBand
network
Minimum of 12
network drops
24 x 1 GbE Ethernet
ports
16 x 10 GbE Ethernet
ports (valid for M2
servers only)
At least 12 InfiniBand
ports
Oracle Exadata
Database Machine
X2-2 Half Rack
Maximum:
Approximately 1,130
CFM
Typical:
Approximately 840
CFM
40 for Ethernet
network, assuming
single cluster (39 IP
addresses are needed
for Oracle Exadata
Database Machine
X2-2 (with X4170 and
X4275 servers))
11 for InfiniBand
network
Minimum of 8 network
drops
12 x 1 GbE Ethernet
ports
8 x 10 GbE Ethernet
ports (valid for M2
servers only)
At least 12 InfiniBand
ports
Oracle Exadata
Database Machine
X2-2 Quarter Rack
Maximum:
Approximately 550
CFM
Typical:
Approximately 410
CFM
23 for Ethernet
network, assuming
single cluster
5 for InfiniBand
network
Minimum of 6 network
drops
6 x 1 GbE Ethernet
ports
4 x 10 GbE Ethernet
ports (valid for M2
servers only)
At least 12 InfiniBand
ports
1.1.11 General Environmental Requirements for Oracle Exadata
Database Machine X2-8 Full Rack
Table 1-10 (page 1-19) shows the general environmental requirements for Oracle
Exadata Database Machine X2-8 Full Rack. The other sections in this chapter provide
detailed information.
1-18
Page 31
Chapter 1
General Environmental Requirements
Table 1-10 Environmental Requirements for Oracle Exadata Database Machine
X2-8 Full Rack
Environmental ComponentOracle Exadata Database
Machine X2-8 Full Rack
(Sun Fire X4800 Oracle
Database Servers)
Weight
See Also: "Flooring
Requirements (page 1-34)"
Acoustic levels85 db(A)85 db(A)
Power
See Also: "Electrical Power
Requirements (page 1-34)"
Cooling
See Also: "Temperature and
Humidity Requirements
(page 1-44)", and
"Ventilation and Cooling
Requirements (page 1-45)"
Air flow front-to-back (subject
to actual data center
environment)
See Also: "Temperature and
Humidity Requirements
(page 1-44)", and
"Ventilation and Cooling
Requirements (page 1-45)"
IP Addresses
See Also: "Network
Connection and IP Address
Requirements for Oracle
Exadata Database Machine
(page 1-47)"
Network drops
See Also: "Network
Connection and IP Address
Requirements for Oracle
Exadata Database Machine
(page 1-47)"
External connectivity
See Also: "Network
Connection and IP Address
Requirements for Oracle
Exadata Database Machine
(page 1-47)"
943.5 kg (2080 lbs)980.7 kg (2162 lbs)
Maximum: 17.0 kW (17.4
kVA)
Typical: 11.9 kW (12.2 kVA)
(varies based on application
load)
Maximum: 58,050 BTU/hour
(61,200 kJ/hour)
Typical: 40,630 BTU/hour
(42,840 kJ/hour)
Maximum: Approximately
2,690 CFM
Typical: Approximately 1,880
CFM
45 for Ethernet network,
assuming single cluster
22 for InfiniBand network
Minimum of 5 network dropsMinimum of 5 network drops
16 x 1 GbE Ethernet ports
16 x 10 GbE Ethernet SFP+
ports
12 InfiniBand ports
Oracle Exadata Database
Machine X2-8 Full Rack
(Sun Server X2-8 Oracle
Database Servers)
Maximum: 17.7 kW (18.1
kVA)
Typical: 12.4 kW (112.7 kVA)
(varies based on application
load)
Maximum: 60,350 BTU/hour
(63,630 kJ/hour)
Typical: 42,280 BTU/hour
(44,580 kJ/hour)
Maximum: Approximately
2,781CFM
Typical: Approximately 1,950
CFM
45 for Ethernet network,
assuming single cluster
22 for InfiniBand network
16 x 1 GbE Ethernet ports
16 x 10 GbE Ethernet SFP+
ports
12 InfiniBand ports
1-19
Page 32
General Environmental Requirements
1.1.12 General Environmental Requirements for Oracle Exadata
Storage Expansion Rack X6-2 and later
For Oracle Exadata Storage Expansion Rack X6-2 and more recent systems, to get
the environmental requirements, such as weight, acoustic level, power, cooling, and
air flow, use the Oracle Exadata Configuration Assistant, available on Oracle
Technology Network:
1.1.13 General Environmental Requirements for Oracle Exadata
Storage Expansion Rack X5-2
The environmental requirements for Oracle Exadata Storage Expansion Rack X5-2
depend on the size of the system. Table 1-11 (page 1-20) shows the general
environmental requirements for each type of Oracle Exadata Storage Expansion Rack
X5-2.
1.1.14 General Environmental Requirements for Oracle Exadata
Storage Expansion Rack X4-2
The environmental requirements for Oracle Exadata Storage Expansion Rack X4-2
depend on the size of the system. Table 1-12 (page 1-22) shows the general
environmental requirements for each type of Oracle Exadata Storage Expansion Rack
X4-2.
1.1.15 General Environmental Requirements for Oracle Exadata
Storage Expansion Rack X3-2
The environmental requirements for Oracle Exadata Storage Expansion Rack X3-2
depend on the size of the system. Table 1-13 (page 1-23) shows the general
environmental requirements for each type of Oracle Exadata Storage Expansion Rack
X3-2.
1.1.16 General Environmental Requirements for Oracle Exadata
Storage Expansion Rack with Exadata Storage Server with Sun Fire
X4270 M2 Servers
The environmental requirements for Oracle Exadata Storage Expansion Rack with
Exadata Storage Server with Sun Fire X4270 M2 Servers depend on the size of the
system. Table 1-14 (page 1-25) shows the general environmental requirements for
each type of Oracle Exadata Storage Expansion Rack with Exadata Storage Server
with Sun Fire X4270 M2 Servers.
Table 1-14 Environmental Requirements for Oracle Exadata Storage Expansion
Rack with Exadata Storage Server with Sun Fire X4270 M2 Servers
Environmental
Component
Weight917.6 kg (2023 lbs)578.3 kg (1275 lbs)396.8 kg (875 lbs)
Acoustic levels83 db(A)82 db(A)81 db(A)
PowerMaximum: 12.6 kW
CoolingMaximum: 43,000
Oracle Exadata
Storage Expansion
Full Rack
(12.9 kVA)
Typical: 8.8 kW (9.0
kVA) (varies based on
application load)
BTU/hour (45,400 kJ/
hour)
Typical: 30,100 BTU/
hour (31,800 kJ/hour)
Oracle Exadata
Storage Expansion
Half Rack
Maximum: 6.9 kW
(7.1 kVA)
Typical: 4.8 kW (5.0
kVA) (varies based on
application load)
Maximum: 23,600
BTU/hour (24,900 kJ/
hour)
Typical: 16,500 BTU/
hour (17,400 kJ/hour)
Oracle Exadata
Storage Expansion
Quarter Rack
Maximum: 3.4 kW
(3.5 kVA)
Typical: 2.4 kW
(2.5kVA) (varies
based on application
load)
Maximum: 11,600
BTU/hour (12,250 kJ/
hour)
Typical: 8,100 BTU/
hour (8,600 kJ/hour)
1-25
Page 38
Chapter 1
General Environmental Requirements
Table 1-14 (Cont.) Environmental Requirements for Oracle Exadata Storage
Expansion Rack with Exadata Storage Server with Sun Fire X4270 M2 Servers
Environmental
Component
Air flow front-to-back
(subject to actual data
center environment)
1.1.17 General Environmental Requirements for Single Servers
The environmental requirements for single servers are shown in the following tables.
Table 1-15 Environmental Requirements for X7-2 Single Servers
Environmental
Component
Weight28.1 kg (62 lbs)33.1 kg (73 lbs)20.4 kg (45 lbs)
Acoustic levels78 db(A)78 db(A)78 db(A)
PowerMaximum: 0.6 kVA
CoolingMaximum: 1,866 BTU/
Air flow front-to-back
(subject to actual data
center environment)
Exadata Storage
Server X7-2 Extreme Flash
Typical: 0.4 kVA
(varies based on
application load)
hour (1,969 kJ/hour)
Typical: 1,307 BTU/
hour (1,378 kJ/hour)
Maximum:
Approximately 86
CFM
Typical:
Approximately 60
CFM
Exadata Storage
Server X7-2 - High
Capacity
Maximum: 0.6 kVA
Typical: 0.4 kVA
(varies based on
application load)
Maximum: 2,006 BTU/
hour (2,117 kJ/hour)
Typical: 1,404 BTU/
hour (1,482 kJ/hour)
Maximum:
Approximately 93
CFM
Typical:
Approximately 65
CFM
Database Server
X7-2
Maximum: 0.665 kW
(0.678 kVA)
Typical: 0.466 kW
(0.475 kVA) (varies
based on application
load)
Maximum: 2,269 BTU/
hour (2,394 kJ/hour)
Typical: 1,588 BTU/
hour (1,676 kJ/hour
Maximum:
Approximately 105
CFM
Typical:
Approximately 74
CFM
1-26
Page 39
General Environmental Requirements
Table 1-16 Environmental Requirements for X6-2 Single Servers
Chapter 1
Environmental
Component
Weight28.1 kg (62 lbs)33.1 kg (73 lbs)20.4 kg (45 lbs)
Acoustic levels78 db(A)78 db(A)78 db(A)
PowerMaximum: 0.6 kVA
CoolingMaximum: 1,866 BTU/
Air flow front-to-back
(subject to actual data
center environment)
Exadata Storage
Server X6-2 Extreme Flash
Typical: 0.4 kVA
(varies based on
application load)
hour (1,969 kJ/hour)
Typical: 1,307 BTU/
hour (1,378 kJ/hour)
Maximum:
Approximately 86
CFM
Typical:
Approximately 60
CFM
Exadata Storage
Server X6-2 - High
Capacity
Maximum: 0.6 kVA
Typical: 0.4 kVA
(varies based on
application load)
Maximum: 2,006 BTU/
hour (2,117 kJ/hour)
Typical: 1,404 BTU/
hour (1,482 kJ/hour)
Maximum:
Approximately 93
CFM
Typical:
Approximately 65
CFM
Database Server
X6-2
Maximum: 0.665 kW
(0.678 kVA)
Typical: 0.466 kW
(0.475 kVA) (varies
based on application
load)
Maximum: 2,269 BTU/
hour (2,394 kJ/hour)
Typical: 1,588 BTU/
hour (1,676 kJ/hour
Maximum:
Approximately 105
CFM
Typical:
Approximately 74
CFM
Table 1-17 Environmental Requirements for X5-2 Single Servers
Environmental
Component
Weight28.1 kg (62 lbs)33.1 kg (73 lbs)20.4 kg (45 lbs)
Acoustic levels78 db(A)78 db(A)78 db(A)
PowerMaximum: 0.6 kVA
CoolingMaximum: 2,037 BTU/
Air flow front-to-back
(subject to actual data
center environment)
Exadata Storage
Server X5-2 Extreme Flash
Typical: 0.4 kVA
(varies based on
application load)
hour (2,149 kJ/hour)
Typical: 1,426 BTU/
hour (1,504 kJ/hour)
Maximum:
Approximately 94
CFM
Typical:
Approximately 66
CFM
Exadata Storage
Server X5-2 - High
Capacity
Maximum: 0.6 kVA
Typical: 0.4 kVA
(varies based on
application load)
Maximum: 2,000 BTU/
hour (2,109 kJ/hour)
Typical: 1,400 BTU/
hour (1,477 kJ/hour)
Maximum:
Approximately 93
CFM
Typical:
Approximately 65
CFM
Database Server
X5-2
Maximum: 0.7 kVA
Typical: 0.5 kVA
(varies based on
application load)
Maximum: 2,481 BTU/
hour (2,617 kJ/hour)
Typical: 1,736 BTU/
hour (1,832 kJ/hour
Maximum:
Approximately 115
CFM
Typical:
Approximately 80
CFM
1-27
Page 40
Space Requirements
Table 1-18 Environmental Requirements for X4-8, X5-8, and X6-8 Single
Servers
Chapter 1
Environmental ComponentDatabase Server X5-8 and
Weight93.4 kg (206 lbs)93.4 kg (206 lbs)
Acoustic levels81 db(A)81 db(A)
PowerMaximum: 3.5 kVA
CoolingMaximum: 11,601 BTU/hour
Air flow front-to-back (subject
to actual data center
environment)
1.2 Space Requirements
Oracle Exadata Database Machine X7-2 and X7-8
The Oracle Exadata X7-2 and X7-8 racks use a different rack than its predecessors.
The space requirements are as follows:
X6-8
Typical: 2.4 kVA (varies based
on application load)
(12,239 kJ/hour)
Typical: 8,121 BTU/hour
(8,568 kJ/hour)
Maximum: Approximately 537
CFM
Typical: Approximately 376
CFM
Database Server X4-8
Maximum: 3.7 kVA
Typical: 2.6 kVA (varies based
on application load)
Maximum: 12,284 BTU/hour
(12,959 kJ/hour)
Typical: 8,599 BTU/hour
(9,072 kJ/hour)
Maximum: Approximately 569
CFM
Typical: Approximately 398
CFM
•Height: 2000 mm (78.74 inches)
•Width: 600 mm (23.62 inches)
•Depth: 1235 mm with doors attached, from handle to handle (48.6 inches)
The minimum ceiling height for the cabinet is 2914 mm (114.72 inches), measured
from the true floor or raised floor, whichever is higher. This includes an additional 914
mm (36 inches) of space required above the rack height for maintenance access, as
described in Table 1-22 (page 1-34). The space surrounding the cabinet must not
restrict the movement of cool air between the air conditioner and the front of the
systems within the cabinet, or the movement of hot air coming out of the rear of the
cabinet.
Oracle Exadata Racks up to Oracle Exadata Database Machine X6-8
All Oracle Exadata Racks up to Oracle Exadata X6-8 use the same rack, and have the
same space requirements. The space requirements are as follows:
•Height: 1998 mm (78.66 inches)
•Width: 600 mm with side panels (23.62 inches)
•Depth: 1200 mm (47.24 inches)
The minimum ceiling height for the cabinet is 2912 mm (114.65 inches), measured
from the true floor or raised floor, whichever is higher. This includes an additional 914
mm (36 inches) of space required above the rack height for maintenance access, as
described in Table 1-22 (page 1-34). The space surrounding the cabinet must not
1-28
Page 41
restrict the movement of cool air between the air conditioner and the front of the
systems within the cabinet, or the movement of hot air coming out of the rear of the
cabinet.
1.2.1 Receiving and Unpacking Requirements
Before your Oracle Exadata Rack arrives, ensure that the receiving area is large
enough for the package.
Use the following package dimensions for Oracle Exadata Rack:
•Shipping height: 2159 mm (85 inches)
•Shipping width: 1219 mm (48 inches)
•Shipping depth: 1575 mm (62 inches)
For weight information for Oracle Exadata Database Machine X6-8, X7-2 and X7-8,
use the Oracle Exadata Configuration Assistant, available on Oracle Technology
Network: Oracle Exadata Configuration Assistant (OECA) Downloads
•Table 1-19 (page 1-29) lists the shipping and net weights for Oracle Exadata
Database Machines.
Chapter 1
Space Requirements
•Table 1-20 (page 1-31) lists the shipping and net weights for Oracle Exadata
Storage Expansion Racks:
•Table 1-21 (page 1-33) lists the access route requirements for Oracle Exadata
Rack.
Table 1-19 Rack Weights for Oracle Exadata Database Machine
Type of RackShipping WeightNet Weight
Oracle Exadata Database
Machine X7-2 Full Rack
Oracle Exadata Database
Machine X7-2 Half Rack
Oracle Exadata Database
Machine X7-2 Quarter Rack
Oracle Exadata Database
Machine X7-2 Eighth Rack
Oracle Exadata Database
Machine X7-8 Full Rack
Extreme Flash: 974.0 kg
(2147.2 lbs)
High Capacity: 1071.1 kg
(2361.4 lbs)
Extreme Flash: 698.4 kg
(1539.6 lbs)
High Capacity: 746.9 kg
(1646.7 lbs)
Extreme Flash: 551.1 kg
(1215.0 lbs)
High Capacity: 571.9 kg
(1260.9 lbs)
Extreme Flash: 548.8 kg
(1209.9 lbs)
High Capacity: 558.9 kg
(1232.2 lbs)
Extreme Flash drives: 894.7
kg (1972.5 lbs)
High capacity drives: 964.6 kg
(2126.5 lbs)
Extreme Flash: 815.1 kg
(1797.2 lbs)
High Capacity: 912.4 kg
(2011.4 lbs)
Extreme Flash: 539.6 kg
(1189.6 lbs)
High Capacity: 558.8 kg
(1296.7 lbs)
Extreme Flash: 392.4 kg
(865.0 lbs)
High Capacity: 413.2 kg
(910.9 lbs)
Extreme Flash: 390.1 kg
(859.9 lbs)
High Capacity: 400.1 kg
(882.2 lbs)
Extreme Flash drives: 828.5
kg (1826.5 lbs)
High capacity drives: 898.3 kg
(1980.5 lbs)
1-29
Page 42
Space Requirements
Table 1-19 (Cont.) Rack Weights for Oracle Exadata Database Machine
Type of RackShipping WeightNet Weight
Oracle Exadata Database
Machine X6-2 Full Rack
Oracle Exadata Database
Machine X6-2 Half Rack
Oracle Exadata Database
Machine X6-2 Quarter Rack
Oracle Exadata Database
Machine X6-2 Eighth Rack
Oracle Exadata Database
Machine X5-8 or X6-8 Full
Rack
Oracle Exadata Database
Machine X6-8 Half Rack
Oracle Exadata Database
Machine X5-8 Half Rack
Oracle Exadata Database
Machine X5-2 Full Rack
Oracle Exadata Database
Machine X5-2 Half Rack
Oracle Exadata Database
Machine X5-2 Quarter Rack
Oracle Exadata Database
Machine X5-2 Eighth Rack
Oracle Exadata Database
Machine X4-2 Full Rack
Oracle Exadata Database
Machine X4-2 Half Rack
Oracle Exadata Database
Machine X4-2 Quarter Rack
Oracle Exadata Database
Machine X4-2 Eighth Rack
Extreme Flash: 871.1 kg
(1920.5 lbs)
High Capacity: 941.0 kg
(2074.5 lbs)
Extreme Flash: 592.2 kg
(1305.5 lbs)
High Capacity: 627.1 kg
(1382.5 lbs)
Extreme Flash: 432.5 kg
(953.5 lbs)
High Capacity: 447.5 kg
(986.5 lbs)
Extreme Flash: 432.5 kg
(953.5 lbs)
High Capacity: 433.8 kg
(956.3 lbs)
Extreme Flash drives: 894.7
kg (1972.5 lbs)
High capacity drives: 964.6 kg
(2126.5 lbs)
Extreme Flash drives: 592.2
kg (1305.5 lbs)
High capacity drives: 607.1 kg
(1338.5 lbs)
Extreme Flash drives: 592.4
kg (1306.1 lbs)
High capacity drives: 607.4 kg
(1339.1 lbs)
984.8 kg (2171 lbs)901.3 kg (1987 lbs)
639.6 kg (1410 lbs)587.4 kg (1295 lbs)
453.1 kg (999 lbs)418.2 kg (922 lbs)
453.1 kg (999 lbs)418.2 kg (922 lbs)
936 kg (2064 lbs)852.8 kg (1880 lbs)
577 kg (1273 lbs)525.3 kg (1158 lbs)
401 kg (883 lbs)365.6 kg (806 lbs)
401 kg (883 lbs)365.6 kg (806 lbs)
Extreme Flash: 794.5 kg
(1751.5 lbs)
High Capacity: 864.3 kg
(1905.5 lbs)
Extreme Flash: 515.5 kg
(1136.5 lbs)
High Capacity: 550.4 kg
(1213.5 lbs)
Extreme Flash: 366.3 kg
(807.5 lbs)
High Capacity: 381.2 kg
(840.5 lbs)
Extreme Flash: 366.3 kg
(807.5 lbs)
High Capacity: 376.6 kg
(810.3 lbs)
Extreme Flash drives: 828.5
kg (1826.5 lbs)
High capacity drives: 898.3 kg
(1980.5 lbs)
Extreme Flash drives: 525.9
kg (1159.5 lbs)
High capacity drives: 540.9 kg
(1192.5 lbs)
Extreme Flash drives: 526.2
kg (1160.1 lbs)
High capacity drives: 541.2 kg
(1193.1 lbs)
Chapter 1
1-30
Page 43
Space Requirements
Table 1-19 (Cont.) Rack Weights for Oracle Exadata Database Machine
Type of RackShipping WeightNet Weight
Oracle Exadata Database
Machine X4-8 Full Rack
Oracle Exadata Database
Machine X3-2 Full Rack
Oracle Exadata Database
Machine X3-2 Half Rack
Oracle Exadata Database
Machine X3-2 Quarter Rack
Oracle Exadata Database
Machine X3-2 Eighth Rack
Oracle Exadata Database
Machine X3-8 Full Racks with
Exadata Storage Server
X4-2L Servers
Oracle Exadata Database
Machine X3-8 Full Racks
Oracle Exadata Database
Machine X2-2 Full Rack
Oracle Exadata Database
Machine X2-2 Half Rack
Oracle Exadata Database
Machine X2-2 Quarter Rack
Oracle Exadata Database
Machine X2-8 Full Rack with
Sun Fire X4800 Oracle
Database Servers
Oracle Exadata Database
Machine X2-8 Full Rack with
Sun Server X2-8 Oracle
Database Servers
High performance drives: 951
kg (2097 lbs)
High capacity drives: 1019 kg
(2247 lbs)
954.8 kg (2105 lbs)871.4 kg (1921 lbs)
596.0 kg (1314 lbs)543.9 kg (1199 lbs)
403.7 kg (890 lbs)368.8 kg (813 lbs)
403.7 kg (890 lbs)368.8 kg (813 lbs)
994.7 kg (2193 lbs)911.3 kg (2009 lbs)
1013.3 kg (2234 lbs)929.9 kg (2050 lbs)
1050.1 kg (2315 lbs)966.61 kg (2131 lbs)
684.1 kg (1508 lbs)602.8 kg (1329 lbs)
487.6 kg (1075 lbs)409.1 kg (902 lbs)
1026.9 kg (2264 lbs)943.8 kg (2080 lbs)
1036.0 kg (2284 lbs)980.7 kg (2162 lbs)
High performance drives: 867
kg (1912 lbs)
High capacity drives: 936 kg
(2063 lbs)
Chapter 1
Table 1-20 Rack Weights for Oracle Exadata Storage Expansion Rack
Oracle Exadata Storage
Expansion Full Rack with
Exadata Storage Server with
Sun Fire X4270 M2 Servers
Oracle Exadata Storage
Expansion Half Rack with
Exadata Storage Server with
Sun Fire X4270 M2 Servers
Oracle Exadata Storage
Expansion Quarter Rack with
Exadata Storage Server with
Sun Fire X4270 M2 Servers
Extreme Flash: 430.7 kg
(949.5 lbs)
High Capacity: 450.6 kg
(993.5 lbs)
Extreme Flash: 850.3 kg
(1874.5 lbs)
High Capacity: 945.1 kg
(2083.5 lbs)
Extreme Flash: 569.0 kg
(1254.5 lbs)
High Capacity: 613.9 kg
(1353.5 lbs)
Extreme Flash: 430.7 kg
(949.5 lbs)
High Capacity: 450.6 kg
(993.5 lbs)
994.7 kg (2193 lbs)915.8 kg (2019 lbs)
640.9 kg (1413 lbs)591.5 kg (1304 lbs)
444.5 kg (980 lbs)411 kg (906.1 lbs)
903.1 kg (1991 lbs)824.2 kg (1817.1 lbs)
562.4 kg (1239.9 lbs)513.0 kg (1131 lbs)
380.1 kg (838 lbs)346.5 kg (764 lbs)
906.3 kg (1998 lbs)827.4 kg (1824.1 lbs)
565.6 kg (1247 lbs)516.2 kg (1138 lbs)
383.3 kg (845 lbs)349.7 kg (771 lbs)
1001.1 kg (2207 lbs)917.6 kg (2023 lbs)
659.6 kg (1454.2 lbs)578.3 kg (1275 lbs)
475.3 kg (1047.9 lbs)396.8 kg (874.8 lbs)
Extreme Flash: 364.5 kg
(803.5 lbs)
High Capacity: 384.4 kg
(847.5 lbs)
Extreme Flash: 784.0 kg
(1728.5 lbs)
High Capacity: 878.8 kg
(1937.5 lbs)
Extreme Flash: 502.8 kg
(1108.5 lbs)
High Capacity: 547.7 kg
(1207.5 lbs)
Extreme Flash: 364.5 kg
(803.5 lbs)
High Capacity: 384.4 kg
(847.5 lbs)
1-32
Page 45
Chapter 1
Space Requirements
If your loading dock meets the height and ramp requirements for a standard freight
carrier truck, then you can use a pallet jack to unload the rack. If the loading dock does
not meet the requirements, then you must provide a standard forklift or other means to
unload the rack. You can also request that the rack be shipped in a truck with a lift
gate.
When Oracle Exadata Rack arrives, leave the rack in its shipping packaging until it
arrives at its installation site. Use a conditioned space to remove the packaging
material to reduce particles before entering the data center. The entire access route to
the installation site should be free of raised-pattern flooring that can cause vibration.
Allow enough space for unpacking it from its shipping cartons. Ensure that there is
enough clearance and clear pathways for moving Oracle Exadata Rack from the
unpacking location to the installation location.
Minimum door height2184 mm (86 inches)2040 mm (80.32 inches)
Minimum door width1270 (50 inches)640 mm (25.19 inches)
Minimum elevator depth1625.6 mm (64 inches)1240 mm (48.82 inches)
Maximum incline6 degrees6 degrees
Minimum elevator, pallet jack,
and floor loading capacity
1134 kg (2500 lbs)1134 kg (2500 lbs)
1.2.2 Maintenance Access Requirements
The maintenance area must be large enough for Oracle Exadata Rack, and have the
required access space. For example, the required space to remove the side panels is
675. 64 mm (26.6 inches). Front access space requirement is typically the length of
the longest chassis supported in the rack, plus the distance the rails need to travel out
to install and remove equipment from the front. Rear access space requirement is the
space needed for a person working behind the Oracle Exadata Rack. Top access
space requirement is for a person standing on a ladder to be able service components
installed in the top of the rack.
Note:
•Open tiles are required for electrical access.
•Oracle Exadata Racks can be placed side-by-side when interconnecting
the racks.
The following table lists the maintenance access requirements.
Oracle recommends that Oracle Exadata Rack be installed on raised flooring. The site
floor and the raised flooring must be able to support the total weight of Oracle Exadata
Rack.
Table 1-23 (page 1-34) lists the floor load requirements.
Table 1-23 Floor Load Requirements for Oracle Exadata Database Machine
Chapter 1
Flooring Requirements
DescriptionRequirement
Maximum allowable weight of installed rack
equipment
Maximum allowable weight of installed power
distribution units
Maximum dynamic load (maximum allowable
weight of installed equipment including PDUs)
1.4 Electrical Power Requirements
Oracle Exadata Racks can operate effectively over a wide range of voltages and
frequencies. However, they must have a reliable power source. Damage may occur if
the ranges are exceeded. Electrical disturbances such as the following may damage
Oracle Exadata Rack:
•Fluctuations caused by brownouts
•Wide and rapid variations in input voltage levels or in input power frequency
•Electrical storms
•Faults in the distribution system, such as defective wiring
To protect Oracle Exadata Rack from such disturbances, you should have a dedicated
power distribution system, power-conditioning equipment, as well as lightning arresters
or power cables to protect from electrical storms.
952.5 kg (2100 lbs)
52.16 kg (115 lbs)
1004.66 kg (2215 lbs)
1.4.1 PDU Power Requirements
Each rack has two pre-installed power distribution units (PDUs). The PDUs accept
different power sources. You must specify the type of PDU that is correct for your
Oracle Exadata Rack and data center.
1-34
Page 47
Chapter 1
Electrical Power Requirements
The following are the PDUs that Exadata currently supports or has supported in the
past:
•Table 1-24 (page 1-35) Low-voltage 15 kVA Single Phase PDUs for North
America, South America, Japan and Taiwan (2 PDUs per Rack)
•Table 1-25 (page 1-36) Low-voltage 15 kVA Three Phase PDUs for North
America, South America, Japan and Taiwan (2 PDUs per Rack)
•Table 1-26 (page 1-37) High-voltage 15 kVA Single Phase PDUs for Europe, the
Middle East and Africa (EMEA), and Asia Pacific (APAC), except for Japan and
Taiwan (2 PDUs per Rack)
•Table 1-27 (page 1-38) High-voltage 15 kVA Three Phase for Europe, the Middle
East and Africa (EMEA), and Asia Pacific (APAC), except for Japan and Taiwan (2
PDUs per Rack)
•Table 1-28 (page 1-39) Low-voltage 22 kVA Single Phase PDUs for North
America, South America, Japan and Taiwan (2 PDUs per Rack)
•Table 1-29 (page 1-39) High-voltage 22 kVA Single Phase PDUs for Europe, the
Middle East and Africa (EMEA), and Asia Pacific (APAC), except for Japan and
Taiwan (2 PDUs per Rack)
•Table 1-30 (page 1-40) Low-voltage 24 kVA Three Phase PDUs for North
America, South America, Japan and Taiwan (2 PDUs per Rack)
•Table 1-31 (page 1-41) High-voltage 24 kVA Three Phase PDUs for Europe, the
Middle East and Africa (EMEA), and Asia Pacific (APAC), except for Japan and
Taiwan (2 PDUs per Rack)
•Table 1-32 (page 1-42) Low-voltage 37 kVA Three Phase PDUs for North
America, South America, Japan and Taiwan (2 PDUs per Rack)
•Table 1-33 (page 1-42) High-voltage 37 kVA Three Phase PDUs for Europe, the
Middle East and Africa (EMEA), and Asia Pacific (APAC), except for Japan and
Taiwan (2 PDUs per Rack)
Table 1-24 (page 1-35) lists the requirements for low-voltage single-phase PDUs for
North America, South America, Japan, and Taiwan. There are two PDUs per rack. The
following specifications are per PDU.
Table 1-24 Low-voltage 15 kVA Single Phase PDUs for North America, South
America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Voltage200 - 240 VAC
Frequency50/60 Hz
Current24 A maximum per input
Power rating15 kVA
Output current72 A (3 x 24 A)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 2-pole circuit
breaker)
20A
1-35
Page 48
Chapter 1
Electrical Power Requirements
Table 1-24 (Cont.) Low-voltage 15 kVA Single Phase PDUs for North America,
South America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Data center receptacle15kVA, with three 30A/250V 2-pole/3-wire
NEMA L6-30P plugs
The following are needed to connect an Oracle Exadata system to a low-voltage onephase power source:
•6 power cords for two PDUs, 30 amperes at 200 - 240 VAC
•6 receptacles to connect the PDUs to 6 NEMA L6-30 data center receptacles
Figure 1-1 (page 1-36) shows the low-voltage, single phase PDU power connector for
North America, South America, Japan and Taiwan.
Figure 1-1 Low-voltage Single Phase Power Connector
Table 1-25 (page 1-36) lists the requirements for low-voltage three-phase PDUs for
North America, South America, Japan, and Taiwan. There are two PDUs per rack. The
following specifications are per PDU.
Table 1-25 Low-voltage 15 kVA Three Phase PDUs for North America, South
America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Voltage190 - 220 VAC
Frequency50/60 Hz
Current40 A maximum per phase
Power rating14.4 kVA
Output current69.3 A (3 x 23.1A)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 2-pole circuit
breaker)
Data center receptacleIEC309-3P4W-IP67 60A 250VAC 3ph
20A
(Hubbell equivalent is HBL460R9W)
The following are needed to connect an Oracle Exadata system to a low-voltage threephase power source:
1-36
Page 49
Chapter 1
Electrical Power Requirements
•2 power cords for two PDUs, 60 amperes at 190 - 220 VAC three-phase
•2 receptacles to connect the PDUs to 2 IEC 60309 60A 4-pin 250VAC 3ph IP67
data center receptacles
Figure 1-2 (page 1-37) shows the low-voltage, three phase PDU power connector for
North America, South America, Japan and Taiwan.
Figure 1-2 Low-voltage Three Phase Power Connector
Table 1-26 (page 1-37) lists the requirements for 15 kVA high-voltage three-phase
PDUs for Europe, the Middle East, Africa, and Asia Pacific, except Japan and Taiwan.
There are two PDUs per rack.
The following specifications are per PDU.
Table 1-26 High-voltage 15 kVA Single Phase PDUs for Europe, the Middle East
and Africa (EMEA), and Asia Pacific (APAC), except for Japan and Taiwan (2
PDUs per Rack)
OptionRequirement, per PDU
Voltage220 - 240 VAC
Frequency50/60 Hz
Current24 A maximum per input
Power rating15 kVA
Output current72 A (3 x 24 A)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 2-pole circuit
breaker)
Data center receptacle15kVA, IEC309-2P3W-IP44 32A 250VAC
20A
(Hubbell equivalent is HBL332R6W
Figure 1-3 (page 1-37) shows the high-voltage single phase PDU power connector
for EMEA, and APAC, except for Japan and Taiwan.
Figure 1-3 High-voltage Single Phase Power Connector
1-37
Page 50
Chapter 1
Electrical Power Requirements
Table 1-27 (page 1-38) lists the requirements for 15 kVA high-voltage three-phase
PDUs for Europe, the Middle East, Africa, and Asia Pacific, except Japan and Taiwan.
There are two PDUs per rack. The following specifications are per PDU.
Table 1-27 High-voltage 15 kVA Three Phase for Europe, the Middle East and
Africa (EMEA), and Asia Pacific (APAC), except for Japan and Taiwan (2 PDUs
per Rack)
OptionRequirement, per PDU
Voltage220/380 - 240/415 VAC 3-phase
Frequency50/60 Hz
Current25 A maximum per phase
Power rating14.4 kVA
Output current62.7 A (3 x 20.9 A)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 1-pole circuit
breaker)
Data center receptacle15kVA, three phase, 5-pin, IEC 60309 32A, 5-
20A
pin 230/400V, three phase IP44
The following are needed to connect an Oracle Exadata system to a high-voltage
three-phase power source:
•2 power cords for two PDUs, 25 amperes at 220/380 - 240/415 VAC three-phase
•2 receptacles to connect the PDUs to 2 IEC 60309 32A 5-pin 230/400VAC 3ph
IP44 data center receptacles
Figure 1-4 (page 1-38) shows the high-voltage three phase PDU power connector for
EMEA, and APAC, except for Japan and Taiwan.
Figure 1-4 High-voltage Three Phase Power Connector
Table 1-28 (page 1-39) lists the requirements for low-voltage 22 kVA single phase
PDUs for North America, South America, Japan, and Taiwan. There are two PDUs per
rack. The following specifications are per PDU.
1-38
Page 51
Chapter 1
Electrical Power Requirements
Table 1-28 Low-voltage 22 kVA Single Phase PDUs for North America, South
America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Voltage200 - 240 VAC
Frequency50/60 Hz
Current36.8 A maximum per input / 110.4 A Maximum
per PDU
Power rating22 kVA
Output current110.4A (3x 36.8)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 2-pole circuit
breaker)
Data center receptacleHubbell CS8265C
20A
The following are needed to connect an Oracle Exadata system to a low-voltage
single-phase power source:
•3 power cords for two PDUs
•6 receptacles to connect the PDUs
Figure 1-5 (page 1-39) shows the low-voltage, 22 kVA single phase PDU power
connector for North America, South America, Japan and Taiwan. This power
connector is different from the power connector for the low-voltage 15 kVA single
phase PDU.
Figure 1-5 Low-voltage 22 kVA Single Phase Power Connector
Table 1-29 (page 1-39) lists the requirements for 22 kVA high-voltage one-phase
PDUs for Europe, the Middle East, Africa, and Asia Pacific, except Japan and Taiwan.
There are two PDUs per rack. The following specifications are per PDU.
Table 1-29 High-voltage 22 kVA Single Phase PDUs for Europe, the Middle East
and Africa (EMEA), and Asia Pacific (APAC), except for Japan and Taiwan (2
PDUs per Rack)
OptionRequirement, per PDU
Voltage220-240 VAC
1-39
Page 52
Chapter 1
Electrical Power Requirements
Table 1-29 (Cont.) High-voltage 22 kVA Single Phase PDUs for Europe, the
Middle East and Africa (EMEA), and Asia Pacific (APAC), except for Japan and
Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Frequency50/60 Hz
Current32 A maximum per input
Power rating22 kVA
Output current96 A (3 x 32 A)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 1-pole circuit
breaker)
Data center receptacleIEC309-2P3W-IP44 32A 250VAC (Hubbell
20A
equivalent is HBL332R6W)
Note:
The high-voltage 15kVA single phase PDU is no longer available. The highvoltage 22kVA is a compatible replacement with the same receptacle and
breaker requirements
The following are needed to connect an Oracle Exadata system to a high-voltage onephase power source:
•6 power cords for two PDUs, 25 amperes at 220/380 - 240/415 VAC 1-phase
voltage
•6 receptacles to connect the PDUs to 2 IEC 60309 32A 3-pin 250VAC IP44 data
center receptacles, and requires 22 kVA, 1-phase
Figure 1-3 (page 1-37) shows the high-voltage single phase PDU power connector for
EMEA, and APAC, except for Japan and Taiwan.
Table 1-30 (page 1-40) lists the requirements for low-voltage 24 kVA three phase
PDUs. There are two PDUs per rack. The following specifications are per PDU.
Table 1-30 Low-voltage 24 kVA Three Phase PDUs for North America, South
America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Voltage200 - 208 VAC 3-phase
Frequency50/60 Hz
Current34.6 A maximum per phase
Power rating25 kVA
Output current120 A (6 x 20 A)
1-40
Page 53
Chapter 1
Electrical Power Requirements
Table 1-30 (Cont.) Low-voltage 24 kVA Three Phase PDUs for North America,
South America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 2-pole circuit
breaker)
Data center receptacleIEC309-3P4W-IP67 60A 250VAC 3ph
20A
(Hubbell equivalent is HBL460R9W)
The following are needed to connect an Oracle Exadata system to a low-voltage threephase power source:
•4 power cords for two PDUs
•4 receptacles to connect the PDUs
Table 1-31 (page 1-41) lists the PDU requirements for high-voltage 24 kVA three
phase PDUs. The following specifications are per PDU.
Table 1-31 High-voltage 24 kVA Three Phase PDUs for Europe, the Middle East
and Africa (EMEA), and Asia Pacific (APAC), except for Japan and Taiwan (2
PDUs per Rack)
OptionRequirement, per PDU
Voltage220/380 - 240/415 VAC 3-phase
Frequency50/60 Hz
Current18.1 A maximum per phase
Power rating25 kVA
Output current108.6A (6 x 18.1 A)
Outlets42 x C13; 6 x C19
Outlet groups6
Group protection (UL489 1-pole circuit
breaker)
Data center receptacleIEC309-4P5W-IP44 32A 400VAC 3ph
20A
(Hubbell equivalent is HBL532R6W)
The following are needed to connect an Oracle Exadata system to a high-voltage
three-phase power source:
•4 power cords for two PDUs
•4 receptacles to connect the PDUs
Table 1-32 (page 1-42) lists the requirements for 37 kVA low-voltage three-phase
PDUs for Oracle Exadata Database Machine X6-8, X5-8, and X4-8 with more than four
database servers. There are two PDUs per rack. The following specifications are per
PDU.
1-41
Page 54
Chapter 1
Electrical Power Requirements
Table 1-32 Low-voltage 37 kVA Three Phase PDUs for North America, South
America, Japan and Taiwan (2 PDUs per Rack)
OptionRequirement, per PDU
Voltage200 - 208 VAC
Frequency50/60 Hz
Current34.6 A maximum per phase
Power rating37 kVA
Output current180 A (9 x 20 A)
Outlets44 C13 and 9 C19
Outlet groups6
Group protection (UL489 1-pole circuit
breaker)
Data center receptacleIEC 309-3P4W-IP67 plugs
20 A
The following are needed to connect an Oracle Exadata system to a low-voltage threephase power source:
•3 power cords for each PDU, 60 amperes at 190 - 220 VAC three-phase
•3 receptacles to connect the PDUs to 2 IEC 60309 60A 4-pin 250VAC 3ph IP67
data center receptacles
•Figure 1-2 (page 1-37) shows the low-voltage 37 kVA single phase PDU power
connector for North America, South America, Japan and Taiwan.
Table 1-33 (page 1-42) lists the requirements for 37 kVA high-voltage three-phase
PDUs for Oracle Exadata Database Machine X6-8, X5-8, and X4-8 with more than four
database servers. There are two PDUs per rack. The following specifications are per
PDU.
Table 1-33 High-voltage 37 kVA Three Phase PDUs for Europe, the Middle East
and Africa (EMEA), and Asia Pacific (APAC), except for Japan and Taiwan (2
PDUs per Rack)
OptionRequirement, per PDU
Voltage220/380 - 240/415 VAC
Frequency50/60 Hz
Current18 A maximum per phase
Power rating37 kVA
Output current163 A (9 x 18.1 A)
Outlets45 C13 and 9 C19
Outlet groups6
Group protection (UL489 1-pole circuit
breaker)
Data center receptacleIEC 309-4P5W-IP44
20A
1-42
Page 55
The following are needed to connect an Oracle Exadata system to a low-voltage threephase power source:
•2 power cords for two PDUs, 60 amperes at 190 - 220 VAC three-phase
•3 receptacles to connect the PDUs to 2 IEC 60309 60A 4-pin 250VAC 3ph IP67
data center receptacles
•Figure 1-4 (page 1-38) shows the high-voltage 37 kVA three phase PDU power
connector for Europe, the Middle East and Africa (EMEA), and Asia Pacific
(APAC), except for Japan and Taiwan.
1.4.2 Facility Power Requirements
Electrical work and installations must comply with applicable local, state, or national
electrical codes. Contact your facilities manager or qualified electrician to determine
what type of power is supplied to the building.
To prevent catastrophic failures, design the input power sources to ensure adequate
power is provided to the PDUs. Use dedicated AC breaker panels for all power circuits
that supply power to the PDU. When planning for power distribution requirements,
balance the power load between available AC supply branch circuits. In the United
States and Canada, ensure that the overall system AC input current load does not
exceed 80 percent of the branch circuit AC current rating.
Chapter 1
Electrical Power Requirements
PDU power cords are 4 meters (13.12 feet) long, and 1 to 1.5 meters (3.3 to 4.9 feet)
of the cord is routed within the rack cabinet. The installation site AC power receptacle
must be within 2 meters (6.6 feet) of the rack.
1.4.3 Circuit Breaker Requirements
To prevent catastrophic failures, the design of your power system must ensure that
adequate power is provided to the servers. Use dedicated AC breaker panels for all
power circuits that supply power to the server. Electrical work and installations must
comply with applicable local, state, or national electrical codes. Servers require
electrical circuits be grounded to the Earth.
In addition to circuit breakers, provide a stable power source, such as an
uninterruptible power supply (UPS) to reduce the possibility of component failures. If
computer equipment is subjected to repeated power interruptions and fluctuations,
then it is susceptible to a higher rate of component failure.
Note:
Circuit breakers are supplied by the customer. One circuit breaker is required
for each power cord.
1.4.4 Grounding Guidelines
The cabinets for Oracle Exadata Rack are shipped with grounding-type power cords.
Always connect the cords to grounded power outlets. Because different grounding
methods are used, depending on location, check the grounding type, and refer to
documentation, such as IEC documents, for the correct grounding method. Ensure
1-43
Page 56
Temperature and Humidity Requirements
that the facility administrator or qualified electrical engineer verifies the grounding
method for the building, and performs the grounding work.
1.5 Temperature and Humidity Requirements
Airflow through Oracle Exadata Rack is from front to back. Refer to General
Environmental Requirements (page 1-1) for information on cooling and airflow.
Note:
Studies have shown that temperature increases of 10 degrees Celsius (15
degrees Fahrenheit) above 20 degrees Celsius (70 degrees Fahrenheit)
reduce long-term electronics reliability by 50 percent.
Excessive internal temperatures may result in full or partial shut down of
Oracle Exadata Database Machine.
Chapter 1
The following table lists the temperature, humidity and altitude requirements for
operating and non-operating machines.
Table 1-34 Temperature, Humidity and Altitude Requirements
ConditionOperating
Requirement
Temperature5 to 32 degrees
Celsius (41 to 89.6
degrees Fahrenheit)
Relative humidity10 to 90 percent
relative humidity, noncondensing
Altitude3048 meters (10000
feet) maximum
Non-operating
Requirement
-40 to 70 degrees
Celsius (-40 to 158
degrees Fahrenheit).
Up to 93 percent
relative humidity.
12000 meters (40000
feet).
Optimum
For optimal rack
cooling, data center
temperatures from 21
to 23 degrees Celsius
(70 to 74 degrees
Fahrenheit)
For optimal data
center rack cooling,
45 to 50 percent, noncondensing
Ambient temperature
is reduced by 1
degree Celsius per
300 m above 900 m
altitude above sea
level
Set conditions to the optimal temperature and humidity ranges to minimize the chance
of downtime due to component failure. Operating Oracle Exadata Rack for extended
periods at or near the operating range limits, or installing it in an environment where it
remains at or near non-operating range limits could significantly increase hardware
component failure.
The ambient temperature range of 21 to 23 degrees Celsius (70 to 74 degrees
Fahrenheit) is optimal for server reliability and operator comfort. Most computer
equipment can operate in a wide temperature range, but near 22 degrees Celsius (72
degrees Fahrenheit) is desirable because it is easier to maintain safe humidity levels.
1-44
Page 57
Chapter 1
Ventilation and Cooling Requirements
Operating in this temperature range provides a safety buffer in the event that the air
conditioning system goes down for a period of time.
The ambient relative humidity range of 45 to 50 percent is suitable for safe data
processing operations. Most computer equipment can operate in a wide range (20 to
80 percent), but the range of 45 to 50 percent is recommended for the following
reasons:
•Optimal range helps protect computer systems from corrosion problems
associated with high humidity levels.
•Optimal range provides the greatest operating time buffer in the event of air
conditioner control failure.
•This range helps avoid failures or temporary malfunctions caused by intermittent
interference from static discharges that may occur when relative humidity is too
low.
Note:
Electrostatic discharge (ESD) is easily generated, and hard to dissipate in
areas of low relative humidity, such as below 35 percent. ESD becomes
critical when humidity drops below 30 percent. It is not difficult to maintain
humidity in a data center because of the high-efficiency vapor barrier and low
rate of air changes normally present.
1.6 Ventilation and Cooling Requirements
Always provide adequate space in front and behind the rack to allow for proper
ventilation.
Do not obstruct the front or rear of the rack with equipment or objects that might
prevent air from flowing through the rack. Rack-mountable servers and equipment
typically draw cool air in through the front of the rack and let out warm air out the rear
of the rack. There is no air flow requirement for the left and right sides due to front-toback cooling.
If the rack is not completely filled with components, then cover the empty sections with
filler panels. Gaps between components can adversely affect air flow and cooling
within the rack.
Relative humidity is the percentage of the total water vapor that can exist in the air
without condensing, and is inversely proportional to air temperature. Humidity goes
down when the temperature rises, and goes up when the temperature drops. For
example, air with a relative humidity of 45 percent at a temperature of 24 degrees
Celsius (75 degrees Fahrenheit) has a relative humidity of 65 percent at a temperature
of 18 degrees Celsius (64 degrees Fahrenheit). As the temperature drops, the relative
humidity rises to more than 65 percent, and water droplets are formed.
Air conditioning facilities usually do not precisely monitor or control temperature and
humidity throughout an entire computer room. Generally, monitoring is done at
individual points corresponding to multiple exhaust vents in the main unit, and other
units in the room. Special consideration should be paid to humidity when using
underfloor ventilation. When underfloor ventilation is used, monitoring is done at each
1-45
Page 58
Chapter 1
Ventilation and Cooling Requirements
point close to an exhaust vent. Distribution of the temperature and humidity across the
entire room is uneven.
Oracle Exadata Racks have been designed to function while mounted in a natural
convection air flow. The following requirements must be followed to meet the
environmental specification:
•Ensure there is adequate air flow through the server.
•Ensure the server has front-to-back cooling. The air inlet is at the front of the
server, and the air is let out the rear.
•Allow a minimum clearance of 1219.2 mm (48 inches) at the front of the server,
and 914 mm (36 inches) at the rear of the server for ventilation.
Use perforated tiles, approximately 400 CFM/tile, in front of the rack for cold air intake.
The tiles can be arranged in any order in front of the rack, as long as cold air from the
tiles can flow into the rack. Inadequate cold air flow could result in a higher inlet
temperature in the servers due to exhaust air recirculation. The following table
describes the recommended number of floor tiles:
Type of Oracle Exadata Database Machine
or Oracle Exadata Storage Expansion Rack
Oracle Exadata full rack systems4
Oracle Exadata half rack systems3
Oracle Exadata quarter and eighth rack
systems
Recommended Number of Floor Tiles
1
Figure 1-6 (page 1-46) shows a typical installation of the floor tiles for Oracle Exadata
Database Machine Full Rack in a typical data center.
Figure 1-6 Typical Data Center Configuration for Perforated Floor Tiles
1-46
Page 59
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
1.7 Network Connection and IP Address Requirements for
Oracle Exadata Database Machine
The network cables must be run from your network equipment to the location of Oracle
Exadata Database Machine. The requirements to connect to your existing Ethernet
network infrastructure are described in the following sections:
1.7.1 Network Connection Requirements for Oracle Exadata Database
Machine
Prior to installation, network cables must be run from your existing network
infrastructure to the installation site. The requirements to connect Oracle Exadata
Database Machine to your existing network infrastructure are as follows:
•Management network connection requirements for all Oracle Exadata Database
Machine systems except for X2-n systems:
–1 Ethernet connection for the Ethernet switch in the rack to the existing
management network.
•Management network connection requirements for Oracle Exadata Database
Machine X2-n:
–1 Ethernet connection for the Ethernet switch in the rack to the existing
management network.
–1 Ethernet connection for the KVM switch in the rack to the existing
management network.
•Client access network connection requirements
–One Ethernet connection per database server to the client access network.
The number depends on the system type (Oracle Exadata Database Machine
Full Rack, Oracle Exadata Database Machine Half Rack, or Oracle Exadata
Database Machine Quarter Rack), and whether network channel bonding is
used. Use the following formula to determine the number of connections you
need:
For bonded configurations, you need two network connections for each
database node.
For non-bonded configurations, you need one network connection for each
database node.
•Additional network NET2 connection requirements
One Ethernet connection per database server to connect NET2 to your existing
network. The number depends on the system type, as follows:
For bonded configurations, you need two network connections for each database
node.
For non-bonded configurations, you need one network connection for each
database node.
1-47
Page 60
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Note:
–This network is unavailable if network channel bonding is used for the
client access network.
–This network is optional. A cable is not required unless the network is
configured during deployment.
•Additional network NET3 connection requirements
One Ethernet connection per database server to connect NET3 to your existing
network. The number depends on the system type, as follows:
–8 connections for Oracle Exadata Database Machine 2-socket, full rack
systems
–4 connections for Oracle Exadata Database Machine 2-socket, half rack
systems
–2 connections for Oracle Exadata Database Machine 2-socket, quarter rack
systems
Chapter 1
–2 connections for Oracle Exadata Database Machine 8-socket, full rack
systems
Note:
This network is optional. A cable is not required unless the network is
configured during deployment.
Oracle Exadata Database Machine X2-8 Full Rack has a total of 16 Ethernet ports per
server. The additional networks for Oracle Exadata Database Machine X2-8 Full Rack
are NET2 through NET15.
The following table shows examples of connection requirements for different sample
environments. The table applies to two-socket x86 Oracle Exadata Database Machine
X3-2 and later.
Table 1-35 Examples of Network Configurations and Connection Requirements
for Oracle Exadata Database Machine 2-Socket Systems X3-2 and Later
ScenarioNetwork Requirements
Core Requirements•1 for Ethernet switch
•2 for PDU monitoring
Bonded network configuration, and connected
to a dedicated backup network
•2 per database node for client access for
bonded Ethernet interface on database
servers
•1 per database node for backup network
access for database servers
Total = 3 + (3 * number of database nodes)
1-48
Page 61
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-35 (Cont.) Examples of Network Configurations and Connection
Requirements for Oracle Exadata Database Machine 2-Socket Systems X3-2 and
Later
ScenarioNetwork Requirements
Non-bonded network configuration, and
connected to a dedicated backup network and
a dedicated disaster recovery network
Non-bonded network configuration, and not
connected to an additional network
Non-bonded network configuration, and
connected to a dedicated backup network
•1 for each database node for client
access for the database servers
•1 per database node for backup network
access for the database servers
•1 per database node for disaster recovery
network access for the database servers
Total = 3 + (3 * number of database nodes)
•1 per database node for database servers
Total = 3 + (1 * database node)
•1 for each database node for client
access for the database servers
•1 per database node for backup network
access for the database servers
Total = 3 + (2 * number of database nodes)
The following table shows examples of connection requirements for different sample
environments with Oracle Exadata Database Machine X2-2.
Table 1-36 Examples of Network Configurations and Connection Requirements
for Oracle Exadata Database Machine X2-2
ScenarioNetwork Requirements
Oracle Exadata Database Machine X2-2 Full
Rack using a bonded network configuration,
and connected to a dedicated backup network
Oracle Exadata Database Machine X2-2 Full
Rack using a non-bonded network
configuration, and connected to a dedicated
backup network and a dedicated disaster
recovery network
Requires 28 connections to your existing
networks
•1 for Ethernet switch
•1 for KVM switch
•16 for database client access for bonded
Ethernet interface on database servers
•8 for backup network access for database
servers
•2 for monitoring the PDUs
Requires 28 connections to your existing
networks
•1 for Ethernet switch
•1 for KVM switch
•8 for database client access for the
database servers
•8 for backup network access for the
database servers
•8 for disaster recovery network access for
the database servers
•2 for monitoring the PDUs
1-49
Page 62
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-36 (Cont.) Examples of Network Configurations and Connection
Requirements for Oracle Exadata Database Machine X2-2
ScenarioNetwork Requirements
Oracle Exadata Database Machine X2-2 Half
Rack using a non-bonded network
configuration, and not connected to an
additional network
Oracle Exadata Database Machine X2-2
Quarter Rack using a non-bonded network
configuration, and connected to a dedicated
backup network
Requires 8 connections to your existing
networks
•1 for Ethernet switch
•1 for KVM switch
•4 for database servers
•2 for monitoring the PDUs
Requires 8 connections to your existing
networks
•1 for Ethernet switch
•1 for KVM switch
•2 for database client access for the
database servers
•2 for backup network access for the
database servers
•2 for monitoring the PDUs
Chapter 1
Related Topics:
•Understanding the Network Requirements for Oracle Exadata Database Machine
(page 2-1)
1.7.2 DNS Configuration for Oracle Exadata Database Machine
Prior to receiving your Oracle Exadata Database Machine, use Oracle Exadata
Database Machine Deployment Assistant. The assistant generates a file to be used
when setting up the system. The host names and IP addresses specified in the
assistant-generated file for the management network, client access network, and
additional networks should be registered in Domain Name System (DNS) prior to initial
configuration. In addition, all public addresses, single client access name (SCAN)
addresses, and VIP addresses should be registered in DNS prior to installation.
The assistant-generated file defines the SCAN as a single name with three IP
addresses on the client access network. The three SCAN addresses provide service
access for clients to Oracle Exadata Database Machine. Configure DNS for round
robin resolution for the SCAN name to these three SCAN addresses.
All addresses registered in DNS must be configured for both forward resolution and
reverse resolution. Reverse resolution must be forward confirmed (forward-confirmed
reverse DNS) such that both the forward and reverse DNS entries match each other.
Note:
Grid Naming Service (GNS) is not configured on Oracle Exadata Database
Machine during initial configuration.
1-50
Page 63
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
•Oracle Grid Infrastructure Installation and Upgrade Guide for Linux for
additional information about SCAN addresses
•Your DNS vendor documentation for additional information about
configuring round robin name resolution
1.7.3 IP Address Requirements for Oracle Exadata Database Machine
Oracle Exadata Database Machine requires a large number of host names and IP
addresses during initial configuration. The number of IP addresses required for a
particular network, such as the management network, depends on the type of system.
The network configuration, such as host names and IP addresses, used during
installation is generated from information when completing the Oracle Exadata
Database Machine Deployment Assistant.
Configure the new IP addresses in your existing networks only after you have run
Oracle Exadata Database Machine Deployment Assistant. All IP addresses in the
assistant-generated file must be unassigned at the time of initial configuration. In
addition, all IP addresses must be statically-assigned IP addresses, not dynamicallyassigned (DHCP) addresses.
All InfiniBand addresses must be in the same subnet, with a minimum subnet mask of
255.255.240.0 (or /20). The subnet mask chosen should be wide enough to
accommodate possible future expansion of the Oracle Exadata Database Machine
and InfiniBand network.
The following table lists the IP address requirements for Oracle Exadata Database
Machine X5-2 and later systems:
1-51
Page 64
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-37 IP Address Requirements for Oracle Exadata Database Machine X5-2 and Later
Systems
Chapter 1
Type of Oracle
Exadata Database
Machine
Oracle Exadata
Database Machine
X5-2 and later Full
Rack
Management
Network
Requirements
Minimum of 49 IP
addresses
•8 IP addresses
for
administration,
one per
database server
•14 IP addresses
for
administration,
one per Exadata
Storage Server
•8 IP addresses
for ILOM, one
per database
server
•14 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 19 IP
address
•8 IP addresses
for public
access, one per
database server
•8 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC
Additional
Networks (NET2
and NET3)
Requirements
Minimum of 8 IP
addresses for each
additional network
•8 IP addresses
for the database
servers, one per
database server
If using a bonded
network configuration
for the client access
network, then NET2
cannot be used as an
additional network.
InfiniBand Private
Network
Requirements
44 IP addresses
•16 IP addresses,
two per
database server
•28 IP addresses,
two per Exadata
Storage Server
1-52
Page 65
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-37 (Cont.) IP Address Requirements for Oracle Exadata Database Machine X5-2 and
Later Systems
Type of Oracle
Exadata Database
Machine
Oracle Exadata
Database Machine
X5-2 and later Half
Rack
Management
Network
Requirements
Minimum of 27 IP
addresses
•4 IP addresses
for
administration,
one per
database server
•7 IP addresses
for
administration,
one per Exadata
Storage Server
•4 IP addresses
for ILOM, one
per database
server
•7 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 11 IP
addresses
•4 IP addresses
for public
access, one per
database server
•4 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC.
Additional
Networks (NET2
and NET3)
Requirements
Minimum of 4 IP
addresses for each
additional network
•4 IP addresses
for the database
servers, one per
database server
If using a bonded
network configuration
for the client access
network, then NET2
cannot be used as an
additional network.
InfiniBand Private
Network
Requirements
For X6-2 and X5-2
Half Rack: 22 IP
addresses:
•8 IP addresses,
two per
database server
•14 IP addresses,
two per Exadata
Storage Server
1-53
Page 66
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-37 (Cont.) IP Address Requirements for Oracle Exadata Database Machine X5-2 and
Later Systems
Type of Oracle
Exadata Database
Machine
•Oracle Exadata
Database
Machine X5-2
and later Quarter
Rack
•Oracle Exadata
Database
Machine X5-2
and later Eighth
Rack
Management
Network
Requirements
Minimum of 15 IP
addresses
•2 IP addresses
for
administration,
one per
database server
•3 IP addresses
for
administration,
one per Exadata
Storage Server
•2 IP addresses
for ILOM, one
per database
server
•3 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 7 IP
addresses
•2 IP addresses
for public
access, one per
database server
•2 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC.
Additional
Networks (NET2
and NET3)
Requirements
Minimum of 2 IP
addresses for each
additional network
•2 IP addresses
for the database
servers, one per
database server
If using a bonded
network configuration
for the client access
network, then NET2
cannot be used as an
additional network.
InfiniBand Private
Network
Requirements
For X5-2 and X6-2:
10 IP addresses:
•4 IP addresses,
two per
database server
•6 IP addresses,
two per Exadata
Storage Server
1-54
Page 67
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-37 (Cont.) IP Address Requirements for Oracle Exadata Database Machine X5-2 and
Later Systems
Type of Oracle
Exadata Database
Machine
Oracle Exadata
Database Machine
X5-8 and X6-8 Full
Rack
Management
Network
Requirements
Minimum of 37 IP
addresses
•2 IP addresses
for
administration,
one per
database server
•14 IP addresses
for
administration,
one per Exadata
Storage Server
•2 IP addresses
for ILOM, one
per database
server
•14 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 7 IP
addresses
•2 IP addresses
for public
access, one per
database server
•2 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC
Additional
Networks (NET2
and NET3)
Requirements
InfiniBand Private
Network
Requirements
44 IP addresses
•16 IP addresses,
two per
database server
•28 IP addresses,
two per Exadata
Storage Server
1-55
Page 68
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-37 (Cont.) IP Address Requirements for Oracle Exadata Database Machine X5-2 and
Later Systems
Type of Oracle
Exadata Database
Machine
Oracle Exadata
Database Machine
X5-8 and X6-8 Half
Rack
Management
Network
Requirements
Minimum of 15 IP
addresses
•2 IP addresses
for
administration,
one per
database server
•3 IP addresses
for
administration,
one per Exadata
Storage Server
•2 IP addresses
for ILOM, one
per database
server
•3 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 7 IP
addresses
•2 IP addresses
for public
access, one per
database server
•2 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC
Additional
Networks (NET2
and NET3)
Requirements
InfiniBand Private
Network
Requirements
22 IP addresses
•16 IP addresses,
two per
database server
•6 IP addresses,
two per Exadata
Storage Server
The following table lists the IP address requirements for Oracle Exadata Database
Machine X4-2, and Oracle Exadata Database Machine X4-8 Full Rack:
1-56
Page 69
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-38 IP Address Requirements for Oracle Exadata Database Machine X4-2 and X4-8 Full
Rack
Type of Oracle
Exadata Database
Machine
Oracle Exadata
Database Machine
X4-2 Full Rack
Management
Network
Requirements
Minimum of 49 IP
addresses
•8 IP addresses
for
administration,
one per
database server
•14 IP addresses
for
administration,
one per Exadata
Storage Server
•8 IP addresses
for ILOM, one
per database
server
•14 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 19 IP
address
•8 IP addresses
for public
access, one per
database server
•8 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC
Additional
Networks (NET2
and NET3)
Requirements
Minimum of 8 IP
addresses for each
additional network
•8 IP addresses
for the database
servers, one per
database server
If using a bonded
network configuration
for the client access
network, then NET2
cannot be used as an
additional network.
InfiniBand Private
Network
Requirements
44 IP addresses
•16 IP addresses,
two per
database server
•28 IP addresses,
two per Exadata
Storage Server
1-57
Page 70
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-38 (Cont.) IP Address Requirements for Oracle Exadata Database Machine X4-2 and
X4-8 Full Rack
Type of Oracle
Exadata Database
Machine
Oracle Exadata
Database Machine
X4-2 Half Rack
Management
Network
Requirements
Minimum of 27 IP
addresses
•4 IP addresses
for
administration,
one per
database server
•7 IP addresses
for
administration,
one per Exadata
Storage Server
•4 IP addresses
for ILOM, one
per database
server
•7 IP addresses
for ILOM, one
per Exadata
Storage Server
•3 IP addresses
for switches: 2
for InfiniBand,
and 1 for
Ethernet
•2 IP addresses
for monitoring
electric current
of the PDUs
Client Access
Network
Requirements
Minimum of 11 IP
addresses
•4 IP addresses
for public
access, one per
database server
•4 IP addresses
for Oracle RAC
VIP addresses,
one per
database server
•3 IP addresses
for SCAN
addresses for
Oracle RAC.
Additional
Networks (NET2
and NET3)
Requirements
Minimum of 4 IP
addresses for each
additional network
•4 IP addresses
for the database
servers, one per
database server
If using a bonded
network configuration
for the client access
network, then NET2
cannot be used as an
additional network.
InfiniBand Private
Network
Requirements
22 IP addresses
•8 IP addresses,
two per
database server
•14 IP addresses,
two per Exadata
Storage Server
1-58
Page 71
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-38 (Cont.) IP Address Requirements for Oracle Exadata Database Machine X4-2 and
X4-8 Full Rack
1.7.3.1 Calculating the IP Address Requirements when Using Oracle VMs
The number of IP addresses depends on the physical deployment, as well as the
number of virtual user domains. The following equations show how to calculate the
number of IP addresses required for the physical deployment and Oracle VM
deployment.
Physical deployment with a single cluster:
Number of management network IP addresses =
(number of databases servers)*2 + \
(number of storage servers)*2 + \
(number of PDUs) + \
(number of IB switches) + \
1-69
Page 82
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
(number of Ethernet switches)
Number of client access network IP addresses =
(number of database servers)*2 + 3
Number of InfiniBand network IP addresses =
(number of database servers)*2 + \
(number of storage servers)*2
Number of additional network IP addresses =
(number of database servers) * (number of additional networks)
Oracle VM deployment:
Number of management network IP addresses =
(number of databases servers)*2 + \
(number of Oracle VM user domains) + \
(number of storage servers)*2 + \
(number of PDUs) + \
(number of IB switches) + \
(number of Ethernet switches) \
Number of client access network IP addresses =
(number of Oracle VM user domains)*2 + \
(number of Oracle RAC VM clusters)*3
Chapter 1
Number of InfiniBand network IP addresses =
(number of Oracle VM user domains)*2 + \
(number of storage servers)*2
Number of additional network IP addresses =
(number of database servers) * (number of Oracle VM user domains)
Table 1-41 (page 1-71) shows the network requirements by component. The IP
address numbers are per component, not rack.
1-70
Page 83
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
Table 1-41 IP Address Requirements by Component
Chapter 1
ComponentManagement
Network
Database serverPhysical
deployment
•1 IP address
for
administratio
n
•1 IP address
for ILOM
Oracle VM
deployment
•1 IP address
for
administratio
n of
management
domain
•1 IP address
for ILOM
•1 IP address
for each user
domain for
administratio
n
Exadata Storage
Server
InfiniBand switch 1 IP addressNoneNoneNone
Ethernet switch1 IP addressNoneNoneNone
PDU1 IP addressNoneNoneNone
•1 IP address
for
administratio
n
•1 IP address
for ILOM
Client Access
Network
Physical
deployment
•1 IP address
for public
access
•1 IP address
for Oracle
RAC VIP
•3 IP
addresses
for each
Oracle RAC
cluster
SCAN
addresses
Oracle VM
deployment
•1 IP address
for each user
domain
public
access
•1 IP address
for each user
domain
Oracle RAC
VIP
•3 IP
addresses
for each
Oracle RAC
VM SCAN
addresses
NoneNone2 IP addresses
Additional
Networks (NET2
and NET3)
Physical
deployment
•1 IP address
for each
additional
configured
network
Oracle VM
deployment
•1 IP address
for each user
domain for
each
additional
configured
network
InfiniBand
Private Network
Physical
deployment
•2 IP address
Oracle VM
deployment
•2 IP
when using
active-active
bonding, or 1 IP
address when
not using activeactive bonding.
es when
using activeactive
bonding, or 1
IP address
when not
using activeactive
bonding
addresses
for each user
domain
when using
active-active
bonding, or 1
IP address
for each user
domain
when not
using activeactive
bonding
Table 1-42 (page 1-72) shows examples of IP addresses requirements when using
Oracle VMs.
1-71
Page 84
Network Connection and IP Address Requirements for Oracle Exadata Storage Expansion Rack
Table 1-42 Examples of IP Address Requirements when Using Oracle VMs
DeploymentIP Address Requirements
Oracle Exadata Database Machine X6-2
Quarter Rack and Oracle Exadata Database
Machine X5-2 Quarter Rack with the following
configuration:
•Oracle VM deployment with two 2-node
Oracle RAC VM clusters (2 clusters and 4
user domains total)
•No additional networks
•Active-active bonding on the InfiniBand
network
Oracle Exadata Database Machine X6-2 Full
Rack and Oracle Exadata Database Machine
X5-2 Full Rack with the following
configuration:
•Oracle VM deployment with one 8-node
Oracle RAC VM cluster, and five 2-node
Oracle RAC VM clusters (6 clusters and
18 user domains total)
•No additional networks
•Active-active bonding on the InfiniBand
network
Oracle Exadata Database Machine X6-2
Elastic Configuration and Oracle Exadata
Database Machine X5-2 Elastic Configuration
with the following configuration:
•3 database servers, 9 Exadata Storage
Servers, and 2 InfiniBand switches
•Oracle VM deployment with two 3-node
Oracle RAC VM clusters (2 clusters and 6
user domains total)
•Dedicated backup network
•Active-active bonding on the InfiniBand
network
•19 IP addresses for the management
network
•14 IP addresses for the client access
network
•No IP addresses for the additional
networks
•14 IP addresses for the InfiniBand
network
•67 IP addresses for the management
network
•54 IP addresses for the client access
network
•No IP addresses for the additional
networks
•64 IP addresses for the InfiniBand
network
•37 IP addresses for the management
network
•18 IP addresses for the client access
network
•6 IP addresses for the additional networks
•30 IP addresses for the InfiniBand
network
Chapter 1
1.8 Network Connection and IP Address Requirements for
Oracle Exadata Storage Expansion Rack
Prior to installation, network cables must be run from your existing network
infrastructure to the installation site.
The requirements to connect Oracle Exadata Storage Expansion Rack to Oracle
Exadata Database Machine are as follows:
•Management network connection requirements for Oracle Exadata Storage
Expansion Rack X4-2 and later:
–1 Ethernet connection from the ILOM to each Exadata Storage Server. For
Oracle Exadata Storage Expansion Full Rack, there are 18 connections, for
Oracle Exadata Storage Expansion Half Rack there are 9 connections, and for
Oracle Exadata Storage Expansion Quarter Rack there are 4 connections.
1-72
Page 85
Network Connection and IP Address Requirements for Oracle Exadata Storage Expansion Rack
–1 Ethernet connection for each Sun Datacenter InfiniBand Switch 36.
–1 Ethernet connection for each Exadata Storage Server. For Oracle Exadata
Storage Expansion Full Rack, there are 18 connections, for Oracle Exadata
Storage Expansion Half Rack there are 9 connections, and for Oracle Exadata
Storage Expansion Quarter Rack there are 4 connections.
–1 Ethernet connection for the Ethernet switch in the rack to the existing
management network.
–1 Ethernet connection for each of the two PDUs. Network connectivity to the
PDUs is only required if the electric current is monitored remotely.
•Management network connection requirements for Oracle Exadata Storage
Expansion Rack X3-2
–1 Ethernet connection from the ILOM to each Exadata Storage Server. For
Oracle Exadata Storage Expansion Full Rack, there are 18 connections, for
Oracle Exadata Storage Expansion Half Rack there are 9 connections, and for
Oracle Exadata Storage Expansion Quarter Rack there are 4 connections.
–1 Ethernet connection for each Sun Datacenter InfiniBand Switch 36.
–1 Ethernet connection for each Exadata Storage Server. For Oracle Exadata
Storage Expansion Full Rack, there are 18 connections, for Oracle Exadata
Storage Expansion Half Rack there are 9 connections, and for Oracle Exadata
Storage Expansion Quarter Rack there are 4 connections.
Chapter 1
–1 Ethernet connection for the Ethernet switch in the rack to the existing
management network.
–1 Ethernet connection for each of the two PDUs. Network connectivity to the
PDUs is only required if the electric current is monitored remotely.
•Management network connection requirements for Oracle Exadata Storage
Expansion Rack with Exadata Storage Server with Sun Fire X4270 M2 Servers
–1 Ethernet connection from the ILOM to each Exadata Storage Server. For
Oracle Exadata Storage Expansion Full Rack, there are 18 connections, for
Oracle Exadata Storage Expansion Half Rack there are 9 connections, and for
Oracle Exadata Storage Expansion Quarter Rack there are 4 connections.
–1 Ethernet connection for each Sun Datacenter InfiniBand Switch 36.
–1 Ethernet connection for each Exadata Storage Server. For Oracle Exadata
Storage Expansion Full Rack, there are 18 connections, for Oracle Exadata
Storage Expansion Half Rack there are 9 connections, and for Oracle Exadata
Storage Expansion Quarter Rack there are 4 connections.
–1 Ethernet connection for the Ethernet switch in the rack to the existing
management network.
–1 Ethernet connection for the KVM switch in the rack to the existing
management network. This connection is only for Oracle Exadata Database
Machine X2-2 racks.
–1 Ethernet connection for each of the two PDUs. Network connectivity to the
PDUs is only required if the electric current is monitored remotely.
The following table lists the IP address requirements for Oracle Exadata Storage
Expansion Racks:
1-73
Page 86
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Storage Expansion Rack
Table 1-43 IP Address Requirements for Oracle Exadata Storage Expansion
Rack
Type of Oracle Exadata Storage Expansion
Rack
Oracle Exadata Storage Expansion X4-2 Full
Rack and later
Total of 60 IP addresses (42 for the
management network, and 18 for the private
InfiniBand network)
•18 IP addresses for administration, one
per Exadata Storage Server
•18 IP addresses for ILOM, one per
Exadata Storage Server
•4 IP addresses for switches (3 for
InfiniBand, and 1 for Ethernet)
•2 IP addresses for monitoring electric
current of the PDUs
•18 IP addresses for the private InfiniBand
network
Total of 33 IP addresses (24 for the
management network, and 9 for the private
InfiniBand network)
•9 IP addresses for administration, one per
Exadata Storage Server
•9 IP addresses for ILOM, one per
Exadata Storage Server
•4 IP addresses for switches (3 for
InfiniBand, and 1 for Ethernet)
•2 IP addresses for monitoring electric
current of the PDUs
•9 IP addresses for the private InfiniBand
network
Total of 17 IP addresses (13 for the
management network, and 4 for the InfiniBand
network)
•4 IP addresses for administration, one per
Exadata Storage Server
•4 IP addresses for ILOM, one per
Exadata Storage Server
•3 IP addresses for switches (2 for
InfiniBand, and 1 for Ethernet)
•2 IP addresses for monitoring electric
current of the PDUs
•4 IP addresses for the private InfiniBand
network
1.9 Ensuring Site is Ready
Before Oracle Exadata Rack is delivered to the site, the following tasks must be
performed to ensure the site is ready:
1-75
Page 88
Chapter 1
Ensuring Site is Ready
Task 1 Review Site Requirements
Review the site requirements in this chapter and use the checklists in Site Checklists
(page A-1) to understand the requirements for Oracle Exadata Rack.
Task 2 Run the Oracle Exadata Database Machine Deployment Assistant
Run the Oracle Exadata Database Machine Deployment Assistant to create the
necessary files.
Task 3 Configure the Network
Configure the network using the files from Oracle Exadata Database Machine
Deployment Assistant. This includes registering the networks in the Domain Name
System (DNS), assigning IP addresses, and configuring data center switches and
firewalls.
Task 4 Prepare the Site Based on Requirements
Prepare the site based on the requirements, such as, install the network cables and
power supplies, prior to the arrival of Oracle Exadata Rack:
1.Review the safety guidelines.
2.Note problems or peculiarities at the site that require special equipment. For
example, ensure the doors are tall enough and wide enough for Oracle Exadata
Rack.
3.Verify that the installation site flooring has a strength rating to withstand the
combined weight of Oracle Exadata Rack and any other installed equipment.
4.Install network cables for Oracle Exadata Rack.
5.Install all necessary electrical equipment, and ensure that sufficient power is
provided for Oracle Exadata Rack.
6.Ensure that the installation site provides adequate air conditioning.
7.Operate the air conditioning system for 48 hours to bring the room temperature to
the appropriate level.
8.Clean and vacuum the area thoroughly in preparation for installation.
Understanding the Network Requirements
for Oracle Exadata Database Machine
This chapter describes the network requirements for Oracle Exadata Database
Machine.
Note:
For ease of reading, the name "Oracle Exadata Rack" is used when
information refers to both Oracle Exadata Database Machine and Oracle
Exadata Storage Expansion Rack.
2.1 Overview of Network Requirements
Oracle Exadata Database Machine includes database servers, Exadata Storage
Servers, as well as equipment to connect the servers to your network. The network
connections allow the servers to be administered remotely, and clients to connect to
the database servers.
The information in this section should be used in conjunction with Oracle Exadata
Deployment Assistant to configure your environment for Oracle Exadata Database
Machine.
Note:
The name used for the InfiniBand interface changed from BONDIB0 to IB0 and
IB1 on Oracle Exadata Database Machine X4-2 systems using release
11.2.3.3.0 and later.
As of release 11.2.2.1.0, the names used for bonding changed. The names
are BONDIB0 for the InfiniBand bonding and BONDETH0 for Ethernet
bonding. In earlier releases, the names were BOND0 and BOND1,
respectively.
To deploy Oracle Exadata Database Machine ensure that you meet the minimum
network requirements. Oracle Exadata Database Machine requires a minimum of
three networks, and there are interfaces available for additional networks. Each
network must be on a distinct and separate subnet from the others. Oracle
recommends one common additional network for backup, which you can configure
with OEDA. The network descriptions are as follows:
•Management network: This required network connects to your existing
management network, and is used for administrative work for all components of
2-1
Page 90
Chapter 2
Overview of Network Requirements
Oracle Exadata Database Machine. It connects the servers, ILOM, and switches
connected to the Ethernet switch in the rack. There is one uplink from the Ethernet
switch in the rack to your management network, one uplink from the KVM switch in
the rack to your management network, and one uplink for each power distribution
unit (PDU).
Notes:
–Network connectivity to the PDUs is only required if the electric current is
monitored remotely.
–A properly secured configuration requires the management network to be
fully isolated from all other networks.
Each database server and Exadata Storage Server has two network interfaces for
management. One provides management access to the operating system through
the embedded NET0 Ethernet port on Oracle Exadata Database Machine TwoSocket systems, or the NEM0/NET1 Ethernet port on Oracle Exadata Database
Machine Eight-Socket systems. The other network interface provides access to
the ILOM through the NET MGT Ethernet port. Oracle Exadata Database
Machines are delivered with the NET MGT and NET0 or NEM0/NET0 ports
connected to the Ethernet switch in the rack. The NET0 or NEM0/NET0 port on
the database servers should not be used for client or application network traffic.
Cabling or configuration changes to these interfaces on Exadata Storage Servers
is not permitted.
•Client access network: This required network connects the database servers to
your existing client network and is used for client access to the database servers.
Applications access the database through this network using Single Client Access
Name (SCAN) and Oracle RAC Virtual IP (VIP) addresses. Database servers
support channel bonding to provide higher bandwidth or availability for client
connections to the database. Oracle recommends channel bonding for the client
access network.
The following list describes the channel bonding configurations:
–Oracle Exadata Database Machine Two-Socket systems, use either:
*The embedded NET1 and NET2 ports
*The two 10 GbE ports or two 10/25GbE ports on Oracle Exadata
Database Machine X7-2
–Oracle Exadata Database Machine Eight-Socket systems, X4-8 or higher
*Use two ports, with each port on a different PCIe card
–Oracle Exadata Database Machine X3-8 Full Rack and Oracle Exadata
Database Machine X2-8 Full Rack
*Use ports from each Network Express Module (NEM)
For the Oracle Exadata Database Machine X3-8 Full Rack and Oracle
Exadata Database Machine X2-8 Full Rack database servers, using the
same ports on the Network Express Modules, such as NEM0/NET1 and
NEM0/NET2, works but does not provide for high availability.
2-2
Page 91
Chapter 2
Overview of Network Requirements
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.
•Additional networks (optional): Database servers can connect to additional
existing networks using the available open ports not used by the management and
client networks.
•InfiniBand private network: This network connects the database servers and
Oracle Exadata Storage Servers using the InfiniBand switches on the rack.
Starting with the Oracle Exadata Storage X4-2L servers, the InfiniBand fabric is
connected using the IB0 and IB1 interfaces. Oracle Exadata Storage Server X3-2L
servers and earlier use the BONDIB0 interface. Oracle Database uses this
network for Oracle RAC cluster interconnect traffic and for accessing data on
Oracle Exadata Storage Servers. This non-routable network is fully contained in
Oracle Exadata Database Machine, and does not connect to your existing
network. This network is automatically configured during installation.
Note:
All networks must be on distinct and separate subnets from each other. For
better security, the management network should be isolated from all other
networks.
Oracle Exadata Database Machine database server networking requirements are
identical with the following exceptions:
•Oracle Exadata Database Machine X7-2 embedded ports are 1/10/25 GbE.
X5-2, Oracle Exadata Database Machine X4-2, and Oracle Exadata Database
Machine X3-2 embedded ports are 1 GbE/10 GbE.
•Oracle Exadata Database Machine X2-2 embedded ports are 1 GbE.
•Only Oracle Exadata Database Machine X2-2 has a KVM.
At start time on an 8-socket system, each database server generates a
cellaffinity.ora
oracle/cell/network-config directory, and must be readable by the Oracle
database.
The file contains a mapping between the NUMA node numbers and the IP address of
the network interface card closest to each node. Oracle Database uses the file to
select the closest network interface card when communicating with Exadata Storage
Servers, thereby optimizing performance. This file is only generated and used on an 8socket system. On a 2-socket system, there is no performance to be gained in this
manner, and no
a text editor.
configuration file. The
cellaffinity.ora
file. The file is not intended to be directly edited with
cellaffinity.or
a file resides in the /etc/
The following image shows the default network diagram for Oracle Exadata Database
Machine X7-2. Use the files from Oracle Exadata Database Machine Deployment
2-3
Page 92
Key
Management
Client Access
Private InfiniBand
* BONDETH0 can be either be
copper or optical links
NET0ILOM
IB0IB1IB1IB0
BONDETH0
NET0
NET3NET4
NET1NET2
ILOM
Ethernet
Switch
PDU APDU B
InfiniBand
Switch
InfiniBand
Switch
Exadata
Database Server
Exadata
Storage Server
Overview of Network Requirements
Assistant to verify the cable connections when cabling Oracle Exadata Database
Machine to the existing network.
Figure 2-1 Network Diagram for Oracle Exadata Database Machine X7-2
Chapter 2
The following image shows the default network diagram for Oracle Exadata Database
Machine X4-2 and later models. Use the files from Oracle Exadata Database Machine
Deployment Assistant to verify the cable connections when cabling Oracle Exadata
Database Machine to the existing network.
2-4
Page 93
IB0 IB1IB0 IB1
Oracle
Database Server
Management
Client Access
Private InfiniBand
Additional network 1 (optional)
NET2 NET1
NET0
NET0
ILOM
ILOMNET3
PCI1 /
PORTA
Exadata
Storage Servers
InfiniBand
Switch
InfiniBand
Switch
Ethernet
Switch
BONDETH0
PDU APDU B
PCI1 /
PORTB
Chapter 2
Overview of Network Requirements
Figure 2-2 Network Diagram for Oracle Exadata Database Machine X4-2 and
Later Models
The following image shows the default network diagram for Oracle Exadata Database
Machine X3-2 and Oracle Exadata Database Machine X2-2. Use the files from Oracle
Exadata Database Machine Deployment Assistant to verify the cable connections
when cabling Oracle Exadata Database Machine to the existing network.
2-5
Page 94
BONDIB0
Oracle
Database Server
Management
Client Access
Private InfiniBand
Additional network 1 (optional)
NET2 NET1
NET0
NET0
ILOM
ILOMNET3
PCI1 /
PORTA
BONDIB0
Exadata
Storage Servers
InfiniBand
Switch
InfiniBand
Switch
Ethernet
Switch
KVM
(X2-2)
BONDETH0
PDU APDU B
PCI1 /
PORTB
Chapter 2
Overview of Network Requirements
Figure 2-3 Network Diagram for Oracle Exadata Database Machine X3-2 and
Oracle Exadata Database Machine X2-2
Notes:
•Oracle Exadata Database Machine X3-8 Full Rack, and Oracle Exadata
Database Machine X2-8 Full Rack have BONDIB0, BONDIB1, and so on
for the InfiniBand private network.
•The KVM switch is only available in Oracle Exadata Database Machine
X2-2 racks.
•Additional configuration, such as defining multiple virtual local area
networks (VLANs) or enabling routing, may be required for the switch to
operate properly in your environment, and is not included in the installation
service. If additional configuration is needed, then the network
Related Topics:
administrator performs the necessary configuration during Oracle Exadata
Database Machine installation.
The Small Form-Factor Pluggable (SFP) modules for the 10 GbE PCIe 2.0
network cards are purchased separately.
2.2.7 Oracle Exadata Database Machine X3-8 Full Rack and Oracle
Exadata Database Machine X2-8 Full Rack Database Server
Each Oracle Exadata Database Machine X3-8 Full Rack and Oracle Exadata
Database Machine X2-8 Full Rack database server consists of the following network
components and interfaces:
•2 Network Express Modules (NEMs) providing the total of the following:
Using Network VLAN Tagging with Oracle Exadata Database Machine
•1 Ethernet port for Sun Integrated Lights Out Manager (ILOM) remote
management
Note:
The SFP+ modules for the NEMs are purchased separately.
2.3 Using Network VLAN Tagging with Oracle Exadata
Database Machine
Compute nodes and storage nodes can use VLANs for the management network,
ILOM, client network, and the backup access network.
By default, the network switch is minimally configured, without VLAN tagging. If VLAN
tagging is to be used, then it must be enabled by the customer after the initial
deployment. This applies to both physical and Oracle VM deployments.
Chapter 2
Client and backup VLAN networks must be bonded. The admin network is never
bonded.
Notes:
•VLANs do not exist in InfiniBand. For equivalent functionality, use
InfiniBand partitioning as described in Oracle Exadata Database MachineMaintenance Guide.
•Network VLAN tagging is supported for Oracle Real Application Clusters
on the public network.
•If the backup network is on a tagged VLAN network, the client network
must also be on a separate tagged VLAN network.
•The backup and client networks can share the same network cables.
•Oracle Exadata Deployment Assistant (OEDA) supports VLAN tagging for
both physical and virtual deployments.
•Virtual deployments do not support IPv6 VLANs.
•If your system will use more than 10 VIP addresses in the Oracle RAC
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.
The following table shows IPv4/IPv6 support on the admin, client, and backup
networks for the different Exadata systems and Oracle Database versions.
2-10
Page 99
Chapter 2
Network Channel Bonding Support
Version of Oracle DatabaseVLAN Tagging on Admin
Network
11.2.0.4Only supported with IPv4
addresses on X3-2 and above
for two-socket servers, and
X4-8 and above for eightsocket servers.
12.1.0.2Only supported with IPv4
addresses on X3-2 and above
for two-socket servers, and
X4-8 and above for eightsocket servers.
•My Oracle Support note 1423676.1, "Enabling 802.1Q VLAN Tagging in Exadata
Database Machine over client networks"
•My Oracle Support note 2018550.1, "Implementing Tagged VLAN Interfaces in
Oracle VM Environments on Exadata"
2.4 Network Channel Bonding Support
Client and Backup
Networks
Supported with IPv4 and IPv6
on all hardware models.
Supported with IPv4 on all
hardware models.
Supported with IPv6 on all
hardware models with fix for
22289350.
The network port on a database server used for the client access network can be
bonded with another network on the database server to provide higher bandwidth or
availability for client connections to the database. In a bonded network configuration,
Oracle RAC SCAN and VIP addresses are defined on the BONDETH0 interface on
database servers.
2.4.1 Bonded Network Configurations
A bonded network configuration is used when there is a need to aggregate multiple
network interfaces together for client connections to the database.
The bonded network configuration is the default configuration.
The following sections describe the bonded network configuration for Oracle Exadata
Database Machine:
•Bonded Network Configuration for Oracle Exadata Database Machine Two-Socket
Systems (page 2-12)
•Bonded Network Configuration for Oracle Exadata Database Machine X7-8
(page 2-13)
•Bonded Network Configuration for Oracle Exadata Database Machine X4-8, X5-8,
and X6-8 (page 2-14)
•Bonded Network Configuration for Oracle Exadata Database Machine X3-8 Full
Rack and Oracle Exadata Database Machine X2-8 Full Rack (page 2-15)
2-11
Page 100
Chapter 2
Network Channel Bonding Support
2.4.1.1 Bonded Network Configuration for Oracle Exadata Database Machine
Two-Socket Systems
When using a bonded network configuration for database client access on Oracle
Exadata Database Machine Two-Socket Systems, the database servers are
configured as follows:
•Port NET0: Provides access to the operating system using the management
network through the ETH0 interface.
•Port NET1: Provides access to the database using the client access network, and
is bonded with NET2 port to create the BONDETH0 interface.
•Port NET2: Provides access to the database using the client access network, and
is bonded with NET1 port to create the BONDETH0 interface.
•Port NET MGT: Provides access to ILOM using the management network.
When channel bonding is configured for the client access network during initial
configuration, the Linux bonding module is configured for active-backup mode (
If a different bonding policy is preferred, then you may reconfigure the bonding module
after initial configuration. For configuration details, refer to the Linux Ethernet Bonding
Driver HOWTO in the /usr/share/doc/kernel-doc-2.6.39/Documentation/networking/bonding.txt directory on any Oracle Exadata Database Machine
database server.
mode=1
).
The following table shows the port connections for Oracle Exadata Database Machine
Two-Socket Systems database servers when using channel bonding. The client
access network and the backup network must use different ports, in that one network
must use the embedded GbE ports and the other network must use the PCIe ports.