Administrator Guide
• Manual key conguration is supported in an authentication or encryption policy (dynamic key conguration using the internet key
exchange [IKE] protocol is not supported).
• In an OSPFv3 authentication policy:
• AH is used to authenticate OSPFv3 headers and certain elds in IPv6 headers and extension headers.
• MD5 and SHA1 authentication types are supported; encrypted and unencrypted keys are supported.
• In an OSPFv3 encryption policy:
• Both encryption and authentication are used.
• IPsec security associations (SAs) are supported only in Transport mode (Tunnel mode is not supported).
• ESP with null encryption is supported for authenticating only OSPFv3 protocol headers.
• ESP with non-null encryption is supported for full condentiality.
• 3DES, DES, AES-CBC, and NULL encryption algorithms are supported; encrypted and unencrypted keys are supported.
NOTE: To encrypt all keys on a router, use the service password-encryption command in Global Conguration mode.
However, this command does not provide a high level of network security. To enable key encryption in an IPsec security policy at
an interface or area level, specify 7 for [key-encryption-type] when you enter the ipv6 ospf authentication
ipsec
or ipv6 ospf encryption ipsec command.
• To congure an IPsec security policy for authenticating or encrypting OSPFv3 packets on a physical, port-channel, or VLAN interface
or OSPFv3 area, perform any of the following tasks:
• Conguring IPsec Authentication on an Interface
• Conguring IPsec Encryption on an Interface
• Conguring IPsec Authentication for an OSPFv3 Area
• Conguring IPsec Encryption for an OSPFv3 Area
• Displaying OSPFv3 IPsec Security Policies
Conguring IPsec Authentication on an Interface
To congure, remove, or display IPsec authentication on an interface, use the following commands.
Prerequisite: Before you enable IPsec authentication on an OSPFv3 interface, rst enable IPv6 unicast routing globally, congure an IPv6
address and enable OSPFv3 on the interface, and assign it to an area (refer to Conguration Task List for OSPFv3 (OSPF for IPv6)).
The SPI value must be unique to one IPsec security policy (authentication or encryption) on the router. Congure the same authentication
policy (the same SPI and key) on each OSPFv3 interface in a link.
• Enable IPsec authentication for OSPFv3 packets on an IPv6-based interface.
INTERFACE mode
ipv6 ospf authentication {null | ipsec spi number {MD5 | SHA1} [key-encryption-type] key}
• null: causes an authentication policy congured for the area to not be inherited on the interface.
• ipsec spi number: the security policy index (SPI) value. The range is from 256 to 4294967295.
• MD5 | SHA1: species the authentication type: Message Digest 5 (MD5) or Secure Hash Algorithm 1 (SHA-1).
• key-encryption-type: (optional) species if the key is encrypted. The valid values are 0 (key is not encrypted) or 7 (key is
encrypted).
• key: species the text string used in authentication. All neighboring OSPFv3 routers must share key to exchange information. For
MD5 authentication, the key must be 32 hex digits (non-encrypted) or 64 hex digits (encrypted). For SHA-1 authentication, the key
must be 40 hex digits (non-encrypted) or 80 hex digits (encrypted).
• Remove an IPsec authentication policy from an interface.
no ipv6 ospf authentication ipsec spi number
• Remove null authentication on an interface to allow the interface to inherit the authentication policy congured for the OSPFv3 area.
no ipv6 ospf authentication null
• Display the conguration of IPsec authentication policies on the router.
Open Shortest Path First (OSPFv2 and OSPFv3)
687