1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. BUSINESS CONTINUITY CLUSTERING 1.2.1 -...
  6. Administration manual

Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
AUTHORIZED DOCUMENTATION
Administration Guide for Novell Open Enterprise Server 2 Support
*
Pack 2 for Linux
Novell
®

Business Continuity Clustering

1.2.1
February 18, 2010
www.novell.com
BCC 1.2.1: Administration Guide for OES 2 SP2 Linux

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION and is the answer not in the manual?

Questions and answers

Related Manuals for Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION

Summary of Contents for Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION

  • Page 1: Business Continuity Clustering

    AUTHORIZED DOCUMENTATION Administration Guide for Novell Open Enterprise Server 2 Support Pack 2 for Linux Novell ® Business Continuity Clustering 1.2.1 February 18, 2010 www.novell.com BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 2: Legal Notices

    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.
  • Page 3 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.
  • Page 4 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 5: Table Of Contents

    Contents About This Guide 1 Overview of Business Continuity Clustering Disaster Recovery Implications ..........13 Disaster Recovery Implementations .
  • Page 6 Novell Cluster Services 1.8.7 for Linux ........
  • Page 7 Novell eDirectory ........
  • Page 8 11.6 Resolving Business Continuity Cluster Failures........99 11.6.1 Storage-Based Mirroring Failure Types and Responses .
  • Page 9 Novell Cluster Services Configuration and Setup ....... . . 144...
  • Page 10 F.2.2 Unlimited Mobility........... 169 F.2.3 Automatic Name Resolution .

  • Page 11: About This Guide

    This guide describes how to install, configure, and manage Novell Business Continuity Clustering 1.2.1 for Novell Open Enterprise Server (OES) 2 Support Pack 2 (SP2) Linux servers in combination with Novell Cluster Services 1.8.7 (the version released in OES 2 SP2 Linux).

  • Page 12: Additional Documentation

    For information about NetWare 6.5 SP8, see the NetWare 6.5 SP8 Documentation Web site (http:// www.novell.com/documentation/nw65/index.html). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.

  • Page 13: Overview Of Business Continuity Clustering

    Clustering As corporations become more international, fueled in part by the reach of the Internet, the ® requirement for service availability has increased. Novell Business Continuity Clustering (BCC) offers corporations the ability to maintain mission-critical (24x7x365) data and application services to their users while still being able to perform maintenance and upgrades on their systems.

  • Page 14: Disaster Recovery Implementations

    Moving applications and services to the Internet frees corporations from the restrictions of traditional LAN-based applications. ® By using Novell exteNd Director portal services, Novell Access Manager, and ZENworks , all services, applications, and data can be rendered through the Internet, allowing for loss of service at one site but still providing full access to the services and data by virtue of the ubiquity of the Internet.

  • Page 15: Stretch Clusters Vs. Cluster Of Clusters

    Stretch Clusters A stretch cluster consists of a single cluster where the nodes are located in two geographically separate data centers. All nodes in the cluster must be in the same Novell eDirectory tree, which requires the eDirectory replica ring to span data centers. The IP addresses for nodes and cluster resources in the cluster must share a common IP subnet.
  • Page 16 At least one storage system must reside in each data center. The data is replicated between locations by using host-based mirroring or storage-based mirroring. For information about using mirroring solutions for data replication, see Section 1.2.2, “Host-Based versus Storage-Based Data Mirroring,” on page 14.
  • Page 17 Nodes in each cluster access only the storage systems co-located in the same data center. Typically, data is replicated by using storage-based mirroring. Each cluster has its own SBD partition. The SBD partition is not mirrored across the sites, which minimizes the chance for a split-brain problem occurring when using host-based mirroring.
  • Page 18 Capability Stretch Cluster Cluster of Clusters eDirectory Organizational Units Single OU container for all nodes. Each cluster can be in a different (OUs) OU. Each cluster is in a single As a best practice, place the OU container. cluster container in an OU separate from the rest of the tree.
  • Page 19 Table 1-3 illustrates why a cluster of cluster solution is less problematic to deploy than a stretch cluster solution. Manual configuration is not a problem when using Novell Business Continuity Clustering for your cluster of clusters. Advantages and Disadvantages of Stretch Clusters versus Cluster of Clusters...

  • Page 20: Business Continuity Clustering

    1.3 Business Continuity Clustering A Novell Business Continuity Clustering cluster is an automated cluster of Novell Cluster Services clusters. It is similar to what is described in “Cluster of Clusters” on page 16, except that the cluster configuration, maintenance, and synchronization have been automated by adding specialized software.

  • Page 21: Bcc Deployment Scenarios

    Provides simplified business continuity cluster configuration and management by using the browser-based Novell iManager management tool. iManager is used for the configuration and monitoring of the overall system and for the individual resources.

  • Page 22: Multiple-Site Business Continuity Cluster Solution

    Active Site/Passive Site: A primary site in which all services are normally active, and a secondary site which is effectively idle. The data is mirrored to the secondary site, and the applications and services are ready to load if needed. The active/active deployment option is typically used in a company that has more than one large site of operations.

  • Page 23: Low-Cost Business Continuity Cluster Solution

    Figure 1-4 depicts a four-site business continuity cluster that uses storage-based data replication between the sites. BCC uses eDirectory and Identity Manager to synchronize cluster information between the two clusters. Four-Site Business Continuity Cluster Figure 1-4 Four independent clusters in geographically separate sites Building D Building C...

  • Page 24: Key Concepts

    Section 1.5.4, “BCC Drivers for Identity Manager,” on page 24 1.5.1 Business Continuity Clusters A cluster of two to four Novell Cluster Services clusters that are managed together by Business Continuity Clustering software. All nodes in every peer cluster are running the same operating system.

  • Page 25: What's New For Bcc 1.2

    This section describes the changes and enhancements that were made to Novell Business Continuity Clustering (BCC) 1.2.1 for Novell Open Enterprise Server (OES) 2 Support Pack 2 (SP2) Linux since the initial release of BCC 1.2 for OES 2 SP1 Linux.

  • Page 26: Bcc 1.2.0 Patch (January 2010)

    The BCC 1.2.1 patch includes the following benefits and changes for the BCC engine: Support for OES 2 SP2 Linux with the latest patches applied. Support for Novell Cluster Services 1.8.7 (the version released with OES 2 SP2 Linux) with the latest patches applied, including the latest Clusters plug-in.

  • Page 27: Bcc Engine

    Typically, the wait is less than 10 seconds. Modified the post-install script of the Novell BCC specification file to wait up to 5 seconds when is stopped. Typically, the wait is about 1 second. adminfsd Improves memory management functions that might cause the daemon to die.

  • Page 28: Identity Manager 3.6.1 Support (June 2009)

    ® for NetWare 6.5 SP8: Support for OES 2 SP1 Linux Support for Novell Cluster Services 1.8.6 for Linux Support for Identity Manager 3.6 (32-bit). A 64-bit update is planned. Support for 32-bit and 64-bit architectures Support for Novell eDirectory 8.8 Support for Novell iManager 2.7.2...

  • Page 29: Planning A Business Continuity Cluster

    Planning a Business Continuity Cluster ® Use the guidelines in this section to design your Novell Business Continuity Clustering solution. The success of your business continuity cluster depends on the stability and robustness of the individual peer clusters. BCC cannot overcome weaknesses in a poorly designed cluster environment.

  • Page 30: Lan Connectivity Guidelines

    When configuring Spanning Tree Protocol (STP), ensure that Portfast is enabled, or consider Rapid Spanning Tree. The default settings for STP inhibit the heartbeat for over 30 seconds whenever there is a change in link status. Test your STP configuration with Novell Cluster Services running to make sure that a node is not cast out of the cluster when a broken link is restored.

  • Page 31: San Connectivity Guidelines

    The primary objective of SAN (storage area network) connectivity in a cluster is to provide solid and stable connectivity between cluster nodes and the storage system. Before installing Novell Cluster Services and Novell Business Continuity Clustering, make sure the SAN configuration is established and verified.

  • Page 32: Storage Design Guidelines

    3.6 eDirectory Design Guidelines Your Novell eDirectory solution for each of the peer clusters in the business continuity cluster must consider the following configuration elements. Make sure your approach is consistent across all peer clusters.

  • Page 33: Cluster Context

    3.6.2 Cluster Context Place each cluster in a separate Organizational Unit (OU). All server objects and cluster objects for a given cluster should be in the same OU. Cluster Resources in Separate OUs Figure 3-1 3.6.3 Partitioning and Replication Partition the cluster OU and replicate it to dedicated eDirectory servers holding a replica of the ®...

  • Page 34: Naming Conventions For Bcc-Enabled Resources

    Cluster Resource Identity in Two Clusters Figure 3-2 3.7 Cluster Design Guidelines Your Novell Cluster Services solution for each of the peer clusters in the business continuity cluster must consider the following configuration guidelines. Make sure your approach is consistent across all peer clusters.
  • Page 35 ID 1 to volume . Cluster-enabled volumes use _ADMIN high volume IDs, starting from 254 in descending order. Novell Client uses the volume ID to access a volume. When existing clusters are configured and enabled within the same business continuity cluster, the volume IDs for the existing shared volumes might also share the same volume IDs.
  • Page 36 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 37: Installing Business Continuity Clustering

    This section describes how to install, set up, and configure Novell Business Continuity Clustering 1.2.1 for Novell Open Enterprise Server (OES) 2 SP2 Linux to meet your specific needs. Section 4.1, “Requirements for BCC 1.2.1 for OES 2 SP2 Linux,” on page 37 Section 4.2, “Downloading the Business Continuity Clustering Software,”...

  • Page 38: Business Continuity Clustering License

    Novell iManager 2.7.3 NCS: Novell Cluster Services 1.8.7 for OES 2 SP2 Linux, with the January 2010 patch OES Linux: Novell Open Enterprise Server 2 SP2 for Linux, with the January 2010 patch BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 39: Oes 2 Sp2 Linux

    4.1.3 OES 2 SP2 Linux Novell Open Enterprise Server (OES) 2 Support Pack 2 (SP2) Linux must be installed and running on each node in every peer cluster that will be part of the business continuity cluster. The January 2010 patch is required.

  • Page 40: Novell Edirectory 8.8.5

    To add or change peer cluster credentials, you must access iManager on a server that is in the same eDirectory tree as the cluster where you are adding or changing peer credentials. 4.1.5 Novell eDirectory 8.8.5 Novell eDirectory 8.8.5 is supported with Business Continuity Clustering 1.2.1. See the eDirectory 8.8.5 documentation (http://www.novell.com/documentation/edir88/index.html) for more information.

  • Page 41: Slp

    Typically, SLP is installed as part of the eDirectory installation and setup when you install the server operating system for the server. For information, see “Implementing the Service Location Protocol” (http://www.novell.com/documentation/edir88/edir88/data/ba5lb4b.html) in the Novell eDirectory 8.8 Administration Guide. Installing Business Continuity Clustering...

  • Page 42: Identity Manager 3.6.1 Bundle Edition

    The bundle edition is a limited release of Identity Manager 3.6.1 for OES 2 SP2 Linux that allows you to use the Identity Manager software, the eDirectory driver, and the Identity Manager management tools for Novell iManager 2.7.3. BCC driver templates are applied to the eDirectory driver to create BCC-specific drivers that automatically synchronize BCC configuration information between the Identity Manager nodes in peer clusters.

  • Page 43: Novell Imanager 2.7.3

    4.1.8 Novell iManager 2.7.3 Novell iManager 2.7.3 (the version released with OES 2 SP2 Linux with the latest patches and plug- ins applied) must be installed and running on a server in the eDirectory tree where you are installing Business Continuity Clustering software.

  • Page 44: Storage-Related Plug-Ins For Imanager 2.7.3

    If you use more than one of these plug-ins, storagemgmt.npm you should install, update, or remove them all at the same time to make sure the common code works for all plug-ins. Other storage-related plug-ins are Novell Storage Services (NSS) ( ), Novell AFP nssmgmt.npm...

  • Page 45: Shared Disk Systems

    For information about how to configure host-based file system mirroring for Novell Storage Services pool resources, see Appendix C, “Configuring Host-Based File System Mirroring for NSS...

  • Page 46: Lun Masking For Shared Devices

    See your storage system vendor documentation for more information on configuring LUN masking. When you create a Novell Cluster Services system that uses a shared storage system, it is important to remember that all of the servers that you grant access to the shared device, whether in the cluster or not, have access to all of the volumes on the shared storage space unless you specifically prevent such access.

  • Page 47: Web Browser

    4.2 Downloading the Business Continuity Clustering Software For new installs, before you install Novell Business Continuity Clustering, download and copy the software to a directory on your workstation. To download Novell Business Continuity Clustering 1.2.1 for OES 2 SP2 Linux, contact Novell Support (http://www.novell.com/support).

  • Page 48: Configuring A Bcc Administrator User And Group

    Add all Linux nodes (Node objects) in the cluster to the bccgroup For information about LUM-enabling groups, see “Managing User and Group Objects in eDirectory” in the OES 2 SP2: Novell Linux User Management Technology Guide. LUM-enabling the automatically enables all users in that group for Linux. bccgroup...

  • Page 49: Assigning Trustee Rights For The Bcc Administrator User To The Cluster Objects

    In order for the BCC Administrator user to gain access to the cluster administration files ( /admin/ ) on other Linux cluster nodes in your BCC, you must add that user to the Novell novell/cluster Cluster Services administration group (such as ) on each cluster node.

  • Page 50: Installing And Configuring The Novell Business Continuity Clustering Software

    4.4 Installing and Configuring the Novell Business Continuity Clustering Software It is necessary to run the Novell Business Continuity Clustering installation program when you want Install and configure Business Continuity Clustering engine software on the cluster nodes for the clusters that will be part of a business continuity cluster.

  • Page 51: Configuring Bcc Software

    2 Use one of the following methods to open the BCC Configuration page: In YaST, select Miscellaneous > Novell-BCC. At a terminal console prompt, enter yast2 novell-bcc 3 When prompted to Install Core Business Continuity Clustering Software and Configure Core Software, click Yes to install and configure the BCC software.

  • Page 52: Installing The Bcc Identity Manager Templates

    9 Accept or change the eDirectory Administrator user name and specify the Administrator user’s password. 10 Click Next. 11 Review your setup on the Novell Business Continuity Clustering Configuration Summary page, then click Next to install the BCC software. 12 Click Finish to save the BCC configuration and exit the tool.

  • Page 53: Using A Yast Auto-Configuration File To Install And Configure Business Continuity Clustering

    The file should appear similar to the example below. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http:// www.suse.com/1.0/configns"> <configure> <bcc> <config-type>New</config-type> <start-now>Yes</start-now> <cluster-dn>cn=my_cluster.o=novell</cluster-dn> <ldap-server>10.1.1.0</ldap-server> <ldap-port>389</ldap-port> <ldap-secure-port>636</ldap-secure-port> <admin-dn>cn=admin.o=novell</admin-dn> <admin-password>password</admin-password> </bcc> </configure> </profile> Edit the above example to apply to your own specific system settings.

  • Page 54: Media

    4 Install Business Continuity Clustering software by opening a shell and running the following commands in the order indicated: yast2 sw_single -i \ novell-business-continuity-cluster \ novell-cluster-services-cli \ yast2-bcc 5 Autoconfigure the Business Continuity Clustering software by running the following command from a shell: BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 55: Removing The Nfs Share From Your Server

    yast2 bcc_autoconfig path_to_XML_profile Replace path_to_XML_profile with the path to the file you created in Step 1 on page 6 Remove the installation source you created in Step 1 above by completing the following steps: 6a Open a shell and run yast2 inst_source 6b Select the Business Continuity Clustering installation source, click Delete, then click Finish.
  • Page 56 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 57: Updating (Patching) Bcc 1.2.1 On Oes 2 Sp2 Linux

    OES 2 SP2 Linux with the January 2010 patches applied Novell eDirectory 8.8.5 Novell Cluster Services 1.8.7 for OES 2 SP2 Linux with the January 2010 patches applied, including the Clusters plug-in Novell iManager 2.7.3, with the January 2010 patches applied.

  • Page 58: Installing The Bcc Patch On A Fully Patched Oes 2 Sp2 Linux Bcc Cluster

    The following BCC 1.2.1 patch is available for OES 2 SP2 Linux: OES2 SP2 January 2010 Scheduled Maintenance 20100130: The BCC 1.2.1 patch includes the following RPM files: novell-business-continuity-cluster-1.2.1.765-0.5.i586.rpm novell-business-continuity-cluster-idm-1.2.1.758-0.6.noarch.rpm yast2-novell-bcc-2.13.1.741-0.6.noarch.rpm The features and changes included in the BCC1.2.1 patch are described in Section 2.2, “BCC...

  • Page 59: Installing The Bcc Patch Along With The Oes 2 Sp2 Linux Patches

    3c If you migrated cluster resources in Step 3a, migrate them back to the updated node. 3d Repeat Step 3a through Step 3c for the remaining nodes in the cluster. 4 Repeat Step 3 on one peer cluster at a time until the BCC 1.2.1 patch has been applied to each node in every peer cluster in the business continuity cluster.
  • Page 60 If you must rebuild the server to use a 64-bit platform, install OES 2 SP2 Linux on the server and apply the latest SP2 patches before you install Identity Manager 3.6.1, then skip Step 2a2 below. 2a2 Update the server to OES 2 SP2 Linux and apply the latest patches, then reboot the server if you are prompted to do so.

  • Page 61: Updating (Patching) Bcc 1.2.0 On Oes 2 Sp1 Linux

    Beginning in January 2010, patches are available for Novell Business Continuity Clustering (BCC) 1.2.0 in the Novell Open Enterprise Server (OES) 2 SP1 Linux patch channel. BCC administrators can use a rolling update approach to download and install the BCC 1.2.0 patch for each node in every peer cluster in the business continuity cluster.

  • Page 62: Installing The Bcc Patch On A Fully Patched Oes 2 Sp1 Linux Bcc Cluster

    6.2 Installing the BCC Patch on a Fully Patched OES 2 SP1 Linux BCC Cluster Use the procedure in this section to apply the BCC patch to a fully patched OES 2 SP1 Linux BCC cluster. In this scenario, it is recommended, but not required, that you migrate the cluster resources to a different node before installing the BCC patch.
  • Page 63 2 On one peer cluster, use a rolling update approach to install the BCC 1.2.0 patch: 2a On the Identity Manager node in the cluster, apply the OES 2 SP1 Linux patches, then reboot the server if you are prompted to do so. 2b On one of the nodes in the cluster, migrate its cluster resources to another node in the cluster.
  • Page 64 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 65: Upgrading The Identity Manager Nodes To Identity Manager

    Business Continuity Clustering 1.2 supports using Identity Manager 3.6.1 (32-bit and 64-bit) on Novell Open Enterprise Server (OES) 2 SP1 Linux. Updating to Identity Manager 3.6.1 is needed only for 64-bit support, or to take advantage of bug fixes that might be offered in 3.6.1.
  • Page 66 2 On a 64-bit machine, reinstall the operating system with the 64-bit OES 2 SP1 Linux, then install Identity Manager 3.6.1 and iManager 2.7.2 on the system as described in Section 4.1.7, “Identity Manager 3.6.1 Bundle Edition,” on page 3 Re-create the BCC drivers in Identity Manager. For information about creating drivers, see Chapter 9, “Configuring the Identity Manager Drivers for BCC,”...

  • Page 67: Converting Bcc Clusters From Netware To Linux

    Linux Before you can upgrade from servers running BCC 1.0 (NetWare only) or BCC 1.1 SP1 for NetWare to BCC 1.2.1 for OES 2 SP2 Linux, you must upgrade the operating system and Novell Cluster Services on each server in every cluster to NetWare 6.5 SP8 with the latest patches, then upgrade the BCC software in the clusters to BCC 1.1 SP2 for NetWare.

  • Page 68: Converting Clusters From Netware To Linux

    5 Configure the BCC Administrator user and group for the Linux cluster. On Linux, the BCC Administrator user must be Linux-enabled with Linux User Management. The user must also be added to the Novell Cluster Services administration group (such as ncsgroup) on each cluster node. Follow the steps outlined in Section 4.3, “Configuring a BCC...

  • Page 69: Deleting And Re-Creating The Bcc Identity Manager Drivers

    See “Finalizing the Cluster Conversion” in the OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide. 8.6 What’s Next After the BCC is upgraded, continue with Chapter 10, “Configuring BCC for Peer Clusters,” on...
  • Page 70 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 71: Configuring The Identity Manager Drivers For Bcc

    Configuring the Identity Manager Drivers for BCC ® Novell Business Continuity Clustering (BCC) software provides two drivers for Identity Manager that are used to synchronize cluster resources and User objects between the clusters in the business continuity cluster. After you install BCC, you must configure the Identity Manager drivers for BCC in order to properly synchronize and manage your business continuity cluster.
  • Page 72 The BCC drivers are installed and configured on the Identity Manager node in each of the peer clusters in the business continuity cluster. Each of the driver connections has a Publisher channel (sending) and a Subscriber channel (listening) for sharing information between any two peer clusters.
  • Page 73 If the clusters are in different trees, or if the User objects are in a separate eDirectory partition than Cluster objects, you also need to install an instance of the User Object Synchronization driver on a different port, as shown in Table 9-3 Table 9-4.
  • Page 74 Driver Set Summary for a Single-Tree, Three-Cluster Business Continuity Cluster Table 9-6 Driver Set for Cluster Driver Instance Driver Set for Cluster One Driver Set for Cluster Two Three Cluster Resource C1 to C2, port 2002 C2 to C1, port 2002 C3 to C1, port 2003 Cluster Resource C1 to C3, port 2003...
  • Page 75 Single-Tree Four-Cluster Driver Set Example Table 9-9 Cluster Resource Subscriber Node Publisher Node Cluster One Cluster Two Cluster Three Cluster Four Cluster One Not applicable CR, port 2002 CR, port 2003 CR, port 2004 (master node) Cluster Two CR, port 2002 Not applicable No channel No channel...

  • Page 76: Prerequisites For Configuring The Bcc Drivers For Identity Manager

    9.2 Prerequisites for Configuring the BCC Drivers for Identity Manager Section 9.2.1, “Identity Manager,” on page 76 Section 9.2.2, “Novell eDirectory,” on page 77 Section 9.2.3, “Landing Zone Container,” on page 77 9.2.1 Identity Manager Before you installed Business Continuity Clustering, you set up and configured the Identity Manager engine and an Identity Manager driver for eDirectory on one node in each cluster.

  • Page 77: Novell Edirectory

    The cluster node where Identity Manager is installed must have an eDirectory full replica with at least read/write access to all eDirectory objects that will be synchronized between clusters. For information about the full replica requirements, see Section 4.1.5, “Novell eDirectory 8.8.5,” on page 9.2.3 Landing Zone Container The landing zone that you specify for drivers must already exist.
  • Page 78 For example, specify Cluster1 BCC Driver Set, where Cluster1 is the name of the cluster where you are configuring a driver instance. 5c Browse to select the context that contains the cluster objects for the cluster where you are configuring a driver instance. For example, cluster1.clusters.siteA.example 5d Deselect (disable) the Create a new partition on this driver set option, then click Next.
  • Page 79 You must specify the same port number for the same template in the destination cluster when you set up the driver instance in that peer cluster. For example, if you specify 2003 as the port number for the resource synchronization driver instance for Cluster1 to Cluster 2, you must specify 2003 as the port number for the Cluster 2 to Cluster 1 resource synchronization driver instance for the peer driver you create on Cluster2.

  • Page 80: Creating Ssl Certificates

    Do the follow to upgrade each BCC driver set you created in “Configuring the BCC Drivers” on page 77 14a In iManager, click Identity Manager, then click Identity Manager Overview. 14b Search for the driver sets that you have added, then click the driver set link to bring up the Driver Set Overview.

  • Page 81: Synchronizing Identity Manager Drivers

    9.6 Synchronizing Identity Manager Drivers If you are adding a new cluster to an existing business continuity cluster, you must synchronize the BCC-specific Identity Manager drivers after you have created the BCC-specific Identity Manager drivers and SSL certificates. If the BCC-specific Identity Manager drivers are not synchronized, clusters cannot be enabled for business continuity.
  • Page 82 Three-Cluster Identity Manager Synchronization Loop Figure 9-1 Cluster IDM Sync Cluster Cluster Three A preferred method is to make Cluster One an Identity Manager synchronization master in which Cluster One synchronizes with Cluster Two, and Cluster Two and Cluster Three both synchronize with Cluster One.

  • Page 83: Changing The Identity Manager Synchronization Drivers

    Alternate Three-Cluster Identity Manager Synchronization Scenario Figure 9-3 Cluster IDM Sync Cluster Cluster Three In a single-tree scenario with a four-cluster business continuity cluster, Cluster One is an Identity Manager synchronization master in which Cluster One synchronizes data with each of the peer clusters, as illustrated in Figure 9-4.

  • Page 84: What's Next

    In order for a cluster to appear in the list of possible peer clusters, that cluster must have the following: Business Continuity Clustering software installed. Identity Manager installed. The BCC-specific Identity Manager drivers configured and running. Be enabled for business continuity. 9.9 What’s Next After the Identity Manager drivers for BCC are configured, you are ready to set up BCC for the clusters and cluster resources.

  • Page 85: Configuring Bcc For Peer Clusters

    Chapter 9, “Configuring the Identity Manager Drivers for BCC,” on page Preform the following tasks on each peer Novell Cluster Services cluster that you want to be part of the business continuity cluster: Section 10.1, “Enabling Clusters for Business Continuity,” on page 85 Section 10.2, “Adding Peer Cluster Credentials,”...

  • Page 86: Adding Peer Cluster Credentials

    3c For each driver, click the upper right corner of the driver icon to see if a driver is started or stopped. 3d If the driver is stopped, start it by selecting Start. 4 In Roles and Tasks, click Clusters, then click the Cluster Options link. 5 Specify a cluster name, or browse and select one.

  • Page 87: Using Imanager To Add Credentials

    When adding the administrator username, do not include the context for the user. For example, instead of bccadmin bccadmin.prv.novell Rather than using the Admin user to administer your BCC, you should consider creating another user with sufficient rights to the appropriate contexts in your eDirectory tree to manage your BCC.

  • Page 88: Adding Search-And-Replace Values To The Resource Replacement Script

    10.3 Adding Search-and-Replace Values to the Resource Replacement Script To enable a resource for business continuity, certain values (such as IP addresses) specified in resource load and unload scripts need to be changed in corresponding resources in the peer clusters. You need to add the search-and-replace strings that are used to transform cluster resource load and unload scripts from another cluster to the one where you create the replacement script.

  • Page 89: Adding Storage Management Configuration Information

    IMPORTANT: Make sure to use a trailing dot in the search-and-replace value. If a trailing dot is not used, 10.1.1 could be replaced with an IP value such as 192.168.100 instead of 192.168.1. 4 (Optional) Select the Use Regular Expressions check box to use wildcard characters in your search-and-replace values.
  • Page 90 Perl script code that you customize for your SAN can be added to a BCC-enabled cluster resource load script and unload script through the BCC management interface. You can include parameters that are passed to each Perl script. BCC passes the parameters in the format of , and so on.
  • Page 91 Edit flags This is an advanced feature, and should not be used except under the direction of Novell Support. 7c Click Apply and OK on the Script Details page, then click OK on the Resource Properties page to save your script changes.

  • Page 92: Configuring Cimom Daemons To Bind To Ip Addresses

    # The default is 0.0.0.0 http_server.listen_addresses = 0.0.0.0 For more information about managing OpenWBEM, see the OES 2: OpenWBEM Services Administration Guide (http://www.novell.com/documentation/oes2/mgmt_openwbem_lx_nw/data/ front.html). 10.6 Enabling Linux POSIX File Systems to Run on Secondary Clusters If you are using Linux POSIX* file systems in cluster resources on the clusters in your BCC and you want to migrate or fail over those file systems to peer clusters, you must add a script to convert the EVMS CSM (Cluster Segment Manager) container for the file system.

  • Page 93: Verifying Bcc Administrator User Trustee Rights And Credentials

    2 Specify your username and password, specify the tree where you want to log in, then click Login. 3 In Roles and Tasks, click Clusters, then click the Cluster Options link. 4 Specify a cluster name, or browse and select one. 5 Under Cluster Objects, select the business-continuity-enabled cluster resource that contains the Reiser or Ext3 file system, then click Details.

  • Page 94: Disabling Bcc For A Peer Cluster

    In order for the BCC Administrator user to gain access to the cluster administration files ( /admin/ ) on other Linux cluster nodes in your BCC, you must add that user to the novell/cluster on each cluster node. For instructions, see “Adding the BCC Administrator User to the ncsgroup ncsgroup on Each Cluster Node”...

  • Page 95: Managing A Business Continuity Cluster

    Managing a Business Continuity Cluster ® This section can help you effectively manage a business continuity cluster with the Novell Business Continuity Clustering software. It describes how to migrate cluster resources from one Novell Cluster Services cluster to another, to modify peer credentials for existing clusters, and to generate reports of the cluster configuration and status.

  • Page 96: Migrating Cluster Resources Between Clusters

    Migrating a pool resource to another cluster causes the following to happen: 1. If the source cluster can be contacted, the state of the resource is changed to offline. 2. The resource changes from primary to secondary on the source cluster. 3.

  • Page 97: Bringing A Downed Cluster Back In Service

    looking at the cluster itself, such as Running or Offline. If the cluster resource is not assigned to the cluster you are managing from (that is, not in the current cluster), then the status is shown as Secondary. 6 In the list of cluster, select the cluster where you want to migrate the selected resources, then click OK.

  • Page 98: Viewing The Current Status Of A Business Continuity Cluster

    6 Edit the administrator username and password that the selected cluster will use to connect to the selected peer cluster, then click OK. When specifying a username, you do not need to include the Novell eDirectory context for the user name.

  • Page 99: Generating A Cluster Report

    11.5 Generating a Cluster Report You can generate a report for each cluster in the business continuity cluster to list information on a specific cluster, such as current cluster configuration, cluster nodes, and cluster resources. You can print or save the report by using your browser. 1 Start your Internet browser and enter the URL for iManager.
  • Page 100 Primary Cluster Fails but Primary Storage System Does Not This type of failure can be temporary (transient) or long-term. There should be an initial response and then a long-term response based on whether the failure is transient or long term. The initial response is to BCC migrate the resources to a peer cluster.

  • Page 101: Host-Based Mirroring Failure Types And Responses

    Intersite Storage System Connectivity Is Lost Recover the connection. If divergence of the storage systems occurred, remirror from the good side to the bad side. Intersite LAN Connectivity Is Lost User connectivity might be lost to a given service or data, depending on where the resources are running and whether multiple clusters run the same service.
  • Page 102 Secondary Cluster and Secondary Storage System Both Fail Secondary clusters are not currently running the resource. Bring up your secondary storage system before bringing up your cluster servers. Then run the command Cluster Scan For New Devices on a primary cluster server to ensure remirroring takes place. When you bring the secondary cluster back up, the storage system is still secondary to the primary cluster.

  • Page 103: Configuring Bcc For Cluster Resources

    Cluster Services clusters for a business continuity cluster by using Novell Business Continuity Clustering software, you are ready to configure the cluster resources for BCC. You can enable one or multiple cluster resources in each of the peer clusters for business continuity that if you want to be able to fail over between peer clusters.

  • Page 104: Shared Disk Cluster Resources

    The clusters in the other eDirectory tree cannot decrypt the NSS volumes. 12.1.3 Shared Disk Cluster Resources Table 12-1 for resources that explain how to create shared disk cluster resources on Novell Open Enterprise Server 2 Linux servers: Shared Disk Cluster Resources on OES 2 Linux Servers...

  • Page 105: Configuring Search-And-Replace Values For An Individual Cluster Resource

    Section 10.3, “Adding Search-and-Replace Values to the Resource Replacement Script,” on page Before you create a replacement script for an individual resource, you should contact Novell Support. The search-and-replace data that you add is resource-specific, and it is not synchronized via Identity Manager between the clusters in the business continuity cluster.

  • Page 106: Assigning Preferred Peer Clusters For The Resource

    The search-and-replace values you specify here apply to only to the resource you are enabling for business continuity. If you want the search-and-replace values to apply to any or all cluster resources, add them to the entire cluster instead of just to a specific resource. IMPORTANT: If you change the resource-specific search-and-replace data after initially adding it, you must update the resource load script and unload script in one of the peer clusters by editing it and adding a space or a comment to it.

  • Page 107: Assigning Preferred Nodes In Peer Clusters

    Cluster Resource New or Existing Action NSS pool Existing Add the storage management configuration information. For information, see “Adding Storage Management Configuration Information” on page 3 After the cluster resource information is synchronized to all of the peer clusters in the resource’s Assigned clusters list, you must specify your node preferences separately for each of the peer clusters.

  • Page 108: Disabling Bcc For A Cluster Resource

    12.6 Disabling BCC for a Cluster Resource After enabling a resource for business continuity, it is possible to disable it. You might want to disable BCC for a cluster resource in any of the following cases: You accidentally enabled the resource for business continuity. You no longer want the cluster resource to be able to fail over between peer clusters.

  • Page 109: Changing The Ip Address Of A Cluster Resource

    8 On the Details page, click the Business Continuity tab, deselect the Enable Business Continuity Features check box, then click Apply. 9 Wait for Identity Manager to synchronize the changes. This could take from 30 seconds to one minute, depending on your configuration. 10 Delete the Cluster Resource object on the clusters where you no longer want the resource to run.
  • Page 110 Wait for Identity Manager to synchronize the change to all peer clusters before continuing. You can check the other peer clusters to make sure that the cluster resource you BCC-disabled no longer appears in their list of resources. 5 Select Clusters > Cluster Options, select the shared NSS pool, then select Offline. WARNING: If you attempt to delete a cluster resource without first offlining it, deletion errors occur, and the data associated with the clustered pool is not recoverable.

  • Page 111: Troubleshooting Business Continuity Clustering

    Troubleshooting Business Continuity Clustering ® This section contains the following topics to help you troubleshoot Novell Business Continuity Clustering 1.2.1 for Novell Open Enterprise Server (OES) 2 SP2 Linux. Section 13.1, “NSS Takes Up to 10 Minutes to Load When the Server Is Rebooted,” on page 112 Section 13.2, “Identity Manager Plug-Ins Do Not Appear in iManager,”...

  • Page 112: Nss Takes Up To 10 Minutes To Load When The Server Is Rebooted

    13.1 NSS Takes Up to 10 Minutes to Load When the Server Is Rebooted In some environments, a timing problem prevents the NDP user space application ( ) from ndpapp loading, and in turn, NSS cannot be loaded until the problem resolves itself. You can increase the UDEV event handling limits to 1024 to circumvent this problem.

  • Page 113: Driver Port Number Conflicts

    Ping the peer cluster to see if it is up to the selected peer cluster. and reachable. Ensure that Novell Cluster Services is running on the servers in the peer cluster, then ensure that BCC is running on the peer clusters.

  • Page 114: Excluded Users

    7 In the Authentication context field, view and if necessary change the port numbers next to the IP address. For example, the Authentication context field might contain a value similar to 10.1.1.12:2003:2003. In this example, the first port number (2003) is the port number for the corresponding Identity Manager driver on the cluster that this cluster is synchronizing with.

  • Page 115: Ssl Certificates

    BCC. For Linux, ensure that the BCC Administrator user is a LUM-enabled user. To LUM-enable a user, “Managing User and Group Objects in eDirectory” (http://www.novell.com/documentation/oes/ lumadgd/data/aeucqum.html) in the Novell Linux User Management Technology Guide.

  • Page 116: Clusters Cannot Communicate

    Turns on tracing. With tracing turned on, certain sections of code that fail will report a message containing the condition that failed along with a file and line number in the code indicating where the condition failed. This is helpful for reporting problems to Novell Support.

  • Page 117: Identity Manager Drivers For Cluster Synchronization Do Not Start

    13.10 Identity Manager Drivers for Cluster Synchronization Do Not Start If the Identity Manager drivers for cluster synchronization do not start, the problem might be caused by one of the following conditions: A certificate has not been created. For information, see “Creating SSL Certificates”...

  • Page 118: Tracing Identity Manager Communications

    (both drivers). For information about setting trace levels for driver sets, see “Adding Trace Levels in iManager” (http://www.novell.com/documentation/idm36/idm_common_driver/data/b1rc6ea.html). For information about using , see “Using ndstrace” (http://www.novell.com/ ndstrace documentation/edir88/edir88tshoot/data/bq0gvax.html) in the Novell eDirectory 8.8 Troubleshooting Guide (http://www.novell.com/documentation/edir88/edir88tshoot/data/ front.html).

  • Page 119: Peer Cluster Communication Is Not Working

    On the resource object, change the NCS:BCC State attribute to 0 to set the resource to the primary state. Also, increment the NCS:Revision attribute one number so that Novell Cluster Services recognizes that the resource properties have been updated. See...

  • Page 120: Administration Of Peer Clusters Is Not Functional

    For information, see “Moving a Cluster, or Changing IP Addresses, LDAP Server, or Administrator Credentials for a Cluster” in the OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide. The virtual server has an extra IP address. IP address changes should always be made on the Protocols page of the iManager cluster plug- in, not in load and unload scripts.

  • Page 121: The Ip Address, Virtual Server Dn, Or Pool Name Does Not Appear On The Imanager Cluster Configuration Page

    If you get an error in iManager with a blank error string (no text appears with the error message) while attempting to bring a resource online, it is possible that Novell Cluster Services views the resource as secondary even though BCC has changed the resource to primary and iManager shows the resource as primary.

  • Page 122: Mapping Drives To Home Directories By Using The %Home_Directory Variable

    SLP Server Name is the name being advertised in SLP as specified in the resource load script. This method requires a client reboot. TID 10057730 (http://support.novell.com/docs/Tids/Solutions/10057730.html) information on modifying the server cache Time To Live (TTL) value on the Novell Client 13.22 Mapping Drives to Home Directories by Using the %HOME_DIRECTORY Variable Consider the following when mapping drives in login scripts in a BCC.

  • Page 123: Bcc Error Codes

    Error returned from the NICI API. 1016 Cannot find peer cluster data. 1017 Invalid BCC API version. 1018 Could not find a pool for the specified cluster resource. 1019 Error managing the SAN via the Novell SAN Management Interface. Troubleshooting Business Continuity Clustering 123...

  • Page 124: Clustered Pool Is Stuck In An Edirectory Synchronization State

    Error Code Number Message 1020 CIM Client error. 1021 Error creating a system resource (mutex, semaphore, etc.). 1022 File IO error. 1023 No data. 1024 Not a member of the cluster. 1025 Invalid token in the script. 1026 Invalid or unknown cluster. 1027 The NSMI script is too long.

  • Page 125: Security Considerations

    Section 14.3, “General Security Guidelines,” on page 130 Section 14.4, “Security Information for Dependent Products,” on page 130 14.1 Security Features ® The following table contains a summary of the security features of Novell Business Continuity Clustering 1.2: Business Continuity Clustering 1.2 or Later Security Features...

  • Page 126: Security Configuration

    14.2 Security Configuration This section provides a summary of security-related configuration settings for Business Continuity Clustering 1.2. Section 14.2.1, “BCC Configuration Settings,” on page 126 Section 14.2.2, “Changing the NCS: BCC Settings Attributes in the BCC XML Configuration,” on page 127 Section 14.2.3, “Disabling SSL for Inter-Cluster Communication,”...

  • Page 127: Changing The Ncs: Bcc Settings Attributes In The Bcc Xml Configuration

    XML Configuration WARNING: You should not change the configuration settings for the NCS:BCC Settings attribute unless instructed to do so by Novell Support. Doing so can have adverse affects on your cluster nodes and BCC. The following XML for the NCS:BCC Settings attribute is saved on the local Cluster object in eDirectory.

  • Page 128: Disabling Ssl For Inter-Cluster Communication

    To turn off SSL for inter-cluster communication, or to specify a different communication port, you need to modify the Novell Cluster Services Cluster object that is stored in eDirectory by using an ®...
  • Page 129 Disabling SSL communication to a specific peer cluster requires changing the BCC management address to the peer cluster. The address is contained in the NCS:BCC Peers attribute that is stored on the NCS Cluster object. For example, a default NCS:BCC Peers attribute could appear similar to the following example where https:// is assumed and is never specified explicitly: <peer>...

  • Page 130: Restricting The Network Address For Administration

    Value Protocol Used Port Used 10.1.1.10:1234 HTTPS 1234 http://10.1.1.10 HTTP 5988 http://10.1.1.10:1234 HTTP 1234 14.2.4 Restricting the Network Address for Administration You can restrict the network address to the loopback address (127.0.0.1) to increase the security for the BCC Administrator user (bccadmin). BCC makes a secure connection to OpenWBEM over port 5989 on both the remote and local boxes.
  • Page 131 Linux User Management (LUM) OES 2 SP2: Novell Linux User Management Technology Guide. Novell Cluster Services for Linux In the OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide, see “Configuration Requirements” “Assigning Install Rights for Container Administrators”...
  • Page 132 132 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 133: A Console Commands For Bcc

    ® Novell Business Continuity Clustering (BCC) provides server console commands to help you perform certain BCC management tasks. Some of the commands can also be used to manage Novell Cluster Services clusters. IMPORTANT: For Novell Cluster Services console commands, see “Console Commands for...
  • Page 134 Console Command Description Disables BCC for the specified cluster resource. The cluster disable [resource] resource you specify must belong to a cluster that has already been enabled for BCC. If no resource is specified, the entire cluster is disabled for BCC. IMPORTANT: Before you disable BCC for a given peer cluster, you must first disable BCC for each of the cluster resources running on that cluster.
  • Page 135 Output is sent to the system log. cluster refresh This command should not be used except under the direction of Novell Support. cluster resetresources Changes the state of all resources on this cluster to offline and secondary. This is a recovery procedure that should be run when a peer cluster in a business continuity cluster is brought back into service.

  • Page 136: Setting Up Linux Scan Commands In /Opt/Novell/Ncs/Bin/Device_Scan.sh

    By default, the scripts is empty so that administrators can add the Linux shell commands they need to refresh their systems. Any changes that are made to the script are not overwritten when Novell Cluster Services is upgraded. 1 In a text editor, open the script file , add the Linux /opt/novell/ncs/bin/device_scan.sh...

  • Page 137: B Setting Up Auto-Failover

    Setting Up Auto-Failover ® Auto-failover is available beginning in Novell Business Continuity Clustering 1.1. To set up the auto-failover feature, you must enable it, then configure the auto-failover settings. WARNING: Auto-failover is disabled by default and is not recommended. It should only be enabled after a thorough examination and review of your network and geographic site infrastructure.

  • Page 138: Creating An Auto-Failover Policy

    8 Click the Auto-Failover link just under the tabs. 9 Select the Enable Automatic Failover of Business Continuity Cluster Resources check box, then click Apply. 10 Continue with Section B.2, “Creating an Auto-Failover Policy,” on page 138 to create a failover policy.
  • Page 139 These conditions can be combined in any order to construct a more robust rule that helps to avoid an undesired failover. For failover to occur, each condition of only one rule must be satisfied for the specified cluster or clusters. For rules with monitor conditions that are automatically created by using the Cluster Membership Monitoring Settings table, you can add a condition that tests if the connection to the peer cluster is up.

  • Page 140: Adding Or Editing Monitor Configurations

    The nodepnt and nodecnt monitors do not support optional parameters. 6 Click Apply to save your settings. NOTE: See the BCC NDK documentation (http://developer.novell.com/documentation/cluster/ index.html?page=/documentation/cluster/ncss_enu/data/bktitle.html) for more information on creating custom failover policies. 140 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 141: C Configuring Host-Based File System Mirroring For Nss Pools

    For information about storage-based mirroring, consult your storage system vendor or see the storage system vendor documentation. Host-based synchronous mirroring functionality is included with the Novell Storage Services file system (NSS mirroring) that is part of OES 2 SP1 Linux. NSS mirroring is a checkpoint-based synchronous mirroring solution.

  • Page 142: Creating And Mirroring Nss Pools On Shared Storage

    OES 2 SP2: NSS File System Administration Guide. Novell CIFS for Linux and Novell AFP for Linux are available in OES 2 SP1 Linux and later. If you plan to mark CIFS or AFP as an advertising protocol for the NSS pool resource, make sure these protocols are installed and running when you create the pool resource.
  • Page 143 (NetWare Core Protocol ) is used by NSS to enforce the Novell trustee model of file access for all users of the data, and also as an advertising protocol for NCP clients. Selecting NCP causes commands to be added to the pool resource load and unload scripts to activate the NCP protocol on the cluster.

  • Page 144: Creating Nss Volumes

    C.4 Checking NSS Volume Mirror Status After you have configured NSS mirroring with Novell Cluster Services , you should check to ensure that it is working properly in a cluster environment.
  • Page 145 IMPORTANT: If you create or delete a pool or partition on shared storage that is part of a business continuity cluster, you must run the command on a server in cluster scan for new devices each of the peer clusters. Configuring Host-Based File System Mirroring for NSS Pools 145...
  • Page 146 146 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 147: D Configuration Worksheet For The Bcc Drivers For Identity Manager

    Configuration Worksheet for the BCC Drivers for Identity Manager ® Use this worksheet to gather the information you need to configure the Novell Business Continuity Clustering 1.2.1 drivers for Identity Manager. Repeat this process for each connection between clusters. For information about how to set up the drivers, see Chapter 9, “Configuring the Identity...
  • Page 148 Driver Set Information Value Create a new partition on this driver set Deselect this option. Driver Instance for the Connection from Source to Destination Driver Set Information Value Pre-configured driver template to import (pick one): BCCClusterResourceSynchronization.xml UserObjectSynchronization.xml TIP: The User Object Synchronization driver is needed only when creating a driver instance for communications between clusters in different trees.

  • Page 149: Cluster2 To Cluster1

    Driver Set Information Value Landing zone for this driver instance Specify the distinguished name of the container where the cluster-enabled pool, NCP server, and volume objects for the destination cluster will be placed when they are synchronized to the source cluster for this driver instance.
  • Page 150 Driver Set Information Value Create a new partition on this driver set Deselect this option. Driver Instance for the Connection from Source to Destination Driver Set Information Value Preconfigured driver template to import (pick the same one that you selected for the Cluster1-to- Cluster2 synchronization): BCCClusterResourceSynchronization.xml UserObjectSynchronization.xml...
  • Page 151 Driver Set Information Value Distinguished name of the source cluster for this driver instance Example: cluster2.clusters.siteB.example TIP: Browse to select the cluster. Landing zone for this driver instance Specify the distinguished name of the container where the cluster-enabled pool, NCP server, and volume objects for the destination cluster will be placed when they are synchronized to the source cluster for this driver instance.
  • Page 152 152 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 153: Requirements And Assumptions

    ® resources to use a different IP address range. In Novell Business Continuity Cluster (BCC) 1.2 or later, you can configure BCC to act as a dynamic DNS (Domain Name System) client.

  • Page 154: Tsig Keys

    Another option for your DNS servers is to put them in your Novell Cluster Services cluster. This creates a DNS service that is extremely resilient to failure. For information, see “Configuring DNS with Novell Cluster Services” in the OES 2 SP2: Novell DNS/DHCP Administration Guide for Linux.

  • Page 155: Configuring The Dns Server With The Public Key

    Replace cluster_dns_name with the name of the host. For BCC, the cluster node that hosts the Novell Cluster Services Master IP Address resource updates the DNS server. Because this can be any node in the cluster, use the fully qualified name of the cluster as the host name.

  • Page 156: Configuring The Dns Server Zones

    To continue our example, the key section for the file might look /var/lib/named/keys.conf like this: key cluster1.clusters.site1.company.com. { algorithm HMAC-MD5; secret "SCUT8rIUoGByvcI1Iok7tY7YvcEaHaM3zusCxXmboBxVcJvUxr335HCg lXcDQRPrJrzIKQhH4dJ4cY10ebOJFw=="; 5 Save the file. 6 Continue with Section E.2.3, “Configuring the DNS Server Zones,” on page 156. E.2.3 Configuring the DNS Server Zones To configure the DNS zones to accept authorized DNS updates: 1 On the DNS server, open a terminal console, then log in as the...
  • Page 157 Test Equipment Sample Value DNS Server IP address 10.1.1.172 Linux client computer wkstn1.clusters.site1.company.com FTP server (testing to see its IP address) 10.1.1.215 ftp.clusters.site1.company.com For example, enter: dig #10.1.1.172 ftp.clusters.site1.company.com The output shows that the IP address for ftp.clusters.site1.company.com is 10.1.1.215: ;...
  • Page 158 ; <<>> DiG 9.3.2 <<>> @10.1.1.172 -x 10.1.1.215 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34957 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;;...
  • Page 159 nsupdate -v -k /home/yourhomedir/ Kcluster1.clusters.site1.company.com.+157+60303.private > server 10.1.1.172 53 > update delete 215.1.1.10.in-addr.arpa PTR > update add 216.1.1.10.in-addr.arpa 300 PTR ftp.clusters.site1.company.com > show Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: ;; flags: ; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;;...
  • Page 160 8b Use the dig utility with the IP address to find the DNS name. dig @10.1.1.172 -x 10.1.1.216 ; <<>> DiG 9.3.2 <<>> @10.1.1.172 -x 10.1.1.216 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14497 ;;...

  • Page 161: Configuring The Cluster Resources For Dynamic Dns

    E.3 Configuring the Cluster Resources for Dynamic DNS After the DNS server is configured for dynamic DNS, you must configure each of the BCC-enabled cluster resources to take advantage of it. You modify the BCC load scripts for each of the cluster resources so that the script automatically updates the DNS server with the correct IP address of the given resource during a BCC migration to a peer cluster.
  • Page 162 6 Specify the following settings for the script: Parameter Description CIM-Enabled Used for CIM (Common Information Model) and SMI-S (Storage Management Initiative Specification) enabled scripts that manage a physical SAN. These are not used for the dynamic DNS script. Deselect the check box. After this check box is deselected, the CIMON IP/ DNS, Namespace, Port, Secure, Username, and Password controls are all disabled.
  • Page 163 Edit Flags This is an advanced option that should only be enabled when instructed to do so by Novell Support, so leave it disabled (deselected). 7 Specify the Script Parameters. Click New to insert a new editable row into the Script Parameters table. The left field is the parameter name and the right field is the parameter value.

  • Page 164: Public And Private Keys

    E.3.2 Public and Private Keys The BCC load and unload scripts always run on the node that is hosting the Novell Cluster Services master resource (that is, the Master_IP_Address_Resource). This resource can be hosted on any node in the Novell Cluster Services cluster, which means the BCC load and unload scripts can also be executed on any node in the cluster.

  • Page 165: Testing The Dynamic Dns Solution

    2 Open the copy of the script in a text editor, then modify the BCC variables by modifying lines 62 – 66 of the script. The uppercase string surrounded by the percent character ( % ) is the BCC variable and should be replaced with the real value (such as %DNS_SERVER_ADDR%).
  • Page 166 166 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 167: Understanding Internal Virtual Ip Networks

    ® resources to use a different IP address range. In Novell Business Continuity Cluster (BCC) 1.2 or later, you can configure BCC to use virtual IP addresses for BCC-enabled resources as an alternate approach to assigning secondary IP addresses to resources.

  • Page 168: Virtual Ip Address Benefits

    F.2 Virtual IP Address Benefits In spite of their simplicity, virtual IP addresses offer the following advantages over their physical counterparts: Improves availability. The virtual IP addresses are bound to virtual adapters instead of physical adapters. The host mask for the virtual adapter allows each cluster resource to have its own entry in the routing tables.

  • Page 169: Unlimited Mobility

    F.2.2 Unlimited Mobility Unlike physical IP addresses which are limited in their mobility, virtual IP addresses are highly mobile. The degree of mobility is determined by the number of servers that an IP address on a specific server could be moved to. In other words, if you choose a physical IP address as an IP address of a network resource, you are limiting the set of potential servers to which this resource could be transparently failed-over.

  • Page 170: Routing Protocol

    Section F.3.4, “IP Addresses for BCC-Enabled Cluster Resources,” on page 170 Section F.3.5, “Host Mask,” on page 171 F.3.1 Routing Protocol In theory, any state-of-the-art routing protocol could be used for the virtual IP network. This section describes how to set up the virtual router using the OSPF (Open Shortest Path First) routing protocol because it is a commonly used protocol.

  • Page 171: Host Mask

    IP network whose route is being advertised by a single node within a cluster. Because Novell Cluster Services™ can migrate a service and its virtual IP address from one node to another, the virtual IP network must migrate to the same node as the service. If multiple virtual IP...

  • Page 172: Configuring Virtual Ip Addresses

    IP address information for the dummy0 adapter. For example, the old and new lines are emphasized in the following sample load script: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs exit_on_error nss /poolact=POOL1 exit_on_error ncpcon mount TVOL1=101 ###exit_on_error add_secondary_ipaddress 10.10.0.101 exit_on_error ip addr add 10.50.0.101/32 dev dummy0 exit_on_error ncpcon bind --ncpservername=CL1-POOL1-VS -- ipaddress=10.50.0.101...
  • Page 173 5 To verify that a virtual IP address is bound, enter at a display secondary ipaddress terminal console of the cluster node where the virtual IP address is assigned. This displays all bound virtual IP addresses. 6 Repeat the previous steps for the remaining cluster resources. Using Virtual IP Addresses with BCC 1.2 173...
  • Page 174 174 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 175: G Removing Business Continuity Clustering Core Software

    Removing Business Continuity Clustering Core Software ® If you need to uninstall Novell Business Continuity Clustering, you can do so by using the Business Continuity Clustering installation program. 1 Log in as the user on the server. root 2 Use one of the following methods to open the BCC Configuration page: In YaST, select Miscellaneous >...
  • Page 176 176 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

  • Page 177: H Documentation Updates

    Documentation Updates ® This section contains information about documentation content changes made to the Novell Business Continuity Clustering 1.2x Administration Guide for Linux since the initial 1.2 release. If you are an existing user, review the change entries to readily identify modified content. If you are a new user, simply read the guide in its current state.

  • Page 178: February 7, 2010 (Bcc 1.2.1 Patch For Oes 2 Sp2 Linux)

    H.2 February 7, 2010 (BCC 1.2.1 Patch for OES 2 SP2 Linux) This guide was updated for the BCC 1.2.1 release for Novell Open Enterprise Server (OES) 2 SP2 Linux. Additions were made to the following sections. The changes are explained below.

  • Page 179: What's New For Bcc 1.2

    H.3.2 What’s New for BCC 1.2 Location Change Section 2.3, “BCC 1.2.0 This section is new. Patch (January 2010),” on A patch for BCC 1.2 for OES 2 SP1 Linux is available in the OES 2 SP1 page 26 patch channel. H.4 January 7, 2010 Updates were made to the following sections.

  • Page 180: Console Commands For Bcc

    H.4.2 Console Commands for BCC Location Change Section A.2, “Setting Up This section is new. Linux Scan Commands in / opt/novell/ncs/bin/ device_scan.sh,” on page 136 H.4.3 Installing Business Continuity Clustering Location Change “Identity Manager Engine Each Identity Manager node must be online in its peer cluster and Identity and eDirectory Driver”...

  • Page 181: Upgrading Identity Manager Nodes To Identity Manager 3.6.1

    H.4.7 Upgrading Identity Manager Nodes to Identity Manager 3.6.1 Location Change Section 7.1, “Upgrading to It is not necessary to re-create the BCC drivers if you perform an in-place 32-Bit Identity Manager upgrade of 32-bit Identity Manager 3.6 to 32-bit Identity Manager 3.6.1. 3.6.1,”...

  • Page 182: August 14, 2009

    Section H.6.4, “What’s New for BCC 1.2,” on page 182 H.6.1 Console Commands for BCC Location Change Appendix A, “Console Updated to add a link to Novell Cluster Services console commands. Commands for BCC,” on page 133 H.6.2 Installing Business Continuity Clustering Location Change Section 4.1.7, “Identity...

  • Page 183: Converting Bcc Clusters From Netware To Linux

    H.7.1 Converting BCC Clusters from NetWare to Linux Location Change Chapter 8, “Converting BCC Updated for clarity. Clusters from NetWare to Linux,” on page 67 Chapter 8, “Converting BCC Updated for clarity. Clusters from NetWare to Linux,” on page 67 H.8 April 28, 2009 Updates were made to the following sections.
  • Page 184 184 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux...

Table of Contents