4.4 Communication error codes

The error message output during a communication error includes the communication error code as additional information. You can eliminate the communication error by taking corrective action according to the communication error code.

The tables below show combinations of message IDs and reason codes output during communication errors, as well as additional information on the meanings of the communication error codes.

Table 4-7 List of messages containing communication error codes

Section numberMessage IDReason codeAdditional information on the meaning of communication error codes
1KFPQ48301-W0201The communication error code is output as detail-code in this message. For information on the meanings of the communication error codes, refer to Table 4-8.
20202
30301
40302
50303
6KFPQ58204-E0201
70301
80302
90304
100305
11KFPQ58303-E0001
120002
13Other than those above
14KFPQ40365-E2000The communication error code is output as maintenance-information-1 in this message. For information on the meanings of the communication error codes, refer to Table 4-8.

The following table shows the meaning of the communication error codes.

Note that causes of communication errors that can potentially occur online as a result of a heavy network load or other causes are listed in Table 4-9 under Major category 1, Minor category 7, as well as under Major categories 2 and 3.

Table 4-8 Meanings of communication error codes

Communication error codesMeaningCause and corrective action
In Linux:In AIX:
-306-306Connection with the processes of other systems failed as a result of one of the following causes:
  • Invalid definitions
  • Invalid network configuration
  • A temporary heavy load on the network or a slowdown
Refer to 1 under Major category in Table 4-9. Alternatively, refer to 3 under Major category in Table 4-9.
-307-307A timeout while waiting for a sending port to become available occurred as a result of one of the following causes:
  • Communication performance is poor.
  • There are no ports for sending.
Refer to refer to 3 under Major category in Table 4-9.
-317-317There is a shortage of receiving buffers in the processes of other systems as a result of one of the following causes:
  • The maximum memory of the XDS has been exceeded.
  • The maximum memory of the machine has been exceeded.
Refer to refer to 2 under Major category in Table 4-9.
-339-339The maximum number of retries has been exceeded as a result of one of the following causes:
  • Communication performance is poor.
  • Communication parameters are invalid.
Refer to 3 under Major category in Table 4-9.
-341
-378
-341
-378
The processes of the other party were disconnected as a result of the following cause:.
  • The processes of the other party are down or have slowed down.
Refer to 1 under Major category in Table 4-9.
-40090-40059The maximum message length for the UDP protocol was exceeded as a result of the following cause:
  • Invalid definitions
-40100
-40101
-40113
-40070
-40078
-40081
Network errors occurred due to one of the following causes:
  • NIC error
  • Invalid network settings
-41390-41390Packet sizes do not match, due to the following cause:
  • Invalid definitions
-41391-41391The processes of the other party cannot be received as a result of the following cause:
  • Invalid timing
Other than those aboveNot applicableContact the customer support center.

The following table shows the causes and corrective actions to take for communication errors.

Table 4-9 Causes and corrective actions to take for communication errors

ClassificationCauseCorrective action
Major categoryMinor category
11Host names of the running system or standby system vary.Re-examine the LAN host name specified in the -n option of the pdqclgrpdef operand, and correct any errors.
2Port numbers vary between the running system and the standby system.Specify the same value for the port number of the -p option of the pdqclgrpdef operand.
3Communication between the running system and the standby system is not possible.Re-examine network devices (NIC, router, cable, etc.) and network settings (routing information, ifconfig, etc.), and check communication by using the ping command and the like.#1
4Multicast send/receive communication failed.#2
Possible causes are as follows:
  • The LAN specifications are wrong.
  • Different LANs have been specified for sending and receiving.
In a multi-homed host configuration, one LAN is used for multicast send/receive communication, so select from the following methods.
For a LAN used for sending
  • When automatically selected by the OS:
    Omit the -a option of the pdqmyudpsnddef operand
  • When explicitly specified in the XDS server definitions:
    Specify the host name of the LAN adapter in the -a option of the pdqmyudpsnddef operand
For a LAN used for receiving
  • When automatically selected by the OS:
    Omit the host name of the LAN adapter in the -m option of the pdqclgrpdef operand
  • When explicitly specified in the XDS server definitions:
    Specify the host name of the LAN adapter in the -m option of the pdqclgrpdef operand
Re-examine the -a option of the pdqmyudpsnddef and the -m option of the pdqclgrpdef operand, and set appropriate values.
5The router between the running system and the standby system does not support multicast.#2Check whether the router supports multicast. If it does not, change to a router that does.
6The number of routers between the running and standby systems is greater than the value specified for the -T option of the pdqmyudpsnddef operand.#2For the -T option of the pdqmyudpsnddef operand, specify a value larger than the number of routers.
7Processes of the other system have not started, are shut down, have just started up, or are slowed down.Check the status of other system processes.
8Packet sizes vary between the running system and the standby system.Specify the same value in the pdq_rpc_udp_packet_size operand.
9The maximum UDP message length has been exceeded.For the pdq_rpc_udp_packet_size operand, set a value equal to or less than the maximum UDP message length#1 of the applicable machine.
10Route information has not been set correctly. The following two conditions overlap.#2
  • There was an omission of the -a option of the pdqmyudpsnddef operand in the XDS server definitions (host name of the LAN adapter)
  • There is no route information for the host name of the host group specified in the -m option of the pdqclgrpdef operand in the XDS server definitions
Perform one of the following corrective actions.
  • Set the default route information in the OS routing table.
  • In the routing table, specify the route information for the host name of the host group specified in the -m option of the pdqclgrpdef operand.
  • Specify the -a option of the pdqmyudpsnddef operand.
21The XTC pool size being used exceeds the maximum value.Increase the specification value for the pdq_memory_xtc_limit_size operand, or specify it as 0.
2There is a shortage of OS memory.Expand real memory or swapping size.
31The performance of the network devices being used (NIC, router, etc.) is poor.Use high-speed network devices.
2Communication overhead is large because the MTU size is small.If the network supports jumbo frames, change to jumbo frames#1, and increase the pdq_rpc_udp_packet_size operand.
3The socket receiving buffer size is too small, so multiple receiving packets have been lost (buffer overflow).Increase the specification value for the -B option of the pdqclgrpdef operand. Note that you cannot increase socket receiving buffers past the maximum for the OS, so expand the maximum for the OS as needed.#1
4The socket receiving buffer size is too small, so multiple instances of waiting for available sending buffers have occurred.Increase the specification value for the -b option of the pdqmyudpsnddef operand. Note that you cannot increase socket sending buffers past the maximum for the OS, so expand the maximum for the OS as needed.#1
5Because there are few sending ports, there are multiple incidences of waiting for sending ports to become available between processing threads.Increase the value of -p in pdqmyudpsnddef operand or the value of the -P operand.
6Network performance is poor, so retries are repeated in the current resend count and resend interval.Increase the specification value for the -R, -w, and -W options in the pdqmyudpsnddef operand.
7Multiple processing threads are concurrently performing mass updates of the memory database.Increase the specification value for the -p option of the pdqclgrpdef operand. Note that if you increase the receiving threads, resources increase and processing conflict may occur between receiving threads.
8The delivery check size is too large, so multiple receiving packets have been lost (buffer overflow).Decrease the specification value for the pdq_rpc_udp_lmsg_deliverychk_sz operand or the pdq_rpc_udp_msg_deliverychk_sz operand.
9Overhead is large due to line trace acquisition.Re-examine the pdq_rpc_udp_linetrace operand, and restrain the acquisition of unnecessary line traces.
#1
For details, refer to the OS documentation.
#2
Applies only when specifying the -m option for the pdqclgrpdef operand in the XDS server definitions to perform multicast communication between the running system and the standby system.