Flexibility to change the reserved TCP ports for ESM processes

Idea ID 2774515

Flexibility to change the reserved TCP ports for ESM processes

0 Votes

There are a list of TCP ports reserved for ESM processes. These ports must be kept open for ESM and the port numbers cannot be changed.  As the list of ports is considerable long...about 30 ports or more?  If customer needs to install another application or agent on the ESM server, there is a chance that the application requires the TCP port that already reserved for ESM.  For example, we have a customer that would need to run BMC patrol agent on all the enterprise servers per company policy.  The BMC patrol would require port 3181 which is already being used by ESM process.  In our environment, a BMC patrol is part of the system baseline when provisioning a VM.  All Linux VM will have a template with preinstalled BMC patrol agent and other basic software like backup agent.   To change the port of BMC agent from port 3181 to a different port, would result a change to the customer's standard VM template and baseline, which is more troublesome.   Hence, it will be desirable if these TCP port reserved by ESM processes, are configurable in config file such as server.properties.

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.