>we use it a lot for our internal iBGP peers - if you define a peer-group
>with stuff like next-hop-self, remote-as, send-community, update-source, and
>the like, then all you need to do for each peer (and you can get a lot in a
>fully meshed iBGP environment) is assign it to a peer-group.
>
>Remember that Cisco recommend Route Reflectors and Confederations for more
>than _100_ peers) all you need do is assign each peer to a peer group and
>all those things are there already - you needn't specify it in each neighbor
>statement. Saves on config lines, and keeps things standardised.
>
>Howard,
>
>not sure how this reduces processor loading... care to elaborate?
>
>HTH
When an update goes out, the policies for the Adj-RIB-Out need to be
examined only once for every peer in the group, rather than for every
peer.
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
