BMC ProactiveNet ports


This topic provides information about the various ports used by BMC ProactiveNet. You can configure some of these ports during the installation of  BMC ProactaiveNet Server and some of these ports can be configured only after the installation of  BMC ProactiveNet.

For more information about ports that can be configured during installation, see Ports-that-can-be-configured-during-installation.

For more information about ports that can be configured after installation, see Ports-that-can-be-configured-after-installation.

For more information about updating the port numbers, see Updating-port-numbers.

Securing internal port communication

Certain BMC ProactiveNet Server ports are used for communication between processes. Some ports are used by processes running on the server only; these are internal and must not be accessed by other computers in the network (Event server).

For security reasons, BMC Software recommends that all internal ports be made accessible only via the loopback address (127.0.0.1). By default, ports that are not required by external computers are secured, that is, the properties associated with the ports are set to the loopback address.

To make the BMC ProactiveNet Server accessible to other computers in a network, certain ports on the server must be made available. From a multi-homed computer, BMC ProactiveNet Server processes can be accessed using any of the available IP addresses.

The ports that the BMC ProactiveNet Server uses are bidirectional by default. That is, the TCP/IP ports transmit and receive data and can be used to perform read and write operations.

Note

Copy the values from installationDirectory/pw/pronto/conf/pronet.conf to installationDirectory/pw/custom/conf/pronet.conf and make changes in the custom/pronet.conf file to retain the changes for upgrades.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*