Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION, Руководство администратора

Страница: 129 / 184

Security Considerations 129
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
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>
<cluster>chicago_cluster</cluster>
<tree>DIGITALAIRLINES_TREE</tree>
<address>10.1.1.10</address>
</peer>
To disable SSL for inter-cluster communication, you would change the <address> attribute to
specify http:// with the IP address, as shown in the following example:
<peer>
<cluster>chicago_cluster</cluster>
<tree>DIGITALAIRLINES_TREE</tree>
<address>http://10.1.1.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 from port 5989 to
port 1234, you would change the
<address>
attribute value in the above examples to:
<peer>
<cluster>chicago_cluster</cluster>
<tree>DIGITALAIRLINES_TREE</tree>
<address>10.1.1.10:1234</address>
</peer>
The attribute now specifies that inter-cluster communication uses 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 clusters by the BCC-specific Identity Manager driver, so a change to an
attribute value on one cluster causes that attribute value to be synchronized to each peer cluster in
the BCC.
The changes do not take effect until either a reboot of each cluster node, or a restart of the Business
Continuity Clustering software on each cluster node.
Table 14-4 provides an example of possible combinations of scheme and port specifier for the
<address>
tag for values of the NCS:BCC Peers attribute:
Table 14-4
Example of Scheme and Port Specifier Values for the NCS:BCC Peers Attribute
Value Protocol Used Port Used
10.1.1.10 HTTPS 5989