I have just configured the scenario below on my lab and it appears that the
internal BGP peers do not need to know the Confed id or peers.  If I look at
the bgp table all the correct routing info is getting passed i.e. an
internal bgp router still sees in its bgp routing table that networks have
came from certain confeds i.e. as path = (8) (7) 254 23.  I believe now that
you only have to configure confed and peers only on the borders.

correct me if I am wrong here.

-----Original Message-----
From: Sijbren Beukenkamp [mailto:[EMAIL PROTECTED]]
Sent: 01 November 2001 15:39
To: McCallum, Robert
Cc: 'Ccielab' (E-mail); Cisco@Groupstudy. Com (E-mail);
[EMAIL PROTECTED]
Subject: Re: BGP Confederations


Yes,
you have to configure all routers within your confederation  with you 
confederation id.

Met vriendelijke groet/ Kind regards,
Sijbren
++++++++++++++++++++++++++++++++++++++++++++++++++++
Ing. Sijbren Beukenkamp     IBM Global Services
Internetworking Specialist    Integrated Technology Services
                                            Networking & Connectivity 
Services
 http://www.ibm.com/services/nc/
GSM    +31 (0)6 53761703          The Netherlands 
Office: +31 (0)30 2850 666




"McCallum, Robert" 
Sent by: [EMAIL PROTECTED]
01-11-2001 16:25
Please respond to "McCallum, Robert"

 
        To:     "'Ccielab' (E-mail)" , "Cisco@Groupstudy.  Com 
(E-mail)" 
        cc: 
        Subject:        BGP Confederations

 

Hi,

If you have 4 routers within an confederation r1,r2,r3&r4.  R1 has and 
EBGP connection to another As so therefore has the bgp confederation id 
and confed peer statements on it.  My question is do all of the IBGP 
router (r2,r3&r4) require the confed statements on them even if they are 
only IBGP
routers??

14 days to go!! Starting to have some fun !!

Robert McCallum




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=24953&t=24953
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to