Hitachi

JP1 Version 12 JP1/Base User's Guide


6.5.1 Issues when using JP1/Base in an environment of distinct networks (with jp1hosts information)

This subsection describes some issues on using JP1/Base in an environment of distinct networks, based on the system configuration example shown in the following figure. This configuration assumes that the physical host hostA and the logical host logicalA are used as manager hosts, and hostX and hostY are used as agent (or client) hosts. In this configuration, the user can log in to JP1/IM - Manager on hostA from JP1/IM - View on hostX to monitor hostY and to execute automated actions on hostY.

Figure 6‒4: Example system configuration when using JP1/Base in an environment of distinct networks (with jp1hosts information)

[Figure]

The following is a list of things to consider for the settings:

Note that when you change the communication settings, you need to restart JP1/Base, products for which JP1/Base is a prerequisite, and programs that have dependency relationships with JP1/Base.

Organization of this subsection

(1) Whether you will adopt the JP1/Base communication protocol.

After installation, JP1/Base initially operates with the communication settings supported in version 06-71 or later. You must first decide whether you will adopt the JP1/Base communication protocol.

(2) Definition of jp1hosts information (for the main part of JP1/Base)

Some OSs do not allow resolution of one host name into multiple IP addresses. If this is the case, JP1/Base can resolve IP addresses by defining its own hosts information. In this case, you can define jp1hosts information that allows JP1/Base to resolve IP addresses.

To enable both physical and logical hosts to use subnet1 and subnet2, assign IP addresses of physical and logical hosts to both NICs (use the ifconfig command in UNIX). Then, the assignments must be defined as the jp1hosts information.

When you execute ping logicalA on hostX, it might detect 20.0.0.11 of subnet2 and you might not be able to establish communication. This case can also be resolved by defining jp1hosts on hostX.

Note

Define the jp1hosts information only when host names cannot be resolved with hosts and DNS settings.

(3) Selection of communication protocol to transmit/receive data (for the main part of JP1/Base)

You need to change the communication protocol when you use a host connected to multiple networks in a cluster system. This subsection briefly describes the selection of the communication protocol based on Figure 6-4.

A host connected to multiple networks uses both physical and logical hosts. If you change the reception setting to the ANY binding method, the logical hosts might receive the data directed to the physical hosts and vice versa. Therefore, the reception setting must be the IP binding method.

On the other hand, the transmission setting must be the ANY binding method because the IP binding method might send data only to subnet1 or subnet2.

In general, if you set JP1/Base for use in a cluster system, both transmission and reception settings of the communication protocol are set to the IP binding method, except for an event service. Therefore, you need to change the transmission setting to the ANY binding method. To change the communication settings for JP1/Base, use the jbssetcnf command to apply the contents of the communication protocol settings file to the common definition information.

For details on communication protocols, see 6.3 Setting up JP1/Base communication protocols. For details on communications protocols in a cluster setup, see H.12 Communication protocols in a cluster setup.

(4) Communication settings of event services

In the case of event services, edit the event server settings file (conf) to change the communication settings described in (2) Definition of jp1hosts information (for the main part of JP1/Base) and (3) Selection of communication protocol to transmit/receive data (for the main part of JP1/Base). For details, see 6.5.3 Changing communication settings of event services.

Note

If you set JP1/Base for use in a cluster system, <jp1hosts2> is specified in the ports and remote-server parameters of the event server settings file (conf) on the logical host. If jp1hosts information is used under that setting, the event service references jp1hosts information. However, if <jp1hosts2> is specified in the server parameter of the API setting file (api), programs that register and obtain JP1 events, such as a log file trapping function, do not reference jp1hosts information when connecting with an event service. Therefore, communication settings for the event service and for programs that register and obtain JP1 events might not match. Change communication settings to use jp1hosts2 information, or change the communication settings for the event service to that used in V9 or earlier.

(5) Restart JP1/Base

When you change the communication settings, you need to restart JP1/Base, products for which JP1/Base is a prerequisite, and programs that have dependency relationships with JP1/Base.