Lenovo ThinkSystem NE2552E, Application Manual

Page: 413 / 574

© Copyright Lenovo 2018 Chapter 28: OSPF
413
OSPFv3 Implementation in Lenovo ENOS
OSPF version 3 is based on OSPF version 2, but has been modified to support IPv6
addressing. In most other ways, OSPFv3 is similar to OSPFv2: They both have the
same packet types and interfaces, and both use the same mechanisms for neighbor
discovery, adjacency formation, LSA flooding, aging, and so on. The administrator
should be familiar with the OSPFv2 concepts covered in the preceding sections of
this chapter before implementing the OSPFv3 differences as described in the
following sections.
Although OSPFv2 and OSPFv3 are very similar, they represent independent
features on the NE2552E. They are configured separately, and both can run in
parallel on the switch with no relation to one another, serving different IPv6 and
IPv4 traffic, respectively.
OSPFv3 Differences from OSPFv2
Note:
When OSPFv3 is enabled, the OSPF backbone area (0.0.0.0) is created by
default and is always active.
OSPFv3 Requires IPv6 Interfaces
OSPFv3 is designed to support IPv6 addresses. This requires IPv6 interfaces to be
configured on the switch and assigned to OSPF areas, in much the same way IPv4
interfaces are assigned to areas in OSPFv2. This is the primary configuration
difference between OSPFv3 and OSPFv2.
See “Internet Protocol Version 6” on page 325 for configuring IPv6 interfaces.
OSPFv3 Uses Independent Command Paths
Though OSPFv3 and OSPFv2 are very similar, they are configured independently.
OSPFv3 command paths are located as follows:
 In the ISCLI
OSPFv3 Identifies Neighbors by Router ID
Where OSPFv2 uses a mix of IPv4 interface addresses and Router IDs to identify
neighbors, depending on their type, OSPFv3 configuration consistently uses a
Router ID to identify all neighbors.
Although Router IDs are written in dotted decimal notation, and may even be
based on IPv4 addresses from an original OSPFv2 network configuration, it is
important to realize that Router IDs are not IP addresses in OSPFv3, and can be
assigned independently of IP address space. However, maintaining Router IDs
consistent with any legacy OSPFv2 IPv4 addressing allows for easier
implementation of both protocols.
NE2552E(config)# ipv6 router ospf
(OSPFv3 router config mode)
NE2552E(config-router-ospf3)# ?
NE2552E(config)# interface ip
<Interface number> (Configure OSPFv3)
NE2552E(config-ip-if)# ipv6 ospf ?
(OSPFv3 interface config)
NE2552E# show ipv6 ospf ?
(Show OSPFv3 information)