ZyXEL Communications ZyWall 10W User Manual page 651

LOG MESSAGE
Recv <packet>
Recv <Main or Aggressive> Mode
request from <IP>
Send <Main or Aggressive> Mode
request to <IP>
Invalid IP <Peer local> / <Peer
local>
Remote IP <Remote IP> / <Remote
IP> conflicts
Phase 1 ID type mismatch
Phase 1 ID content mismatch
No known phase 1 ID type found
ID type mismatch. Local / Peer:
<Local ID type/Peer ID type>
ID content mismatch
Configured Peer ID Content:
<Configured Peer ID Content>
Incoming ID Content: <Incoming
Peer ID Content>
Unsupported local ID Type: <%d>
Build Phase 1 ID
Log Descriptions
ZyWALL Series Internet Security Gateway
Chart S-13 IKE Logs
IKE uses ISAKMP to transmit data. Each ISAKMP packet
contains many different types of payloads. All of them show
in the LOG. Refer to RFC2408 – ISAKMP for a list of all
ISAKMP payload types.
The router received an IKE negotiation request from the
peer address specified.
The router started negotiation with the peer.
The peer's "Local IP Address" is invalid.
The security gateway is set to "0.0.0.0" and the router used
the peer's "Local Address" as the router's "Remote
Address". This information conflicted with static rule #d; thus
the connection is not allowed.
This router's "Peer ID Type" is different from the peer IPSec
router's "Local ID Type".
This router's "Peer ID Content" is different from the peer
IPSec router's "Local ID Content".
The router could not find a known phase 1 ID in the
connection attempt.
The phase 1 ID types do not match.
The phase 1 ID contents do not match.
The phase 1 ID contents do not match and the configured
"Peer ID Content" is displayed.
The phase 1 ID contents do not match and the incoming
packet's ID content is displayed.
The phase 1 ID type is not supported by the router.
The router has started to build the phase 1 ID.
DESCRIPTION
S-11