Solved: Basic BGP config - ISP not see announcements

srroeder · ‎03-16-2010

I am setting up my first BGP connection to our ISP and when we turned it on I receive his feed but he does not the subnets I am trying to announce.

Any of you BGP gurus out there care to tell me what I am doing wrong? Is it the Null0 route? Should I just direct the subnets to his next hop??

Any help is appreciated.

Here is my config.

router bgp 11111
no synchronization
no bgp log-neighbor-changes
network 180.7.253.0
network 180.7.254.0
redistribute static
neighbor 4.4.4.4 remote-as 22222
no auto-summary
!
ip route 0.0.0.0 0.0.0.0 4.4.4.4
ip route 180.7.2.220 255.255.255.255 180.7.254.125
ip route 180.7.253.0 255.255.255.0 Null0
ip route 180.7.254.0 255.255.255.0 Null0

I am trying to announce the 180.8.253.0 and 180.7.254.0 networks. The route statement for 180.7.2.220 is a route back inside for my internal FTP server to back up configs.

This is what the ISP sees on his side.

ISP-router#show ip bgp nei x.x.x.x rec
BGP table version is 1348900, local router ID is x.x.x.x
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
* 180.7.2.220/32 4.4.4.3 0 0 11111 ?

Total number of prefixes 1

Jon Marshall · ‎03-16-2010

srroeder wrote:

Sure ,

router#sho ip bgp 180.7.253.0
BGP routing table entry for 180.7.252.0/22, version 44913
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11111

66.196.17.1 from 66.196.17.1 (66.196.29.33)
Origin IGP, localpref 100, valid, external, best
hqprt02#sho ip bgp 180.7.254.0
BGP routing table entry for 180.7.252.0/22, version 44913
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11111

66.196.17.1 from 66.196.17.1 (66.196.29.33)
Origin IGP, localpref 100, valid, external, best

Okay, your BGP table is showing a route entry for 180.7.252.0 255.255.252 so do you know where you are getting this route from ? What is 66.196.17.1 ?

Sorry to keep asking for outputs but can you do

1) sh ip bgp | include 180.7.

2) sh ip bgp 180.7.253.0 255.255.255.0

3) sh ip route | include 180.7

4) sh ip route 180.7.253.0 255.255.255.0

Jon

View solution in original post

Jon Marshall · ‎03-16-2010

Can you post from your router -

1) sh ip bgp

2) sh ip bgp neighbor 4.4.4.4 advertised-routes

By the way, you shouldn't need the network statements as your redistribute static should cover those additional static routes.

Jon

srroeder · ‎03-16-2010

Thanks for the reply, when I do a "sho ip bgp" I get a list of 40000 some odd routes...... here are the first few lines......

hqprt02#sho ip bgp
BGP table version is 69053, local router ID is 180.7.254.126
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
r> 0.0.0.0          4.4.4.4                            0 10756 i
*> 1.0.0.0          4.4.4.4                            0 10756 1239 3356 365
61 i
*> 2.0.0.0/16       4.4.4.4                            0 10756 1239 6762 126
54 i
*> 3.0.0.0          4.4.4.4                           0 10756 1239 15412 93

hqprt02#sho ip bgp neig 4.4.4.4 advertised-routes
BGP table version is 69031, local router ID is 180.7.254.126
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 180.7.2.220/32 180.7.254.125 0 32768 ?

Total number of prefixes 1

Jon Marshall · ‎03-16-2010

Okay, sorry.

Can you do a "sh ip bgp" for the specific routes you have the null0 static routes for. I just want to make sure they are in the BGP table. Also can you do a "sh ip route" for the same routes to make sure they are in the routing table.

Jon

srroeder · ‎03-16-2010

Sure ,

router#sho ip bgp 180.7.253.0
BGP routing table entry for 180.7.252.0/22, version 44913
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11111

66.196.17.1 from 66.196.17.1 (66.196.29.33)
Origin IGP, localpref 100, valid, external, best
hqprt02#sho ip bgp 180.7.254.0
BGP routing table entry for 180.7.252.0/22, version 44913
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11111

66.196.17.1 from 66.196.17.1 (66.196.29.33)
Origin IGP, localpref 100, valid, external, best

Jon Marshall · ‎03-16-2010

srroeder wrote:

Sure ,

router#sho ip bgp 180.7.253.0
BGP routing table entry for 180.7.252.0/22, version 44913
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11111

66.196.17.1 from 66.196.17.1 (66.196.29.33)
Origin IGP, localpref 100, valid, external, best
hqprt02#sho ip bgp 180.7.254.0
BGP routing table entry for 180.7.252.0/22, version 44913
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
11111

66.196.17.1 from 66.196.17.1 (66.196.29.33)
Origin IGP, localpref 100, valid, external, best

Okay, your BGP table is showing a route entry for 180.7.252.0 255.255.252 so do you know where you are getting this route from ? What is 66.196.17.1 ?

Sorry to keep asking for outputs but can you do

1) sh ip bgp | include 180.7.

2) sh ip bgp 180.7.253.0 255.255.255.0

3) sh ip route | include 180.7

4) sh ip route 180.7.253.0 255.255.255.0

Jon

srroeder · ‎03-16-2010

Jon,

OK , I feel like a real dummy, the 66.196.17.1 is another ISP we have a connection to and he is announcing that CIDR back to me. I believe that is the cause of my problems. I will contact them.

Thanks for your help.

Steve