Installation - Practical Oracle Database Appliance - page 36

Table 3-4. Internet Protocol Information for node0

Node Bond name IP Address Network Mask DNS Entry

0 bond0 172.30.0.20 255.255.255.0 ejb1.m57.local

1 bond0 172.30.0.21 255.255.255.0 ejb2.m57.local

■ notice that you only need to be concerned about the bond0 interface on both nodes. the bond0 interface is
configured when using the firstnet utility.

Note

The Oracle Database Appliance also uses the normal network resources like DNS, Gateways, and Network Time
Protocol (NTP). Configured examples of these resources are shown in Table 3-5 .

Table 3-5. Additional Resources for Oracle Database Appliance

Resource Entry

DNS Servers 172.16.11.215

DNS Suffix m57.local

DNS Search Order m57.local

NTP Servers 172.30.0.1

Default Gateway 172.30.0.1

SMTP Relay 172.30.0.1

Real Application Cluster (RAC) Network
Oracle Real Application Cluster 11g Release 2 (RAC) comes preinstalled on the Oracle Database Appliance. This
version of RAC introduces the concept of a Single Client Access Name (SCAN) addressing. A SCAN address provides
the cluster with an alias for the database by providing two or more IP addresses. This alias-like approach allows
remote clients to connect without the need to change connection information related to the environment.

■ sCan requires either a corporate Dns or the oracle Global naming service to work. For the oracle
Database appliance, the approach is to use your corporate Dns. More information on sCan can be found at
www.oracle.com/technetwork/products/clustering/overview/scan-129069.pdf .

Note

SCAN addressing uses DNS in a round-robin approach. This approach ensures that network traffic is load
balanced across multiple IP addresses. This approach ensures that remote hosts can configure local naming without
needing to change connection information if changes in the environment occur. Table 3-6 provides an example of
how to configure entries in your corporate DNS server.