The BCC management address of
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
<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 cluster 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 by a restart of the
Business Continuity Clustering software on each cluster node.
Table C-4
provides an example of possible combinations of scheme and port specifier for the
tag for values of the NCS:BCC Peers attribute:
<address>
Example of Scheme and Port Specifier Values for the NCS:BCC Peers Attribute
Table C-4
Value
10.1.1.10
10.1.1.10:1234
http://10.1.1.10
http://10.1.1.10:1234
https://10.1.1.10
https://10.1.1.10:1234
C.2.2 Security Information for Other Products
Table C-5
provides links to security-related information for other products that impact the security
of BCC:
now specifies non-secure HTTP
chicago_cluster
attribute value in the above examples to:
<address>
Protocol Used
HTTPS
HTTPS
HTTP
HTTP
HTTPS
HTTPS
Port Used
5989
1234
5988
1234
5989
1234
Security Considerations
93
Need help?
Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR NOVELL OPEN ENTERPRISE SERVER 1 SP2 LINUX and is the answer not in the manual?