Job Management Partner 1/Software Distribution Description and Planning Guide
In an environment that uses host names as ID keys for operations, if the connection to the DNS server is interrupted for some reason (for example, because the system is a quarantined system), the client might no longer be able to resolve the name of a connection-target higher system. In such a situation, the client can resolve the name from the IP address in the communications protocol when it receives execution request information from the connection-target higher system. If the environment is such that it prevents the client from using this method to resolve the name of the connection-target higher system, the client can still poll for jobs and send inventory information to the higher system. During this time, the client will recognize the higher system that originates the execution request as the connection target.
To use this function, the following settings must be specified during client setup:
When this function is enabled, a file for higher system addresses is automatically created on the client when it receives an execution request from a higher system. This file contains a mapping of the IP addresses and host names of the higher systems. Subsequently, the client uses the information in this file to perform name resolution and connect to the higher system.
Normally, there is no need to edit the file for higher system addresses. However, in an environment in which the name of the higher system cannot be resolved, you will need to create the file before you initially install a host name-keyed client.
For details about the settings to use when initially installing a host-name keyed client in an environment in which the name of the higher system cannot be resolved, see (1) Settings to use when initially installing a client in an environment in which the name of the higher system cannot be resolved. For details about the syntax required in the file for higher system addresses, see (2) Syntax in the file for higher system addresses.
If you initially install a host name-keyed client in an environment in which the name of the higher system cannot be resolved, the client will not be recognized as a target because it cannot connect to a higher system. In such a case, create a file for higher system addresses beforehand, and use one of the following methods to save the file at the client.
JP1/Software-Distribution-installation-directory\MASTER\DB
Setting | Specification |
---|---|
Copy file | File for higher system addresses you created |
To directory | %NETMDMP%\MASTER\DB |
When you restart the client after setup has been completed, the client will connect to the higher system based on the information in the file for higher system addresses.
The file for higher system addresses contains mappings for multiple connection targets. The client connects to the higher systems by means of the IP addresses corresponding to the host names as described in this file.
The following shows the syntax in the file for higher system addresses:
[host-name] IPaddress=IP-address [#-filecheck] key=Programcheck
[host001] IPaddress=10.100.100.20 [host005] IPaddress=10.100.100.15 [host007] IPaddress=10.100.100.57 [#-filecheck] key=Programcheck |
Note the following points when creating a file for higher system addresses:
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.