6.6.1 Issues when using JP1/Base in an environment of distinct networks (with jp1hosts2 information)
This section discusses the use of JP1/Base in an environment of distinct networks, based on the system configuration example shown in the following figure. This example 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]](GRAPHICS/ZU040450.GIF)
Consider the following when configuring JP1/Base in such an environment:
-
Whether you will use the JP1/Base communication protocol.
-
How you will want to configure the communication settings of JP1/Base.
These communication settings determine how data other than JP1 events is exchanged between hosts. This includes data for user authentication, distribution of configuration definition information, and remote commands (for JP1/IM). The following two points are important in terms of the communication settings of JP1/Base:
-
Definition of jp1hosts2 information
-
Selection of the communication protocols for sending and receiving data
-
In products such as JP1/IM - Manager and JP1/AJS3 - Manager that reference jp1hosts2 information, if you define jp1hosts2 information, definition of jp1hosts information is ignored. When you define jp1hosts2 information, any jp1hosts information you had defined becomes invalid. If you add jp1hosts2 to an environment that uses jp1hosts information, you need to migrate the environment from jp1hosts to jp1hosts2 information. For details on how to do so, see 6.4.5 Migrating from jp1hosts information to jp1hosts2 information.
When you add an IP address for a host (such as a newly added agent host) to jp1hosts2 information, you do not need to restart JP1/Base, products for which JP1/Base is a prerequisite, and programs that have dependency relationships with JP1/Base. However, you do need to restart these products and programs if you change the communication settings of the event server or change the IP address of a local or remote host in the jp1hosts2 information.
- Organization of this subsection
(1) Whether to adopt the JP1/Base communication protocol
To maintain backward compatibility, JP1/Base version 06-71 and later use the communication settings for version 06-51 at installation. First, consider whether to adopt the JP1/Base communication protocol.
(2) Required settings when performing overwrite installations from JP1/Base version 09-00 or earlier
When you perform an overwrite installation from JP1/Base version 09-00 or earlier, perform the following settings to adopt the JP1/Base communication protocol.
(a) Modify the event server settings file (conf)
To allow the event server to communicate using the communication protocol of JP1/Base, specify <jp1hosts2> in the address component of the ports and remote-server parameters of the event server settings file (conf), and delete the client-bind parameter from the file.
|
Before |
After |
|---|---|
|
ports hostA jp1imevt jp1imevtapi remote-server hostY close 20.0.0.20 client-bind 192.168.0.3 |
ports <jp1hosts2> jp1imevt jp1imevtapi remote-server hostY close <jp1hosts2> |
(b) Modify the API settings file (api)
To allow application programs to communicate with the event server using the communication protocol of JP1/Base, specify <jp1hosts2> in the address component of the server parameter of the API settings file (api).
|
Before |
After |
|---|---|
|
server hostA keep-alive 10.0.0.10 |
server * keep-alive <jp1hosts2> |
(3) Defining jp1hosts2 information (for main part of JP1/Base)
Some OSs do not allow resolution of one host name into multiple IP addresses. If this is the case, you can define jp1hosts2 information that allows JP1/Base to resolve IP addresses.
To allow physical and logical hosts to both use subnet1 and subnet2, assign the IP addresses of the physical and logical hosts to both NICs (use the ifconfig command in UNIX). Then, define the assignments as the jp1hosts2 information.
When you execute ping logicalA on hostX, the name might resolve to 20.0.0.11 in subnet 2, preventing a connection from being established. You can avoid this issue by defining jp1hosts2 information on hostX.
When you define jp1hosts2 information for a physical host, the definition merges with that of the logical host. Only define an IP address in the jp1hosts2 information for a logical host if you need the physical and logical hosts to resolve to different IP addresses.
(4) Selecting the communication protocols for sending and receiving data (for main part of JP1/Base)
When you use JP1/Base on a host connected to multiple networks in a cluster system, you need to change the communication protocol. This subsection briefly describes how to select the communication protocol based on Figure 6-5.
A host connected to multiple networks uses both physical and logical hosts. If you change the reception protocol to the ANY binding method, logical hosts might receive data intended for physical hosts and vice versa. For this reason, you must use the IP binding method as the reception protocol.
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.
(5) Restart JP1/Base
When you change the communication settings of JP1/Base, you need to restart JP1/Base, products for which JP1/Base is a prerequisite, and programs that have dependency relationships with JP1/Base.