ipv4ipv6ospfrouterrouting
When configuring OSPFv2 on a router, you type in
router ospf 10
router-id 1.1.1.1
network 10.0.0.0 0.0.0.3 area 0
for example. That way the network can be advertised per LSAs.
But in OSPFv3 it seems that there isn't such a command.
Unfortunately I haven't found anything by googling.
When using Cisco equipment, OSPF calls several things a "stub"... it gets a bit confusing....
The meanings are very different for each term; even more confusing is the reality that you can potentially apply multiple stub terms to a single OSPF interface. I'll elaborate more below.
Let's clear up some terminology... The question starts off asking about what Cisco is calling a "Stub Host"... OSPF automatically assigns Loopback interfaces to this category...
CORE01.PUB.DAL02#sh ip ospf interface lo0
Loopback0 is up, line protocol is up
Internet Address 128.66.62.5/32, Area 0.0.0.0
Process ID 100, Router ID 128.66.62.5, Network Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
^^^^^^^^^
CORE01.PUB.DAL02#
All this is not to be confused with what OSPF refers to as "Stub Network"... which merely means a network without an OSPF neighbor
CORE01.PUB.DAL02#sh ip ospf data router internal
...
Link connected to: a Transit Network <------- Broadcast Intf w/ Neighbor
(Link ID) Designated Router address: 128.66.62.75 <-------
(Link Data) Router Interface address: 128.66.62.75
Number of TOS metrics: 0
TOS 0 Metrics: 10
...
Link connected to: a Stub Network <------ Broadcast Intf w/o Neighbor
(Link ID) Network/subnet number: 128.66.62.32 <------
(Link Data) Network Mask: 255.255.255.248
Number of TOS metrics: 0
TOS 0 Metrics: 1
Link connected to: a Stub Network <------ Loopback interface
(Link ID) Network/subnet number: 128.66.62.5
(Link Data) Network Mask: 255.255.255.255
Number of TOS metrics: 0
TOS 0 Metrics: 1
Then, of course, we have an OSPF Stub Area. Let's consider where all this comes from...
Transit and Stub networks are discussed in RFC 2328: OSPFv2 - Section 2.1:
2. The Link-state Database: organization and calculations
The following subsections describe the organization of OSPF's link-
state database, and the routing calculations that are performed on
the database in order to produce a router's routing table.
2.1. Representation of routers and networks ... Networks can be either transit or stub networks. Transit networks are those capable of carrying
data traffic that is neither locally originated nor locally
destined. A transit network is represented by a graph vertex
having both incoming and outgoing edges. A stub network's vertex
has only incoming edges.
The whole point of this distinction between Transit Network and Stub Network is to save resources in the router.
When we start scaling to potentially thousands of LSAs, even small memory savings are important. Note that OSPF hellos are still sent on a stub networks, and they are capable of forming neighbors / transitioning to a transit network unless the interface has been administratively marked as a passive interface.
So now we still have the original discussion about the Stub Host, which also happens to be an OSPF Stub Network. This concept comes from RFC 2328: OSPFv2 - Section 9.1, where it discusses various interface states...
9.1. Interface states The various states that router interfaces may attain is
documented in this section.
Down
...
Loopback
... For this reason, IP packets may
still be addressed to an interface in Loopback state. To
facilitate this, such interfaces are advertised in router-
LSAs as single host routes, whose destination is the IP
interface address.[4]
...
Waiting
...
Point-to-point
...
The RFC requires Loopback network types to be advertised as a /32 host route. What Cisco calls a Stub Host in show ip ospf interface output is really just the Loopback interface type, which OSPF allocates automatically as a /32 host route within OSPF.
Stub areas are covered in RFC 2328: OSPFv2 - Section 3.6. There are several categories of OSPF stub areas...
ExternalRoutingCapability), which is cleared when an area is configured as a Stub AreaIn summary, we talked about...
If you really want to wrap your mind around all this, consider an OSPF router, which has a loopback interface; this router is completely contained in a single OSPF stub area. Technically, you could apply all three of the OSPF "stub" terms to this Loopback (Stub Host, Stub Network, Stub Area).
I would suggest creating a static route to Null 0 on the external router:
ip route 192.168.0.0 255.255.248.0 Null 0
When you redistribute from one routing process to the other the summary route should be injected into the OSPF process.
You could also filter out the subnets with a prefix list or route map to be sure the smaller subnets don't get injected.
Hopefully this helps.
Best Answer
To run OSPF dual stack, just run OSPFv2 and OSPFv3 simultanously. They won't interfere because they are completely separate.
With OSPFv3, there is NO
networkcommand under OSPF process configuration section. The reason why is here: To enable OSPFv3 on interfaces, you have to configureipv6 ospfcommand under interface configuration section of each interface. That way OSPFv3 knows what network to advertise.Below is simple OSPFv3 configuration for your reference:
R1
R2
R3
You can find more helpful information at OSPF Implementation - OSPFv3 from the "Implementing Cisco IP Routing (ROUTE) Foundation Learning Guide" book.