505
Configuring an extended community list
You can configure multiple items for an extended community list that is identified by a number. The
relationship between the items is logical OR. A route matches the extended community list if it
matches one item in the list.
To configure an extended community list:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure an
extended community
list.
ip extcommunity-list
ext-comm-list-number
{
deny
|
permit
} {
rt
route-target
|
soo
site-of-origin
}&<1-32>
By default, no extended
community lists exist.
Configuring a MAC list
If all the items are set to
deny
mode, no MAC address entries can pass the MAC list. To permit
unmatched MAC address entries, you must configure the
permit
0-0-0 0 item following multiple
deny
items.
The MAC list filter applies only to EVI IS-IS. For information about EVI IS-IS, see
EVI Configuration
Guide
.
To configure a MAC list:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure a MAC
list.
mac-list
mac-list-name
[
index
index-number
]
{
deny
|
permit
}
mac-address
[
mask-length
]
By default, no MAC lists
exist.
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.
Creating a routing policy
For a routing policy that has more than one node, configure a minimum of one permit node. A route
that does not match any node cannot pass the routing policy. If all the nodes are in
deny
mode, no
routes can pass the routing policy.
To create a routing policy:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a routing policy and a node, and
enter routing policy node view.
route-policy
route-policy-name
{
deny
|
permit
}
node
node-number
By default, no routing
policies exist.
Summary of Contents for HPE FlexNetwork 7500 series
Page 505: ...493 Connector N A ...
