www.amulethotkey.com | Page 31
n
etwork
manaGement
8
8. Manage the network
8.1 Consider network bandwidth requirements
PCoIP uses the Internet Protocol (IP) to transmit data
between the host and client. The data can be routed over
any IP-compatible infrastructure between offices or across
continents. In every case, performance depends on the available
bandwidth and signal latency.
8.1.1
Factors affecting bandwidth
The bandwidth required depends on several factors, including:
•
the number of pixels changing from frame to frame;
•
the number and resolution of screens to be encoded;
•
settings made by the user.
Exact bandwidth requirements for PCoIP are difficult to predict,
use the values in
as a guide only:
Setting
Bandwidth
Idle display
~ 0
No USB or audio data
~32Kbit/s per pair of
monitors.
General office use (that is,
writing documents)
300-500Kbit/s.
Audio
2 Mbit/s.
A significant display change
(such as minimising or
restoring a window)
4-5Mbit/s
USB transfers
< 6Mbit/s of traffic
Playing full-screen video
< 70Mbit/s
Table 5:
PCoIP.bandwidth.requirements
Example1:
A dual head configuration running a word
processor, spreadsheets, and 2D illustrations/designs will
typically use between 1 and 10 Mbit/s.
Example2:
A quad video head system running real time full
screen video might peak at 70 Mbit/s.
8.1.2 What happens when available bandwidth is exceeded
In all cases, PCoIP builds to a lossless image. If the required
bandwidth is not available, PCoIP dynamically adjusts the quality
to match. You can also use the zero client management tools
) to optimise performance for
most conditions.
If bandwidth usage is a concern, we recommend testing and
monitoring on your network. For assistance, please contact
Amulet Hotkey Technical Support.
8.2
Dual redundant network connections
Important!
In an octal configuration, both DXP4s can be
linked via an additional cable so that traffic can be routed
through either DXP4. The network ports are connected to
an internal, unmanaged network switch. The DXP4 does not
monitor its network links and relies on the LAN spanning tree
to prevent switching loops and to provide redundancy.
If both network ports are connected when a connection
between the zero client and PCoIP host is interrupted, the
recovery process is as follows:
1.
The Spanning Tree network protocol brings up the redundant
path between the disconnected zero client and host.
2.
The zero client attempts to resume the session. By default,
it retries for up to 30 seconds. If the remote PCoIP host is
reachable within this time, the session resumes seamlessly.
3.
If the zero client cannot reach the host within the retry
period, it displays the Connect screen of the On Screen Display.
See
.
4.
When the user re-authenticates themselves, they are
reconnected to the previous session as it was at the time of the
failure.
Note:
If you use a connection broker to pair zero clients to
PCoIP hosts (see
), you can configure the session so that
the Windows desktop is locked while disconnected.
