- as-path <as-path> <origin (egp
| igp | incomplete)> <atomic-aggregate> <aggregator as-number ip-address>;
- [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
(aggregate | generate | static) (defaults | route)],
- [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
rib routing-table-name (aggregate | generate | static) (defaults |
route)],
- [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)],
- [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)],
- [edit routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)],
- [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)],
- [edit routing-options (aggregate | generate | static) (defaults | route)],
- [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)]
Statement introduced before JUNOS Release 7.4.
Associate BGP autonomous system (AS) path information with a static, aggregate, or generated route.
In JUNOS Release 9.1 and later, the numeric range for the AS number is extended to provide BGP support for 4-byte AS numbers. For more information, see Configuring AS Numbers for BGP. All releases of the JUNOS Software support 2-byte AS numbers.
aggregator—(Optional) Attach the BGP aggregator path attribute to the aggregate route. You must specify the last AS number that formed the aggregate route (encoded as two octets) for as-number, followed by the IP address of the BGP system that formed the aggregate route for in-address.
as-path—(Optional) 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 cannot specify a regular expression for as-path; you must use a full, valid AS path.
atomic-aggregate—(Optional) Attach the BGP atomic-aggregate path attribute to the aggregate route. This path attribute indicates that the local system selected a less specific route instead of a more specific route.
origin egp—(Optional) BGP origin attribute that indicates that the path information originated in another AS.
origin igp—(Optional) BGP origin attribute that indicates that the path information originated within the local AS.
origin incomplete—(Optional) BGP origin attribute that indicates that the path information was learned by some other means.
See Configuring Static Routes, Configuring Aggregate Routes, and Configuring Generated Routes.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.