10-20-2023 12:52 PM
I've set it up with the HSRP address but the remote unit gives this error message:
2.2.2.1 is the HSRP address
2.2.2.3 is the real IP address.
Local:1.1.1.1:500 Remote:2.2.2.3:500 Username:2.2.2.1 IKEv2 Negotiation aborted due to ERROR: Failed to authenticate the IKE SA
The profile, keyring and policy all point to the HSRP address. For instance,
crypto ikev2 policy test
match address local 2.2.2.1
proposal test_propose
crypto keyring test_ring
peer testremote
match address 1.1.1.1
identity address 2.2.2.1
pre-shared-key test
crypto ikev2 profile
match address local 2.2.2.1
match identity remote address 1.1.1.1 255.255.255.255
identity local address 2.2.2.1
auth remote pre-share
auth local pre-share
keyring local test_ring
the rest doesn't have a local IP configured and it was working before I converted to having HSRP with the IPSEC tunnel. One of the reasons that I'm using HSRP is that the guide lists it as such:
"The IPsec on the Cisco 8500 Series Catalyst Edge Platform supports only stateless failover. Stateless failover uses protocols such as the Hot Standby Router Protocol (HSRP) to provide primary to secondary cutover and also allows the active and standby VPN gateways to share a common virtual IP address."
Does HSRP work with ikev2?
Solved! Go to Solution.
10-22-2023 09:23 AM - edited 10-22-2023 09:23 AM
How does your configuration look like on the interfaces? Did you remember to put in the "redundancy" keyword on your crypto map?
Ex.
crypto map vpn redundancy VPNHA
Without the redundancy keyword, it'll not utilize the HSRP (or VRRP) configuration in regard to the source IP. Hence, it'll just source it from its own "outside" or crypto interface - and not taking VIP into account.
10-20-2023 10:32 PM
I think it work
You need to use virtual ip of hsrp in ikev2
And use set route reverse
10-21-2023 12:37 AM
as i take this side Cat 8K router - what is other devices ? (what Logs you see there ?)
10-22-2023 09:23 AM - edited 10-22-2023 09:23 AM
How does your configuration look like on the interfaces? Did you remember to put in the "redundancy" keyword on your crypto map?
Ex.
crypto map vpn redundancy VPNHA
Without the redundancy keyword, it'll not utilize the HSRP (or VRRP) configuration in regard to the source IP. Hence, it'll just source it from its own "outside" or crypto interface - and not taking VIP into account.
10-23-2023 09:13 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide