...
The set routing route-map action atomicmap 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-map action atomicaction atomic-aggregate command removes the configurations.
...
set routing route-map <route-map-name> order <NUMBER> action atomicset-action atomic-aggregate
delete routing route-map <route-map-name> <NUMBER> action atomic 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. | metric <VALUE> | Specifies the value to be set as the metric attribute of the route entry. Range: 0 to 4294967295
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 in clause to inform the route map to modify the metric value of the route:recipient that the route is aggregated and is a recognized optional attribute.
| Code Block |
|---|
admin@Xorplus# set routing route-map GlobalMap order 10 set-action localatomic-preference 100aggregate admin@Xorplus# commit |