Driver Port Number Conflicts - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

BCC Connection State
Cannot Connect
Not Authorized
Connection Unknown

13.4 Driver Port Number Conflicts

If your Identity Manager driver or drivers will not start, check for a port number conflict. Identity
Manager driver port numbers must not be the same as other driver port numbers in the cluster or
ports being used by other services such as Apache.
To check driver port numbers:
1 Start your Internet browser and enter the URL for iManager.
The URL is http://server_ip_address/nps/iManager.html. Replace server_ip_address with the
IP address or DNS name of the server that has iManager and the Identity Manager
preconfigured templates for iManager installed.
2 Specify your username and password, specify the tree where you want to log in, then click
Login.
3 In Roles and Tasks, click Identity Manager, then click the Identity Manager Overview link.
4 Select Search Entire Tree, then click Search.
5 Select the driver you want to check by clicking the red Cluster Sync icon or the blue User Sync
icon.
6 Click the red or blue icon again, then click the Identity Manager tab (if it is not already
selected).
Number Description
3 This cluster cannot connect
to the selected peer cluster.
4 The connected user does not
have sufficient rights for
permissions.
5 The connection state
between clusters is
unknown.
Possible Actions
Ping the peer cluster to see if it is up
and reachable.
Ensure that Novell Cluster Services
is running on the servers in the peer
cluster, then ensure that BCC is
running on the peer clusters.
Ensure that OpenWBEM is running
on the peer cluster.
Ensure that a firewall is not
preventing access on OpenWBEM
ports 5988 and 5989.
Ensure that the Admin file system is
running. To do this, enter
init.d/adminfs status.
Assign the appropriate trustee rights
to the user who will manage your
BCC. For information, see
Trustee Rights for the BCC
Administrator User to the Cluster
Objects" on page 49.
This connection state might be
caused by any number of problems,
including a severed cable or link
problems between geographic sites.
Troubleshooting Business Continuity Clustering 113
TM
etc/
"Assigning