3.3.4 Examining network configurations
The system administrator should examine what network configuration to use when configuring an operation monitoring system.
- Point:
-
With Performance Management, the performance data collected with the monitoring agent is stored in the monitoring agent itself. As a result, large amounts of performance data are not sent regularly over the network.
- Organization of this subsection
(1) Using Performance Management in a LAN environment
(a) How the Performance Management services communicate with each other
To allow Performance Management services to communicate with each other, the host names (or IP addresses) and the port numbers used by the services are registered in PFM - Manager when PFM - Agent or PFM - RM starts. For Performance Management, these host names, IP addresses, and port numbers are called node information. PFM - Manager manages node information. Performance Management services communicate with each other by using this node information.
If a service fails to establish a connection by using its node information, the host name was probably not resolved successfully. Check and, if necessary, revise the following settings and retry the connection:
-
jpchosts file
-
hosts file
-
DNS server
(b) Purpose of the jpchosts file
In a Performance Management system, PFM - Manager, PFM - Agent, and PFM - RM are installed on hosts and each host has multiple network adapters. As a result, each host can connect to multiple LANs.
Suppose a system in which each PFM - Manager and PFM - Agent (or PFM - RM) has multiple network adapters. In such a system, if some of the IP routes cannot be used to connect to the network, the IP addresses to be used must be specified in the PFM node information.
|
|
![[Figure]](GRAPHICS/ZU103030.GIF)
Configure the jpchosts file on the PFM - Manager server and the PFM - Agent server as follows to enable communication using IP address IP_C and IP address IP_A:
-
Settings in the jpchosts file on the PFM - Manager server
hostA IP_C
hostB IP_A
-
Settings in the jpchosts file on the PFM - Agent server
hostA IP_C
hostB IP_A
For details about the settings in the jpchosts file, see 5.3.1 Specifying and changing the network configuration or 6.3.1(1)(b) Setting IP addresses.
(2) Using Performance Management in a WAN environment
With Performance Management, PFM - Manager, PFM - Web Console, or PFM - Agent or PFM - RM can be placed behind a firewall.
Performance Management supports static NAT (basic NAT), which translates addresses one-to-one. In addition, the port number used by Performance Management can be changed to an arbitrary port number depending on the environment.
|
|
![[Figure]](GRAPHICS/ZU103035.GIF)
For details about port numbers, see the port number list in the manual Job Management Partner 1/Performance Management Reference.
(3) Using Performance Management in an environment that contains multiple hosts with the same name
Performance Management can be used in an environment that contains multiple hosts with the same name, for example, a host extending over multiple domains. In such an environment, create an alias name for each host to prevent hosts from being misidentified.
With Performance Management, you can choose to use the actual host name or an alias name. For details about which host name is used, for Windows see 5.3.3 Specifying and changing the monitoring host name in a Performance Management system, and for UNIX see 6.3.3 Specifying and changing the monitoring host name in a Performance Management system.
- Reference note
-
Alias names cannot be used as the host names in the logical host environment.
(4) Example of a network configuration that also supports an IPv6 environment
For Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Linux, Performance Management supports not only IPv4 network configurations, but also IPv6 network configurations. This means that with these operating systems you can run Performance Management in a network configuration that supports both IPv4 and IPv6 environments.
Note that IPv6 communications are not supported between PFM - Manager and PFM - Web Console.
The following figure shows an example of such a network configuration.
|
|
![[Figure]](GRAPHICS/ZU103063.GIF)
In a network configuration that supports both IPv4 and IPv6 environments, the PFM - Manager hosts must also support both IPv4 and IPv6 communications.
If IPv6 communications are used on the same hosts, PFM - Manager or PFM - Base, and PFM - Agent or PFM - RM must all be version 10-00 or later.
Specify for the IP address of a server on which IPv6 is installed a unique local address, a site-local address, or a global address. Neither a loopback address nor a link-local address can be specified.
To use IPv6 communications, you must execute the jpcconf ipv6 enable command on any PFM - Agent, PFM - RM, and PFM - Manager that will be using IPv6 communications. In a cluster system, these settings must be specified in both the active and the standby systems. For details about when to execute this command, for Windows see 5.3.1 Specifying and changing the network configuration, and for UNIX see 6.3.1 Specifying and changing the network configuration.
- Note:
-
In a network configuration that supports both IPv4 and IPv6 environments, connection cannot be established between a server on which only IPv4 is configured and a server on which only IPv6 is configured. Therefore, in the following commands some of the options might not be available or a portion of the function might be limited:
-
jpctool service list command
-
jpctool db backup command
-
jpctool db dump command
For details, see the chapter that explains these commands in the manual Job Management Partner 1/Performance Management Reference.
-