Hub Profiles: Traffic Steering
Traffic steering is where you define the different paths that application traffic can take to traverse the network. Destination zone is also determined by the paths configured within traffic steering.
We will set up three traffic steering policies, one for the overlay, one for the
underlay, and one for dc1-servers, which is detailed here. The
figure below shows the policies in the context of a screenshot.
To set up Traffic Steering,
- Under the Traffic Steering section, click the Add Traffic Steering button to display the Traffic Steering configuration screen.
- Give your policy a name. For this example we'll use dc1-servers, but any name will do.
- Select the Strategy you want to apply. For this example, choose
Ordered.
- Ordered
- Weighted—Distribute traffic across links according to a weighted bias, as determined by the configure cost.
- ECMP-- Equal-cost multipath; distributed traffic equally across multiple paths (for links with similar capacity and utilization)
- Click Add Paths to expose the Add Path drop-down.
- For Type, choose LAN
- For Name, choose dc1-servers.
- Click the blue checkmark in the corner of the panel to apply these settings.
- Click Save to add the policy to the list.
- Continue by adding the site variables for the remaining WAN using the information in the table.
Values for the Traffic Steering Policies in the WAN Edge template
Name | Field | Value | Paths | Value | Value |
dc1-servers | Strategy: | Ordered | |||
spoke-corp | Type: | LAN | |||
Network: | dc1-servers | ||||
Overlay | Strategy: | Weighted | |||
h1-wan0 | Type: | Overlay | |||
Name: | h1-wan0 | ||||
Cost: | 5 | ||||
h1-wan1 | Type: | Overlay | |||
Name: | h1-wan1 | ||||
Cost: | 5 | ||||
Underlay | Strategy: | Weighted | |||
wan0 | Type: | WAN | |||
Name: | wan0 | ||||
Cost: | 5 | ||||
wan1 | Type: | WAN | |||
Name: | wan1 | ||||
Cost: | 200 |