H3C Technologies H3C SecPath F1000-E - Manual (Page 161)

149
Analysis
In IPsec, user IDs are used to identify data flows and to set up different IPsec tunnels for different data
flows. Now, the IP address and username are used as the user ID.
The following is the debugging information:
got NOTIFY of type INVALID_ID_INFORMATION
Or
drop message from A.B.C.D due to notification type INVALID_ID_INFORMATION
Solution
Check that the ACLs in the IPsec policies configured on the interfaces at both ends are compatible.
Configure the ACLs to mirror each other. For more information about ACL mirroring, see "Configuring
IPsec."
Proposal mismatch
Symptom
The proposals mismatch.
Analysis
The following is the debugging information:
got NOTIFY of type NO_PROPOSAL_CHOSEN
Or
drop message from A.B.C.D due to notification type NO_PROPOSAL_CHOSEN
The two parties in the negotiation have no matched proposals.
Solution
For the negotiation in phase 1, look up the IKE proposals for a match. For the negotiation in phase 2,
check whether the parameters of the IPsec policies applied on the interfaces are matched, and whether
the referred IPsec proposals have a match in protocol, encryption and authentication algorithms.
Failing to establish an IPsec tunnel
Symptom
The expected IPsec tunnel cannot be established.
Analysis
Sometimes this may happen that an IPsec tunnel cannot be established or there is no way to
communicate in the presence of an IPsec tunnel in an unstable network. According to examination results,
however, ACLs of both parties are configured correctly, and proposals are also matched.
In this case, the problem is usually caused by the reboot of one SecPath after the IPsec tunnel is
established.
Solution
• Use the display ike sa command to check whether both parties have established an SA in phase 1.
• Use the display ipsec sa policy command to check whether the IPsec policy on the interface has
established IPsec SA.