7
IPsec VPN
151
Incorrect pre-shared key
A
problem
with
the
pre
‐
shared
key
on
either
side
has
caused
the
tunnel
negotiation
to
fail.
This
is
perhaps
the
easiest
of
all
the
error
messages
to
troubleshoot
since
it
can
be
only
one
thing,
and
that
is
incorrect
pre
‐
shared
key.
Double
‐
check
that
the
pre
‐
shared
key
is
of
the
same
type
(Passphrase
or
Hex
‐
key)
and
correctly
added
on
both
sides
of
the
tunnel.
Another
reason
for
why
the
SEG
detects
that
the
pre
‐
shared
key
is
incorrect
could
be
because
the
wrong
tunnel
is
triggering
during
tunnel
negotiations.
IPsec
tunnels
are
processed
from
the
top
to
the
bottom
of
the
SEG
tunnel
list
and
are
initially
matched
against
the
remote
gateway.
An
example
is
if
there
is
a
roaming
tunnel
that
uses
all
‐
nets
as
its
remote
gateway.
This
tunnel
will
trigger
before
your
defined
tunnel
if
it
is
above
it
in
the
tunnel
list.
Ike_invalid_payload, Ike_invalid_cookie
In
this
case
the
IPsec
engine
in
the
SEG
receives
an
IPsec
IKE
packet
but
is
unable
to
match
it
against
an
existing
IKE.
If
a
VPN
tunnel
is
only
established
on
one
side,
this
can
be
the
resulting
error
message
when
traffic
arrives
from
a
tunnel
that
does
not
exist.
An
example
would
be
if,
for
some
reason,
the
tunnel
has
only
gone
down
from
the
initiator
side
but
the
terminator
still
sees
it
as
up.
It
then
tries
to
send
packets
through
the
tunnel
but
when
they
arrive
at
the
initiator
it
will
drop
them
since
no
matching
tunnel
can
be
found.
Simply
remove
the
tunnel
from
the
side
that
believes
it
is
still
up
to
solve
the
immediate
problem.
An
investigation
as
to
why
the
tunnel
only
went
down
from
one
side
is
recommended.
It
could
be
that
DPD
and/or
Keep
‐
Alive
is
only
used
on
one
side.
Another
possible
cause
could
be
that
even
though
it
has
received
a
DELETE
packet,
it
has
not
deleted/removed
the
tunnel.
Payload_Malformed
This
problem
is
very
similar
to
the
Incorrect
pre
‐
shared
key
problem
described
above.
A
possible
reason
is
that
the
PSK
is
of
the
wrong
TYPE
on
either
side
(Passphrase
or
Hex
key).
Verify
that
you
are
using
the
same
type
on
both
sides
of
the
IPsec
tunnel.
If
one
side
is
using
Hex
and
the
other
Passphrase,
this
is
most
likely
the
error
message
that
you
will
receive.
No public key found
This
is
a
very
common
error
message
when
dealing
with
tunnels
that
use
certificates
for
authentication.
Troubleshooting
this
error
message
can
be
very
difficult.
It
is
very
important
to
keep
in
mind
that
when
dealing
with
certificates
it
may
be
required
to
combine
the
output
from
ike
‐
snoop
with
standard
SEG
event
logs
because
ike
‐
snoop
does
not
give
that
much
information
about
certificates.
A
good
suggestion
before
starting
to
troubleshoot
certificate
based
tunnels
is
to
first
configure
it
as
a
PSK
tunnel
and
then
verify
that
it
can
successfully
establish,
then
move
on
to
using
certificates.
(Unless
the
configuration
type
prohibits
that).