Quanta Computer QuantaMesh, User Manual, Page: 771 / 1020

UANTA COMPUTER INC.
Layer 2/3/4 Managed Switch
QuantaMesh | Routing Commands 771
6.10.2.11 set as-path
To prepend one or more AS numbers to the AS path in a BGP route, use the set as-path command in
Route Map Configuration mode. This command is normally used to insert one or more instances of the
local AS number at the beginning of the AS_PATH attribute of a BGP route. Doing so increases the AS
path length of the route. The AS path length has a strong influence on BGP route selection. Changing
the AS path length can influence route selection on the local router or on routers to which the route is
advertised.
When prepending an inbound route, if the first segment in the AS_PATH of the received route is an
AS_SEQUENCE, as-path-string is inserted at the beginning of the sequence. If the first segment is an
AS_SET, as-path-string is added as a new segment with type AS_SEQUENCE at the beginning of the
AS path. When prepending an outbound route to an external peer, as-path-string follows the local AS
number, which is always the first ASN.
To remove a set command from a route map, use the no form of this command.
Syntax
set as-path prepend <as-path-string>
no set as-path prepend
Default Setting
None.
Command Mode
Route Map Config
Parameter
as-path-string: A list of AS path numbers to insert at the beginning of the AS_PATH attribute of
matching BGP routes. To prepend more than one AS number, separate the ASNs with a space and
enclose the string in quotes. Up to ten AS numbers may be prepended.
6.10.2.12 set comm-list delete
To remove BGP communities from an inbound or outbound UPDATE message, use the set comm-list
delete command in Route Map Configuration mode. A route map with this set command can be used to
remove selected communities from inbound and outbound routes. When a community list is applied to a
route for this purpose, each of the route's communities is submitted to the community list one at a time.
Communities permitted by the list are removed from the route. Because communities are processed
individually, a community list used to remove communities should not include the exact-match option on
statements with multiple communities. Such statements can never match an individual community.
When a route map statement includes both set community and set comm-list delete terms, the set
comm-list delete term is processed first, and then the set community term (meaning that, communities
are first removed, and then communities are added).
To delete the set command from a route map, use the no form of this command.
Syntax
set comm-list <community-list-name> delete
no set comm-list