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).

  7. In the Authentication context field, view and if necessary change the port numbers next to the IP address.

    For example, the Authentication context field might contain a value similar to In this example, the first port number (2003) is the port number for the corresponding Identity Manager driver on the cluster that this cluster is synchronizing with. The second port number (2003) is the port number for the Identity Manager driver on this cluster.

    These port numbers should be the same, but should not be the same as the port numbers for other Identity Manager drivers on either this or the remote cluster.

  8. If you change the port numbers, restart the driver by clicking the upper right corner of the Cluster Sync or User Sync icon (whichever you have chosen), then click Restart driver.

  9. If you changed the port number in Step 7 above, change the port numbers to be the same for the corresponding driver in the other cluster.

    You can do this by repeating Step 1 through Step 8 for the Identity Manager driver on the other cluster.