Using Virtual IP Addresses with BCC 1.2 167novdocx (en) 7 January 2010F.3.5 Host MaskTo use a virtual IP address in a business continuity cluster, we recommend using a host mask. Tounderstand why, consider the fact that each service in a clustered environment must have its ownunique IP address, or a unique virtual IP address. Furthermore, consider that each virtual IP addressbelongs to a virtual IP network whose route is being advertised by a single node within a cluster.Because Novell Cluster Services™ can migrate a service and its virtual IP address from one node toanother, the virtual IP network must migrate to the same node as the service. If multiple virtual IPaddresses belong to a given virtual IP network, one of two events must occur: All services associated with the virtual IP addresses on a given virtual IP network must failover together. The virtual IP addresses on a given virtual IP network must go unused, thereby wasting aportion of the available address space.Neither of these situations is desirable. Fortunately, the use of host masks remedies both.F.4 Configuring a Virtual Router with OSPFPerform the following procedure for each node in every peer cluster:1 Use YaST® to add a Dummy Device to the node.This creates a virtual network device named dummy0.2 In YaST, use the Software Installer to install the Quagga Routing Software Suite package.3 Edit the configuration files for the Quagga Routing Software Suite.For information, see the Quagga Routing Software Suite Documentation Web site (http://www.quagga.net/docs.php).3a In a text editor, configure /etc/quagga/zebra.conf to specify values for the followingfields: Hostname Password (optional) Physical and virtual interface Log file (optional)3b In a text editor, configure /etc/quagga/ospfd.conf to specify values for the followingfields: Hostname Password (optional) Physical and virtual interface OSPF area ID Log file (optional)3c In a text editor, configure /etc/services.
