From: srdja blagojevic (srdja1@pexim.co.yu)
Date: Thu Nov 23 2006 - 04:20:24 ART
Nambi,
this output (you are talking about) is what I can see on SW1 and on R1. And
I can conclude that SW1 have wrong AS configured for neighbor R1, and that
right AS should be 30 (001E in my example). But I can not see on R1 what is
wrong AS configured on SW1 for neighbor R1 (12 in my example).
Thanks, anyway :)
rgds,
Srdja
-----Original Message-----
From: Nambi Appachigounder [mailto:nambi_gct@yahoo.co.in]
Sent: Thursday, November 23, 2006 03:34
To: srdja blagojevic; 'CharlesB'; 'Liu_Liao'; 'ccielab groupstudy'
Subject: RE: BGP misconfigure AS number
Not sure if this is the easiest.But I use this.
All the notifications are logged.The first two octets represent the AS
number.
00:18:35: %BGP-3-NOTIFICATION: sent to neighbor
10.1.1.2 2/2 (peer in wrong AS) 2 bytes 00A0 FFFF FFFF FFFF FFFF FFFF FFFF
FFFF FFFF 002D 0104 00A0 00B4 5800
0002 1002 0601 0400 0100 0102 0280 0002 0202 00
Here 00A0 is the AS number.i.e 160.
regds
nambi.
--- srdja blagojevic <srdja1@pexim.co.yu> wrote:
> Ok guys I have question for you all regarding this matter.
>
> My topology and configs are like this:
>
> R1 (fa0/1) ---------------(Vlan 17) SW1
>
> --------
> R1:
> --------
> !
> interface FastEthernet0/0
> ip address 187.1.17.1 255.255.255.0
> !
> !
> router bgp 30
> no synchronization
> bgp log-neighbor-changes
> neighbor 187.1.17.7 remote-as 100
> no auto-summary
> !
>
>
> -------
> SW1:
> -------
>
> !
> interface Vlan17
> ip address 187.1.17.7 255.255.255.0
> !
> router bgp 100
> bgp log-neighbor-changes
> neighbor 187.1.17.1 remote-as 12
> !
>
>
------------------------------------------------------
>
> And now the question:
>
> On SW1 I can find out about mistake in configured AS
> from: debug ip bgp,
>
> But if I can not access to SW1, how I can find this mistake on R1??
>
> What debug I have to turn on, to find out that SW1 has wrong AS
> configured for me (R1), so I can put local AS command on neighbor
> command for this wrong AS. How can I find out that AS 12 is configured
> on SW1 instead of AS 30, looking only on R1?
>
>
>
> Here is debug ip bgp from R1:
>
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 passive
> open to 187.1.17.1
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 went from
> Active to Idle
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 went from
> Idle to Connect
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 rcv
> message type 1, length (excl.
> header) 26
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 rcv OPEN,
> version 4, holdtime 180
> seconds
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 went from
> Connect to OpenSent
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 sending
> OPEN, version 4, my as:
> 30, holdtime 180 seconds
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 rcv OPEN
> w/ OPTION parameter len:
> 16
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 rcvd OPEN
> w/ optional parameter
> type 2 (Capability) len 6
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 OPEN has
> CAPABILITY code: 1,
> length 4
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 OPEN has
> MP_EXT CAP for afi/safi:
> 1/1
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 rcvd OPEN
> w/ optional parameter
> type 2 (Capability) len 2
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 OPEN has
> CAPABILITY code: 128,
> length 0
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 OPEN has
> ROUTE-REFRESH
> capability(old) for all address-families
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 rcvd OPEN
> w/ optional parameter
> type 2 (Capability) len 2
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 OPEN has
> CAPABILITY code: 2,
> length 0
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 OPEN has
> ROUTE-REFRESH
> capability(new) for all address-families
> BGP: 187.1.17.7 rcvd OPEN w/ remote AS 100
> *Nov 22 20:16:37.010 CET: BGP: 187.1.17.7 went from
> OpenSent to OpenConfirm
> *Nov 22 20:16:37.014 CET: BGP: 187.1.17.7 send
> message type 1, length (incl.
> header) 45
> *Nov 22 20:16:37.014 CET: BGP: 187.1.17.7 rcv
> message type 3, length (excl.
> header) 4
> *Nov 22 20:16:37.014 CET: %BGP-3-NOTIFICATION:
> received from neighbor
> 187.1.17.7 2/2 (peer in wrong AS) 2 bytes 001E
> *Nov 22 20:16:37.014 CET: BGP: 187.1.17.7 went from
> OpenConfirm to Closing
> *Nov 22 20:16:37.030 CET: BGPNSF state: 187.1.17.7
> went from nsf_not_active
> to nsf_not_active
> *Nov 22 20:16:37.030 CET: BGP: 187.1.17.7 went from
> Closing to Idle
> *Nov 22 20:16:37.030 CET: BGP: 187.1.17.7 closing
> *Nov 22 20:16:37.130 CET: BGP: 187.1.17.7 went from
> Idle to Active
> *Nov 22 20:16:37.130 CET: BGP: 187.1.17.7 open
> active delayed 27275ms
> (35000ms max, 28% jitter)
> *Nov 22 20:17:04.406 CET: BGP: 187.1.17.7 open
> active, local address
> 187.1.17.1
> *Nov 22 20:17:04.406 CET: BGP: 187.1.17.7 went from
> Active to OpenSent
> *Nov 22 20:17:04.406 CET: BGP: 187.1.17.7 sending
> OPEN, version 4, my as:
> 30, holdtime 180 seconds
> *Nov 22 20:17:04.406 CET: BGP: 187.1.17.7 send
> message type 1, length (incl.
> header) 45
> *Nov 22 20:17:04.410 CET: BGP: 187.1.17.7 rcv
> message type 3, length (excl.
> header) 4
> *Nov 22 20:17:04.410 CET: %BGP-3-NOTIFICATION:
> received from neighbor
> 187.1.17.7 2/2 (peer in wrong AS) 2 bytes 001E
> *Nov 22 20:17:04.410 CET: BGP: 187.1.17.7 went from
> OpenSent to Closing
> *Nov 22 20:17:04.422 CET: BGPNSF state: 187.1.17.7
> went from nsf_not_active
> to nsf_not_active
> *Nov 22 20:17:04.422 CET: BGP: 187.1.17.7 went from
> Closing to Idle
> *Nov 22 20:17:04.422 CET: BGP: 187.1.17.7 closing
> *Nov 22 20:17:04.522 CET: BGP: 187.1.17.7 went from
> Idle to Active
> *Nov 22 20:17:04.522 CET: BGP: 187.1.17.7 open
> active delayed 31584ms
> (35000ms max, 28% jitter)
> *Nov 22 20:17:36.106 CET: BGP: 187.1.17.7 open
> active, local address
> 187.1.17.1
> *Nov 22 20:17:36.106 CET: BGP: 187.1.17.7 went from
> Active to OpenSent
> *Nov 22 20:17:36.106 CET: BGP: 187.1.17.7 sending
> OPEN, version 4, my as:
> 30, holdtime 180 seconds
> *Nov 22 20:17:36.106 CET: BGP: 187.1.17.7 send
> message type 1, length (incl.
> header) 45
> *Nov 22 20:17:36.110 CET: BGP: 187.1.17.7 rcv
> message type 3, length (excl.
> header) 4
> *Nov 22 20:25:58.978 CET: %BGP-3-NOTIFICATION:
> received from neighbor
> 187.1.17.7 2/2 (peer in wrong AS) 2 bytes 001E
> *Nov 22 20:17:36.110 CET: %BGP-3-NOTIFICATION:
> received from neighbor
> 187.1.17.7 2/2 (peer in wrong AS) 2 bytes 001E
> *Nov 22 20:17:36.110 CET: BGP: 187.1.17.7 went from
> OpenSent to Closing
> *Nov 22 20:17:36.110 CET: BGPNSF state: 187.1.17.7
> went from nsf_not_active
> to nsf_not_active
> *Nov 22 20:17:36.110 CET: BGP: 187.1.17.7 went from
> Closing to Idle
> *Nov 22 20:17:36.110 CET: BGP: 187.1.17.7 closing
> *Nov 22 20:17:36.210 CET: BGP: 187.1.17.7 went from
> Idle to Active
> *Nov 22 20:17:36.210 CET: BGP: 187.1.17.7 open
> active delayed 31644ms
> (35000ms max, 28% jitter)
> *Nov 22 20:18:07.854 CET: BGP: 187.1.17.7 open
> active, local address
> 187.1.17.1
> *Nov 22 20:18:07.854 CET: BGP: 187.1.17.7 went from
> Active to OpenSent
> *Nov 22 20:18:07.854 CET: BGP: 187.1.17.7 sending
> OPEN, version 4, my as:
> 30, holdtime 180 seconds
> *Nov 22 20:18:07.854 CET: BGP: 187.1.17.7 send
> message type 1, length (incl.
> header) 45
> *Nov 22 20:18:07.858 CET: BGP: 187.1.17.7 rcv
> message type 3, length (excl.
> header) 4
> *Nov 22 20:18:07.858 CET: %BGP-3-NOTIFICATION:
> received from neighbor
> 187.1.17.7 2/2 (peer in w
> rong AS) 2 bytes 001E
>
> Thanks,
> Srdja
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> CharlesB
> Sent: Wednesday, November 22, 2006 18:47
> To: Liu_Liao; 'ccielab groupstudy'
> Subject: RE: BGP misconfigure AS number
>
> I think they are after local-as command, you can
> change how your neighbor
> sees you.
>
> router bgp 10
> neighbor 10.1.1.2 local-as 110
> neighbor 10.1.1.2 remote-as XXXX
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com]On Behalf Of
> Liu_Liao
> Sent: Wednesday, November 22, 2006 6:58 AM
> To: 'ccielab groupstudy'
> Subject: BGP misconfigure AS number
>
>
> Hi All
> ( BGP AS 10 )
> RA(10.1.1.1/24) <----> RB(10.1.1.2)
> (neighbor 10.1.1.1 remote-as 110 ==> mistake) If
> RB's manager have
> misconfigure of the AS number and the RA's manager
> doesn't know this
> problem.
> The BGP peer can work or can't
> If can
> How many solutions can resolve it
>
>
This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:48 ART