"Translated from MoS article" after the network traffic becomes larger (for example, Rman duplicat an active database), the node restarts due to brain fissure

After the network traffic becomes large (for example, Rman duplicat an active database), the node restarts due to brain fissures

From:
The node reboots due to split brain during increased network traffic like Rman duplicating an active database (document ID 98512 3.1)

Suitable for:
Oracle server-enterprise edition-version:11.1.0.7 to 11.1.0.7-release:11.1 to 11.1
Oracle server-enterprise edition-version:11.1.0.7 and later [release:11.1 and later]
Information in this document applies to any platform.

Symptoms:

Comments--------= = = ODM Issue Clarification = = = The node reboots only during the RMAN process duplicate database from AC tive database. The node, reboots is the node where RMAN process is started.  

Reason:

Comments--------= = = ODM cause determination = = = The node reboots because of the network heartbeats is not getting to th e remote nodes.  The ocssd.log shows that's the node is rebooted due to a split brain condition. This is a network related problem.

Solution:

Comments--------= = = ODM Solution/action Plan = = = Increasing Rmem_max, Rmem_default, Wmem_max, and Wmem_default Resolve D The problem

My question:
is the node reboot caused by a brain fissure generally not a private network communication problem? This case is characterized as network heartbeats, is it said that Rman duplicate database from active database is a private network?

My summary:

The technology that is available is not necessarily the best technology.

"Translated from MoS article" after the network traffic becomes larger (for example, Rman duplicat an active database), the node restarts due to brain fissure