Setup Guide

– bgp | connected | static: enter one of the keywords to redistribute those routes.
– metric metric-value: The range is from 0 to 4294967295.
– metric-type metric-type: enter 1 for OSPFv3 external route type 1 OR 2 for OSPFv3 external route type 2.
– route-map map-name: enter a name of a congured route map.
– tag tag-value: The range is from 0 to 4294967295.
Conguring a Default Route
To generate a default external route into the OSPFv3 routing domain, congure the following parameters.
To specify the information for the default route, use the following command.
• Specify the information for the default route.
CONF-IPV6-ROUTER-OSPF mode
default-information originate [always [metric metric-value] [metric-type type-value]] [route-
map map-name]
Congure the following required and optional parameters:
– always: indicate that default route information is always advertised.
– metric metric-value: The range is from 0 to 4294967295.
– metric-type metric-type: enter 1 for OSPFv3 external route type 1 OR 2 for OSPFv3 external route type 2.
– route-map map-name: enter a name of a congured route map.
OSPFv3 Authentication Using IPsec
OSPFv3 uses OSPFv3 authentication using IP security (IPsec) to provide authentication for OSPFv3 packets. IPsec authentication ensures
security in the transmission of OSPFv3 packets between IPsec-enabled routers.
IPsec is a set of protocols developed by the internet engineering task force (IETF) to support secure exchange of packets at the IP layer.
IPsec supports two encryption modes: transport and tunnel.
• Transport mode — encrypts only the data portion (payload) of each packet, but leaves the header untouched.
• Tunnel mode — is more secure and encrypts both the header and payload. On the receiving side, an IPsec-compliant device decrypts
each packet.
NOTE
: The system supports only Transport Encryption mode in OSPFv3 authentication with IPsec.
With IPsec-based authentication, Crypto images are used to include the IPsec secure socket application programming interface (API)
required for use with OSPFv3.
To ensure integrity, data origin authentication, detection and rejection of replays, and condentiality of the packet, RFC 4302 and RFC 4303
propose using two security protocols — authentication header (AH) and encapsulating security payload (ESP). For OSPFv3, these two
IPsec protocols provide interoperable, high-quality cryptographically-based security.
• HA — IPsec authentication header is used in packet authentication to verify that data is not altered during transmission and ensures
that users are communicating with the intended individual or organization. Insert the authentication header after the IP header with a
value of 51. AH provides integrity and validation of data origin by authenticating every OSPFv3 packet. For detailed information about
the IP AH protocol, refer to RFC 4302.
• ESP — encapsulating security payload encapsulates data, enabling the protection of data that follows in the datagram. ESP provides
authentication and condentiality of every packet. The ESP extension header is designed to provide a combination of security services
for both IPv4 and IPv6. Insert the ESP header after the IP header and before the next layer protocol header in Transport mode. It is
possible to insert the ESP header between the next layer protocol header and encapsulated IP header in Tunnel mode. However, Tunnel
mode is not supported in the Dell Networking OS. For detailed information about the IP ESP protocol, refer to RFC 4303.
In OSPFv3 communication, IPsec provides security services between a pair of communicating hosts or security gateways using either AH
or ESP. In an authentication policy on an interface or in an OSPF area, AH and ESP are used alone; in an encryption policy, AH and ESP may
710
Open Shortest Path First (OSPFv2 and OSPFv3)