Appendix D.2 Routing through a firewall

Organization of this subsection
(1) Routing through a firewall
(2) Routing through a firewall (for logical host use)

(1) Routing through a firewall

If PFM - Manager and PFM - RM for Microsoft SQL Server communicate across a firewall, set fixed port numbers for all PFM - Manager and PFM - RM for Microsoft SQL Server ports. Set the port numbers in the directions shown in the table below so that all the services can route through the firewall.

Table D-2 Routing through a firewall (between PFM - Manager and PFM - RM for Microsoft SQL Server)

Service nameParameterDirection
Remote Monitor Store servicejp1pcsto4 [nnn]#RM [Figure] Manager
Remote Monitor Collector servicejp1pcagt4 [nnn]#RM [Figure] Manager
Legend:
Manager: PFM - Manager host
RM: PFM - RM host
[Figure]: Direction to start communication (connection) from the right-hand side to the left-hand side
#
When multiple instances are created, a sequential number (nnn) is appended to the second and subsequent instances. The first instance does not have a sequential number.

When starting communication (connection), the left-hand-side host that is being connected uses the port numbers listed in the table D-1. The right-hand-side host that opens communication uses the available port numbers allocated automatically by the OS. The range of the allocated port numbers differs depending on the host's OS.

In the case shown in table D-2, set up the firewall so that the Manager's temporary used transmitting port can route through the RM's receiving port.

Note:
To execute the jpctool db dump or jpcconf inst list command on a PFM - RM host, use either of the following methods:
  • Execute these commands with the proxy option to communicate through PFM - Manager. For details about the proxy option of the jpctool db dump or jpcconf inst list command, see the chapter on commands in the manual Job Management Partner 1/Performance Management Reference.
  • On each PFM - RM host, set port numbers in the direction shown in the table below to route traffic through the firewall.

    Table D-3 Routing through a firewall (between each PFM - RM hosts)

    Service nameParameterDirection
    Remote Monitor Store servicejp1pcsto4 [nnn]#RM [Figure][Figure] RM
    Remote Monitor Collector servicejp1pcagt4 [nnn]#RM [Figure][Figure] RM
    Legend:
    RM: PFM - RM host
    [Figure][Figure]: Direction to start communication (connection) from the left-hand side to the right-hand side, and from the right-hand side to the left-hand side
    #
    When multiple instances are created, a sequential number (nnn) is appended to the second and subsequent instances. The first instance does not have a sequential number.

(2) Routing through a firewall (for logical host use)

If PFM - Manager and PFM - RM for Microsoft SQL Server communicate across a firewall, set fixed port numbers for all PFM - Manager and PFM - RM ports. Set the port numbers in the directions shown in the table below so that all the services can route through the firewall.

Table D-4 Routing through a firewall (between PFM - Manager and PFM - RM (for logical host use))

Service nameParameterDirection
Remote Monitor Store service(logical host)jp1pcsto4[nnn] #RM(logical host)[Figure]Manager
Remote Monitor Collector service(logical host)jp1pcagt4[nnn] #RM(logical host)[Figure]Manager
Legend:
Manager : PFM - Manager host
RM(logical host) : PFM - RM host
Direction to start communication (connection) from the right-hand side to the left-hand side
#
When multiple instances are created, a sequential number (nnn) is appended to the second and subsequent instances. The first instance does not have a sequential number.

When starting communication (connection), the left-hand-side host that is being connected uses the port numbers listed in the table D-1. The right-hand-side host that opens communication uses the available port numbers allocated automatically by the OS. The range of the allocated port numbers differs depending on the host's OS.

In the case shown in table D-4, set up the firewall so that the Manager's temporary used transmitting port can route through the RM (logical host)'s receiving port.