[c-nsp] FW: Cisco/OSPF/EIGRP/7206/routing

Drew Weaver drew.weaver at thenap.com
Fri Apr 14 12:32:46 EDT 2006


border#sh ip eigrp topo 10.1.0.1 255.255.255.0
IP-EIGRP topology entry for 10.1.0.1/24
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is
2181120
  Routing Descriptor Blocks:
  172.16.0.1 (FastEthernet1/1/0), from 172.16.0.1, Send flag is 0x0
      Composite metric is (2181120/2178560), Route is External
      Vector metric:
        Minimum bandwidth is 1536 Kbit
        Total delay is 20100 microseconds
        Reliability is 255/255
        Load is 82/255
        Minimum MTU is 1500
        Hop count is 1
      External data:
        Originating router is 192.168.1.1
        AS number of route is 0
        External protocol is Static, external metric is 0
        Administrator tag is 0 (0x00000000)

That is when redistribute static is present in eigrp config on CORE
(which is the router in which the bonded T1s are connected) and I run
that command from border, which is the router upstream from it.

core#sh ip eigrp topo 10.1.0.0 255.255.255.0
IP-EIGRP topology entry for 10.1.0.0/24
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is
2178560
  Routing Descriptor Blocks:
  0.0.0.0, from Redistributed, Send flag is 0x0
      Composite metric is (2178560/0), Route is External
      Vector metric:
        Minimum bandwidth is 1536 Kbit
        Total delay is 20000 microseconds
        Reliability is 255/255
        Load is 82/255
        Minimum MTU is 1500
        Hop count is 0
      External data:
        Originating router is 192.168.1.1 (this system)
        AS number of route is 0
        External protocol is Static, external metric is 0
        Administrator tag is 0 (0x00000000)

This is from core, the actual router in which the T1s are bonded in.

Thanks for having a look. I appreciate it.
Andrew

-----Original Message-----
From: Scott Altman [mailto:staltman at gmail.com] 
Sent: Friday, April 14, 2006 12:11 PM
To: Drew Weaver
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Cisco/OSPF/EIGRP/7206/routing

The 10.1.0.0 route is being sourced from somewhere, perhaps not the
router in question?  When you do a 'show ip eigrp topo 10.1.0.0
255.255.255.0' what are the results?

On 4/14/06, Drew Weaver <drew.weaver at thenap.com> wrote:
>
> Observations:
>
> On the router that is exporting routes:
>
> core#sh ip route 10.1.0.0
> Routing entry for 10.1.0.0/24
>   Known via "static", distance 1, metric 0
>   Redistributing via eigrp 1, ospf 1
>   Advertised by eigrp 1 route-map FILTERDEFAULT
>                 ospf 1 subnets route-map FILTERDEFAULT
>   Routing Descriptor Blocks:
>   * 192.168.1.2
>       Route metric is 0, traffic share count is 1
>
> If I remove the redistribute static command from eigrp:
>
> core#sh ip route 10.1.0.0
> Routing entry for 10.1.0.0/24
>   Known via "static", distance 1, metric 0
>   Redistributing via eigrp 1, ospf 1
>   Advertised by ospf 1 subnets route-map FILTERDEFAULT
>   Routing Descriptor Blocks:
>   * 192.168.1.2
>       Route metric is 0, traffic share count is 1
>
> You can see that this router is redistributing this route into eigrp
and
> ospf.
>
> On this router's neighbor:
>
> border#sh ip route eigrp | i 10.1.0.0
> D EX 10.1.0.0/24
>
> border#sh ip route ospf | i 10.1.0.0
> border#
>
> ^(this behaviour is expected because a route will only appear in a
> single protocol at a time).
>
> If I look in the ospf database:
>
> border#sh ip ospf database | i 10.1.0.0
> 10.1.0.0   192.168.1.1   885    0x80001707 0xF587   0
>
> The entry does appear.
>
> I suppose the question is:
>
> Why, when I remove the command: redistribute static from the eigrp
> config, on this 7206,
> does the route: 10.1.0.0/24 not appear in OSPF?
>
> Here is a little more background information incase it helps:
>
> 192.168.1.1 is Loopback4 on the 7206 it is used to bond multiple
> interfaces together (Serial).
>
> I have been through and through the configurations on both routers;
and
> I wouldn't ask such a ridiculous question if I hadn't.
>
> Does anyone have any insight?
>
> Thanks,
> Andrew
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>



More information about the cisco-nsp mailing list