94
Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
Disabling SSL for Inter-Cluster Communication
Disabling SSL for inter-cluster communication should only be done for debugging purposes, and
should not be done in a production environment or for an extended period of time.
To turn off SSL for inter-cluster communication, or to specify adifferent communication port, you
need to modify the NCS cluster object that is stored in eDirectory using an eDirectory management
tool such as iManager or ConsoleOne. See the
Novell iManager 2.5 Administration Guide
for
information on using iManager.
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 sample:
<peer><cluster>chicago_cluster</cluster><tree>DIGITALAIRLINES-TREE</
tree><address>123.45.78.10</address></peer>
To disable SSL for intercluster communication, you would change the attribute to the following:
<peer><cluster>chicago_cluster</cluster><tree>DIGITALAIRLINES-TREE</
tree><address>http://123.45.78.10</address></peer>
The BCC management address of 'chicago_cluster' now specifies non-secure http communication.
The BCC management port can also be changed by modifying the NCS:BCC Peers attribute values.
The default ports for secure and non-secure inter-cluster communication are 5989 and 5988
respectively.
For example, if you want to change the secure port on which OpenWBEM listens to 1234, you
would change the attribute value in the above example to:
<peer><cluster>chicago_cluster</cluster><tree>DIGITALAIRLINES-TREE</
tree><address>123.45.78.10:1234</address></peer>
The attribute now specifies that inter-cluster communication will use https over port number 1234.
The 'NCS:BCC Peers' attribute has a value for each peer cluster in the BCC. Attribute values are
synchronized among peer cluster by the BCC IDM driver, so a change to an attribute value on one
cluster will cause that attribute value to be synchronized to each peer cluster in the BCC.
The changes will not take effect until either a reboot of each cluster node, or by a restart of BCC
software on each cluster node.
The following table provides an example of possible combinations of scheme and port specifier for
the <address> tag for values of the NCS:BCC Peers attribute:
<resourceOnlineTimeout>
The number of seconds BCC will wait for a
resource to go online during a BCC migrate.
300
<scanForNewDevicesDelay>
The number of seconds BCC sleeps after
performing a "Scan for new Devices" during a
BCC migrate of a resource.
5
Setting
Description
Default Value
