300-730 · Question #95
Refer to the exhibit. An IKEv2 site-to-site tunnel between an ASA and a remote peer is not building successfully. What will fix the problem based on the debug output?
The correct answer is C. Correct crypto access-list on both VPN devices. An IKEv2 site-to-site tunnel fails when crypto ACLs are not mirrored on both peers, producing a traffic selector mismatch during IKE negotiation.
Question
Options
- AEnsure crypto IPsec policy matches on both VPN devices.
- BInstall the correct certificate to validate the peer.
- CCorrect crypto access-list on both VPN devices.
- DSpecify the peer IP address in the tunnel group name.
How the community answered
(60 responses)- A25% (15)
- B13% (8)
- C55% (33)
- D7% (4)
Why each option
An IKEv2 site-to-site tunnel fails when crypto ACLs are not mirrored on both peers, producing a traffic selector mismatch during IKE negotiation.
IPsec transform-set mismatches produce a phase-2 proposal rejection error, which is a distinct failure mode from the traffic selector error caused by ACL mismatches.
Certificate validation failures generate IKE authentication errors during peer identity verification, not traffic selector errors seen in a crypto ACL debug context.
In IKEv2/IPsec, both peers must have mirror-image crypto ACLs defining the same interesting traffic; a mismatch causes a TS_UNACCEPTABLE error because the traffic selectors proposed by one peer do not match what the other peer expects. Correcting the crypto ACLs on both devices aligns the proxy identities and allows the IKE_AUTH exchange to complete successfully.
Specifying the peer IP in the tunnel group name resolves tunnel group lookup failures on the ASA but does not correct a traffic selector mismatch caused by mismatched ACLs.
Concept tested: IKEv2 IPsec crypto ACL proxy identity matching on ASA
Source: https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/113819-config-asa-00.html
Topics
Community Discussion
No community discussion yet for this question.