From: Digital Yemeni (digital-yemeni@hotmail.com)
Date: Sat Feb 24 2007 - 19:48:44 ART
Good try! BUT, as stated earlier, that does not show the "actual" AS# that
was configured which we are interested to know! ;-)
Best Regards,
Digital
------------------------------------------------------------------------------------------------------------------
***********************************************************************************
*.* You'll NEVER succeed as a "CCIE" until you LOVE Cisco MORE than your
sleep! *.*
***********************************************************************************
I'm expected to be busy for the next 57 years + CCIE preparation adds on
that a bit. Therefore, please be concise on your email. Thank you!
>From: "Edison Ortiz" <edisonmortiz@gmail.com>
>Reply-To: "Edison Ortiz" <edisonmortiz@gmail.com>
>To: "Digital Yemeni" <digital-yemeni@hotmail.com>, <ccielab@groupstudy.com>
>Subject: Re: BGP AS-No.
>Date: Sat, 24 Feb 2007 10:29:37 -0500
>
>conf t
>Enter configuration commands, one per line. End with CNTL/Z.
>R2(config)#router bgp 100
>R2(config-router)#neighbor 183.1.254.1 remote-as 200
>
>conf t
>Enter configuration commands, one per line. End with CNTL/Z.
>R1(config)#router bgp 200
>R1(config-router)#neigh 183.1.254.2 remote-as 500
>
>On R2
>
>%BGP-3-NOTIFICATION: sent to neighbor 183.1.254.2 2/2 (peer in wrong AS) 2
>bytes 0064 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 0064 00B4 9601
>0202 1002 0601 0400 0100 0102 0280 0002 0202 00
>
>Above message says "(peer in wrong AS) 2 bytes 0064"
>
>0064 is a hex value corresponding to 100. It's saying 183.1.254.2 is on
>AS100 not AS500.
>
>If you go to R2, you will see this message as well
>
>%BGP-3-NOTIFICATION: received from neighbor 183.1.254.1 2/2 (peer in wrong
>AS) 2 bytes 0064
>
>
>
>----- Original Message ----- From: "Digital Yemeni"
><digital-yemeni@hotmail.com>
>To: <ccielab@groupstudy.com>
>Sent: Saturday, February 24, 2007 5:47 AM
>Subject: BGP AS-No.
>
>
>>Hi Guys,
>>
>>Someone has asked me if the following scenario is "Solvable"
>>
>>R1 (IP:1.1.1.1)
>>----------------------
>>router bgp 100
>> neighbor 2.2.2.2 remote-as 200
>>
>>
>>
>>R2 (IP:2.2.2.2)
>>----------------------
>>router bgp 200
>> neighbor 1.1.1.1 remote-as 500 <---(intentional-mistake!)
>>
>>
>>Assuming that R1 does not know what the AS# that was configured on R2 -
>>(if R1 knows then it can use the "neighbor 2.2.2.2 local-as 500" command
>>to resolve the problem) - how can you figure out what AS# was configured
>>on R2 so u can establish relationship?
>>Note: "debug ip bgp detail" won't show you that!
>>
>>
>>I tried to see IF the "wrong AS# 500" shows up in any of the
>>communications debugs between R1 and R2 when they hardly try to establish
>>the relationshops but i could not succeed!! Is it really possible to
>>detect what AS# the remote router has configured for our router?
>>
>>
>>Best Regards,
>>
>>Digital
>>------------------------------------------------------------------------------------------------------------------
>>
>>
>>***********************************************************************************
>>*.* You'll NEVER succeed as a "CCIE" until you LOVE Cisco MORE than your
>>sleep! *.*
>>***********************************************************************************
>>I'm expected to be busy for the next 57 years + CCIE preparation adds on
>>that a bit. Therefore, please be concise on your email. Thank you!
>>
>>_________________________________________________________________
>>Don't just search. Find. Check out the new MSN Search!
>>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>>
>>_______________________________________________________________________
>>Subscription information may be found at:
>>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Mar 01 2007 - 07:38:48 ART