pw system portcheck



Run the pw system portcheck command to check the port availability of the specified component.

Syntax

pw system portcheck [<host> <port> [timeout in milliseconds]]

Notes:

  • If you do not specify any component host details, the command checks the availability of the Infrastructure Management Server ports.
  • (Applicable only to TrueSight Infrastructure Management version 11.3.02 and later) Enter the <host> and <port> details to check a specific component's port availability.
  • (Applicable only to TrueSight Infrastructure Management version 11.3.02 and later) When you want to check a specific component's port availability, you can specify the timeout value in milliseconds. The timeout value is optional. The default timeout is 5000 ms. You can change this default value by setting the parameter in the pronet.conf file located in the <Infrastructure Management Server Installation Directory>\custom\conf directory as shown in the following example:

    portcheck.remote.timeout.milliseconds=7000

Examples

Example 1

The following command checks the availability of the Presentation Server's port number 1900:

pw system portcheck tspsServer.bmc.com 1900 6000

In the preceding command, the timeout period specified is 6000 ms.

Output

Port 1900 on tspsServer.bmc.com is reachable
Connection status:- Success.

Example 2

The following command checks the availability of the Presentation Server's port number 99999:

pw system portcheck tspsServer.bmc.com 99999

The preceding command considers the default timeout value that is 5000 ms.

Output

Connection status:- Failed: Unable to establish a connection with the host tspsServer.bmc.com on port 99999, exception: port out of range:99999

Example 3

The following command checks the availability of the Infrastructure Management Server ports:

pw system portcheck

The command checks the default ports of the Infrastructure Management Server:

Component

Default port number

Rate

15000

Agent port

12124

JServer Event Server

9149

JMS

8093

Log Server

12141

Staging

3183

JNDI

1100

Database

2638

Agent controller

12123

Tomcat connector

8080

High-availability

10590
11590

Output

Rate port 15000 is busy
Agent port 12124 is busy
Jserver port 9149 is busy
JMS port 8093 is busy
Log Server port 12141 is busy
Staging port 3183 is busy
JNDI port 1100 is busy
Database port 2638 is busy
Agent Controller port 12123 is busy
Tomcat connector port 8080 is busy

Tips to troubleshoot port failure

If the port check fails, it indicates that the Infrastructure Management Server was not able to communicate to the remote host using a socket connection. Verify that the port configured between the Infrastructure Management Server host and the remote host is:

  • Open
  • Listening on the remote host
  • Not restricted by the firewall from the remote host
  • Not associated with a network delay
  • Not associated with network traffic routed through a load balancer

 

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