Page tree
Skip to end of metadata
Go to start of metadata

The BMC TrueSight Infrastructure Management Server uses several TCP control ports for its operations. This topic provides information about these ports.

You can configure all these ports and specify values other then the default value. Some of these ports can be configured at the time of installing Infrastructure Management and some of these only after installation.

 To see the list of ports that can be configured at any time (during installation and later), see Ports that can be configured during installation.

To see the list of ports that cannot be configured during the time of installation, see Ports that cannot be configured during installation.

Securing internal port communication

Some BMC TrueSight Infrastructure Management 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 TrueSight Infrastructure Management Server accessible to other computers in a network, certain ports on the server must be made available. From a multi-homed computer, BMC TrueSight Infrastructure Management Server processes can be accessed using any of the available IP addresses.

The ports that the BMC TrueSight Infrastructure Management 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.