Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 Administration Guide


A.1 Port number list

This section describes the port numbers used by JP1/IT Desktop Management 2.

If not otherwise specified, "management server" includes "primary management server" and "management relay server".

Tip

All port numbers used by JP1/IT Desktop Management 2 - Manager are the same as those used by JP1/IT Desktop Management 2 - Operations Director.

JP1/IT Desktop Management 2 - Manager port number list

Management server

Port number for management server

Connection direction

Connected to [port number]

Protocol

Use

Ephemeral

[Figure]

The JP1/Base authentication server [20240]

TCP

Used for communication from a management server to the authentication server when authenticating JP1 users.

31080

[Figure]

Administrator's computer [ephemeral]

TCP

Used for communication from an administrator's computer to a management server when the operation window is referenced or used.

This port number is also used for communication from Remote Install Manager or Packager, or network control command installed on the administrator's computer to a management server.

31000

[Figure]

Agent, relay system or internet gateway [ephemeral]

TCP

Used for communication from an agent, relay system or an internet gateway to a management server

31002

[Figure]

Remote Install Manager or management server [ephemeral]

TCP

Used for communication from a remote Install Manager to a management server.

Ephemeral

[Figure]

Management relay server, agent or relay system [31001]

TCP

Used for communication from a management server to a management relay server, agent or relay system during distribution using Remote Install Manager

31006 to 31009, 31011, 31012

[Figure][Figure]

Management server [ephemeral]

TCP

Used for communication for internal processing within a management server.

31010

[Figure]

  • Remote Install Manager [ephemeral]

  • Asset Console (jamTakeITDM2Info.exe) [ephemeral]

TCP

Used for communication from Remote Install Manager or Asset Console to a management server, or internal processing

ephemeral

[Figure]

Management relay server, agent, or relay system [31001]

UDP

Used for controlling the power source by using Wake on LAN.

Ephemeral

[Figure]

Agent or relay system [31014]

UDP

Used for communication from a management server to an agent or relay system to distribute jobs by multicasting

31015

[Figure]

Agent or relay system [ephemeral]

UDP

Used for communication from an agent or relay system to a management server for requesting retransmission during multicast distribution

31021

[Figure]

  • Remote Install Manager [ephemeral]

  • Agent [ephemeral]

  • Relay system [ephemeral]

  • Packager [ephemeral]

  • Management relay server [ephemeral]

  • Management server [ephemeral]

  • Internet gateway [ephemeral]

TCP

Used for communication from Remote Install Manager, agent, relay system, Packager, management relay server, management server and internet gateway to a management server during distribution using Remote Install Manager

31023

[Figure][Figure]

Management server or management relay server [ephemeral]

TCP

Used for communication between a management server and a management relay server.

31026 to 31029

[Figure][Figure]

Management server [ephemeral]

TCP

Used for communication of internal processing performed on the management server when the API is used.

31030

[Figure]

External system [ephemeral]

TCP

Used for communication between the external system and the management server via the API.

Ephemeral

[Figure]

Management relay server, agent, or relay system [16992]

TCP

Used for controlling the power source of a computer that uses AMT

Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, in the setup, change them to port numbers that are not used.

If a management server controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Also, specify firewall settings to enable ports used for communication in internal processing. Note that if you install JP1/IT Desktop Management 2 - Manager in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).

Administrator's computer (Remote Install Manager )

Port number for administrator's computer

Connection direction

Connected to [port number]

Protocol

Use

Ephemeral

[Figure]

Management server [31002, 31010, 31021, 31080]

TCP

Used for communication from Remote Install Manager to a management server during distribution using Remote Install Manager

Ephemeral#

[Figure][Figure]

Management server [ephemeral#]

TCP

Used for Remote Install Manager internal processing

Ephemeral

[Figure]

Relay system [31021]

TCP

Used when deleting a package on a relay system using Remote Install Manager.

#: The following describes how to fix the port numbers used for connecting the database to the agent.

To fix the port number of the management server (connection destination):
  1. Execute the stopservice command to stop the services on the management server.

  2. Use a text editor to open the pdsys file stored in JP1/IT Desktop Management 2 - Manager-installation-folder\mgr\db\CONF.

  3. Add set pd_service_port = port-number. For port-number, specify the port number you want to use.

    Example: To specify 10000 as the port number, enter as follows:

    set pd_service_port = 10000
  4. Execute the startservice command to restart the services on the management server.

To fix the port numbers of Remote Install Manager (connection destination):

For receiving ports, the OS automatically assigns port numbers by default. Ten or more receiving ports are used.

  1. Stop Remote Install Manager and other applications for JP1/IT Desktop Management 2.

  2. Use a text editor to open the HiRDB.ini file stored in Remote-Install-Manager-installation-folder\mgr\dbclt.

    If Remote Install Manager and the management server are installed in the same computer, HiRDB.ini is stored in JP1/IT Desktop Management 2-Manager-installation-folder\mgr\dbclt.

  3. For PDCLTRCVPORT=, specify the range of port numbers you want to use in the port-number-port-number format. Note that the range of port numbers is not set if you do not specify anything or specify 0 after PDCLTRCVPORT=, By default, the range of port numbers is not set.

    Example: To specify 10000-10500 as the range of port numbers, enter as follows:

    PDCLTRCVPORT=10000-10500
  4. Start Remote Install Manager and other applications for JP1/IT Desktop Management 2.

Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, in the setup, change them to unused port numbers.

If the administrator's server controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if you install Remote Install Manager in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).

Port number list for a relay system

Port number for relay system

Connection direction

Connected to [port number]

Protocol

Use

16992

[Figure]

Management server [ephemeral]

TCP

Used for controlling the power source of a computer that uses AMT

31001

[Figure]

Management server [ephemeral]

TCP

Used for communication from a management server to a relay system during distribution using Remote Install Manager

31001

[Figure]

Management server [ephemeral]

UDP

Used for controlling the power source by using Wake on LAN.

31002

[Figure]

  • Agent [ephemeral]

  • Internet Gateway [ephemeral]

TCP

Used for communication from an agent and internet gateway to a relay system during distribution using Remote Install Manager

31014

[Figure]

Management server [ephemeral]

UDP

Used for communication from a management server to a relay system to distribute jobs by multicasting

31015

[Figure]

Agent [ephemeral]

UDP

Used for communication from an agent to a relay system for requesting retransmission during multicast distribution

31021

[Figure]

Remote Install Manager [ephemeral]

TCP

Used when deleting a package on a relay system using Remote Install Manager.

ephemeral

[Figure]

Management server [31015]

UDP

Used for communication from a relay system to a management server for requesting retransmission during multicast distribution.

Ephemeral

[Figure]

Management server [31021]

TCP

Used for communication from a relay system to a management server during distribution using Remote Install Manager

Ephemeral

[Figure]

Agent [16992]

TCP

Used for controlling the power source of a computer that uses AMT

ephemeral

[Figure]

Agent [31001]

UDP

Used for controlling the power source by using Wake on LAN.

ephemeral

[Figure]

Agent [31014]

UDP

Used for communication from a relay system to an agent during multicast distribution.

Port number list for a controller and remote control agent

Controller or remote control agent [port number]

Connection direction

Connected server [port number]

Protocol

Use

Remote control agent [31016]

[Figure]

Controller [ephemeral]

TCP

Used for window operation from a controller to a remote control agent

Remote control agent [31017]

[Figure]

Controller [ephemeral]

TCP

Used for transferring files from a controller to a remote control agent

Remote control agent or controller [31018](when used as a chat server)

[Figure][Figure]

Remote control agent or controller [ephemeral]

TCP

Used for chat

Remote control agent [ephemeral]

[Figure]

Controller [31019]

TCP

Used for requesting a remote connection from a remote control agent to a controller

Remote control agent [ephemeral]

[Figure]

Controller [31020]

TCP

Used for callback file transfer from a remote control agent to a controller

controller [ephemeral]

[Figure]

RFB connection target device [5900]

TCP

Used for remote control by means of RFB connection.

controller [ephemeral]

[Figure]

Remote control agent[16992]

TCP

Used for controlling the power source of a computer that uses AMT

Controller [ephemeral]

[Figure]

Remote control agent [31016]

UDP

Used for controlling the power source by using Wake on LAN.

If a computer with a controller installed or a computer that is remotely controlled controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if a controller and remote control agent are installed in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).

Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, follow the steps below to change them to port numbers that are not used.

JP1/IT Desktop Management 2 - Agent port number list

Agent port number

Connection direction

Connected server [port number]

Protocol

Use

31001

[Figure]

Management server [ephemeral]

TCP

Used for communication from a management server to the agent

31001

[Figure]

Management server or relay system [ephemeral]

UDP

Used for controlling the power source by using Wake on LAN.

16992

[Figure]

Management server [ephemeral]

TCP

Used for controlling the power source of a computer that uses AMT

Ephemeral

[Figure]

Relay system [31002]

TCP

Used for communication from an agent to a relay system during distribution using Remote Install Manager

31014

[Figure]

Management server or relay system [ephemeral]

UDP

Used for communication from a management server or relay system to an agent to distribute jobs by multicasting

Ephemeral

[Figure]

Management server or relay system [31015]

UDP

Used for communication from an agent to a management server or relay system for requesting retransmission during multicast distribution

Ephemeral

[Figure]

Management server [31021]

TCP

Used for communication from an agent to a management server system during distribution using Remote Install Manager

31024

[Figure]

Agent [ephemeral]

TCP

Used for communication within an agent when an agent that communicates with a higher system via the Internet gateway communicates with the Internet gateway.

31025

[Figure]

Agent [ephemeral]

TCP

Used for communication within an agent when an agent that communicates with a higher system via the Internet gateway communicates with the Internet gateway.

Ephemeral

[Figure]

Internet gateway [443]

TCP

Used for communication via the Internet gateway.

Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, when setting up a management server, change them to port numbers that are not used.

If a computer with an agent installed controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if an agent is installed in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).

If networks between JP1/IT Desktop Management 2 - Manager and JP1/IT Desktop Management 2 - Agent control ports by using Windows Firewall, specify firewall settings to enable the ports in the above table.

Port numbers for agentless devices

For agentless devices, the port numbers for Windows administrative shares or SNMP are used depending on the authentication status of the devices.

Port number list for an Internet gateway

Port number for Internet gateway

Connection direction

Connected to [port number]

Protocol

Use

443

[Figure]

Agent [ephemeral]

TCP

Used for communication via the Internet gateway.