Configure local communication ports

OMi servers open outbound connections to HPE Operations Agents, and HPE Operations Agents open outbound connections to OMi gateway servers, as the figure below shows:

  • An OMi gateway server (1) opens outbound connections, for example, to deploy policy templates and instrumentation, or to launch actions.

  • An agent (2) opens outbound connections, for example, to send events and action responses.

  • An OMi data processing server (3) opens outbound connections to send certificates.

A server and a node, which both open outbound connections each other.

By default, OMi gateway servers, data processing servers, and HPE Operations Agents use local port 0 for outbound connections, which means that the operating system allocates the local port for each connection. Typically, the operating system will allocate local ports sequentially. For example, if the operating system allocated local port 5055 to an Internet browser, and then the agent opens a connection, the agent receives local port 5056.

However, if a firewall restricts the ports that you can use, you can configure OMi servers and HPE Operations Agents to use a specific range of local ports instead.

Tip Make sure the port range is wide enough to accommodate all server-agent connections. Each HPE Operations Agent that is connected to OMi requires about three ports. For example, if your OMi servers monitor 20 nodes, the range should be 60 ports wide.

Learn more

Tasks