From: Wouter Prins (wp@null0.nl)
Date: Sun Feb 08 2009 - 11:56:46 ARST
You need to configure AS 3 for neighbor 111.111.111.116 on R1, because R1 is
not part of your confederation.
2009/2/8 Sidda6 <sidda6@gmail.com>
> 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