debug ip routing lots of odd output

topology;

 AREA1-[SW1]----AREA0----[SW2]-AREA2

here is an example below ,  i have two  3560 switches running ospf , both are in area 0 , and in SW2 , the debug ip routing is going crazy,  below routes are IA routes from area 1 .  SW1 is stable.

can anyone explain to me the output and what is possibly happening?

 

2y2w: RT: Try lookup less specific 10.66.0.94/32, default 0
2y2w: RT: Found subnet on less specific 10.66.0.92/30
2y2w: RT: Try lookup less specific 10.66.0.94/29, default 0
2y2w: RT: Failed found subnet on less specific
2y2w: RT: return NULL
2y2w: RT: Try lookup less specific 10.66.0.46/32, default 0
2y2w: RT: Found subnet on less specific 10.66.0.44/30
2y2w: RT: Try lookup less specific 10.66.0.46/29, default 0
2y2w: RT: Failed found subnet on less specific
2y2w: RT: return NULL
2y2w: RT: Try lookup less specific 10.141.9.26/32, default 0
2y2w: RT: Found subnet on less specific 10.141.9.24/30
2y2w: RT: Try lookup less specific 10.141.9.26/29, default 0
2y2w: RT: Failed found subnet on less specific
2y2w: RT: return NULL
2y2w: RT: Try lookup less specific 10.141.9.26/32, default 0
2y2w: RT: Found subnet on less specific 10.141.9.24/30
2y2w: RT: Try lookup less specific 10.141.9.26/29, default 0
2y2w: RT: Failed found subnet on less specific
2y2w: RT: return NULL
2y2w: RT: Try lookup less specific 10.1.160.1/32, default 0
2y2w: RT: Found subnet on less specific 10.1.160.0/30
2y2w: RT: Try lookup less specific 10.1.160.1/29, default 0
2y2w: RT: Failed found subnet on less specific
2y2w: RT: return NULL
2y2w: RT: Try lookup less specific 10.1.160.1/32, default 0
2y2w: RT: Found subnet on less specific 10.1.160.0/30
2y2w: RT: Try lookup less specific 10.1.160.1/29, default 0
2y2w: RT: Failed found subnet on less specific
2y2w: RT: return NULL

Comments

  • Can you post the config of both sw1 and sw2?  Is sw1 doing any summarizarion into area 0 from area 1?

     

     

  • no summarisation being done

    SW1

    router ospf 10
     router-id 172.20.0.1
     log-adjacency-changes
     timers throttle spf 10 100 5000
     timers throttle lsa all 10 100 5000
     timers lsa arrival 80
     passive-interface default
     no passive-interface Vlan11
     no passive-interface Vlan13
     no passive-interface Vlan111
     no passive-interface Vlan1111
     no passive-interface GigabitEthernet1/0/46
     network 10.1.4.64 0.0.0.15 area 1
     network 10.1.4.144 0.0.0.15 area 1
     network 10.1.60.0 0.0.0.255 area 1
     network 10.1.141.0 0.0.0.255 area 1
     network 10.1.150.0 0.0.0.255 area 1
     network 10.1.160.0 0.0.0.3 area 1
     network 10.8.36.222 0.0.0.0 area 1
     network 10.66.0.20 0.0.0.3 area 1
     network 10.66.0.40 0.0.0.3 area 1
     network 10.66.0.44 0.0.0.3 area 1
     network 10.66.0.52 0.0.0.3 area 1
     network 10.66.0.56 0.0.0.3 area 1
     network 10.66.0.60 0.0.0.3 area 1
     network 10.66.0.64 0.0.0.3 area 1
     network 10.66.0.68 0.0.0.3 area 1
     network 10.66.0.72 0.0.0.3 area 1
     network 10.66.0.76 0.0.0.3 area 1
     network 10.66.0.80 0.0.0.3 area 1
     network 10.66.0.88 0.0.0.3 area 1
     network 10.66.0.92 0.0.0.3 area 1
     network 10.66.0.105 0.0.0.0 area 1
     network 10.78.7.0 0.0.0.255 area 1
     network 10.85.0.250 0.0.0.0 area 1
     network 10.131.0.76 0.0.0.3 area 1
     network 10.137.0.4 0.0.0.3 area 1
     network 10.141.9.24 0.0.0.3 area 1
     network 172.17.140.0 0.0.0.255 area 1
     network 172.20.0.1 0.0.0.0 area 0
     network 172.20.0.10 0.0.0.0 area 0
     network 172.20.1.0 0.0.0.3 area 0
     network 172.20.1.4 0.0.0.3 area 0
     network 172.20.1.8 0.0.0.3 area 0
     network 172.20.1.21 0.0.0.0 area 0
     network 192.168.20.16 0.0.0.7 area 1
     network 192.168.30.99 0.0.0.0 area 1

     

    ip route 0.0.0.0 0.0.0.0 172.17.140.254 name DEFAULT

    SW2

    router ospf 10
     router-id 172.20.0.2
     log-adjacency-changes
     timers throttle spf 10 100 5000
     timers throttle lsa all 10 100 5000
     timers lsa arrival 80
     passive-interface default
     no passive-interface Vlan11
     no passive-interface Vlan111
     no passive-interface Vlan200
     no passive-interface Vlan1111
     no passive-interface GigabitEthernet0/46
     network 10.0.0.0 0.0.0.255 area 2
     network 10.1.4.128 0.0.0.7 area 2
     network 10.8.52.0 0.0.0.255 area 2
     network 10.77.0.4 0.0.0.3 area 2
     network 10.77.0.8 0.0.0.3 area 2
     network 10.77.0.12 0.0.0.3 area 2
     network 10.77.0.16 0.0.0.3 area 2
     network 10.77.0.20 0.0.0.3 area 2
     network 10.77.0.40 0.0.0.3 area 2
     network 10.77.0.44 0.0.0.3 area 2
     network 10.77.0.56 0.0.0.3 area 2
     network 10.77.0.60 0.0.0.3 area 2
     network 10.77.0.64 0.0.0.3 area 2
     network 10.134.0.0 0.0.0.255 area 2
     network 10.137.0.24 0.0.0.3 area 2
     network 10.181.0.0 0.0.255.255 area 2
     network 172.18.32.0 0.0.0.255 area 2
     network 172.20.0.2 0.0.0.0 area 0
     network 172.20.0.10 0.0.0.0 area 0
     network 172.20.1.0 0.0.0.3 area 0
     network 172.20.1.4 0.0.0.3 area 0
     network 172.20.1.8 0.0.0.3 area 0
     network 172.20.1.12 0.0.0.3 area 2
     network 172.20.1.33 0.0.0.0 area 0
     network 172.168.55.0 0.0.0.255 area 2

    ip route 0.0.0.0 0.0.0.0 10.0.0.1 name DEFAULT-ROUTE

     

  • 2y2w: RT: Try lookup less specific 10.66.0.94/32, default 0
    2y2w: RT: Found subnet on less specific 10.66.0.92/30
    2y2w: RT: Try lookup less specific 10.66.0.94/29, default 0
    2y2w: RT: Failed found subnet on less specific
    2y2w: RT: return NULL
    2y2w: RT: Try lookup less specific 10.66.0.46/32, default 0
    2y2w: RT: Found subnet on less specific 10.66.0.44/30
    2y2w: RT: Try lookup less specific 10.66.0.46/29, default 0
    2y2w: RT: Failed found subnet on less specific
    2y2w: RT: return NULL
    2y2w: RT: Try lookup less specific 10.141.9.26/32, default 0
    2y2w: RT: Found subnet on less specific 10.141.9.24/30
    2y2w: RT: Try lookup less specific 10.141.9.26/29, default 0
    2y2w: RT: Failed found subnet on less specific
    2y2w: RT: return NULL
    2y2w: RT: Try lookup less specific 10.141.9.26/32, default 0
    2y2w: RT: Found subnet on less specific 10.141.9.24/30
    2y2w: RT: Try lookup less specific 10.141.9.26/29, default 0
    2y2w: RT: Failed found subnet on less specific
    2y2w: RT: return NULL
    2y2w: RT: Try lookup less specific 10.1.160.1/32, default 0
    2y2w: RT: Found subnet on less specific 10.1.160.0/30
    2y2w: RT: Try lookup less specific 10.1.160.1/29, default 0
    2y2w: RT: Failed found subnet on less specific
    2y2w: RT: return NULL
    2y2w: RT: Try lookup less specific 10.1.160.1/32, default 0
    2y2w: RT: Found subnet on less specific 10.1.160.0/30
    2y2w: RT: Try lookup less specific 10.1.160.1/29, default 0
    2y2w: RT: Failed found subnet on less specific
    2y2w: RT: return NULL

     

    Are you also running BGP between SW1 & SW2?

  • no just ospf , and the  couple of static routes above

    i have noticed on switch1 , i have this in cef table for the default

    0.0.0.0/0            172.17.140.254       GigabitEthernet1/0/1
    0.0.0.0/32           receive         

     

    but on switch 2

     

    0.0.0.0/0            10.0.0.1             GigabitEthernet0/1
    0.0.0.0/8            drop
    0.0.0.0/32           receive

     

    i have no idea where the 0.0.0.0/8  comes from

     

    the rib of Sw2 below...

     

         192.168.30.0/25 is subnetted, 2 subnets
    O IA    192.168.30.0 [110/11] via 172.20.1.5, 1d19h, Vlan111
    C       192.168.30.128 is directly connected, Vlan159
         172.168.0.0/24 is subnetted, 1 subnets
    C       172.168.55.0 is directly connected, Vlan603
         172.17.0.0/24 is subnetted, 1 subnets
    O IA    172.17.140.0 [110/11] via 172.20.1.5, 2d02h, Vlan111
         172.20.0.0/16 is variably subnetted, 8 subnets, 2 masks
    C       172.20.1.32/30 is directly connected, Vlan200
    O IA    172.20.0.8/32 [110/16] via 172.20.1.34, 2d02h, Vlan200
    C       172.20.1.8/30 is directly connected, Vlan1111
    C       172.20.0.10/32 is directly connected, Loopback100
    O       172.20.0.1/32 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       172.20.0.2/32 is directly connected, Loopback10
    C       172.20.1.4/30 is directly connected, Vlan111
    O       172.20.0.7/32 [110/6] via 172.20.1.34, 2d02h, Vlan200
    C    192.168.200.0/24 is directly connected, GigabitEthernet0/40
         192.168.20.0/31 is subnetted, 2 subnets
    C       192.168.20.30 is directly connected, Vlan499
    C       192.168.20.14 is directly connected, Vlan499
         10.0.0.0/8 is variably subnetted, 51 subnets, 4 masks
    O IA    10.66.0.72/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.66.0.76/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.64/30 is directly connected, Vlan3844
    O IA    10.66.0.64/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.0.0.0/24 is directly connected, GigabitEthernet0/1
    O IA    10.66.0.68/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.66.0.92/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.66.0.80/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.66.0.104/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.1.42.0/30 is directly connected, GigabitEthernet0/14
    O IA    10.8.36.0/24 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.77.0.104/30 [110/16] via 172.20.1.34, 2d02h, Vlan200
    C       10.8.52.0/24 is directly connected, Vlan511
    O IA    10.1.60.0/24 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.75.1.0/24 [110/15] via 172.20.1.34, 2d02h, Vlan200
    O IA    10.78.7.0/24 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.0/30 is directly connected, Vlan1099
    C       10.77.0.12/30 is directly connected, Vlan501
    C       10.77.0.8/30 is directly connected, GigabitEthernet0/2
    O IA    10.1.4.64/28 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.20/30 is directly connected, Vlan90
    C       10.77.0.16/30 is directly connected, Vlan511
    C       10.77.0.28/30 is directly connected, Vlan91
    O IA    10.85.0.0/24 [110/11] via 172.20.1.5, 01:42:22, Vlan111
    C       10.77.0.24/30 is directly connected, Vlan139
    C       10.77.0.36/30 is directly connected, Vlan160
    O IA    10.66.0.44/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.32/30 is directly connected, Vlan191
    C       10.77.0.44/30 is directly connected, GigabitEthernet0/11
    C       10.77.0.40/30 is directly connected, GigabitEthernet0/10
    O IA    10.66.0.56/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.52/30 is directly connected, Vlan602
    O IA    10.66.0.60/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.48/30 is directly connected, GigabitEthernet0/35
    C       10.77.0.60/30 is directly connected, GigabitEthernet0/19
    O IA    10.66.0.52/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.77.0.56/30 is directly connected, Vlan603
    O IA    10.1.141.0/24 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.137.0.4/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.134.0.0/24 is directly connected, GigabitEthernet0/2
    C       10.1.4.128/29 is directly connected, Vlan90
    O IA    10.141.9.24/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    C       10.137.0.24/30 is directly connected, Vlan501
    O IA    10.1.150.0/24 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.1.4.144/28 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.1.160.0/30 [110/11] via 172.20.1.5, 2d02h, Vlan111
    O IA    10.181.13.0/24 [110/16] via 172.20.1.34, 2d02h, Vlan200
    C       10.181.5.0/24 is directly connected, Vlan2844
    C       10.181.4.0/24 is directly connected, Vlan197
    C       10.181.3.0/24 is directly connected, Vlan510
    C       10.181.2.0/24 is directly connected, Vlan500
    S*   0.0.0.0/0 [1/0] via 10.0.0.1

Sign In or Register to comment.