Configure communication broker ports

OMi servers and HPE Operations Agents both include communication brokers that listen for inbound connections on port 383, as the figure below shows:

  • The communication broker on an OMi gateway server (1) handles all inbound connections from HPE Operations Agents systems, and also from servers in other OMi or OM deployments.

  • The communication broker on an HPE Operations Agent system (2) handles all inbound connections from OMi servers.

  • The communication broker on the data processing server (3) handles all inbound connections from the OMi gateway server (1); for example, certificate requests.

A server and a node, which both listen on port 383 for inbound connections from each other.

You can configure any communication broker to listen on a port other than 383. If you do this, you must also configure all other systems in the environment, so that their outbound connections are destined for the correct port. For example, if you configure the communication broker on the HPE Operations Agent to listen on port 5000, you must also configure the OMi gateway servers so that they connect to port 5000 when they communicate with the agent.

Changing the communication broker port is mandatory on UNIX or Linux systems where the OMi or HPE Operations Agent processes run under a non-root user account. On UNIX or Linux systems, non-root users cannot open ports in the range 0 to 1023.

Learn more

Tasks