Discussion

When you are looking at the configuration contents, pipe the output to hide the
passwords:
[edit]
aviva@RouterG# show protocols ospf | except SECRET-DATA
area 0.0.0.0 {
authentication-type md5;
interface fe-0/0/1.0 {
authentication {
}
}
interface fe-1/0/1.0 {
authentication {
}
}
}
You can do the same thing in operational mode:
aviva@RouterG> show configuration protocols ospf | except SECRET-DATA
area 0.0.0.0 {
authentication-type md5;
interface fe-0/0/1.0 {
authentication {
}
}
interface fe-1/0/1.0 {
authentication {
}
}
}
As part of your security measures, you may, from time to time, want to transition
from using one MD5 key to another. You can do this by configuring multiple MD5
keys, each with a unique key ID, and setting the date and time to switch to the new
key. Here, the new keys take effect at 12:01 a.m. on the first day of the month for the
next several months:
[edit protocols ospf area 0.0.0.0]
aviva@RouterG# set interface fe-0/0/1 authentication md5 1 key $1991poPPi
aviva@RouterG# set interface fe-0/0/1 authentication md5 2 key NeWpsswdFEB start-time
2006-02-01.00:01
aviva@RouterG# set interface fe-0/0/1 authentication md5 3 key NeWpsswdMAR start-time
2006-03-01.00:01
aviva@RouterG# set interface fe-0/0/1 authentication md5 4 key NeWpsswdAPR start-time
2006-04-01.00:01
The start time specifies the time at which the router starts using the MD5 key for
transmission. When receiving packets, the router accepts packets with any MD5 key
as long as the key ID specified in the packet corresponds to a currently configured
key, regardless of the key’s start time.
404 | Chapter 12: OSPF
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.