It would appear from this query that you are advertizing thru sprint just
fine.
route-server.cerf.net>show ip bgp regexp _19105$
BGP table version is 2437100, local router ID is 134.24.38.246
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
* 205.243.23.0 192.157.69.5 20 0 1740 1239 19105
i
* 198.32.176.25 20 0 1740 1239 19105
i
*> 192.41.177.69 20 0 1740 1239 19105
i
* 134.24.88.55 20 0 1740 1239 19105
i
route-server.cerf.net>
Last I checked 1239 was sprint and 1740 was cerf.net.
And from ATT's network too:
route-server>show ip bgp reg _19105$
BGP table version is 14822297, local router ID is 12.0.1.28
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
* 205.243.23.0 12.123.145.124 0 7018 1239 19105
i
* 12.123.9.241 0 7018 1239 19105
i
* 12.123.25.245 0 7018 1239 19105
i
* 12.123.33.249 0 7018 1239 19105
i
* 12.123.134.124 0 7018 1239 19105
i
* 12.123.13.241 0 7018 1239 19105
i
* 12.123.137.124 0 7018 1239 19105
i
* 12.123.29.249 0 7018 1239 19105
i
* 12.123.142.124 0 7018 1239 19105
i
* 12.123.139.124 0 7018 1239 19105
i
* 12.123.17.244 0 7018 1239 19105
i
* 12.123.5.240 0 7018 1239 19105
i
* 12.123.45.252 0 7018 1239 19105
i
* 12.123.41.250 0 7018 1239 19105
i
* 12.123.21.243 0 7018 1239 19105
i
* 12.123.133.124 0 7018 1239 19105
i
* 12.123.37.250 0 7018 1239 19105
i
*> 12.123.1.236 0 7018 1239 19105
i
route-server>
"John Neiberger" <[EMAIL PROTECTED]> wrote in message
29633798.980448496061.JavaMail.imail@slippery">news:29633798.980448496061.JavaMail.imail@slippery...
> We have connections to Sprint and Verio and I had BGP up and running with
> Sprint for a couple of weeks. It appeared to me that they were
advertising
> our specific /24, 205.243.23.0, along with the rest of their
advertisements.
> Today, I turned up a BGP session with Verio, again just advertising our
/24.
>
> Soon afterward, with the help of lookingglass sites I noticed that
> everywhere I checked was using the Verio path, including Sprint! I know
> that a common cause of this would be if Sprint were not advertising our
> more-specific /24, but Verio was. This would create a more specific match
> through Verio. However, I don't think this is the case.
>
> Next, I prepended our AS, 19105, twice on the Verio side and then checked
> the LG sites again. Now, all were using the Sprint path. Next, I tried
> reducing the number of prepends to one and again most places--including
> Sprint--were using the Verio path.
>
> What would cause this behavior? Even with no prepends, it looks like the
AS
> path for a lot of these locations (NAPs) was the same length. If so, and
> both ISPs are advertising our /24 like they're supposed to be, why would I
> have to prepend our AS twice to force routers to choose the Sprint path?
>
> I think I just may have thought of a reason. If there were locations that
> were aggregating Sprint's routes before advertising them to peers, that
> would cause this behavior. But if that were the case, why would
prepending
> an AS matter at all? The Verio path would always be preferred because it
is
> most specific, right?
>
> Arg.... I *thought* I understood this!
>
> Any ideas?
>
> Thanks,
> John
>
>
>
>
>
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
>
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
