Defining a continue clause – H3C Technologies H3C S10500 Series Switches User Manual

Page 374

Advertising
background image

359

To do…

Use the command…

Remarks

Set a preferred value for BGP
routing information

apply preferred-value
preferred-value

Optional
Not set by default.

Set the QoS-local ID

apply qos-local-id local-id-value

Optional
Not set by default.

Set a tag value for RIP, OSPF, or
IS-IS routing information

apply tag value

Optional
Not set by default.

Configure FRR

apply fast-reroute

{ backup-interface interface-type
interface-number
[ backup-nexthop

ip-address ] }

Optional
Not configured by default.

NOTE:

The difference between IPv4 and IPv6 apply clauses is the command for setting the next hop for routing
information.

The apply ip-address next-hop and apply ipv6 next-hop commands do not apply to redistributed IPv4
and IPv6 routes, respectively.

For more information about IP precedence and QoS-local ID, see

ACL and QoS Configuration Guide.

Defining a continue clause

Follow these steps to define a continue clause for a routing policy:

To do…

Use the command…

Remarks

Enter system view

system-view

Create a routing policy and enter
routing policy view

route-policy route-policy-name
{ deny | permit } node node-number

Required
Not created by default.

Specify the next routing policy node
to be matched

continue [ node-number ]

Optional
Not configured by default.
The node number specified must

be larger that the current node

number.

NOTE:

If you configure the same type of apply clauses that set different values (including the apply community
and apply extcommunity clauses with the additive keyword) on nodes that are combined by the

continue clause, the apply clause configured on the last matching node takes 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 of preceding nodes.

Advertising