Link Search Menu Expand Document

Application Definitions

Configuration > Templates & Policies > Applications & SaaS > Application Definitions

This tab provides application visibility and control.

  • You can search to determine whether a definition exists for a specific application and, if so, how it is defined.

  • You can set AppExpress performance monitoring for specific applications.

  • You can monitor up to 50 applications.

  • To filter the application definition list to show only monitored applications, click the Monitored button in the tab header. Click All to remove the filter.

Orchestrator uses the following eight dimensions to identify and define applications:

  • IP Protocol

  • UDP Port

  • TCP Port

  • Domain Name

  • Address Map – (Formerly known as IP Intelligence). Given a range of IP addresses, the Address Map reveals the organization that owns the segment, along with the country of origin.

  • DPI – Deep Packet Inspection. An expanded list of Orchestrator legacy built-in applications.

  • Compound – Created by user from multiple criteria.

  • SaaS – Created by user. If any components of the definition change, the user must manually update the definition.

You can use any of these dimensions to define a new application, and you can modify or disable an existing application.

Orchestrator automatically checks the Cloud Portal for updated application definitions every 24 hours by default (Auto update set to ON). Application definition data on the Cloud Portal is updated generally once per month. If new definitions are discovered, Orchestrator downloads the data, merges it with the applications, and pushes the changes to appliances in the network. You can also force an update at any time by clicking the Update Now button.

Enabling AppExpress for an Application

You can enable AppExpress performance monitoring for any application. If you choose to have AppExpress steer traffic for an application, you must enable steering and it must be added to an AppExpress group. For more information, see AppExpress Groups Tab.

  1. Navigate to Configuration > Templates & Policies > Applications & SaaS > Application Definitions.

  2. Click Show Advanced App Definitions.

  3. Locate the application in the advanced definitions list and click the edit icon.

    The Application Definition dialog box opens.

  4. Enter information in the following fields based on the level of monitoring you want to apply to the application:

    Field Description
    AppExpress Off – Click to disable AppExpress for the application.

    Monitor only – Click to enable only AppExpress monitoring for the application. Data is collected about the performance of the application, which is reflected on the AppExpress Summary tab and in reports, but the data is not used to steer the application traffic.

    Monitor and Steer – Click to enable AppExpress monitoring and steering for the application. Data is collected about the performance of the application, which the system uses to steer the application traffic from one transport to another.

    The application must be added to an AppExpress group for traffic steering to occur. For more information, see AppExpress Groups Tab.
    Use Cloud Portal Config Select this check box to use the Aruba-provided AppExpress settings for this application.

    NOTE: Not all applications have Aruba-provided AppExpress settings. You can override these settings at any time.
    Ping Type Select the method used to send probes to the application across the loopback interface. Options include ICMP echo-request/response, TCP connect, HTTP, or HTTPS.

    NOTE: TCP is the default selection and recommended for most AppExpress applications.
    Ping Hostname Enter the hostname or IP address of the server from which the probes originate.
    User Experience Thresholds Enter the two threshold values (in milliseconds) for the application performance. These values are measures of latency and are what the Target QoE is derived from. The defaults are 100 ms for the threshold between Satisfied and Tolerable, and 300 ms for the threshold between Tolerable and Frustrated. When determining the threshold values, keep the following definitions in mind:

    Satisfied – If latency for the application is at or below this threshold, users will have the best experience with the application.

    Tolerable – If latency for the application falls in this range, users will have a tolerable experience with the application, but it could be better.

    Frustrated – If latency for the application falls at or above this threshold, users may have a negative experience with the application.
  5. Click Apply to save your changes. The dialog box closes, and the Performance Monitor column shows “Yes” for the application.

Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.

Open Source Code:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America