1 |
Encryption error |
An error occurred while trying to encrypt an
outbound packet. |
2 |
AH authentication error |
An error was encountered when trying to authenticate
an outbound packet. 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 error |
An error was encountered when trying to authenticate
an outbound packet. 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 |
Maximum packet exceeded |
The addition of ESP headers will cause the maximum
packet size to be exceeded. |
5 |
Lifesize exceeded |
The number of bytes in the outbound packet will
cause the lifesize specification to be exceeded for the tunnel. |
6 |
Unknown authentication algorithm |
An internal error occurred while authenticating
the packet. |
7 |
Unknown encryption algorithm |
An internal error occurred while encrypting
the packet. |
8 |
No tunnel found |
A tunnel was not found for the specified tunnel
ID. |
9 |
Sequence numbers were not obtained |
Sequence numbers could not be obtained from
the coupling facility for a distributed tunnel. |
10 |
IP header not valid |
The IP header of the packet being encapsulated
does not contain the same source and destination IP address as specified
in the tunnel; transport mode is in effect. |
13 |
Storage shortage |
Storage to complete the request is not currently
available. Until the storage shortage is relieved, encapsulation
will fail. |
24 |
Encryption 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 |
Version mismatch |
The IP version of the packet did not match the
IP version of the tunnel. |
27 |
Encapsulation using transport mode not valid
for routed traffic |
Encapsulation using transport mode was requested
but the packet that is being processed is a routed packet. This
is most likely the result of a policy definition error. For
manual tunnels, this might occur if routed traffic matches a filter
rule referencing an IpManVpnAction statement that specified the transport
method HowToEncap. For IPv6, this might occur if a routing header
contains an intermediate hop that routed the packet back through the
packet's originating system. The tunnel endpoints matched the packet;
however, the packet has been routed to this system.
|
28 |
Sequence number wrapped |
The sequence number has wrapped, which indicates
that the tunnel has expired. The tunnel will be deleted. |