Oracle X6-2-HA Deployment And User's Manual page 42

Database appliance
Hide thumbs Also See for X6-2-HA:
Table of Contents

Advertisement

Network Administration Requirements
Ensure that the names and addresses that you provide for network configuration are
configured in your Domain Name System (DNS) servers. The addresses that you
provide are configured in the /etc/hosts file to provide IP name and address
resolution, even if a DNS server is not available.
You have the option to connect either to a copper, or to a fiber public network. Ensure
that your network planning is based on the correct type of public network.
Oracle recommends that you resolve addresses using a DNS server, so that you can
use Single Client Access Names (SCANs). Having a single name to access the cluster
enables the client to use the EZConnect client and the simple JDBC thin URL to
access any Oracle Database running in the cluster, independent of the active servers
in the cluster. The SCAN provides load-balancing and failover for client connections to
these databases. The SCAN works as a cluster alias for Oracle Databases in the
cluster.
If you deploy without using a DNS server, then you can add a DNS server later, and
add SCANs. If you add SCANs, then you must specify additional VIP addresses for
those SCANs.
A correctly configured Oracle Database Appliance requires at least six public
addresses on the same subnet for the nodes:
A public IP name and address for each node
A virtual IP name and address for each node
Two addresses that resolve to the SCAN for the cluster.
All names must conform to the RFC 952 standard, which permits alphanumeric
characters and hyphens ("-"), but does not allow underscores ("_").
Provide an IP address for the public interface for each node. This interface is bond0, or
Eth1 on Oracle Database Appliance Virtualized Platform, (a bond of Eth2 and Eth3),
which is used for the host IP address for the node.
Use bond1 and bond2 for management, backup, disaster recovery, or other options
where you require a network interface. Be prepared to provide a netmask and a
gateway for each interface, as both are required when you configure network
connections for Oracle Database Appliance. If you select a Custom installation, then
provide names and addresses for the bond1 optional interface.
Also determine answers to the following questions:
Do you have a Network Time Protocol (NTP) service configured for each server,
so that the local system time for each server is synchronized?
If you have NTP servers, and you want to synchronize time between Oracle
Database Appliance nodes using NTP, then be prepared to provide the addresses
for the servers. If you do not provide addresses for NTP servers, then Oracle Grid
Infrastructure software configures time synchronization between nodes using
Cluster Time Synchronization Service (CTSS).
Do you want to plug in the public IP address cables to redundant switches, so that
you can avoid a single point of failure for Oracle Database Appliance? Oracle
recommends that you use redundant switches for High Availability.
Gathering System Requirement Information
Chapter 2
2-8

Advertisement

Table of Contents
loading

Table of Contents