Where Do I Start?

Network topology and application definitions form the reusable building blocks that allow you to inspect and direct network traffic using the QoS, path selection, and web proxy features. On an SCC, you can protect network traffic by reusing these building blocks with the secure transport feature. In addition, the application statistics collector in the SCC provides visibility into the throughput data for optimized and passthrough traffic flowing in and out of the SteelHeads in your network. For details, see the SteelCentral Controller for SteelHead User’s Guide.

Task	Notes	For Detailed Instructions
1. Define applications	Attach a business relevancy to all traffic that goes through your network. Application definitions enable you to prioritize traffic with QoS and steer traffic down a particular path with path selection. Use the preexisting default definitions to identify applications. If the application doesn’t appear in the preexisting application list, you can define a custom application.	Defining Applications
2. Configure QoS profiles	• Define the QoS profiles by creating classes and rules. • The classes specify the traffic hierarchy, priority, and the minimum and maximum bandwidth the class will use for shaping. • The rules can use application definitions and application groups.	Creating QoS Profiles
3. Define a view of all available networks	Choose Networking > Topology: Sites & Networks On a SteelHead, the network definition is simply a name: for example, MPLS.	Defining a Network
4. Define sites	Choose Networking > Topology: Sites & Networks Sites provide the SteelHead with the IP addresses of all existing subnets (including nonSteelHead sites). It’s important to define all remote subnets in the enterprise so they can be matched with the correct QoS profile rules. You must define local and remote sites and local gateways. You also need to define the default site to provide a catch all for traffic not assigned to another site.	Defining a Site
5. Assign the QoS profiles created in Step 2 to sites	Choose Networking > Topology: Sites and Networks, click Edit Site, select an inbound or outbound QoS profile from the drop-down list, and click Save. Assign one profile per site. You can’t assign a profile to a network.
6. Enable QoS	Choose Networking > Network Services: Quality of Service	To enable QoS

Task	Notes	For Detailed Instructions
1. Define applications	Attach a business relevancy to all traffic that goes through your network. Use the preexisting default definitions to identify applications. If the application doesn’t appear in the preexisting application list, you can define a custom application.	Defining Applications
2. Define a view of all available networks	Choose Networking > Topology: Sites & Networks The network definition is simply a name: for example, MPLS.	Topology Properties Defining a Network
3. Define sites	Choose Networking > Topology: Sites & Networks Provides the SteelHead with the IP addresses of all subnets existing within a site (this applies to nonSteelHead sites as well). It’s important to define all remote subnets in the enterprise so they can be matched with the correct rules. You must define local and remote sites. The site definitions include a list of IP subnets that path selection will use to identify the site. Every subnet must be globally unique, although they can overlap. You also need to define the default site that provides a catch all for traffic not assigned to another site. Specify the SteelHead peers to use for path monitoring. SteelHead peers are select distinct IP addresses you choose to poll, in order, to verify path availability.	Defining a Site
4. Define uplinks that join the sites to the networks	Choose Networking > Topology: Sites & Networks You must define the local site with the gateway IP address and the inpath interface the uplinks will use to connect to the network. On the SteelHead you are configuring, the local default gateway is the inpath interface. If the default gateway is pointing to the LAN side, you need to change the interface because when you configure path selection, We recommend that the gateway to a network points to the WAN side of the SteelHead to avoid packet ricochet. The order isn’t important because the longest prefix on the site subnet is matched first.	Defining Uplinks
5. Enable path selection	Choose Network > Network Services: Path Selection and select Enable Path Selection.
6. Configure path selection rules	Path Selection rules direct matching traffic onto specific uplinks. Traffic is matched by a combination of application and destination site.	To configure path selection