To remove extended communities from the extended community attribute of an inbound or outbound Border Gateway Protocol (BGP) update, use the set extcomm-list delete command. To remove a previous set extcomm-list delete command, use the no form of this command.
set extcomm-list community-list-name delete
no set extcomm-list
|
community-list-name |
Standard or expanded extended community list name. The name is any alphanumeric string up to 63 characters. |
No communities are removed.
Route-map configuration mode
|
Release |
Modification |
|---|---|
|
5.0(3)N1(1) |
This command was introduced. |
Use the set extcomm-list delete command in a route map to delete the extended community attribute in a BGP route.
You must have a match clause in a route map (even if it points to a "permit everything" list) if you want to use set commands.
The set commands specify the set actions to be performed when all of the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
When you configure both the set extcommunity community-number and set ext comm-list delete commands in the same sequence of a route map attribute, the deletion operation (set extcomm-list delete) is performed before the set operation (set extcommunity community-number).
This example shows how to remove extended communities from the extended community attribute of an inbound or outbound update:
switch(config)# route-map test1
switch(config-route-map)#Â match as-path 1
switch(config-route-map)#Â set extcomm-list list1 delete
|
Command |
Description |
|---|---|
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match extcommunity |
Matches a BGP extended community. |
|
set extcommunity |
Sets the BGP extended communities attribute. |