E.3 August 2012 (OES 11 SP1)

Procedures throughout the guide were updated to use the newly reorganized Clusters plug-in for iManager. In addition, updates were made to the following sections. The changes are explained below.

E.3.1 Console Commands for Novell Cluster Services

Location	Change
NCPCON Mount Command for NCP and NSS Volumes	This section is new.

E.3.2 Comparing Novell Cluster Services for Linux and NetWare

Updated for new or changed OES 11 SP1 features.

E.3.3 Configuring and Managing Cluster Resources

Location	Change
Section 10.1.2, Using Parameter Values with Spaces in a Cluster Script	This section is new.
Section 10.2, Setting Up a Personalized List of Resources to Manage	This section is new.
Section 10.14, Changing the IP Address of a Cluster Resource	This procedures in this section are new.

E.3.4 Configuring and Managing Cluster Resources for Shared Linux LVM Volume Groups

Location	Change
NCP File Access with Novell NCP Server	For information about using antivirus software with NCP volumes, see Security in the OES 11 SP3: Planning and Implementation Guide.
Section 13.3, Configuring an LVM Volume Group Cluster Resource with NSS Management Tools	This section was expanded to include nlvm commands and NCP enabling the clustered LVM logical volume.
Section 13.6, Enabling NCP File Access for a Clustered LVM Volume	This section is new.
Section 13.7, Modifying the LVM Resource Scripts for Other Services	This section is new.

E.3.5 Configuring and Managing Cluster Resources for Shared NSS Pools and Volumes

Location	Change
Volume	For information about using antivirus software with NSS volumes, see Antivirus Support for NSS in the OES 11 SP3: NSS File System Administration Guide for Linux and Security in the OES 11 SP3: Planning and Implementation Guide.
NCP Server for Linux	NCP Server does not support cross-protocol locks across a cluster migration or failover of the resource. Hyphens are used in the default NCP virtual server name. Underscores can be used in custom names.
Novell CIFS for Linux	The default name suggested for the CIFS virtual server name is based on the NCP virtual server name.
Initializing and Sharing a Device with NLVM	This section is new.
Cluster-Enabling an Existing NSS Pool and Its Volumes	The default name suggested for the CIFS virtual server name is based on the NCP virtual server name.
Specifying a Custom Mount Point for an NSS Volume	For information about using a custom mount point path, see Section 12.14, Renaming the Mount Point Path for a Shared NSS Volume (Using a Custom Mount Point for a Shared NSS Volume).
Configuring a Monitor Script for the Shared NSS Pool	If AFP is used as an advertising protocol, the exit_on_error afpstat command is added to the monitor script.
Adding NFS Export for a Clustered Pool Resource	This section is new.
Renaming a Clustered NSS Pool	Because renaming involves changing information for the Pool object in eDirectory, you must ensure that the shared pool is active on a cluster node that has its NCP server object in the same context as the Pool object of the pool you are going to rename. Added details for the renaming procedure.
Changing the Name Space for a Clustered NSS Volume	This section is new
Expanding the Size of a Clustered Pool	Corrected the procedures for an online pool expansion.

E.3.6 Configuring Cluster Policies, Protocols, and Priorities

Location	Change
Section 8.5, Configuring Cluster Protocols	Modify the Master Watchdog and Slave Watchdog parameter settings only when supervised by Novell Technical Support.
Section 8.6, Configuring Cluster Event Email Notification	Because both Postfix and the GWIA default to using port 25, you must configure the GWIA to bind exclusively to its resource’s secondary IP address in order to avoid a port conflict between Postfix and the GWIA.
Section 8.12, Viewing or Modifying the Cluster Master IP Address or Port	A cluster restart is required before iManager can continue to manage the cluster.

E.3.7 Configuring Novell Cluster Services in a Virtualization Environment

Location	Change
Section 15.0, Configuring Novell Cluster Services in a Virtualization Environment	To get started with KVM virtualization, see the Virtualization with KVM documentation.

E.3.8 Electing a Master Node

The section Section C.0, Electing a Master Node is new.

E.3.9 Files for Novell Cluster Services

Location	Change
Table B-1, Location and Purpose of Novell Cluster Services Files	References to the hang-check timer were removed. It was obsoleted in OES 2 SP2 Patches. The NCS tolerance is now used to determine whether NCS has been starved of CPU. You can use directive kernel.panic in file /etc/sysctl.conf file to control the behaviors after NCS has determined to kill the node. See Section 8.1.8, Cluster Node Reboot Behavior.
/opt/novell/ncs/bin/NCS_STONITH_SCRIPT file	You create and code the /opt/novell/ncs/bin/NCS_STONITH_SCRIPT script file to enable and control the STONITH feature.

Location

Change

Table B-1, Location and Purpose of Novell Cluster Services Files

References to the hang-check timer were removed. It was obsoleted in OES 2 SP2 Patches.

The NCS tolerance is now used to determine whether NCS has been starved of CPU. You can use directive kernel.panic in file /etc/sysctl.conf file to control the behaviors after NCS has determined to kill the node. See Section 8.1.8, Cluster Node Reboot Behavior.

/opt/novell/ncs/bin/NCS_STONITH_SCRIPT file

You create and code the /opt/novell/ncs/bin/NCS_STONITH_SCRIPT script file to enable and control the STONITH feature.

E.3.10 Installing and Configuring Novell Cluster Services on OES 11

Location	Change
Section 5.7, Installing or Updating the Clusters Plug-in for iManager	Expanded to explain the updates for OES 11 SP1.

E.3.11 Managing Clusters

Location	Change
Section 9.4, Monitoring Cluster and Resource States	Added information about the Resource not found condition for resources on the My Resources page of the Clusters plug-in.
Section 9.5, Responding to a Start, Failover, or Failback Alert	This section is new.
Table 9-2, Cluster Resource States	Updated the Alert entry to identify alert types: Start alert, Failover alert, and Failback alert.
Section 8.10, Configuring STONITH	This section is new.

E.3.12 Planning for Novell Cluster Services

Location	Change
Section 4.3, Volume ID Requirements	Volume IDs for BCC-enabled clustered volumes must be unique across all nodes in every peer cluster.
NCP Server for Linux	NCP Server does not support cross-protocol locks across a cluster migration or failover of the resource.
Section 4.10.3, Modifying the Polling Interval, No Path Retry, and Failback Settings in the multipath.conf File	Added information about the polling_interval.
Section 4.6.8, SFCB and CIMOM	The user name that you use to log in to Novell iManager when you manage a cluster and the BCC cluster must be an eDirectory user name that has been LUM-enabled.

E.3.13 Security Considerations

Location	Change
Ports	Email Notification uses Postfix, port 25.
Log Files	NCS configuration writes log messages to /var/log/YaST2/y2log.
Configuration Files	This section is new.

E.3.14 Troubleshooting Novell Cluster Services

Location	Change
iManager: Error 500 Occurs while Connecting to a Cluster	This section is new.

E.3.15 Upgrading and Managing Cluster Resources for Linux POSIX Volumes with CSM Containers

Location	Change
Configuring and Adding OES 11x Nodes to the OES 2 SP3 Cluster	The path for the NLVM configuration file is /etc/opt/novell/nss/nlvm.conf.

E.3.16 Upgrading Clusters from OES 2 SP3 to OES 11 SP1

Location	Change
Supported Upgrade Paths from OES 2 SP3 to OES 11x	Upgrade is supported from OES 2 SP3 on SLES 10 SP3 or SLES 11 SP4 to OES 11 SP1 on SLES 11 SP2.
Section 7.3, Requirements and Guidelines for Upgrading Clusters from OES 2 SP3	Upgrade OES 2 SP3 cluster nodes with the higher IP addresses first.
Multiple locations	Procedures have been updated for OES 11 SP1.

E.3.17 Upgrading OES 11 Clusters

This section is new.

E.3.18 What’s New or Changed in Novell Cluster Services

Location	Change
What’s New (OES 11 SP1)	This section is new.