Nodeagent and DMGR ports

Nodeagent and DMGR ports that needs to be enabled for in firewall are listed below. Recently while working on a customer assignment I was asked to list the ports that needs to be enabled in the firewall on a production environment. Customer wants to open only those ports that are getting communicated between servers. There are not going to allow any of the other set of ports.

Version that I was referring to is Websphere Application Server v8.0.0.0

I had issues where the Nodeagent from secondary server is not able to communicate with Deployment manager and the basic command of addNode was not working. Following is the message that was appearing for me while executing addNode,

ADMU0027E: An error occurred during federation ADMU0036E: The Deployment
Manager cannot lookup by name host
<hostname> at address <ip>; rolling back to original configuration.

One option was to give all the ports that are configured with nodeagent with firewall team or else provide them a range of ports so that they will enable them.

As part of the same, there is a technote that mentions about the ports that needs to be enabled and these are the first set of ports that gets configured with Nodeagent and Deployment manager. This technote provides a brief overview of the ports that needs to be enabled and its obvious that we need to check the ports in our current configuration and then inform the network team accordingly.

Though I mentioned specific ports, I have asked them to disable the IPTABLES in Linux for sometime so that I can eliminate the issue of ports as I was able to ping between the systems. After fixing the ports between the systems, I was able to successfully add the node to deployment manager. addNode command was successful after enabling the ports.