Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / Oracle Новый топик    Ответить
 oracle 11.2.0.3 RAC interconnect  [new]
bombardun
Member

Откуда:
Сообщений: 85
Вопрос в следующем.
Насколько я помню, для приватных сетевых интерфейсов Oracle рекомендует использовать изолированную подсеть, и желательно на обособленном оборудовании. Но коллега заронил зерно сомнений, заявив, что есть официальная рекомендация от oracle, использовать именно конкретный диапазон адресов для интерконнекта, типа 192.168.0.1

Никто не может прояснить вопрос?
9 июн 14, 10:50    [16140794]     Ответить | Цитировать Сообщить модератору
 Re: oracle 11.2.0.3 RAC interconnect  [new]
Тролин
Guest
bombardun,

How to use VLANs for Oracle RAC and the Oracle Clusterware Interconnect?

It is Oracle's standing requirement to separate the various types of communication in an Oracle RAC cluster. This requirement addresses the following separation of communication:

Each node in an Oracle RAC cluster must have at least one public network.
Each node in an Oracle RAC cluster must have at least one private network, also referred to as "cluster interconnect".
Each node in an Oracle RAC cluster must have at least an additional network interface, if the shared storage is accessed using a network based connection.
Cluster interconnect network separation can be satisfied either by using standalone, dedicated switches, which provide the highest degree of network isolation, or Virtual Local Area Networks defined on the Ethernet switch, which provide broadcast domain isolation between IP networks. VLANs are fully supported for Oracle Clusterware interconnect deployments. Partitioning the Ethernet switch with VLANs allows for:



Sharing the same switch for private and public communication.
Sharing the same switch for the private communication of more than one cluster.
Sharing the same switch for private communication and shared storage access.

The following best practices should be followed:

The Cluster Interconnect VLAN must be on a non-routed IP subnet.


All Cluster Interconnect networks must be configured with non-routed IPs. The server-server communication should be single hop through the switch via the interconnect VLAN. There is no VLAN-VLAN communication.

Oracle recommends maintaining a 1:1 mapping of subnet to VLAN.


The most common VLAN deployments maintain a 1:1 mapping of subnet to VLAN. It is strongly recommended to avoid multi-subnet mapping to a single VLAN. Best practice recommends a single access VLAN port configured on the switch for the cluster interconnect VLAN. The server side network interface should have access to a single VLAN.

The shared switch should be configured to mitigate the cost of Spanning Tree


The switch vendor’s best practices should be followed to either disable or limit the cost of Spanning Tree convergence for the cluster interconnect VLAN.

Sharing the same switch for private communication and shared storage access


This configuration is supported, if the underlying network infrastructure supports Data Center Bridging (DCB), zero packet loss and can satisfy the latency and throughput defined for the application. This may require imposing a Quality of Service (QoS) on the shared switch to prioritize network based communication to the storage. Fiber Channel over Ethernet (FCoE) converged networks are supported for certified configurations.
9 июн 14, 12:31    [16141585]     Ответить | Цитировать Сообщить модератору
 Re: oracle 11.2.0.3 RAC interconnect  [new]
Тролин
Guest
По сути вы оба правы.
9 июн 14, 12:35    [16141613]     Ответить | Цитировать Сообщить модератору
 Re: oracle 11.2.0.3 RAC interconnect  [new]
Тролин
Guest
The Cluster Interconnect VLAN must be on a non-routed IP subnet.
172
10
и
192 подсеть.
RFC 1918

What are the IP requirements for the private interconnect?

The install guide will tell you the following requirements private IP address must satisfy the following requirements:
1. Must be separate from the public network
2. Must be accessible on the same network interface on each node
3. Must have a unique address on each node
4. Must be specified in the /etc/hosts file on each node
The Best Pratices recommendation is to use the TCP/IP standard for non-routeable networks. Reserved address ranges for private (non-routed) use (see TCP/IP RFC 1918):
* 10.0.0.0 -> 10.255.255.255
* 172.16.0.0 -> 172.31.255.255
* 192.168.0.0 -> 192.168.255.255
Cluvfy will give you an error if you do not have your private interconnect in the ranges above.
You should not ignore this error. If you are using an IP address in the range used for the public network for the private network interfaces, you are pretty much messing up the IP addressing, and possibly the routing tables, for the rest of the corporation. IP addresses are a sparse commodity, use them wisely. If you use them on a non-routable network, there is nothing to prevent someone else to go and use them in the normal corporate network, and then when those RAC nodes find out that there is another path to that address range (through RIP), they just might start sending traffic to those other IP addresses instead of the interconnect. This is just a bad idea.
9 июн 14, 12:38    [16141641]     Ответить | Цитировать Сообщить модератору
 Re: oracle 11.2.0.3 RAC interconnect  [new]
Vadim Lejnin
Member

Откуда:
Сообщений: 7134
C Oracle Interface Configuration (OIFCFG) Command Reference

p.s. Oracle Database Appliance
не умеет менять адрес интерконнекта
но это внутренний интерфейс, который нигде больше не виден
9 июн 14, 12:42    [16141669]     Ответить | Цитировать Сообщить модератору
Все форумы / Oracle Ответить