Is it possible that adjacencies do not flap when changing keys?
EIGRP Authentication Rotating Key
Scenario:
As the senior security officer you decide all routing protocols should be configured as secure as possible. The company you work for has a single vendor policy and since you only have Cisco equipment you are running EIGRP (Enhanced Interior Gateway Routing Protocol). EIGRP has more advanced features for authentication since it uses a key-chain. The key-chain supports rotating keys which makes it more secure than having a single static key. Before implementing this for your whole organization you decide to test your enhanced security in a lab environment.
Goal:
- All IP addresses have been preconfigured for you.
- EIGRP has been preconfigured for you (AS12).
- Enable EIGRP authentication between router Jack and Johnson. Use the following parameters:
Key-chain should be called: GNS3VAULT
Key1: password VAULT
Key2: password SAFE - Key1 should be sent until 9:00AM on the 2nd of february 2020 and should be accepted 15 minutes past this time.
- Key2 should be valid from 8:50AM on the 2nd of february 2020 and should be valid till the 1st of february 2021.
- Make sure routing adjacencies do not drop when the keys are switched.
IOS:
c3640-jk9s-mz.124-16.bin
Topology:

Video Solution:
You need to register to download the GNS3 Topology File. (Registration is Free!)
- Related Articles
Comments (11)
-
ReneMolenaar 2011-02-06 10:55:26If the keys are overlapping the adjacency should not flap. Did you check it?
-
Akiii 2011-02-06 13:35:59Thanks for the reply.
Yeah they are overlapping but I still see flapping adjacencies when applying the ip authentication command on the serial interfaces..
-
aaaa2209 2011-04-15 04:06:59The file seems crash?
-
ReneMolenaar 2011-04-15 19:22:14What do you mean by 'crash' william?
-
aaaa2209 2011-04-19 03:45:36The winrar reports file name issue and it generate two similar folders. One is 'EIGRP Authentication Rotating Key' and another one is 'EIGRP Authentication Rotating Key_' The first one is empty and I just found that the second one has the files I want. I am not sure why. It might be my computer's problem. But I still get the topology file. Thank you!
-
ReneMolenaar 2011-04-21 16:56:05Hi william,
Not sure what went wrong, just checked the file and it seems to be fine!
Rene
-
Buddha1115 2011-07-22 06:12:16Hi Rene,
I absolutely love all these videos and labs that you've created for those of us who want to educate ourselves. Quick question, though... I couldn't help but notice that this video is in a slightly different resolution than the others, and I honestly cannot read what you are entering at the CLI.
I was wondering if there was any way that this video could be re-made in the same resolution as the others so that the text is more readable? None of my CCNA books mention EIGRP keys, let alone rotation, so I'm eager to review the video so I can learn the commands, but I just have a hard time seeing what you're doing on this one. A humongous "Thanks!" if there's anyway you could do it, and I'd like to think that others would be appreciative as well.
Thanks again for everything you do, Rene!
-
ReneMolenaar 2011-07-22 16:32:12Hello Barry,
Thanks for your message! I accidently rendered it with super-low quality instead of 1080p ;D
When I get home i'll replace it with the 1080p version so you can see it. You can also try it yourself if you like, just download the final configuration and do this:
- Enable debug EIGRP packets
- Change the time by using the clock command.You will see that the neighbor adjacency doesn't drop and will switch from MD5 key1 to key2.
Or wait a day and i'll have the video for you

-
G3000LEE 2011-10-03 16:35:46Hi Rene
Your GOLES state for key 1:
•Key1 should be sent until 9
0AM on the 2nd of february 2020 and should be accepted 15 minutes past this time.Your final config files which I downloaded shows the following for key 1:
key chain GNS3VAULT
key 1
key-string VAULT
accept-lifetime 00
0
0 Jan 1 1995 09:15
0 Feb 2 2020
send-lifetime 00
0
0 Jan 1 1995 09
0
0 Feb 2 2020
Isn't it supposed to be:key chain GNS3VAULT
key 1
key-string VAULT
accept-lifetime 09:15
0 feb 2 2020 infinite
send-lifetime 09
0
0 feb 2 2020 infiniteI put infinite, as you didn't specify when the key is to end.
GRATE JOB YOU ARE DOING HERE.
-
ReneMolenaar 2011-10-03 19:38:54Hello Lee,
The goal says "Key1 should be sent until 9
0AM on the 2nd of february 2020 and should be accepted 15 minutes past this time."It doesn't say from what moment it is valid, only until which date/time it is valid. At 9
0AM on the 2nd of february 2020 this key will expire.Your example will accept they key on this day until forever ;D
Thanks for your comment!





