Step
1.
Enter system view.
2.
Configure a community
list.
Configuring an extended community list
You can configure multiple items for an extended community list that is identified by a number. The
relationship between items is logic OR. A route that matches one item matches the extended community
list.
To configure an extended community list:
Step
1.
Enter system view.
2.
Configure an extended
community list.
Configuring a MAC list
If all the items are set to deny mode, no routes can pass the MAC list. To allow other routing information
to pass, you must configure the permit 0.0.0.0 0 less-equal 32 item following multiple deny items.
To configure a MAC list:
Step
1.
Enter system view.
2.
Configure a MAC
list.
Configuring a routing policy
Configuration prerequisites
Configure filters and routing protocols, and determine the routing policy name, node numbers, match
criteria, and the attributes to be modified.
Command
system-view
•
Configure a basic community list:
ip community-list { basic-comm-list-num | basic
basic-comm-list-name } { deny | permit }
[ community-number&<1-32> | aa:nn&<1-32> ]
[ internet | no-advertise | no-export |
no-export-subconfed ] *
•
Configure an advanced community list:
ip community-list { adv-comm-list-num | advanced
adv-comm-list-name } { deny | permit }
regular-expression
Command
system-view
ip extcommunity-list ext-comm-list-number { deny |
permit } { rt route-target }&<1-32>
Command
system-view
mac-list mac-list-name [ index index-number ] { deny |
permit } mac-address [ mask-length ]
399
Remarks
N/A
Use either method.
By default, no
community list is
configured.
Remarks
N/A
By default, no extended
community list is
configured.
Remarks
N/A
By default, no MAC list is
configured.