Novell Open Enterprise Server Conversion Guide
Novell®
www.novell.com
Novell Cluster ServicesTM Conversion Guide
Open Enterprise Server
2 SP3
December 22, 2010
AUTHORIZED DOCUMENTATION
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respec t to any sof tware, a nd sp ecific ally disc laims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export contr ols and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Copyright © 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
Contents
About This Guide 7
1 Planning the Cluster Conversion 9
1.1 Supported Conversion Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Supported Mixed-Node Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 SBD Devices Must Be Marked as Shareable for Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Syntax Translation Issues for Load and Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 Case Sensitivity Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6 Adding a New NetWare Node to a Mixed-Node Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.7 Converting Multiple NetWare Cluster Nodes to OES 2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.8 Converting Nodes that Contain the eDirectory Master Replica . . . . . . . . . . . . . . . . . . . . . . . . 12
1.9 Failing Over Service Cluster Resources on Mixed-Node Clusters. . . . . . . . . . . . . . . . . . . . . . 12
1.10 Failing Over Data Cluster Resources on Mixed-Node Clusters . . . . . . . . . . . . . . . . . . . . . . . . 12
1.11 Managing File Systems in Mixed-Node Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.12 Using Novell iManager in Mixed-Node Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.13 Using Novell Remote Manager Is Not Supported in Mixed-Node Clusters . . . . . . . . . . . . . . . 13
1.14 Using ConsoleOne Is Not Supported for Mixed-Node Clusters . . . . . . . . . . . . . . . . . . . . . . . . 13
1.15 Using the Monitoring Function in Mixed-Node Clusters Is Not Supported. . . . . . . . . . . . . . . . 14
2 Planning the Conversion of Cluster Resources 15
3 Planning the Conversion of Load and Unload Scripts 19
3.1 Translation of Cluster Resource Scripts for Mixed NetWare and Linux Clusters. . . . . . . . . . . 19
3.2 Comparing Script Length Limits for NetWare and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3 Comparing Script Commands for NetWare and Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.4 Comparing Master IP Address Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4.1 Master IP Address Resource Load Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4.2 Master IP Address Resource Unload Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5 Comparing NSS Pool Resource Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5.1 NSS Pool Resource Load Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5.2 NSS Pool Resource Unload Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6 Comparing File Access Protocol Resource Script Commands . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.1 File Access Protocol Resource Load Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.6.2 File Access Protocol Resource Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.7 Customizing the Translation Syntax for Converting Load and Unload Scripts. . . . . . . . . . . . . 25
3.8 Adding Monitoring Scripts on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4 Converting NetWare 6.5 Clusters to OES 2 Linux 27
4.1 Converting NetWare Cluster Nodes to OES 2 Linux (Rolling Cluster Conversion) . . . . . . . . . 27
4.2 Adding New OES 2 Linux Nodes to Your NetWare Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.3 Finalizing the Cluster Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Contents 3
5Novell AFP 35
6 Apache Web Server 37
6.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.2 Converting the Apache Cluster Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.3 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3.1 Apache 2 Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3.2 Virtual Hosts Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7 Novell Archive and Version Services 41
7.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.2 Copying Database Files from MySQL to PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8 eDirectory Server Certificates 43
8.1 Server Certificate Changes in OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.2 Using Internal Certificates in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.3 Using External Certificates i n a Cl u s ter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9Novell CIFS 45
10 Novell Distributed File Services VLDB 47
10.1 Cluster Migrating the Shared NSS Volume for the VLDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.2 Adding a Linux Server as a Replica Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11 DHCP Server 51
11.1 Setting Up Novell DHCP on OES 2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2 Prerequisites for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.3 Migrating the DHCP Configuration from NetWare to Linux Clusters in the Same Tree. . . . . . 51
11.4 Post-Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
12 DNS Server 53
12.1 Prerequisites for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
12.2 Migrating the DNS Configuration from NetWare to Linux Clusters in the Same Tree . . . . . . . 53
12.3 Post-Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
13 Novell iPrint 55
13.1 Installing iPrint on the OES 2 Linux Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.2 Setting Up iPrint on the OES 2 Linux Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.2.1 Preparing the OES 2 Linux Nodes for iPrint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.2.2 Setting Up iPrint on the OES 2 Linux iPrint Cluster Resource. . . . . . . . . . . . . . . . . . 57
13.2.3 Setting Up Preferred Nodes for the OES 2 Linux iPrint Cluster Resource . . . . . . . . 57
13.2.4 Editing the Load and Unload Scripts for the OES 2 Linux iPrint Cluster Resource . . 57
13.2.5 Verifying the Status of the iPrint Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
13.3 Migrating the iPrint Cluster Resource from NetWare to OES 2 Linux . . . . . . . . . . . . . . . . . . . 58
13.4 Finalizing the Cluster Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
13.5 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4 OES 2 SP3: Novell Cluster Services Conversion Guide
14 MySQL 61
15 QuickFinder Server 63
15.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
15.2 Setting Up QuickFinder Server on Linux Cluster Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
15.3 Migrating QuickFinder Data from NetWare to Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
15.4 Post-Migration Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
15.5 Searching the Cluster Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
16 Novell St orage Services Pools 67
16.1 NSS Pool Cluster Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
16.2 NSS File System Migration to NCP Volumes or Linux POSIX File Systems . . . . . . . . . . . . . . 67
16.3 Estimated Time Taken to Build the Trustee File on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
A Documentation Updates 69
A.1 December 2010 (OES 2 SP3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A.1.1 Apache Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A.1.2 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 70
A.1.3 Novell Distributed File Services VLDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
A.1.4 Planning the Cluster Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
A.1.5 Planning the Conversion of Load and Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . 70
A.2 May 31, 2010 (Maintenance Patch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
A.2.1 Novell AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A.2.2 Novell CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A.3 January 29, 2010 (Maintenance Patch). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A.3.1 Planning the Cluster Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A.3.2 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A.4 January 20, 2010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
A.4.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.5 January 4, 2010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.5.1 eDirectory Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.6 December 10, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.6.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.7 November 2009 (OES 2 SP2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.7.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 73
A.7.2 Planning the Conversion of Load and Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . 73
A.8 July 30, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
A.8.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 73
A.8.2 Planning the Cluster Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
A.9 June 22, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A.9.1 Planning the Cluster Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A.10 June 5, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A.10.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A.10.2 Novell Storage Services Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.11 May 6, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.11.1 Planning the Cluster Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.12 March 3, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.12.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.13 February 13, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.13.1 Converting NetWare 6.5 Clusters to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 76
A.13.2 Novell Storage Services Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
A.13.3 Planning the Conversion of Load and Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . 76
Contents 5
A.14 February 3, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
A.14.1 Novell AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
A.15 December 2008 (OES 2 SP1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
A.15.1 Converting NetWare 6.5 Cluster to OES 2 Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
A.15.2 Planning the Cluster Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
A.15.3 Planning the Conversion of Cluster Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
A.15.4 Planning the Conversion of Load and Unload Scripts . . . . . . . . . . . . . . . . . . . . . . . . 77
6 OES 2 SP3: Novell Cluster Services Conversion Guide
About This Guide
This guide describes how to convert Novell Cluster Services cluster nodes and resources from
NetWare 6.5 Support Pack (SP) 8 (with the latest patches) to Novell Open Enterprise Server (OES)
2 SP3.
This guide includes the following sections:
Chapter 1, “Planning the Cluster Conversion,” on page 9
Chapter 2, “Planning the Conversion of Cluster Resources,” on page 15
Chapter 3, “Planning the Conversion of Load and Unload Scripts,” on page 19
Chapter 4, “Converting NetWare 6.5 Clusters to OES 2 Linux,” on page 27
Chapter 5, “Novell AFP,” on page 35
Chapter 6, “Apache Web Server,” on page 37
Chapter 7, “Novell Archive and Version Services,” on page 41
Chapter 8, “eDirectory Server Certificates,” on page 43
Chapter 9, “Novell CIFS,” on page 45
Chapter 10, “Novell Distributed File Services VLDB,” on page 47
Chapter 11, “DHCP Server,” on page 51
Chapter 12, “DNS Server,” on page 53
Chapter 13, “Novell iPrint,” on page 55
Chapter 14, “MySQL,” on page 61
Chapter 15, “QuickFinder Server,” on page 63
Chapter 16, “Novell Storage Services Pools,” on page 67
Appendix A, “Documentation Updates,” on page 69
Audience
This guide is intended for Novell Cluster Services administrators and other administrators that are
responsible for clustered services and data. It is assumed that readers of this guide have a basic
understanding of Novell Cluster Services and of the services and file systems that are being
clustered.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the OES 2 SP3: Novell Cluster Services Conversion Guide, visit the
OES 2 SP3 documentation Web site (http://www.novell.com/documentation/oes2).
About This Guide 7
Additional Documentation
For documentation on Novell Cluster Services and cluster resources management, see the OES 2
SP3 Clustering (High Availability) documentation Web site (http://www.novell.com/
documentation/oes2/cluster-services.html).
For information about managing a NetWare cluster, see the “Clustering NetWare Services” list on
the NetWare 6.5 SP8 Clustering (High Availability) documentation Web site (http://
www .novell.com/documentation/nw65/cluster-services.html#clust-config-resources).
8 OES 2 SP3: Novell Cluster Services Conversion Guide
1
Planning the Cluster Conversion
Upgrading a NetWare 6.5 SP8 cluster to Novell Open Enterprise Server 2 SP3 Linux is a multiphase process referred to as a rolling cluster conversion. This approach lets you keep your cluster up
and running and lets your users continue to access cluster resources while the conversion is in
progress. During a rolling cluster conversion, one server is converted to OES 2 while the other
servers in the cluster continue running NetW are 6.5. Then another server can be converted to OES 2,
and then another , until a ll servers in the cluster have been converted. During the conversion, you can
also add OES 2 servers to the cluster, and remove NetWare 6.5 servers from the cluster.
Before you begin a conversion, make sure your system meets the requirements and caveats
described in this section. In addition, your OES 2 Linux nodes and network environment must meet
the cluster requirements as described in “Planning for Novell Cluster Services” in the OES 2 SP3 :
Novell Cluster Services 1.8.8 Administration Guide for Linux.
Section 1.1, “Supported Conversion Paths,” on page 9
Section 1.2, “Supported Mixed-Node Clusters,” on page 10
Section 1.3, “SBD Devices Must Be Marked as Shareable for Clustering ,” on pa ge 10
Section 1.4, “Syntax Translation Issues for Load and Unload Scripts,” on page 10
Section 1.5, “Case Sensitivity Issues,” on page 11
1
Section 1.6, “Adding a New NetWare Node to a Mixed-Node Cluster,” on page 11
Section 1.7, “Converting Multiple NetWare Cluster Nodes to OES 2 Linux,” on page 11
Section 1.8, “Converting Nodes that Contain the eDirectory Master Replica,” on page 12
Section 1.9, “Failing Over Service Cluster Resources on Mixed-Node Clusters,” on page 12
Section 1.10, “Failing Over Data Cluster Resources on Mixed-Node Clusters,” on page 12
Section 1.11, “Managing File Systems in Mixed-Node Clusters,” on page 12
Section 1.12, “Using Novell iManager in Mixed-Node Clusters,” on page 13
Section 1.13, “Using Novell Remote Manager Is Not Supported in Mixed-Node Clusters,” on
page 13
Section 1.14, “Using ConsoleOne Is Not Supported for Mixed-Node Clusters,” on page 13
Section 1.15, “Using the Monitoring Function in Mixed-Node Clusters Is Not Supported,” on
page 14
1.1 Supported Conversion Paths
The following conversion paths are supported from NetWare to OES 2 Linux:
From this NetWare platform
Interim platform upgrade for all
nodes
Before conversion to this platform
NetWare 6.5 SP8 Latest patches applied OES 2 SP3 Linux
NetWare 6.0 Latest support packs and patches
applied
OES 2 SP3 Linux
Planning the Cluster Conversion
9
From this NetWare platform
Interim platform upgrade for all
nodes
Before conversion to this platform
NetWare 5.1 NetWare 6.5 SP8 with the latest
patches applied
Before converting NetWare 6.5 clusters or NetWare 6.0 clusters to OES 2 Linux, you must apply all
of the latest service packs and patches for that version. For information, see “Upgrading NetWare
Clusters” in the NW6.5 SP8: Novell Cluster Services 1.8.5 Administration Guide.
If you have a NetWare 5.1 cluster, you must upgrade all nodes to NetWare 6.5 (with the latest
service packs and patches) before you convert any nodes to OES 2 Linux or add OES 2 Linux nodes
to the cluster. For information, see “U pgrading NetWare Cluste rs” in the NW6.5 SP8: Novell Cluster
Services 1.8.5 Administration Guide.
OES 2 SP3 Linux
1.2 Supported Mixed-Node Clusters
During the conversion, the intermediate cluster is referred to as a mixed-node cluster because the
cluster contains both NetWare and Linux nodes. This is a temporary configuration that is supported
for the purpose of converting the cluster and is not supported as a long-term operational state of the
cluster.
A mixed cluster made up of NetWare 6.5 nodes and OES 2 Linux nodes is supported for the purpose
of converting the cluster from NetWare 6.5 (with the latest support packs and patches) to OES 2 SP3
Linux or later.
A mixed cluster made up of NetWare 6.0 nodes and OES 2 Linux nodes is supported for the purpose
of converting the cluster from NetWare 6.0 (with the latest support packs and patches) to OES 2 SP3
Linux or later.
A mixed cluster made up of NetWare 6.0 nodes, NetWare 6.5 nodes, and OES 2 Linux nodes is not
supported.
1.3 SBD Devices Must Be Marked as Shareable for Clustering
Novell Cluster Services for Linux requires that the devices used for the SBD partition be explicitly
marked as Shareable for Clustering. When converting a NetWare cluster, make sure that the SBD
device, or both devices for a mirrored SBD, are marked as Shareable for Clustering before you add
the first Linux node to the cluster.
1.4 Syntax Translation Issues for Load and Unload Scripts
Executing a script that is valid for the NetWa re p lat form is not ne cessarily reco gnize d on the O ES 2
Linux platform. When cluster migrating a reso urce from a NetWare node to a OES 2 Linux node, the
resource’s Load sc ri pt and Unload script need to be translat ed i n-memory while t he cluster cont ains
mixed nodes. It is also translated in-memory when the cluster is finally converted from NetWare to
Linux. This translation is done by the Cluster Translation Library script (
clstrlib.py
).
/opt/novell/ncs/bin/
10 OES 2 SP3: Novell Clu ster Services Conversion Guide
IMPORTANT: If the commands in cluster resource’s load or unload scripts are not part of the
normal translation library, the cluster resource can end up in a comatose state.
Beginning in OES 2 SP2, Novell Cluster Services allows you to customize the translation syntax
that is used for load and unload scripts in mixed-node clusters by defining them in the
novell/ncs/customized_translation_syntax
reads the additional translation syntax from the syntax file. For information, see Section 3.7,
“Customizing the Translation Syntax for Converting Load and Unload Scripts,” on page 25.
file that you create. The
clstrlib.py
/var/opt/
script
1.5 Case Sensitivity Issues
When adding a Linux node to the existing NetWare cluster, there are two areas where case
sensitivity might be an issue:
Node name: After you install the Linux node into the NetWare cluster, the Linux node is
unable to join the cluster. T o resolve th is problem, edit the
file to modify the hostname of the node from lowercase (
characters (CLUSNODE1), reboot the server, then run the
This allows the cluster node to start and join the cluster.
NOTE: This case sensitivity issue has been resolved for OES 2 SP2 and later.
Cluster object name: The Cluster object name (such as
cn=Clustername,ou=context,o=org
Clustername.sbd
(
command displays the SBD name. If the case used when you enter the Cluster object name
-f
and SBD name during the Linux cluster install do not match the case used in eDirectory, the
cluster install fails to detect the SBD partition.
) matches the case of the object name in eDirectory. Running the
) is also present on the SBD partition. The SBD name
/etc/opt/novell/ncs/nodename
clusnode1
rcnovell-ncs start
) to all uppercase
command.
sbdutil
1.6 Adding a New NetWare Node to a MixedNode Cluster
You cannot add addi tional NetWare nodes to your cluster afte r adding a new Linux node o r changing
an existing NetW are cluster node to a Linux cluster node. If you want to add NetWare cluster nodes
after converting part of your cluster to Linux, you must first remove the Linux nodes from the
cluster.
1.7 Converting Multiple NetWare Cluster Nodes to OES 2 Linux
If you attempt to concurrently convert multiple NetWare cluster servers to OES 2 Linux, we strongly
recommend that you use the old NetWare node IP addresses for your Linux cluster servers. You
should record the NetWare node IP addresses before converting them to Linux.
If you must assign new node IP addresses, we recommend that you only convert one node at a time.
Planning the Cluster Conversion 11
If new cluster node IP addresses are required and new server hardware is being used, another option
is to shut down the NetWare nodes that are to be removed and then add the new Linux cluster nodes.
After adding the new Linux cluster node s, you can remove th e NetWare clu ster node-re lated ob jects
as described in Step 5 of Section 4.1, “Converting NetWare Cluster N od es t o OES 2 Lin ux (Ro lli ng
Cluster Conversion),” on page 27.
IMPORTANT: Failure to follow these recommendations might result in NetWare server abends
and Linux server restarts.
1.8 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 eDirect ory master replica is a cluster node, convert it at
the end of the rolling cluster conversion.
1.9 Failing Over Service Cluster Resources on Mixed-Node Clusters
For service cluster resources, the intention is to have a one-time cluster migration of the service
from NetWare to OES 2 Linux. After you cluster migrate the resource to an OES 2 Linux node, the
relocated resource should be cluster migrated only be tween nodes running the OES 2 Linux
platform.
1.10 Failing Over Data Cluster Resources on Mixed-Node Clusters
Pool 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 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 assign ments to sync hronize after the mig ration. User s might
have limited access to the migrated volumes until after the synchronization process is complete.
1.11 Managing File Systems in Mixed-Node Clusters
In a mixed cluster of NetWare and OES 2 Linux nodes, Linux POSIX file systems as cluster
resources cannot be created until the entire c luster had been su ccessfully converted to OES 2 Linux.
Linux POSIX file systems as cluster resources cannot be migrated or fai led over to NetWare c luster
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.
12 OES 2 SP3: Novell Clu ster Services Conversion Guide
NetW are-to-Linux 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 in a mixed-node cluster unless you are
performing documented steps for the conversion. That is, do not create, delete, expand, o r modify
the properties for partitions, pools, or volumes for shared resources in the cluster unless the
conversion instructions specifically guide you to do so.
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 all Linux cluster nodes prior to making changes, then
make the configuration changes on a NetWare node. Make sure the resources are working properly
on NetWare before having the Linux cluster nodes rejoin the cluster.
1.12 Using Novell iManager in Mixed-Node Clusters
Use Novell iManager 2.7.2 or later for all cluster administrati on 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 mixe d-node cluster. However, you can use
admin/Novell/Cluster/NodeConfig.xml
on any cluster node to get the node IDs.
cat /
1.13 Using Novell Remote Manager Is Not Supported in Mixed-Node Clusters
Do not use Novell Remote Manager when managing mixe d-no de clu s ters. N ovell Remote Manager
is not supported for cluster management on OES 2 Linu x.
Because different time formats are used in the NCS Event log for NetWare and Linux, Novell
Remote Manager might have difficulty displaying the time of logged events. To avoid this problem
in a mixed-node cluster, use iManager to access the NCS Event log.
To reduce any confusion you might have when using Novell Remote Manager, you can unload
module
in Novell Remote Manager.
pcluster.nlm
and delete its references in
ldncs
and
uldncs
. This removes the Cluster tab
1.14 Using ConsoleOne Is Not Supported for Mixed-Node Clusters
Do not use ConsoleOne when managing mixed-node clusters. ConsoleOne is not supported for
cluster management on OES 2 Linux.
Planning the Cluster Conversion 13
1.15 Using the Monitoring Function in MixedNode Clusters Is Not Supported
In mixed-node clusters, the Monitor function in Novell Cluster Services for Linux is not available.
You cannot enable the Monitor function or modify the Monitor script for cluster resources on the
Linux nodes until the conversion is finalized and all nodes in the cluster are running OES 2 Linux.
Then the monitor scripts are created automatically for each of the converted cluster resources.
14 OES 2 SP3: Novell Clu ster Services Conversion Guide
2
Planning the Conversion of Cluster Resources
In addition to changing the operating system, the software and file systems for various clustered
services must also be considered in your conversion from NetWare 6.5 to Novell Open Enterprise
Server (OES) 2. This section provides an overview of the NetWare 6.5 services and their
counterparts in OES 2 SP3. Before you begin a conversion, make sure your system meets the
general requirements and caveats described in this section.
Converting cluster resources for OES 2 services from NetWare to Linux might require more than a
simple cluster migration from a NetWare node to a Linux node. For example, the service might
require that you use Migration Tool to convert the service to Linux. Some services require postconversion configuration to finalize the conversion. A few services on NetWare are not available on
OES 2 Linux, so you must use the standard Linux service instead.
See Table 2-1 for information about converting cluster resources for NetWare 6.5 SP8 services:
Table 2-1 Guidelines for Converting Service Cluster Resources from NetWare to Linux
Service on NetWare 6.5
SP8
Apache Web Server Yes See Chapter 6, “Apache Web Server,” on page 37.
Cluster Migrate the
Resource
Converting the Service to OES 2 Linux
2
Apple Filing Protocol
(AFP)
Archive and Version
Services
CIFS
(Windows File
Services)
DFS VLDB
(Distributed File
Services volume
location database)
DHCP Server Yes See Chapter 11, “DHCP Server,” on page 51.
DNS Server Yes See Chapter 12, “DNS Server,” on page 53 .
eDirectory Not clustered, but
Yes See Chapter 5, “Novell AFP,” on page 35.
No, but you can
migrate the database
Yes See Chapter 9, “Novell CIFS,” on page 45.
Yes See Chapter 10, “Novell Distributed File Services
requires special
handling
See Chapter 7, “Novell Archive and Version
Services,” on page 41.
VLDB,” on page 47.
See Section 1.8, “Converting Nodes that Contain the
eDirectory Master Replica,” on page 12.
Planning the Conversion of Cluster Resources
15
Service on NetWare 6.5
SP8
Cluster Migrate the
Resource
Converting the Service to OES 2 Linux
eDirectory Certificate
Server
Not clustered, but
requires special
handling
The Certificate Authority (CA) service is not clusterenabled for NetWare or OES 2 Linux. There are no
cluster-specific tasks for the CA itself.
The Server Certificate service issues Server
Certificate objects that might need to reside on each
node in a cluster, depending on the service that is
clustered. NetWare and Linux generate certificates
differently, so the NetWare server’s certificate is not
reused for the OES 2 Linux server.
See Chapter 8, “eDirectory Server Certificates,” on
page 43.
exteNd Application
Server and MySQL
Not applicable The exteNd Application Server was discontinued as
an install option for NetWare 6.5 SP3. It is not
available for Linux.
See also MySQL in this table.
FTP No Use the Pure-FTPd service for Linux.
For information, see “Novell FTP (Pure-FTPd) and
OES 2” in the OES 2 SP3: Planning and
Implementation Guide.
iFolder No, but you can
migrate the settings
Novell iFolder 2.1x is not available on OES 2 Linux.
You must use Novell iFolder 3.x.
and data
After you add a Novell iFolder 3.x server to the
NetWare cluster and before you finalize the cluster
conversion, use iFolder migration procedures to
migrate the iFolder 2.1x server configuration and user
data from the source NetWare node to the target
Linux node. For information, see “Migrating iFolder
Services” in the Novell iFolder 3.8.4 Administration
Guide.
iPrint Yes See Chapter 13, “Novell iPrint,” on page 55.
MySQL No Use the MySQL 5.0.x software on OES2 Linux that is
NetStorage Not tested Clustering the NetStorage service is supported for
NFS No Use standard NFS service for Linux.
16 OES 2 SP3: Novell Clu ster Services Conversion Guide
offered under the GPL.
See Chapter 14, “MySQL,” on page 61.
OES 2 SP1 Linux and later.
For information, see “Configuring NetStorage with
Novell Cluster Services” in the OES 2 SP3:
NetStorage Administration Guide.
Service on NetWare 6.5
SP8
Cluster Migrate the
Resource
Converting the Service to OES 2 Linux
QuickFinder (Server
Synchronization
Feature)
No, but you can
migrate the settings
and data
You must create a new cluster resource. QuickFinder
5.0.x is supported only on OES 2 Linux. NetWare
uses QuickFinder 4.2.0. QuickFinder does not support
any automated procedure or scripts for a rolling
upgrade from Netware to Linux.
Instead of converting the resource, you can migrate
the settings from NetWare after you set up a
QuickFinder resource on Linux.
See Chapter 15, “QuickFinder Server,” on page 63.
NSS pools and
volumes
Yes See Chapter 16, “Novell Storage Services Pools,” on
page 67.
Tomcat No Use the standard Tomcat service for Linux.
Planning the Conversion of Cluster Resources 17
18 OES 2 SP3: Novell Clu ster Services Conversion Guide
3
Planning the Conversion of Load and Unload Scripts
You can use a rolling cluster conversion to convert a Nove ll Clu ster Service s cluste r fro m Ne tWare
6.5 SP8 to Novell Open Enterprise Server (OES) 2 SP3 Linux. This section describes how to prepare
for and perform the conversion, and how to manage the temporarily mixed cluster during the
conversion.
Section 3.1, “T ran s la tio n o f Clust er Reso urce Scrip ts for Mi xed Ne tWare an d Li nu x Cl ust ers,”
on page 19
Section 3.2, “Comparing Script Length Limits for NetWare and Linux,” on page 20
Section 3.3, “Comparing Script Commands for NetWare and Linux,” on page 20
Section 3.4, “Comparing Master IP Address Scripts,” on page 21
Section 3.5, “Comparing NSS Pool Resource Scripts,” on page 22
Section 3.6, “Comparing File Access Protocol Resource Script Commands,” on page 23
Section 3.7, “Customizing the Translation Syntax for Converting Load and Unload Scripts,” on
page 25
Section 3.8, “Adding Monitoring Scripts on Linux,” on page 26
3.1 Translation of Cluster Resource Scripts for
3
Mixed NetW are and Linux Clusters
Novell Cluster Services includes specialized script translation functionality, called the Cluster
Translation Library script (
servers coexist in the same cluster. It provides an automatic translation of the Master IP Address
resource and cluster-enabled NSS pool resource load and unload scripts from NetWare to Linux.
This functionality is also beneficial as you migrate NetWare cluster servers to Linux.
The Cluster Translation Library reads the NetWare load and unload scripts from eDirectory,
converts them, and writes them as Linux load and unload scri pt files. The Linux load and unload
script files are then searched for NetWare-specific command strings, and the command strings are
then either deleted or replaced with Linux-specific command strings. Separate Linux-specific
commands are also added, and the order of certain lines in the scripts is also changed to function
with Linux.
The Linux load and unload scripts are stored in files on Linux cluster servers, instead of being stored
in eDirectory like the NetWare scripts. The cluster resource name is used in the load and unload
script filenames. The path to the files is
IMPORTANT: Use the Properties > Scripts page in the Clusters plug-in in iManager whenever
you make manual changes to the load and unload scripts. The changes are automatically saved to the
files.
/opt/novell/ncs/bin/clstrlib.py
/var/opt/novell/ncs/
), to help NetWare and Linux
.
Planning the Conversion of Load and Unload Scripts
19
The normal translations performed by the Cluster Translation Library are described in the following
sections:
Section 3.3, “Comparing Script Commands for NetWare and Linux,” on page 20
Section 3.4, “Comparing Master IP Address Scripts,” on page 21
Section 3.5, “Comparing NSS Pool Resource Scripts,” on page 22
Section 3.6, “Comparing File Access Protocol Resource Script Commands,” on page 23
IMPORTANT: If the commands in cluster resource’s load or unload scripts are not part of the
translation library, the cluster resource can end up in a comatose state.
Beginning in OES 2 SP2, Novell Cluster Services allows you to customize the translation syntax
that us used for load and unload scripts in mixed-platform situations by defining new syntax
translations to be used in addition to the normal translations. For information, see Section 3.7,
“Customizing the Translation Syntax for Converting Load and Unload Scripts,” on page 25.
3.2 Comparing Script Length Limits for NetWare and Linux
Scripts have different size limits on NetWare and OES 2 Linux. In a mixed-node cluster, the scripts
for NetWare resources that are cluster migrated to OES 2 Linux nodes are restricted to the NetWare
script-size limits until the final
cluster convert
command is issued.
The maximum supported lengths for cluster scripts’ content are as follows:
Script
Load script 924 bytes 924 bytes 3200 bytes
Unload script 924 bytes 924 bytes 3200 bytes
Monitor script Not supported Not supported 3200 bytes
NetWare 6.5 Resources
on NetWare Nodes
NetWare 6.5 Resources
on OES 2 Linux Nodes
OES 2 Linux Resources
and Converted NetWare
Resources After the Final
Conversion
In cases where a Linux converted script exceeds the imposed NetWare script size limit, it is best to
avoid bringing the resource online on OES 2 Linux nodes until the final cluster convert command
has been run.
IMPORTANT: Because the Linux script for GroupWise exceeds the NetWare script limit, we
recommend that you do not online GroupWise resources in while running in mixed-node clusters.
3.3 Comparing Script Commands for NetWare and Linux
Table 3-1 identifies some of the NetWare cluster load and unload script commands that the Cluster
Translation Library script searches for and the Linux commands that it replaces them with (unless
the commands are deleted).
20 OES 2 SP3: Novell Clu ster Services Conversion Guide
Table 3-1 Cluster Script Command Comparison
Action NetWare Cluster Command Linux Cluster Command
Replace
Replace
Replace
Replace
Delete
Delete
Replace
Replace
Replace
Replace
Replace
IGNORE_ERROR add secondary
ipaddress
IGNORE_ERROR del secondary
ipaddress
del secondary ipaddress ignore_error
add secondary ipaddress exit_on_error
IGNORE_ERROR NUDP
IGNORE_ERROR HTTP
nss /poolactivate= nss /poolact=
nss /pooldeactivate= nss /pooldeact=
mount volume_name VOLID=number exit_on_error ncpcon mount
NUDP ADD clusterservername
ipaddress
NUDP DEL clusterservername
ipaddress
ignore_error
add_secondary_ipaddress
ignore_error
del_secondary_ipaddress
del_secondary_ipaddress
add_secondary_ipaddress
(deletes the entire line)
(deletes the entire line)
volume_name=number
exit_on_error ncpcon bind
--ncpservername=ncpservername
--ipaddress=ipaddress
ignore_error ncpcon unbind
--ncpservername=ncpservername
--ipaddress=ipaddress
Delete
Delete
CLUSTER CVSBIND
CIFS
(deletes the entire line)
(deletes the entire line)
3.4 Comparing Master IP Address Scripts
Section 3.4.1, “Master IP Address Resource Load Script,” on page 21
Section 3.4.2, “Master IP Address Resource Unload Script,” on page 22
3.4.1 Master IP Address Resource Load Script
This section provides examples o f the master IP address resource load scripts on NetWare and
Linux.
“NetWare” on page 22
“Linux” on page 22
Planning the Conversion of Load and Unload Scripts 21
NetWare
IGNORE_ERROR set allow ip address duplicates = on
IGNORE_ERROR CLUSTER CVSBIND ADD BCCP_Cluster 10.1.1.175
IGNORE_ERROR NUDP ADD BCCP_Cluster 10.1.1.175
IGNORE_ERROR add secondary ipaddress 10.1.1.175
IGNORE_ERROR HTTPBIND 10.1.1.175 /KEYFILE:"SSL CertificateIP"
IGNORE_ERROR set allow ip address duplicates = off
Linux
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
ignore_error add_secondary_ipaddress 10.1.1.175 -np
exit 0
3.4.2 Master IP Address Resource Unload Script
This section provides examples of the master IP address resource unload scripts on NetWare and
Linux.
“NetWare” on page 22
“Linux” on page 22
NetWare
IGNORE_ERROR HTTPUNBIND 10.1.1.175
IGNORE_ERROR del secondary ipaddress 10.1.1.175
IGNORE_ERROR NUDP DEL BCCP_Cluster 10.1.1.175
IGNORE_ERROR CLUSTER CVSBIND DEL BCCP_Cluster 10.1.1.175
Linux
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
ignore_error del_secondary_ipaddress 10.1.1.175
exit 0
3.5 Comparing NSS Pool Resource Scripts
Section 3.5.1, “NSS Pool Resource Load Script,” on page 22
Section 3.5.2, “NSS Pool Resource Unload Script,” on page 23
3.5.1 NSS Pool Resource Load Script
This section provides examples of the NSS pool resource load scripts on NetWare and Linux.
“NetWare” on page 23
“Linux” on page 23
22 OES 2 SP3: Novell Clu ster Services Conversion Guide
NetWare
nss /poolactivate=HOMES_POOL
mount HOMES VOLID=254
CLUSTER CVSBIND ADD BCC_CLUSTER_HOMES_SERVER 10.1.1.180
NUDP ADD BCC_CLUSTER_HOMES_SERVER 10.1.1.180
add secondary ipaddress 10.1.1.180
CIFS ADD .CN=BCC_CLUSTER_HOMES_SERVER.OU=servers.O=lab.T=TEST_TREE.
Linux
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=HOMES_POOL
exit_on_error ncpcon mount HOMES=254
exit_on_error add_secondary_ipaddress 10.1.1.180
exit_on_error ncpcon bind --ncpservername=BCC_CLUSTER_HOMES_SERVER
--ipaddress=10.1.1.180
exit 0
3.5.2 NSS Pool Resource Unload Script
This section provides examples of the NSS pool resource unload scripts on NetWare and Linux.
“NetWare” on page 23
“Linux” on page 23
NetWare
del secondary ipaddress 10.1.1.180
CLUSTER CVSBIND DEL BCC_CLUSTER_HOMES_SERVER 10.1.1.180
NUDP DEL BCC_CLUSTER_HOMES_SERVER 10.1.1.180
nss /pooldeactivate=HOMES_POOL /overridetype=question
CIFS DEL .CN=BCC_CLUSTER_HOMES_SERVER.OU=servers.O=lab.T=TEST_TREE.
Linux
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
ignore_error ncpcon unbind --ncpservername=BCC_CLUSTER_HOMES_SERVER
--ipaddress=10.1.1.180
ignore_error del_secondary_ipaddress 10.1.1.180
ignore_error nss /pooldeact=HOMES_POOL
exit 0
3.6 Comparing File Access Protocol Resource Script Commands
Section 3.6.1, “File Access Protocol Resource Load Scripts,” on page 24
Section 3.6.2, “File Access Protocol Resource Unload Scri pts,” on page 24
Planning the Conversion of Load and Unload Scripts 23
3.6.1 File Access Protocol Resource Load Scripts
This section provides examples of the file access protocol commands for load scripts on NetWare
and Linux.
“NetWare” on page 24
“Linux” on page 24
NetWare
Protocol Script Command for Load Scripts
NCP
Novell AFP
Novell CIFS
NUDP ADD NCS1_P1_SERVER 10.10.10.194
AFPBIND ADD NCS1_P1_SERVER 10.10.10.204
CIFS ADD .CN=NCS1_P1_SERVER.O=novell.T=CLUSTER.
Linux
Protocol Script Command for Load Scripts
NCP
Novell AFP
Novell CIFS
# mount the NCP volume
exit_on_error ncpcon mount $NCP_VOLUME=VOL_ID,PATH=$MOUNT_POINT
exit_on_error ncpcon bind --ncpservername=NCS1_P1_SERVER
--ipaddress=10.10.10.194
exit_on_error cluster_afp.sh add NCS1_P1_SERVER 10.10.10.204
exit_on_error novcifs --add
--vserver=.CN=NCS1_P1_SERVER.O=novell.T=TREE-188. --ipaddr=<virtual_server_ip_address>
3.6.2 File Access Protocol Resource Unload Scripts
This section provides examples of the Novell AFP commands for unload scripts on NetWare and
Linux.
“NetWare” on page 24
“Linux” on page 25
NetWare
Protocol Script Command for Unload Scripts
NCP
Novell AFP
Novell CIFS
NUDP DEL NCS1_P1_SERVER 10.10.10.194
AFPBIND DEL NCS1_P1_SERVER 10.10.10.204
CIFS DEL .CN=NCS1_P1_SERVER.O=novell.T=TREE-188.
24 OES 2 SP3: Novell Clu ster Services Conversion Guide
Loading...