PC-over-IP® (PCoIP®) System User’s Guide Revision C 1.2.03.03.
Technical Support See the support Web site for technical updates, additional warranty information and documentation, and software revisions: Web http://www.clearcube.com/support Email: support@clearcube.com Phone: (512) 652-3400 or call toll free (866) 652-3400 (United States) ClearCube Technology, Inc. Corporate Headquarters ClearCube 3700 W Parmer Ln Austin, Texas 78727 E-mail info@clearcube.
Contents Chapter 1. Introduction ................................................................................... 1 1.1 What is PC-over-IP? ....................................................................................................... 1 1.2 Component and Interface Overview ................................................................................ 3 1.2.1 Zero Client ........................................................................................................... 3 1.2.
3.2 Overview and Terms..................................................................................................... 20 3.3 User Experience ........................................................................................................... 22 3.4 Bandwidth Effects on Usability..................................................................................... 23 3.5 Typical Bandwidth Usage ............................................................................................. 24 3.5.
4.6.2 R-Series Blades .................................................................................................. 46 4.6.2.1 Using a Zero Client ........................................................................................ 46 4.6.2.2 Using a ClearCube C/Port (Analog) ................................................................ 49 Chapter 5. Zero Client Controls and Supported Power States .................. 51 5.1 Buttons and Indicators ..........................................
.6.3 Unmanaged Static IPs with Direct Connection .................................................... 78 6.6.3.1 Direct Connection Best Practices .................................................................... 81 6.6.3.2 Configuring Devices in Direct Connection ...................................................... 81 6.6.4 Unmanaged DHCP with SLP Discovery ............................................................. 82 6.6.5 Managed Environments Using ClearCube Sentral......................
Appendix B: Troubleshooting ........................................................................ 111 Can’t set or change peer for a device .................................................................................. 111 “No route to host” message................................................................................................. 112 PCoIP does not support all power states ..............................................................................
Chapter 1. Introduction This document: Provides a brief overview of PC-over-IP® (PCoIP®) technology (see 1.
Chapter 1. Introduction computing experience in the data center and transmits it across a standard IP network to a zero client—a stateless desktop device—for an exceptional user experience. Devices using PCoIP technology contain PCoIP processors that process display images at the pixel level, eliminating any dependence on the blade CPU or GPU. External display processing provides complete independence from the host PC or workstation operating system and applications.
1.2 Component and Interface Overview 1.2 Component and Interface Overview In typical deployments, a zero client is connected to a remote computing device (a remote PC, blade, or virtual machine) by a direct connection or over an IP network. Zero clients use the PCoIP protocol to connect to a host card in a remote device, which is typically located in a secure data center.
Chapter 1. Introduction ClearCube zero clients support multi-head operation, enabling you to specify a different resolution and display orientation (portrait or landscape) for each monitor. Zero clients do not require unique OS drivers, and support the following standard peripherals: Up to four independently–configurable monitors Keyboards Mouse and other pointing devices Audio devices USB peripherals, including isochronous USB devices and printers (zero client USB ports are USB-2.
1.3 TERA2 and TERA1 Processors 1.2.2 Host Card A PCIe® card, based on the TERA processor, contained in a computing device (such as a PC blade or a VM). Host cards enable supported zero clients to connect to using PCoIP technology to provide high resolution graphics, audio, and video and full USB peripheral support. Figure 3. Host cards NOTE: ClearCube recommends always using the same firmware version on zero clients and host cards.
Chapter 1. Introduction TERA1 Host cards: V5300-series and lower Zero clients: C7400-series and lower I9400-series 1.4 Device Interfaces Host cards and zero clients provide the following interfaces for device configuration and management: Web interface On-screen display (OSD) The following table shows each device and the interface to use for configuration and management. Table 1.
1.4 Device Interfaces Figure 4. The Web interface’s Network page displayed in a browser Table 1. “Device support for each interface” on page 6 shows each device and the interfaces you can use to configure them. For additional information: 6.3 “Using the Web Interface” on page 63 Appendix D: “Zero Client and Host Card Web Interfaces” on page 118 6.8.1 “Session Control and Peer Information” on page 88 ClearCube Technology, Inc.
Chapter 1. Introduction 1.4.2 On-Screen Display (OSD) The On Screen Display (OSD) is a local zero client interface that is displayed when a zero client is powered on and a PCoIP session is not established. Thin client users click the Connect button (shown below) to connect to a host card. The OSD provides zero client configuration options, session- and device-related information, and more. Click the Options menu to display menu options. Options Menu Connect Button Figure 5.
1.5 Terminology Used in This Guide Term Description A3100 The ClearCube A3100 Chassis houses up to 10 A-series blades in a secure, rack-mounted, 6U enclosure. The A3100 Chassis provides chassis management features, cable management, and blade connectivity. Chassis connectivity includes USB 2.0, two network ports for each enclosed blade, and PCoIP connections to support zero clients. Blade A computer with a typically longer, narrower shape than traditional computers.
Chapter 1. Introduction Term Description Peer Each PCoIP device has a corresponding device, or a peer, to which it connects. For example, if a zero client establishes a PCoIP connection to a host card, the zero client and host at each end of the session are peers. PCoIP A presentation protocol that enables zero clients and host video cards to deliver high–performance video, audio and USB data to users.
1.5 Terminology Used in This Guide Term Description to find services. ClearCube devices can use SLP to dynamically discover zero clients and host cards without information about their location on a network. Standard static A static session on a network. Static session Describes a connection between a PCoIP hosts and zero client, where a device always connects to the same peer (requiring that device IPs do not change).
Chapter 2. Connection Modes and Network Topology When considering and preparing for your deployment of zero clients and host cards with PCoIP technology, there are several critical aspects of your deployment to address. This section identifies and provides a general description of these concepts: Device management Peer assignment IP address assignment The following sections describe each of these concepts. Consider each to determine how to address them in your deployment.
2.2 Peer Assignment clients, hosts, and users. Connection brokers dynamically issue peer assignments based on device- and user-based settings within the connection broker. Sentral enables administrators to update device firmware, configure devices, manage chassis, mange device power states, generate reports, perform event logging, and much more.
Chapter 2. Connection Modes and Network Topology You cannot use device management tools and connection brokers, including Sentral, which require network access. The picture below shows a PCoIP deployment using direct connections. Figure 6. A deployment using direct connections 2.2.2 SLP Discovery Zero clients and host cards require a peer to create a PCoIP session. Zero clients and host cards can use Service Location Protocol (SLP) to discover devices to which they can connect.
2.3 IP Address Assignment Figure 7. The Web interface’s Discovery page, where you can enable SLP discovery See 6.6.4 “Unmanaged DHCP with SLP Discovery” on page 82 for instructions about enabling SLP discovery. 2.3 IP Address Assignment The following sections describe the various IP address assignment methods in a PCoIP deployment. 2.3.1 DHCP ClearCube PCoIP devices are initially configured for DHCP environments through the Web interface’s Enable DHCP option (see 6.
Chapter 2. Connection Modes and Network Topology Enable DHCP Option Figure 8. The Enable DHCP Option on the Web interface's network page When a user powers on a zero client or host, the PCoIP device obtains an IP address from the network’s DHCP server. If the DHCP server is unavailable at any time while the zero client or host is already powered on, the zero client keeps its current IP address. The zero client keeps this IP address until a user powers off the device.
2.3 IP Address Assignment NOTE: In instances where you are assigning peer devices using reserved DHCP addresses, device discovery is not appropriate. ClearCube recommends disabling SLP discovery in deployments using reserved DHCP addresses. In a managed environment, Sentral must discover the devices to build the Sentral database. NOTE: If you are using SLP discovery, after you click the Connect button on the zero client’s OnScreen Display (OSD), the OSD displays a maximum of 10 hosts (blades).
Chapter 2. Connection Modes and Network Topology 2.3.3 Static IP You can use static IPs in any environment—managed or unmanaged. PCoIP devices have default, fallback static IP addresses. The default, static IP addresses are as follows: zero client—192.168.1.100 host card—192.168.1.101 Subnet—255.255.255.0 Gateway—192.168.1.1 These default, known addresses ensure that users can move zero clients between networks and always have a known IP address. See 6.1.
2.4 Network Topology method. A check mark () indicates that you can use an IP address assignment technique in an environment, and an X indicates that you cannot use a technique in the environment. Table 3.
Chapter 3. Network Considerations This chapter shows network-related items to consider when preparing for deployment and shows settings to configure for optimal network performance. The focus is on network bandwidth and zero client and host card settings that you can configure. Additional topics include a brief note about network architecture and the ports and protocols that devices use. See PCoIP Protocol Network Design Checklist (TER1105004) at techsupport.teradici.com/ for additional information. 3.
3.2 Overview and Terms Bandwidth The capacity of the network, or the quantity of bits per second that can travel through the transfer medium. Round-trip latency The time it takes a packet to travel from one device to a destination and the reply to come back to the original host. For example, the ping command measures round-trip latency. Bridge A network device used to transparently connect two sides of the same network. The two network halves that run through the bridge appear as the same network.
Chapter 3. Network Considerations Screen updates Mouse and keyboard responsiveness Video streaming quality including pixilation and blocking Mass storage (USB thumb drive) responsiveness 3.3 User Experience Figure 11. Latency and user experience The figure above shows that acceptable performance is around 17 milliseconds latency (34 milliseconds round trip). The point where users can perceive a delay is 12 milliseconds (24 milliseconds round trip).
3.4 Bandwidth Effects on Usability Non-interactive usage: For USB devices, increased latency nearly linearly affects the performance of the device. For example, in the figure below, transferring a 4-MB file to a USB drive, the following numbers can be seen by stepping through latency increases. NOTE: Although WAN acceleration products cannot affect the video portion of PCoIP traffic, they can optimize and improve USB performance. Figure 12. Latency affecting transfer speed 3.
Chapter 3. Network Considerations 3.5 Typical Bandwidth Usage In a PCoIP environment, bandwidth consumption is determined by: Dynamic screen content Audio USB traffic 3.5.1 User Types and Bandwidth Consumption Bandwidth usage in a PCoIP environment primarily depends on the computing tasks that zero client users perform. Zero client users are generally grouped in the following types.
3.6 Bandwidth Limiting NOTE: The values shown below represent bandwidth consumption only when a user is performing work of the specified type. User types can change throughout the day depending on the activity a user performs at a given time. For example, a power user is effectively a task user when they check their email—even if a CAD application is displayed on a second monitor and is waiting for interaction. Table 4.
Chapter 3. Network Considerations Figure 13. The Web interface Bandwidth page 3.6.1 Device Bandwidth Limit This field defines the maximum bandwidth peak for the PCoIP system. The bandwidth setting defines the bandwidth based on which side is sending data: On the host side: from the host to the client (e.g., graphics data) On the client side: from the client to the host (e.g., USB data) The usable range of the device bandwidth is 1000 to 220,000 kbps.
3.6 Bandwidth Limiting Setting Device Bandwidth Limit to 0 configures the PCoIP processor to adjust the bandwidth depending on network congestion. If there is no congestion, there is no limit on bandwidth. That is, the processor uses the maximum rate available. We recommend setting this field to the limit of the network connected to the client and host. NOTE: The setting in this field is applied immediately after you click Apply. 3.6.
Chapter 3. Network Considerations 3.6.4 Image Quality The Image page enables you to adjust the image (graphics) quality of the PCoIP session. Figure 14. Image configuration page The table below shows each setting on the Image page. Table 5. Image page settings Field Use Client Image Settings Description This field is only available from the host. When enabled: Image settings on this page are not editable. The settings that appear (grayed out) are those stored for the host in flash memory.
3.6 Bandwidth Limiting Field Description moving the slider towards Reduced allows higher frame rates. Moving the slider towards Perception-Free allows for higher image quality. When network bandwidth is not constrained, the PCoIP system maintains perception-free quality regardless of the Minimum Image Quality parameter. NOTE: The Minimum Image Quality must be less than or equal to the Maximum Initial Image Quality.
Chapter 3. Network Considerations Field Description only parameter. This setting does not work in PCoIP sessions with VMware View virtual desktops running release 5.0 or earlier. Disable Build to Lossless Leave this field unchecked to retain build to lossless. In these cases, the images continue to be built to a lossless state. This is the default (recommended) setting. WARNING: Enabling the Disable Build to Lossless feature will degrade the image presented to zero client users.
3.8 Port and Protocol Requirements 3.8 Port and Protocol Requirements The following table details ports used in deployments using PCoIP technology. The table indicates in the Interface column if the open ports are required or are optional. Table 6. Ports and protocols Interface Protocols Port(s) Encrypted Authenticated Purpose IP Network DHCP 67, 68 (UDP) n/a n/a Dynamic IP address.
Chapter 3. Network Considerations Interface Protocols Port(s) Encrypted Authenticated Purpose HTTPS/SOAP/XML (TCP with SSL/TLS) 50000 (TCP) Yes Yes Connection Management Interface (CMS) DNS 53 (UDP) n/a n/a Used to lookup IP address of CMS (if FQDN specified). No No Obtains encrypted firmware binary image file from specified FTP server. Yes Yes Media traffic channel (USB/audio/video) between TERA1100 and TERA1200. IP protocol 50 per RFC. Yes Mutual authentication using X.
Chapter 4. Initial Setup 4.1 Caution Statements Improper connection, mounting, or use of this product could result in component failure or undesired interference. Read the following caution statements before setting up and operating zero clients. Do not connect to AC power until all other connections are made, including the power adapter. Connecting or disconnecting components or equipment on the back panel when the zero client is receiving AC power can cause power surges and damage the device.
Chapter 4. Initial Setup 4.2 Mandatory Mounting, Cooling, and Airflow Provisions This section describes important provisions to ensure that there is adequate and proper airflow and cooling for zero clients. 4.2.1 Ensuring Adequate Clearance around Zero Clients Ensure that there is at least 4 inches of space around and above zero clients. Horizontal Mounting (Side View) Horizontal Mounting (Overhead View) 4” minimum 4” minimum 4” min 4” min 4” min 4” min Front Figure 15.
4.2 Mandatory Mounting, Cooling, and Airflow Provisions 4.2.2.1 Desktop Mounting When placing a zero client on top of a desk or other flat, unenclosed surface, ensure that: The open vent faces up (as described in the following section) There is at least 4 inches of space around edges of the zero client. There is open space above the zero client. You do not stack any objects on top of the zero client, including any paper or USB peripherals (such as hard drives).
Chapter 4. Initial Setup 4.2.2.2 Horizontal Mounting: Open Vents Must Face Up ClearCube zero clients are typically mounted horizontally, as shown below. TERA1-based zero clients have diamond-shaped vents on both sides, and TERA2-based zero clients have diamondshaped vents on the top. Open vents reveal the interior of the zero client (the open vent is located on the top of most zero clients. The closed vent on the bottom of TERA1-based zero clients is sealed with a grey, metal plate.
4.3 Cabling Figure 18. Typical network cabling diagram 4.3.2 A-Series Chassis Ports The picture below shows the rear of the A3100 chassis and the expansion backplane port assignments. Connect cables from zero clients to the PCoIP ports on the rear of the chassis Connect cables for standard blade network traffic to the PRI (primary) and SEC (secondary) network ports (depending on blade support as noted below). ClearCube Technology, Inc.
Chapter 4. Initial Setup A6106D Blade A6105D Blade Dedicated PCoIP Ethernet Ethernet Dedicated PCoIP Ethernet Unsupported Figure 19. A3100 chassis backplane network port assignments 4.3.3 R-Series Chassis Ports (Network Module) The picture below shows the rear of the R4300 chassis and the EP2 Pass-Thru Network Module port assignments. Connect cables from zero clients to Secondary ports on the rear of the chassis.
4.4 Mandatory Network-Related Settings PCoIP in Secondary Ports Blade Data in Primary Ports EP2 Network Module R4300 Chassis Figure 20. R4300 chassis network port assignments 4.4 Mandatory Network-Related Settings The following sections describe mandatory network-related requirements for zero clients, host cards, and network devices in copper and in fiber networks. ClearCube Technology, Inc.
Chapter 4. Initial Setup 4.4.1 Copper-Based Devices In deployments using PCoIP technology, the duplex mode and link speed settings for all connected devices must be the same. When deploying devices in a copper network, ensure that: You set all devices to auto-negotiate (zero clients, host cards, and other network devices such as switchers, media converters, and so on). Instructions for zero clients and host cards are provided below.
4.4 Mandatory Network-Related Settings how to configure negotiation and flow control settings on Cisco Catalyst® switches to connect with fiber zero clients. NOTE: Only TERA1-based devices need to disable auto-negotiation as shown in the example configuration below. TERA2-based devices do not need to disable auto-negotiation. NOTE: The configuration below is not applicable to Cisco Nexus® switches.
Chapter 4. Initial Setup The list below shows operating systems that Teradici Host Driver Software supports. Windows 8.1, 64-bit Windows 7, 32- and 64-bit Windows Vista, 32- and 64-bit Windows XP SP2, 32- and 64-bit Windows Server 2008, Server 2008 R2 Windows Server 2003 (not supported by V5140 host cards) Linux® is supported but has not been tested.
4.5 Image Creation Requirements NOTE: If you are re-imaging a blade or installing a custom image on ClearCube blades, you must install components in the order listed below. Failure to do so can cause unsupported behavior. The following list details items and steps required when imaging and configuring ClearCube blades that use PCoIP technology. Ensure that you install items and perform steps in the order listed below. 1.
Chapter 4. Initial Setup for blades with a V54x0-series host card and a GPU card, install a driver for the GPU. 10. Optionally, install PCoIP Host Driver Software on the blade or VM containing a host card. The version of the PCoIP Host Software must match the host card and the zero client firmware versions. 11. Install drivers for any additional peripherals or hardware. 12. Now connect to a zero client (as described in this guide).
4.6 Viewing Pre-OS Video (BIOS Configuration) and USB Input NOTE: These instructions assume that devices are connected to an imaging network or other network with a DHCP server to provide IP addresses for the blade’s PCoIP host card and for the zero client. MAC addresses are specified on labels on the side of the blade and on the zero client. To identify the blade host card to connect to from the zero client, you might need to consult DHCP tables.
Chapter 4. Initial Setup 7. Connect a power cable to the external power connector at the rear of the blade and then plug the cable into a power outlet. Continue by connecting the power adapter to the zero client and then plugging the cord into a power outlet. 8. Power on the blade and then the zero client by pressing the power button on the front of each device. 9. From the monitors connected to the zero client, click the Connect button.
4.6 Viewing Pre-OS Video (BIOS Configuration) and USB Input Setting up Devices 1. Be sure to have the following: R-series blade in an R-series chassis. Note the MAC address shown on a label (VIDEO V5xxx CONFIGURATION) on the side of the blade. This is the MAC address you will select when connecting from the zero client. Ethernet cables, zero client power supply, and a ClearCube zero client. A switch connected to a DHCP network. A USB keyboard and mouse. Monitors and monitor power cables.
Chapter 4. Initial Setup 6. Use an Ethernet cable to connect the zero client to a network switch on the same subnet as the host card (that is, the subnet that the blade is on). 7. Connect monitors, a mouse, and a keyboard to the zero client. 8. Connect the zero client power adapter to the zero client and then plug the cord into a power outlet. Continue by configuring the zero client as shown below. Configure the Zero Client 1. Press the zero client’s power button to power it on. 2.
4.6 Viewing Pre-OS Video (BIOS Configuration) and USB Input 3. Press any key on the keyboard to restart the remote blade. The zero client should display the message Waiting for host to wakeup, please wait…. 4. Press the F2 key several times to enter the BIOS setup utility. 5. Configure your BIOS as appropriate for your environment. After performing BIOS configuration steps, press F10 to save and exit the BIOS. The blade now boots to the OS.
Chapter 4. Initial Setup The picture below shows the C/Port connectors in the Connect Bay Module, located on the rear of the chassis on the far left side. Figure 22.
Chapter 5. Zero Client Controls and Supported Power States The following sections describe: Zero client power buttons and indicators Ways to manage blade power (host power states) in a PCoIP environment 5.1 Buttons and Indicators The following subsections describe zero client buttons and indicators. The figure below shows the buttons and indicators common to zero clients, unless noted otherwise. Other components, such as USB ports and audio connectors, are omitted for clarity.
Chapter 5. Zero Client Controls and Supported Power States The list below shows indicators and front panel button operations: Power Button Colors Green (solid): device is powered on. Green (blinking): PCoIP session is sleeping. Press any key on the keyboard to wake the session. Orange: device is in low-power state and wake-on-LAN (WoL) or wake-on-USB (WoUSB) is enabled. ClearCube Sentral or third-party utilities can provide WoL and WoUSB features for devices.
5.2 Power Operations 5.2 Power Operations Power management of the host system is handled primarily by the host TERA processor. 5.2.1 Soft Power Off (S5) Graceful shutdowns through the operating system (OS), the zero client’s power button (short press), the blade (host’s) front panel power button, and the host card’s Web interface will cause the system to enter S5. During this operation the session enters a sleep state.
Chapter 5. Zero Client Controls and Supported Power States might be displayed while the session is resuming and might not be visible. Video typically resumes at the OS login. 5.2.5 Standby (S3) ClearCube host cards support Standby (or Sleep) power state S3. 5.2.6 Sleep (S1 and S2) Host cards do not support Sleep power state S1 and Sleep power state S2.
Chapter 6. Configuring Devices, Setting Peers, and Connecting You must configure zero clients and host cards when deploying them. To provision a zero client: 1. Determine the IP address structure for your environment and determine the IP addresses of the blade, the host card, and the zero client as described below. 2. Configure the PCoIP processors on the zero client and on the host card (for example, enabling 64-bit audio, specifying a static IP, and so on).
Chapter 6. Configuring Devices, Setting Peers, and Connecting 6.1 Finding a Device’s IP Address and MAC Address This section describes how to find the IP address and MAC address of a zero client or host card, which is necessary for many normal tasks, including the configuration tasks described later in this chapter. NOTE: The IP address of a zero client or host card using PCoIP technology is not the same as the external IP address of the device’s network interface, as noted in the following section.
6.1 Finding a Device’s IP Address and MAC Address SLP Discovery Independent of Connection Mode Use CMS (Sentral) Zero Client with SLP Discovery Mode Use OSD (Device GUI) Use Fallback IPs (Devices Must Be Set for DHCP) Figure 24. Techniques for discovering device IP addresses 6.1.
Chapter 6. Configuring Devices, Setting Peers, and Connecting To find a zero client IP address or MAC address: Perform the following steps from Sentral (note that you must discover your zero client, optionally install the Sentral Host Agent on your blade, and discover your host card before performing this step for the first time; see Sentral Administrator’s Guide for more information): 1.
6.1 Finding a Device’s IP Address and MAC Address To find a host card IP address or MAC address: Perform the following steps from the Sentral menu: 1. From the Sentral menu, click Management > Hosts > PCoIP Hosts to display the PCoIP Hosts Management screen, as shown in the following figure. 2. Record the host IP address (shown in the IP Address column) or the MAC address (shown in the MAC Address column).
Chapter 6. Configuring Devices, Setting Peers, and Connecting 6.1.3 Finding Zero Client IP or MAC Address Using OSD You can use the zero client On-Screen Display (OSD) to identify its IP address. To find the address, perform the following steps. 1. Ensure the zero client is powered on and is set up as described in “Chapter 4 Initial Setup” on page 33. 2. From the OSD menu in the upper-right portion of the screen, click Options > Configuration to display the Configuration page. 3.
6.1 Finding a Device’s IP Address and MAC Address You can use this IP address to specify a peer device for your zero client or host, as described in 6.5 “Specifying a Device’s Peer” on page 68. 6.1.5 Using Default Device Fallback IP Addresses ClearCube PCoIP devices have default IP addresses to ensure you can always access the device.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Use one or more switches to connect the device to a computer (ensuring that no DHCP servers can access the device through any switches). 4. Power on the device. Wait 120 seconds for the device to fall back to its default IP address. 5. Verify that the device is using its default IP address by typing the IP address in a Web browser.
6.3 Using the Web Interface Table 7. Interfaces for device configuration Web Interface On-Screen Display (OSD) Zero client Host card X Device The following sections show and describe each device interface. 6.3 Using the Web Interface PCoIP devices provide a Web interface that you can use to configure all zero client and host features. The Web interface supports the following browsers: Mozilla® Firefox® 3.0 and higher Internet Explorer 7.0 and 8.0 Google® Chrome 2.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Zero Client Label Figure 27. Zero client label on the Web interface Host Card Label Figure 28.
6.3 Using the Web Interface To display the zero client and host Web-based interface, you must specify the device’s current IP address in a Web browser. For information about how to find a device’s IP address, see 6.1 “Finding a Device’s IP Address and MAC Address” on page 56. To access a client or host Web interface, ensure that you have: 1. Open a Web browser on a computer on the same subnet as the zero client or host card you want to access. 2.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Options Menu Connect Button Figure 29. On-Screen Display (OSD) The Connect screen provides the following: A Connect button (shown below) that users click to start a session between a zero client and host device. Figure 30. Connect button on OSD 66 A local zero client interface, similar to the Web interface, with a subset of the Web interface’s features.
6.4 Configuring Blades Figure 31. OSD interface 6.4 Configuring Blades The following sections describe blade configuration options. 6.4.1 Blade Video Settings See “6.4.1 Blade Video Settings” on page 67 for instructions about video configuration. 6.4.2 Enabling Audio on a 64-bit OS NOTE: The 64-bit audio setting shown below only applies to PCoIP using Teradici firmware version 4.2.0 and lower.
Chapter 6. Configuring Devices, Setting Peers, and Connecting 2. Click Yes to dismiss the security alert, and then click Log In. 3. From the main menu, click Permissions > Audio. 4. Ensure that Enable Microsoft® Windows Vista®/Windows® 64-bit Mode is selected. Click Apply. 5. The Web interface displays a success message. Click Continue. 6. Restart the PCoIP session to make your changes. a. From the main menu, click Diagnostics > Session Control and then click Disconnect.
6.5 Specifying a Device’s Peer 3. Specify the peer for the device. NOTE: You can specify Accept Any Peer for host cards only. If you specify this setting, do not specify a peer IP address or MAC address for the host card. From the zero client OSD or host Web interface, click Configuration > Session and specify the following depending on the session type you want. Zero client: – Direct to Host (this option enables zero clients to connect to the same host every time): a.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Figure 32. Session page 4. Verify that the devices are peers. To verify that devices are set as peers, click Connect from the OSD and select the host to which to connect. Perform either one of the following steps: Click Configuration > Session and verify the address shown as the Peer IP Address. —OR— 70 Click Diagnostics > Session Control and verify the Peer IP Address is the peer you specified in the previous step.
6.6 Connecting to a Device Current Peer IP Address Figure 33. Session Control page showing current peer IP 6.6 Connecting to a Device The following sections describe how to deploy and connect zero clients and hosts for each of the methodologies shown in Table 3 on page 19 (and repeated in each of the following sections). The concepts and terms discussed below (such as managed environment, CMS, reserved DHCP, and so on) are discussed in 2.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Table 8. Unmanaged, static IP with static assignment Management Managed Environment Unmanaged Environment Peer Assignment Network Topology CMS Assignment SLP Discovery Static Assignment × Static IP Direct Static IP Connection × IP Assignment DHCP Shared Reserved DHCP The following figure shows the architecture described in this section. Figure 34. Unmanaged static IPs with static assignment 1.
6.6 Connecting to a Device a. Connect one end of a CAT5 or CAT6 Ethernet cable to the appropriate port on your chassis. R4300 chassis—insert the cable in the Secondary Network port. A3100 chassis—insert the cable in the PCoIP port. b. Connect the other end of the cable to a network switch on a known subnet. 3. Connect the zero client to a network switch. a. Connect one end of a CAT5 or CAT6 Ethernet cable to the RJ-45 connector on the zero client. b.
Chapter 6. Configuring Devices, Setting Peers, and Connecting f. From the Session tab, select IP address in the Identify Peer by line. Specify the following in the appropriate fields: Identify Peer by—The host card IP address Peer MAC Address—The host card MAC addresses (printed on a label on the side of the blade) g. Click Apply and then click OK to close the Configuration page. You can now continue to provision the host card on the blade. 5. Provision the host card on the blade. a.
6.6 Connecting to a Device h. Click Configuration > Monitor Emulation. Select the monitor emulation option for both monitors (DVI 1 and DVI 2). i. Click Apply and then click Reset. The host card displays a power state message. Click OK. Briefly press and hold the reset button on your blade to reset it. You can now start your zero client and click Connect to connect to your blade. 6.6.
Chapter 6. Configuring Devices, Setting Peers, and Connecting The following figure shows the architecture described in this section. Figure 35. Unmanaged SLP assignment with direct connection (no network connection) NOTE: You must have a physical connection to a computer running a Web browser to view the PCoIP browser-based management interface. A direct connection between a host card and a zero client does not provide the Web interface.
6.6 Connecting to a Device a. Briefly press and hold the power button on the front of the zero client to power it on. The zero client displays a dialog box. b. In the upper–left corner of the page, click Options > Configuration to open the Configuration window. Click Unlock on the lower-left portion of the window to display the Unlock dialog box. Click OK to unlock the window (you should not need to type a password). c. In the Network tab, ensure that the Enable DHCP option is cleared. d.
Chapter 6. Configuring Devices, Setting Peers, and Connecting 6.6.3 Unmanaged Static IPs with Direct Connection In the following table, the PCoIP configuration described in this section is circled in red. Table 10.
6.6 Connecting to a Device NOTE: You must have a physical connection to a computer running a Web browser to view the PCoIP browser-based management interface. A direct connection between a host card and a zero client does not provide the Web interface. To use the Web interface to configure a host, connect a computer running the Web interface to the host card. After working with the Web interface, you can reconnect the zero client to the host.
Chapter 6. Configuring Devices, Setting Peers, and Connecting These values can be any value appropriate for your environment. d. Click Apply and then click Reset in the Attention dialog box to reset the zero client. e. In the upper–left corner of the page, click Options > Configuration to open the Configuration window. Click Unlock on the lower–left portion of the window to display the Unlock dialog box. Click OK to unlock the window (you should not need to type a password). f.
6.6 Connecting to a Device —OR— To enable administrators to move zero clients from one host to another without modifying the host’s peer data, leave the Accept Any Peer option selected. g. Click Apply and then click Continue. h. Click Configuration > Monitor Emulation. Select the monitor emulation option for both monitors (DVI 1 and DVI 2). i. Click Apply and then click Reset. The host card displays a power state message. Click OK. 6. Briefly press and hold the reset button on your blade to reset it.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Figure 37. Using a portable computer and switch to configure host cards and zero clients 6.6.4 Unmanaged DHCP with SLP Discovery In the following table, the PCoIP configuration described in this section is circled in red. Table 11.
6.6 Connecting to a Device The following figure shows the architecture described in this section. Figure 38. Unmanaged DHCP with SLP discovery When connecting a blade and a zero client on a network with a DHCP server, you can enable both devices to accept a dynamic IP addresses. NOTE: Ensure that your chassis and zero client are connected to a switch on a network with a DHCP server. 1. Ensure that you have set up devices as described in 4.
Chapter 6. Configuring Devices, Setting Peers, and Connecting b. Connect the other end of the cable to a network switch on the same subnet as the chassis. This switch can be the same switch used in step the previous step. 5. Configure networked devices as described in 3.8 “Port and Protocol Requirements” on page 31 and 4.4 “Mandatory Network-Related Settings” on page 39. 4. Configure the zero client. a. Briefly press and hold the power button on the front of the zero client to start it. b.
6.7 Configuring Video Settings 6.6.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Specifying the order and physical arrangement of displays in your multi-monitor setup and any additional configuration. The following sections provide high-level descriptions of video configuration steps you can perform. For comprehensive documentation about GPU driver features and interfaces, see the manufacturers’ driver documentation. NOTE: ClearCube only supports drivers included in the product.
6.7 Configuring Video Settings mirroring) displays so all monitors display the same image, extending the desktop across all monitors so you can move windows back and forth between all monitors, and turning off displays. Display order You can configure how the operating system orders the displays connected to a zero client. A simple method is to make the virtual arrangement of displays the same as their physical arrangement.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Figure 41. Setting display orientation from the Control Panel ClearCube recommends using the host’s operating system to configure display settings. For Microsoft Windows operating systems, right-click an empty portion of the host’s desktop and select Screen resolution (other Windows operating system menus can be different; display settings are available from the Control Panel).
6.8 Managing Sessions (Connections) and Device Behavior NOTE: You can use the Session Control Web interface page to connect and disconnect devices using standard static sessions only. Figure 42. Detail from the Session Control Web interface page To access the Session Control page, display the zero client or host card Web interface as described in 6.3 “Using the Web Interface” on page 63. Connect or disconnect the devices as described below.
Chapter 6. Configuring Devices, Setting Peers, and Connecting Disconnect If the connection state is Connected or Connection Pending, click the Disconnect button to end the PCoIP session. If the connection state is Disconnected, this button is disabled. After you click the Disconnect button, it is disabled. You must refresh the page to use it again. Peer IP Address The Peer IP Address displays the IP address of the peer device. The field is blank when there is no session.
6.8 Managing Sessions (Connections) and Device Behavior 7. Click Options > Configuration, and then unlock the OSD as shown above. 8. From the Session tab, select Direct to Host and specify the address of a dedicated peer (host card). 9. Click OK. The zero client must be in an unmanaged environment (that is, it cannot have a CMS specified from OSD’s Options > Connection Management page).
Chapter 6. Configuring Devices, Setting Peers, and Connecting Table 12. Sentral server configuration tags to modify Legend File A i9400.disconnect.logoff B logoff.on.i9400.disconnect Table 13.
Chapter 7. Changing Device Peers After deploying a zero client and allocating it to a host, you might need to change the host to which the zero client connects. The steps below show how to change a device’s peer. 1. Ensure that you have: Properly configured the zero client for the host to which you are connecting. For example, if you are deploying a zero client that is using a fallback IP address or a static IP address, make sure the host is on a compatible subnet and can connect to the zero client.
Chapter 7. Changing Device Peers NOTE: Disabling host discovery forces the zero client to connect to its specified peer only. The Enable Host Discovery option must be selected for the OSD to display a list of hosts to which you can connect. 7. To start a new session between the zero client and host, click Diagnostics > Session Control and click the Connect button. Alternatively, you can click the Connect button located on the local zero client GUI.
Chapter 8. Mass Storage Lockout (MSL) ClearCube devices support MSL, enabling administrators to prevent access to USB-based mass storage devices and other USB peripherals. ClearCube devices provide: Hardware-based MSL Firmware-based MSL The following list describes options for configuring MSL: R-series blades and peers: Configure MSL using a jumper on the blade motherboard. A-series blades and peers: Configure MSL using PCoIP device firmware (as shown below for all PCoIP devices).
Chapter 8. Mass Storage Lockout (MSL) R-series blades and peers When MSL is enabled on R-series blades using the motherboard jumper, MSL settings apply to the peer zero client. Blade settings cannot be overridden by any MSL settings on a connected zero client (note that you can set MSL on zero clients using a Web interface). Changes to blade MSL settings are possible only with physical access to the R-series blade.
8.2 Setting MSL on R-Series Blades See R-Series Data Center Products User’s Guide for detailed instructions about working with R-series blades. Use needle-nose pliers to move the jumper, as described in the following steps. 1. Power down the blade and remove it from the chassis (if the blade is not in an enclosure—for example, for maintenance—ensure that power is disconnected). 2.
Chapter 8. Mass Storage Lockout (MSL) Figure 44. JP6 MSL header in default position on R3080D motherboard 3. Use needle-nose pliers to move the jumper. Perform one of the following steps: To enable MSL Move the JP6 jumper to pins 1 and 2. This setting prevents access to USB devices connected to the blade or to the zero client. —OR— To disable MSL Move the JP6 jumper to pins 2 and 3. This setting enables access to USB devices connected to the blade or to the zero client. 4.
8.3 Setting MSL on A-Series Blades 8.3.1 MSL on A6106D and Higher Enable MSL on A-series blades A6106D and higher using PCoIP device firmware as described in 8.4 “Setting MSL from a Zero Client or Host Card Web Interface” on page 100 below. 8.3.2 MSL on A6105D and Lower To enable MSL on A-series blades A6105D and lower with TERA1-based processors, move a DIP switch on the blade’s host card (or the MSL jumper on V5120 host cards).
Chapter 8. Mass Storage Lockout (MSL) V5320 Card 2 3 4 DIP Switch 1 V5340 Card A6105D Blade MSL Enabled USB Devices Accessible USB Access Prohibited 1 1 2 2 3 3 4 4 MSL Disabled Figure 45. MSL DIP switch on V5320 host card in A6105D blade 5. Replace the blade cover and screws, then return the blade to the chassis and power it on. After connecting to the blade, all USB devices are disabled from the zero client. 8.
8.4 Setting MSL from a Zero Client or Host Card Web Interface USB plug events are blocked in the PCoIP zero client hardware for unauthorized USB devices. The host card or VM cannot see or access the device for an additional layer of security. The USB page is available on the host card and on the zero client but the host USB permissions have a higher priority and update the client USB permissions. It is strongly recommended to set the USB permissions only on the host when connecting to a PCoIP host card.
Chapter 8. Mass Storage Lockout (MSL) The following table details each parameter in the USB page. Table 14. USB page parameters Parameter Authorized Devices Description Specify the authorized USB device for the host card and the zero client. Two buttons let you customize this white list. Add New: add a new device or device group to the list. This allows USB authorization by ID or by Class.
8.4 Setting MSL from a Zero Client or Host Card Web Interface The following table summarized the USB authorization entry type and the associated data fields. Two buttons let you customized this white list. Table 15.
Chapter 9. Updating Device Firmware ClearCube recommends always using the same firmware version on zero clients and host cards. See PCoIP Firmware Compatibility Guide, available on the ClearCube Support site, for detailed information about PCoIP firmware versions and compatibility. You can update firmware on ClearCube PCoIP devices by uploading self-installing firmware files to zero clients and hosts. Devices (except as noted below) use files with the .ALL file extension.
9.2 Identify Firmware on Device You Are Updating 9.1 Update Prerequisites Ensure you have access to the location of the PCoIP firmware file you are installing. If you are using Sentral in a managed environment, ensure that no users are logged in to the device you are upgrading. 9.2 Identify Firmware on Device You Are Updating ClearCube recommends always using the same firmware version on zero clients and host cards.
Chapter 9. Updating Device Firmware 3. Make a note of the version number of the firmware you are updating. In the final step, you will verify that the firmware version shown here matches the version you are installing. 9.3 Upload Firmware to Device ClearCube recommends always using the same firmware version on zero clients and host cards. See PCoIP Firmware Compatibility Guide, available on the ClearCube Support site, for detailed information about PCoIP firmware versions and compatibility. 1.
9.5 Troubleshooting Firmware Updates You can now continue to verify your firmware installation as described in 9.2 “Identify Firmware on Device You Are Updating” on page 105. 9.4.2 Host Card 1. Click Reset to reset the PCoIP processor, and then click OK. After several moments the device displays the message: The PCoIP processor will reset on the next host system restart; your changes will take effect then. Are you s ure you want to proceed? 2. Click OK to continue.
Appendix A: Best Practices The following list details items to consider and issues to address to ensure deploy and use your zero clients successfully. Recommended deployments The following table shows the recommended deployment option in a shared, managed deployment; in a shared, unmanaged deployment; and in a direct, unmanaged environment. Table 16.
Troubleshooting Firmware Updates the correct host. Administrators can also use the auto-reconnect feature in this environment. Unmanaged environment with a shared network (static IP): The benefits of using static IP addresses in a shared, unmanaged environment are similar to those described above for reserved DHCP addresses. When using static IP addresses, a DHCP server is not required in the environment.
Appendix A: Best Practices cause zero clients to overheat and damage the zero client (ambient temperature around zero clients should never exceed 35 degrees Celsius). See 4.2 “Mandatory Mounting, Cooling, and Airflow Provisions” on page 34 for more information. Power states: zero client, host card, and operating system Be aware of the power management settings (power states) that your host card supports.
Appendix B: Troubleshooting This section describes common troubleshooting tasks. Can’t set or change peer for a device When you try to specify or change a device’s peer using the Web interface and click Apply, the page reloads but the new peer data is not applied. Resolution Make sure that the device does not have an active session. From the Web interface, click Diagnostics > Session Control. If the Connection State is Connected or Connection Pending, click Disconnect.
Appendix B: Troubleshooting Figure 48. The Session Control Web interface page “No route to host” message If you are working with a zero client that is connected to blade using a static session (through static IP addresses or using DHCP reservations), you might see this message. Resolution The zero client and the host cannot establish a connection. Try any of the following: You might see this message if you attempt to establish a connection before the devices initialize after boot up.
Host cards do not respond to ARP requestsTroubleshooting Firmware Updates For more information, see Chapter 2 “Connection Modes and Network Topology” on page 12 and “Configuring Zero Clients and Host Cards” on page 62. PCoIP does not support all power states Several power states do not provide power to all system components, preventing PCoIP components from establishing sessions, maintaining sessions, and from receiving wake requests.
Appendix B: Troubleshooting Connected to 100-Mbit, full-duplex switch: poor performance, not full-duplex To ensure 100-megabit, full-duplex transmission between a host and a zero client, set any network switches connecting the blade and the zero client to automatic negotiation.
Zero client video degrades or displays do not workTroubleshooting Firmware Updates To prevent this issue: Avoid disabling the zero client's DHCP setting. If you specify a static IP address for the host card, ensure that you record it. Ensure that the zero client's IP address and default gateway are on the same subnet.
Appendix B: Troubleshooting Resolution Ensure that there is at least 4 inches of clearance around each edge of the zero client and two inches of clearance above the zero client. If the zero client is improperly enclosed in a microenvironment (for example, in a drawer or in a desk cable tray), the ambient temperature can easily rise above the supported operating level. See 4.
Appendix C: PCoIP Management and ClearCube Sentral You can use ClearCube’s Sentral to manage PCoIP devices, virtual machines, thin clients, and other clients and hosts in your environment.
Appendix D: Zero Client and Host Card Web Interfaces Zero client and host card Web interfaces and OSD are detailed in PCoIP Administrator’s Guide, available on the Teradici support site.
Updating Device Firmware Rev C 1.2.03.03.2014 ClearCube Technology, Inc. P/N G0400087 119 clearcube.
