HP Velocity Version 2.1.0

HP Velocity Version 2.1.0
Administrator Guide
HP Velocity
Version 2.1.0
Copyright © 2015 LiveQoS Incorporated All Rights Reserved
Microsoft, Windows, and Windows Server are trademarks of the Microsoft group of companies.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.
Second Edition: February 2015
First Edition: January 2015
Document Part Number: 804968-002
Table of contents
HP Velocity functional overview ......................................................................................................................................1
Establishing a connection .............................................................................................................................................1
Initialization.................................................................................................................................................................1
Beaconing....................................................................................................................................................................1
Handshaking ...............................................................................................................................................................2
Protected state...........................................................................................................................................................2
HP Velocity Server Side deployments for thin clients ..................................................................................................3
Direct deployment .........................................................................................................................................................3
Proxied deployment ......................................................................................................................................................4
Direct-and-proxied deployment..................................................................................................................................4
Terminal services deployment.....................................................................................................................................4
HP Velocity installation......................................................................................................................................................5
HP Velocity Server Side system requirements..........................................................................................................5
Installing HP Velocity Server Side................................................................................................................................6
HP Velocity operation on Windows .................................................................................................................................7
HP Velocity operational modes....................................................................................................................................7
Setting the HP Velocity operational mode on Windows ..........................................................................................8
Identifying the HP Velocity version on Windows.......................................................................................................8
HP Velocity configuration..................................................................................................................................................9
HP Velocity policy engine ..............................................................................................................................................9
Adding an HP Velocity administrative template to a GPO...................................................................................9
Configuring HP Velocity using the Group Policy Object .......................................................................................9
HP Velocity configuration settings ........................................................................................................................... 10
Management Application Mode ............................................................................................................................ 10
System settings....................................................................................................................................................... 11
Boot settings............................................................................................................................................................ 14
Policy filter (port & IP) settings ............................................................................................................................. 15
LiveQ settings .......................................................................................................................................................... 16
LiveTCP settings ...................................................................................................................................................... 18
Logging settings...................................................................................................................................................... 19
HP Velocity account privileges .................................................................................................................................. 21
HP Velocity management .............................................................................................................................................. 22
Network statistics ....................................................................................................................................................... 22
Network Statistics operations............................................................................................................................... 24
Network Monitor graph .............................................................................................................................................. 25
Flow information ......................................................................................................................................................... 26
Latency and throughput data ............................................................................................................................... 27
Flow Information operations ................................................................................................................................ 28
Network loss simulation ............................................................................................................................................ 28
Configuration settings ................................................................................................................................................ 29
Restoring default configuration settings ............................................................................................................ 30
Generating the HP Velocity configuration report............................................................................................... 30
FAQs................................................................................................................................................................................... 32
All HP Velocity application flows are blocked......................................................................................................... 32
Traffic between HP Velocity servers is only monitored........................................................................................ 32
Protected flows are not established........................................................................................................................ 32
TCP-based VPNs are not protected ......................................................................................................................... 32
Decision trees................................................................................................................................................................... 33
VDI connectivity issue ................................................................................................................................................. 33
Non-VDI connectivity issue ........................................................................................................................................ 34
HP Velocity-protected flows not established......................................................................................................... 35
Quality of Experience: Packet-loss issue ................................................................................................................ 36
Quality of Experience: Latency issue ....................................................................................................................... 37
Appendix: HP Velocity configuration on HP ThinPro ................................................................................................. 38
Changing the value of a configuration parameter................................................................................................. 38
about ............................................................................................................................................................................. 38
system .......................................................................................................................................................................... 39
boot ............................................................................................................................................................................... 40
core................................................................................................................................................................................ 40
filters/filters ................................................................................................................................................................. 41
filters/liveq ................................................................................................................................................................... 42
liveq ............................................................................................................................................................................... 43
simulator ...................................................................................................................................................................... 44
Administrator Guide | HP Velocity
HP Velocity functional overview
Real-time applications delivered over data networks can be compromised by packet loss and transmission latency. This
results in stop-and-go behavior, loss of interactivity, and an overall reduction in the throughput of an application.
HP Velocity is a Quality of Service (QoS) software engine that integrates seamlessly and, when protecting application
flows, enhances Quality of Experience (QoE) by managing packet loss, congestion, and the impact of network latency.
Establishing a connection
An HP Velocity-protected connection is established over four steps:
• Initialization
• Beaconing
• Handshaking
• Protected state
Figure 1: Establishing a connection
Initialization
During initialization, HP Velocity-enabled endpoints start streaming data transparently. No optimizations are performed.
Beaconing
After an HP Velocity-enabled endpoint detects that a bidirectional network path is available, it periodically and
seamlessly modifies IP and TCP packet headers (which can contain options-based beacons) to advertise itself to other
HP Velocity-enabled endpoints (Figure 2 on page 2).
After an HP Velocity-enabled endpoint processes enough beacons on a network flow to discover that another
HP Velocity-enabled endpoint is at the other end, handshaking occurs.
Note: The use of TCP option-based beacons for TCP flows and IP option-based beacons for UDP flows is a configurable
system setting. For information, see System settings on page 11.
1
Administrator Guide | HP Velocity
Figure 2: Beaconing
Handshaking
An HP Velocity-enabled endpoint initiates a three-way handshaking procedure with another HP Velocity-enabled
endpoint discovered during beaconing. When the handshake is completed, both HP Velocity-enabled endpoints enter the
protected state.
Protected state
In the protected state, HP Velocity-enabled endpoints exchange information about current and trending network
conditions. This information is then used to intelligently activate and adjust HP Velocity network optimizers.
2
Administrator Guide | HP Velocity
HP Velocity Server Side deployments for thin clients
HP Velocity Server Side deployments vary based on the virtualization architecture in use. Use the following table to
determine where to install HP Velocity Server Side.
Virtualization architecture
HP thin clients are directly connected to virtual desktops or applications.
Direct deployment on page 3
HP thin clients use a connection broker as a proxy to access virtual desktops or
applications.
Proxied deployment on page 4
The virtualization environment supports both direct and proxied connections to
virtual desktops and applications.
Direct-and-proxied deployment on page 4
HP thin clients connect to a terminal services server.
Terminal services deployment on page 4
Note: HP Velocity Server Side is supported on Windows operating systems only.
Direct deployment
Virtualization architectures that allow an HP thin client to connect directly to a virtual desktop must have HP Velocity
Server Side installed on the virtual desktop. In this deployment, a connection broker does not act as a proxy.
In Figure 3 on page 3, thin clients A and B are directly connected to their respective virtual desktops A and B.
Figure 3: Example of a direct deployment
3
Administrator Guide | HP Velocity
Proxied deployment
For virtualization architectures that require an HP thin client to access a virtual desktop via a proxy service provided by a
connection broker (such as VMware View Manager), HP Velocity Server Side must be installed on the connection broker.
In Figure 4 on page 4, thin clients A and B are connected to their respective virtual desktops via the connection broker.
HP Velocity Server Side is installed on the connection broker. This results in HP Velocity-protected flows between the thin
clients and the connection broker.
Figure 4: Example of a proxied deployment
Note: Additional configuration is not required after HP Velocity Server Side is installed on the connection broker.
Direct-and-proxied deployment
Some virtualization architectures allow both direct and proxied access to virtual desktops. In this type of deployment,
HP Velocity Server Side must be installed on the following:
• Virtual desktops that are accessed directly
• Connection brokers that provide a proxy service to access the virtual desktop
In Figure 5 on page 4, thin client A connects to virtual desktop A through the connection broker, and thin client B connects
to virtual desktop B directly.
Figure 5: Example of a direct-and-proxied deployment
Terminal services deployment
In a terminal services deployment, multiple HP thin clients are connected to a terminal services server, such as a
Windows Server. In this type of deployment, HP Velocity Server Side must be installed on the terminal services server
(Figure 6 on page 4).
Figure 6: Example of a terminal services deployment
4
Administrator Guide | HP Velocity
HP Velocity installation
This section provides information about installing HP Velocity Server Side and covers the following information:
• HP Velocity Server Side system requirements
• Installing HP Velocity Server Side
Note: HP Velocity is preinstalled on HP thin clients. Updates might be available as an add-on. For more information, go
to http://www.hp.com/go/velocity.
HP Velocity Server Side system requirements
Table 1: HP Velocity Server Side system requirements
Component
Server operating system
Virtual desktop operating system
CPU
Any
Any
Memory
40 MB
3 MB
Disk space
10 MB
10 MB
Operating system
Windows Server 2012
Windows Server 2008
Windows Server 2003
Windows 8 and later
Windows 7
Operating-system variants
32-bit and 64-bit
Clients
HP thin clients
Note: Memory requirements are proportional to the number of simultaneously protected flows supported by
HP Velocity.
Note: HP Velocity Server Side is not supported on Linux operating systems.
5
Administrator Guide | HP Velocity
Installing HP Velocity Server Side
HP Velocity Server Side installs as a network driver on the following platforms:
• Virtual desktop
• Host operating system of Microsoft Terminal Services
• Microsoft Hyper-V server
Note: During installation, HP Velocity resets the system’s network interfaces, briefly interrupting network connections. If
HP Velocity is installed over a remote connection, network connectivity might be disrupted.
Note: HP Remote Graphics Software (RGS) 6.0 and later include HP Velocity. If RGS 6.x is already installed on the system
and a message is displayed stating that another version of HP Velocity is already installed, uninstall RGS, install HP
Velocity, and then reinstall RGS. RGS 7.x and later do not require these steps. If you want to use HP Velocity for the RGS
protocol only, see the HP Remote Graphics Software User Guide for instructions on installing and enabling the HP Velocity
functionality included with RGS instead of installing the standalone HP Velocity components.
1.
Log on to the system where HP Velocity Server Side will be installed.
Note: Only users with Windows Administrator privileges can install HP Velocity Server Side.
2.
Select the correct installation package for the operating system and architecture, and start the installer.
Important: See the Release Notes to ensure that the correct installation package is available and selected for
installation.
The Welcome to the HP Velocity Setup Wizard starts.
3.
Click Next.
The License Agreement appears.
4.
Read the end-user license agreement, select I Agree, and click Next.
Note: Selecting Cancel ends the installation.
5.
Navigate to the location where HP Velocity will be installed, or accept the default location.
6.
Enable one of the following radio buttons:
• Everyone—Installs HP Velocity for all user accounts and administrators
• Just Me—Installs HP Velocity for only the current user account
7.
Click Next.
The Confirm Installation screen appears.
8.
Click Next to confirm the selections and begin the installation.
The following message might appear during the installation:
Do you want to allow the following program from an unknown publisher to make
changes to your system?
If this message appears, select the option to allow the changes to take place.
The Installation Complete screen appears when the installation completes.
9.
Click Close.
The HP Velocity icon appears on the taskbar (see HP Velocity operational modes on page 7).
6
Administrator Guide | HP Velocity
HP Velocity operation on Windows
This section covers the following information:
• HP Velocity operational modes
• Setting the HP Velocity operational mode on Windows
• Identifying the HP Velocity version on Windows
For information about setting the HP Velocity operational mode and identifying the HP Velocity version on HP ThinPro,
see Appendix: HP Velocity configuration on HP ThinPro on page 38.
HP Velocity operational modes
The HP Velocity icon appears on the taskbar in one of four colors that correspond to the HP Velocity operational modes
(Table 2 on page 7).
Figure 7: HP Velocity icon on Windows
Table 2: HP Velocity icon color codes
Icon color
Mode
Description
Green
Protect
HP Velocity is enabled and is protecting one or more flows between HP Velocity-enabled
endpoints. In this mode, HP Velocity continuously monitors end-to-end network conditions to
activate and adjust enabled HP Velocity optimizers (such as LiveQ packet loss protection, LiveWiFi,
and LiveTCP latency mitigation).
Blue
Protect
HP Velocity is enabled and ready to protect, but flows have not been established.
Orange
Monitor
HP Velocity is profiling present and trending network conditions but will not apply enabled
HP Velocity optimizers.
Note: HP Velocity server-to-server flows are monitored only.
Gray
Off
HP Velocity is disabled.
Note: On Windows platforms, positioning the cursor over the HP Velocity icon when HP Velocity is in Protect mode
displays a tooltip indicating the number of active connections.
7
Administrator Guide | HP Velocity
Setting the HP Velocity operational mode on Windows
Once set, the HP Velocity operational mode should be changed at the following times only:
• During troubleshooting (to set the operational mode to Off)
• After troubleshooting (to set the operational mode to Protect)
• When instructed by HP Support
Note: Only users with administrator privileges can set the HP Velocity operational mode.
1.
Click the HP Velocity icon (see Figure 7 on page 7) on the taskbar.
2.
On the HP Velocity Mode selector, enable the radio button for the desired operational mode.
3.
Click Close.
The color of the HP Velocity icon changes to reflect the selected operational mode (see Table 2 on page 7).
Identifying the HP Velocity version on Windows
• Right-click the HP Velocity icon, and then click About.
The About HP Velocity dialog appears, displaying the HP Velocity version number, release number, product edition
information (Server or Client), and license restriction mode [Restricted (R) or Unrestricted (U)].
8
Administrator Guide | HP Velocity
HP Velocity configuration
HP Velocity is installed with a default configuration suitable for most deployments. This section provides information
about using the HP Velocity Policy Engine to create a custom configuration on a supported Windows platform and covers
the following information:
• HP Velocity policy engine
• HP Velocity configuration settings
• HP Velocity account privileges
For information about configuring HP Velocity on HP ThinPro, see Appendix: HP Velocity configuration on HP ThinPro
on page 38.
Note: For information about accessing a report that describes the current configuration, see Generating the HP Velocity
configuration report on page 30. For information about specifying configuration settings that apply only until a system
restart, see HP Velocity management on page 22.
HP Velocity policy engine
The HP Velocity policy engine uses Microsoft Group Policy, which provides centralized management and configuration of
users and computers in a Windows Active Directory (AD) environment.
Group policy settings are contained in a group policy object (GPO), which can be used to centrally manage and propagate
new settings for HP Velocity over an entire Windows AD domain. The GPO manages settings for both HP Velocity Server
Side and HP Velocity Thin Client.
To create a GPO, use the Group Policy Management Console (GPMC), which is available for download from the Microsoft
Download Center Web site. After the GPO is created, add an HP Velocity administrative template to it (see Adding an
HP Velocity administrative template to a GPO on page 9).
Each HP Velocity administrative template consists of policies that allow administrators to create a custom configuration
for HP Velocity (see Configuring HP Velocity using the Group Policy Object on page 9). They also specify which registry
keys are set when a custom configuration is created.
Adding an HP Velocity administrative template to a GPO
Note: The HP Velocity administrative template is included with the HP Velocity (Server Side or Thin Client) installation
package available at http://www.hp.com/go/velocity.
1.
Open the applicable Group Policy Editor:
• For local group policy administration, use gpedit.msc.
• For domain group policy administration, use gpmc.msc and select the applicable GPO.
2.
Click Computer Configuration.
3.
Right-click Administrative Templates, and then click Add/Remove Templates.
4.
Click Add.
5.
Browse to and select hp_velocity_configuration_REL#-R#.adm, where REL# is the software release
number and R# is the revision number that matches the release number of the HP Velocity Server Side or HP Velocity
Thin Client installation package.
The HP Velocity administrative template is applied to the GPO.
6.
Click Close.
Configuring HP Velocity using the Group Policy Object
Changes made to the default configuration using the Group Policy Object are applied immediately to HP Velocity
endpoints on which the HP Velocity Management application is running. If the HP Velocity Management application is not
running, changes are applied to those endpoints after a system reboot. For information about the HP Velocity
Management application, see HP Velocity management on page 22.
9
Administrator Guide | HP Velocity
Note: HP recommends that HP Velocity settings be changed on all systems in an organizational unit (OU). This ensures
that all installations in the OU use the same settings.
Note: You must have Administrator privileges to configure HP Velocity. For information, see HP Velocity account
privileges on page 21.
1.
Open the GPO in the Group Policy Editor.
2.
Click Computer Configuration > Administrative Templates.
3.
Click Classic Administrative Templates (ADM) > HP Velocity.
4.
In the Setting list, double-click a configuration setting.
5.
Specify the parameters as required (see HP Velocity configuration settings on page 10), and click Apply.
6.
Click Next Setting or Previous Setting to access the parameters for another configuration setting, or click Close to
close the template.
HP Velocity configuration settings
The HP Velocity Server Side and HP Velocity Thin Client administrative templates provide access to configuration
parameters for the following settings, which can be modified to create a custom configuration:
• Management Application Mode
• System settings
• Boot settings
• Policy filter (port & IP) settings
• LiveQ settings
• LiveTCP settings
• Logging settings
Note: Administrators can use the HP Velocity Management application to temporarily modify configuration settings. For
information, see HP Velocity management on page 22.
Management Application Mode
The HP Velocity Management application provides a toolset for monitoring and debugging HP Velocity-protected flows,
as well as the ability to temporarily override configuration settings.
10
Administrator Guide | HP Velocity
Table 3: Management Application Mode settings
Parameter
Options
Default
Advanced Management Application Mode
• Enabled
Thin Client: Disabled
Server Side: Enabled
• Disabled
Figure 8: HP Velocity Server Side administrative template—Management Application Mode
System settings
System settings (Table 4 on page 12) specify the following parameters:
• Operational Mode—Set the HP Velocity operational mode.
• LiveQ - Packet Loss Protection—Provide packet loss protection to application flows. For more information, see
LiveQ settings on page 16.
• LiveTCP - Latency Mitigation—Provide latency mitigation to application flows. For more information, see LiveTCP
settings on page 18.
Note: The LiveQ and LiveTCP system settings are available only in the HP Velocity Server Side administrative template.
• LiveTCP Mode—Set the mode HP Velocity uses to provide optimization.
Note: The LiveTCP Mode system setting is available only in the HP Velocity Thin Client administrative template.
• LiveWiFi - Prioritization—Accelerate application flows by leveraging Wi-Fi multimedia standards to minimize latency
and prioritize HP Velocity traffic. This ensures that HP Velocity-protected flows experience lower latency and jitter, and
higher throughput.
• IP Option Beacon (UDP Flows)—Use the IP option beacon (0x880477FB) for UDP flows.
• TCP Option Beacon (TCP Flows)—Use the TCP option beacon (0x01000000 and 0x00000000) for TCP flows.
• Network MTU—The MTU that can be processed within the network.
11
Administrator Guide | HP Velocity
Table 4: System settings
Parameter
Options
Default
Operational Mode
• Protect: Provide session establishment, session statistics, packet
loss protection, Wi-Fi optimization, and latency mitigation.
Protect
• Monitor: Continuously profile end-to-end network conditions over
established flows. (HP Velocity network optimizers are not applied.)
• Off: Pass all application flows transparently and do not perform any
monitoring or optimization.
LiveQ - Packet Loss Protection
(HP Velocity Server Side only)
• Enabled
LiveTCP - Latency Mitigation
(HP Velocity Server Side only)
• Enabled
LiveTCP Mode
(HP Velocity Thin Client only)
• Standard: Provide LiveQ packet loss protection, LiveTCP latency
mitigation, and network statistics.
Enabled
• Disabled
Enabled
• Disabled
Standard
• Zero Overhead: Provide LiveTCP latency mitigation and network
statistics.
• Compatibility: Provide LiveTCP latency mitigation, network
statistics, and accessibility through firewalls and proxies.
Note: Changing the LiveTCP Mode setting affects only the flows
established after the setting is changed.
LiveWiFi - Prioritization
• Enabled
Enabled
• Disabled
IP Option Beacon (UDP Flows)
• Enabled
Enabled
• Disabled
TCP Option Beacon (TCP Flows)
• Enabled
Enabled
• Disabled
Network MTU
750 to 1500 bytes
1492
Note: When the IP Option Beacon or TCP Option Beacon setting is enabled, HP Velocity adds up to 4 bytes of data to 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 the IP Option
Beacon or TCP Option Beacon setting should resolve the issue.
12
Administrator Guide | HP Velocity
Figure 9: HP Velocity Server Side administrative template—System Settings
Figure 10: HP Velocity Server Side administrative template—System Settings
13
Administrator Guide | HP Velocity
Boot settings
Boot settings (Table 5 on page 14) specify the following parameters:
• Number of Protected Flows—The number of simultaneously protected flows allowed.
Note: When the default setting is changed, the system must be rebooted for the change to take effect.
Note: LiveTCP provides latency mitigation for up to 32 simultaneously protected flows.
• Local System Information Collection—Allow the local endpoint to send its system information and per-flow
statistics to the remote endpoint.
• Remote System Information Collection—Allow the local endpoint to process and display remote-endpoint system
information and per-flow statistics received.
For more information, see Flow information on page 26.
Table 5: Boot settings
Parameter
Options
Default
Protected flows
16 to 1024
• Thin Client: 16
• Server Side Desktop OS: 16
• Server Side Server OS: 256
Local System Information Collection
• Enabled
Enabled
• Disabled
Remote System Information Collection
• Enabled
Enabled
• Disabled
Figure 11: HP Velocity Server Side administrative template—Boot Settings
14
Administrator Guide | HP Velocity
Policy filter (port & IP) settings
Global policy filters (Table 6 on page 15) allow administrators to filter and optimize application flows on the basis of port
number, destination IP address, or both. When multiple policy filters are configured, they are evaluated in a predefined
order.
The Policy Filter (Port & IP) settings specify the following parameters:
• Transparent Ports TCP, UDP—The TCP and UDP port numbers whose application flows HP Velocity will not protect,
but will instead pass on transparently.
• Special TCP, UDP Ports—The TCP and UDP port numbers to which HP Velocity will provide support for certain
protocols (see Table 7 on page 15).
• Whitelist TCP, UDP Ports—The TCP and UDP ports whose application flows HP Velocity will protect when the
following criteria are met:
- The destination IP address for the application flow is not specified in the IP Blacklist filter.
- The destination IP address for the application flow is specified in the IP Whitelist filter.
• IP Address Blacklist—The destination IP addresses of application flows that HP Velocity will not protect, but will
instead pass on transparently.
• IP Address Whitelist—The destination IP addresses of application flows that HP Velocity will protect.
Important: When the IP Whitelist filter is configured, HP Velocity will protect an application flow only if its destination IP
address matches an address included in this filter.
Note: If the IP Whitelist filter includes subnet destination IP addresses, the IP Blacklist filter can be used to filter IP
addresses in that subnet whose application flows HP Velocity will not protect.
Table 6:
Policy filter (port & IP) settings
Parameter
Default
Evaluation order
Transparent TCP, UDP Ports
TCP: 21 53 1194 1723 2869 9100 17500
4
UDP: 53 67 68 123 161 500 1194 4500 17500 42966
Special TCP, UDP Ports
TCP: 554 1720 5060
5
UDP: 554 5060
Whitelist TCP, UPD Ports
All ports
3
IP Address Blacklist
255.255.255.255/32
1
IP Address Whitelist
All IP addresses
2
Note: Use the CIDR format for IP addresses. To enter multiple IP addresses or port numbers in a field, use a
space-separated list; for example, 192.168.1.0/24 145.76.53.3/32 or 80 1750 1751.
Table 7:
Special port policy filter—Default settings
Protocol
Special TCP port
Special UDP port
RTSP
554
554
H.323
1720
SIP
5060
5060
15
Administrator Guide | HP Velocity
Note: When the special port policy filter includes ports not recognized by HP Velocity, those ports will be ignored.
Figure 12: HP Velocity administrative template - Policy Filters (Port & IP)
LiveQ settings
LiveQ applies a mathematical transformation to original input packets, which outputs one or more segments for each
original packet received as input. Each segment logically represents a portion of the input packet and might carry
additional information, such as redundancy data. The number of logical segments used to represent an original packet
varies based on current network-loss conditions.
Target Loss Rate policy filters can be used to specify the IP addresses and ports of application flows to which a specific
level of packet loss protection is applied.
LiveQ configuration settings (Table 8 on page 17 and Table 9 on page 17) specify the following parameters:
• Global Target Loss Rate—The Target Loss Rate (TLR) that HP Velocity will attempt to achieve for
HP Velocity-protected flows.
Note: TLR refers to the amount of packet loss that a thin-client application can tolerate while still delivering an
acceptable QoE. The recommended TLR for thin-client applications is 0.04%.
• Congestion Avoidance—Analyze network links to identify those with bandwidth constraints, and then automatically
adjust packet-loss protection to accommodate the constraints.
• Bandwidth Control—The encoding level applied to HP Velocity-protected flows. HP Velocity constantly monitors
network loss and automatically applies the protection mode required to reduce network loss to the default TLR. The
protection mode used at any given time depends on the real-time loss measured in the network.
• Burst Loss Protection (BLP)—Protect against correlated (sequential) loss in the network that can otherwise prevent
HP Velocity from reconstructing source packets at the remote endpoint.
Note: The net effect of BLP is added resiliency against burst loss. Its success depends on the number of source packets
that are encoded by HP Velocity and the sequential loss duration. BLP might degrade performance for highly
latency-sensitive applications.
16
Administrator Guide | HP Velocity
• BLP Buffer—The amount of packet buffering (in milliseconds) that HP Velocity can use when protecting against
bursty or correlated loss.
• Target Loss Rate Policy Filters—The TLR that HP Velocity will attempt to achieve for all protected flows whose
destination IP address, TCP port number, or UDP port number are included in this policy filter.
Table 8: LiveQ settings
Parameter
Options
Default
Target Loss Rate
• 0.04%
0.04%
• 0.1%
• 0.2%
• 0.4%
Note: An aggressive TLR might not be achievable in high-loss
networks. After modifying the TLR, refer to the Network Monitor graph
(see Network Monitor graph on page 25) to verify whether the rate
specified is being achieved.
Congestion Avoidance
• Disabled
Enabled
• Enabled
Note: When Congestion Avoidance is enabled and bandwidth
constraints are detected, the Bandwidth Control and TLR settings are
overridden to ensure the best network performance possible.
Bandwidth Control
• Dynamic: Maximize performance while minimizing the required
bandwidth. (Recommended for environments where bandwidth is
not constrained.)
Dynamic
• Low: Cap the estimated HP Velocity protection overhead at or below
27%. (Recommended for environments where bandwidth is very
constrained.)
• Medium: Cap the estimated HP Velocity protection overhead at or
below 40%. (Recommended for environments where bandwidth is
moderately constrained.)
• High: Maximize performance in environments where bandwidth is
not constrained, but network loss is high. When HP Velocity is at the
far end, High mode uses aggressive encoding without first
measuring the loss in the network.
Note: Higher encoding levels protect against greater network loss, but
require more bandwidth.
Burst Loss Protection
• Off
Auto
• On
• Auto: Allow HP Velocity to determine whether BLP is required.
BLP Buffer
10 ms to 100 ms (in increments of 10 ms)
20 ms
Table 9: Target loss rate policy filter—Default settings
Parameter
Options
Default
TLR
• 0.04%
0.04%
• 0.1%
• 0.2%
• 0.4%
IP
All IP addresses
UDP Ports
All UDP ports
TCP Ports
All TCP ports
17
Administrator Guide | HP Velocity
Note: Use the CIDR format for IP addresses. To enter multiple IP addresses or port numbers in a field, use a
space-separated list.
Figure 13: HP Velocity administrative template—LiveQ - Packet Loss Protection
LiveTCP settings
As HP Velocity observes the network and detects packet loss, the LiveTCP congestion control algorithm dynamically
adapts to changing network conditions, boosting QoE in high-latency networks.
Note: LiveTCP configuration settings are available only in the HP Velocity Server Side administrative template.
LiveTCP configuration settings (Table 10 on page 18) specify the following parameters:
• Latency Threshold (ms)—Activate LiveTCP latency mitigation once the specified delay threshold (in milliseconds) is
exceeded.
• Congestion Control—The level of congestion control required. LiveTCP adapts its algorithm to automatically provide
congestion control that is optimized independently for each TCP flow (LAN, remote network, Wi-Fi) and the conditions
in the network.
• Advanced Congestion Detection—Apply advanced tuning that detects and reacts to packet loss.
• Peering Filters—The port numbers on HP Velocity-enabled endpoints to which the LiveTCP algorithm is applied to
application flows.
Table 10: LiveTCP latency mitigation settings
Parameter
Options
Default
Latency Threshold (ms)
20 to 2000
20
Congestion Control
• Standard: Handle the effects of a high-latency network
Standard
• TCP-Friendly: Use the standard TCP-like congestion control
algorithm
18
Administrator Guide | HP Velocity
Parameter
Options
Default
Advanced Congestion
Detection
• Enabled
Enabled
• Disabled
Peering Filters
3389 42966 2598 1494
Note: Use a space-separated list to enter multiple port numbers in the Peering Filters field.
Figure 14: HP Velocity Server Side administrative template—LiveTCP - Latency Mitigation
Logging settings
HP Velocity logs provide detailed network statistics per endpoint and per-flow statistics, facilitating diagnostics.
Logging settings (Table 11 on page 19) specify the following parameters:
• Statistics Logging—Collect endpoint network statistics at the specified interval.
• Flow Logging—Collect per-flow network statistics at the specified interval.
• Flow Records—Create a flow record when a flow is terminated. Each record provides detailed flow information,
including system information.
Table 11: Logging settings
Setting
Options
Default
Statistics Logging
• Disabled
Disabled
• Every 5 Seconds
• Every Minute
• Every Five Minutes
19
Administrator Guide | HP Velocity
Setting
Options
Default
Flow Logging
• Disabled
Disabled
• Every 5 Seconds
• Every Minute
• Every Five Minutes
Flow Records
• Disabled
Disabled
• Enabled
Figure 15: HP Velocity Server Side administrative template—Logging settings
20
Administrator Guide | HP Velocity
HP Velocity account privileges
Table 12 on page 21 and Table 13 on page 21 describe the HP Velocity account privileges.
Table 12: Administrator (Windows) and root user (HP ThinPro) account privileges
Information
Read
Write
Export
Flow information
X
Network monitoring graphs
X
Network statistics
X
X
X
Configuration values
X
X
X
Write
Export
Table 13: Non-administrator (Windows) and non-root user (HP ThinPro) account privileges
Information
Read
Flow information
X
Network monitoring graphs
X
Network statistics
X
X
Configuration values
X
X
21
Administrator Guide | HP Velocity
HP Velocity management
The HP Velocity Management application is a Windows-based application that provides HP Velocity Administrators with a
toolset for monitoring and troubleshooting HP Velocity-protected flows, and for working with configuration parameters.
The HP Velocity Management application automatically starts on system startup and runs in the background. To access
the application toolset, right-click the HP Velocity System Tracy icon, and click Management. To stop the Management
application, right-click the HP Velocity system tray icon, and click Exit. To restart it, expand the HP Velocity folder on the
Windows Start menu, and click HP Velocity Management Application.
Note: Stopping the HP Velocity Management application does not affect the HP Velocity operational mode.
This section covers the following information:
• Network statistics
• Network Monitor graph
• Flow information
• Network loss simulation
• Configuration settings
Network statistics
HP Velocity collects real-time data on HP Velocity-protected flows and makes available basic and advanced statistics on
how the network is performing.
To access basic statistics (Table 14 on page 22), click the Network Statistics tab in the HP Velocity Management
application to display the Statistics view. To access advanced statistics (Table 15 on page 23), select the Advanced check
box. For information about working with network statistics, see Network Statistics operations on page 24.
Figure 16: Statistics view showing basic and advanced statistics
Note: Statistics are accumulated in time-incremented bins (Total, 5 Seconds, 1 Minute, and 5 Minutes columns). The Total
column represents the accumulated statistics since either the system was started or statistics were last cleared.
Table 14: Basic statistics
Statistic name
Description
Loss - Without Velocity
The actual received packet loss rate measured by HP Velocity.
Loss - With Velocity
The received packet loss rate after correction by HP Velocity.
22
Administrator Guide | HP Velocity
Statistic name
Description
Compatibility Tx Loss
The amount (percentage) of transmit network loss.
Note: Supported on HP Velocity Server Side only. Data for this statistic is available only
when the LiveTCP Mode parameter (see System settings on page 11) is set to
Compatibility.
Encoded Data Sent
The bytes of encoded data, in Kbps for intervals or MB/KB for cumulative totals, sent by
HP Velocity to each remote HP Velocity-enabled endpoint.
Encoded Data Received
The bytes of segment data, in Kbps for intervals or MB/KB for cumulative totals,
received by HP Velocity from each remote HP Velocity-enabled endpoint.
Total Active Flows
The number of currently active, unique application flows detected by HP Velocity as an
endpoint.
Protected Flows
The number of currently active, unique, and protected application flows detected by
HP Velocity as an endpoint.
Table 15: Advanced statistics
Statistic name
Description
Packets Encoded
The number of IP packets that were encoded by HP Velocity into segments.
Note: When the LiveTCP Mode parameter (see System settings on page 11) is set to
Compatibility, this statistic reflects the total amount of data packets, acknowledgment
(ACK) packets, and final (FIN) packets.
Segments Sent
The number of encoded segments sent by HP Velocity to each remote
HP Velocity-enabled endpoint.
Note: When the LiveTCP Mode parameter (see System settings on page 11) is set to
Compatibility, this statistic reflects the total amount of data packets, ACK packets
(including ACK packets generated by the LiveTCP optimizer), and FIN packets.
Compatibility Segment ReTx
The number of encoded data packets that HP Velocity retransmitted.
Note: Supported on HP Velocity Server Side only. Data for this statistic is available only
when the LiveTCP Mode parameter (see System settings on page 11) is set to
Compatibility.
Segments Received
The number of encoded segments received by HP Velocity from each remote
HP Velocity-enabled endpoint.
Note: When the LiveTCP Mode parameter (see System settings on page 11) is set to
Compatibility, this statistic reflects the total amount of data packets, acknowledgment
(ACK) packets, and final (FIN) packets.
Segments Lost
The number of encoded segments that were not received by HP Velocity due to packet
loss in the network.
Packets Decoded
The number of IP packets that HP Velocity successfully reconstructed from the
received encoded segments.
Note: When the LiveTCP Mode parameter (see System settings on page 11) is set to
Compatibility, this statistic reflects the total amount of data packets, ACK packets
(including ACK packets generated by the LiveTCP optimizer), and FIN packets.
Packets Lost
The number of IP packets that HP Velocity was unable to reconstruct from the received
encoded segments due to excessive loss in the network.
Full Packets Lost
The number of IP packets that HP Velocity was unable to reconstruct because it did not
receive any encoded segments for the encoded packet.
Note: Together with the Packets Lost counter, this counter indicates burst loss.
High Loss Events
The number of times that HP Velocity detected difficulty communicating with the
remote HP Velocity-enabled endpoints due to extremely high packet loss in the
network.
23
Administrator Guide | HP Velocity
Statistic name
Description
Non-accelerated Packets Sent
The number of unprotected IP packets sent.
Non-accelerated Packets Received
The number of unprotected IP packets received.
Packet Flows Monitored
The number of unique application flows detected by HP Velocity.
Accelerated Packet Flows Monitored
The number of unique application flows protected by HP Velocity.
Accelerated Requests Unfulfilled
The number of data-flow requests that cannot be fulfilled due to resource limitations.
Packets Encoded (Throughput)
The bytes of IP packet data, in Kbps for intervals or KB/MB for cumulative totals,
received from each application encoded into HP Velocity segments or monitored by HP
Velocity.
Packets Decoded (Throughput)
The bytes of IP packet data, in Kbps for intervals or KB/MB for cumulative totals,
received from the network that were successfully reconstructed or monitored by HP
Velocity.
Non-accelerated Throughput (Tx)
The bytes of all transmitted unprotected IP packet data, in Kbps for intervals or KB/MB
for cumulative totals.
Non-accelerated Throughput (Rx)
The bytes of all received non-protected IP packet data in Kbps for intervals or KB/MB
for cumulative totals.
Network Statistics operations
Table 16: Network Statistics operations
Operation
Description
Logging Interval
Set the interval at which statistics are saved to the log file:
• Disabled (no logging)
• Every 5 Seconds
• Every Minute
• Every 5 Minutes
Save Log History
Export the statistics log to a comma-separated value (CSV) file.
Note: This operation is available only when a logging is not disabled.
Save Log Snapshot
Clear Statistics
Save the current 5-second, 1-minute, and 5-minute statistics to a file with the same column order
as the log history file.
Reset statistic counts and collection time to zero.
Note: When this operation is performed, the throughput data on the Network Monitor graph (see
Network Monitor graph on page 25) drops momentarily.
Note: HP Velocity maintains the statistics history for up to seven days. Logs are stored in the temporary folder for the
current user; for example, C:\Users\<username>\AppData\Local\Temp. The log filename format is
HPVelocity_logtype_yymmdd.log
24
Administrator Guide | HP Velocity
Network Monitor graph
HP Velocity collects information about endpoint network conditions (Table 17 on page 25) and presents the data in a
graph.
To view the Network Monitor graph, click the Network Monitor tab in the HP Velocity Management application.
Figure 17: Network Monitor graph
Table 17: Network monitoring data
Data
Description
Throughput (blue line)
The received throughput over the most recent interval. The
right axis indicates the throughput in Kbps or Mbps.
With Velocity (green bars)
The corrected packet loss seen by applications for which
HP Velocity is protecting flows. The left axis indicates the loss
as a percentage.
Without Velocity (red bars)
The packet loss in the network. The left axis indicates the loss
as a percentage.
Network Loss
Peak
The highest packet loss for the duration of the graph.
Without Velocity
The packet loss over the most recent interval.
With Velocity
The corrected loss over the most recent interval.
Note: Low corrected loss is optimal when sufficient
bandwidth is available.
Network Throughput
Peak
The highest received throughput for the duration of the
graph.
Current
The received throughput for the most recent interval.
25
Administrator Guide | HP Velocity
Flow information
HP Velocity facilitates end-to-end monitoring of network flows and the associated systems by collecting and reporting
information on protected endpoints and individual protected flows. HP Velocity also provides endpoint and per-flow data
on latency (see Latency and throughput data on page 27), as well as information about local and remote systems.
To view flow information, click the Flow Information tab in the HP Velocity Management application. The Flow
Information tab shows data for protected endpoint parameters (Table 18 on page 26) and protected flow parameters
(Table 19 on page 26). For information about working with flow information, see Flow Information operations
on page 28.
Figure 18: Flow Information tab
Table 18: Protected Endpoint information
Parameter
Description
Remote Host
The IP address of the remote host.
Product
The product name as defined in the System BIOS.
CPU Usage
The percentage of CPU in use.
Memory Usage
The percentage of memory in use.
Link
The type of network link in use.
Table 19: Protected Flow information
Parameter
Description
Remote IP
The remote IP address for the protected flow.
Remote Port
The remote TCP or UDP port number for the protected flow. If the port number is a well-known
protocol, the protocol name also appears.
Local IP
The local IP address for the protected flow.
Local Port
The local TCP or UDP port number for the protected flow. If the port number is a well-known
protocol, the protocol name also appears.
Protocol
The protocol (such as TCP or UDP) used by the protected flow.
IPQ
Indicates the active mode of the HP Velocity driver: P (Protect), M (Monitor), or C (LiveTCP Mode on
client side = Compatibility)
26
Administrator Guide | HP Velocity
Parameter
Description
LiveTCP
The LiveTCP status.
• Server Side: Protect, Inspect, or Off.
• Client Side: Protect or Off.
Note: For HP Velocity Thin Client, Protect indicates that the client has requested that the server
protect the application flow.
LiveQ
The LiveQ status: Protect or Off.
TLR
The TLR that HP Velocity will attempt to achieve for the protected flow.
Encoding
The encoding level applied to the protected flow.
To view information (OS Description, Vendor Name, Product Name, etc.) about local and remote systems (Figure 19
on page 27), click either the Local or Remote button on the Flow Information tab.
Figure 19: Local System Information dialog
Latency and throughput data
The Flow Information tab also provides graphs that represent Local Rx throughput, Remote Rx throughput, or plotting
latency for a protected endpoint or application flow.
To view a graph, click an entry for a protected endpoint or data point in the Flow Information tab.
Figure 20: Latency graph for a protected endpoint
27
Administrator Guide | HP Velocity
Flow Information operations
Table 20: Flow Information operations
Operation
Description
Logging Interval
Set the interval at which flow information is saved to the log file:
• Disabled (no logging)
• Every 5 Seconds
• Every Minute
• Every 5 Minutes
Save Log Snapshot
Save the current 5-second, 1-minute, and 5-minute interval flow information to a file.
Flow Records
Enable or disable flow-records collection.
Save Flow Record
Export the flow-records log to a CSV file.
Network loss simulation
HP Velocity allows administrators to simulate network loss (Table 21 on page 28) and test how HP Velocity-protected
flows respond to varying rates of loss in the network.
To access configuration settings for network simulation, click the Configuration tab in the HP Velocity Management
application, and click Network Simulator in the navigation tree.
Important: Network loss can be simulated on the server side only when the LiveTCP Mode parameter is set to either
Standard or Zero Overhead (see System settings on page 11). Loss settings applied when the LiveTCP mode parameter is
set to Compatibility will not result in network-loss simulation on the server side.
Figure 21: Network Simulator dialog
Table 21: Network Simulator parameters
Parameter
Description
Transmit Loss Rate (%)
The percentage of loss for the application flows being transmitted over the network.
Receive Loss Rate (%)
The percentage of loss for the application flows being received from the network.
Important: Network simulation is intended for debugging and demonstration purposes only. Therefore, always set the
transmit and receive loss rates to 0 under normal operating conditions.
28
Administrator Guide | HP Velocity
Configuration settings
The HP Velocity Management application provides access to current configuration settings (see HP Velocity
configuration settings on page 10), which users can export to a configuration report. Administrators can also use the
HP Velocity Management application to temporarily modify configuration settings.
To access a configuration dialog, click the Configuration tab in the HP Velocity Management application, and then click a
setting in the navigation tree.
Note: Management Application Mode settings and Logging settings are accessible only via the HP Velocity administrative
template. Boot settings can be viewed with the HP Velocity Management application, but cannot be modified.
Figure 22: System Settings dialog
Note: A system reboot automatically restores all configuration settings modified using the HP Velocity Management
application to either the system default values or, if applicable, custom configuration values (see HP Velocity configuration
on page 9).
This section covers the following information:
• Restoring default configuration settings
• Generating the HP Velocity configuration report
29
Administrator Guide | HP Velocity
Restoring default configuration settings
To restore default configuration settings, click the Configuration tab in the HP Velocity Management application, and
then click General in the navigation tree. In the General view, click Reset Configuration To Factory Defaults, and then
click Yes to confirm the reset.
Figure 23: Restore default configuration
Note: When group policies are in effect, the system configuration reset is overridden at the next system restart.
Generating the HP Velocity configuration report
To generate a configuration report, click the Configuration tab in the HP Velocity Management application, and then click
General in the navigation tree. In the General view, click Export Current Configuration To File.
A detailed configuration report (Table 22 on page 31) is automatically generated and opened in a text editor (such as
Windows Notepad) so that it can be saved locally.
Figure 24: HP Velocity configuration report
30
Administrator Guide | HP Velocity
Table 22: Configuration report parameters
Parameter
Description
Driver Configuration
Current configuration and internal driver settings of HP Velocity.
Local System Metrics
Statistics on host system performance.
OS Information
Operating system type, configuration, and performance information for the system on which
HP Velocity is installed.
Registry Keys
Registry key values configured by the Group Policy Engine.
Statistics
Snapshot of current network statistics.
Protected Flows
List of current protected flows.
Monitored Flows
List of current monitored flows.
31
Administrator Guide | HP Velocity
FAQs
This section provides information for the following scenarios:
• All HP Velocity application flows are blocked
• Traffic between HP Velocity servers is only monitored
• Protected flows are not established
• TCP-based VPNs are not protected
All HP Velocity application flows are blocked
HP Velocity uses the IP ID value 0x420B and the IP option 0x880477FB in IP headers, and the TCP option 0x01000000
and 0x00000000 in TCP headers.
Intrusion Detection Systems (IDS) and firewall systems might require configuration to support HP Velocity-enabled
traffic so that devices do not block it. See your device documentation to configure these settings.
Traffic between HP Velocity servers is only monitored
HP Velocity protects only the flows between HP thin clients and HP Velocity-enabled servers (virtual desktops or terminal
services). HP Velocity only monitors the flows of server-to-server connections.
Protected flows are not established
Virtualization architectures that require HP thin clients to access virtual desktops via a proxy service provided by a
connection broker (such as VMware View Manager) must have HP Velocity installed on the connection broker. This
ensures that protected flows are established for connections to a VMware desktop where HP Velocity is installed. For
information, see HP Velocity Server Side deployments for thin clients on page 3.
TCP-based VPNs are not protected
HP Velocity does not provide protection for virtual point-to-point connections for the Secure Socket Tunneling Protocol
(SSTP) VPN type.
32
Administrator Guide | HP Velocity
Decision trees
This section provides decision trees for troubleshooting the following issues:
• VDI connectivity issue
• Non-VDI connectivity issue
• HP Velocity-protected flows not established
• Quality of Experience: Packet-loss issue
• Quality of Experience: Latency issue
VDI connectivity issue
33
Administrator Guide | HP Velocity
Non-VDI connectivity issue
34
Administrator Guide | HP Velocity
HP Velocity-protected flows not established
35
Administrator Guide | HP Velocity
Quality of Experience: Packet-loss issue
36
Administrator Guide | HP Velocity
Quality of Experience: Latency issue
37
Administrator Guide | HP Velocity
Appendix: HP Velocity configuration on HP ThinPro
HP Velocity provides a default configuration suitable for most deployments. It also provides a configuration interface
(/proc) that enables users with root privileges to temporarily modify configuration settings on HP ThinPro.
The /proc/net/<ipeak0/1/2>/config file provides access to the following parameter files:
• about
• system
• boot
• core
• filters/filters
• filters/liveq
• liveq
• simulator
Note: Use ipeak0 for wired connections, ipeak1 for wireless connections, and ipeak2 for Point-to-Point Protocol
connections.
Changing the value of a configuration parameter
Note: The /proc/net/<ipeak0/1/2>/config file is a virtual file used to display the current HP Velocity
configuration in an easy-to-read format. The file cannot be modified using standard text editors.
Note: After a system restart, modifications written to the /proc interface are not retained. Original configuration
settings are restored.
1.
Log in to HP ThinPro as an administrator.
2.
Access the /proc/net/<ipeak0/1/2>/config file to be modified.
3.
Write a new line to the file in the same format as the line being modified. For example, to change the line
<parameter> = <value_1> <value_2> <value_3>, enter <parameter> = <newvalue_1>
<newvalue_2> <newvalue_3>.
4.
Use the echo command and a > symbol to redirect the new value to the file. For example, echo opMode=1 >
/proc/net/ipeak0/config/system.
5.
Use the commit command to commit the modification. For example, echo commit=1 >
proc/net/ipeak0/config/system.
about
Description
The /proc/net/hpvelocity/config/about file provides the HP Velocity version number, release number, and
product edition information; for example, Version: 2.1.0r17014 [Server].
Read / Write
• Read Only
38
Administrator Guide | HP Velocity
system
Description
The /proc/net/<ipeak0/1/2>/config/system file specifies the following parameters:
• opMode: Set the operational mode of HP Velocity.
• liveTcpMode: Set the mode HP Velocity uses to provide optimization.
• liveWiFiEnable: Accelerate application flows by leveraging Wi-Fi multimedia standards to minimize latency and
prioritize HP Velocity traffic. This ensures that HP Velocity-protected flows experience lower latency and jitter, and
higher throughput.
• ipOptionMark: Use the IP option beacon (0x880477FB) for UDP flows.
• tcpOptionMark: Use the TCP option beacon (0x01000000 and 0x00000000) for TCP flows.
• mtu: The MTU that can be processed within the network.
Read / Write
• Read / Write: Any single value using a string with the format <parameter> = <value>.
Parameters
Table 23: ./config/system parameters
Parameter
Options
Default
opMode
• 0 = Protect: Provide session establishment, session statistics,
packet loss protection, Wi-Fi optimization, and latency mitigation.
0
• 1 = Off: Pass all application flows transparently and do not perform
any monitoring or optimization.
• 3 = Monitor: Continuously profile end-to-end network conditions
over established flows. (HP Velocity network optimizers are not
applied.)
liveTcpMode
• 0 = Standard: Provide LiveQ packet loss protection, LiveTCP latency
mitigation, and detailed network statistics.
0
• 1 = Zero Overhead: Provide LiveTCP latency mitigation and detailed
network statistics.
• 2 = Compatibility: Provide LiveTCP latency mitigation and
accessibility through firewalls and proxies.
liveWiFiEnable
• 0 = Disabled
1
• 1 = Enabled
ipOptionMark
• 0 = Disabled
1
• 1 = Enabled
tcpOptionMark
• 0 = Disabled
1
• 1 = Enabled
mtu
750 to 1500 bytes
1492
Note: When the IP option beacon (ipOptionMark) or TCP option beacon (tcpOptionMark) setting is enabled, HP Velocity
adds up to 4 bytes of data to 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 the IP option beacon or TCP option beacon setting should resolve the issue.
39
Administrator Guide | HP Velocity
boot
Description
The /proc/net/<ipeak0/1/2>/config/boot file specifies the following parameters:
• ProtectedFlows: The number of simultaneously protected flows allowed.
Note: If the default Protected Flows setting is changed, the system must be rebooted for the change to take effect.
• localSystemInformationCollection: Allow the local endpoint to send its system information and per-flow statistics to
the remote endpoint.
• remoteSystemInformationCollection: Allow the local endpoint to process and display remote endpoint system
information and per-flow statistics received.
Read / Write
• Read Only
Parameters
Table 24: ./config/boot parameters
Parameter
Options
Default
ProtectedFlows
16 to 1024
16
localSystemInformationCollection
• 0 = Disabled
1
remoteSystemInformationCollection
• 0 = Disabled
• 1 = Enabled
1
• 1 = Enabled
core
Description
The /proc/net/<ipeak0/1/2>/config/core file specifies the following parameters:
• globalFilter: Set the operational mode of HP Velocity.
Note: The /proc/net/<ipeak0/1/2>/config/core file provides legacy support for the graphical user
interface.
Read / Write
• Read / Write: Any single value using a string with the format <parameter> = <value>.
Parameters
Table 25: ./config/core parameters
Parameter
Options
Default
globalFilter
• 0 = Protect: Provide session establishment, session statistics,
packet loss protection, Wi-Fi optimization, and latency
mitigation.
0
• 1 = Off: Pass all application flows transparently and do not
perform any monitoring or optimization.
• 3 = Monitor: Continuously profile end-to-end network
conditions over established flows. (HP Velocity network
optimizers are not applied.)
40
Administrator Guide | HP Velocity
filters/filters
Description
The /proc/net/<ipeak0/1/2>/config/filters/filters file specifies the following global port and IP
parameters:
• udpFilters, tcpFilters: The TCP and UDP port numbers whose application flows HP Velocity will not protect, but will
instead pass on transparently.
• specialUdpFilters, specialTcpFilters: The TCP and UDP port numbers to which HP Velocity will provide support for
certain protocols (see Table 27 on page 42).
• whiteUdpFilters, whiteTcpFilters: The TCP and UDP ports whose application flows HP Velocity will protect when the
following criteria are met:
- The destination IP address for the application flow is not included in the IP Blacklist filter (blackIPAddressFilters).
- The destination IP address for the application flow is included in IP Whitelist filter (whiteIPAddressFilters).
• blackIPAddressFilters: The destination IP addresses of application flows that HP Velocity will not protect, but will
instead pass on transparently.
• whiteIPAddressFilters: The destination IP addresses of application flows that HP Velocity will protect.
Important: When the IP Whitelist filter is configured, HP Velocity will protect an application flow only if its destination IP
address matches an address included in this filter.
Note: If the IP Whitelist filter includes subnet destination IP addresses, the IP Blacklist filter can be used to filter IP
addresses in that subnet whose application flows HP Velocity will not protect.
Read / Write
• Read / Write: Any single value using a string with the format <parameter> = <value>.
Parameters
Table 26: ./config/filters/filters parameters
Parameter
Default
Evaluation order
udpFilters, tcpFilters
TCP: 21 53 1194 1723 2869 9100 17500
4
UDP: 53 67 68 123 161 500 1194 4500 17500 42966
specialUdpFilters, specialTcpFilters
TCP: 554 1720 5060
5
UDP: 554 5060
whiteUdpFilters, whiteTcpFilters:
All ports
3
blackIPAddressFilters
255.255.255.255/32
1
whiteIPAddressFilters
All IP addresses
2
Note: Use the CIDR format for IP addresses. To enter multiple IP addresses or port numbers, use a space-separated list;
for example, 192.168.1.0/24 145.76.53.3/32 or 80 1750 1751.
41
Administrator Guide | HP Velocity
Table 27: Special port filter default settings
Protocol
Special TCP port
Special UDP port
RTSP
554
554
H.323
1720
SIP
5060
5060
Note: When the Special Port Policy filter configuration includes ports not recognized by HP Velocity, those ports will be
ignored.
filters/liveq
Description
The /proc/net/<ipeak0/1/2>/config/filters/liveq file specifies the destination IP addresses, TCP port
numbers, or UDP port numbers of application flows for which LiveQ will attempt to achieve the defined Target Loss Rate
(TLR).
Read / Write
• Read / Write: Any single value using a string with the format <parameter> = <value>.
Parameters
Table 28: ./config/filters/liveq parameters
Parameter
Description
Default
targetLossHighIPFilters
The destination IP addresses of protected application flows for which
HP Velocity will attempt to achieve the defined TLR:
All IP addresses
targetLossDefaultIPFilters
• High = 0.4%
targetLossLowIPFilters
• Default = 0.2%
• Low = 0.1%
targetLossUltraLowIPFilters
• UltraLow = 0.04%
targetLossHighTCPFilters
The destination TCP port numbers of protected application flows for
which HP Velocity will attempt to achieve the defined TLR:
targetLossDefaultTCPFilters
• High = 0.4%
targetLossLowTCPFilters
• Default = 0.2%
• Low = 0.1%
targetLossUltraLowTCPFilters
• UltraLow = 0.04%
targetLossHighUDPFilters
The destination UDP port numbers of protected application flows for
which HP Velocity will attempt to achieve the defined TLR:
targetLossDefaultUDPFilters
• High = 0.4%
targetLossLowUDPFilters
targetLossUltraLowUDPFilters
All TCP ports
All UDP ports
• Default = 0.2%
• Low = 0.1%
• UltraLow = 0.04%
Note: Use the CIDR format for IP addresses. To enter multiple IP addresses or port numbers, use a space-separated list.
42
Administrator Guide | HP Velocity
liveq
Description
The /proc/net/<ipeak0/1/2>/config/liveq file specifies the following parameters:
• targetLossLevel: The Target Loss Rate (TLR) that HP Velocity will attempt to achieve for application flows whose
destination IP address, or TCP or UDP port number does not match an IP address or port number specified by the file
/proc/net/<ipeak0/1/2>/config/liveq (see filters/liveq on page 42).
Note: TLR refers to the amount of packet loss that a thin-client application can tolerate while still delivering an
acceptable QoE. The recommended TLR for thin-client applications is 0.04%.
• congestionAvoidance: Analyze network links to identify those with bandwidth constraints, and then automatically
adjust packet-loss protection to accommodate the constraints.
• bandwidthControl: The protection mode used to encode HP Velocity-protected flows. HP Velocity constantly monitors
network loss and automatically applies the protection mode required to reduce network loss to the default TLR. The
protection mode used at any given time depends on the real-time loss measured in the network.
• burstLossProtection: Protect against correlated (sequential) loss in the network that can otherwise prevent
HP Velocity from reconstructing source packets at the remote endpoint.
Note: The net effect of Burst Loss Protection (burstLossProtection) is added resiliency against burst loss. Its success
depends on the number of source packets that are encoded by HP Velocity and the sequential loss duration. BLP might
degrade performance for highly latency-sensitive applications.
• blpBuffer: The amount of packet buffering (in milliseconds) that HP Velocity can use when protecting against bursty or
correlated loss.
Read / Write
• Read / Write: Any single value using a string with the format <parameter> = <value>.
Parameters
Table 29: ./config/liveq parameters
Parameter
Options
Default
targetLossLevel
• 0 = 0.4%.
3
• 1 =: 0.2%.
• 2 = 0.1%.
• 3 = 0.04%.
Note: An aggressive TLR might not be achievable in high-loss
networks.
congestionAvoidance
• 0 = Off
1
• 1 = On
Note: When Congestion Avoidance is enabled and bandwidth
constraints are detected, the Bandwidth Control and TLR settings are
overridden to ensure the best network performance possible.
43
Administrator Guide | HP Velocity
Parameter
Options
Default
bandwidthControl
• 0 = Dynamic: Maximize performance while minimizing the required
bandwidth. (Recommended for environments where bandwidth is
not constrained.)
0
• 1 = Low: Cap the estimated HP Velocity protection overhead at or
below 27%. (Recommended for environments where bandwidth is
very constrained.)
• 2 = Medium: Cap the estimated HP Velocity protection overhead at or
below 40%. (Recommended for environments where bandwidth is
moderately constrained.)
• 3 = High: Maximize performance in environments where bandwidth
is not constrained, but network loss is high. When HP Velocity is at
the far end, High mode uses aggressive encoding without first
measuring the loss in the network.
Note: Higher encoding levels protect against greater network loss, but
require more bandwidth.
burstLossProtection
• 0 = Off
2
• 1 = On
• 2 = Auto: Allow HP Velocity to determine whether BLP is required.
blpBuffer
10 ms to 100 ms (in increments of 10 ms)
20
simulator
Description
The /proc/net/<ipeak0/1/2>/config/simulator file specifies the following parameters:
• lossRateTx: The percentage of loss for application flows transmitted over the network.
• lossRateRx: The percentage of loss for application flows received from the network.
Note: Network simulation is intended for debugging and demonstration purposes only. Therefore, always set the
transmit (lossRateTx) and receive (lossRateRx) loss rates to 0.00% under normal operating conditions.
Read / Write
• Read / Write: Any single value using a string with the format <parameter> = <value>.
Parameters
Table 30: ./config/simulator parameters
Parameter
Options
Default
lossRateTx
0 to 1000 (e.g., 40 to 0.4%)
0
lossRateRx
0 to 1000 (e.g., 40 to 0.4%)
0
44
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement