Skip to content

OSPF incorrectly set ASBR flag in router lsa when unset nssa area #17084

@Shbinging

Description

@Shbinging

Description

When OSPF is configured with nssa, if hello-multiplier is set on the backbone interface, Type4 LSA will be generated incorrectly.

Version

10.3(with latest commit in master branch)

How to reproduce

Consider two routers r2, r4 and following topo.

   +--------+                 +--------+          
   |        |      area 0     |        |          
   |   r2   +-----------------+   r4   |          
   |        |                 |        |          
   +---+----+                 +----+---+          
       |                           |              
       |                           |              
       |                           |              
       |                           |              
      +++ area 2                  +++ area 1      
      | | stub network            | | stub network
      | | nssa                    | |             
      | |                         | |             
      +-+                         +-+             
                                                  

r2 conf is

interface r2-eth3
 ip address 133.212.247.199/15
exit
!
interface r2-eth5
 ip address 207.235.166.38/17
 ip ospf dead-interval minimal hello-multiplier 10
exit
!
router ospf
 ospf router-id 0.0.0.2
 timers throttle spf 0 0 1
 network 133.212.247.199/32 area 0.0.0.1
 network 207.235.166.38/32 area 0.0.0.0
exit

r4 conf is

interface r2-eth3
 ip address 133.212.247.199/15
exit
!
interface r2-eth5
 ip address 207.235.166.38/17
 ip ospf dead-interval minimal hello-multiplier 10
exit
!
router ospf
 ospf router-id 0.0.0.2
 timers throttle spf 0 0 1
 network 133.212.247.199/32 area 0.0.0.1
 network 207.235.166.38/32 area 0.0.0.0
exit

Expected behavior

When we check r2's database, we should get only type1, type 2, type 3 lsa.

               Router Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Link count
0.0.0.2        0.0.0.2           20 0x80000005 0x32fe 1
0.0.0.4        0.0.0.4           20 0x80000005 0x0a22 1

                Net Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum
207.235.166.37 0.0.0.4           21 0x80000001 0xf651

                Summary Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Route
133.212.0.0    0.0.0.2           21 0x80000001 0xfdf9 133.212.0.0/15
177.64.0.0     0.0.0.4           22 0x80000001 0x324a 177.64.0.0/11

                Router Link States (Area 0.0.0.1)

Link ID         ADV Router      Age  Seq#       CkSum  Link count
0.0.0.2        0.0.0.2           21 0x80000002 0xa148 1

                Summary Link States (Area 0.0.0.1)

Link ID         ADV Router      Age  Seq#       CkSum  Route
177.64.0.0     0.0.0.2           15 0x80000001 0xa2d1 177.64.0.0/11
207.235.128.0  0.0.0.2           20 0x80000002 0x2271 207.235.128.0/17

Actual behavior

r2 generated wrong type4 LSA

                ASBR-Summary Link States (Area 0.0.0.1)

Link ID         ADV Router      Age  Seq#       CkSum
0.0.0.4        0.0.0.2           15 0x80000001 0x8dbe

Additional context

No response

Checklist

  • I have searched the open issues for this bug.
  • I have not included sensitive information in this report.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageNeeds further investigation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions