Handling of node downtime caused by iptables enabled by 11gR2 RAC

When iptables is enabled in 11gR2 RAC, node downtime is usually handled. When installing a database, the vast majority of users require selinux and iptables to be disabled before installation. However, in the carrier's system, many security factors need to enable iptables on the Database Host on the current network. When enabling iptables, you must note that, for example, the hosts configuration in RAC is as follows: 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-priv192.168.142.32 db-scan so naturally to the above IP address must be put through. However, in actual operation, the above IP address has been released, and a database-1 instance is down. Check the database's alert Log: Tue Aug 20 00:29:40 2013IPC Send timeout detected. sender: ospid 8284 [oracle @ subsdb2 (LMD0)] Explorer: inst 1 binc 1740332689 ospid 15851IPC Send timeout to 1.0 inc 10 for msg type 65521 from opid 12Tue Aug 20 00:29:48 2013IPC Send timeout detected. sender: ospid 8276 [oracle @ subsdb2 (PING)] Receiver: inst 2 binc 1801834534 ospid 8276Tue Aug 20 00:29:52 2013 Detected an inconsistent ins Tance 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.trcUse ADRCI or Support Workbench to package the incident. see Note 411.1 at My Oracle Su Pport 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 29740Tue Aug 20 00:29:54 2013ORA-1092: opitsk aborting processTue Aug 20 00:29:54 2013 License high water mark = 29Tue Aug 20 00:29:57 2013 System state dum P 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.trcInstance terminated by LMON, pid = 8282 USER (ospid: 31106 ): terminating the instanceInstance terminated by USER, pid = 31106 from the above, we can initially conclude that there is a problem with internal communication, but how to solve it? However, the alert log of the database and the alert log of the ASM instance contain the following information: 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 from this information, in the internal communication of RAC, the IP address net = 169.254.0.0/16 is also used, and the description is also provided from MOS Doc ID 1383737.1, finally, I used ifconfig to find out that the IP address of the 169 network segment used in the two nodes of RAC is 169.254.122.59169.254.148.209. After these two IP addresses are enabled in iptables, the cluster will be normal.