Detect Unstable Network Connections

Omnissa Horizon Client can monitor the network quality during remote sessions and display a notification message if it detects network instability due to high latency. The network latency is based on round-trip time (RTT) for TCP connections, and on RTT, packet loss, and RTT variation (RTTV) for BEAT and UDP connections.

You can use the Horizon Client settings to control the display of these notification messages. You can also configure the threshold parameters used by Horizon Client to identify unstable networks.

Configure the Display of Network Notifications

You can control the display of network notification messages using the Configure Omnissa Horizon Blast menu item.

1. Start Horizon Client.

2. Select File > Configure Horizon Blast from the menu bar.

   

3. Configure the display of notifications when the network is unstable.

   • To turn on network notifications, deselect the Disable network state display option. By default, this option is deselected to allow the display of notifications.
   • To turn off network notifications, select the Disable network state display option.

4. Click OK to save your changes.

How Horizon Client Determines the Network Quality

To determine the quality of a network connection, Horizon Client compares the network conditions during a specified time interval to a pair of low and high threshold values and calculates a quality score from 0 through 100 percent. If the score falls below a certain percentage, the network is deemed to be high-latency and unstable.

Horizon Client measures the following network conditions depending on the network protocol in use.

Horizon Client then uses the following rules to calculate the network quality score:

TCP Connections

Definitions:
rtt = detected RTT value
lowBound = RTT low threshold
highBound = RTT high threshold
score = overall network quality score

Rules:
If rtt >= highBound, then score = 0 (network is considered POOR)
If rtt <= lowBound, then score = 100 (network is considered GOOD)
If lowBound < rtt < highBound, then score = 100 * (rtt / (highBound - lowBound))

BEAT and UDP Connections

Definitions:
RTT = detected RTT value
RTT_extreme = RTT extreme threshold
RTT_lowBound = RTT low threshold
RTT_highBound = RTT high threshold
RTT_score = RTT quality score
RTT_weight_percentage = weight of RTT quality score

PkLoss = detected packet loss value
PkLoss_extreme = packet loss extreme threshold
PkLoss_lowBound = packet loss low threshold
PkLoss_highBound = packet loss high threshold
PkLoss_score = packet loss quality score
PkLoss_weight_percentage = weight of packet loss quality score


RTTV = detected RTT variation
RTTV_lowBound = low RTTV threshold
RTTV_highBound = high RTTV threshold
RTTV_score = RTTV quality score
RTTV_weight_percentage = weight of RTTV quality score

score = overall network quality score

Rules:
If RTT > RTT_extreme, then score = 0 (network is automatically considered POOR, all other calculations are skipped)
If RTT >= RTT_highBound, then RTT_score = 0
If RTT <= RTT_lowBound, then RTT_score = 100
If RTT_lowBound < RTT < RTT_highBound, then RTT_score = 100 * (rtt / (RTT_highBound - RTT_lowBound))

If PkLoss > PkLoss_extreme, then score = 0 (network is automatically considered POOR, all other calculations are skipped)
If PkLoss >= PkLoss_highBound, then PkLoss_score = 0
If PkLoss <= PkLoss_lowBound, then PkLoss_score = 100
If PkLoss_lowBound < PkLoss < PkLoss_highBound, then PkLoss_score = 100 * (PkLoss / (PkLoss_highBound - PkLoss_lowBound))

If RTTV >= RTTV_highBound, then RTTV_score = 0
If RTTV <= RTTV_lowBound, then RTTV_score = 100
If RTTV_lowBound < RTTV < RTTV_highBound, then RTTV_score = 100 * (RTTV / (RTTV_highBound - RTTV_lowBound))

To calculate the overall score, take the weighted average of the three quality scores:
score = RTT_score * RTT_weight_percentage / 100 +
        PkLoss_score * PkLoss_weight_percentage / 100 +
        RTTV_score * RTTV_weight_percentage / 100

Horizon Client then uses the following rules to determine the network stability:

Definitions:
score = overall network quality score
thresholdGood = minimum score indicating GOOD network stability
thresholdPoor = high limit of score range indicating POOR network stability

Rules:
If score >= thresholdGood, the network is considered GOOD and no notification is displayed.
If thresholdPoor < score < thresholdGood, the network is considered OK and no notification is displayed.
If score <= thresholdPoor, the network is considered POOR and a notification is displayed.

Configure Threshold Parameters for Network Quality

To customize the threshold parameters used by Horizon Client to calculate the network quality score and determine network stability, configure the keys in one of the configuration files.

1. Global settings
2. User preferences
3. User default config
4. Host defaults config
5. Site defaults

Horizon Client searches through the configuration files in the listed order and stops as soon as it finds a key with a configured value.

Note: Use caution when changing the defaults for these configuration keys. The default threshold values were determined through extensive internal testing and are designed to produce reasonable results for typical network environments.