|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: BGP Routing problem
i believe (received-only) means that bgp soft-reconfiguration is configured for the peer and since some policy is denying the route, it won't be used .. unless a policy change occurs. here's what we're currently hearing from you folks... peer1.sjc1#sh ip bgp re 6180 BGP table version is 2830358, local router ID is 207.240.24.10 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 * i196.6.121.0 192.41.177.248 10 80 0 701 5713 6180 i * i 198.32.176.2 10 80 0 701 5713 6180 i *> 198.32.184.42 10 80 0 701 5713 6180 i * i196.28.5.0 192.41.177.248 10 80 0 701 5713 6180 i * i 198.32.176.2 10 80 0 701 5713 6180 i *> 198.32.184.42 10 80 0 701 5713 6180 i h 206.49.228.0 198.32.184.42 10 80 0 701 5713 6180 i * i 192.41.177.243 10 80 0 4000 6187 6180 i * i 192.157.69.80 10 80 0 4000 6187 6180 i *> 198.32.136.94 10 80 0 4000 6187 6180 i * i206.49.229.0 192.41.177.243 10 80 0 4000 6187 6180 i * i 192.157.69.80 10 80 0 4000 6187 6180 i *> 198.32.136.94 10 80 0 4000 6187 6180 i and it appears as though routing via alternet is working for the networks you mentioned. -danny > Hi > > We are a ISP in South Africa and have a problem we are trying to > figure out rather urgently, without much success so far. > > We are currently multi-homed during the day and tripple homed at > night. (our peaks are at night and we get cheap bandwidth from > another ISP who has their peak in the day). Internic has refused to > give us our own block of addresses which would have made thins much > simpler. (despite repeated attempts, and we now have 7 /24's from > various places and badly need more). > > Basicaly we (AS6180) have been announcing all our adresses including > 196.25.116.0, 196.25.117.0 and 196.25.203.0 via AS 3741 at night, > and this gets switched of during the day. The problem seems to relate > to the fact that these addresses are part of AS 5713's CIDR > 196.25.0.0/16 and we thought we could get away with announcing them > like this. It did work fine for over a week, but now today we have a > problem. > > MAE-East (see example at end of message) , the Sprintnap and who > knows who else still have entries for these via AS3741 but they are > showing as received-only, and no best path. Yet via MAE West they are > fine. > > We are going to stop announcing these via AS3741 at night, but its > been 9 hours now since they were not announced and these > received-only entries are still sitting there blocking these routes > from it seems about a third of the internet. > > Can any one offer any comments on why they are still there, what > received-only means and how we can get if fixed? > > Many thanks > Regards > Anthony Walker > > > MAE-East Looking Glass Results > Query: bgp > Addr: 196.25.203.0 > BGP routing table entry for 196.25.203.0/24, version 5006458 > Paths: (1 available, no best path, advertised over IBGP) > 1673 1239 4005 3741 6180, (received-only) > 192.41.177.141 from 192.41.177.141 (140.223.57.217) > Origin IGP, external
|