I actually had phase 2 complete earlier today although we've been having problems getting this to work for a while now. TAC has remoted in and looked at it and I still have an open call for it.
I was hoping this might be something that someone here has seen before.
Here's what I'm seeing in the log:
8502 07/31/2003 15:02:17.110 SEV=5 IKE/68 RPT=17726 192.31.X.X
Group [192.31.X.X]
Received non-routine Notify message: Invalid ID info (18)
8503 07/31/2003 15:02:17.110 SEV=4 IKEDBG/0 RPT=11862
QM FSM error (P2 struct &0x483ca28, mess id 0xd39022fa)!
8504 07/31/2003 15:02:17.110 SEV=4 IKEDBG/65 RPT=19526 192.31.X.X
Group [192.31.X.X]
IKE QM Initiator FSM error history (struct &0x483ca28)
<state>, <event>:
QM_DONE, EV_ERROR
QM_WAIT_MSG2, EV_TIMEOUT
QM_WAIT_MSG2, NullEvent
QM_SND_MSG1, EV_SND_MSG
8509 07/31/2003 15:02:17.110 SEV=5 IKE/68 RPT=17727 192.31.X.X
Group [192.31.X.X]
Received non-routine Notify message: Invalid ID info (18)
8510 07/31/2003 15:02:17.120 SEV=5 IKE/68 RPT=17728 192.31.X.X
Group [192.31.X.X]
Received non-routine Notify message: Invalid ID info (18)
8511 07/31/2003 15:02:17.130 SEV=5 IKE/68 RPT=17729 192.31.X.X
Group [192.31.X.X]
Received non-routine Notify message: Invalid ID info (18)
8512 07/31/2003 15:02:18.100 SEV=4 IKE/41 RPT=7145
IKE Initiator: New Phase 2, Intf 2, IKE Peer 192.31.X.X
local Proxy Address 161.113.X.X, remote Proxy Address 10.2.0.0,
SA (L2L: TIRR)
I'm not sure why the remote proxy address is coming across as 10.2.0.0 when it is actually coming from or going to a specific address. Regardless Phase 2 is not completing.
TIA
