From: Scott M Vermillion (scott_ccie_list@it-ag.com)
Date: Fri Oct 24 2008 - 20:55:45 ARST
>00C8 is BB1`s AS = 200 and showing on R1
>BB1#(Dont have control )
>*Mar 1 00:26:01.455: %BGP-3-NOTIFICATION: received from neighbor 1.1.1.1
2/2 (p
>eer in wrong AS) 2 bytes 00C8
>*Mar 1 00:26:29.115: %BGP-3-NOTIFICATION: received from neighbor 1.1.1.1
2/2 (p
>eer in wrong AS) 2 bytes 00C8
>now what you think ?
I think that our results are (nearly) identical! ;-)
The misconfiguration is AS600, which should have been AS200, no (as you
said, you mistyped or didn't know)? Show me where AS600 shows up in any
error message being sent or received. That's the information that you'd
need to know if you were trying to compensate for a bad configuration of a
device which you couldn't access (e.g. a lab backbone router).
BTW, your example seems a bit odd. You have stuff from BB1, BB2, and R1 all
mixed together. Try a baseline topology of just two routers and see what
you see. Make sure you place the misconfiguration on the device which you
are using as your non-accessible device. Then be on the lookout for what
the incorrectly configured AS might be from the perspective of the
non-backbone device that you *can* access so that you can compensate for the
misconfiguration (or unknown configuration). Or just simply refer to my
earlier example to see that the misconfigured AS number is never advertised
in any BGP message in any direction; only the "My AS" sent in open messages
is reflected back by the misconfigured router.
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