Determining which TCP control ports are being used

Before you change or assign a new TCP control port, you might want to determine which TCP control ports are already in use on that server. The procedure for retrieving this information depends on whether the server is running Linux, Solaris, or Microsoft Windows.

Before you begin

Ensure that all applications on the server that are using TCP control ports are running.

To determine which TCP control ports are in use on a Microsoft Windows server

1. On a Microsoft Windows server, access a command line and run the following command: netstat
   
   On the command screen, active connections are listed, with the active TCP control ports shown in the Local Address column in the format: pcuser:control_port. For example, the listing jjohnson:12124 indicates that system name jjohnson is running the local agent on the default TCP control port 12124.
   
   Active connections
   
   
2. Check the TCP control port listings to see if the TCP control port entry that you want to use is not already in use.

To determine whether a TCP control port is in use on a Linux or Solaris server

1. On the UNIX server, access the command-line interface and run the following command:
   netstat -a|grep LISTEN|grep ".control_port"
   
   No return indicates port 80 is not being used.

2. Repeat the command for each of the following ports: 443, 1099, 9149, 12123, 12124, 12125, 12130, and 45000.
   
   The following ports are required by Infrastructure Management, and if any are used, you need to resolve the conflict before continuing. 
   BMC recommends that the following port configuration be not changed.

   Non-configurable (Internal Process) Ports

   Control port	Description
   1099	pronet.rmi.port
   8008	Connector port between Apache Web server an