To configure CF over IP, you should do the following:
Designate which subnetworks you want to use for CF over IP. Up to four subnetworks can be used.
Make sure that each node that is to be in the cluster has IP interfaces properly configured for each subnetwork. Make sure the IP broadcast and netmasks are correct and consistent on all nodes for the subnetworks.
Make sure that all of these IP interfaces are up and running.
Run the CF Wizard in Cluster Admin.
The CF Wizard has a window which allows CF over IP to be configured. The Wizard will probe all the nodes that will be in the cluster, find out what IP interfaces are available on each, and then offer them as choices in the CF over IP window. It will also try to group the choices for each node by subnetworks. See "1.1 CF, CIP, and CIM configuration" for details.
CF uses special IP devices to keep track of CF over IP configuration. There are four of these devices named as follows:
/dev/ip0 /dev/ip1 /dev/ip2 /dev/ip3
These devices do not actually correspond to any device files under /dev in the Solaris. Instead, they are just place holders for CF over IP configuration information within the CF product. Any of these devices can have an IP address and broadcast address assigned by the cfconfig(1M) command (or by Cluster Admin which invokes the cfconfig(1M) command in the Wizard).
If you run cfconfig(1M) by hand, you may specify any of these devices to indicate you want to run CF over IP. The IP device should be followed by an IP address and broadcast address of an interface on the local node. The addresses must be in internet dotted-decimal notation. For example, to configure CF on fuji2 in "Figure 8.3 CF with IP interconnects," the cfconfig(1M) command would be as follows:
fuji2 # cfconfig -S A clustername /dev/ip0
\172.25.200.4 172.25.200.255 /dev/ip1 172.25.219.83
It really does not matter which IP device you use. The above command could equally have used /dev/ip2 and /dev/ip3.
Note
The cfconfig(1M) command does not do any checks to make sure that the IP addresses are valid.
The IP devices chosen in the configuration will appear in other commands such as cftool -d and cftool -r.
IP interfaces will not show up in CF pings using cftool -p unless they are configured for use with CF and the CF driver is loaded.
Note
cftool -d shows a relative speed number for each device, which is used to establish priority for the message send. If the configured device is IP, the relative speed 100 is used. This is the desired priority for the logical IP device. If a Gigabit Ethernet hardware device is also configured, it will have priority.
