Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Performance Management Planning and Configuration Guide

5.3.1 Specifying and changing the network configuration

This subsection explains how to change the Performance Management settings when you have set up or changed the network configuration.

For details about commands, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference. For details about 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

(a) Setting IPv6 communication

Perform this setting if you use not only IPv4 communication but also IPv6 communication in Performance Management.

Note that only IPv4 communication is supported between PFM - Manager and PFM - Web Console.

To use IPv6 communication, you must execute the jpcconf ipv6 enable command in the PFM - Agent, PFM - RM, and PFM - Manager that will be using IPv6 communication.

In a cluster system, this setting must be specified in both the executing system and the standby system.

Once the command has executed, IPv6 communication will be used by default thereafter.

To set IPv6 communication:

  1. Execute the jpcconf ipv6 enable command for each PFM - Agent, PFM - RM, and PFM - Manager that will be using IPv6 communication.

    You can execute the commands in any order.

For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

(b) 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 IP addresses, 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.

  • The same host name cannot be specified more than once. If there are multiple lines that specify the same host name, only the definition in the first line specified will be used.

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 installation folder.

  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 multiple IP addresses are specified for a single host, the leftmost IPv4 and IPv6 addresses specified are used.

    • IP address settings becomes invalid if any of the following conditions is met:

      - The host name length is 33 bytes or longer

      - The host name is localhost

      - The IP address (such as 172.16.233.12 or ACE6:45:75:91::1) is used as a host name

      - The host name starts with a hyphen (-)

      - The host name includes any of the following characters or the space character:

      \ / : , ; * ? " > < | . =

    • For IPv4, specify the IP address in dotted decimal notation (example: 172.16.233.12). For IPv6, specify the IP address in colon hexadecimal notation (example: ACE6:45:75:91::1).

    • A zone ID that is added at the end of an IPv6 address, such as in the format of %1 in Windows, cannot be specified. If specified, zone IDs are treated as invalid IPv6 addresses and ignored.

    • 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, when the IP address that is set first becomes invalid, the system does not simply continue to use the IP address 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 that connects 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 that you want to allocate to 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.

Supplemental information:

If names are resolved between the PFM - Manager host and the PFM - Agent or PFM - RM host, there is no problem in the network settings. However, to avoid any confusion during operation, we recommend that you use the same definition in the jpchosts file among all target hosts.

■ IP addresses used between the PFM - Manager host and the PFM - Agent or PFM - RM host

This subsection describes the IP addresses that are used for communication between the PFM - Manager host and the PFM - Agent or FM - RM host.

• IP address used by the services at the sending end
Source IP address used for communication between the PFM - Manager host and the PFM - Agent or PFM - RM host

Performance Management executes the connect function and issues a connection request without specifying the source IP address. In this case, depending on the OS specifications, the OS assigns the IP address corresponding to the connection target. In general, the OS assigns the IP address corresponding to the NIC that is used for sending packets to the connection destination. For details, see the OS's TCP/IP control specifications.

Target IP address used for communication between the PFM - Manager host and the PFM - Agent or PFM - RM host

For communication between the PFM - Manager host and the PFM - Agent or PFM - RM host, the target IP address is determined in the order described below.

When the target is not the Status Server service:

  1. IP address used by the target service

  2. IP address specified in the jpchosts file

  3. hosts file or DNS

When the target is the Status Server service:

  1. IP address specified in the jpchosts file

  2. hosts file or DNS

Supplemental information:

All the services of Performance Management, except for the Status Server service, register their IP addresses in PFM - Manager when they start.

When communication is established with a service of Performance Management (other than the Status Server service), the IP address registered in PFM - Manager is used.

• IP address used by the services at the receiving end

This is the IP address used by the services of Performance Management to accept connection. In Performance Management's communication standby processing, data addressed to all IP addresses allocated to the host can be received. If you want to use only a specific IP address in a network environment connected to multiple LANs, you must specify the IP address in the jpchosts file.

Specify the local host name and IP address to be used in the jpchosts file on each host.

For example, if a host has host name hostA and IP addresses 20.108.41.0 and 20.108.41.1 and you want to use 20.108.41.1 as the IP address to be used by the services of Performance Management running on hostA, specify hostA's jpchosts file as follows:

hostA 20.108.41.1

or

hostA 20.108.41.1, 20.108.41.0

Thus, if you want to specify the target IP address used for communication between the PFM - Manager host and the PFM - Agent or PFM - RM host, the jpchosts file must be specified at both the sending and the receiving ends.

The following shows an example of settings.

This example uses the following target IP on each host:

PFM - Manager: IP:C

PFM - Agent (A): IP:E

PFM - Agent (B): IP:G

This example specifies the following information in the jpchosts file on each host:
PFM - Manager
PFM - Manager IP:C IP:B
PFM - Agent(A) IP:E IP:D
PFM - Agent(B) IP:G IP:H
PFM - Agent (A)
PFM - Manager IP:C IP:B
PFM - Agent(A) IP:E IP:D
PFM - Agent(B) IP:G IP:H
PFM - Agent (B)
PFM - Manager IP:C IP:B
PFM - Agent(A) IP:E IP:D
PFM - Agent(B) IP:G IP:H

(c) 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 about how to edit the config.xml file on the PFM - Web Console host, see 5.4.7 Changing PFM - Web Console settings.

This subsection explains how to execute the jpcconf port define command in the interactive mode and the non-interactive mode. For details about the jpcconf port define command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

For details about the port number settings, see the description of firewall routing in the appendixes of the manual Job Management Partner 1/Performance Management Reference.

Supplemental information:

The same port number must be specified in the Name Server service on all hosts in the Performance Management system.

Also, the same port number must be specified in the Status Server service on all hosts in the Performance Management system.

To avoid confusion during operations, also use for other Performance Management services the same port numbers and service names throughout the entire Performance Management system.

■ Executing in the interactive mode

  1. Execute the jpcconf port define command.

    For example, to set the port numbers to fixed values for all services, execute the following command:

    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.

    Setting

    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 and 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 jpcconf 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 of all services, execute the following command:

    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.

■ Executing in the non-interactive mode

  1. Use the jpcconf port define command to create a template for the definition file.

    For example, to set the port numbers to fixed values for all services, execute the following command:

    jpcconf port define -key all -template definition-file-name

    A definition file containing the labels and values for all target services is output. The value of a label is set to the specified port number for a service whose port number has already been specified and to 0 for a service whose port number has not been specified.

  2. Edit the template for the definition file that was created in step 1.

    Edit the settings in the template according to the port numbers that you want to use.

    For details about the specification format of the definition file, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.

    The following shows an example specification of a definition file:

    [Common Definitions]
Definition File Version=0001
 
[Common]
Name Server=22285
Status Server=22350
OpenView=22292
[Manager]
Master Manager=auto
Master Store=auto
Correlator=auto
:
[Windows]
Collector=0
Store=0
:
[Oracle]
[[oracle1]]
Collector=0
Store=0

  3. Use the jpcconf port define command to import the edited definition file.

    Execute the command as shown below. In the -input option, specify the definition file edited in step 2. 

    jpcconf port define -key all -input definition-file-name -noquery

(d) Setting the host name or IP address used for communication with PFM - Web Console and JP1/ITSLM

TCP/IP is used for communication between PFM - Manager and PFM - Web Console. This is true not only when PFM - Manager and PFM - Web Console are located on separate hosts but also when they are located on the same host. Therefore, to run Performance Management, a host name or an IP address that will always be available for communication must be specified on both the Performance Management and the PFM - Web Console hosts.# If this information has not been specified, the first IP address resolved from the PFM - Manager host name or the PFM - Web Console host name will be used.

Similarly, when Performance Management is linked with JP1/ITSLM, a host name or an IP address that will always be available for communication must be specified on both the PFM - Manager and the JP1/ITSLM host. If this information has not been specified, the first IP address resolved from the PFM - Manager host name or the JP1/ITSLM host name will be used.

#

If multiple PFM - Web Consoles connect to PFM - Manager, the specified host name or IP address must be available for communication from all PFM - Web Console hosts.

For example, if Performance Management is configured and run as described below, a host name or an IP address that is always available for communication must be specified in both the PFM - Manager and PFM - Web Console hosts or both the PFM - Manager and JP1/ITSLM hosts.

  • IP address translation (NAT) is used between the PFM - Manager and PFM - Web Console hosts or between the PFM - Manager and JP1/ITSLM hosts.

  • The PFM - Manager host is connected to two networks, a LAN for business and a LAN for monitoring, and Performance Management uses the LAN for monitoring for host-to-host communications.

  • The LAN cable is disconnected from NIC temporarily during maintenance of the hosts (because the HP address assigned to NIC might be disabled).

For details about the host name and IP address settings, see the appendix of the manual Job Management Partner 1/Performance Management Reference as well as the section that describes the host names used for communication between PFM - Manager and PFM - Web Console and between PFM - Manager and JP1/ITSLM.

To Page Top

(2) Setting procedure on the PFM - Web Console host

Use the initialization file (config.xml) to specify and change the network settings on the PFM - Web Console host.

For details about how to edit the config.xml file, see 5.4.7 Changing PFM - Web Console settings.

To Page Top

Trademarks

All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.

(C)opyright 2000-2009, by Object Refinery Limited and Contributors.