Description

This article explains why route 128.0.0.0/2 is shown in the OSPF database even though "interface all" is specified. The route must be disabled; a procedure for doing so is provided.

Symptoms

Route 128.0.0.0/2 is shown in OSPF (Open Shortest Path First) database. This can cause issues in reaching all the public IPs which fall in this subnet. Our goal is to remove this route from the database.

Solution

When interface all is specified, interface fxp1 also participates in OSPF peering and advertises this route (see the OSPF database below):

{primary:node0}[edit]
root@100-1# run show ospf interface
Interface           State   Area            DR ID           BDR ID          Nbrs
fxp1.0              DR      0.0.0.0         129.32.0.1      0.0.0.0            0
reth0.0             BDR     0.0.0.0         0.0.0.22        129.32.0.1         2
If we check the OSPF database detail output:
root@100-2# run show ospf database detail | no-more

    OSPF database, Area 0.0.0.0
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Router   0.0.0.22         0.0.0.22         0x800001bf   108  0x22 0x7983  36
  bits 0x0, link count 1
  id 172.27.201.147, data 172.27.201.147, Type Transit (2)
    Topology count: 0, Default metric: 1
  Topology default (ID 0)
    Type: Transit, Node ID: 172.27.201.147
      Metric: 1, Bidirectional
Router   129.32.0.1       129.32.0.1       0x80000004    79  0x22 0xd508  48>>>>>>>>>>>>>>>>>Advertised by fxp1
  bits 0x0, link count 2
  id 128.0.0.0, data 192.0.0.0, Type Stub (3)>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Topology count: 0, Default metric: 1
  id 172.27.201.147, data 172.27.201.4, Type Transit (2)
    Topology count: 0, Default metric: 1
  Topology default (ID 0)
    Type: Transit, Node ID: 172.27.201.147
      Metric: 1, Bidirectional
Router  *172.27.201.5     172.27.201.5     0x80000002   103  0x22 0x1831  36
  bits 0x0, link count 1
  id 172.27.201.147, data 172.27.201.5, Type Transit (2)
    Topology count: 0, Default metric: 1
  Topology default (ID 0)
    Type: Transit, Node ID: 172.27.201.147
      Metric: 1, Bidirectional
Network  172.27.201.147   0.0.0.22         0x80000002   103  0x22 0x6545  36
  mask 255.255.255.0
  attached router 0.0.0.22
  attached router 172.27.201.5
  attached router 129.32.0.1
  Topology default (ID 0)
    Type: Transit, Node ID: 129.32.0.1
      Metric: 0, Bidirectional
    Type: Transit, Node ID: 172.27.201.5
      Metric: 0, Bidirectional
    Type: Transit, Node ID: 0.0.0.22
      Metric: 0, Bidirectional
On the one of the peers we can see the route:
root@100-2# run show route protocol ospf

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

128.0.0.0/2        *[OSPF/10] 00:00:27, metric 2
                    > to 172.27.201.4 via fe-0/0/5.0


Disable OSPF under fxp1 as follows:

protocols {
    ospf {
        area 0.0.0.0 {
            interface all;
            interface fxp1.0 {
                disable;
            }
        }
    }
}
After this change, the route is no longer advertised.