3.1.1 Issues to consider before installing the Windows edition

(a) Setting IP addresses

You must set up the environment for PFM - RM for Platform in such a way that it can resolve an IP address from a host name. PFM - RM for Platform will not start in an environment in which an IP addresses cannot be resolved.

In Performance Management, a host such as a PFM - RM for Platform host that is used in the Performance Management system is called a monitoring host.

You use one of the following methods to set host names and IP addresses:

• jpchosts file (Performance Management's host information configuration file)

• hosts file

• DNS

For the monitoring host name, use either the real host name or the alias name.

• Using the real host name

  In a Windows environment, specify the name in such a way that the IP address can be resolved from a host name that can be checked with the execution results of the hostname command.

  Note that Performance Management supports DNS, but not FQDN. This means that when you set the IP address, you must use the host name obtained by the hostname command without the domain name.

• Using an alias name

  Set up the environment in such a way that the IP address can be resolved from a specified alias name.

For details about setting the name of the monitoring host, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Note that the IP address specified in the jpchosts file is not used for IP address resolution with the monitored host.

Notes about setting IP addresses

• If you use Performance Management in multiple LAN environments, use the jpchosts file to set IP addresses. For details about using the jpchosts file to set IP addresses, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

• Performance Management will not run on a host where IP addresses are assigned dynamically by DHCP. You must set fixed IP addresses for all monitoring hosts.

(b) Settings for using IPv6

Performance Management supports both IPv4 and IPv6 network environments. Therefore, you can run Performance Management even in a network environment where IPv4 and IPv6 coexist.

PFM - RM for Platform can use IPv6 to communicate with PFM - Manager. However, this applies only when the OS of the host on which PFM - RM for Platform and PFM - Manager are installed is Windows Server 2008 R2, Windows Server 2012, or Linux. For details about the applicable scope of communication in the IPv4 and IPv6 environments, see L. Communication in IPv4 and IPv6 Environments.

To communicate using IPv6, you must enable the use of IPv6 on both the PFM - Manager host and the PFM - RM host. You specify this setting by executing the jpcconf ipv6 enable command. The following explains the conditions to use for determining whether you need to execute this command.

Cases in which you need to execute the jpcconf ipv6 enable command:

• If all hosts are being changed from an IPv4 environment to an IPv6 environment.

• In an environment where IPv4 and IPv6 coexist, if PFM - Manager is being changed from an IPv4 environment to an IPv6 environment.

Cases in which you do not need to execute the jpcconf ipv6 enable command:

• If all hosts are already in an IPv6 environment.

• In an environment where IPv4 and IPv6 coexist, if PFM - Manager is already set up as an IPv6 environment.

An execution example of the jpcconf ipv6 enable command follows:

jpcconf ipv6 enable

For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference. For details about the conditions and timing for executing the jpcconf ipv6 enable command, see the chapter that describes an example of a network configuration that includes an IPv6 environment in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

When PFM - RM for Platform will use IPv6 to communicate with monitored hosts, specify a monitored host name that can be resolved.

PFM - RM for Platform uses a resolvable IP address to communicate with a monitoring target. When PFM - RM for Platform communicates with a monitoring target in an environment where IPv4 and IPv6 coexist, PFM - RM for Platform will not try to communicate using another IP address if communication using a resolvable IP address fails.

For example, if a connection attempt using IPv4 fails, PFM - RM for Platform will not retry using IPv6. Similarly, if a connection attempt using IPv6 fails, PFM - RM for Platform will not retry using IPv4. Therefore, make sure that connection can be established before starting PFM - RM.

(c) Setting port numbers

You must assign a port number to each service of the programs used in Performance Management. Set up the network in such a manner that the port numbers assigned to PFM - RM for Platform can be used for communication.

The table below lists and describes the default port number assigned to various services. For other services, an unused port number is assigned automatically each time the service starts.

When you use Performance Management in an environment that includes a firewall, you must use fixed port numbers. For details about how to use fixed port numbers, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

(a) When installing PFM - RM for Platform on the PFM - Manager host

With this program configuration, PFM - RM for Platform is installed on the same host as PFM - Manager. The following figure shows the program configuration.

(b) When installing PFM - RM for Platform on a host other than the PFM - Manager host

With this program configuration, PFM - RM for Platform is installed on a host other than the PFM - Manager host. If you use this program configuration, you must install PFM - Base on the same host as for PFM - RM for Platform. The following figure shows the program configuration.

(c) Prerequisite OSs for monitored hosts

A monitored host must be using one of the following OSs:

• Windows Server 2003

• Windows Server 2008

• Windows Server 2012

• HP-UX

• Solaris

• AIX

• Linux

(d) Prerequisite programs for Performance Management

PFM - Manager or PFM - Base must be available on the host where PFM - RM for Platform is installed.

If you install PFM - RM for Platform on a host where PFM - Manager is available, PFM - Base is not required. If you install multiple PFM - RMs on a host where PFM - Base is available, you need only one PFM - Base.

You also need PFM - Web Console in order to use PFM - RM for Platform to monitor the operation of monitored hosts.

(a) Setting the user accounts

To use WMI, you need a local user account or domain account for the PFM - RM host, and a local user account for the monitored host.

PFM - RM for Platform collects information using the account that is specified for connection in WMI's name space.

• PFM - RM host account

  To set up the host account, specify the values appropriate to the RMHost_User, RMHost_Password, and RMHost_Domain settings shown in Table 3-20 Instance environment setting items and values for PFM - RM for Platform (for Windows). You specify this account when you set up an instance.

  If you run PFM - RM for Platform in a cluster system, set up the account for the PFM - RM host so that it is possible to log on to both the executing system and the standby system by specifying the same user name and password.

  When the PFM - RM host itself is the monitoring target, the specified account also affects the WMI connection. The type of records that can be collected differs depending on the account type. The following table shows various account types and whether records can be collected.

  Table 3‒2: PFM - RM host account types and whether records can be collected (when the monitored host is the local host and is running Windows Server 2003)

  Account type	Can records be collected?
  	Records that stores process operation status information#1	Records that stores information other than process operation status#2
  Administrator (Built-in Administrator)	Y	Y
  Administrators group member	Y	Y
  Performance Log Users group member	N	Y
  Performance Monitor Users group member	N	Y

  Legend:

  Y: Can be collected.

  N: Cannot be collected.

  #1

  Applies to PD_APS, PD_ASVC, PD_APP2, PD_APPC, and PD_APPD records.

  #2

  Applies to PI, PI_CPU, PI_LDSK, PI_NET, PI_PDSK, and PD records.

  Table 3‒3: PFM - RM host account types and whether records can be collected (when the monitored host is the local host and is running Windows Server 2008 or Windows Server 2012)

  Account type	Can records be collected?
  	Records that stores process operation status information#1	Records that stores information other than process operation status#2
  Administrator (Built-in Administrator)	Y	Y
  Administrators group member (UAC enabled)	N	N
  Administrators group member (UAC disabled)	Y	Y
  Performance Log Users group member	N	Y
  Performance Monitor Users group member	N	Y

  Legend:

  Y: Can be collected.

  N: Cannot be collected.

  #1

  Applies to PD_APS, PD_ASVC, PD_APP2, PD_APPC, and PD_APPD records.

  #2

  Applies to PI, PI_CPU, PI_LDSK, PI_NET, PI_PDSK, and PD records.

• Monitored host accounts

  To set up a monitored host account, specify the values appropriate to the User, Password, and Domain settings shown in Table 3-27 Setting items and values for a monitored host in PFM - RM for Platform. You specify such an account when you set up each monitoring target.

  Note that a monitored host account must be set as a member of the Administrators, Performance Log Users, or Performance Monitor Users group.

  You need permissions to perform operations such as Windows security audits.

  The type of records that can be collected differs depending on the account type. The following table shows various account types and whether records can be collected.

  Table 3‒4: Account types and whether records can be collected (when the monitored host is running Windows Server 2003)

  Account type	Can records be collected?
  	Records that stores process operation status information#1	Records that stores information other than process operation status#2
  Administrator (Built-in Administrator)	Y	Y
  Administrators group member	Y	Y
  Performance Log Users group member	N	Y
  Performance Monitor Users group member	N	Y

  Legend:

  Y: Can be collected.

  N: Cannot be collected.

  #1

  Applies to PD_APS, PD_ASVC, PD_APP2, PD_APPC, and PD_APPD records.

  #2

  Applies to PI, PI_CPU, PI_LDSK, PI_NET, PI_PDSK, and PD records.

  Table 3‒5: Account types and whether records can be collected (when the monitored host is running Windows Server 2008 or Windows Server 2012)

  Account type		Can records be collected?
  		Record that stores process operation status information#1	Record that stores information other than process operation status#2
  Local account	Administrator (Built-in Administrator)	Y	Y
  	Administrators group member (UAC enabled and LocalAccountTokenFilterPolicy not specified)	N	N
  	Administrators group member (UAC enabled and LocalAccountTokenFilterPolicy specified)	Y	Y
  	Administrators group member (UAC disabled)	Y	Y
  	Performance Log Users group member	N	Y
  	Performance Monitor Users group member	N	Y
  Domain account	Administrator (Built-in Administrator)	Y	Y
  	Administrators group member (UAC enabled)	Y	Y
  	Administrators group member (UAC disabled)	Y	Y
  	Performance Log Users group member	N	Y
  	Performance Monitor Users group member	N	Y

  Legend:

  Y: Can be collected.

  N: Cannot be collected.

  #1

  Applies to PD_APS, PD_ASVC, PD_APP2, PD_APPC, and PD_APPD records.

  #2

  Applies to PI, PI_CPU, PI_LDSK, PI_NET, PI_PDSK, and PD records.

(b) Setting the WMI service

Set the WMI service startup option for monitored hosts to a value other than Disabled. If it is set to Disabled, performance data will not be collected.

(c) WMI connection settings

Specify the WMI connection settings at both the PFM - RM host and the monitored hosts. For details about the WMI connection settings, see 3.1.5 WMI connection setting method (when both the PFM - RM host and the monitored host are running Windows).

(d) Setting up WMI remote connection that uses UAC

If either Windows Server 2008 or Windows Server 2012 is used, the UAC function restricts the permissions granted to local users who have Administrator permissions (except for the Administrator user who is created during OS installation). Consequently, if WMI remote connection to monitored servers running Windows Server 2008 or Windows Server 2012 is executed as a local user who has Administrator permissions, a problem might occur. That is, because the connection attempt will be made with ordinary user permissions instead of Administrator permissions, the access might be refused, resulting in an error. To avoid this, take one of the following steps if UCA is enabled:

• For the user to be used for authentication, use the Administrator user who is created during OS installation.

• Execute the following command with Administrator permissions to update the registry value to make UAC permit remote connection.

  reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

  To cancel the remote connection permitted by UAC, execute the following command:

  reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /f

If UAC is disabled, use a member of the Administrator group as the user to be used for authentication.

(a) User account settings

To use SSH, both PFM - RM host and monitored host accounts are required.

• PFM - RM host account

  To set up an account, specify the values using the settings for RMHost_User, RMHost_Password, and RMHost_Domain in Table 3-20 Instance environment setting items and values for PFM - RM for Platform (for Windows). The account that is set up must be specified during instance setup.

  If you run PFM - RM for Platform in a cluster system, specify the same user and password for the PFM - RM host account at both the active server and the standby server so that the account can log on to both servers.

• Monitored host account

  If the OS of the connection-target monitored host is AIX and a user other than root user is to collect information, that user must belong to both the adm group and the system group; otherwise, some information will not be collected.

  To ensure that the user belongs to both groups (adm and system), execute the following command at the connection-target monitored host:

  $ id
  uid=xxx(xxx) gid=x(xxx) groups=0(system),4(adm)

  For details about the information that is not collected, see 7. Records. If the OS of the monitored host is not AIX, this user limitation is not applicable.

(b) Installing software and packages

(c) SSH connection settings

Specify the SSH connection settings on both the PFM - RM host and the monitored hosts. For details about the SSH connection settings, see 3.1.6 SSH connection setting method for Windows (when the PFM - RM host is running Windows and the monitored host is running UNIX).

(a) Setting method in Windows Server 2003

• Memory dump output settings

1. From Control Panel, double-click System.

2. Under the Advanced tab, choose Startup and Recovery, and then click Settings.

3. Under Write debugging information, choose Kernel memory dump, and then specify an output destination file.

Note:

The memory dump size varies according to the size of the physical memory. If a large amount of physical memory is installed, the memory dump size will be large. Therefore, allocate a disk area that is large enough for collecting the memory dump. For details, see the documentation for the OS.

• Crash dump output settings

1. From the Start menu, choose Run.

2. Enter drwtsn32 in the text box and click the OK button.

   The Dr. Watson for Windows dialog box appears.

3. Select the Create Crash Dump File check box and specify the output destination file in the Crash Dump text box.

4. Click the OK button.

Note:

The information that is output in a crash dump includes problem information on Job Management Partner 1 as well as other application programs. When a crash dump is output, it uses disk space. Therefore, when you are specifying that a crash dump is to be output, allocate sufficient disk space.

(b) Setting method in Windows Server 2008 or Windows Server 2012

• Output settings for user-mode process dump

  By entering the following registry, you can instantly collect user-mode process dump for investigation purposes if an application program terminates abnormally:

  \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

  Specify the following registry values in the registry key:

  • DumpFolder : REG_EXPAND_SZ <dump-output-destination-folder-name>

    (You must have permissions to write data to the output destination folder.)

  • DumpCount : REG_DWORD <number-of-dumps-to-be-saved>

  • DumpType : REG_DWORD 2

Note:

• Setting up this registry entry enables you to output user-mode process dumps in Job Management Partner 1 as well as other application programs. Be aware of this point when deciding to output user-mode process dump.

• When a user-mode process dump is output, it uses disk space. Therefore, when you decide to output user-mode process dump, make sure that sufficient disk space is allocated to the specified dump output destination folder.