The set routing route-map set-action atomic-aggregate command is used to inform the route recipient that the route is aggregated and is a recognized optional attribute.

The delete routing route-map set-action atomic-aggregate command removes the configurations.

Command Syntax

set routing route-map <route-map-name> order <NUMBER> set-action atomic-aggregate

delete routing route-map <route-map-name> order <NUMBER> set-action atomic-aggregate

Parameter

Parameter	Description
route-map <route-map-name>	Specifies the name of the route map. Required.
order <NUMBER>	Specifies the sequence number of the entry. Required. The value is an integer that ranges from 1 to 65535.

Usage Guidelines

Sometimes a BGP publisher will receive two overlapping routes, one of which contains addresses that are a subset of the other route. Normally the BGP publisher prefers the finer route (the former), but when publishing externally, if it chooses to publish the coarser one (the latter), it then needs to append the ATOMIC-AGGREGATE attribute to inform the peer. It is actually a warning, because publishing the coarser route means that the finer routing information is lost in the publishing process. When performing route aggregation, the ATOMIC-AGGREGATE attribute is added to the aggregated route information.

Example

Configure a action clause to inform the route recipient that the route is aggregated and is a recognized optional attribute.

admin@Xorplus# set routing route-map GlobalMap order 10 set-action atomic-aggregate
admin@Xorplus# commit

Browser not supported