Applicable versions and levels
Windows versions: V5.0L30 or later
Solaris versions: 5.2 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 10.0 or later
AIX versions: 10.0 or later
Action
Points to check
Have multiple logical IP addresses with different network segments been allocated to the schedule server?
Cause
The mechanism is that, after the request to start the network job is made by the schedule server to the execution server, the job runs on the execution server, and when the job ends, a completion notification is sent from the execution server to the schedule server.
If multiple logical IP addresses with different network segments have been allocated to the schedule server, the IP address of a network segment to which the execution server does not belong may be used as the IP address that is used as the recipient for the completion notification. In this case, the execution server cannot send the job completion notification.
However, the checking of the job status on the execution server is performed at fixed intervals by the schedule server, therefore the schedule server is able to recognize that a job has ended. For this reason, it may take a while from the end of the job on the execution server until the schedule server recognizes this.
Action method
In the node name definition file of the execution server, define the logical IP address of a schedule server that the execution server can use for communication.
Use the following to define the node name definition file:
V11.0L10/11.0 or later
In the Cluster settings tab of the Define Operating Information window, define the schedule server node name in Nodes of Server settings.
V5.0L30/5.2 to V10.0L21/10.1
Select Define node names of the cluster system in the Options tab of the Define Operating Information window, and define the node name of the schedule server in the cluster configuration in Node Name 1: and Node Name 2:.
