Oracle11g:R2 RAC啓用iptables致使節點宕機問題

一般，在安裝數據庫時，絕大多數都是要求把selinux及iptables關閉，而後再進行安裝的。可是在運營商的系統中，不少安全的因素，須要將現網的數據庫主機上的iptables開啓的。
在開啓iptables時就要注意了，好比一RAC中的hosts配置以下：
192.168.142.115 subsdb1
192.168.142.117 subsdb1-vip
10.0.0.115 subsdb1-priv
192.168.142.116 subsdb2
192.168.142.118 subsdb2-vip
10.0.0.116 subsdb2-priv
192.168.142.32 db-scan

那麼理所固然的要將上面的IP都要放通的。可是在實際操做中，已經放通了上面的IP，結果數據庫一的個實例宕掉了。

看看數據庫的alert日誌：

Tue Aug 20 00:29:40 2013
IPC Send timeout detected. Sender: ospid 8284 [oracle@subsdb2 (LMD0)]
Receiver: inst 1 binc 1740332689 ospid 15851
IPC Send timeout to 1.0 inc 10 for msg type 65521 from opid 12
Tue Aug 20 00:29:48 2013
IPC Send timeout detected. Sender: ospid 8276 [oracle@subsdb2 (PING)]
Receiver: inst 2 binc 1801834534 ospid 8276
Tue Aug 20 00:29:52 2013
Detected an inconsistent instance membership by instance 2
Errors in file /oracle/app/oracle/diag/rdbms/gdordb/GDORDB2/trace/GDORDB2_lmon_8282.trc (incident=784092):
ORA-29740: evicted by instance number 2, group incarnation 12
Incident details in: /oracle/app/oracle/diag/rdbms/gdordb/GDORDB2/incident/incdir_784092/GDORDB2_lmon_8282_i784092.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /oracle/app/oracle/diag/rdbms/gdordb/GDORDB2/trace/GDORDB2_lmon_8282.trc:
ORA-29740: evicted by instance number 2, group incarnation 12
LMON (ospid: 8282): terminating the instance due to error 29740
Tue Aug 20 00:29:54 2013
ORA-1092 : opitsk aborting process
Tue Aug 20 00:29:54 2013
License high water mark = 29
Tue Aug 20 00:29:57 2013
System state dump requested by (instance=2, osid=8282 (LMON)), summary=[abnormal instance termination].
System State dumped to trace file /oracle/app/oracle/diag/rdbms/gdordb/GDORDB2/trace/GDORDB2_diag_8272.trc
Instance terminated by LMON, pid = 8282
USER (ospid: 31106): terminating the instance
Instance terminated by USER, pid = 31106

單純從上面來看，初步能夠判定是內部通訊有問題，可是如何解決？
但再從數據庫的alert和ASM實例的alert日誌中都有這樣的信息：
Private Interface 'bond2:1' configured from GPnP for use as a private interconnect.
[name='bond2:1', type=1, ip=169.254.148.209, mac=00-25-b5-00-00-67, net=169.254.0.0/16, mask=255.255.0.0, use=haip:cluster_interconnect/62]
Public Interface 'bond0' configured from GPnP for use as a public interface.
[name='bond0', type=1, ip=192.168.142.116, mac=00-25-b5-00-01-cb, net=192.168.142.0/24, mask=255.255.255.0, use=public/1]
Picked latch-free SCN scheme 3

從這個信息來看，RAC的內部通訊還要用到net=169.254.0.0/16的IP，再從MOS Doc ID 1383737.1也有這樣的說明，最後用ifconfig查到了RAC的兩個節點中使用到的169網段的IP爲：
169.254.122.59
169.254.148.209
在iptables中放通了這兩個IP後，集羣正常。