From: ISolveSystems (support@isolvesystems.com)
Date: Wed Sep 05 2007 - 13:40:27 ART
Yup. IEWB lab 16. I think what you have described is a fixed. I also used
the update source lo0, on top of the ebgp-multihop.
On 9/5/07, Alex Steer <alex.steer@eison.co.uk> wrote:
>
> Funny you are asking this question. I had this exact problem about 5
> minutes ago and was going to ask how to solve it. Lab16 by any chance?
> Trace from r3 to r5 or look at r3 routing table. You will probably see
> it using r4 as a next hop.
>
> On one of the OSPF questions it asked you to prefer r4 due to it having
> a high bw link. I did this with the ospf neigh cost command, the cause
> of the problem I guess. To work around this (2 minute fix as I lazy) I
> just configured the ebgp-multihop command on r3 for r5 so that traffic
> can route through R4
>
> Any body know how to produce a real fix for this?
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> ISolveSystems
> Sent: 04 September 2007 17:06
> To: Cisco certification
> Subject: BGP neighbor not neighbor up
>
> R3 connects to R4 and R5 via FR. R3 is the hub.
>
> For some reason, R3 and R5 does not form BGP neighbor relationship. The
> show ip bgp sum status shows OpenSent on one side and OpenConfirm on
> another
> side. Any suggestion?
>
>
>
> Rack1R3(config-router)#
> *Sep 4 16:34:02.907: %BGP-3-NOTIFICATION: sent to neighbor 154.1.0.5
> 4/0
> (hold time expired) 0 bytes
>
> Rack1R5(config-router)#
> *Sep 4 16:39:16.031: %BGP-3-NOTIFICATION: sent to neighbor 154.1.0.3
> 4/0
> (hold time expired) 0 bytes
>
>
>
>
> R3
> interface Serial0/0/0
> ip address 154.1.0.3 255.255.255.0
> encapsulation frame-relay IETF
> ip ospf network point-to-multipoint non-broadcast
> frame-relay map ip 154.1.0.4 304
> frame-relay map ip 154.1.0.5 305
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> end
>
> Rack1R3(config-router)#do sh run | sec bgp
> router bgp 300
> no synchronization
> bgp log-neighbor-changes
> neighbor 154.1.0.4 remote-as 400
> neighbor 154.1.0.4 send-community
> neighbor 154.1.0.5 remote-as 400
> neighbor 154.1.0.5 send-community
> neighbor 154.1.13.1 remote-as 200
> neighbor 154.1.13.1 send-community
> neighbor 154.1.23.2 remote-as 200
> neighbor 154.1.23.2 send-community
> neighbor 154.1.38.8 remote-as 300
> neighbor 154.1.38.8 send-community
> no auto-summary
>
>
> R5
> interface Serial0/0/0
> ip address 154.1.0.5 255.255.255.0
> encapsulation frame-relay IETF
> ip ospf network point-to-multipoint non-broadcast
> ip ospf priority 0
> frame-relay map ip 154.1.0.3 503
> frame-relay map ip 154.1.0.4 503
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> end
>
> Rack1R5#sh run | sec bgp
> router bgp 400
> no synchronization
> bgp log-neighbor-changes
> neighbor 154.1.0.3 remote-as 300
> neighbor 154.1.0.3 send-community
> neighbor 154.1.45.4 remote-as 400
> neighbor 154.1.45.4 send-community
> no auto-summary
> Rack1R5#
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:09 ART