deny: Specifies the match mode for the extended community list as deny.
permit: Specifies the match mode for the extended community list as permit.
{ rt route-target }&<1-32>: Specifies the RT extended community attribute, a string of 3 to 21 characters.
&<1-32> indicates that the argument before it can be entered up to 32 times.
A route-target has the following forms:
16-bit AS number:32-bit self-defined number. For example, 101:3. The AS number is in the range of
•
0 to 65535, and the self-defined number is in the range of 0 to 4294967295.
•
32-bit IP address:16-bit self-defined number. For example, 192.168.122.15:1. The self-defined
number is in the range of 0 to 65535.
32-bit AS number:16-bit self-defined number. For example, 70000:3. The AS number is in the range
•
of 65536 to 4294967295, and the self-defined number is in the range of 0 to 65535.
Examples
# Define extended community list 1 to permit routes with RT 200:200 to pass.
<Sysname> system-view
[Sysname] ip extcommunity-list 1 permit rt 200:200
Related commands
apply extcommunity
•
display ip extcommunity-list
•
if-match extcommunity
•
route-policy
Use route-policy to create a routing policy and a node, and enter routing policy node view.
Use undo route-policy to remove a routing policy or a node of it.
Syntax
route-policy route-policy-name { deny | permit } node node-number
undo route-policy route-policy-name [ deny | permit ] [ node node-number ]
Default
No routing policy is created.
Views
System view
Predefined user roles
network-admin
Parameters
route-policy-name: Specifies a name for the routing policy, a case-sensitive string of 1 to 63 characters.
deny: Specifies the deny match mode for the routing policy node. If a route matches all the if-match
clauses of the node, it is denied without matching against the next node. If not, it matches against the
next node.
573