Reference Guide

Table Of Contents
OS10(conf-if-eth1/1/1)# ipv6 ospf dead-interval 20
OS10(conf-if-eth1/1/1)# ipv6 ospf priority 4
View OSPFv3 Interface Parameters
OS10# show ipv6 ospf interface
fortyGigE 0/0 is up, line protocol is up
Link Local Address fe80::92b1:1cff:fef4:a39d, Interface ID 1048581
Area 0, Process ID 10, Instance ID 0, Router ID 60.60.60.1
NetworkType BROADCAST, Cost: 1, Passive: No
Transmit Delay is 0 sec, State BDR, Priority 4
Designated router on this network is 70.70.70.1
Backup designated router on this network is 60.60.60.1 (local)
Timer intervals configured, Hello 5, Dead 20
Default route
You can generate an external default route and distribute the default information to the OSPFv3 routing domain.
To generate the default route, use the default-information originate [always] command in ROUTER-OSPFv3
mode.
Configure default route
OS10(config)# router ospfv3 100
OS10(config-router-ospf-100)# default-information originate always
View default route configuration
OS10(config-router-ospf-100)# show configuration
!
router ospfv3 100
default-information originate always
OSPFv3 IPsec authentication and encryption
Unlike OSPFv2, OSPFv3 does not have authentication fields in its protocol header to provide security. To provide authentication
and confidentiality, OSPFv3 uses IP Security (IPsec) a collection of security protocols for authenticating and encrypting data
packets. OS10 OSPFv3 supports IPsec using the IPv6 authentication header (AH) or IPv6 encapsulating security payload (ESP).
AH authentication verifies that data is not altered during transmission and ensures that users are communicating with the
intended individual or organization. The authentication header is inserted after the IP header with a value of 51. MD5 and
SHA1 authentication types are supported; encrypted and unencrypted keys are supported.
ESP encryption encapsulates data, enabling the protection of data that follows in the datagram. The ESP extension header
is inserted after the IP header and before the next layer protocol header. 3DES, DES, AES-CBC, and NULL encryption
algorithms are supported; encrypted and unencrypted keys are supported.
Apply IPsec authentication or encryption on a physical, port-channel, or VLAN interface or in an OSPFv3 area. Each
configuration consists of a security policy index (SPI) and the key used to validate OSPFv3 packets. After you configure an
IPsec protocol for OSPFv3, IPsec operation is invisible to the user.
You can only enable one security protocol (authentication or encryption) at a time on an interface or for an area. Enable IPsec
AH with the ipv6 ospf authentication command; enable IPsec ESP with the ipv6 ospf encryption command.
A security policy configured for an area is inherited by default on all interfaces in the area.
A security policy configured on an interface overrides any area-level configured security for the area to which the interface
is assigned.
The configured authentication or encryption policy is applied to all OSPFv3 packets transmitted on the interface or in the
area. The IPsec security associations are the same on inbound and outbound traffic on an OSPFv3 interface.
There is no maximum AH or ESP header length because the headers have fields with variable lengths.
Configure IPsec authentication on interfaces
Prerequisite: Before you enable IPsec authentication on an OSPFv3 interface, first enable IPv6 unicast routing globally, then
enable OSPFv3 on the interface, and assign it to an area.
Layer 3
419