Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Traffic Steering Rules

Use this information to enter the settings in the Traffic Steering section of a WAN Edge template, hub profile, or device configuration.

Navigating to a Traffic Steering Rule

You'll find traffic steering policies on the configuration page for your WAN Edge templates (for spokes), hub profiles, and individually managed devices.

  • For a WAN Edge template—From the left menu, select Organization > WAN > WAN Edge Templates. Click a template, or create a new one. Scroll down to the Traffic Steering section.

  • For a hub profile—From the left menu, select Organization > WAN > Hub Profiles. Click a profile, or create a new one. Scroll down to the Traffic Steering section.

  • For an individually managed WAN Edge device—From the left menu, select WAN Edges > WAN Edges. Click a device. Scroll down to the Traffic Steering section.

Traffic Steering Overview

You can think of traffic steering in Juniper Mist as how the WAN Edge device uses your LAN and WAN interfaces to connect your users to your applications. Define traffic steering rules to define the various paths that application traffic can traverse to reach its intended destination.

When an application has multiple available paths, you can further restrict the traffic to a subset of those paths and establish a preference order. Additionally, traffic steering enables the loading and balancing of multiple streams across the available paths for optimal performance and redundancy.

Traffic steering is where you define the different paths that application traffic can take to traverse the network. The paths that you configure within traffic steering determine the destination zone. For any traffic steering rule, you must define the paths for traffic to traverse and strategies for utilizing those paths.

Note: If you're planning to create application policies for an SRX Series Firewall, you'll also need to create traffic steering policies. Every application policy needs to be associated with a traffic steering rule.

Order of Traffic Steering Rules

Be aware of these factors when defining rules.

  • SRX, being a zone-based firewall, determines the destination zone based on the paths configured within the traffic steering policy. This integration ensures that security policies are enforced in conjunction with the defined traffic paths.

  • SSR employs a proprietary traffic steering solution known as Secure Vector Routing. This innovative approach determines the next hop and the optimal vector to the destination, leveraging advanced algorithms and network intelligence to make informed routing decisions.

Settings for Traffic Steering

Table 1: Settings for Traffic Steering
Field Description
Name Enter a descriptive name to identify this traffic steering rule. The name can contain up to 32 letters, numbers, underscores, and dashes. It must start and end with a letter or number.
Strategy
  • Ordered—Starts with a specified path and fails over to backup path(s) when needed.
  • Weighted—Selects the paths with lowest cost; if paths have equal costs, trraffic is load-balanced.
  • Equal-cost multipath—Load balances traffic equally across multiple paths.
Paths Displays all the paths that you've already defined.

Click a path or click Add Paths. Then, enter the path settings, and click the check mark in the Add Paths title bar.

The settings include:

  • Type and Name—Select a type from the drop-down list. Based on the selected type, select the network, name, or provider.

  • Cost(applicable to the Weighted strategy only)—Enter a number or variable to indicate the relative cost of this path. The path with the lowest cost will be prefered over those with higher costs.