Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Example: Configuring Walkup for Route Filters Globally to Improve Operational Efficiency

Use the walkup feature if you have concerns about policy performance because of split route filters across multiple policy terms. The walkup feature enables the consolidation of route filters under one policy term.

This example shows how to configure the route filter walkup feature globally for policy statements with route filters. When configured at the global level, the route filter walkup option applies to all policy statements. This example changes the default behavior of policy terms with multiple route filters globally, so that any reversion to the default “no walkup” behavior must be established locally.


This example uses the following hardware and software components:

  • A Juniper Networks router

  • A Junos operating system from 13.3 or above

Before you configure route filter walkup locally, be sure you have:

  • A properly configured routing policy or set of routing policies

  • A need to consolidate multiple route filter terms into fewer routing policy terms


Routing protocols exchange information with other routers running the same routing protocols. In many cases, route filters are used in routing policy statements to filter prefixes for import or export. In some cases, when route filters are split into many separate terms, performance is impacted. The route filter walkup feature allows consolidation of policy statement terms for operational efficiency.

This example uses BGP, but the same walkup feature applies to any routing protocol that supports route filtering of input or output.

You can configure a Juniper Networks router to change the default operation of a term in a policy statement with route filters. By default, only a single longest match attempt is made for all route filters in a term. The walkup feature allows the router to “walk up” the route filters in a term from longest match to less specific in search of a true condition. This allows consolidation of multiple terms in a policy statement and corresponding operational efficiency.

This example changes the default behavior globally, for all policy statements. You can still configure no-walkup for an individual policy.


In the sample network in Figure 1, the router CE1 is a router from another vendor. The rest are Juniper Networks routers. The walkup feature can be configured on any router in the figure, except for router CE1. The vendor of router CE1 might or not might support a similar feature.

Figure 1: Topology for the Global Walkup ExampleTopology for the Global Walkup Example

In the example, the following addresses are used:




Although the address space is not specifically reserved for documentation, the private RFC 1918 address space is used in this topic because of the flexibility and realistic scenarios that this address spaces provides.

Configuring Route Filter Walkup Globally

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details such as addresses and interfaces to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Device PE1


Step-by-Step Procedure

The following example requires that you navigate to various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide

To configure router PE1 to perform walkup globally and combine multiple route filters in one term:

  1. Configure the walkup feature globally.

  2. Configure the policy statements for an import policy named routeset1-import.

  3. Configure the policy options for the import and export policy statements.

  4. Apply the import and export policies to a BGP neighbor.


From configuration mode, confirm your configuration by entering the show protocols and show policy-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

If you are done configuring the device, enter commit from configuration mode.


Verifying Route Filter Operation


Display expected information about the routes to confirm the route filters are working as expected.

Notice that the orlonger filter includes the prefix-length-range /22-/24 filter in its scope. That is, any route with a prefix of 8 bits or longer could also be a route with a prefix in the range between 22 and 24 bits. Without the walkup feature enabled, a route such as would be rejected and become a hidden route. If the walkup feature is working as expected, then a route such as would be accepted by the policy.


From operational mode, enter the show route protocolbgp command. Make sure that is not a hidden route.

As a further check, make sure that no routes that should be accepted are hidden routes. From operational mode, enter the show route protocol bgp ip-address-prefix hidden command to verify this.


The presence of routes that are not the longest match in the configured policy route filter term shows that the walkup feature is functioning globally.


To troubleshoot route filter walkup globally:

Troubleshooting BGP


BGP is not functioning as expected.


See the BGP Configuration Overview topic, examples, and troubleshooting.

Troubleshooting Policy Statements


The policy statements are not functioning as expected.

Troubleshooting Route Filters


The route filters are not functioning as expected.


See the Route Filter Match Conditions topic, examples, and troubleshooting.