Specify the AS Path
By default, the AS path for aggregate routes is built from the component routes. To manually specify the AS path and associate AS path information with the routes, include the
as-pathoption:[edit routing-options aggregate (defaults | route)]as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate><aggregatoras-number in-address>For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.
as-pathis the AS path to include with the route. It can include a combination of individual AS path numbers and AS sets. Enclose sets in brackets ( [ ] ). The first AS number in the path represents the AS immediately adjacent to the local AS. Each subsequent number represents an AS that is progressively farther from the local AS, heading toward the origin of the path.You also can specify the AS path using the BGP origin attribute, which indicates the origin of the AS path information:
egp—Path information originated in another AS.igp—Path information originated within the local AS.incomplete—Path information was learned by some other means.To attach the BGP
ATOMIC_AGGREGATEpath attribute to the aggregate route, specify theatomic-aggregateoption. This path attribute indicates that the local system selected a less specific route rather than a more specific route.To attach the BGP
AGGREGATORpath attribute to the aggregate route, specify theaggregatoroption. When using this option, you must specify the last AS number that formed the aggregate route (encoded as 2 octets), followed by the IP address of the BGP system that formed the aggregate route.