It's not so much a slave relationship but rather an administrative grouping.
The only thing to technically need is to point the neighbor (ip) to the peer-group itself. The peer-group can contain everything else... remote-as, update-source, distribute-list, etc., etc. You're just preventing yourself from typing in the same commands over and over and over and over and over and over and over. (you get the point!) HTH, Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al. CCSI/JNCI-M/JNCI-ER VP - Technical Training - IPexpert, Inc. IPexpert Sr. Technical Instructor A Cisco Learning Partner - We Accept Learning Credits! [EMAIL PROTECTED] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 http://www.ipexpert.com -----Original Message----- From: Bradley Lowry [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 10:49 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: BGP peer group questions Scott, I'm trying to make BGP peer groups work. All the resources I can find only show the configuration on the router where options are set for the peer-group. What must be configured (besides the "neighbor x.x.x.x remote-as xx") on the router that will be pulling the BGP configurations? Also, how do you check to make sure that the 'slaves' for want of a better word are actually getting their options? Any help would be appreciated. Thanks, Bradley
