From: Kaushikkumar Randeriya (kranderiya@googlemail.com)
Date: Sun Feb 08 2009 - 13:28:11 ARST
Hi,
Your R6 is in confederation and confed id is 3. Mean your global AS 3.
R1 is not part of your confed. You have to peer with AS3 on R1 or you
can put your R1 in confed. Depends on you what you want to do.
Regards,
Kaushik
On Sun, Feb 8, 2009 at 1:49 PM, Sidda6 <sidda6@gmail.com> wrote:
> Hi GS,
>
> I have topology like as shown below
>
> R6#
> router bgp 6
> no synchronization
> bgp router-id 3.3.6.6
> bgp log-neighbor-changes
> bgp confederation identifier 3
> bgp confederation peers 2
> neighbor 3.3.2.2 remote-as 2
> neighbor 3.3.2.2 ebgp-multihop 4
> neighbor 3.3.2.2 update-source Loopback0
> neighbor 111.111.111.111 remote-as 11
> no auto-summary
>
> R1#
> router bgp 11
> no synchronization
> bgp router-id 11.11.11.11
> bgp log-neighbor-changes
> neighbor 111.111.111.116 remote-as 6
> no auto-summary
>
> I am just trying to establish peering between R6 and R1. It is poping
> up error from both R1 and R6 as " %BGP-3-NOTIFICATION: sent to
> neighbor x.x.x.x (peer in wrong AS) 2 bytes".
>
> What is wrong with my config.? Is there anything thing should I add to
> establish perfect peering between these. Kindly advise.
>
> Regards,
> Sidda
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:10 ARST