From: Scott Morris (smorris@ipexpert.com)
Date: Tue Jul 31 2007 - 21:12:43 ART
You'll start receiving error messages about "peer in wrong as" which will
actually be the correct AS number in hex. If you search the archives, I
think you'll find a few discussions with examples and whatnot. Basically
just pick any random AS and watch the messages!
Cheers,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
smorris@ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Uchil Perera
Sent: Tuesday, July 31, 2007 6:15 PM
To: ccielab@groupstudy.com
Subject: BGP AS
Hi Group,
Below is the scenario
R1 - AS 100 <---------------------> R2 - AS 254
R1
router bgp 100
neighbor r2 remote-as 254
R2
router bgp 254
neighbor r1 remote-as X
Though R1 is in AS 100 R2 is trying to peer with R1 using a different AS,
which is unknown. Is there any way to debug and see, with which AS the
neighbor is trying to peer with.
Regards
---------------------------------
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:42 ART