422
apply cost clauses with the + or - keyword, the apply community clauses with the additive keyword,
and the apply extcommunity clauses with the additive keyword), all the apply clauses configured
on the matching nodes take effect.
• If you configure the apply community clause for multiple nodes that are combined by the continue
clause, the apply comm-list delete clause configured on the current node cannot delete the
community attributes set by preceding nodes.
To configure a continue clause:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter routing policy node view.
route-policy route-policy-name
{ deny | permit } node node-number
N/A
3. Specify the next node to be
matched.
continue [ node-number ]
By default, no continue clause is
configured.
The specified next node must
have a larger number than the
current node.
Displaying and maintaining the routing policy
Execute display commands in any view and reset commands in user view.
Task Command
Display BGP AS path list information. display ip as-path [ as-path-number ]
Display BGP community list information.
display ip community-list [ basic-community-list-number |
adv-community-list-number | name comm-list-name ]
Display BGP extended community list
information.
display ip extcommunity-list [ ext-comm-list-number ]
Display IPv4 prefix list statistics. display ip prefix-list [ name prefix-list-name ]
Display IPv6 prefix list statistics. display ipv6 prefix-list [ name prefix-list-name ]
Display routing policy information. display route-policy [ name route-policy-name ]
Clear IPv4 prefix list statistics. reset ip prefix-list [ prefix-list-name ]
Clear IPv6 prefix list statistics. reset ipv6 prefix-list [ prefix-list-name ]
Routing policy configuration examples
Applying a routing policy to IPv4 route redistribution
Network Requirements
As shown in Figure 101, Switch B exchanges routing information with Switch A by using OSPF and with
Switch C by using IS-IS.
To Next Page
Loading...
