Node reboot or eviction: How to check if your private interconnect CRS can transmit network heartbeats (文档 ID 1445075.1)
In this Document
Frequently, in the case of node reboots, the log of the CSS daemon processes (ocssd.log) indicates that the network heartbeat from one or more remote nodes was not received (for example, the message "CRS-1610:Network communication with node xxxxxx (3) missing for 90% of timeout interval. Removal of this node from cluster in 2.656 seconds" appears in the ocssd.log), and that the node subsequently was rebooted (to avoid a split brain or because it was evicted by another node).
The script. in here performs the network connectivity check using ssh. This check complements ping or traceroute since ssh uses TCP protocol while ping uses ICMP and traceroute in Linux/Unix uses UDP (traceroute on Windows use ICMP).
The network communication involves both the actual physical connection and the OS layer such as IP, UDP, and TCP.
CRS (10g and 11.1) uses TCP to communicate, so using ssh to test the connection as well as TCP and IP layer is a better test than ping or traceroute.
Because CRS on 11.2 uses UDP to communicate, using ssh to test TCP is not the optimal test, but this test will complement the traceroute test.
The script. tests the private interconnect once every 5 seconds, so this script. will put an insignificant load on the server.
1) Create a file in a location of your choice and copy and paste the lines in the following note box:
3) If there are more than two nodes in the cluster, add more lines to issue
Make sure that this script. issues ssh to every node including the local node.
The script. will likely grow less than one MB every day, so you do not need large amount of space.
You can also regularly delete old log files.
6) Save the file and issue "chmod +x
7) Make sure that the ssh works without asking for any password over the private interconnect.
It is best to first test the ssh connection over the private interconnect from all nodes to every other node including itself (local node).
8) Issue "nohup
Run this script. from every node in the cluster.
How to interpret the output in the log file:
The following script. is an example from the three node cluster:
Database - RAC/Scalability Community
To discuss this topic further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Database - RAC/Scalability Community
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/17252115/viewspace-768227/，如需转载，请注明出处，否则将追究法律责任。