Managing Novell Cluster Services
4
no
vd
ocx (
E
NU)
29
Ja
nua
ry
200
7
49
4
Managing Novell Cluster Services
After you have installed, set up, and configured Novell
®
Cluster Services
TM
for your specific needs,
some additional information can be useful to help you effectively manage your cluster. This
information consists of instructions for migrating resources, identifying cluster and resource states,
and customizing cluster management.
4.1 Migrating Resources
You can migrate resources to different servers in your cluster without waiting for a failure to occur.
You might want to migrate resources to lessen the load on a specific server, to free up a server so it
can be brought down for scheduled maintenance, or to increase the performance of the resource or
application by putting it on a faster machine.
Migrating resources lets you balance the load and evenly distribute applications among the servers
in your cluster.
1
In the left column of the main iManager page, locate
Clusters
, then click the
Cluster Manager
link.
2
Enter the cluster name or browse and select it, then check the box next to the resource you want
to migrate and click
Migrate
.
A page appears, displaying a list of possible servers that you can migrate this resource to.
3
Select a server from the list to migrate the resource to, then click
OK
to migrate the resource to
the selected server.
If you select a resource and click Offline, the resource will be unloaded from the server. It will not
load on any other servers in the cluster and will remain unloaded until you load it again. This option
is useful for editing resources because resources can't be edited while loaded or running on a server.
4.2 Identifying Cluster and Resource States
The Cluster Manager link in iManager gives you important information about the status of servers
and resources in your cluster.
Cluster servers and resources display in different colors, depending on their operating state. When
servers and resources are display with a green ball, they are in a normal (online or running)
operating condition. When a server that has been part of the cluster has a red X in the icon, it has
failed. When a resource is red, it is waiting for administrator intervention. When a server is gray
with no break in the icon, either that server is not currently a member of the cluster or its state is
unknown. When a resource is blank or has no colored icon, it is unassigned, offline, changing state,
or in the process of loading or unloading.
The yellow diamond in the middle of the server icon designates the master server in the cluster. The
master server is initially the first server in the cluster, but another server can become the master if
the first server fails.
The Epoch number indicates the number of times the cluster state has changed. The cluster state will
change every time a server joins or leaves the cluster.