Portal V7.0 cluster: Set up unique UNICAST and MULTICAST ports

Update the ports for the dmgr, node agents and appservers.

You may still have the source servers running and broadcasting services within the network. Note that after migration, the dmgr name for example remains unchanged. To avoid conflicts with the new target environment server and services set unique ports.

As a rule of thumb, increase by 100 the original port number. You still need to make sure the same ports are not used in the source environment.

1. Open the WAS admin console and select...
   System administration > dmgr > Ports

2. Update the following ports:

   • CELL_DISCOVERY_ADDRESS

   • DCS_UNICAST_ADDRESS

3. Click System administration > Node agents > node_agent > Ports.

   1. Update the following ports:

      • DCS_UNICAST_ADDRESS

      • NODE_DISCOVERY_ADDRESS

      • NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS

      • NODE_MULTICAST_DISCOVERY_ADDRESS

   2. Repeat this step on all node agents

4. Click Servers > Server types > WebSphere appservers > application_servers > Ports.

   The default value for application_servers is WebSphere_Portal however you may have more servers defined. You need to update the ports on all appservers listed.

5. Update the following ports:

   • DCS_UNICAST_ADDRESS

6. Fully resynchronize the primary node:

   1. Click System administration > Nodes

   2. Select the check box for the primary node.

   3. Click on Full Resynchronize.

   For resynchronizing the primary node, the node agent on the primary node has to be running.

7. Restart the dmgr and node agent.

Parent: Portal V7.0 clustered environment