From: Shahid Ansari (shahid1357@gmail.com)
Date: Fri Oct 24 2008 - 15:44:08 ARST
When you configure neighbor with wrong AS, you will receive the message
informing you of the remotely configured ASN.
In your example:
<< Error >>
*Mar 1 08:37:53.965: %BGP-3-NOTIFICATION: sent to neighbor 150.1.2.1 2/24
(peer in wrong AS) 2 bytes 0004
--More-- FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 0004 00B4 0606
0606 1002 0601 0400 0100 0102 0280 0002 0202 00
Look at the end. Hex number "0004" is *remotely configured ASN*. You
just change your configuration to peer with AS 4 and you're done.
Please correct me If I am wrong .
On Fri, Oct 24, 2008 at 8:38 PM, Scott M Vermillion <
scott_ccie_list@it-ag.com> wrote:
> >looks like ebgp-multihop is missing on BB1 also.
>
> I think all of that stuff related to IP 2.2.2.2 is a confederation peer
> elsewhere in the topology - not BB1. The last three lines of config got
> concatenated into a single line in the original e-mail, so you probably
> didn't see on R6:
>
>
>
> neighbor 150.1.2.254 remote-as 254
>
>
>
> That's the subnet of the segment between R6 & BB1, so multi-hop shouldn't
> be
> required.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Regards,Shahid Ansari Saudi Arabia(Riyadh)
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:22 ARST