Event Logging - Intergraph WebScale User Manual

WebScale™
Inconsistency
Duplicate host
priorities
Different number
of port rules
Inconsistent port
rule
If inconsistencies are unexpectedly discovered when a host attempts to join the cluster,
the host should be taken out of the cluster with the webscale stop command. The
problem should be located and corrected using the WebScale Setup dialog on each host
prior to returning the host(s) to the cluster using the webscale start command.
You can add port rules or update their parameters by taking each host out of the cluster
in turn, updating its parameters, and then returning it to the cluster. During this process,
other cluster hosts will detect inconsistencies in the rules and will handle them as
described above. This will permit the cluster to maintain service for client requests
while the changes are made. For example, if a rule is added, it will not take effect until
all hosts have been updated and have rejoined the cluster. If a rule is modified, the rule
will not be used until it is made consistent on all hosts.

Event Logging

WebScale uses Windows NT event logging mechanism to record information about
event of major importance. You can view the event log by running Windows NT Event
Viewer utility program found in the Administrative Tools folder.
WebScale classifies logged events into three categories:
Information These events record normal state transitions, such as driver
events: startup, the completion of convergence, and the completion of
cluster control actions. These events are recorded for
informational purposes only.
Warning These events warn about abnormal occurrences that do not
events: impede cluster operations. These events can indicate a
configuration problem, such as an invalid dedicated IP address
or other parameter. They also can indicate a temporary
condition, such as the transient exhaustion of driver resources.
Cluster operations are not disrupted when warning events
WebScale's recovery method
The joining host handles no traffic until convergence
completes. The cluster will not converge to a consistent
state until duplicate hosts are no longer detected.
The joining host handles no traffic until convergence
completes. The cluster will not converge to a consistent
state until all hosts have the same number of rules.
The joining host handles no traffic until convergence
completes. The cluster will not converge to a consistent
state until the rule is consistent across all hosts in the
cluster.
60
User's Guide