User Manual UMN:CLI
V8102
637
aa:nn_or_IPaddr:nn' format
ip extcommunity-list <100-199>
{deny | permit} LINE
Specifies a deny or permit statement of the extended
community-list.
100-199: expanded extended community list number
LINE: An ordered list as a regular-expression
ip extcommunity-list standard
WORD {deny | permit} [LINE]
Creates a standard extcommunity-list.
WORD: extended community list name
ip extcommunity-list expanded
WORD {deny | permit} LINE
Creates a expanded extcommunity-list.
WORD: extended community list name
To delete an entry in the extended community list, use the following command.
no ip extcommunity-list {<1-99>
| <100-199>}
Deletes an entry of the extended community-list.
no ip extcommunity-list {<1-99>
| <100-199>} {deny | permit} LINE
no ip extcommunity-list stand-
ard WORD [{deny | permit} LINE]
no ip extcommunity-list ex-
panded WORD [{deny | permit}
LINE]
To display the entry information of the extended community list, use the following com-
mand.
show ip extcommunity-list
Shows an entry of the extended communi-
ty-list.
show ip extcommunity-list {<1-99> | <100-
199> | WORD}
Route tagging with communities is always done with a route-map. You can attach up to
32 communities to a single route with one route-map set statement. And community-lists
can be used in match conditions in route-maps to match on communities attached to BGP
routes.
To display the BGP routes matching a community, use the following command.
Shows all routes in a BGP table that all
the specified communities attached.
show ip bgp community {AA:NN | local-AS |
no-advertise | no-export} [exact-match]
show bgp community {AA:NN | local-AS | no-
advertise | no-export} [exact-match]
show ip bgp {unicast | multicast} community