58
OES Novell Cluster Services 1.8.2 Administration Guide for Linux
no
vd
ocx (
E
NU)
29
Ja
nua
ry
200
7
If you are connecting to an iSCSI target that already has NSS partitions and pools created on it, you
may not be able to access those NSS partitions and pools until you either reboot the Linux intitiator
server or run the
evms_activate
command at the Linux server console. This is required for each
Linux initiator server that will access the iSCSI target.
4.6.2 Adding a Node That Was Prevously in the Cluster
1
If necessary, install NetWare and Novell Cluster Services, including the latest Service Pack on
the server using the same node name and IP address.
If your SAN is not configured, install Novell Cluster Services after configuring the SAN.
2
If the Cluster object for the server is still present, use ConsoleOne
®
to delete the object.
You can do this by going to the Cluster container, selecting the node in the right frame, and
pressing Delete.
3
Run the Novell Cluster Services installation.
The node will assume its former identity.
4.6.3 Cluster Maintenance Mode
Cluster maintenance mode lets you temporarily suspend the cluster heartbeat while hardware
maintenance is being performed. This is useful if you want to reset or power down the LAN switch
without bringing down cluster servers. See
Section 4.3, “Novell Cluster Services Console
Commands,” on page 50
for more information.
If the master server in the cluster goes down while the cluster is in cluster maintenance mode, you
must enter
cluster maintenance off
on all remaining cluster servers to bring the cluster out
of maintenance mode. This is only necessary if the master server in the cluster goes down. If the
master server in the cluster is up, you can enter
cluster maintenance off
on one server in
the cluster to bring the entire cluster out of maintenance mode.
4.6.4 Shutting Down Linux Servers When Servicing Shared
Storage
If you need to power down or recycle your shared storage system, you should shut down Linux
Cluster Servers prior to doing so.
4.6.5 Preventing Cluster Node Reboot after Node Shutdown
If LAN connectivity is lost between a cluster node and the other nodes in the cluster, it is possible
that the lost node will be automatically shut down by the other cluster nodes. This is normal cluster
operating behavior, and it prevents the lost node from trying to load cluster resources because it
cannot detect the other cluster nodes.
By default, cluster nodes are configured to reboot after an automatic shutdown. On certain
occasions, you might want to prevent a downed cluster node from rebooting so you can troubleshoot
problems. To do this, edit the
opt/novell/ncs/bin/ldncs
file and find the following line:
echo -n $TOLERANCE > /proc/sys/kernel/panic
Replace $TOLERANCE with 0 to cause the server to not automatically reboot after a shutdown.
After editing the ldncs file, you must reboot the server to cause the change to take effect.