Oracle12cRAC环境配置支持IPV6

Oracle各版本对IPV6的支持情况
Oracle 11.2中除了ORACLE RAC和Oracle Clusterware所有功能都支持IPV6, 还有也不支持ASM使用IPV6,支持IPV6和IPV4共存. 在ORACLE 12C中，Oracle支持IPV4和IPV6在同一个网络，同样也可以配置PLUBIC network(Public/vip)在IPV6和IPV4，但是确保同一集群中所有节点使用相同的IP协议。但12.1 时不支持WINDOWS和private newwork. 在12.2 版本中 ORACLE提供了完全的支持IPV6，包括WINDOWS平台，ASM, FAN， 所有平台中的ORACLE Clusterwarer的private network。

配置和修改步骤

Changing Static IPv4 Addresses To Static IPv6 Addresses Using SRVCTL
When you change from IPv4 static addresses to IPv6 static addresses, you add an IPv6 address and modify the network to briefly accept both IPv4 and IPv6 addresses, before switching to using static IPv6 addresses, only.

Note:If the IPv4 network is in mixed mode with both static and dynamic addresses, then you cannot perform this procedure. You must first transition all addresses to static.
To change a static IPv4 address to a static IPv6 address:

1.Add an IPv6 subnet using the following command as root once for the entire network:

# srvctl modify network –subnet ipv6_subnet/prefix_length

In the preceding syntax ipv6_subnet/prefix_length is the subnet of the IPv6 address to which you are changing along with the prefix length, such as 3001::/64.

2.Add an IPv6 VIP using the following command as root once on each node:

# srvctl modify vip -node node_name -netnum network_number -address vip_name/netmask

In the preceding syntax:

node_name is the name of the node

network_number is the number of the network

vip_name/netmask is the name of a local VIP that resolves to both IPv4 and IPv6 addresses

The IPv4 netmask or IPv6 prefix length that follows the VIP name must satisfy two requirements:

If you specify a netmask in IPv4 format (such as 255.255.255.0), then the VIP name resolves to IPv4 addresses (but can also resolve to IPv6 addresses). Similarly, if you specify an IPv6 prefix length (such as 64), then the VIP name resolves to IPv6 addresses (but can also resolve to IPv4 addresses).

If you specify an IPv4 netmask, then it should match the netmask of the registered IPv4 network subnet number, regardless of whether the -iptype of the network is IPv6. Similarly, if you specify an IPv6 prefix length, then it must match the prefix length of the registered IPv6 network subnet number, regardless of whether the -iptype of the network is IPv4.

3.Add the IPv6 network resource to OCR using the following command:
$ oifcfg setif -global if_name/subnet:public

4.Update the SCAN in DNS to have as many IPv6 addresses as there are IPv4 addresses. Add IPv6 addresses to the SCAN VIPs using the following command as root once for the entire network:

# srvctl modify scan -scanname scan_name

scan_name is the name of a SCAN that resolves to both IPv4 and IPv6 addresses.

5.Convert the network IP type from IPv4 to both IPv4 and IPv6 using the following command as root once for the entire network:

srvctl modify network -netnum network_number -iptype both

This command brings up the IPv6 static addresses.

6.Change all clients served by the cluster from IPv4 networks and addresses to IPv6 networks and addresses.

7.Transition the network from using both protocols to using only IPv6 using the following command:
# srvctl modify network -iptype ipv6

8.Modify the VIP using a VIP name that resolves to IPv6 by running the following command as root:
# srvctl modify vip -node node_name -address vip_name -netnum network_number
Do this once for each node.

9.Modify the SCAN using a SCAN name that resolves to IPv6 by running the following command:
# srvctl modify scan -scanname scan_name
Do this once for the entire cluster.

Related Topics

Oracle Real Application Clusters Administration and Deployment Guide
OIFCFG Command Format

oifcfg setif -global eth0/fc00:0:130f:0:192:168:123:231:::public
Oracle12.2RAC环境IPV6配置
IPV6地址规划
cat  /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

192.168.123.231   ora12racZ1
192.168.123.232   ora12racZ1-vip
172.168.15.2      ora12racZ1-priv
192.168.123.233   ora12racZ2
192.168.123.234   ora12racZ2-vip
172.168.15.3      ora12racZ2-priv
192.168.123.235   ora12racZ-scan

fc00:0:130f:0:192:168:123:231 ora12racZ1
fc00:0:130f:0:192:168:123:232 ora12racZ1-vip
fc00:0:130f:0:172:168:15:2 ora12racZ1-priv
fc00:0:130f:0:192:168:123:233 ora12racZ2
fc00:0:130f:0:192:168:123:234 ora12racZ2-vip
fc00:0:130f:0:172:168:15:3 ora12racZ2-priv
fc00:0:130f:0:192:168:123:235 ora12racZ-scan


#oifcfg setif -global eth0/fc00:0:130f:0:192:168:123:231/64:public 
################12c Database : IPV6 and IPV4 support for Clusterware#################
eth0和eth1配置公网和私网的ipv6地址
fc00:0:130f:0:192:168:123:231
fc00:0:130f:0:172:168:15:2

fc00:0:130f:0:192:168:123:234
fc00:0:130f:0:172:168:15:3
# set the ipv6 for eth0 as public
oifcfg setif -global eth0/fc00:0:130f:0:192:168:123:232:public
oifcfg setif -global eth0/fc00:0:130f:0:192:168:123:234:public
# Change the cluster resource 'network' to use the ipv6 eth0 we just created
srvctl modify network -subnet fc00:0:130f:0::/64/eth0
# Modify the scan to use these format
srvctl modify scan -scanname  ora12racZ-scan
# Modify the node vip's,
#note:- option skip must be used since the vip is reachable as we enabled  network above, and vip must not be reachable before cluster starts, hence use skip
srvctl modify vip -node ora12racZ1 -address ora12racZ1-vip/64 -netnum 1 -skip
srvctl modify vip -node ora12racZ2 -address ora12racZ2-vip/64 -netnum 1 -skip
#Firstly, enable the iptype for the network to both for the cluster to use IPV6 and IPV4
srvctl modify network -iptype both
srvctl modify network -netnum network_number -iptype both
复制

参考文档

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/cwadd/oracle-clusterware-administration.html#GUID-4406AD31-76D8-4FBA-AA5E-1D60643FB720