Basic configuration of all routers:
R1:
ipv un
!
int lo0
ip add 1.1.1.1 255.255.255.0
ipv add 1::1/64
ipv6 enable
ospfv3 1 ipv6 area 0
ospfv3 1 ipv4 area 0
ospfv3 network point-to-point
!
interface G0/0
ip address 12.0.0.1 255.255.255.0
ipv6 address 12::1/64
ipv6 enable
ospfv3 1 ipv6 area 12
ospfv3 1 ipv4 area 12
no shut
!
router ospfv3 1
!
address-family ipv4 unicast
router-id 0.0.0.1
exit-address-family
!
address-family ipv6 unicast
router-id 0.0.0.11
exit-address-family
R2:
ipv un
!
interface G0/0
ip address 12.0.0.2 255.255.255.0
ipv6 address 12::2/64
ipv6 enable
ospfv3 1 ipv6 area 0
ospfv3 1 ipv4 area 0
no shut
!
interface G0/1
ip address 23.0.0.2 255.255.255.0
ipv6 address 23::2/64
ipv6 enable
ospfv3 1 ipv6 area 1
ospfv3 1 ipv4 area 1
no shut
!
router ospfv3 1
!
address-family ipv4 unicast
router-id 0.0.0.2
exit-address-family
!
address-family ipv6 unicast
router-id 0.0.0.22
exit-address-family
R3:
ipv un
!
interface G0/0
ip address 23.0.0.3 255.255.255.0
ipv6 address 23::3/64
ipv6 enable
ospfv3 1 ipv6 area 1
ospfv3 1 ipv4 area 1
no shut
!
router ospfv3 1
!
address-family ipv4 unicast
router-id 0.0.0.3
exit-address-family
!
address-family ipv6 unicast
router-id 0.0.0.33
exit-address-family
By definition, In OSPFv3, the Type-1 and 2 LSAs no longer carry any addressing information. They only carry a description of topology adjacencies. This is how type 8 and 9 LSAs came to carry the prefix informations.
Rememeber with OSPFv2, the prefix suppression suppresses the subnet carried in the Type-1 and 2 LSA.
So how this feature works with OSPFv3?
Per RFC 6860 Hiding Transit-Only Networks in OSPF
- Hiding IPv6 Transit-Only Networks in OSPFv3
In [OSPFv3], addressing semantics have been removed from the OSPF
protocol packets and the main LSA types, leaving a network-protocol-
independent core.
More specifically, router-LSAs and network-LSAs no longer contain
network addresses but simply express topology information. Instead,
two new LSA types, link-LSA and intra-area-prefix-LSA, have been
introduced. A link-LSA associates a list of IPv6 addresses to a link
and has local-link flooding scope, and an intra-area-prefix-LSA
either associates a list of IPv6 addresses with a router by
referencing a router-LSA or associates a list of IPv6 addresses with
a broadcast/NBMA network by referencing a network-LSA. In the latter
case, the prefixes in the link-LSAs from adjacent neighbors are
copied into the intra-area-prefix-LSA by the Designated Router.
To hide a transit-only network in [OSPFv3], the IPv6 address prefixes
are omitted from the router-LSA. Consequently, when a Designated
Router builds an intra-area-prefix-LSA referencing a network-LSA,
these IPv6 address prefixes will be omitted.
In addition, when a router builds an intra-area-prefix-LSA that is
referencing a router-LSA, the associated IPv6 address prefixes from
the transit-only network MUST also be omitted from the intra-area-
prefix-LSA.
3.1. Hiding AF-Enabled Transit-Only Networks in OSPFv3
[OSPF-AF] supports multiple Address Families (AFs) by mapping each AF
to a separate Instance ID and OSPFv3 instance.
In the meantime, each prefix advertised in OSPFv3 has a prefix length
field [OSPFv3], which facilitates advertising prefixes of different
lengths in different AFs. The existing LSAs defined in [OSPFv3] are
used for prefix advertising, and there is no need to define new LSAs.
In other words, as link-LSAs and intra-area-prefix-LSAs are still
being used, the same mechanism explained in Section 3 can be used to
hide those AF-enabled transit-only networks as well.
Let's verify the IPv4 and IPv6 routing table of R3:
R3#show ip route ospfv | beg Gate
Gateway of last resort is not set
1.0.0.0/24 is subnetted, 1 subnets
O IA 1.1.1.0 [110/3] via 23.0.0.2, 00:02:44, GigabitEthernet0/0
12.0.0.0/24 is subnetted, 1 subnets
O IA 12.0.0.0 [110/2] via 23.0.0.2, 00:02:44, GigabitEthernet0/0
R3#
R3#show ipv route ospf
IPv6 Routing Table - default - 5 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, a - Application
OI 1::/64 [110/3]
via FE80::F60F:1BFF:FE06:E2C1, GigabitEthernet0/0
OI 12::/64 [110/2]
via FE80::F60F:1BFF:FE06:E2C1, GigabitEthernet0/0
R3#
Since in OSPFv3 the IP prefixes are no longer carried in the Type-1 LSA, instead the new LSAs, Type-8 and Type-9 LSA come to carry the IP prefixes:
By default, for each prefix connected, a router creates a single Type-8 LSA to carry it and this LSA has a link flooding scope (not area scope), in other words, it is not flooded beyond the receiving neighbor similar to broadcast:
For IPv4 Address Family.
Since R1 has two IP prefixes connected, it creates two separates Type-8 LSA for each link (Loopback and Fa0/0):
Type-8 LSA for the link loopback carries 1.1.1.0/24 (Number of Prefixes: 1).
Type-8 LSA for link fa0/0 carries 12.0.0.0/24 (Number of Prefixes: 1).
R1#show ospfv3 ipv4 data link self
OSPFv3 1 address-family ipv4 (router-id 0.0.0.1)
Link (Type-8) Link States (Area 0)
LS age: 105
Options: (E-Bit, R-Bit, DC-Bit, AF-Bit)
LS Type: Link-LSA (Interface: Loopback0)
Link State ID: 18 (Interface ID)
Advertising Router: 0.0.0.1
LS Seq Number: 80000001
Checksum: 0x15C5
Length: 52
Router Priority: 1
Link Local Address: 1.1.1.1
Number of Prefixes: 1
Prefix Address: 1.1.1.0
Prefix Length: 24, Options: None
LS age: 96
Options: (E-Bit, R-Bit, DC-Bit, AF-Bit)
LS Type: Link-LSA (Interface: GigabitEthernet0/0)
Link State ID: 3 (Interface ID)
Advertising Router: 0.0.0.1
LS Seq Number: 80000002
Checksum: 0xFADB
Length: 52
Router Priority: 1
Link Local Address: 12.0.0.1
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None
R1#
R1#show ospfv3 ipv4 data link self | s Prefix
Number of Prefixes: 1
Prefix Address: 1.1.1.0
Prefix Length: 24, Options: None
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None
R1#
For IPv6 Address Family.
Since R1 has two IP prefixes connected, it creates two separates Type-8 LSA for each link (Loopback and Fa0/0):
Type-8 LSA for the link loopback carries 1::/64 (Number of Prefixes: 1).
Type-8 LSA for link fa0/0 carries 12::/64 (Number of Prefixes: 1).
R1#show ospfv3 ipv6 data link self
OSPFv3 1 address-family ipv6 (router-id 0.0.0.11)
Link (Type-8) Link States (Area 0)
LS age: 405
Options: (V6-Bit, E-Bit, R-Bit, DC-Bit)
LS Type: Link-LSA (Interface: Loopback0)
Link State ID: 18 (Interface ID)
Advertising Router: 0.0.0.11
LS Seq Number: 80000001
Checksum: 0x4D0E
Length: 56
Router Priority: 1
Link Local Address: FE80::1205:CAFF:FE29:6560
Number of Prefixes: 1
Prefix Address: 1::
Prefix Length: 64, Options: None
LS age: 396
Options: (V6-Bit, E-Bit, R-Bit, DC-Bit)
LS Type: Link-LSA (Interface: GigabitEthernet0/0)
Link State ID: 3 (Interface ID)
Advertising Router: 0.0.0.11
LS Seq Number: 80000003
Checksum: 0x255
Length: 56
Router Priority: 1
Link Local Address: FE80::1205:CAFF:FE29:6560
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None
R1#
R1#show ospfv3 ipv6 data link self | s Prefix
Number of Prefixes: 1
Prefix Address: 1::
Prefix Length: 64, Options: None
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None
R1#
For IPv4 Address Family.
To advertise the prefix 1.1.1.0/24 to R2, it creates a Type-9 LSA, unlike with Type-8 LSA this LSA has an area flooding scope and a single Type-9 LSA can carry multiple prefixes:
Below the IP prefixe 1.1.1.0/24 is carried by the Type-9 LSA's R1:
R1#show ospfv3 ipv4 database prefix self-originate
OSPFv3 1 address-family ipv4 (router-id 0.0.0.1)
Intra Area Prefix Link States (Area 0)
LS age: 6
LS Type: Intra-Area-Prefix-LSA
Link State ID: 0
Advertising Router: 0.0.0.1
LS Seq Number: 80000004
Checksum: 0xCF1A
Length: 40
Referenced LSA Type: 2001
Referenced Link State ID: 0
Referenced Advertising Router: 0.0.0.1
Number of Prefixes: 1
Prefix Address: 1.1.1.0
Prefix Length: 24, Options: None, Metric: 1
R1#
R1#show ospfv3 ipv4 database prefix self | s Prefix
Intra Area Prefix Link States (Area 0)
LS Type: Intra-Area-Prefix-LSA
Number of Prefixes: 1
Prefix Address: 1.1.1.0
Prefix Length: 24, Options: None, Metric: 1
R1#
For IPv6 Address Family.
To advertise the prefix 1::/64 to R2, it creates a Type-9 LSA, unlike with Type-8 LSA this LSA has an area flooding scope and a single Type-9 LSA can carry multiple prefixes:
Below the IP prefixe 1::/64 is carried by the Type-9 LSA's R1:
R1#show ospfv3 ipv6 database prefix self-originate
OSPFv3 1 address-family ipv6 (router-id 0.0.0.11)
Intra Area Prefix Link States (Area 0)
LS age: 273
LS Type: Intra-Area-Prefix-LSA
Link State ID: 0
Advertising Router: 0.0.0.11
LS Seq Number: 80000004
Checksum: 0x5A51
Length: 44
Referenced LSA Type: 2001
Referenced Link State ID: 0
Referenced Advertising Router: 0.0.0.11
Number of Prefixes: 1
Prefix Address: 1::
Prefix Length: 64, Options: None, Metric: 1
R1#
R1#show ospfv3 ipv6 database prefix self | s Prefix
Intra Area Prefix Link States (Area 0)
LS Type: Intra-Area-Prefix-LSA
Number of Prefixes: 1
Prefix Address: 1::
Prefix Length: 64, Options: None, Metric: 1
R1#
Let's enable prefix suppression feature on loopback of R1:
R1(config)#int lo0
R1(config-if)#ospfv3 prefix-suppression
Let's verify the Type-8 LSA for IPv4 and IPv6 Address Families, the prefixes 1.1.1.0/24 and 1::/64 are suppressed in the Type-8 LSAs for the link lo0 as mentioned by the Number of Prefixes: 0:
R1#show ospfv3 ipv4 data link self | s Prefix
Number of Prefixes: 0
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None
R1#
R1#show ospfv3 ipv6 data link self | s Prefix
Number of Prefixes: 0
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None
R1#
Since R1 does not have any prefixes that belong to another link except the link fa0/0, it does not generate a Type-9 LSA for both IPv4 and IPv6 Address Families as shown below:
R1#show ospfv3 ipv4 database prefix self
OSPFv3 1 address-family ipv4 (router-id 0.0.0.1)
R1#
R1#show ospfv3 ipv6 database prefix self
OSPFv3 1 address-family ipv6 (router-id 0.0.0.11)
R1#
Since the prefixes 1.1.1.1.0/24 and 1::/64 are not included in the Type-8 LSA's R1, no route in the IPv4 and IPv6 routing tables of R3:
R3#show ip route ospfv | beg Gate
Gateway of last resort is not set
12.0.0.0/24 is subnetted, 1 subnets
O IA 12.0.0.0 [110/2] via 23.0.0.2, 00:16:40, GigabitEthernet0/0
R3#
R3#show ipv route ospf
IPv6 Routing Table - default - 4 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, a - Application
OI 12::/64 [110/2]
via FE80::F60F:1BFF:FE06:E2C1, GigabitEthernet0/0
R3#
Now what about the filtering of the prefix 12.0.0.0/24 ?
First let's verify that R2 is the DR for the segments 12.0.0.0/24 and 12::/64 for both IPv4 and IPv6 Address Families:
R2#show ospfv3 interface g0/0 | inc Designated Router
Designated Router (ID) 0.0.0.2, local address FE80::F60F:1BFF:FE06:E2C0
Adjacent with neighbor 0.0.0.1 (Backup Designated Router)
Designated Router (ID) 0.0.0.22, local address FE80::F60F:1BFF:FE06:E2C0
Adjacent with neighbor 0.0.0.11 (Backup Designated Router)
R2#
By definition with OSPFv2 the content of the LSA Type 2 describes the network segment listing the DR address, the attached routers, and the used subnet mask. This information is used by
each router participating in OSPF to build the exact picture of the described multiaccess segment, which cannot be fully described with just LSAs Type 1.
With OSPFv3 the Type-2 LSA does not carry the used subnet mask and the DR address.
Let's verify the Network LSA Type 2 generated by the R2 for both IPv4 and IPv6 Address Families, we can see that there is no information about the subnet mask /24 and /64 and the DR address (12.0.0.2 and 12::2), only the attached routers and the Link State ID are carried as shown by the show ospfv3 database network command:
R2#show ospfv3 database network self-originate
OSPFv3 1 address-family ipv4 (router-id 0.0.0.2)
Net Link States (Area 0)
LS age: 910
Options: (E-Bit, R-Bit, DC-Bit, AF-Bit)
LS Type: Network Links
Link State ID: 3 (Interface ID of Designated Router)
Advertising Router: 0.0.0.2
LS Seq Number: 80000001
Checksum: 0xE719
Length: 32
Attached Router: 0.0.0.2
Attached Router: 0.0.0.1
OSPFv3 1 address-family ipv6 (router-id 0.0.0.22)
Net Link States (Area 0)
LS age: 910
Options: (V6-Bit, E-Bit, R-Bit, DC-Bit)
LS Type: Network Links
Link State ID: 3 (Interface ID of Designated Router)
Advertising Router: 0.0.0.22
LS Seq Number: 80000001
Checksum: 0xC509
Length: 32
Attached Router: 0.0.0.22
Attached Router: 0.0.0.11
R2#
Since the creators of OSPFv3 decided to remove the subnet mask in the Type-2 LSA, a router can originate multiple intra-area prefix LSAs for each router or transit network, each with a unique link-state ID. The link state ID for each intra-area prefix LSA describes its association to either the router LSA or the network LSA. The link-state ID also contains prefixes for stub and transit networks.
This LSA type (Intra Area Prefix) provides information for two different scenarios:
1) It will provide information about IPv6 address prefixes associated with a transit network by referencing a Network LSA.
2) It will provide information about IPv6 address prefixes associated with a router by referencing a Router LSA. Type 9 LSAs are only flooded within an area.
Let's verify the Intra-area prefix LSA (Type 9) advertised by the DR R2:
We can see that the Type-9 LSAs carries the following information:
For IPv4 Address Family:
-the subnet 12.0.0.0 and the subnet mask (Prefix Length) /24
-Referenced Link State ID: 2 that matches the Link State ID of the LSA Type 2.
-Referenced LSA Type: 2002 describes its association to the Network LSA Type 2 (or 2002).
For IPv6 Address Family:
-the subnet 12::/64 and the subnet mask (Prefix Length) /64
-Referenced Link State ID: 3 that matches the Link State ID of the Type-2 LSA
-Referenced LSA Type: 2002 describes its association to the Network LSA Type 2 (or 2002).
R2#show ospfv3 database prefix self-originate
OSPFv3 1 address-family ipv4 (router-id 0.0.0.2)
Intra Area Prefix Link States (Area 0)
LS age: 51
LS Type: Intra-Area-Prefix-LSA
Link State ID: 3072
Advertising Router: 0.0.0.2
LS Seq Number: 80000001
Checksum: 0x14BE
Length: 40
Referenced LSA Type: 2002
Referenced Link State ID: 3
Referenced Advertising Router: 0.0.0.2
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None, Metric: 0
OSPFv3 1 address-family ipv6 (router-id 0.0.0.22)
Intra Area Prefix Link States (Area 0)
LS age: 51
LS Type: Intra-Area-Prefix-LSA
Link State ID: 3072
Advertising Router: 0.0.0.22
LS Seq Number: 80000001
Checksum: 0x9BDC
Length: 44
Referenced LSA Type: 2002
Referenced Link State ID: 3
Referenced Advertising Router: 0.0.0.22
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None, Metric: 0
R2#
R2#show ospfv3 database prefix self | inc Prefix
Intra Area Prefix Link States (Area 0)
LS Type: Intra-Area-Prefix-LSA
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None, Metric: 0
Intra Area Prefix Link States (Area 0)
LS Type: Intra-Area-Prefix-LSA
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None, Metric: 0
R2#
Let's enable prefix suppression on g0/0's R2
R2(config)#int g0/0
R2(config-if)#ospfv3 prefix-suppression
Let's verify the Type-9 LSAs for both IPv4 and IPv6 Address Families:
The show ospfv3 database prefix self-originate output shown that the prefixes of the transit network 12.0.0.0/24 and 12::/64 are not suppressed:
R2#show ospfv3 database prefix self-originate
OSPFv3 1 address-family ipv4 (router-id 0.0.0.2)
Intra Area Prefix Link States (Area 0)
LS age: 136
LS Type: Intra-Area-Prefix-LSA
Link State ID: 3072
Advertising Router: 0.0.0.2
LS Seq Number: 80000001
Checksum: 0x14BE
Length: 40
Referenced LSA Type: 2002
Referenced Link State ID: 3
Referenced Advertising Router: 0.0.0.2
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None, Metric: 0
OSPFv3 1 address-family ipv6 (router-id 0.0.0.22)
Intra Area Prefix Link States (Area 0)
LS age: 136
LS Type: Intra-Area-Prefix-LSA
Link State ID: 3072
Advertising Router: 0.0.0.22
LS Seq Number: 80000001
Checksum: 0x9BDC
Length: 44
Referenced LSA Type: 2002
Referenced Link State ID: 3
Referenced Advertising Router: 0.0.0.22
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None, Metric: 0
R2#
R2#show ospfv3 database prefix self | inc Prefix
Intra Area Prefix Link States (Area 0)
LS Type: Intra-Area-Prefix-LSA
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None, Metric: 0
Intra Area Prefix Link States (Area 0)
LS Type: Intra-Area-Prefix-LSA
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None, Metric: 0
R2#
Let's verify the Type-8-LSA's R1:
We can see that R1 advertises a Type-8 LSAs for IPv4 and IPv6 Address Families describing and including the prefixes 12.0.0.0/24 and 12::/64:
R2#show ospfv3 ipv4 database link adv 0.0.0.1
OSPFv3 1 address-family ipv4 (router-id 0.0.0.2)
Link (Type-8) Link States (Area 0)
LS age: 271
Options: (E-Bit, R-Bit, DC-Bit, AF-Bit)
LS Type: Link-LSA (Interface: GigabitEthernet0/0)
Link State ID: 3 (Interface ID)
Advertising Router: 0.0.0.1
LS Seq Number: 80000005
Checksum: 0xF4DE
Length: 52
Router Priority: 1
Link Local Address: 12.0.0.1
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None
Link (Type-8) Link States (Area 1)
R2#
R2#show ospfv3 ipv6 database link adv 0.0.0.11
OSPFv3 1 address-family ipv6 (router-id 0.0.0.22)
Link (Type-8) Link States (Area 0)
LS age: 280
Options: (V6-Bit, E-Bit, R-Bit, DC-Bit)
LS Type: Link-LSA (Interface: GigabitEthernet0/0)
Link State ID: 3 (Interface ID)
Advertising Router: 0.0.0.11
LS Seq Number: 80000006
Checksum: 0xFB58
Length: 56
Router Priority: 1
Link Local Address: FE80::1205:CAFF:FE29:6560
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None
Link (Type-8) Link States (Area 1)
R2#
R2#show ospfv3 ipv4 data link adv 0.0.0.1 | s Prefix
Number of Prefixes: 1
Prefix Address: 12.0.0.0
Prefix Length: 24, Options: None
R2#
R2#show ospfv3 ipv6 data link adv 0.0.0.11 | s Prefix
Number of Prefixes: 1
Prefix Address: 12::
Prefix Length: 64, Options: None
R2#
Since R2 is getting the information about the prefixes 12.0.0.0/24 and 12::/64 through Type-8 LSA, R2 creates a Type-9 LSAs for these prefixes et advertises them as Type-3 LSAs into area 1 to R3, even if the interface G0/0 of R2 is configured with prefix suppression feature:
R3#show ip route ospfv | beg Gate
Gateway of last resort is not set
12.0.0.0/24 is subnetted, 1 subnets
O IA 12.0.0.0 [110/2] via 23.0.0.2, 00:07:42, GigabitEthernet0/0
R3#
R3#show ipv route ospf
IPv6 Routing Table - default - 4 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, a - Application
OI 12::/64 [110/2]
via FE80::F60F:1BFF:FE06:E2C1, GigabitEthernet0/0
R3#
To ensure so that R2 will never generate or will never include the prefixes 12.0.0.0/24 and 12::/64 in its Type-9 LSA, we should tell to R1 to suppress these prefixes in the Type-8 LSAs generated by R1:
Let's enable prefix suppression in G0/0's R1:
R1(config-if)#int g0/0
R1(config-if)#ospfv3 prefix-suppression
Let's verify the Type-8 LSA advertised by R1 for both IPv4 and IPv6 Address Families:
For IPv6 there is no prefix 12::/64 in the Type-9 LSA's R1 as mentioned by the Number of Prefixes: 0:
R2#show ospfv3 ipv6 data link adv 0.0.0.11 | s Prefix
Number of Prefixes: 0
R2#
For IPv4 there is no prefix 12.0.0.0/24 in the Type-9 LSA's R1 as mentioned by the Number of Prefixes: 0:
R2#show ospfv3 ipv4 data link adv 0.0.0.1 | s Prefix
Number of Prefixes: 0
R2#
Since R2 will not get any information from R1 about the prefixes 12.0.0.0/24 and 12::/64, it will never generate a Type-9 LSAs or it will never include these prefixes in its Type-9 LSA as shown by the show ospfv3 database prefix self command:
R2#show ospfv3 database prefix self
OSPFv3 1 address-family ipv4 (router-id 0.0.0.2)
OSPFv3 1 address-family ipv6 (router-id 0.0.0.22)
R2#
The routing tables for both IPv4 and IPv6 of R3 displays no routes to the prefixes 12.0.0.0/24 and 12::/64:
R3#show ip route 12.0.0.0
% Network not in table
R3#
R3#show ipv route 12::
% Route not found
R3#
