Deployment configurations

Deployment considerations

Deployment considerations

Maximum number of protected flows

HP Velocity supports a range of 16 to 1024 simultaneously protected flows.

The minimum supported protected flows are:

•16 for HP thin clients

•16 for virtual desktops

•256 terminal services servers

HP Velocity defaults to the minimum supported simultaneous flows. If the default setting is changed, the system must be rebooted for the change to take effect.

NOTE: HP Velocity server-to-server flows are only monitored, not protected. Only flows between a server enabled with HP Velocity and an HP thin client are protected.

NOTE: LiveTCP will provide latency mitigation for up to 32 simultaneous protected flows.

About HP Velocity beacons

HP Velocity advertises its presence in a non-intrusive way by modifying IP and TCP headers in compliance with International Engineering Task Force (IETF) standards.

If either IP or TCP Option beacons are enabled, HP Velocity will add up to 4 bytes of data to the IP or TCP headers. This is in compliance with RFC 791 and RFC 793. Some applications might not be compliant with RFC 791 or RFC 793, and as a result might not be able to process IP or TCP Option beacons. If this occurs, disabling IP and/or TCP Option beacons should resolve the issue.

For more information on configuring beacons, see the HP Velocity User Guide.

NOTE: HP Velocity beacons are:

IP Option - 0x880477FB (UDP Flows)

TCP Option - 0x010000000000000000 (TCP Flows)

HP Velocity Server Side Deployment Guide

16