| |
Depending on your needs and cluster setup, some additional configuration may be required for you to effectively use NetWare Cluster Services. This additional configuration consists of changing the network settings on the clients that will access the cluster. You might also need to change the values on some of the properties for the Cluster object and the Cluster Node objects.
Certain advanced settings are required for older Windows 95/98 and all Windows NT clients to transparently reconnect or access cluster enabled volumes in NetWare Cluster Services. These advanced settings are only required for Windows 95/98 clients that are earlier than version 3.10, Support Pack 2 (the client version that ships with NetWare Cluster Services). Use the following intructions to ensure workstations are properly configured.
NOTE: Autoreconnect only works for volumes that are cluster-enabled.
For older Windows* 95/98 clients:
In the Control Panel, select Network, then select Novell NetWare Client.
Click Properties.
Select the Advanced Settings tab.
Verify or change the settings to the following:
For all Windows NT* clients:
In the Control Panel, select Network, then select Services.
Select Novell Client for NT and verify or change the following settings.
On the Advanced Settings tab:
On the Protocol Preferences tab:
NetWare Cluster Services requires that NetWare clients be configured to use TCP/IP for transparent client reconnect. NetWare clients configured to use only IPX cannot map drives to the shared disk volume through NDS. IPX clients can however map drives to the shared disk volume through the server that currently has the volume mounted. When a failover occurs, the connection to the share disk volume fails and a new drive mapping must be manually created to the volume through the server where the volume has migrated.
To edit Quorum Membership and Timeout properties, in ConsoleOne, right click the Cluster object and select Properties. This will bring up the Cluster Object Property page. Select the Quorum tab.
The Quorum Membership is the number of nodes that must be running in the cluster before resources will start to load. When you first bring up servers in your cluster, NetWare Cluster Services reads the number specified in the Membership field and waits until that number of servers is up and running in the cluster before it starts loading resources. Set the Membership value to a number greater than 1 so that all resources don't automatically load on the first server that is brought up in the cluster. For example, if you set the Membership value to 4, there must be four servers up in the cluster before any resource will load and start.
Timeout specifies the amount of time to wait for the number of servers defined in the Membership field to be up and running. If the timeout period elapses before the quorum membership reaches its specified number, resources will automatically start loading on the servers that are currently up and running in the cluster. For example, if you specify a Membership value of 4 and a timeout value equal to 30 seconds, and after 30 seconds, only two servers are up and running in the cluster, resources will begin to load on the two servers that are up and running in the cluster.
You can use the Cluster Protocol property pages to view or edit the transmit frequency and tolerance settings for all nodes in the cluster, including the master node. The master node is generally the first node brought online in the cluster, but if that node fails, any of the other nodes in the cluster can become master.
To view or edit Cluster Protocol properties, in ConsoleOne, right click the Cluster object and select Properties. This will bring up the Cluster Object property page. Select the Protocol tab. This tab has two pages, Settings and Internals. The Internals page lets you view the script used to configure the cluster protocol settings, but not change it. Use the Settings page to make changes to cluster protocol properties.
Heartbeat specifies the amount of time between transmits for all nodes in the cluster except the master. For example, if you set this value to one, non-master nodes in the cluster will send a signal that they are alive to the master node every second.
Tolerance specifies the amount of time the master node gives all other nodes in the cluster to signal that they are alive. For example, setting this value to four means that if the master node does not receive an "I'm alive" signal from a node in the cluster within four seconds, that node will be removed from the cluster.
Master Watchdog specifies the amount of time between transmits for the master node in the cluster. For example, if you set this value to one, the master node in the cluster will transmit an "I'm alive" signal to all the other nodes in the cluster every second.
Slave Watchdog specifies the amount of time the master node has to signal that it is alive. For example, setting this value to five means that if the non-master nodes in the cluster do not receive an "I'm alive" signal from the master within 5 seconds, the master node will be removed from the cluster and one of the other nodes will become the master node.
This option is not currently used with NetWare Cluster Services but will be used for future versions.
The default cluster port number is 7023, and is automatically assigned when the cluster is created. The cluster port number does not need to be changed unless there is a conflict created by another resource using the same port number. If there is a port number conflict, change the Port number to any other value that doesn't cause a conflict.
To view or edit the Cluster Port property, in ConsoleOne, right click the cluster object and select Properties. This will bring up the Cluster Object property page. Select the Port tab.
You can use the Cluster Node property page to view or edit the cluster node number or IP address of the selected node or view the context for the NetWare Server object.
To view or edit Cluster Node properties, in ConsoleOne, select the Cluster object, right click the desired cluster node on the right side of the ConsoleOne display screen, and select Properties. This will bring up the Cluster Node property page. Select the Node tab.
Number+IP Address specifies the cluster node number and IP address for the selected node. If the cluster node number or IP address changes for the selected node, the new information is not automatically updated in NDS. Edit the information and click Apply to update the information in NDS.
The NCP Server field is used to view the context for the NetWare Server object. This field cannot be edited.
| |