Re: troubleshooting bgp confederation, HELP!!

From: Eric Phillips (eric@phillips.tc)
Date: Fri Jan 18 2008 - 12:23:31 ARST


Uyota,

That post did not come across in any readable form. Can you try sending it
again? And what are you experiencing? Are peers not coming up, routes not
being propagated, or are routes being propagated, but just no connectivity?
Are all routes in the trasit path running BGP?

-Eric

On 1/16/08, uyota oyearone <spycharlies@hotmail.com> wrote:
>
> Hi Engineers;
>
> Am having problems pinging and tracing an advertised network via BGP
> Confederation. Here is the basic config. let me know if am missing
> something
> OR how i can troubleshooting this problem.
>
> ***
> [R3(as 65013)]s1/3-->s1/1[r2(as 65002)]s1/0-->frameRelay-->s1/0[r5(as
> 1)]--r3
> & R2 Directly connected, r2 & R5 thru. Frame Relay***
> --R3#
> interface Ethernet0/0 ip address 155.1.3.3 255.255.255.0!router ospf 1
> router-id 3.3.3.3 log-adjacency-changes network 155.1.23.3 0.0.0.0 area
> 0!router bgp 65013 no synchronization bgp log-neighbor-changes bgp
> confederation identifier 2 bgp confederation peers 65002 network 155.1.3.0
> mask 255.255.255.0 neighbor 155.1.23.2 remote-as 65002 no auto-summary
> --R2#
> interface Ethernet0/1 ip address 155.1.5.5 255.255.255.0!interfaceSerial1/0
> ip address 155.1.0.2 255.255.255.0 encapsulation frame-relay ip ospf
> network
> broadcast serial restart-delay 0 no dce-terminal-timing-enable frame-relay
> map
> ip 155.1.0.5 205 broadcast no frame-relay inverse-arp!router ospf 1
> router-id
> 2.2.2.2 log-adjacency-changes network 155.1.23.2 0.0.0.0 area 0!router bgp
> 65002 no synchronization bgp log-neighbor-changes bgp confederation
> identifier
> 2 bgp confederation peers 65013 network 155.1.2.0 mask 255.255.255.0neighbor
> 155.1.0.5 remote-as 1 neighbor 155.1.23.3 remote-as 65013 no
> auto-summary--R5#
> interface Ethernet0/1 ip address 155.1.5.5 255.255.255.0!interfaceSerial1/0
> ip address 155.1.0.5 255.255.255.0 encapsulation frame-relay ip ospf
> network
> broadcast serial restart-delay 0 no dce-terminal-timing-enable frame-relay
> map
> ip 155.1.0.2 502 broadcast no frame-relay inverse-arp!router bgp 1 no
> synchronization bgp log-neighbor-changes network 155.1.5.0 mask
> 255.255.255.0
> neighbor 155.1.0.2 remote-as 2 no auto-summary
> ===r5# sh ip bgp
> Network Next Hop Metric LocPrf Weight Path*>
> 155.1.2.0/24 155.1.0.2 0 0 2 i*>
> 155.1.3.0/24
> 155.1.0.2 0 2 i*> 155.1.5.0/24 0.0.0.0
> 0 32768 i
> r5#ping 155.1.0.2 (**frame connection workin fine)
> Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 155.1.0.2,
> timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip
> min/avg/max = 40/68/120 ms
> --r5#ping 155.1.2.2 so e0/1 (** directly connected adv. netw working fine)
> Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 155.1.2.2,
> timeout is 2 seconds:Packet sent with a source address of
> 155.1.5.5!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max =
> 32/64/92 ms
> --r5#ping 155.1.3.3 so e0/1
> Type escape sequence to abort.Sending 5, 100-byte ICMP Echos tPacket sent
> with
> a source addres.....Success rate is 0 percent (0/5)
>
> ***We would assume the problem is btw r2 & r3***
> R2#sh ip bgp
> Network Next Hop Metric LocPrf Weight Path*>
> 155.1.2.0/24 0.0.0.0 0 32768 i*> 155.1.3.0/24
> 155.1.23.3 0 100 0 (65013) i*> 155.1.5.0/24
> 155.1.0.5 0 0 1 i
> *> 155.1.5.0/24 155.1.0.5 0 0 1 i--r2#sh ip
> bgp
> su
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> State/PfxRcd155.1.0.5 4 1 84 86 5 0 0
> 01:19:10 1155.1.23.3 4
> 65013 84 84 5 0 0
> 01:18:34 2
>
> R2#ping 155.1.3.3 so fa0/0
> Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 155.1.3.3,
> timeout is 2 seconds:Packet sent with a source address of
> 155.1.2.2!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max =
> 24/52/84 ms
> *****R3#clea ip bgp 155.1.2.2Debug on R3******Mar 1 04:00:51.003:
> %BGP-5-ADJCHANGE: neighbor 155.1.23.2 Up*Mar 1 04:00:51.019: BGP(0):
> 155.1.23.2 send UPDATE (format) 155.1.3.0/24, next 155.1.23.3, metric 0,
> path
> Local*Mar 1 04:00:51.023: BGP(0): 155.1.23.2 NEXT_HOP part 1 net
> 155.1.4.0/24, next155.1.13.1*Mar 1 04:00:51.027: BGP(0): 155.1.23.2 send
> UPDATE (format) 155.1.4.0/24, next 155.1.13.1, metric 0, path 3*Mar 1
> 04:00:51.047: BGP(0): 155.1.23.2 rcvd UPDATE w/ attr: nexthop 155.1.23.2,
> origin i, localpref 100, metric 0, path (65002)*Mar 1 04:00:51.055:
> BGP(0):
> 155.1.23.2 rcvd 155.1.2.0/24*Mar 1 04:00:51.063: BGP(0): 155.1.23.2 rcvd
> UPDATE w/ attr: nexthop 155.1.0.5, origin i, localpref 100, metric 0, path
> (65002) 1*Mar 1 04:00:51.071: BGP(0): 155.1.23.2 rcvd 155.1.5.0/24
> ******This shows R3 received the network 155.1.5.0/24. **No access list,
> community etc. has been configured***
>
> What other troubleshooting step do i take to enable me know y I'm unable
> to
> ping of trace this network.
> Regards
>
>
>
>
>
>
>
>
>
>
> _________________________________________________________________
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>

-- 
Eric M. Phillips                               Senior Network Consultant

LTI Information Technology http://www.ltiit.com 501 Avis Drive Ann Arbor, MI 48108

Phone: (734) 929-1400 Fax: (734) 929-1401



This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:00 ARST