Refer to the exhibit. A network security administrator receives this error message after configuring a site-to-site IPsec VPN between two sites What is the solution to this problem?
```
IPSEC(validate_proposal): invalid local address 192.168.10.1
ISAKMP (0:3): atts not acceptable. Next payload is 0
ISAKMP (0:3): SA not acceptable!
```

Question

Accepted Answer

D. Crypto map must be applied to correct interface. The error 'invalid local address 192.168.10.1' occurs when the router cannot find the configured local VPN endpoint IP on the interface where the crypto map is applied. Applying the crypto map to the interface that actually holds 192.168.10.1 resolves the binding mismatch and allows ISAKMP to proceed with negotiation.

Answer

A. The transport set must match between sites. A transform set mismatch generates errors referencing unsupported encryption or hash algorithms, not an invalid local address binding.

Answer

B. IPsec policy must match between sites. IPsec policy mismatches between peers produce negotiation failures citing specific unacceptable proposal attributes, not a missing local address error.

Answer

C. ISAKMP policy must match between sites. ISAKMP policy mismatches result in errors about differing authentication or encryption method proposals, not the 'invalid local address' condition shown in the exhibit.

Refer to the exhibit. A network security administrator receives this error message after configuring a site-to-site IPsec VPN between two sites What is the solution to this problem? ``…

Question

Options

How the community answered

Why each option

Topics

Community Discussion