[zebra 23115] BGP routes can't publish!

View: New views
4 Messages — Rating Filter:   Alert me  

[zebra 23115] BGP routes can't publish!

by Charles Robinson-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

I’m in need of help as soon as possible.

 

Here’s the scenario:

 

I’m using BPG as just a route publisher traffic doesn’t actually filter through my Zebra box.

I have Time Warner as my ISP AS4323.  From the timewarner router traffic flows into my Cisco 515Pix firewall.

My Zebra box is behind my firewall in my DMZ. I have a NAT’d IP & port 179 port open for the Zebra box to allow routes to publish.

 

I’ve gotten the bgp session established with timewarner but I’m unable to get routes sent to them.

I’m not sure if I should be using multihop or if the problem is much deeper. So far I have not been able to get a next hop defined.

As you can see towards the bottom the next hop route is missing how can I get this working to publish routes?

 

 

 

Here are the details:

 

ZebraConf:

 

log file /usr/local/etc/zebra.log

!

interface lo

!

interface eth0

 ip address 192.168.173.105/24

 multicast

 ipv6 nd suppress-ra

!

ip route 0.0.0.0/0 192.168.173.3

!

!

line vty

!

end

 

 

BGPConfig:

 

Current configuration:

!

hostname Frodo-bgp

log file /usr/local/etc/bgp.log

!

router bgp [my AS #]

 neighbor [Timewarner router IP] remote-as 4323

!

 address-family ipv4

 redistribute static

 neighbor [Timewarner router IP]  activate

 neighbor [Timewarner router IP] distribute-list xx out

 network [ARIN Assigned IP subnet]/24

 exit-address-family

!

ip as-path access-list xx permit [ARIN Assigned IP subnet] 0.0.0.255

!

line vty

!

End

 

 

 

BGP Logs Incoming :

2008/02/15 12:04:36 BGP: 64.129.152.65 rcvd UPDATE w/ attr: nexthop 64.129.152.65, origin i, community 1273:12826 4323:51 4323:501 4323:1003 4323:20

01 4323:2503 4323:50000 65101:1003 65102:4 65103:1 65104:301, path 4323 1273 3741 33769

2008/02/15 12:04:36 BGP: 64.129.152.65 rcvd UPDATE about 196.13.220.0/24 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: 64.129.152.65 rcvd UPDATE w/ attr: nexthop 64.129.152.65, origin i, community 1273:12826 4323:51 4323:501 4323:1003 4323:20

01 4323:2503 4323:50000 65101:1003 65102:4 65103:1 65104:301, path 4323 1273 3741 36889

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE about 196.36.191.0/24 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE w/ attr: nexthop 64.129.152.65, origin ?, community 1273:12826 4323:51 4323:501 4323:1003 4323:20

01 4323:2503 4323:50000 65101:1003 65102:4 65103:1 65104:301, path 4323 1273 3741

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE about 196.3.114.0/24 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE about 196.3.115.0/24 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE about 196.3.113.0/24 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE about 196.10.224.0/24 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE about 163.195.128.0/17 -- DENIED due to: non-connected next-hop;

2008/02/15 12:04:37 BGP: [TW Router IP] rcvd UPDATE w/ attr: nexthop 64.129.152.65, origin i, community 1273:12826 4323:51 4323:501 4323:1003 4323:20

01 4323:2503 4323:50000 65101:1003 65102:4 65103:1 65104:301, path 4323 1273 3741

2008/02/15 12:04:40 BGP: [TW Router IP] rcvd UPDATE about 196.13.127.0/24 -- withdrawn

2008/02/15 12:04:40 BGP: [TW Router IP] Can't find the route 196.13.127.0/24

2008/02/15 12:04:40 BGP: [TW Router IP] rcvd UPDATE about 196.37.42.0/24 -- withdrawn

2008/02/15 12:04:40 BGP: [TW Router IP] Can't find the route 196.37.42.0/24

2008/02/15 12:04:40 BGP: [TW Router IP] rcvd UPDATE about 196.6.222.0/23 -- withdrawn

2008/02/15 12:04:40 BGP: [TW Router IP]Can't find the route 196.6.222.0/23

2008/02/15 12:04:40 BGP: [TW Router IP] rcvd UPDATE about 163.195.128.0/17 -- withdrawn

2008/02/15 12:04:40 BGP: [TW Router IP]Can't find the route 163.195.128.0/17

2008/02/15 12:04:40 BGP: [TW Router IP] rcvd UPDATE about 196.37.5.0/24 -- withdrawn

2008/02/15 12:04:40 BGP: [TW Router IP] Can't find the route 196.37.5.0/24

2008/02/15 12:04:40 BGP: [TW Router IP] rcvd UPDATE about 196.36.191.0/24 -- withdrawn

2008/02/15 12:04:40 BGP: [TW Router IP] Can't find the route 196.36.191.0/24

 

 

BGP Logs Outgoing:

2008/02/15 12:13:54 BGP: scanning IPv4 Unicast routing tables

2008/02/15 12:13:54 BGP: scanning IPv6 Unicast routing tables

2008/02/15 12:14:00 BGP: [TW Router IP] routeadv timer expired for IPv4 Unicast

2008/02/15 12:14:05 BGP: Import timer expired.

2008/02/15 12:14:20 BGP: Import timer expired.

2008/02/15 12:14:30 BGP: [TW Router IP] routeadv timer expired for IPv4 Unicast

2008/02/15 12:14:35 BGP: Import timer expired.

2008/02/15 12:14:50 BGP: Import timer expired.

2008/02/15 12:14:54 BGP: Performing BGP general scanning

2008/02/15 12:14:54 BGP: scanning IPv4 Unicast routing tables

2008/02/15 12:14:54 BGP: scanning IPv6 Unicast routing tables

2008/02/15 12:15:00 BGP: [TW Router IP] routeadv timer expired for IPv4 Unicast

 

 

 

# sh bg sum

No IPv6 neighbor is configured

 

 

# sh bg nei

BGP neighbor is [TW Router IP], remote AS 4323, local AS [MY AS #], external link

  BGP version 4, remote router ID 168.215.52.14

  BGP state = Established, up for 2d20h03m

  Last read 00:00:07, hold time is 90, keepalive interval is 30 seconds

  Neighbor capabilities:

    Route refresh: advertised and received(old & new)

    Address family IPv4 Unicast: advertised and received

  Message statistics:

    Inq depth is 0

    Outq depth is 0

                         Sent       Rcvd

    Opens:                  1          1

    Notifications:          0          0

    Updates:                0      31394

    Keepalives:          8166       8551

    Route Refresh:          0          0

    Capability:             0          0

    Total:               8167      39946

  Minimum time between advertisement runs is 30 seconds

 

 For address family: IPv4 Unicast

  Configuration flags 0x0

  Community attribute sent to this neighbor(both)

  Outbound path policy configured

  Outgoing update network filter list is xx

  0 accepted prefixes

 

  Connections established 1; dropped 0

  Last reset never

Local host: 192.168.173.105, Local port: 45371

Foreign host: [TW Router IP], Foreign port: 179

Nexthop: 192.168.173.105

Nexthop global: fe80::219:d1ff:fedf:9c6c

Nexthop local: ::

BGP connection: non shared network

Read thread: on  Write thread: off

 

 

 

# sh ip bgp [ARIN Assigned IP subnet]

BGP routing table entry for [ARIN Assigned IP subnet]/24

Paths: (1 available, best #1, table Default-IP-Routing-Table)

  Not advertised to any peer

  Local

    0.0.0.0 from 0.0.0.0 (192.168.173.105)

      Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced, local, best

      Last update: Tue Feb 12 16:19:14 2008

 

# sh ip bgp att

attr[1] nexthop 0.0.0.0

 

# sh ip bgp community-info

Address Refcnt Community

#

 

 

# sh ip bgp ip mu

No BGP network exists

 

# sh ip bgp

BGP table version is 0, local router ID is 192.168.173.105

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

*> [ARIN Assigned IP subnet]    0.0.0.0                  0         32768 i

 

Total number of prefixes 1

 

 

# sh ip bgp pa

Address Refcnt Path

[0x8224758:0] (1)

 

 

#sh ip bgp scan

BGP scan is running

BGP scan interval is 60

Current BGP nexthop cache:

BGP connected route:

 192.168.173.0/24

 

 

# sh ip bgp sum

BGP router identifier 192.168.173.105, local AS number [my AS #]

1 BGP AS-PATH entries

0 BGP community entries

 

Neighbor              V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd

[TW Router IP]   4  4323   40235    8204        0    0    0 2d20h22m        0

 

Total number of neighbors 1

 

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.


_______________________________________________
Zebra mailing list
Zebra@...
http://ml.zebra.org/mailman/listinfo/zebra

[zebra 23116] Re: BGP routes can't publish!

by Arnold Nipper :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 15.02.2008 22:07 Charles Robinson wrote

> I’m not sure if I should be using multihop

Did you try to set multihop? If not, please do. If so, what was the result?




Arnold
--
Arnold Nipper / nIPper consulting, Sandhausen, Germany
email: arnold@...       phone: +49 6224 9259 299
mobile: +49 172 2650958         fax: +49 6224 9259 333



_______________________________________________
Zebra mailing list
Zebra@...
http://ml.zebra.org/mailman/listinfo/zebra

signature.asc (194 bytes) Download Attachment

[zebra 23117] Re: BGP routes can't publish!

by Charles Robinson-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Damn I thought I tried multi in my config already.

Looks much different now.

Sh ip bgp pa:

[0x865cfd8:137274] (142) 4323 1273 4651 4621
[0x8683828:104508] (1) 4323 10931
[0x827f6b0:71753] (2) 4323 14131
[0x8601880:530494] (7) 4323 1257 8437 8926 8926 8926 8926 8926 15836
8474
[0x8519770:202824] (3) 4323 1273 4651 4621 3839
[0x8248fb0:71756] (4) 4323 5400 9498
[0x8294ec8:71757] (1) 4323 15155
[0x86dbcc8:104530] (1) 4323 16563
[0x82e37d0:71764] (1) 4323 16947
[0x8279438:104531] (1) 4323 16819
[0x828ca30:104540] (1) 4323 19123
[0x8703b10:170089] (2) 4323 1273 21433
[0x83bff78:432228] (1) 4323 1273 1273 1273 1273 5588 3340 8425
[0x8551160:137328] (2) 4323 3300 21070
[0x8486bd0:235632] (1) 4323 5400 5400 5400 12883 12294 12294 12294 12294
12294 21488 43774
[0x849dbc0:170100] (2) 4323 13237 34088 43731


sh ip bgp scan:

BGP scan is running
BGP scan interval is 60
Current BGP nexthop cache:
 [TW Router IP] valid [IGP metric 0]
BGP connected route:
 192.168.173.0/24

Sh ip bgp:

*> 204.134.104.0/21 [TW Router IP]                          0 4323 2901
2901 2901 2901 2901 i
*> 204.134.112.0/20 [TW Router IP]                          0 4323 2901
2901 2901 2901 2901 i
*> 204.134.128.0    [TW Router IP]                         0 4323 293
10702 i
*> 204.134.129.0    [TW Router IP]                         0 4323 293
292 i
*> 204.134.131.0    [TW Router IP]                         0 4323 293
10702 i
*> 204.134.132.0    [TW Router IP]                         0 4323 293
10702 i
*> 204.134.133.0    [TW Router IP]                         0 4323 293
10702 i
*> 204.134.135.0    [TW Router IP]                         0 4323 293
10702 i
*> 204.134.136.0    [TW Router IP]                         0 4323 293
10702 i




I'm now getting the routes ok
But the main sending route problem exists, TW doesn't see anything
coming from me at all.
They see the keepalives but nothing else?
And I need the route to go from TW to my firewall not my actual Zebra
router? Is that possible.


Sorry for the simple questions (I promise to order a bgp book tomorrow)



-----Original Message-----
From: Arnold Nipper [mailto:arnold@...]
Sent: Friday, February 15, 2008 6:48 PM
To: Charles Robinson
Cc: 'zebra@...'
Subject: Re: [zebra 23115] BGP routes can't publish!

On 15.02.2008 22:07 Charles Robinson wrote

> I'm not sure if I should be using multihop

Did you try to set multihop? If not, please do. If so, what was the
result?




Arnold
--
Arnold Nipper / nIPper consulting, Sandhausen, Germany
email: arnold@...       phone: +49 6224 9259 299
mobile: +49 172 2650958         fax: +49 6224 9259 333


This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.



_______________________________________________
Zebra mailing list
Zebra@...
http://ml.zebra.org/mailman/listinfo/zebra

[zebra 23118] Re: BGP routes can't publish!

by Arnold Nipper :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 18.02.2008 21:47 Charles Robinson wrote


> I'm now getting the routes ok But the main sending route problem
> exists, TW doesn't see anything coming from me at all.

What does

  show ip bgp neigh [TW Router IP] advertised-routes

give you?

> And I need the route to go from TW to my firewall not my actual Zebra
>  router? Is that possible.
>

What kind of fw do you have? Is the fw able to talk any routing
protocol? Depending on your set-up you might also be able to use the
next-hop feature.


> Sorry for the simple questions (I promise to order a bgp book
> tomorrow)

Have a look at Cisco first (www.cisco.com). They have a lot of excellent
documentation.



Arnold
--
Arnold Nipper / nIPper consulting, Sandhausen, Germany
email: arnold@...       phone: +49 6224 9259 299
mobile: +49 172 2650958         fax: +49 6224 9259 333



_______________________________________________
Zebra mailing list
Zebra@...
http://ml.zebra.org/mailman/listinfo/zebra

signature.asc (194 bytes) Download Attachment
LightInTheBox - Buy quality products at wholesale price!