Invalid User Id; Proposal Mismatch; Failing To Establish An Ipsec Tunnel - HP 12500 Series Configuration Manual

Invalid user ID

Symptom
Invalid user ID.
Analysis
In IPsec, user IDs identify IPsec tunnels for different data flows. In the HP implementation of IPsec, a user
ID comprises an IP address and a username.
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
Verify that the ACLs in the IPsec policies configured on the interfaces at both ends are correct and mirror
each other. For more information about ACL configuration, see

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, verify that the parameters of the IPsec policies applied on the interfaces
are matched, and that 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 if an IPsec tunnel cannot be established or there is no way to communicate
in the presence of an IPsec tunnel in an unstable network.
If ACLs of both parties are configured correctly, and proposals are also matched, the problem is usually
caused by the reboot of one switch after the IPsec tunnel is established.
"Configuring an
206
ACL."