OSPF incorrectly generates summary LSA when using area range command #17079
Description
Description
We use area X.X.X.X range A.B.C.D/M not-advertise(or advertise) commands to filter intra area paths , when the area X.X.X.X does not exist, ospf will incorrectly generate the Type3 LSA of this area.
Version
10.3
How to reproduce
configure of router r0
router ospf
ospf router-id 0.0.0.1
interface r0-eth0
ip address 194.97.141.182/14
ip ospf area 0.0.0.1
interface r0-eth1
ip address 204.234.174.128/11
ip ospf area 0.0.0.0
then, we use commands
router ospf
area 32.34.40.120 range 204.234.174.128/11 not-advertise
Expected behavior
The router's LSDB should be
OSPF Router with ID (0.0.0.1)
Router Link States (Area 0.0.0.0)
Link ID ADV Router Age Seq# CkSum Link count
0.0.0.1 0.0.0.1 5 0x80000002 0x9b1b 1
Summary Link States (Area 0.0.0.0)
Link ID ADV Router Age Seq# CkSum Route
194.96.0.0 0.0.0.1 5 0x80000001 0x55dc 194.96.0.0/14
Router Link States (Area 0.0.0.1)
Link ID ADV Router Age Seq# CkSum Link count
0.0.0.1 0.0.0.1 5 0x80000002 0xa282 1
Summary Link States (Area 0.0.0.1)
Link ID ADV Router Age Seq# CkSum Route
204.224.0.0 0.0.0.1 5 0x80000001 0x5c67 204.224.0.0/11
Actual behavior
The router's LSDB is actually the above following
Summary Link States (Area 32.34.40.120)
Link ID ADV Router Age Seq# CkSum Route
194.96.0.0 0.0.0.1 2 0x80000001 0x55dc 194.96.0.0/14
204.224.0.0 0.0.0.1 2 0x80000001 0x5c67 204.224.0.0/11
The type3 LSA of area 32.34.40.120 is redundant and should not exist. Because the area with ID 32.34.40.120 does not exist in this network.
Additional context
No response
Checklist
- I have searched the open issues for this bug.
- I have not included sensitive information in this report.