How to configure MultiNICA and IPMultiNIC in VERITAS Cluster Server for Windows NT
VERITAS Cluster Server (VCS) for NT includes two agents which allow the clustering of multiple public network adapters, thereby adding an additional level of fault tolerance to an existing cluster configuration.
By default, the NIC agent is capable of monitoring one public network adapter; should that resource fault, VCS initiates a failover. The MultiNICA agent is capable of monitoring multiple public network adapters; should one of the agents fault, VCS will failover the IP address using the IPMultiNIC agent to the next available public network adapter, rather than failing over the entire cluster group. The process is similar to the "teaming" technology included with some network adapters. VERITAS recommends using "teaming" technology if available, rather than MultiNICA, IPMultiNIC; however if "teaming" is not an option, our solution is a viable alternative.
Before configuring the MultiNICA and IPMultiNIC agents, verify the following conditions have been met:
Network interface cards (NICs) on a single system must be connected to the same network segment. NetBIOS must be enabled on one NIC only.
Ensure that the NICs do not have built-in failover support, i.e. "teaming." If they do, disable it. (If necessary, refer to the NIC documentation.)
Ensure that the value of the agent attribute UseConnectionStatus is set correctly in the configuration file. This value is set to 0 by default. It must be set to 1 if all NICs that form the MultiNICA resource maintain their connection status. If UseConnectionStatus is set to 0, ensure that at least one host is listed in the attribute PingHostList. VCS provides a utility, NICTest, that can be used to determine if a NIC maintains its connection status. For additional information on using NICTest, refer to pg. 49 of the VERITAS Cluster Server for Windows NT Installation Guide.
To configure the MultiNICA agent (Figure 1):
1. Specify those adapters in the AdapterList attribute to be monitored by the resource.
2. Specify an administrative IP address in the AdminIPAddr attribute. This address is different from the one which clients will use to connect to clustered resources.
3. Specify the subnet mask associated with the administrative IP address in the AdminSubnetMask attribute.
4. Specify the correct value for the UseConnectionStatus attribute.
5. If UseConnectionStatus is set to "0", specify those host IP addresses that are always reachable from the clustered nodes in the PingHostList attribute.
To configure the IPMultiNIC agent (Figure 2):
1. In the Address attribute, specify the public IP address through which clients will connect to the clustered resource .
2. In the MultiNICAResName attribute, specify the name of the MultiNICA resource on which the IPMultiNIC resource depends.
3. In the SubNetMask attribute, specify the subnet mask associated with the public IP address.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.