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 number | Message ID | Reason code | Additional information on the meaning of communication error codes |
---|---|---|---|
1 | KFPQ48301-W | 0201 | The 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. |
2 | 0202 | ||
3 | 0301 | ||
4 | 0302 | ||
5 | 0303 | ||
6 | KFPQ58204-E | 0201 | |
7 | 0301 | ||
8 | 0302 | ||
9 | 0304 | ||
10 | 0305 | ||
11 | KFPQ58303-E | 0001 | |
12 | 0002 | ||
13 | Other than those above | ||
14 | KFPQ40365-E | 2000 | The 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 codes | Meaning | Cause and corrective action | |
---|---|---|---|
In Linux: | In AIX: | ||
-306 | -306 | Connection with the processes of other systems failed as a result of one of the following causes:
| Refer to 1 under Major category in Table 4-9. Alternatively, refer to 3 under Major category in Table 4-9. |
-307 | -307 | A timeout while waiting for a sending port to become available occurred as a result of one of the following causes:
| Refer to refer to 3 under Major category in Table 4-9. |
-317 | -317 | There is a shortage of receiving buffers in the processes of other systems as a result of one of the following causes:
| Refer to refer to 2 under Major category in Table 4-9. |
-339 | -339 | The maximum number of retries has been exceeded as a result of one of the following causes:
| 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:.
| Refer to 1 under Major category in Table 4-9. |
-40090 | -40059 | The maximum message length for the UDP protocol was exceeded as a result of the following cause:
| |
-40100 -40101 -40113 | -40070 -40078 -40081 | Network errors occurred due to one of the following causes:
| |
-41390 | -41390 | Packet sizes do not match, due to the following cause:
| |
-41391 | -41391 | The processes of the other party cannot be received as a result of the following cause:
| |
Other than those above | Not applicable | Contact 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
Classification | Cause | Corrective action | |
---|---|---|---|
Major category | Minor category | ||
1 | 1 | Host 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. |
2 | Port 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. | |
3 | Communication 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 | |
4 | Multicast send/receive communication failed.#2 Possible causes are as follows:
For a LAN used for sending
| Re-examine the -a option of the pdqmyudpsnddef and the -m option of the pdqclgrpdef operand, and set appropriate values. | |
5 | The router between the running system and the standby system does not support multicast.#2 | Check whether the router supports multicast. If it does not, change to a router that does. | |
6 | The number of routers between the running and standby systems is greater than the value specified for the -T option of the pdqmyudpsnddef operand.#2 | For the -T option of the pdqmyudpsnddef operand, specify a value larger than the number of routers. | |
7 | Processes 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. | |
8 | Packet sizes vary between the running system and the standby system. | Specify the same value in the pdq_rpc_udp_packet_size operand. | |
9 | The 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. | |
10 | Route information has not been set correctly. The following two conditions overlap.#2
| Perform one of the following corrective actions.
| |
2 | 1 | The 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. |
2 | There is a shortage of OS memory. | Expand real memory or swapping size. | |
3 | 1 | The performance of the network devices being used (NIC, router, etc.) is poor. | Use high-speed network devices. |
2 | Communication 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. | |
3 | The 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 | |
4 | The 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 | |
5 | Because 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. | |
6 | Network 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. | |
7 | Multiple 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. | |
8 | The 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. | |
9 | Overhead is large due to line trace acquisition. | Re-examine the pdq_rpc_udp_linetrace operand, and restrain the acquisition of unnecessary line traces. |