Adding application groups

For easier configuration, you can use host labels instead of local and remote subnets and port labels instead of TCP/UDP port numbers.

In addition to criteria matching on the IP-header based characteristics or the VLAN ID, you can use the AFE to let RiOS automatically detect the application. See the description of the Application Layer Protocol control in the table for details.

Specifies an IP address and mask for the traffic source, or you can specify all or 0.0.0.0/0 as the wildcard for all traffic.

Use this format: xxx.xxx.xxx.xxx/xx

Specify a host label. You predefine host labels under Networking > App Definitions: Host Labels.

Specifies all source ports, a single source port value or a port range of port1-port2, where port1 must be less than port2. The default setting is all ports.

Specify a port label. You predefine port labels under Networking > App Definitions: Port Labels.

Specifies an IP address and mask pattern for the traffic destination, or you can specify all or 0.0.0.0/0 as the wildcard for all traffic.

Use this format: xxx.xxx.xxx.xxx/xx

Specify a host label. You predefine host labels under Networking > App Definitions: Host Labels.

Specifies a transport layer protocol from the drop-down list. The default setting is All.

Specifies an application layer protocol or an application signature. To specify an application signature, type the first letters of the application. For example, if you want to create specific criteria to identify Facebook traffic, type the first three letters and select a Facebook application from the drop-down menu.

Specifies all destination ports, a single source port value or a port range of port1-port2, where port1 must be less than port2. The default setting is all ports.

Specify a port label. You predefine port labels under Networking > App Definitions: Port Labels.

Specifies a VLAN tag as follows:

RiOS supports VLAN v802.1Q. To configure VLAN tagging, configure transport rules to apply to all VLANs or to a specific VLAN. By default, rules apply to all VLAN values unless you specify a particular VLAN ID. Pass-through traffic maintains any preexisting VLAN tagging between the LAN and WAN interfaces.

Specifies a DSCP value from 0 to 63, or all to use all DSCP values.

Specifies Optimized, Passthrough, or All from the drop-down list. The default setting is All.

Specifies an application group for the application from the drop-down list (highest priority to lowest):

• Business Bulk—Captures business-level file transfer applications and protocols, such as CIFS, SCCM, antivirus updates, and over-the-network backup protocols.

• Business Critical—Captures business-level, low-latency transactional applications and protocols, such as SQL, SAP, Oracle and other database protocols, DHCP, LDAP, RADIUS, the Riverbed Control Channel (to identify and specify a DSCP value for out-of-band traffic), routing, and other network communication protocols.

• Business Productivity—Captures general business-level productivity applications and protocols, such as email, messaging, streaming and broadcast audio/video, collaboration, intranet HTTP traffic, and business cloud services O365, Google apps, SFDC, and others through a white list.

• Business Standard—Captures all intranetwork traffic going within local subnets as defined by the uplinks on the SteelHead. Use this class to define the default path for traffic not classified by other application groups.

• Business VDI—Captures real-time interactive business-level virtual desktop interface (VDI) protocols, such as PC over IP (PCoIP), Citrix CGP and ICA, RDP, VNC, and Telnet protocols.

• Business Video—Captures business-level video conferencing applications and protocols, such as Microsoft Lync and RTP video.

• Business Voice—Captures business-level voice over IP (VoIP) applications and protocols (signaling and bearer), such as Microsoft Lync, RTP, H.323 and SIP.

• Recreational—Captures all internet-bound traffic that has not already been classified and processed by other application groups.

• Standard Bulk—Captures general file transfer protocols, such as FTP, torrents, NNTP/usenet, and online file hosting services Dropbox, Box.net, iCloud, MegaUpload, Rapidshare, and others.

• Custom Applications—Captures user-defined applications that have not been classified into another application group.

Specifies a category for the application from the drop-down list.

Specifies a service class for the application from the drop-down list:

• Low Criticality—Specifies a low-priority service class: for example, FTP, backup, replication, other high-throughput data transfers, and recreational applications such as audio file sharing.

These are minimum service class guarantees; if better service is available, it’s provided. For example, if an application is specified as low priority and the higher-priority classes aren’t active, then the low-priority class receives the highest possible available priority for the current traffic conditions. This parameter controls the priority of the application relative to the other applications.

The service class describes only the delay sensitivity of a class, not how much bandwidth it’s allocated, nor how important the traffic is compared to other classes. Typically you configure low priority for high-throughput, non-packet delay sensitive applications like FTP, backup, and replication.