5-26z It is not required to specify an AS number for creating an IBGP peer group.z If there already exists a peer in a peer group, you can neither change the AS number of the peergroup, nor delete a specified AS number through the undo command.z In a hybrid EBGP peer group, you need to specify the AS number for all peers respectively.Configuring BGP CommunityFollow these steps to configure BGP community:To do... Use the command... RemarksEnter system view system-view —Enter BGP view bgp as-number —Configure the peers toadvertise COMMUNITYattribute to each otherpeer group-nameadvertise-communityRequiredBy default, no COMMUNITY attribute orextended COMMUNITY attribute isadvertised to any peer group.Specify routing policy forthe routes exported tothe peer grouppeer group-name route-policyroute-policy-name exportRequiredBy default, no routing policy is specified forthe routes exported to the peer group.z When configuring BGP community, you must use a routing policy to define the specificCOMMUNITY attribute, and then apply the routing policy when a peer sends routing information.z For configuration of routing policy, refer to “IP Routing Policy Configuration”.Configuring BGP RRFollow these steps to configure BGP RR:To do... Use the command... RemarksEnter system view system-view —Enter BGP view bgp as-number —Configure the RR and its client peer group-name reflect-clientRequiredBy default, no RR and its client isconfigured.Configure route reflection betweenclients reflect between-clientsOptionalBy default, route reflection isenabled between clients.
