ECS4660-28F_Management Guide-R03

C HAPTER 51 | IP Routing Commands
Policy-based Routing for BGP
– 1910 –
set
atomic-aggregate
This command indicates the loss of some information in the route
aggregation process. Use the no form to remove this entry from a route
map.
SYNTAX
[no] set atomic-aggregate
COMMAND MODE
Route Map
COMMAND USAGE
The purpose of the atomic-aggregate attribute is to alert BGP speakers
along the path that some information have been lost due to the route
aggregation process and that the aggregate path might not be the best
path to the destination. This attribute should be set when the BGP speaker
advertises ONLY the less-specific prefix and suppresses more specific ones.
EXAMPLE
Console(config)#route-map RD permit 9
Console(config-route-map)#match peer 192.168.0.99
Console(config-route-map)#set atomic-aggregate
Console(config-route-map)#
set comm-list delete This command removes communities from the community attribute of
inbound or outbound routing messages. Use the no form to remove this
entry from a route map.
SYNTAX
[no] set comm-list {1-99 | 100-500 | community-list-name} [delete]
1-99 – Standard community list number that identifies one or more
groups of communities.
100-500 – Expanded community list number that identifies one or
more groups of communities.
community-list-name – Name of standard or expanded community
list. (Maximum length: 32 characters, no spaces or other special
characters)
COMMAND MODE
Route Map
COMMAND USAGE
When using the ip community-list command to configure a community
access list, each entry of a standard community list should list only one
community. Otherwise, the set comm-list delete command will not
succeed. For example, in order to be able to delete communities 100 and
200, you must create two separate entries with the ip community-list
command.