HP Velocity FAQ

General

What is an HP Velocity-monitored flow?

A monitored flow is formed between two HP Velocity endpoints in Monitor mode. In this mode, HP Velocity continuously monitors end-to-end network conditions but does not activate or adjust HP Velocity optimizers, such as zero-latency loss protection, WiFi acceleration, TCP flow control, and latency mitigation.

What is the maximum number of supported HP Velocity flows?

HP Velocity supports simultaneously protected flows as follows:

•An HP thin client supports 16 to 1024 simultaneously protected flows.

•HP Velocity installed on a virtual desktop supports 16 to 1024 simultaneously protected flows with one or more HP thin clients.

•HP Velocity installed on a terminal services server supports 256 to 1024 simultaneously protected flows with one or more HP thin clients.

HP Velocity defaults to the minimum number of supported simultaneous sessions. If the default setting is changed, reboot the system for the change to take effect.

What is the purpose of policy filters?

The policy filters define which data flows to protect and the level of protection to apply, based on the configured IP addresses and ports. For more information, see the “Policy Filters” section of the HP Velocity Server Side Deployment Guide.

What is the LiveQ - Packet Loss Protection Optimizer?

HP Velocity provides zero-latency loss protection from end-to-end packet loss. HP Velocity protects application flows from packet loss by automatically adapting the amount of added redundancy.

What is the LiveTCP - Flow Control Optimizer?

HP Velocity improves the throughput of applications like multimedia streaming and remote desktop access by modifying TCP flow control mechanisms to perform better in WiFi environments.

What is LiveTCP - Latency Mitigation?

HP Velocity optimizes TCP throughput over all networks and provides latency mitigation for RDP, RGS, and ICA protocols. HP Velocity optimizes the throughput of applications like

HP Velocity FAQ and Troubleshooting Guide

9