Advanced Features
358
. . . . .
LIMITATIONS
The following limitations apply when using Check Point QoS to control Citrix
MetaFrame traffic:
• The Citrix TCP services are supported in Traditional mode QoS Policies
only.
• Session Sharing must be disabled.
• The number of applications that are detected by the inspection infrastructure
is limited to 2,048. Console errors will be sent, if this limit is exceeded.
These errors are harmless, and will not affect your system. Simply restart the
machine.
• Versions of MetaFrame prior to 1.8 are not supported, because there is no
packet tagging in these versions.
• Only one Citrix TCP service can be allocated per single rule.
Load Sharing
Load Sharing is a mechanism that distributes traffic within a cluster of
Gateways, so the total throughput of multiple machines is increased. Check
Point QoS’s architecture guarantees that Load Sharing will provide either:
• Two-way stickiness. All packets of a single connection use the same
machine in both directions.
• Conversation stickiness. All packets of control/data connections within a
conversation use the same machine in both directions.
Check Point QoS provides a fault-tolerant QoS solution for cluster Load
Sharing that deploys a unique, distributed WFQ bandwidth-management
technology. The user is able to specify a unified QoS Policy per virtual interface
of the cluster. The resulting bandwidth allocation is therefore identical to that
obtained by installing the same QoS Policy on a single server.
Under a load state, there are a few connections that are
backlogged actively for short periods of time. In such cases, the
Load Sharing function in ClusterXL is not spread evenly. But in
this case, there is no congestion and therefore no need for QoS.
