BGP: Configuring Route Maps
Atomic- This adds the atomic aggregate attribute to the update. aggregate
Use the command:
set atomic-aggregate
Extended This specifies a value to set as the Extended Community attribute in the update message. community
Use the command:
set extcommunity {rtsoo} <ext-comm-number>
The rt parameter configures a route target extended community. This consists of routers that will receive matching routes.
The soo parameter configures a
Next hop This specifies the next hop for matching routes.
Use the command:
set ip next-hop <ipadd>
Originator ID This specifies the Originator ID attribute in the update message. The originator ID is the router ID of the IBGP peer that first learned this route, either via an EBGP peer or by some other means such as importing it.
Use the command:
set originator-id <ipadd>
Weight Specifies a weight value for matching routes. The weight value assists in best path selection of BGP routes. It is stored with the route in the BGP routing table, but is not advertised to peers. When there are multiple routes with a common destination, the device uses the route with the highest weight value.
Use the command:
set weight <0-4294967295>
Dampening This is used to turn out BGP dampening and optionally set dampening parameters for the routes that match the route map entry.
Use one of the commands:
set dampening
set dampening <reachtime>
set dampening <reachtime> <reuse> <suppress> <maxsuppress>
Page 32 Use Route Maps and Other Filters to Filter and Alter BGP and OSPF Routes