HP LH4r Novell NetWare Cluster Services for NetWare 5 Installation guide - Page 28

Cluster Protocol Properties

Page 28 highlights

value to 4, there must be four servers up in the cluster before any resource will load and start. Timeout 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. Cluster Protocol Properties 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 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 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. 22 Overview and Installation

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

22
Overview and Installation
value to 4, there must be four servers up in the cluster before any resource will
load and start.
Timeout
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.
Cluster Protocol Properties
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
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
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.