Dns Configuration For Oracle Exadata Database Machine - Oracle EXADATA X6-2 Installation And Configuration Manual

Table 1-36
Requirements for Oracle Exadata Database Machine X2-2
Scenario
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
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.
Network Connection and IP Address Requirements for Oracle Exadata Database Machine
(Cont.) Examples of Network Configurations and Connection
Note:
Grid Naming Service (GNS) is not configured on Oracle Exadata Database
Machine during initial configuration.
Network Requirements
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
1-50