Configuring The Cluster Resources For Dynamic Dns; Modifying The Bcc Load Script - Novell BUSINESS CONTINUITY CLUSTERING 1.2 - ADMINISTRATION Administration Manual

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.
IMPORTANT: In each of the peer clusters, the keys and the BCC load script for each resource will
differ. You assign the resource an IP address that is consistent with the subnet into which the BCC-
enabled cluster resource is being migrated or failed over. This allows the DNS server to be updated
when the resource fails over from the primary cluster to the secondary cluster. The same thing needs
to be done on the primary cluster so the DNS server is automatically updated on failback from the
secondary cluster to the primary cluster. You must perform these steps for every BCC-enabled
resource in the business continuity cluster.
The BCC load and unload scripts for BCC-enabled cluster resources are used to automate any tasks
that need to occur when the resource is failed over to a peer cluster. For example, during a BCC
migration, the BCC scripts manage the storage and update eDirectory
on Perl, which means that you need to create Perl-based wrappers for the
commands before placing them in the BCC load script. Typically, the line for the nsupdate utility
would be the last command to run in the script, but this might not be true for all environments.
Section E.3.1, "Modifying the BCC Load Script," on page 157
Section E.3.2, "Public and Private Keys," on page 160
Section E.3.3, "Testing the Perl Wrapper Script," on page 160
E.3.1 Modifying the BCC Load Script
For your convenience, the
the
<media>/nsmi_scripts/linux
nsupdate utility. You can add the script to the BCC load script without modifications.
NOTE: The
bcc_dyn_dns.pl
because the interpreter does not understand the variables used in lines 62–66 of the script. If you
need to test the script outside of the BCC environment, substitute values for the variables. Put the
variables back in before using the script in BCC.
1 Open iManager, then log in as the BCC Administrator user.
2 In Roles and Tasks, select Clusters > Cluster Options.
3 Select the Cluster object of the secondary peer cluster in the business continuity cluster
environment for the cluster resource. (That is, choose a peer cluster where the resource is not
currently assigned and running.)
4 Click the name link of the BCC-enabled resource where you want to add dynamic DNS
support.
This opens the Properties page for the selected resource.
5 Select the Business Continuity tab, click SAN Management, then click New in the BCC Load
Script table.
NSMI script is included in the BCC 1.2 ISO image in
bcc_dyn_dns.pl
directory. This is the script you need as the wrapper for the
NSMI script cannot be executed directly by a Perl interpreter
. The BCC scripts are based
TM
utility
nsupdate
Using Dynamic DNS with BCC 1.2 157