| Home | Register | Members | Search | Links |
![]() |
| Thread Tools | Display Modes |
|
Andy M
Guest
Posts: n/a
|
Hello - I'm new to BGP, however I know the basics of what it does. I
am playing with it using Zebra (actually Quagga packaged with Fedora Core 2) to learn more about it, and I want to do a certain type of setup. See a picture of my target topology here: http://www.geocities.com/drsmartz/BG...t_Color_v2.gif I will have two AS's, with three links between the two AS's using eBGP: this is a total of 6 border routers. One AS runs OSPF and the other iBGP as their IGP. My goal isn't to make a mini ISP or anything connected to the internet. I just want to make a contained experiment where the route tables are shared between the zebra routers. I have the OSPF working, however the BGP is proving difficult. I am currently setting the BGP neighbors as follows: Zebra1 is neighbor to 2 & 4 & 3 Zebra2 is neighbor to 1 & 3 & 5 Zebra3 is neighbor to 1 & 2 & 6 Zebra4 is neighbor to 1 Zebra5 is neighbor to 2 Zebra6 is neighbor to 3 On Zebra 1-3, I set the eBGP links to be remote-as 20, and the iBGP links to be remote-as 10 On Zebra 4-6, I set the respective eBGP link to be remote-as 10 I am including the bgp and zebra config files along with bgp log files at the very bottom of the post. Zebra 1-3 have default gateways set to a proxy on my LAN to the internet, which I don't have control over. Problems with the setup: With all routers up and all BGP links established, and OSPF is converged, I can ping from Zebra3 to Zebra6 or to Zebra10. I cannot ping from Zebra2 to Zebra6 or to Zebra10. When I traceroute, or look at the Zebra2 routing table, I see that the 10.0.60.0/24 network next hop is to the Zebra2 default gateway, not to Zebra3. Next hop should be Zebra 3! I have a feeling the bgp configuration in the routers that I have is not right, however I can't find any tutorials to clue me in on the right config. Any suggestions? I have checked all subnets to be sure my wiring and eth configurations are operating correctly. Please notice in the log files that there are many entries where "origin ?" -- Is the "?" for origin a problem? I have read that a question mark for origin might indicate an incomplete/incompatible LSA. How should I change my *.conf files? Thanks in advance!! Andy Configs and Logs: Zebra 1 BGPD.conf: ! Zebra configuration saved from vty ! 2004/09/17 14:43:37 ! hostname ZebraBGP1 password zebra enable password zebra ! router bgp 10 network 0.0.0.0/0 redistribute kernel redistribute connected neighbor 10.0.5.2 remote-as 10 neighbor 10.0.5.3 remote-as 10 neighbor 10.0.5.100 remote-as 10 neighbor 192.168.0.2 remote-as 20 ! line vty ! ----- END BGPD.conf Zebra1 Zebra.conf: ! Zebra configuration saved from vty ! 2004/08/05 15:22:27 ! hostname Router1 password zebra enable password zebra service advanced-vty ! interface eth0 description Boeing Intranet Interface ip address 10.0.5.1/24 ! interface eth1 description BGP IFace ip address 192.168.0.1/24 ! interface lo ! !interface sit0 ! ip route 0.0.0.0/0 141.102.36.1 ip route 10.0.5.0/24 eth0 ip route 192.168.0.0/24 eth1 ! no ipv6 forwarding ! line vty ! ------- end ZEBRA.CONF Zebra 3 bgpd.conf: ! Zebra configuration saved from vty ! 2004/08/05 08:48:16 ! hostname ZebraBGP3 password zebra enable password zebra ! debug bgp events debug bgp updates ! router bgp 10 network 0.0.0.0/0 redistribute kernel redistribute connected neighbor 10.0.5.1 remote-as 10 neighbor 10.0.5.2 remote-as 10 neighbor 10.0.5.100 remote-as 10 neighbor 192.168.2.2 remote-as 20 ! line vty ! log file /etc/quagga/_bgpd.log ------- END BGPD.conf on Zebra3 Zebra 3 zebra.conf file: ! Zebra configuration saved from vty ! 2004/08/05 15:22:27 ! hostname Router3 password zebra enable password zebra service advanced-vty ! interface eth0 description Boeing Intranet Interface ip address 10.0.5.3/22 ! interface eth1 description BGP IFace ip address 192.168.2.1/24 ! interface lo ! interface sit0 ! ip route 0.0.0.0/0 141.102.36.1 ip route 10.0.5.0/22 eth0 ip route 192.168.2.0/24 eth1 ! no ipv6 forwarding ! line vty ! ----- END zebra.conf on ZEBRA3 Zebra 6 bgpd.conf file: ! Zebra configuration saved from vty ! 2004/08/05 08:48:16 ! hostname ZebraBGP4 password zebra enable password zebra ! router bgp 20 network 0.0.0.0/0 redistribute kernel redistribute connected redistribute ospf neighbor 192.168.0.1 remote-as 10 ! route-map set permit 10 set local-preference 5 ! line vty ! ------ END bgpd.conf for ZEBRA6 zebra6 zebra.conf file: ! Zebra configuration saved from vty ! 2004/08/05 15:22:27 ! hostname Router4 password zebra enable password zebra service advanced-vty ! interface eth0 description BGP Iface ! interface eth1 description Vlan 40 IFace ! interface lo ! !interface sit0 ! ip route 0.0.0.0/0 192.168.0.1 ip route 192.168.0.0/24 eth0 ip route 10.0.40.0/24 eth1 ip route 10.0.10.0/24 eth2 ! no ipv6 forwarding ! line vty ! ------- END Zebra.conf on Zebra6 Zebra 3 BGP LOG FILE START: 2004/09/17 14:30:53 BGP: [Event] BGP connection from host 192.168.2.2 2004/09/17 14:30:53 BGP: [Event] BGP connection IP address 192.168.2.2 is Idle state 2004/09/17 14:30:54 BGP: 192.168.2.2 [Event] Connect start to 192.168.2.2 fd 11 2004/09/17 14:30:54 BGP: 192.168.2.2 [Event] BGP connection closed fd 11 2004/09/17 14:30:57 BGP: [Event] BGP connection from host 192.168.2.2 2004/09/17 14:30:57 BGP: [Event] Make dummy peer structure until read Open packet 2004/09/17 14:30:57 BGP: 192.168.2.2 [Event] Transfer temporary BGP peer to existing one 2004/09/17 14:30:57 BGP: 192.168.2.2 [Event] Accepting BGP peer delete 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin i, path 20 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 0.0.0.0/0 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin ?, path 20 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 10.0.10.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 192.168.2.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 169.254.0.0/16 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 10.0.60.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 send UPDATE 0.0.0.0/0 2004/09/17 14:30:58 BGP: 192.168.2.2 send UPDATE 141.102.36.0/22 2004/09/17 14:30:58 BGP: 192.168.2.2 send UPDATE 192.168.2.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 send UPDATE 169.254.0.0/16 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin ?, metric 20, path 20 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 10.0.40.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 192.168.1.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 192.168.0.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 10.0.100.0/24 2004/09/17 14:30:58 BGP: 192.168.2.2 rcvd 10.0.50.0/24 2004/09/17 14:32:37 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 14:32:37 BGP: 192.168.2.2 rcvd UPDATE about 10.0.50.0/24 -- withdrawn 2004/09/17 14:32:37 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 14:32:37 BGP: 192.168.2.2 rcvd UPDATE about 192.168.1.0/24 -- withdrawn 2004/09/17 14:32:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin ?, metric 20, path 20 2004/09/17 14:32:58 BGP: 192.168.2.2 rcvd 10.0.50.0/24 2004/09/17 14:32:58 BGP: 192.168.2.2 rcvd 192.168.1.0/24 2004/09/17 14:33:02 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 14:33:02 BGP: 192.168.2.2 rcvd UPDATE about 10.0.40.0/24 -- withdrawn 2004/09/17 14:33:02 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 14:33:02 BGP: 192.168.2.2 rcvd UPDATE about 192.168.0.0/24 -- withdrawn 2004/09/17 14:33:28 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin ?, metric 20, path 20 2004/09/17 14:33:28 BGP: 192.168.2.2 rcvd 10.0.40.0/24 2004/09/17 14:33:28 BGP: 192.168.2.2 rcvd 192.168.0.0/24 2004/09/17 14:34:33 BGP: [Event] BGP connection from host 141.102.36.29 2004/09/17 14:34:33 BGP: [Event] BGP connection IP address 141.102.36.29 is not configured 2004/09/17 14:34:39 BGP: [Event] BGP connection from host 141.102.36.29 2004/09/17 14:34:39 BGP: [Event] BGP connection IP address 141.102.36.29 is not configured 2004/09/17 14:34:39 BGP: [Event] BGP connection from host 141.102.36.228 2004/09/17 14:34:39 BGP: [Event] BGP connection IP address 141.102.36.228 is not configured 2004/09/17 14:34:46 BGP: [Event] BGP connection from host 141.102.36.29 2004/09/17 14:34:46 BGP: [Event] BGP connection IP address 141.102.36.29 is not configured 2004/09/17 14:34:47 BGP: [Event] BGP connection from host 141.102.36.228 2004/09/17 14:34:47 BGP: [Event] BGP connection IP address 141.102.36.228 is not configured 2004/09/17 14:34:49 BGP: Terminating on signal 2004/09/17 14:34:49 BGP: BGPd 0.96.4 starting: vty@2605, bgp@179 2004/09/17 14:34:51 BGP: [Event] BGP connection from host 141.102.36.228 2004/09/17 14:34:51 BGP: [Event] BGP connection IP address 141.102.36.228 is Idle state 2004/09/17 14:34:52 BGP: [Event] BGP connection from host 141.102.36.29 2004/09/17 14:34:52 BGP: [Event] BGP connection IP address 141.102.36.29 is Idle state 2004/09/17 14:34:53 BGP: [Event] BGP connection from host 192.168.2.2 2004/09/17 14:34:53 BGP: [Event] BGP connection IP address 192.168.2.2 is Idle state 2004/09/17 14:34:53 BGP: 141.102.36.228 [Event] Connect start to 141.102.36.228 fd 11 2004/09/17 14:34:53 BGP: 192.168.2.2 [Event] Connect start to 192.168.2.2 fd 12 2004/09/17 14:34:53 BGP: 141.102.36.228 [Event] BGP connection closed fd 11 2004/09/17 14:34:53 BGP: 192.168.2.2 [Event] BGP connection closed fd 12 2004/09/17 14:34:54 BGP: 141.102.36.29 [Event] Connect start to 141.102.36.29 fd 11 2004/09/17 14:34:54 BGP: 141.102.36.29 [Event] BGP connection closed fd 11 2004/09/17 14:34:56 BGP: [Event] BGP connection from host 141.102.36.29 2004/09/17 14:34:56 BGP: [Event] Make dummy peer structure until read Open packet 2004/09/17 14:34:56 BGP: 141.102.36.29 [Event] Transfer temporary BGP peer to existing one 2004/09/17 14:34:56 BGP: 141.102.36.29 [Event] Accepting BGP peer delete 2004/09/17 14:34:57 BGP: 141.102.36.29 send UPDATE 0.0.0.0/0 2004/09/17 14:34:57 BGP: 141.102.36.29 send UPDATE 141.102.36.0/22 2004/09/17 14:34:57 BGP: 141.102.36.29 send UPDATE 192.168.2.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 send UPDATE 169.254.0.0/16 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE w/ attr: nexthop 141.102.36.29, origin i, localpref 100, path 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 0.0.0.0/0 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE w/ attr: nexthop 192.168.0.2, origin ?, localpref 100, path 20 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 10.0.10.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 10.0.40.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE w/ attr: nexthop 192.168.0.2, origin ?, localpref 100, metric 20, path 20 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 10.0.60.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 192.168.2.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE w/ attr: nexthop 192.168.0.2, origin ?, localpref 100, metric 30, path 20 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 10.0.100.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE w/ attr: nexthop 141.102.36.29, origin ?, localpref 100, path 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 141.102.36.0/22 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 192.168.0.0/24 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd 169.254.0.0/16 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i, localpref 0 2004/09/17 14:34:57 BGP: 141.102.36.29 rcvd UPDATE about 192.168.2.0/24 -- withdrawn 2004/09/17 14:34:57 BGP: [Event] BGP connection from host 141.102.36.228 2004/09/17 14:34:57 BGP: [Event] Make dummy peer structure until read Open packet 2004/09/17 14:34:57 BGP: 141.102.36.228 [Event] Transfer temporary BGP peer to existing one 2004/09/17 14:34:57 BGP: 141.102.36.228 [Event] Accepting BGP peer delete 2004/09/17 14:34:58 BGP: [Event] BGP connection from host 192.168.2.2 2004/09/17 14:34:58 BGP: [Event] Make dummy peer structure until read Open packet 2004/09/17 14:34:58 BGP: 192.168.2.2 [Event] Transfer temporary BGP peer to existing one 2004/09/17 14:34:58 BGP: 192.168.2.2 [Event] Accepting BGP peer delete 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin i, path 20 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 0.0.0.0/0 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin ?, path 20 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 10.0.10.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 192.168.2.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 169.254.0.0/16 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 10.0.60.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd UPDATE w/ attr: nexthop 192.168.2.2, origin ?, metric 20, path 20 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 10.0.40.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 192.168.1.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 192.168.0.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 10.0.100.0/24 2004/09/17 14:34:58 BGP: 192.168.2.2 rcvd 10.0.50.0/24 ---------------------------- END ZEBRA 3 BGP log Zebra 6 BGP LOG FILE: 2004/09/17 16:54:56 BGP: 192.168.2.1 [Event] Connect start to 192.168.2.1 fd 11 2004/09/17 16:54:56 BGP: 192.168.2.1 [Error] bgp_read_packet error: Connection reset by peer 2004/09/17 16:54:57 BGP: [Event] BGP connection from host 192.168.2.1 2004/09/17 16:54:57 BGP: [Event] BGP connection IP address 192.168.2.1 is Idle state 2004/09/17 16:55:00 BGP: 192.168.2.1 [Event] Connect start to 192.168.2.1 fd 11 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 0.0.0.0/0 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 10.0.10.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 192.168.2.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 169.254.0.0/16 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 10.0.60.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 10.0.40.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 192.168.1.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 192.168.0.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 10.0.100.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 send UPDATE 10.0.50.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin i, path 10 2004/09/17 16:55:01 BGP: 192.168.2.1 rcvd 0.0.0.0/0 2004/09/17 16:55:01 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin ?, path 10 2004/09/17 16:55:01 BGP: 192.168.2.1 rcvd 141.102.36.0/22 2004/09/17 16:55:01 BGP: 192.168.2.1 rcvd 192.168.2.0/24 2004/09/17 16:55:01 BGP: 192.168.2.1 rcvd 169.254.0.0/16 2004/09/17 16:56:40 BGP: 192.168.2.1 send UPDATE 10.0.50.0/24 -- unreachable 2004/09/17 16:56:40 BGP: 192.168.2.1 send UPDATE 192.168.1.0/24 -- unreachable 2004/09/17 16:57:01 BGP: 192.168.2.1 send UPDATE 10.0.50.0/24 2004/09/17 16:57:01 BGP: 192.168.2.1 send UPDATE 192.168.1.0/24 2004/09/17 16:57:05 BGP: 192.168.2.1 send UPDATE 10.0.40.0/24 -- unreachable 2004/09/17 16:57:05 BGP: 192.168.2.1 send UPDATE 192.168.0.0/24 -- unreachable 2004/09/17 16:57:31 BGP: 192.168.2.1 send UPDATE 10.0.40.0/24 2004/09/17 16:57:31 BGP: 192.168.2.1 send UPDATE 192.168.0.0/24 2004/09/17 16:58:52 BGP: 192.168.2.1 [Event] BGP connection closed fd 11 2004/09/17 16:58:56 BGP: 192.168.2.1 [Event] Connect start to 192.168.2.1 fd 11 2004/09/17 16:58:56 BGP: 192.168.2.1 [Error] bgp_read_packet error: Connection reset by peer 2004/09/17 16:58:57 BGP: [Event] BGP connection from host 192.168.2.1 2004/09/17 16:58:57 BGP: [Event] BGP connection IP address 192.168.2.1 is Idle state 2004/09/17 16:59:01 BGP: 192.168.2.1 [Event] Connect start to 192.168.2.1 fd 11 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 0.0.0.0/0 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 10.0.10.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 192.168.2.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 169.254.0.0/16 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 10.0.60.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 10.0.40.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 192.168.1.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 192.168.0.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 10.0.100.0/24 2004/09/17 16:59:01 BGP: 192.168.2.1 send UPDATE 10.0.50.0/24 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin i, path 10 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd 0.0.0.0/0 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin ?, path 10 20 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd UPDATE about 10.0.40.0/24 -- DENIED due to: as-path contains our own AS; 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd UPDATE about 10.0.50.0/24 -- DENIED due to: as-path contains our own AS; 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin ?, path 10 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd 141.102.36.0/22 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd 192.168.2.0/24 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd 169.254.0.0/16 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin ?, path 10 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd 192.168.0.0/24 2004/09/17 16:59:02 BGP: 192.168.2.1 rcvd 192.168.1.0/24 2004/09/17 17:08:23 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 17:08:23 BGP: 192.168.2.1 rcvd UPDATE about 10.0.40.0/24 -- withdrawn 2004/09/17 17:08:23 BGP: 192.168.2.1 Can't find the route 10.0.40.0/24 2004/09/17 17:08:23 BGP: 192.168.2.1 rcvd UPDATE about 192.168.0.0/24 -- withdrawn 2004/09/17 17:08:29 BGP: 192.168.2.1 send UPDATE 10.0.40.0/24 -- unreachable 2004/09/17 17:08:29 BGP: 192.168.2.1 send UPDATE 192.168.0.0/24 -- unreachable 2004/09/17 17:08:32 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin ?, path 10 2004/09/17 17:08:32 BGP: 192.168.2.1 rcvd 192.168.0.0/24 2004/09/17 17:09:02 BGP: 192.168.2.1 send UPDATE 10.0.40.0/24 2004/09/17 17:09:02 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 192.168.2.1, origin ?, path 10 20 2004/09/17 17:09:02 BGP: 192.168.2.1 rcvd UPDATE about 10.0.40.0/24 -- DENIED due to: as-path contains our own AS; 2004/09/17 17:30:00 BGP: 192.168.2.1 send UPDATE 10.0.50.0/24 -- unreachable 2004/09/17 17:30:00 BGP: 192.168.2.1 send UPDATE 192.168.1.0/24 -- unreachable 2004/09/17 17:30:32 BGP: 192.168.2.1 send UPDATE 10.0.50.0/24 2004/09/17 17:48:29 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 17:48:29 BGP: 192.168.2.1 rcvd UPDATE about 10.0.40.0/24 -- withdrawn 2004/09/17 17:48:29 BGP: 192.168.2.1 Can't find the route 10.0.40.0/24 2004/09/17 17:48:29 BGP: 192.168.2.1 rcvd UPDATE about 192.168.0.0/24 -- withdrawn 2004/09/17 17:48:32 BGP: 192.168.2.1 send UPDATE 192.168.0.0/24 2004/09/17 17:50:01 BGP: 192.168.2.1 rcvd UPDATE w/ attr: nexthop 0.0.0.0, origin i 2004/09/17 17:50:01 BGP: 192.168.2.1 rcvd UPDATE about 10.0.50.0/24 -- withdrawn 2004/09/17 17:50:01 BGP: 192.168.2.1 Can't find the route 10.0.50.0/24 2004/09/17 17:50:01 BGP: 192.168.2.1 rcvd UPDATE about 192.168.1.0/24 -- withdrawn 2004/09/17 17:50:02 BGP: 192.168.2.1 send UPDATE 192.168.1.0/24 2004/09/17 17:52:41 BGP: 192.168.2.1 [Event] BGP connection closed fd 11 2004/09/17 17:52:45 BGP: 192.168.2.1 [Event] Connect start to 192.168.2.1 fd 11 2004/09/17 17:52:45 BGP: 192.168.2.1 [Error] bgp_read_packet error: Connection reset by peer -------------- END of Zebra6 bgp log file. |
|
|
|
|
|||
|
|||
|
|
|
| |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| VPN setup Troubleshooting | Cali Tech | Windows Networking | 6 | 07-10-2007 02:52 PM |
| NAT troubleshooting | Alex Smirnoff | Windows Networking | 13 | 08-19-2006 08:48 AM |
| NAT - TROUBLESHOOTING | MICROSOFT | Windows Networking | 3 | 04-16-2005 09:19 AM |
| Need Help Troubleshooting | polar_bear | Windows Networking | 2 | 05-21-2004 11:23 PM |
| troubleshooting WRT54g | Tom Rogie | Wireless Internet | 0 | 04-08-2004 04:23 PM |
Forum Software Powered by vBulletin®, Copyright Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc. |



Linear Mode

