62
BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8
no
vd
ocx
(e
n)
13
Ma
y 20
09
5
On the Identity Manager node in the cluster, upgrade Identity Manager from version 2.
x
to
3.51.
For information, see
“Upgrading” (http://www.novell.com/documentation/idm35/install/data/
ampxjxi.html)
in the
Identity Manager 3.5.1 Installation Guide
.
5a
Before you begin, make sure that the Identity Manager node meets the 3.5.1 upgrade
requirements.
5b
Upgrade Identity Manager from version 2.
x
to 3.51.
IMPORTANT:
Do not start the drivers yet.
The upgrade updates the Identity Manager software and its plug-ins for iManager 2.7.2 on
the same node.
5c
Stop Tomcat 5 by issuing
tc5stop
command.
5d
Reset Apache 2 by using the
ap2webrs
command.
5e
Start Tomcat 5 by using the
tomcat
command.
5f
Wait at least 5 minutes for the iManager changes to take effect, then restart iManager.
5g
In iManager, verify that
Identity Manager
is available.
IMPORTANT:
In iManager, the Identity Manager plug-ins are displayed as version 3.6.
The 3.6 version functions properly with Identity Manager 3.5.1.
6
Issue the
cluster join
command on each node in the cluster.
7
Issue the
ldbcc.ncf
command on each node to have them join the BCC.
8
Repeat
Step 3
through
Step 7
for each peer cluster.
9
Verify that Novell Cluster Services and Business Continuity Clustering appear to be
functioning correctly by migrating a BCC enabled resource between peer clusters.
10
Create the new BCC driver sets for Identity Manager.
11
On the Identity Manager node in every peer cluster, create the new Identity Manager drivers
with the new BCC 1.1 SP2 templates.
IMPORTANT:
Do not create a new partition when creating the driver set.
As a guide, you can use the information from
Step 1
and
Step 5b
in
Section 5.3.1, “Upgrading
the BCC Cluster from 1.0 to 1.1 SP1,” on page 58
.
12
Start the new Identity Manager drivers for each peer cluster.
13
Verify that Novell Cluster Services and BCC 1.1 SP2 appear to be functioning correctly by
performing the following tests:
13a
Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and
verify that it migrates correctly.
13b
Make a load script change (for example, add a space character and save the change) to an
existing BCC resource that was created with 1.0, allow the revised load script to
synchronize, then verify that the load script was updated at all eDirectory locations.
13c
BCC migrate the pool resource that you modified in
Step 13b
between peer clusters, and
verify that it migrates correctly and that the Identity Manager drivers are synchronizing.
13d
Check all SAN scripts ensure that they will perform the desired functions.
Summary of Contents for BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION
Page 4: ...4 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 10: ...10 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 26: ...26 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 36: ...36 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 54: ...54 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 82: ...82 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 92: ...92 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 122: ...122 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...
Page 126: ...126 BCC 1 1 SP2 Administration Guide for NetWare 6 5 SP8 novdocx en 13 May 2009...