What TCP/IP ports will my Tivoli monitoring address space use?
The most common customer question about Tivoli OMEGAMON and Tivoli Monitoring products in the context of TCP/IP port consumption is: Which TCP/IP ports will my Tivoli monitoring address space use? The TCP/IP port consumption of a Tivoli monitoring product address space depends on the connection protocols configured for that address space. Chart 1 illustrates, for a given protocol name, the TCP/IP port allocated when the address space is ‘acting’ as a server (by listening on a well-known address), and the TCP/IP port allocated when the address space is ‘acting’ as a client (is in an established session with a server at a well-known address). To understand the port usage above, follow this example of an actual z/OS NETSTAT display, which has been modified with line numbers to assist the description: Line 01 illustrates the port consumption of a Tivoli Enterprise Monitoring Server (TEMS) address space configured with IP.PIPE. In the server port column, Rule 2 in Chart 1 shows that 1918 is
