Using 2 ISAKMP policies, if policy 10 fails, try policy 20
I use pre-shared keys for authentication, and I have written an automated script for periodically updating (rotating) keys. However, sometimes the rotation fails and I get paged in the middle of the night. So I had an idea:
I was thinking that if the pre-share policy fails, the next policy would be tried. This doesn't seem to be the case. When I test in the lab by putting different pre-shared keys on the peers, I simply get the message "Nov 2 08:50:05.525: %CRYPTO-4-IKMP_BAD_MESSAGE: IKE message from 10.1.0.1 failed its sanity check or is malformed"
Re: Using 2 ISAKMP policies, if policy 10 fails, try policy 20
Thanks for the response . . . but I don't follow. You're saying the "key" command is global, understood . . . but policy 10 fails because the keys don't match, and policy 20 uses certificates for authentication. You're saying policy 20 wouldn't be tried?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...