search

MERAprojects / ops-quagga

GNU General Public License v2.0
0 stars 0 forks source link

OSPFv2: After some time default route disappears from route table #21

Closed xivamar closed 7 years ago

xivamar commented 8 years ago

Problem Description:

On DUT2 we configure default route and distribute it in OSPF. After ~ 40 min default route disappears from route table on other DUTs.

OpenSwitch version:

OpenSwitch 1.0.0 (Build: appliance-ops-1.0.0-release+2016090200)

Test Topology:

ospf_topology

Steps to reproduce the problem:

  1. Configure DUTs as in attached file.

  2. Check routing table via show ip route on DUT3 and DUT4.

    on DUT3:

     switch# show ip route 
 Displaying ipv4 routes selected for forwarding
 '[x/y]' denotes [distance/metric]
 0.0.0.0/0,  1 unicast next-hops 
     via  172.16.1.1,  [110/10],  ospf
 172.16.1.0/24,  1 unicast next-hops 
     via  eth1,  [0/0],  connected
 172.16.10.4/30,  1 unicast next-hops 
     via  eth2,  [0/0],  connected
 172.16.20.0/24,  1 unicast next-hops 
     via  172.16.10.6,  [110/20],  ospf
 172.16.51.0/24,  1 unicast next-hops 
     via  172.16.1.2,  [110/20],  ospf
 192.168.3.1/32,  1 unicast next-hops 
     via  lo1,  [0/0],  connected
 switch#

    on DUT4:

     switch# show ip route 
 Displaying ipv4 routes selected for forwarding
 '[x/y]' denotes [distance/metric]
 0.0.0.0/0,  1 unicast next-hops 
     via  172.16.10.5,  [110/11],  ospf
 172.16.1.0/24,  1 unicast next-hops 
     via  172.16.10.5,  [110/20],  ospf
 172.16.10.4/30,  1 unicast next-hops 
     via  eth2,  [0/0],  connected
 172.16.20.0/24,  1 unicast next-hops 
     via  eth1,  [0/0],  connected
 172.16.51.0/24,  1 unicast next-hops 
     via  172.16.10.5,  [110/30],  ospf
 192.168.4.1/32,  1 unicast next-hops 
     via  lo1,  [0/0],  connected
 switch#
  3. Check routing table via show ip route after ~ 40 min. - NOK: default route is disappeared from route table

on DUT3:

   switch# show ip route 
   Displaying ipv4 routes selected for forwarding
   '[x/y]' denotes [distance/metric]
   172.16.1.0/24,  1 unicast next-hops 
           via  eth1,  [0/0],  connected
   172.16.10.4/30,  1 unicast next-hops 
       via  eth2,  [0/0],  connected
   172.16.20.0/24,  1 unicast next-hops 
       via  172.16.10.6,  [110/20],  ospf
   172.16.51.0/24,  1 unicast next-hops 
       via  172.16.1.2,  [110/20],  ospf
   192.168.3.1/32,  1 unicast next-hops 
       via  lo1,  [0/0],  connected
   switch#

config.txt

xivamar commented 7 years ago

fixed.