goto next-node

Function

The goto next-node command further matches routes against a specified node after the routes match the current node.

The undo goto next-node command restores the default configuration.

By default, if a route matches the current node, it matches the route-policy and is no longer matched against other nodes.

Product	Support
S5720-EI, S5720-HI, S5730-HI, S5731-S, S5731S-S, S5731-H, S5731S-H, S5732-H, S6720-EI, S6720-HI, S6720S-EI, S6730S-H, and S6730-H	Supported
S2720-EI, S5720I-SI, S5720-LI, S5735-L, S5735S-L, S5735S-L-M, S5720S-LI, S5720S-SI, S5720-SI, S5735-S, S5735S-S, S5735-S-I, S5730S-EI, S5730-SI, S6720-LI, S6720S-LI, S6720-SI, S6720S-SI, S6730-S, and S6730S-S	Not supported

Format

goto next-node [ node ]

undo goto next-node

Parameters

Parameter	Description	Value
node	Specifies the index of a node against which routes are further matched.	The value is an integer ranging from 1 to 65535 and must be greater than the index of the current node.

Views

Route-Policy view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The relationship among the matching rules of nodes in the same route-policy is OR. Specifically, if a route matches a node, it matches the route-policy and is no longer matched against other nodes. If you want the route to be matched against two or more nodes, run the goto next-node command so that the route is further matched against a specified node after the route matches the current node.

If node is not specified in the command, the route will be further matched against the next node of the current node by default.
If the node specified in the command does not exist, the route will be further matched against the next node of the specified node by default. If the next node of the specified node does not exist either, the route fails to match the route-policy, and no apply clause will be applied to the route.

Precautions

If the goto next-node command is run in the route-policy view and a route matches all the specified nodes, the apply clauses of these nodes will be applied to the route.
If the route fails to match one node, the route is matched against the next node until it succeeds in matching a node, and then the apply clauses of the nodes that the route matches will be applied to the route. If the route fails to match all nodes, no apply clauses will be applied to the route.
If the goto next-node command is run for multiple nodes, and QoS policy propagation on BGP (QPPB) policies are configured for these nodes using one or more of the apply ip-precedence, apply qos-local-id, apply behavior, and apply traffic-index commands, only the configuration of the last node takes effect.
In the same route-policy, a maximum of 50 nodes can be specified using the command.
In the same route-policy, if this command is configured to match routes against multiple nodes, a maximum of 10 AS numbers, 16 RT extended community attributes, 16 color extended community attributes, and 36 community attributes can be added to the routes that match the nodes; if multiple community filters are used in the same route-policy to delete community attributes from the routes that match filtering conditions, only the first community filter takes effect.

Example

# Configure a route-policy named test to further match routes against node 20 after the routes match node 10.

<HUAWEI> system-view
[HUAWEI] route-policy test permit node 10
[HUAWEI-route-policy] if-match tag 123
[HUAWEI-route-policy] apply cost 10
[HUAWEI-route-policy] goto next-node 20
[HUAWEI-route-policy] quit
[HUAWEI] route-policy test permit node 20
[HUAWEI-route-policy] if-match tag 456
[HUAWEI-route-policy] apply local-preference 30