User manual NOVELL BUSINESS CONTINUITY CLUSTERING 1.0 ADMINISTRATION

[. . . ] Novell Business Continuity Cluster Services 1. 0 Administration Guide novdocx (ENU) 10 August 2006 Novell Business Continuity Clustering 1. 0 ADMINISTRATION GUIDE May 22, 2006 www. novell. com novdocx (ENU) 10 August 2006 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. 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. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] This context must be a parent container to all contexts where cluster-enabled pool and voume objects for the other cluster reside. Prior to performing this step, you could create a separate container in eDirectory specificly for these cluster pool and volume objects. You would then specify the context of the new container in this step. Name of other tree : Enter the name of the tree where the other cluster is located. This could be the same tree if the clusters are in the same eDirectory tree. The DirXML Driver object must have sufficient rights to create, mofify, and delete objects and attributes in the container where the cluster objects reside, and if necessary, in the container where the user objects reside. You can do this by making the DirXML Driver object security equivalent to the Admin User object or to another user object with those rights. If you choose to include User object synchronization, exclude the Admin User object from being synchronized. You can also exclude the Cluster Resource Driver object from being synchronized. 9 Make the DirXML Driver object security equivalent to an administrative User object. The DirXML Driver object must have sufficient rights to create, mofify, and delete objects and attributes in the container where the cluster objects reside, and if necessary, in the container where the user objects reside. You can do this by making the DirXML Driver object security equivalent to the Admin User object or to another user object with those rights. Installation and Setup 31 novdocx (ENU) 10 August 2006 9a Click the Define Security Equivalences button, then click Add. 9b Browse to and select the desired User object, then click OK. 10 (Optional) If you want to synchronize User objects between clusters in separate trees, repeat Step 1 through Step 9, and in Step 7, select the preconfigured template for User object synchronization. The template name is BCCUserObjectSynchronization. XML. To synchronize User objects 10a In the left column of the iManager page, click DirXML and then click DirXML Overview. 10b Search for the eDirectory tree for the DirXML driver sets by clicking Search. 10c Click the User Sync driver icon, then click Migrate from eDirectory. 10d Click Add, browse to and select the context that contains the User objects, then click OK. 11 (Optional) If you choose to include user object synchronization, exclude the Admin User object from being synchronized. 11a Click the Exclude Administrative Roles button, then click Add. 11b Browse to and select the Admin User object, then click OK. [. . . ] The virtual IP addresses on a given virtual IP network must go unused, thereby wasting a portion of the available address space. 52 Novell Business Continuity Cluster Services 1. 0 Administration Guide novdocx (ENU) 10 August 2006 Neither of these situations is desirable. Fortunately, the use of host masks remedies both. 3. 5 Configuring Virtual IP Addresses The routers in a virtual IP address configuration must be running the RIP I or RIP II protocols. For a business continuity cluster, RIP II is the preferred protocol and should be used whenever possible. In NetWare, this can be accomplished by configuring the NetWare RIP Bind Options to use RIP I and RIPII, or RIPII only. [. . . ]