Table 1-41 IP Address Requirements by Component
Component
Management
Network
Client Access
Network
Additional
Networks (NET2
and NET3)
InfiniBand
Private Network
Database server
Physical
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
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
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
Physical
deployment
•
2 IP address
es when
using active-
active
bonding, or 1
IP address
when not
using active-
active
bonding
Oracle VM
deployment
•
2 IP
addresses
for each user
domain
when using
active-active
bonding, or 1
IP address
for each user
domain
when not
using active-
active
bonding
Exadata Storage
Server
•
1 IP address
for
administratio
n
•
1 IP address
for ILOM
None
None
2 IP addresses
when using
active-active
bonding, or 1 IP
address when
not using active-
active bonding.
InfiniBand switch 1 IP address
None
None
None
Ethernet switch
1 IP address
None
None
None
PDU
1 IP address
None
None
None
(page 1-72) shows examples of IP addresses requirements when using
Oracle VMs.
Chapter 1
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
1-71