F5030(V7) L2TP OVER IPSEC拨号不成功问题

三、debug ike/ipsec分析：

Debug能看到两个ip之间的正常交互报文，ipsec第二阶段协商失败，提示INVALID_ID_INFORMATION

*Oct 10 12:09:49:500 2018 H3C IKE/7/EVENT: -COntext=1; vrf = 0, local = 59.x.x.245, remote = 27.x.x.192/27998

IPsec SA state changed from IKE_P2_STATE_INIT to IKE_P2_STATE_GETSP.

*Oct 10 12:09:49:500 2018 H3C IPSEC/7/EVENT: -COntext=1;

 Could not find tunnel, ike profile name is 1.

*Oct 10 12:09:49:500 2018 H3C IPSEC/7/EVENT: -COntext=1;

 Could not find tunnel, ike profile name is 1.

*Oct 10 12:09:49:500 2018 H3C IKE/7/EVENT: -COntext=1; Received message from ipsec, message type is 10.

*Oct 10 12:09:49:500 2018 H3C IKE/7/ERROR: -COntext=1; vrf = 0, local = 59.x.x.245, remote = 27.x.x.192/27998

Failed to get IPsec policy for phase 2 responder. Delete IPsec SA.

*Oct 10 12:09:49:500 2018 H3C IKE/7/ERROR: -COntext=1; vrf = 0, local = 59.x.x.245, remote = 27.x.x.192/27998

Failed to negotiate IPsec SA.

*Oct 10 12:09:49:500 2018 H3C IKE/7/EVENT: -COntext=1; Delete IPsec SA.

*Oct 10 12:09:49:501 2018 H3C IKE/7/PACKET: -COntext=1; vrf = 0, local = 59.x.x.245, remote = 27.x.x.192/27998

Encrypt the packet.

*Oct 10 12:09:49:501 2018 H3C IKE/7/PACKET: -COntext=1; vrf = 0, local = 59.x.x.245, remote = 27.x.x.192/27998

Construct notification packet: INVALID_ID_INFORMATION.

且查看ike报文情况