[c-nsp] BGP, RIP and default routes advice

Marco Matarazzo marmata at libero.it
Thu Aug 5 11:23:57 EDT 2004


Border is a 7200 with NPE-400 running  Version 12.2(24a)
Downstream is 3550-SMI running Version 12.1(22)EA1

I didn't check for bugs on cco... but I'll search for that, you never know!
;)

Cheers,
]\/[arco

----- Original Message ----- 
From: "Rodney Dunn" <rodunn at cisco.com>
To: "Rodney Dunn" <rodunn at cisco.com>
Cc: "Marco Matarazzo" <marmata at libero.it>; "Sam Stickland"
<sam_ml at spacething.org>; <cisco-nsp at puck.nether.net>
Sent: Thursday, August 05, 2004 5:11 PM
Subject: Re: [c-nsp] BGP, RIP and default routes advice


> That test I did was on 12.2(12f).
>
> What code are you trying that on?
>
> I missed the fact that you said it wasn't
> in the database.  Sorry..
>
> For RIP you don't need it in the routing table
> for RIP to orginate it.
>
> Rodney
>
> On Thu, Aug 05, 2004 at 11:09:34AM -0400, Rodney Dunn wrote:
> > Did you check the downstream router?
> >
> > Try looking at the full 'sh log' or
> > try "sh log | incl RIP|tag".
> >
> > hub_#sh ip ro
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> >        D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> >        N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> >        E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> >        i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter area
> >        * - candidate default, U - per-user static route, o - ODR
> >        P - periodic downloaded static route
> >
> > Gateway of last resort is not set
> >
> >      1.0.0.0/24 is subnetted, 1 subnets
> > C       1.1.1.0 is directly connected, Serial2/0.1
> >      4.0.0.0/32 is subnetted, 1 subnets
> > C       4.4.4.1 is directly connected, Loopback0
> > hub_#sh ip rip da
> > hub_#sh ip rip database
> > 0.0.0.0/0    auto-summary
> > 0.0.0.0/0    redistributed
> >     [0] via 0.0.0.0,
> > 1.0.0.0/8    auto-summary
> > 1.1.1.0/24    directly connected, Serial2/0.1
> > 4.0.0.0/8    auto-summary
> > 4.4.4.1/32    directly connected, Loopback0
> > hub_#debug ip rip
> > RIP protocol debugging is on
> > hub_#
> > *Aug  5 15:06:43.514: RIP: sending v2 update to 224.0.0.9 via
Serial2/0.1 (1.1.1.1)
> > *Aug  5 15:06:43.514: RIP: build update entries
> > *Aug  5 15:06:43.514:   0.0.0.0/0 via 0.0.0.0, metric 1, tag 0
> > *Aug  5 15:06:43.514:   4.0.0.0/8 via 0.0.0.0, metric 1, tag 0
> > *Aug  5 15:06:43.514: RIP: sending v2 update to 224.0.0.9 via Loopback0
(4.4.4.1)
> > *Aug  5 15:06:43.514: RIP: build update entries
> > *Aug  5 15:06:43.514:   0.0.0.0/0 via 0.0.0.0, metric 1, tag 0
> > *Aug  5 15:06:43.514:   1.0.0.0/8 via 0.0.0.0, metric 1, tag 0
> > *Aug  5 15:06:43.566: RIP: ignored v2 packet from 4.4.4.1 (sourced from
one of our addresses)
> > hub_#un all
> > All possible debugging has been turned off
> >
> > You show command would have missed  it because the route is on
> > a separate line.
> >
> > See if that is what it is.
> >
> > Rodney
> >
> > On Thu, Aug 05, 2004 at 04:47:00PM +0200, Marco Matarazzo wrote:
> > > I tried that, but it's not working, so I thought that without a
default
> > > router installed, it wouldn't originate one:
> > >
> > > Border router:
> > >
> > > router rip
> > >  version 2
> > >  passive-interface default
> > >  no passive-interface FastEthernet0/0.6
> > >  network 1.1.1.1
> > >  default-information originate
> > >  no auto-summary
> > >
> > > sh ip route
> > > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > >        D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> > >        N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> > >        E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > >        i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
level-2
> > >        ia - IS-IS inter area, * - candidate default, U - per-user
static
> > > route
> > >        o - ODR, P - periodic downloaded static route
> > >
> > > Gateway of last resort is not set
> > >
> > > [output omitted]
> > >
> > > sh ip rip dat
> > > 1.0.0.0/8    auto-summary
> > > 1.1.1.0/20    directly connected, Null0
> > > 1.1.1.1/29    directly connected, FastEthernet0/0.6
> > >
> > > sh log | in RIP
> > > Aug  5 16:43:30.621: RIP-DB: redist 0.0.0.0/0(metric 0) to RIP
> > > Aug  5 16:43:43.129: RIP-TIMER: periodic timer expired
> > > Aug  5 16:43:43.129: RIP: sending v2 update to 224.0.0.9 via
> > > FastEthernet0/0.6 (81.29.192.82)
> > > Aug  5 16:43:43.129: RIP: build update entries
> > > Aug  5 16:43:43.129: RIP: Update contains 1 routes
> > > Aug  5 16:43:43.129: RIP: Update queued
> > > Aug  5 16:43:43.129: RIP: Update sent via FastEthernet0/0.6
> > >
> > > It's sending always only one route, the default is never sent, and
it's not
> > > in the RIP database... but from the debug output, it seems to
redistribute
> > > 0.0.0.0/0 to RIP... what can be wrong?!?!
> > >
> > > Cheers,
> > > ]\/[arco
> > >
> > >
> > > ----- Original Message ----- 
> > > From: "Rodney Dunn" <rodunn at cisco.com>
> > > To: "Sam Stickland" <sam_ml at spacething.org>
> > > Cc: "Marco Matarazzo" <marmata at libero.it>; <cisco-nsp at puck.nether.net>
> > > Sent: Thursday, August 05, 2004 3:14 PM
> > > Subject: Re: [c-nsp] BGP, RIP and default routes advice
> > >
> > >
> > > > Yep...
> > > >
> > > >
> > > > hub_#sh run | begin router rip
> > > > router rip
> > > >  version 2
> > > >  network 1.0.0.0
> > > >  network 4.0.0.0
> > > >  default-information originate
> > > >
> > > > hub_#sh ip ro
> > > > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > > >        D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > > >        N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > > >        E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > > >        i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter
> > > area
> > > >        * - candidate default, U - per-user static route, o - ODR
> > > >        P - periodic downloaded static route
> > > >
> > > > Gateway of last resort is not set
> > > >
> > > >      1.0.0.0/24 is subnetted, 1 subnets
> > > > C       1.1.1.0 is directly connected, Serial2/0.1
> > > >      4.0.0.0/32 is subnetted, 1 subnets
> > > > C       4.4.4.1 is directly connected, Loopback0
> > > >
> > > >
> > > > downstream spoke:
> > > >
> > > > spokeA_#sh ip ro
> > > > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > > >        D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > > >        N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > > >        E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > > >        i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter
> > > area
> > > >        * - candidate default, U - per-user static route, o - ODR
> > > >        P - periodic downloaded static route
> > > >
> > > > Gateway of last resort is 1.1.1.1 to network 0.0.0.0
> > > >
> > > >      1.0.0.0/24 is subnetted, 1 subnets
> > > > C       1.1.1.0 is directly connected, Serial3/0.1
> > > > R    4.0.0.0/8 [120/1] via 1.1.1.1, 00:00:10, Serial3/0.1
> > > > R*   0.0.0.0/0 [120/1] via 1.1.1.1, 00:00:10, Serial3/0.1
> > > >
> > > >
> > > > Rodney
> > > >
> > > > On Thu, Aug 05, 2004 at 02:02:12PM +0100, Sam Stickland wrote:
> > > > > Is there an RIP equivalent of BGP's 'neighbor default-originate'?
> > > > >
> > > > > (
> > > > >
> > >
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/iprrp_r/ip2_n1g.htm#wp1037042
> > > > > )
> > > > >
> > > > > In fact, a quick google search has just shown me that there is :)
> > > > >
> > > > >
> > >
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_r/1rprt1/1rrip.htm#1017420
> > > > >
> > > > > Looks like this ought to do the trick:
> > > > >
> > > > > router rip
> > > > >   default-information originate
> > > > >
> > > > > If it works like the bgp default-originate there's no need to have
a
> > > > > default route on the borders for this to work.
> > > > >
> > > > > Sam
> > > > >
> > > > > On Thu, 5 Aug 2004, Marco Matarazzo wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I've a little question to ask about default routes and their
> > > redistribution
> > > > > > in RIP.
> > > > > >
> > > > > > Right now I've two border 7200s speaking eBGP with two ISPs, and
iBGP
> > > > > > between them. The eBGP peers are full, without default. The
internal
> > > router
> > > > > > now is an OpenBSD with zebra, taking participating in the iBGP
peers.
> > > No
> > > > > > problems so far, zebra has the full routing tables, and knows
how to
> > > route
> > > > > > packets in the world.
> > > > > > We're in the process of removing the OpenBSD router, and install
some
> > > > > > 3550-48-SMIs as customer facing routers. They'll run RIP (it's
SMI)
> > > with the
> > > > > > two borders, and redistribute the connected customer routes to
them.
> > > Of
> > > > > > course those 3550s must also have a default route. And this is
the
> > > problem.
> > > > > > I don't want to configure a couple of static ones, since it's
all
> > > ethernet,
> > > > > > and the interfaces won't go down, and the backup default will
never
> > > catch
> > > > > > in. Also I don't take default from the upstreams, so I must
create one
> > > on
> > > > > > the borders. Connection to the upstreams is also ethernet, so no
> > > statics
> > > > > > here. From what I understand, I'll have to use the ip
default-network
> > > > > > statement, but which network to use? Have you any suggestion?
> > > > > > Could I just take the network number of a couple large NAPs in
the
> > > region,
> > > > > > hoping that they won't do a mantainance of the electrical panels
in
> > > the same
> > > > > > hours of the same day? :)
> > > > > >
> > > > > > TIA!
> > > > > > ]\/[arco
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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/
> > > > > >
> > > > > _______________________________________________
> > > > > 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