Job Management Partner 1/Performance Management Planning and Configuration Guide

[Contents][Glossary][Index][Back][Next]

6.3.1 Changing the network configuration

This subsection describes the procedure to change the Performance Management settings when the network configuration is changed.

For details on commands, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference. For details on settings and notes about communication through a firewall between PFM - Manager and PFM - Web Console or between PFM - Manager and either PFM - Agent or PFM - RM, see the list of port numbers in the appendix of the manual Job Management Partner 1/Performance Management Reference.

Organization of this subsection
(1) Procedure on the PFM - Manager host and either PFM - Agent host or PFM - RM host

(1) Procedure on the PFM - Manager host and either PFM - Agent host or PFM - RM host

This subsection describes the procedure to change network settings on the PFM - Manager host and either PFM - Agent host or PFM - RM host.

(a) Setting IP addresses

You need to set IP addresses if you wish to specify IP addresses to use Performance Management in a network environment connected to multiple LANs.

To set the IP address, directly edit the content of the jpchosts file.

Note:
If you have set the jpchosts file, the definitions in the hosts file or DNS are not referenced for a host name defined in the jpchosts file. Therefore, the IP address obtained from a host name must be defined in the jpchosts file.

To set IP addresses:

  1. Use a text editor or a similar tool to open the jpchosts file.
    The jpchosts file is stored in the /opt/jp1pc directory.

  2. Edit the jpchosts file.
    For example, if there is a hostA with the IP address 20.108.41.1 and a hostB with the IP addresses 20.108.41.2 and 20.108.41.3, set the IP addresses of the hosts as follows: 
     
hostA 20.108.41.1
hostB 20.108.41.2, 20.108.41.3
    If you want to provide an alias name aliasA to a host whose IP address is 20.108.41.1, specify the name as follows:
     
aliasA 20.108.41.1
    • If more than one IP address is set for one host, then the first specified IP address is given priority.
    • IP address settings becomes invalid if any of the following conditions are met:
      - When the host name length is 33 bytes or longer
      - When the host name is localhost
      - When an IP address in dotted decimal format is used for the host name (example: 172.16.233.12)
      - When the host name starts with a hyphen (-)
      - When the host name includes the following characters or space characters:
      \ / : , ; * ? " > < | . =
    • Specify IP addresses in dotted decimal format (for example: 172.16.233.12).
    • You can specify up to 16 IP addresses for one host.

  3. Stop Performance Management on the host whose IP address you set, and then copy the jpchosts file according to the instructions in note 2 below.

  4. Restart Performance Management on the host.
    The information settings for the jpchosts file become valid when Performance Management is restarted.

Note 1
In name resolution using the jpchosts file, if the IP address that was set first becomes invalid, the system does not simply continue and use the IP address that was set second. For the next and subsequent communications, an attempt is made to use the first IP address and then the following addresses in order.

Note 2

Determining whether to add settings for a PFM - Manager host to jpchosts
  1. When the PFM - Manager host uses a single NIC:
    jpchosts of PFM - Manager: Setting not required.
    jpchosts of PFM - Agent or PFM - RM connected to PFM - Manager: Setting not required.
  2. When the PFM - Manager host uses two or more NICs:
    jpchosts of PFM - Manager: Specify the IP address you want to allocate to PFM - Manager.
    jpchosts of PFM - Agent or PFM - RM connected to PFM - Manager: Specify the IP address you want to allocate to PFM - Manager.

Determining whether to add settings for a PFM - Agent or PFM - RM host to jpchosts
Perform the steps below for each PFM - Agent or PFM - RM host in the system.
  1. When the PFM - Agent or PFM - RM host uses a single NIC:
    jpchosts of PFM - Manager: Setting not required.
    jpchosts of the confirmed instance of PFM - Agent or PFM - RM: Setting not required.
    jpchosts of other instances of PFM - Agent or PFM - RM: Setting not required.
  2. When the PFM - Agent or PFM - RM host uses two or more NICs:
    jpchosts of PFM - Manager: Specify the IP address you want to allocate to the PFM - Agent or PFM - RM.
    jpchosts of the confirmed instance of PFM - Agent or PFM - RM: Specify the IP address you want to allocate to the PFM - Agent or PFM - RM.
    jpchosts of other instances of PFM - Agent or PFM - RM: Setting not required.
    Note: If you want the PFM - Agent or PFM - RM to be able to communicate with another PFM - Agent host or PFM - RM host during operations such as using the jpctool db backup command, jpctool db clear command, jpctool db dump command, or jpctool service list command, you need to add the setting for the confirmed instance of PFM - Agent or PFM - RM to the jpchosts file.

(b) Setting port numbers

Set a fixed port number for each service when you want to operate the Performance Management system with fixed port numbers for reasons such as to allow communication through a firewall between PFM - Manager and PFM - Web Console, or between PFM - Manager and either PFM - Agent or PFM - RM.

Use the jpcconf port define command to set a fixed port number for each service or change port numbers that have been set. Use the Windows initialization file (config.xml) to set the port numbers on the PFM - Web Console side. For details on how to change the config.xml file on the PFM - Web Console host, see 6.4.6 Changing PFM - Web Console settings.

For procedures on setting port numbers, see the description of firewall routing in the appendixes of the manual Job Management Partner 1/Performance Management Reference.

Supplemental information:
To avoid confusion during operations, use the same port numbers and service names throughout the entire Performance Management system.

To set port numbers:

  1. Execute the jpcconf port define command.
    For example, to set fixed values to the port numbers for all services, specify and execute the command as follows: 
     
jpcconf port define -key all

  2. Set a port number for the individual services.
    Executing the jpcconf port define command displays the currently set port number or default port number.
    For example, the current port number 22285 for the Name Server service is displayed as follows: 
     
Component[Name Server]
ServiceID[PN1001]
Port[22285]
     :
    Actions vary depending on how you set the port number. The following table lists and describes the settings and actions. As long as there is no duplicate port numbers in the system, use the port number displayed by the jpcconf port define command as is.
    Settings Action
    To use the displayed number as the fixed port number for a service Press the return key.
    To change the displayed port number to another number Enter a port number between 1024 - 65535.
    However, you cannot specify the port numbers currently used by the system.
    Port numbers that are not fixed Enter 0.
    However, you cannot fix port numbers for the following services: If you enter 0, the default value is set.
    • Name Server service
    • View Server service (between PFM - Web Console and View Server service)
    • NNM Object Manager service
    • Status Server service

    Notes:
    • If Performance Management programs and services are running when you set port numbers, stop the services and then execute the jpcconf port define command. After completing the port number settings, manually start the services.
    • The port number cannot be set correctly if you use the Ctrl+C key command to interrupt execution of the port define command. Execute the jpcconf port define command again to set the port number.

  3. Execute the jpcconf port list command again to check if the port number has been set correctly.
    For example, to display the port numbers used by all services, specify and execute the command as follows: 
     
jpcconf port list -key all
    If <error> is displayed in the Service area or Port area, the port numbers have not been set correctly. Set the port numbers again. One of the following could be the cause of the error:
    • The port number is not registered in the services file.
    • The same port number is already registered in the services file.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.