Table of Contents
Advertisement
ip ospf message-digest-key md5
Configuring the BFD Protocol for OSPF
Copyright © 2010, Juniper Networks, Inc.
Use to specify that no authentication is used for the OSPF interface.
Example
host1(config-if)#ip ospf authentication-none
The no version has no effect.
See ip ospf authentication-none
Use to enable MD5 authentication on the OSPF interface and configure the MD5 key.
NOTE: If all the MD5 keys have been deleted, the authentication type is
still MD5, but you need to configure MD5 keys.
The MD5 key is a character string up to 16 characters long. You must also specify a key
identifier and whether the key is entered in unencrypted or encrypted format. If you do
not specify which, the string is assumed to be unencrypted.
NOTE: To display the password only in encrypted text, use the service
password-encryption command.
Example
host1(config-if)#ip ospf message-digest-key 3 md5 0 tre987is
Use the no version to delete an MD5 key from the OSPF interface.
NOTE: To disable MD5 authentication for the interface, use the ip ospf
authentication-none command.
See ip ospf message-digest-key md5
The ip ospf bfd-liveness-detection and ipv6 ospf bfd-liveness-detection commands
configure the Bidirectional Forwarding Detection (BFD) protocol for OSPFv2 and OSPFv3
(respectively). The BFD protocol uses control packets and shorter detection time limits
to more rapidly detect failures in a network. Also, because they are adjustable, you can
modify the BFD timers for more or less aggressive failure detection.
When you issue the ip ospf bfd-liveness-detection or ipv6 ospf bfd-liveness-detection
command on an OSPF peer, the peer establishes BFD liveness detection with all
BFD-enabled OSPF peers. When the local peer receives an update from a remote OSPF
Chapter 5: Configuring OSPF
269
Advertisement
Table of Contents
