Product Documentation

Use Cases: HDX Insight

Aug 19, 2016

HDX Insight provides end-to end visibility for ICA traffic passing through NetScaler ADC.

HDX Insight enables administrators to view real-time client and network latency metrics, historical reports, End-to-end performance data, and troubleshoot performance issues.

Availability of both real-time and historical visibility data enables NetScaler Insight Center to support a wide variety of use cases.

The following Thin Clients support HDX Insight for NetScaler Insight Center release 11.0 build 65.35 and later:

  • WYSE Windows based Thin Clients
  • WYSE Linux based Thin Clients
  • WYSE ThinOS based Thin Clients
  • 10Zig Ubuntu based Thin Clients

This document includes the following details:

Identifying the root cause of slow performance issues

Scenario 1

User is experiencing delays while accessing XenApp and XenDesktop.

The delays might be due to latency on the server network, ICA traffic delays caused by the server network, or latency on the client network.

To identify the root cause of the issue, analyze the following metrics:
  • WAN Latency
  • DC Latency
  • Host Delay
To view the client metrics
  1. On the Dashboard tab, navigate to HDX Insight > Users.
  2. Scroll down and select the user name.
  3. On the Current Application Sessions table, hover the mouse over the RTT value and note the host delay, DC latency, and WAN latency values.

On the Current Application Sessions table, click the hop diagram symbol to display information about the connection between the client and the server, including latency values.

Figure 1. Current Application Session
localized image

Summary

In this example, the DC Latency is 1 millisecond, the WAN latency is 592 milliseconds and Host Delays is 0 seconds.

This indicates that the user is experiencing delay due to latency caused by the client network.

Scenario 2

User is experiencing delay while launching an application on XenDesktop or XenApp

The delay might be due to latency on the server network, ICA-traffic delays caused by the server network, latency on the client network, or time taken to launch an application.

To identify the root cause of the issue, analyze the following metrics:

  • WAN latency
  • DC Latency
  • Application Launch Duration

To view the user metrics

  1. On the Dashboard navigate to HDX Insight> Users.
  2. Scroll down and click on the user name.
  3. In the graphical representation, note the WAN Latency, DC Latency and RTT values for the particular session.
  4. In the Current Application Sessions table, click the first session ID.
  5. Scroll down, and in the Applications pane, from the dropdown list, select Launch Duration to view the time taken for the application to launch.
localized image

Summary

In this example, the DC Latency is 1 millisecond, the WAN latency is 13 milliseconds, and the Launch Duration value of 2.37 seconds. This indicates that the cause for the delay in launching the application is high application launch time.

Geo Maps for HDX Insight

The NetScaler Insight Center geo maps functionality displays the usage of applications across different geographical locations on a map. Administrators can use this information to understand the trends in application usage across various geographical locations.

You can configure NetScaler Insight Center to display the geo maps for a particular geographical location or LAN by specifying the private IP range (start and end IP address) for the location.

To configure a geo map for private IP block

On the Configuration tab, navigate to NetScaler Insight Center > Private IP Block to configure geo maps for a particular location.

Use Case

Consider a scenario in which organization ABC has 2 branch offices, one in Santa Clara and the other in India.

The Santa Clara users use the NetScaler Gateway appliance at SClara.x.com to access VPN traffic. The Indian users use the NetScaler Gateway appliance at India.x.com to access VPN traffic.

During a particular time interval, say 10 AM to 5 PM, the users in Santa Clara connect to SClara.x.com to access VPN traffic. Most of the users access the same NetScaler Gateway, causing a delay in connecting to the VPN, so some users connect to India.x.com instead of SClara.x.com.

A NetScaler administrator analyzing the traffic can use the geo map functionality to show the traffic in Santa Clara office. The map shows that the response time in the Santa Clara office is very high, because the Santa Clara office has only one NetScaler Gateway appliance through which users can access VPN traffic. The administrator might therefore decide to install another NetScaler Gateway, so that users have two local NetScaler Gateway appliances through which to access the VPN.