From: Scott M Vermillion (scott_ccie_list@it-ag.com)
Date: Fri Oct 24 2008 - 14:51:20 ARST
That answer could actually be a tad misleading (although correct, I
believe), since you did appropriately configure your sub-AS under the
'router bgp nnn' command. So what AS does BB1 need to peer with? That
would likely have been a better way to respond...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott M Vermillion
Sent: Friday, October 24, 2008 10:45 AM
To: 'nouman abbasi'; 'Cisco certification'
Subject: RE: BGP Error
The "BGP-3-NOTIFICATION" is telling you what the problem is (peer in wrong
AS). Recall that when you do confederation, your AS as seen by the outside
world is what you configure as your 'bgp confederation identifier nnn'; the
'router bgp nnn' command is where you specify your sub-as.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
nouman abbasi
Sent: Friday, October 24, 2008 10:28 AM
To: Cisco certification
Subject: BGP Error
Hello,
Need input on BGP Issue
I m able to ping from BB1 to R6 and vice-versa but bgp doesnt comes up....
<< Error >>
*Mar 1 08:37:53.965: %BGP-3-NOTIFICATION: sent to neighbor 150.1.2.1 2/2
(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
<<BB1>>
interface FastEthernet0
ip address 150.1.2.254 255.255.255.0
router bgp 254
no synchronization
bgp log-neighbor-changes
network 150.1.2.0
neighbor 150.1.2.1 remote-as 64514
<<R6>>
router bgp 64514
no synchronization
bgp router-id 6.6.6.6
bgp log-neighbor-changes
bgp confederation identifier 4
bgp confederation peers 64513
neighbor 2.2.2.2 remote-as 64513
neighbor 2.2.2.2 ebgp-multihop 5
neighbor 2.2.2.2 update-source Loopback0
neighbor 150.1.2.254 remote-as 254
no auto-summary
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