Specify port numbers for the file transfer server facility in the /etc/services file. Specify the same port numbers as were specified for JP1/IT Desktop Management 2 - Agent (relay system) (Windows version). The syntax of the /etc/services file is described below.
[ 0netmdmw 1port-number/tcp]
[ 0netmdmclt 1port-number/tcp]
port-number ~ <unsigned integer>((5001-65535))
Specifies a port number for the relay system's file transfer server facility. For the port number, specify a number that is unique within the network system.
netmdmclt port-number/tcp
Specifies the number of the port that receives a start request from a higher-level system.
This specification is required when the system connects to the managing server via a firewall. If this specification is omitted, port number 31001 is assumed.
5.3.2 Setting the host name
Specify the host names described below in the /etc/hosts file.
• JP1/IT Desktop Management 2 - Agent (distribution-destination system)
Specify the host name of the local system and higher-level system. When the system is used in a DNS environment, register the host names of the local system and higher-level system at the name server.
If you use JP1/IT Desktop Management 2 - Agent in a firewall environment, the host name definition differs depending on the firewall environment. For details on the host name definition in a firewall environment, see 5.3.4 Settings when using firewalls.
Note
• If your system uses a name server in a TCP/IP environment, do not specify host name aliases that differ only in the case of the letters, but are otherwise identical. That is, do not specify aliases such as the following:
Example (Invalid network information specified in /etc/named.db.) host.hitachi.com IN A 123.456.0.7 HOSTNAME.hitachi.com IN CNAME host.hitachi.com HostName.hitachi.com IN CNAME host.hitachi.com
• To change the host name or IP address of the local system, make sure that no job is being executed, stop JP1/IT Desktop Management 2 - Agent, and then change the host name or IP address. In addition, delete the files below in either of the following cases: (i) If the host name is specified for the working key in the settings of the managing server, and the host name of the local system (local host name of the OS or DMHOSTNAME of the operating-environment settings file) is changed, or (ii) if the IP address is specified for the working key, and the IP address
of the local system (the local IP address of the OS or DMIPADDR of the operating-environment settings file) is changed.
For systems other than HP-UX: /NETMRDS/rdsprm/.myname For HP-UX: /var/opt/NETMDMW/rdsprm/.myname
5.3.3 Defining the network interface for JP1/IT Desktop Management 2
You can define two or more network connections in the managing server, and use one specifically for JP1/IT Desktop Management 2. Define the connections in a network interface definition file. This enables the network connection to be switched automatically when JP1/IT Desktop Management 2 is used.
In the network interface definition file, specify the network interface to be used by JP1/IT Desktop Management 2. You must also define each network in the /etc/hosts file. For details about setting an /etc/hosts file, see 5.3.2 Setting the host name.
Figure 5-2 shows how to define a network interface definition file.
Figure 5‒2: Defining a network interface definition file
File name of the network interface definition file:
• System other than HP-UX: /NETMRDS/rdsprm/IFCONFIG
• HP-UX: /etc/opt/NETMDMW/rdsprm/IFCONFIG
Rules for defining a network interface definition file:
• Define the network interfaces displayed when you execute the netstat command with the -i option specified.
Write one interface name per line, starting with the interface that has highest priority.
• You can write up to 8 lines. Definitions exceeding this limit are invalid.
• The characters from the start of a line to the next line feed code are interpreted as one line. If more than one network interface name is written in a line, the second and subsequent names are invalid.
• A space or tab at the beginning of a line is invalid. Spaces at the end of a line are also invalid.
• Begin a comment with a slash and asterisk (/*), and end it with an asterisk and slash (*/). To insert a comment in a line in which the network interface name is defined, insert one or more space characters between the network interface name and the comment. Note that the tab symbol cannot be specified here.
• Restart JP1/IT Desktop Management 2 - Agent for the settings in the definition file to take effect.
The following example shows how to define multiple network interface names in the network interface definition file:
In this example, net1 to net8 are the network interface names and the top name has the highest priority. The comments show the priority level of each network interface name.
Network interface selection sequence
The network to be used for JP1/IT Desktop Management 2 is selected in the following sequence:
1. When JP1/IT Desktop Management 2 is used, the system selects the network defined first in the network interface definition file.
2. If the system cannot connect to the first network, the second definition is selected. If still unsuccessful, the system tries each network in turn, in order of priority.
3. If the system cannot connect to any of the defined networks, the retry count set in the RetryCount parameter in the settings file determines the subsequent processing, as follows.
1 set in RetryCount in the settings file:
Connection fails, and JP1/IT Desktop Management 2 is unable to start.
2 or higher set in RetryCount in the settings file:
The system waits for a specified length of time (RetryInterval in the settings file), then tries again to make the connection, starting from the first network in the definition file.
This process is repeated for the number of times set in RetryCount. If connection still fails, JP1/IT Desktop Management 2 is unable to start.
Note
• If a network has frequent connection failures, define a lower priority for that network, or delete the definition.
• To clear the network interface settings, delete the following files:
For systems other than HP-UX:
/NETMRDS/rdsprm/IFCONFIG /NETMRDS/rdsprm/.ifconfig
For HP-UX:
/etc/opt/NETMDMW/rdsprm/IFCONFIG /var/opt/NETMDMW/rdsprm/.ifconfig
• Specify the network interface definition file settings so that JP1/IT Desktop Management 2 - Agent can use a specific network when communicating with the higher-level system specified for ManagingHost in the settings file. In the settings, you cannot define a network used by the higher-level system to communicate with JP1/IT Desktop Management 2 - Agent in situations such as job execution. You cannot control the network used for communication from the higher-level system to JP1/IT Desktop Management 2 - Agent.
• In an environment in which multiple IP addresses are assigned to one network interface, such as in a cluster environment, the first IP address that can be obtained from the defined network interface name is used for communication. If the first IP address cannot be used to communicate with the higher-level system, a communication error occurs. In this case, clear the settings specified in the network interface definition file.
5.3.4 Settings when using firewalls
Figure 5-3 shows an example of the JP1/IT Desktop Management 2 system configuration that uses firewalls.
Figure 5‒3: Example of the JP1/IT Desktop Management 2 system configuration using firewalls
When you distribute a package from the managing server through a firewall, you can install a relay system within the firewall to reduce the number of nodes to be defined in the firewall.
For details on the environment settings of the managing server for distributing packages via a firewall, see the manual of your managing server.