Managing Your Network : Managing Appliances : Managing Appliance Pages : Managing Path Selection
  
Managing Path Selection
You configure legacy path selection rules in the Editing Appliance Configuration: <hostname>, Path Selection page.
Important: You cannot migrate your previously defined path selection rules to SCC 9.0 or later.
SCC 9.0 and later do not support path selection-policy pushes for SteelHead 8.0, 9.0.x or later or SteelHead EX 2.0 and 3.6.x or later. If you are running this version of the software on your remote appliance, you must create a new set of path selection rules based on sites, networks, and uplinks to apply to simplified QoS or secure transport. For details about creating sites, networks, and uplinks, see Managing Interceptor Clusters. For details about configuration path selection in the SCC, see Managing Path Selection.
This page applies to SteelHead and SteelHead EX.
To add a new path
1. Choose Manage > Topology: Appliances to display the Appliances page.
2. Select the name of the appliance you want to edit to display the Edit Appliance tab.
3. Select the Appliance Pages tab to display the Appliance Configuration Pages list.
4. Under Appliance Configuration Pages, click Path Selection to display the Editing Appliance Configuration: <hostname>, Path Selection page.
5. Click + Add a New Path to expand the page.
Figure: Configuring Legacy Path Selection Rules
6. Complete the configuration as described in this table.
Control
Description
Name
Specify the path selection name.
Note: The path selection name is case sensitive and must match the path name in the policy being pushed to this appliance. If the names do not match, policy push will fail.
Gateway IP Address
Specify the IP address for the gateway. The gateway must be in the same network as the in-path interface.
Note: The gateway IP address must be in the same subnet (local network) as the in-path interface.
Interface
Select a relay interface over which the appliance reaches the path.
Tunnel Mode
Select the tunnel mode from the drop-down list: None or GRE.
GRE provides IPv4 generic routing encapsulation (GRE) for direct uplinks. Direct uplinks using GRE become direct tunneled uplinks. You must create direct tunneled uplinks to steer traffic over any uplink that traverses a stateful firewall between the SteelHeads.
Without GRE, traffic attempting to switch midstream to an uplink that traverses a stateful firewall might be blocked. The firewall needs to track the TCP connection state and sequence numbers for security reasons. Because the firewall has not logged the initial connection handshake, and has partial or no packet sequence numbers, it blocks the attempt to switch to the secondary uplink and might drop these packets. To traverse the firewall, path selection can encapsulate that traffic into a GRE tunnel.
Add
Adds the path to the path table. The SCC redisplays the path table and applies your changes to the running configuration, that is stored in memory.
Remove Selected
Select the check box next to the name and click Remove Selected.