Note
All IP configurations must be done prior to using CF over IP. The devices must be initialized with a unique IP address and a broadcast mask. IP must be configured to use these devices. If the configuration is not done, cfconfig(1M) will fail to load CF, and CF will not start.
The devices used for CF over IP must not be controlled by an RMS userApplication that could unconfigure a device due to Offline processing.
CF communications are based on the use of interconnects. A properly configured interconnect will have connections to all of the nodes in the cluster through some type of device. This is illustrated in the figure below.
Figure 9.1 Conceptual view of CF interconnects
When CF is used over Ethernet, Ethernet devices are used as the interfaces to the interconnects. The interconnects themselves are typically Ethernet hubs or switches. An example of this is shown in the figure below.
Figure 9.2 CF with Ethernet interconnects
When CF is run over IP, IP interfaces are the devices used to connect to the interconnect. The interconnect is an IP subnetwork. Multiple IP subnetworks may be used for the sake of redundancy. The figure below shows a CF over IP configuration.
Figure 9.3 CF with IP interconnects
It is also possible to use mixed configurations in which CF is run over both Ethernet devices and IP subnetworks.
When using CF over IP, you should make sure that each node in the cluster has an IP interface on each subnetwork used as an interconnect.
Note
IPv4 address is used for CF over IP.
Use CF over IP only if one of the following applies:
For a cloud environment
For an RHOSP environment
When configuring an interconnect between cluster nodes with different network segments
When a device that only supports IP exists in the route tracking of the interconnect
Note
CF is not allowed to reach nodes that are on different subnets. Caution When selecting a subnetwork to use for CF, you should use a private subnetwork that only cluster nodes can access. CF security is based on access to its interconnects. Any node that can access an interconnect can join the cluster and acquire root privileges on any cluster node.
When CF over IP is used, this means that any node on the subnetworks used by CF must be trusted. You should not use the public interface to a cluster node for CF over IP traffic unless you trust every node on your public network.
