1 |
Decryption failed |
This problem might be caused by a transmission
error or by a sender error. For manual tunnels, this might be the
result of a policy definition error. |
2 |
AH authentication failed |
This problem might be caused by a transmission
error or by a sender error. For manual tunnels, this might be the
result of a policy definition error. This problem might also be caused
by a failure in an ICSF service. If so, the specific failure will
be reported on the ICSF Return Code and ICSF Reason Code fields.
|
3 |
ESP authentication failed |
This problem might be caused by a transmission
error or by a sender error. For manual tunnels, this might be the
result of a policy definition error. This problem might also be caused
by a failure in an ICSF service. If so, the specific failure will
be reported on the ICSF Return Code and ICSF Reason Code fields.
|
4 |
Out of Replay window |
A transmission error might have occurred or
a packet might have been delayed. |
6 |
Unknown authentication algorithm |
An internal error occurred while authenticating
the packet. |
7 |
Unknown encryption algorithm |
An internal error occurred while decrypting
the packet. |
8 |
No tunnel found for AH SPI |
This message might be the result of a timing
condition. On tunnel activation this message might be seen if packets
are sent while one tunnel endpoint has the tunnel installed and the
other tunnel endpoint does not. In this case, this is a transient
condition and no action is required. For manual tunnels, this might
be the result of a policy definition error. This message can also
be the result of a transmission error or a sender error.
|
9 |
No tunnel found for ESP SPI |
This message might be the result of a timing
condition. On tunnel activation this message might be seen if packets
are sent while one tunnel endpoint has the tunnel installed and the
other tunnel endpoint does not. In this case, this is a transient
condition and no action is required. For manual tunnels, this might
be the result of a policy definition error. This message can also
be the result of a transmission error or a sender error.
|
10 |
More than one tunnel matched during decapsulation |
This might be due to one of the following problems:
- For manual tunnels, there is an error in the spi values specified
in the policy definition.
- The packet is protected by nested tunnels and z/OS is the endpoint for more than 1 of these
tunnels. This configuration is not supported by z/OS
|
11 |
IPSec headers did not match tunnel definition |
The policy, either the AH policy, the ESP policy,
or both, defined for the tunnel did not match the IPSec protocols
in the packet. For example, the policy specified encryption was required
but no ESP header was found. For manual tunnels, this is most likely
a policy definition error. |
12 |
AH and ESP headers not in expected sequence |
For manual tunnels, this might be a result
of a policy definition error. |
13 |
Storage shortage |
Storage to complete the request is not currently
available. Until the storage shortage is relieved, decapsulation
will fail. |
14 |
Encrypted data length is not a multiple of 8
bytes or 16 bytes if AES encryption or decryption is being used |
This problem might be caused by a transmission
error or by faulty encryption of the data by the sender. |
15 |
No data was sent in the packet |
This problem might be caused by a transmission
error or by a sender error. |
16 |
The packet is too small to contain the AH or
ESP header |
This problem might be caused by a transmission
error or by a sender error. |
17 |
Invalid IP option length |
This problem might be caused by a transmission
error or by a sender error. |
18 |
UDP Encapsulation mismatch |
Either the packet was UDP-encapsulated and the
tunnel did not indicate UDP encapsulation or the packet was not UDP-encapsulated
and the tunnel expected UDP encapsulation. |
19 |
Nested UDP-encapsulated headers |
This configuration is not supported by z/OS. |
24 |
Failure in ICSF Service |
The ICSF Return Code and the ICSF Reason Code
fields contain the return and reason codes that were returned from
the ICSF service. |
25 |
ICSF is not available |
Either ICSF is not active or it has not completed
initialization. |
26 |
Encapsulation mismatch |
The packet encapsulation did not match the local
tunnel policy. |