C.1 Port numbers for JP1/IM

Organization of this subsection

(1) Port numbers used by JP1/IM - Manager and JP1/IM - View

The following table shows the port-numbers used by JP1/IM - Manager and JP1/IM - View.

For communication, JP1/IM also uses the port numbers in the range from 1025/tcp to 65535/tcp, which are automatically assigned by the OS. The range of automatically assigned port numbers, however, might vary depending on the OS.

Table C‒1: List of port numbers
Service name	Port number	IM-V	IM-M	Description
`jp1imevtcon`	20115/tcp	Y	Y	Used to connect to JP1/IM - Manager (event console service) from JP1/IM - View
`jp1imcmda`	20238/tcp	Y	Y	Used for the following: Used to execute commands from JP1/IM - View Used for JP1/IM - Manager (Central Console) to request JP1/Base^#1 to execute automated actions
`jp1imcss`	20305/tcp	Y	Y	Used to connect to JP1/IM - Manager (Central Scope service) from JP1/IM - View
None^#2	Port number of the IM database^#3	--	--	Used for internal processing by JP1/IM - Manager (IM database) (for physical hosts)
None^#2	Port number of the IM database^#4	--	--	Used for internal processing by JP1/IM - Manager (IM database) (for logical hosts)
`jp1imcf`	20702/tcp	Y	Y	Used to connect to JP1/IM - Manager (IM Configuration Management service) from JP1/IM - View
`jp1imfcs`	20701/tcp	--	Y	Used for internal processing by JP1/IM - Manager (event base service)
`jp1imegs`	20383/tcp	--	Y	Used for internal processing by JP1/IM - Manager (event generation service)
`jddmain`	20703/tcp	--	--	Used to connect from a Web client (a Web browser or a client to issue REST APIs) to JP1/IM - Manager (Intelligent Integrated Management Base service)
None	20705/tcp	--	Y	Used for JP1/IM - Manager (Intelligent Integrated Management Database)
None	20706/tcp	--	Y	Used by JP1/IM - Manager (Trend Data Management Service) internally

Legend:

IM-V: JP1/IM - View

IM-M: JP1/IM - Manager

Y: Registered in the services file at installation.

--: Not registered in the services file at installation (and does not need to be set).

#1: It refers to JP1/Base on the manager.

#2: Not registered in the services file.

#3: This port number is set in the setup information file when the IM database is set up on a physical host. For details about the setup information file, see Setup information file (jimdbsetupinfo.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

#4: This port number is set up in the cluster setup information file when the IM database is set up on a logical host. The port number increments with each IM database configured on the logical host. For details about the cluster setup information file, see Cluster setup information file (jimdbclustersetupinfo.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

Remotely monitored hosts use the port numbers shown in the following table.

Remotely monitored host	Port number
Remote-monitoring log file trap (SSH connection)	Port number specified in the System Common Settings window of IM Configuration Management
Remote-monitoring log file trap (NetBIOS [NetBIOS over TCP/IP]) connection^#1	137/udp, 137/tcp, 138/udp, 139/tcp, 445/tcp
Remote-monitoring event log trap (WMI connection)^#1	135/tcp, 445/tcp and dynamic port numbers that are automatically assigned as needed^#2

#1: To collect host information in remote monitoring, WMI and NetBIOS (NetBIOS over TCP/IP) are used for Windows hosts and SSH is used for UNIX hosts.

#2: WMI uses DCOM, and DCOM uses dynamic port allocation. Therefore, set the ports to be used by DCOM so that the lines connected to the ports pass through a firewall.

Standard ranges of the port numbers that are assigned by individual OSs are as follows:

Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025: 49152 to 65535

To Page Top

(2) Port numbers used by JP1/IM - Agent

The following shows the port numbers used by JP1/IM - Agent.

Table C‒2: Listening ports for processes in the integrated agent (in the Integration Manager host)
Process	Listening port to use	Default port number
imbase	Processes and JP1/IM agent control base (imagent) listening ports in the Integration Manager host	20724
imbaseproxy	Processes and JP1/IM agent control base (imagentproxy) listening ports in the Integration Manager host	20725

Table C‒3: Listening port for processes in the integrated agent (in integrated agent host)
Process	Listening port to use	Default port number
Prometheus server	Listening port for REST API	20713
Alertmanager	Listening port for REST API and Alert notifications	20714
Node exporter	Listening port for scrape	20716
Windows exporter		20717
Blackbox exporter		20715
Yet another cloudwatch exporter		20718
Promitor Scraper		20719
Process exporter		20721
Script exporter		20722
Fluentd(Log metrics feature)		24820 to 24850^#1
Promitor Resource Discovery	Connection port for Promitor Scraper	20720
imagent	Listening port in integrated agent host	20726
imagent	Listening port for JP1/Base event-forwarding	20733
imagentproxy	Listening port in integrated agent host	20727
imagentaction	Listening port in integrated agent host	20728
OracleDB exporter	Listening port for scrape	None
Node exporter for AIX^#2		20730
Web exporter		20731
VMware exporter		20732
Windows exporter (Hyper-V monitoring)		20734
SQL exporter		20735

#1

The listen port depends on the worker_id (specified for worker-id in the log metrics definition file (fluentd_any-name_logmetrics.conf)) of the worker used by Fluentd (the log metrics feature), and then it is expressed in the formula below.

24820 + worker_id

If the log metrics feature uses 129 workers, the default port numbers are the consecutive port numbers from 24820 to 24948.

#2

Node exporter for AIX operates on the monitored hosts.

Table C‒4: Destination ports to communicate with from JP1/IM - Agent processes
Process	Destination port to use	Default port number
Intelligent Integrated Management Base	Alert notification	Follow JP1/IM - Manager settings.
Promscale	Remotewrite
PostgreSQL	JP1/IM - Agent administration, message queuing, and command execution history
Web server to be monitored	Monitor target of Blackbox exporter	80/443
Web server to be monitored	Web exporter monitoring destination^# #: The specific usage and port number depend on the monitoring target.	80/443
AWS CloudWatch to be monitored	Monitor target of Yet another cloudwath exporter	443
HTTP proxy server	Communication from imagent,imagentproxy to imabase,imbaseproxy Communication from Exporter to monitoring target	The settings of the installed HTTP proxy server are followed.
Monitored Oracle listeners	OracleDB exporter monitoring destination	1521
Monitored Microsoft SQL Server	SQL exporter monitoring destination	1433

To Page Top