[nsp] BGP routes received but not used
Adam Kujawski
adamkuj@amplex.net
Wed, 06 Nov 2002 11:33:07 -0500
We ended up changing IOS versions from 12.2(4)T3 to 12.2(12a) and the
problem appears to be resolved.
Thanks,
Adam
At 04:42 PM 11/4/2002, MPuras@solunet.com wrote:
>I think this is an IOS issue. There is nothing wrong with the config. By
>default if no address family is specified, Unicast address family is
>supported for that neighbor. So the fact that you got the "address family"
>error tells me that this could just be the IOS acting up.
>
>
>
>Thanks,
>
>Mario Puras
>SoluNet Technical Support
>Mailto: mpuras@solunet.com
>Direct: (321) 309-1410
>888.449.5766 (USA) / 888.SOLUNET (Canada)
>
>
>
>-----Original Message-----
>From: Adam Kujawski [mailto:adamkuj@amplex.net]
>Sent: Monday, November 04, 2002 4:07 PM
>To: MPuras@solunet.com
>Cc: cisco-nsp@puck.nether.net
>Subject: RE: [nsp] BGP routes received but not used
>
>
>Here's the basic BGP config:
>
>router bgp 20205
> no synchronization
> network XXX.XXX.XXX.0 mask 255.255.254.0
> neighbor 65.207.235.181 remote-as 701
> neighbor 144.223.18.33 remote-as 1239
> no auto-summary
> !
> address-family ipv4 multicast
> neighbor 144.223.18.33 activate
> network XXX.XXX.XXX.0 mask 255.255.254.0
> exit-address-family
>!
>
>As far as I can tell, this seems to be the correct format for the "new"
>syntax. However, I did notice that when saving or copying the running
>config, I got an 'Address-family not configured' message. Is there
>something wrong with the above config outline?
>
>I removed the ipv4 multicast address family and did a soft inbound reset on
>the neighbors and it didn't change anything - the routes were still not
>working. Oddly enough, adding the multicast address family back appears to
>have fixed the problem... or at least the routes that weren't working
>before are working now. I don't expect this to last... a reboot usually
>fixes the problem temporarily. It's acting pretty strange... I'm starting
>to think it is just an IOS error.
>
>Thanks,
>Adam
>
>
>
>
>Thanks,
>Adam
>
>
>
>
>
>At 08:40 AM 11/4/2002, MPuras@solunet.com wrote:
> >Hi. Check that your next-hop for that route is in the routing table. That
> >you have added the "activate" key word after the multicast neighbor or
> >unicast neighbor. If this is supposed to be a route learned from your
> >multicast enable peer, then check to make sure that your RPF table shows
> >this route as being in there otherwise it will not place it into the
>routing
> >table. Can you post the " show ip bgp ipv4 multicast" commands for that
> >route and perhaps the relevant bgp config?
> >
> >
> >
> >
> >Thanks,
> >
> >Mario Puras
> >SoluNet Technical Support
> >Mailto: mpuras@solunet.com
> >Direct: (321) 309-1410
> >888.449.5766 (USA) / 888.SOLUNET (Canada)
> >
> >
> >
> >-----Original Message-----
> >From: Adam Kujawski [mailto:adamkuj@amplex.net]
> >Sent: Monday, November 04, 2002 1:06 AM
> >To: cisco-nsp@puck.nether.net
> >Subject: [nsp] BGP routes received but not used
> >
> >
> >We have a 3660 running 12.2(4)T3 with 256 MB RAM. We are multihomed to two
> >providers, and take full routes from both (about 113000 routes from each
> >provider, according to 'show ip bgp sum'). We recently enabled MBGP with
> >one of the upstreams. Since that time, we've had to add a default route to
> >one of our providers, because routes received via BGP were not always being
> >seen. It does not appear to be a memory problem - the router reports over
> >130 MB of free RAM.
> >
> >'show ip route summary' gives the following:
> >
> >IP routing table name is Default-IP-Routing-Table(0)
> >Route Source Networks Subnets Overhead Memory (bytes)
> >connected 1 28 2056 4176
> >static 4 30 2676 4896
> >ospf 100 0 5 320 720
> > Intra-area: 3 Inter-area: 2 External-1: 0 External-2: 0
> > NSSA External-1: 0 NSSA External-2: 0
> >bgp 20205 81508 30070 7140992 16230432
> > External: 111578 Internal: 0 Local: 0
> >internal 1149 1337436
> >Total 82662 30133 7146044 17577660
> >
> >For example, www.cisco.com resolves to 198.133.219.25.
> >
> >'show ip bgp 198.133.219.25' gives the following:
> >
> >BGP routing table entry for 198.133.219.0/24, version 276733
> >Paths: (2 available, best #2)
> > XXXX 109
> > XXX.XXX.XXX.XXX from XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX)
> > Origin IGP, metric 98, localpref 100, valid, external
> > XXXX 109
> > XXX.XXX.XXX.XXX from XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX)
> > Origin IGP, localpref 100, valid, external, best
> >
> >However, 'show ip route 198.133.219.25' gives the following:
> >
> >% Network not in table
> >
> >Without a default route, packets to 198.133.219.25 die at our router.
> >
> >Any ideas?
> >
> >Thanks,
> >Adam
> >
> >
> >
> >
> >
> > Adam Kujawski adamkuj@amplex.net
> > Network Administrator Cell: 419.261.3268
> > Amplex Internet Services Office: 419.720.3635
> >
> >_______________________________________________
> >cisco-nsp mailing list real_name)s@puck.nether.net
> >http://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
> Adam Kujawski adamkuj@amplex.net
> Network Administrator Cell: 419.261.3268
> Amplex Internet Services Office: 419.720.3635
>_______________________________________________
>cisco-nsp mailing list real_name)s@puck.nether.net
>http://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
Adam Kujawski adamkuj@amplex.net
Network Administrator Cell: 419.261.3268
Amplex Internet Services Office: 419.720.3635