Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

5.2. Network Topology

Clusterware requires a heartbeat network, and an inter-node network for moving database block between nodes (GCS). These are usually the same network, and often the same network as the Red Hat Cluster Suite network.
It is critical that Red Hat Cluster Suite operates heartbeat services over the private, bonded network and not the public network. If the private network fails for a node, then this node must be removed from the cluster. If the public network fails, the application tier cannot access the database on the node, but the CRS VIP service is responsible for the public network. 
<clusternode name="rac7-priv" nodeid="1" votes="1">
         <multicast addr="225.0.0.12" interface="bond0"/>
         <fence>
                 <method name="1">
                         <device name="jLO7"/>
                 </method>
         </fence>
 </clusternode>
 <clusternode name="rac8-priv" nodeid="2" votes="1">
         <multicast addr="225.0.0.12" interface="bond0"/>
         <fence>
                 <method name="1">
                         <device name="jLO8"/>
                 </method>
         </fence>
 </clusternode>
Copy to Clipboard Toggle word wrap
While most customers do not bond this interface, it is supported by Oracle.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat