Converting Nodes That Contain The Edirectory Master Replica; Failing Over Cluster Resources On Mixed-Node Clusters; Managing File Systems In Mixed-Node Clusters; Using Novell Imanager In Mixed-Node Clusters - Novell OPEN ENTERPRISE SERVER 2 SP 2 - CLUSTER SERVICES 1.8.7 FOR LINUX Manual

6.1.7 Converting Nodes that Contain the eDirectory Master
Replica
When converting NetWare cluster servers to Linux, do not convert the server that has the master
eDirectory replica first. If the server with the eDirectory master replica is a cluster node, convert it at
the end of the rolling cluster conversion.

6.1.8 Failing Over Cluster Resources on Mixed-Node Clusters

Cluster resources that were created on NetWare cluster nodes and migrated or failed over to Linux
cluster nodes can be migrated or failed back to NetWare cluster nodes.
Cluster resources that were originally created on Linux cluster nodes cannot be migrated or failed
over to NetWare cluster nodes.
If you cluster migrate an NSS pool from a NetWare cluster server to a Linux cluster server, it could
take several minutes for volume trustee assignments to synchronize after the migration. Users might
have limited access to the migrated volumes until after the synchronization process is complete.

6.1.9 Managing File Systems in Mixed-Node Clusters

In a mixed cluster of NetWare and OES 1 or 2 Linux nodes, Linux POSIX file systems as cluster
resources cannot be created until the entire cluster had been successfully converted to OES 2 Linux.
Linux POSIX file systems as cluster resources cannot be migrated or failed over to NetWare cluster
nodes.
Only NSS pool cluster resources that are created on a NetWare cluster node can be failed over
between Linux and NetWare nodes of a mixed-node cluster.
NetWare-to-Linux (and vice versa) failover of NSS pool cluster resources requires that the Linux
node be configured for NSS and that the version of NSS supports the NSS media format and features
that are currently being used by the NSS pool cluster resource on NetWare.
No storage management functions should be executed while a cluster is in a mixed-cluster mode. Do
not attempt to create, delete, expand, or modify the properties for partitions, pools, or volumes for
any shared resources in the cluster.
WARNING: Attempting to reconfigure shared storage in a mixed cluster can cause data loss.
If you need to configure (or reconfigure) existing shared NSS pools and volumes in a mixed-node
cluster, you must temporarily bring down either all Linux cluster nodes or all NetWare cluster nodes
prior to making changes.

6.1.10 Using Novell iManager in Mixed-Node Clusters

Use Novell iManager 2.7.2 or later for all cluster administration in the mixed-node cluster. Using the
Clusters plug-in to iManager is required to manage the cluster after the first OES 2 Linux node is
added to the cluster.
The display of node IDs from the NetWare master node might be incomplete if you use other tools
®
like ConsoleOne and Novell Remote Manager in a mixed-node cluster. However, you can use
cat
on any cluster node to get the node IDs.
/admin/Novell/Cluster/NodeConfig.xml
62 OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide