From: Spicer, Troy (SpicerT@xxxxxxxxxxxx)
Date: Fri Jul 14 2000 - 00:38:26 GMT-3
Title: RE: BGP Sync Problem
It seems that a couple good random power outages to the whole rack did
the trick of fixing the sync/no sync problem.
I'm glad to say it was that easy and that I didn't discover some
horrible caveat to sync/no sync.
-----Original Message-----
From: Kevin M. Woods [mailto:kev@nil.org]
Sent: Thursday, July 13, 2000 3:10 PM
To: Spicer, Troy
Cc: 'ccielab@groupstudy.com'
Subject: Re: BGP Sync Problem
// I'm assuming that IA and E2 areas are not good enough to sync. I
just
// added a 155.1.1.1 in the same area as this router and it syncs up
without a
// problem. Can anyone confirm?
I don't know about IA, but E1/2 will certainly allow BGP to
synchronize since
that's exactly what it's looking for (EBGP routes redistributed into
an IGP).
The problem is that the E2 route is coming from RIP instead of EBGP
(although
I think OSPF is the only protocol in which this is an issue).
// Given a BGP table of
//
// BGP table version is 7, local router ID is 40.1.1.1
// Status codes: s suppressed, d damped, h history, * valid, > best, i
-
// internal
// Origin codes: i - IGP, e - EGP, ? - incomplete
//
// Network Next Hop Metric LocPrf Weight Path
// *> 20.1.1.0/24 0.0.0.0 0 32768 ?
// *>i103.0.0.0 30.1.1.4 1 100 0 6000 e
<-no sync
// *>i151.1.1.1/32 30.1.1.4 0 100 0 i <-no
sync
// *>i152.1.1.1/32 30.1.1.4 0 100 0 i <-no
sync
// *>i153.1.1.1/32 30.1.1.4 0 100 0 i <-no
sync
// *>i154.1.1.1/32 30.1.1.4 0 100 0 i
<-synced static route added
// *>i155.1.1.1/32 20.1.1.2 0 100 0 i
<-synced same ospf area
That's weird output...according to it all those routes are
synchronized. I'm
interested in knowing what IOS version this is. Did you know the
routes were
not sync'd from "s ip bgp A.B.C.D"?
Kevin
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:53 GMT-3