cisco virtualization experience client 2111/2211 pcoip ... · contents iv cisco virtualization...

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide for 3.3.1_327April 27, 2012

Text Part Number: OL-25151-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide© 2011-2012 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

iiiCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

C O N T E N T S

Preface vii

Overview vii

Audience vii

Organization vii

Related Documentation viii

Obtaining Documentation, Obtaining Support, and Security Guidelines viii

Document Conventions viii

C H A P T E R 1 Introduction 1-1

Menu and Page Overview 1-1

C H A P T E R 2 Administrative Web Interface Overview 2-1

About the Page Layout 2-1

Supported Web Browsers 2-2

Administrative Web Interface IP Address 2-2

Administrative Web Interface Security 2-3

Installing the CA Root Certificate 2-3

Installing the CA Root Certificate in Internet Explorer 2-3

Installing the CA Root Certificate in Firefox 2-3

Logging In 2-4

Viewing the Home Page 2-5

About the Administrative Web Interface Menus 2-6

C H A P T E R 3 Working with the On Screen Display 3-1

About the Connect Screen 3-1

Connect Button 3-2

About the OSD Options Menu 3-3

C H A P T E R 4 Cisco VXC PCoIP Configuration 4-1

Configuring the Device 4-1

Initial Setup Web Page 4-1

Step 1: Audio 4-2

Step 2: Network 4-3

Contents

ivCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Step 3: Session 4-3

Step 4: Apply Changes 4-3

Configuring the Network Parameters 4-3

Adding Custom Information to the Device 4-6

Enabling or Disabling Connection Management 4-7

Configuring for Use with a VMware View Connection Server 4-9

Configuring the VMware View Advanced Parameters 4-11

Configuring the VMware View Kiosk Mode Parameters 4-14

Configuring the Discovery Mechanism 4-15

Configuring the SNMP Agent 4-16

Configuring the Connections 4-17

Identify Peer By 4-19

Controlling Bandwidth for PCoIP Sessions 4-19

Configuring Device Parameters for RDP 4-21

Setting the User Interface Language 4-23

Configuring the OSD Screen-Save Timeout 4-24

Adjusting the Image Quality 4-25

Enabling Monitor Emulation 4-27

Enabling the Host Driver Function 4-28

Configuring the NTP Parameters 4-28

Updating the Password for a Device 4-29

Password Reset Window 4-30

Resetting the Parameters to Factory Defaults 4-31

Configuring the EDID Override Mode 4-31

Setting up User Permissions 4-32

Specifying USB Devices 4-33

Configuring the Audio Parameters 4-35

Setting up the Client Power-off Permissions 4-36

Using the Diagnostic Tools 4-36

Viewing and Clearing Event Log Messages 4-36

Session Control 4-37

Viewing PCoIP Protocol Statistics 4-38

Working with the Host CPU web page 4-40

Generating an Audio Test Tone from the Client 4-41

Viewing a Test Pattern on the Client Display 4-41

Resetting the Device Processor 4-42

Determining if a Device is Reachable 4-43

Viewing Device Information 4-44

Viewing the Version Information 4-44

Contents

vCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Viewing the Attached Devices 4-46

Uploading to the device 4-47

Uploading the Firmware to the Device 4-47

Uploading a Logo to the Device 4-48

Configuring the User Settings 4-49

Configuring the Mouse Settings 4-49

Changing the Keyboard Repeat Settings 4-49

Image Tab 4-50

Configuring the Display Topology 4-50

C H A P T E R 5 About the Overlay Pages 5-1

Network Connection Lost Overlay 5-1

USB Device Not Authorized Overlay 5-1

USB Over Current Notice Overlay 5-2

Half-Duplex Overlay 5-2

Video Source Overlays 5-2

A P P E N D I X A Usage Examples A-1

Bandwidth and Image Configuration Example A-1

Configuring the Client Bandwidth Limit to 25 Mbps A-2

Configuring Image Properties A-4

Configuring the Client Bandwidth Limit to 0 Mbps (No Limit) A-6

USB Permissions Example A-7

Authorizing USB Device By Class A-7

Authorizing USB Device By Vendor ID and Product ID A-8

A P P E N D I X B Client Language and Keyboard Support B-1

A P P E N D I X C Cisco VXC 2111/2211 Power Considerations C-1

Available Power on USB Ports C-1

USB Hub Support C-1

PoE Power Negotiation C-2

Cisco VXC 2111 Power Support C-2

Cisco VXC 2211 Power Support C-3

Cisco VXC 2211 Base LED Behavior C-3

Power Consumption C-4

Contents

viCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

viiCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Preface

OverviewCisco Virtualization Experience Clients (VXC) 2111 and 2211 run PC over IP (PCoIP) firmware for operation in PCoIP networks. The Cisco VXC clients are highly optimized zero clients that provide ultra-fast access to applications, files, and network resources available on machines hosted by a PCoIP infrastructure.

Note Cisco VXC 2111/2211 clients provide Remote Desktop Protocol (RDP) configuration options. However, Cisco does not provide support for RDP network implementations for the Cisco VXC 2111/2211.

AudienceThis guide is intended for administrators of Cisco VXC running PCoIP. It provides information and detailed system configurations to help you design and manage a PCoIP environment.

OrganizationThis manual is organized as described in the following table.

Chapter Description

Chapter 1, “Introduction” Describes the manual.

Chapter 2, “Administrative Web Interface Overview”

Provides an overview of the Administrative Web Interface.

Chapter 3, “Working with the On Screen Display” Provides an overview of the On Screen Display (OSD).

Chapter 4, “Cisco VXC PCoIP Configuration” Describes the Cisco VXC client configuration using PCoIP Administrative Web Interface and On Screen Display.

Chapter 5, “About the Overlay Pages” Describes the user message Overlay Windows.

Appendix A, “Usage Examples” Describes examples of setting up clients.

viiiCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Preface

Related DocumentationFor more information, see the documents available at the following URLs:

Cisco Virtualization Experience Client 2000 Series

http://www.cisco.com/en/US/products/ps11499/tsd_products_support_series_home.html

Cisco Virtualization Experience Client Manager

http://www.cisco.com/en/US/products/ps11582/tsd_products_support_series_home.html

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

Document ConventionsThis document uses the following conventions:

Appendix B, “Client Language and Keyboard Support”

Describes the languages and keyboards supported by the clients.

Appendix C, “Cisco VXC 2111/2211 Power Considerations”

Describes the Power over Ethernet (PoE) support for the Cisco VXC client.

Chapter Description

Convention Description

boldface font Commands and keywords are in boldface.

italic font Arguments for which you supply values are in italics.

[ ] Elements in square brackets are optional.

{ x | y | z } Alternative keywords are grouped in braces and separated by vertical bars.

[ x | y | z ] Optional alternative keywords are grouped in brackets and separated by vertical bars.

string A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

screen font Terminal sessions and information the system displays are in screen font.

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

ixCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Preface

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Warnings use the following convention:

boldface screen font Information you must enter is in boldface screen font.

italic screen font Arguments for which you supply values are in italic screen font.

^ The symbol ^ represents the key labeled Control—for example, the key combination ^D in a screen display means hold down the Control key while you press the D key.

< > Nonprinting characters, such as passwords are in angle brackets.

Convention Description

Warning IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071

SAVE THESE INSTRUCTIONS

xCisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Preface

C H A P T E R

1-1Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

1Introduction

As a user or administrator you can interact with your Cisco VXC clients through the embedded HTTPS web interface (the Administrative Web Interface) and On Screen Display (OSD). To minimize the total learning curve and maximize the accessibility, the web interface and OSD are organized as similarly as possible and are structured in a task-oriented fashion.

The Administrative Web Interface and the OSD let you configure the client through the GUI. With the OSD, messages appear overlaid on the user display as required.

Note This document describes the interface for Cisco VXC Clients running PCoIP. This document does not describe the Administrative Web Interface for PCoIP software integrated into products such as VMware View.

The configuration features are also available through some connection brokers and the Cisco VXC Manager console (web-based tool used to manage multiple PCoIP endpoints). These features are not described in this guide. For more information on the Cisco VXC Manager, see the Administration Guide for Cisco VXC Manager.

This document has four main sections:

• Administrative Web Interface Overview provides on overview of the Administrative Web Interface.

• Working with the On Screen Display provides an introduction to the On Screen Display (OSD).

• Cisco VXC PCoIP Configuration details the Cisco VXC client configuration using the PCoIP Administrative Web Interface and the On Screen Display (OSD).

• About the Overlay Pages discusses the user message overlay windows.

The Appendix contains:

• Appendix A, “Usage Examples”

• Appendix B, “Client Language and Keyboard Support”

• Appendix C, “Cisco VXC 2111/2211 Power Considerations”

This document is intended to give administrators and users a working understanding of a PCoIP system.

Menu and Page OverviewThe Administrative Web Interface and OSD have various menus and pages. The following tables list each the pages according to their menus as well as if they are available in the Administrative Web Interface, OSD, or both.


OL-25151-01

Chapter 1 IntroductionMenu and Page Overview

Note Many of the pages available from the OSD include a subset of parameters that are available in the Administrative Web Interface.

Note The pages marked with an asterisk (*) are not applicable to Cisco VXC.

Table 1-1 Configuration Menu

Page Name Web, OSD, or Both

Initial Setup Web

Network Both

Label Both

Connection Management Both

VMware View Both

VMware View Advanced (in OSD, this page is available from the VMware View page)

Both

VMware View Kiosk Mode (in OSD, this page is available from the VMware View page)

Both

Discover Both

SNMP Web

Sessions Both

Bandwidth Web

RDP Both

Language Both

OSD Both

Image (The Web Image page is available form the User Settings menu.)

Web

Monitor Emulation* Web

Host Driver Function* Web

Time Web

Password Web

Reset Parameters Both

Display OSD

USB Web

Audio Web

Power Web


OL-25151-01


Table 1-2 Permissions Menu


USB Web

Audio Web

Power Web

Table 1-3 Diagnostics Menu


EventLog Both

Session Control Web

Session Statistics Both

Host CPU* Web

Audio Web

Display Both

PCoIP Both

Ping OSD

Table 1-4 Info Menu


Version Both

Attached Devices Web

Table 1-5 Upload Menu


Firmware Web

OSD Logo Web

Table 1-6 User Settings Menu


Mouse OSD

Keyboard OSD

Image OSD

Display Topology OSD


OL-25151-01


C H A P T E R


OL-25151-01

2Administrative Web Interface Overview

The PCoIP Administrative Web Interface lets you interact with the device remotely using an Internet browser.

About the Page LayoutFigure 2-1 shows an example of the client page. It has seven basic regions:

• Log Out—Log out of the Administrative Web Interface

• PCoIP Zero Client—Displays Cisco VXC PCoIP endpoint information

• Home—Click to navigate to the Home web page

• Drop-down menus—The toolbar at the top part of the page lets you easily find pages through its menus: Configuration, Permissions, Diagnostics, Info, and Upload

• Web page information—Displays the title and summary of the current web page

• Data field—A configurable or read-only parameter (inline help appears when appropriate)

• Apply/Cancel—Each web page that includes editable parameters has these two buttons:

– Apply—Store the edited parameters in flash

– Cancel—Reset the edited parameters to the values currently stored in flash


OL-25151-01

Chapter 2 Administrative Web Interface Overview

Figure 2-1 Administrative Web Interface Home Page

Supported Web BrowsersThe web page servers have been tested and are compatible with the following web browsers:

• Firefox 1.5, 2.0, 3.0, 3.5, 3.6

• Internet Explorer 6.0, 7.0, and 8.0

Note Other browsers may also be compatible.

We strongly recommend you install the CA root certificate in the browser you use to avoid warning messages from occurring when you log in to the Administrative Web Interface (see Installing the CA Root Certificate, page 2-3).

Administrative Web Interface IP AddressTo access the Administrative Web Interface:

Procedure

Step 1 Browse to the IP address of the client. The IP address used depends on how the IP addresses are determined within your IP network:

• Static IP Address: the IP address is hard-coded and must be known

• Dynamic IP Address: the IP address is dynamically assigned by the Dynamic Host Configuration Protocol (DHCP) server and can be obtained from the DHCP server

Step 2 Enter the IP address into the browser (for example, https://192.168.1.123).


OL-25151-01

Chapter 2 Administrative Web Interface Overview

Note Some networks using DHCP may be able to also access the Administrative Web Interface using the PCoIP Device Name. See Adding Custom Information to the Device, page 4-6 for more information.

Administrative Web Interface SecurityThe Administrative Web Interface uses HTTP over an SSL socket (HTTPS). You cannot access it without an administrative password. The HTTPS connection is secured using a Teradici self-signed certificate.

Note Some PCoIP devices have password protection disabled and do not require a password to log in. You can enable or disable the password protection through the Cisco VXC Manager.

Installing the CA Root Certificate

You can install a Certificate Authorities (CA) root certificate in the Internet browser to avoid the browser security warnings. Steps for installing the certificate on Internet Explorer 7 and Firefox are described in the following sections.

Installing the CA Root Certificate in Internet Explorer

Procedure

Step 1 Open the Tools menu and select Internet Options.

Step 2 Click on the Content tab, and select Certificates.

Step 3 On the Trusted Root Certification Authorities tab, select Import.

Step 4 Follow the on-screen directions to import the certificate. The certificate file is part of the firmware release. The file is called cacert.pem. Ensure you use the Trusted Root Certification Authorities certificate store.

Installing the CA Root Certificate in Firefox

Procedure

Step 1 Open the Tools menu and select Options.

Step 2 Select the Advanced icon at the top of the page.

Step 3 On the Encryption tab, select View Certificates.

Step 4 On the Authorities tab, select Import.


OL-25151-01

Chapter 2 Administrative Web Interface OverviewLogging In

Step 5 Follow the on-screen directions to import the certificate. The certificate file is part of the firmware release. The file is called cacert.pem. Check the option labeled Trust this CA to identify web sites.

Logging InTo log in to the Administrative Web Interface:

Procedure

Step 1 From the Log In page, enter your password. The default value is blank (“”).

Figure 2-2 Log In Web Page (Client)

Step 2 To change the time after which the device is automatically logged out, set the Idle Timeout field to one of the following values:

• 1 minute

• 5 minutes

• 15 minutes

• 30 minutes

• Never

Step 3 Click Log In.

When you first log in to a device, the home page appears. It provides an overview of the device status. If configured in the firmware defaults, the Initial Setup page optionally appears the first time you log in.

Note Some PCoIP devices have password protection disabled by default and do not require a password to login. Password protection for the Log In page can be enabled or disabled using the Cisco VXC Manager. See the Administration Guide for Cisco VXC Manager document for more information.

If a warning message appears when you try to log in, a session is already in progress on that device. Only one administrator can log in to a device at one time. Logging in to a session already in progress terminates that session.


OL-25151-01

Chapter 2 Administrative Web Interface OverviewViewing the Home Page

See Updating the Password for a Device, page 4-29 for information on changing the password.

Viewing the Home PageThe home page displays a summary of the client. The first time you log into the Administrative Web Interface, the Initial Setup page appears. The home page appears for each subsequent session. To display it, click the Home link at the top left section of the menu bar.

Note When you click the Reset Statistics button, the statistics reported in the home page are also reset. For details about resetting the statistics, see Viewing PCoIP Protocol Statistics, page 4-38.

Figure 2-3 Home Page

The information fields shown on the home page are summarized in Table 2-1.

Table 2-1 Home Page Parameters

Parameter Comments

Time since boot Length of time that the PCoIP processor has been running (see Resetting the Device Processor, page 4-42)

Connection State Possible states: Disconnected, Connection Pending, Connected (see Viewing PCoIP Protocol Statistics, page 4-38)

Packet Statistics Packets sent (see Viewing PCoIP Protocol Statistics, page 4-38)

Packets received (see Viewing PCoIP Protocol Statistics, page 4-38)

Packets lost (see Viewing PCoIP Protocol Statistics, page 4-38)


OL-25151-01

Chapter 2 Administrative Web Interface OverviewAbout the Administrative Web Interface Menus

About the Administrative Web Interface MenusThe Administrative Web Interface has five menus that link to the various configuration and status pages.

• Configuration: The items on this menu let you configure the various aspects for the device, such as network settings, language, session parameters, and so on.

• Permissions: The items on this menu let you set up the client permissions for the USB, audio, and power.

• Diagnostics: The items on this menu help you troubleshoot the device.

• Info: The items on this menu let you view firmware information and the devices currently attached to the device.

• Upload: The items on this menu let you upload new a firmware version as well as an OSD logo to the device.

Byte Statistics Bytes sent (see Viewing PCoIP Protocol Statistics, page 4-38)

Bytes received

Round Trip Latency Approximate network minimum, average, and maximum round trip latency; for example, client to virtual machine and back to client (see Viewing PCoIP Protocol Statistics, page 4-38)

Bandwidth Stats Active bandwidth Limit is bandwidth PCoIP processors may generate (see Viewing PCoIP Protocol Statistics, page 4-38)

Transmit Bandwidth is minimum, average, and maximum traffic transmitted (see Viewing PCoIP Protocol Statistics, page 4-38)

Receive Bandwidth is minimum, average, and maximum traffic received see Viewing PCoIP Protocol Statistics, page 4-38)

Display Frame Rates Display Rate for video content through PCoIP protocol; for example, if nothing changed, Frame Rate is 0 fps (see Viewing PCoIP Protocol Statistics, page 4-38)

Session Encryption Type The type of encryption configured for the device. Options include AES-128-GCM, and SALSA20-256-Round 12 (see Configuring the Connections, page 4-17)

PCoIP Device Name The logical name for the device.

This field is the name the client registers with the DNS server if DHCP is enabled and the system is configured to support registering the host name with the DNS server.

Table 2-1 Home Page Parameters (continued)

Parameter Comments


OL-25151-01


Figure 2-4 shows the web pages available in the Administrative Web Interface.

Note The pages marked with an asterisk (*) are not applicable to Cisco VXC.

Figure 2-4 Administrative Web Interface Overview


OL-25151-01


C H A P T E R


OL-25151-01

3Working with the On Screen Display

The On Screen Display (OSD) local GUI appears on the client when the device is powered on and a PCoIP session is not in progress. The OSD provides a way for the user to connect to a virtual machine through the Connect screen.

The Connect screen also lets the user access the Options page which provides a subset of the functionality provided by the Administrative Web Interface. You can access the Options page by clicking the Options menu on the Connect screen.

About the Connect ScreenThe Connect screen appears during the startup except when the client is configured for a managed startup or auto-reconnect.

You can change the logo that appears above the Connect button by uploading a replacement image through the Administrative Web Interface. See Uploading a Logo to the Device, page 4-48 for information on updating the Connect Screen logo.

The Network icon at the bottom right of the Connect screen shows the status of the network connection. Users must wait until the network icon appears as shown in Figure 3-1:


OL-25151-01

Chapter 3 Working with the On Screen Display

Figure 3-1 OSD Connect Screen

A red X over the network icon means that either the network is not properly connected or the connection is still being initialized (that is, during client bootup).

Figure 3-2 Network Not Ready (detail)

Figure 3-3 shows the network icon when ready.

Figure 3-3 Network Ready (detail)

Connect ButtonClick the Connect button to initiate a PCoIP session or RDP session (depending on the session settings). While the PCoIP connection is pending, the OSD local GUI displays a “Connecting, please wait” message. When the connection is established, the OSD local GUI disappears and is replaced with the session image.


OL-25151-01

Chapter 3 Working with the On Screen DisplayAbout the OSD Options Menu

Figure 3-4 OSD Connect Screen (Connecting)

About the OSD Options MenuThere are five pages available from the Options menu:

• Configuration: This option lets you configure various aspects for the device, such as the network settings, peer connection, session parameters, and so on.

• Diagnostics: This option helps you troubleshoot the device.

• Information: This option lets you view details about the device.

• User Settings: This option lets the user define mouse and keyboard settings, as well as the PCoIP protocol image quality.

• Password: This option lets you update the administrative password for the device.


OL-25151-01

Chapter 3 Working with the On Screen DisplayAbout the OSD Options Menu

Figure 3-5 OSD Options Menu

C H A P T E R


OL-25151-01

4Cisco VXC PCoIP Configuration

As a user or administrator you can interact with your Cisco VXC clients through the embedded HTTPS web interface (the Administrative Web Interface) and On Screen Display (OSD).

Users can connect or disconnect a session, view diagnostics, and configure user parameters. Administrators can view and change configuration settings and user permissions, upload data to the PCoIP device, view session diagnostics information, and view product information.

To minimize the total learning curve and maximize the accessibility, the web interface and OSD are organized as similarly as possible and are structured in a task-oriented fashion.

Configuring the DeviceThe Configuration option on the Administrative Web Interface and OSD let you configure various aspects for the device. This section walks you through the full set of configuration options.

Note The OSD configuration options are a subset of the options available in the Administrative Web Interface. To make changes to the configuration settings you need an administrative password. You do not need a password to view the Diagnostic and Information menus.

Note The Cisco VXC firmware lets you disable the OSD and Administrative Web Interface from the Cisco VXC Manager.

Initial Setup Web PageIf configured in the firmware defaults, the Initial Setup web page optionally appears the first time you log in. For subsequent sessions, the home page appears unless the firmware parameters are reset.

Note This page is not generally used to configure Cisco VXC connections. To set up a connection with a VMware View Connection Server, see Configuring for Use with a VMware View Connection Server, page 4-9.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationConfiguring the Device

The Initial Setup web page contains the configuration parameters that the administrator must first set when using the client. The web page simplifies the out-of-box experiences and reduces the time for initial users to establish sessions between a Cisco VXC client and a remote virtual machine. More complex environments that use connection management systems require further configuration.

After you update the settings on this page, click Apply.

Figure 4-1 Initial Setup Client Web Page

Step 1: Audio

Step 1: Audio allows the administrator to configure the audio parameters. Table 4-1 summarizes the applicable parameters. For details on the full set of Audio parameters, see Generating an Audio Test Tone from the Client, page 4-41.

Table 4-1 Step 1: Audio Parameters

Parameter Comments

Enable HD Audio Enables audio support on the client


OL-25151-01


Step 2: Network

Step 2: Network allows the administrator to configure the network parameters. Table 4-2 summarizes the applicable parameters. For details on the full set of Network parameters, see Configuring the Network Parameters, page 4-3

Step 3: Session

Step 3: Session allows the administrator to configure the session parameters. Table 4-3 shows the client parameters. For details on configuring the full set of Session parameters, see Configuring the Connections, page 4-17.

Step 4: Apply Changes

Step 4: Apply Changes allows the administrator to apply the parameter updates made in the preceding steps. Parameters will not be updated until Apply is selected.

Configuring the Network ParametersYou can configure the client network Parameters from the Initial Setup web page or Network page. After you update the Parameters on this page, click Apply to save your changes.

Table 4-2 Step 2: Network Parameters

Parameter Comments

Enable DHCP Enables DHCP rather than manual configuration

IP Address The device IP address

Subnet Mask The device subnet mask

Gateway The device gateway IP address

Primary DNS Server The device primary DNS IP address

Secondary DNS Server The device secondary DNS IP address

Table 4-3 Step 3: Session Parameters (Client)

Parameter Comments

Session Type Specifies the PCoIP protocol or RDP

Identify Host by Specifies the host identify method

Note In this context, host refers to the server that hosts the virtual machine.

Host IP Address Specifies the host IP address

Host MAC Address Specifies the host MAC address


OL-25151-01


Figure 4-2 Network Configuration Web Page

Figure 4-3 OSD: Network Configuration

Table 4-4 Network Parameters

Parameter Description

Enable DHCP When enabled: The device contacts a DHCP server to be assigned an IP address, subnet mask, gateway IP address, and DNS servers. The firmware requests a domain name (option 15), host name (option 12), and client FQDN (option 81).

When disabled: You must set these parameters manually.

IP Address The device IP address. If DHCP is disabled, you must set this field to a valid IP address. If DHCP is enabled, you cannot edit this field.


OL-25151-01


Subnet Mask The device subnet mask. If DHCP is disabled, you must set this field to a valid subnet mask. If DHCP is enabled, you cannot edit this field.

Warning It is possible to configure an illegal IP Address/Subnet Mask combination (for example, invalid mask) that leaves the device unreachable. Take care when setting the Subnet Mask.

Gateway The device gateway IP address. If DHCP is disabled, this field is required. If DHCP is enabled, you cannot edit this field.

Primary DNS Server The device primary DNS IP address. This field is optional. If the DNS server IP address is configured when using a Connection Manager, the Connection Manager address may be set as an FQDN instead of an IP address

Secondary DNS Server The device secondary DNS IP address. This field is optional. If the DNS server IP address is configured when using a Connection Manager, the Connection Manager address may be set as an FQDN instead of an IP address.

Domain Name The domain named used (for example, domain.local). This field is optional. This field specifies the client domain.

FQDN The Fully Qualified Domain Name for the client. The default is pcoip-portal-<MAC> where <MAC> is the client MAC address. If used, the Domain Name is appended (for example, pcoip-portal-<MAC>.domain.local). This field is read-only on this page.

Note To use the FQDN feature, the DNS server with DHCP option 81 must be available and properly configured.

Table 4-4 Network Parameters (continued)



OL-25151-01


Adding Custom Information to the DeviceThe Label page allows an administrator to add custom information for the client.

Ethernet Mode Lets you configure the Ethernet mode of the client as:

• Auto

• 10 Mbps Full-Duplex

• 100 Mbps Full-Duplex

When you choose 10 Mbps Full Duplex or 100 Mbps Full-Duplex and then click Apply, this warning message appears:

“Warning: When Auto-Negotiation is disabled on the PCoIP device, it must also be disabled on the switch. Additionally, the PCoIP device and switch must be configured to use the same speed and duplex parameters. Different parameters may result in a loss of network connectivity. Are you sure you want to continue?”

Click OK to change the parameter.

Note Always set the Ethernet Mode to Auto and use only 10 Mbps full-duplex or 100 Mbps full-duplex when the other network equipment (for example, switch) is also configured to operate at 10 Mbps full-duplex or 100 Mbps full-duplex. An improperly set Ethernet Mode may result in the network operating at half-duplex (which is not supported by the PCoIP protocol). The session will be severely degraded and eventually dropped.

Maximum MTU Size Lets you configure the Maximum Transfer Unit packet size.

A smaller MTU may be needed for situations such as VPN tunneling because PCoIP packets cannot be fragmented. Set the Maximum MTU Size to a value smaller than the network path MTU for the end-to-end connection between the virtual machine and client.

The Maximum MTU Size range is 500 to 1500 bytes.

Note The default MTU is 1300 for sessions with the remote virtual machine.

Table 4-4 Network Parameters (continued)



OL-25151-01


Figure 4-4 Label Configuration Web Page

Figure 4-5 OSD: Label Configuration

Enabling or Disabling Connection ManagementThe Connection Management page allows you to enable or disable connection management and to specify the IP address of the connection manager that is not VMware View.

Table 4-5 Label Parameters


PCoIP Device Name Lets you give the client a logical name. The default is or pcoip-portal-<MAC> where <MAC> is the device MAC address.

This field is the name the client registers with the DNS server if DHCP is enabled and the system is configured to support registering the host name with the DNS server. It is important to ensure that the PCoIP Device Name is unique for each endpoint in the network.

PCoIP Device Description

A description or other information (such as the location of the endpoint) for the device. The firmware does not use this field. It is provided for administrator use.

Generic Tag Generic tag information about the device. The firmware does not use this field. It is provided for administrator use.


OL-25151-01


VMware View connection management settings are in dedicated pages. See Configuring for Use with a VMware View Connection Server, page 4-9.

In a managed connection, an external Connection Manager Server does the following:

• Communicates with and can remotely control and configure the device

• Can locate an appropriate peer for the device to connect to and initiate the connection

• Can simplify the administration effort for a large, complex system

Figure 4-6 Connection Management Configuration Web Page (IP Address)

Figure 4-7 Connection Management Configuration Web Page (FQDN)


OL-25151-01


Figure 4-8 OSD: Connection Management Configuration

Configuring for Use with a VMware View Connection ServerThe VMware View page allows configuration for use with a VMware View Connection Server.

Table 4-6 Connection Management Parameters


Enable Connection Management

When enabled, you can configure and control the device by using an external connection manager.

Identify Connection Manager By

Lets you choose whether the connection manager is identified by an IP address or by an FQDN. If Connection Management is disabled, this field is not required and not editable.

Enable Event Log Notification

Controls whether the client devices send the contents of their event logs to the connection management server.

Enable Diagnostic Log Controls whether connection-management-specific debug messages are written to the event log of the client devices.


OL-25151-01


Figure 4-9 VMware View Configuration Web Page

Figure 4-10 OSD: VMware View Configuration

Table 4-7 VMware View Parameters


Enable VMware View When enabled, you can configure the client for use with a VMware View Connection Server.

Note To enable the VMware View feature, the Enable Connection Management check box on the Connection Management page must be unchecked.

If VMware View is disabled, the remaining fields are not required and are not editable.

Identify Connection Server by

Choose how the connection manager is identified:

• IP Address

• FQDN


OL-25151-01


Configuring the VMware View Advanced ParametersThe Advanced button from the VMware View page lets you set advanced VMware View parameters for the Cisco VXC client.

To display the Advanced Settings page from the Administrative Web Interface:

Procedure

From the Configuration menu, click VMware View (Advanced).

The Advanced Settings page appears.

Connection Server FQDN

When FQDN is enabled, you can enter the URI used to specify the VMware View Connection Server. Some examples of valid URL formats include:

• myconnectionserver.cisco.com

• http://myconnectionserver.cisco.com

• https://myconnectionserver.cisco.com/

Port Specify the port used to communicate to the VMware View Connection Server

SSL Specify whether you want the client to communicate with the VMware View Connection server over a secure connection using SSL.

Auto connect Specify whether the client always connects with the VMware View Connection server at startup.

Connection Server Cache Mode

Set this field to:

• Last five servers used—These appear on the Connection Server entry box on the OSD VMware View Connect screen

• Read-only

The Cisco VXC Manager can be used to prepopulate the list of available connection servers.

Table 4-7 VMware View Parameters (continued)



OL-25151-01


To display the Advanced Settings page from the OSD:

Procedure

Step 1 From the Configuration menu, click the VMware View tab.

The VMware View page appears.

Step 2 Click the Advanced button.


OL-25151-01


Table 4-8 VMware View Advanced Settings Parameters


Auto Launch If Only One Desktop

When enabled and the user credentials are entered, users are automatically connected to their desktop VM.

Note This feature is for users who are entitled to a single desktop. It does not apply to users entitled to multiple virtual desktops

Login Username Caching

When enabled, the username text box automatically populates with the last username entered.

Use OSD Logo for View banner

When enabled, the Cisco VXC Client OSD logo is used for login. Administrators can upload a custom OSD logo through the Cisco VXC client web interface.

Prefer GSC-IS When selected, the CAC GSC interface is used if a smart card supports more than one interface such as CAC (GSC-IS) and PIV endpoint. If a smart card supports only one interface, such as either CAC or PIV endpoint, then only the CAC or PIV endpoint interface is used regardless of the Prefer GSC-IS setting. This affects only smart card access performed outside of PCoIP sessions.

Prefer GSC-IS is selected by default.

Enable Auto-Logon When enabled, the login information is automatically entered. The user does not need to enter a username or password when connecting to the device.

Logon Username The name of the user.

Logon Password The user password.

Logon Domain Name The domain name for the client being configured.

Desktop Name to Select Enter the pool/desktop name used by a Cisco VXC client when starting a session.


OL-25151-01


Configuring the VMware View Kiosk Mode ParametersKiosk mode is used with VXC clients when you want to provide access to Virtual Machines (VM) to multiple users in a public place (such as airports, bus stations, and stadiums). Such users use the zero client to obtain information that is not specific to any individual, such as bus schedules, sightseeing information, public phone numbers, and so on.

In addition, if there are concerns that a guest user might damage a VM by using it in an inappropriate way, you can configure the VM as non-persistent in the datacenter. In this case, the VM does not save any persistent information after it is powered down, and will restart in its original state when it is powered up again.

You can configure Kiosk Mode through the OSD or the Administrative Web Interface. Kiosk mode requires a properly configured VMware View environment. See VMware View documentation for more information.

To access the Kiosk Mode settings from the Administrative Web Interface:

Procedure

Step 1 Log in to the Administrative Web Interface for the client.

Step 2 From the Configuration menu, click VMware View (Kiosk Mode).

The Kiosk Mode Configuration page appears.

To configure the kiosk mode settings from the OSD:

Procedure

Step 1 From the Configuration menu, click the VMware View tab.

Step 2 Click Kiosk Mode.

The Kiosk Mode window appears.


OL-25151-01


Configuring the Discovery Mechanism

Note The Discovery Configuration page is not applicable to Cisco VXC clients.

Table 4-9 VMware View Kiosk Mode Parameters


Enable Kiosk Mode When enabled, the Cisco VXC client automatically logs in at startup to a predefined virtual desktop. Users do not need to enter their credentials.

Zero Client MAC Option

If the Zero Client MAC option is selected, the username is automatically entered based on the unique MAC address of the Cisco VXC client.

Custom Option If the Custom option is selected, the username is set to CM and the username is entered.

Password The system uses the contents of the Password field as the session password when Kiosk Mode automatically logs the Cisco VXC client in to the predefined virtual desktop.


OL-25151-01


Figure 4-11 Discovery Configuration Web Page

Figure 4-12 OSD: Discovery Configuration

Configuring the SNMP AgentThe Cisco VXC includes an SNMP agent that supports reporting of management information to an SNMP manager. The SNMP page lets you enable or disable the Cisco VXC SNMP agent.

The Cisco VXC uses “public” as the SNMP community string.

Figure 4-13 SNMP Configuration Web Page

Table 4-10 SNMP Parameters


Enable SNMP When enabled, the client enables the PCoIP SNMP agent. Disabling the SNMP agent ensures that the PCoIP SNMP MIB cannot be accessed.


OL-25151-01


Configuring the Connections

Note This page is not generally used to configure Cisco VXC connections. To set up a connection with a VMware View Connection Server, see Configuring for Use with a VMware View Connection Server, page 4-9.

The Session page lets you configure how the client device connects to or accepts connections from peer devices.

Figure 4-14 Session Configuration Web Page

Figure 4-15 OSD: Session Configuration

Note If Accept Any Peer is disabled the user must enter the peer (client) MAC address and the IP address will be non-editable.


OL-25151-01


Table 4-11 Session Parameters


Accept Any Peer Note This field is not applicable to Cisco VXC.

Session Type You can choose a PCoIP session or an RDP session.

Note Cisco does not provide support for RDP network implementations for the Cisco VXC 2111/2211.

Identify Peer By Choose whether the device is identified by its IP and MAC address or by the FQDN.

Identify Peer By, page 4-19 shows the peer identify parameters available for either method. If you enter an invalid IP address or DNS name, the web interface prompts you to correct it.

You can set the Peer MAC address equal to 00-00 00-00-00-00 on a Cisco VXC client and the field is ignored.

Peer IP Address Specify the peer IP address.

Peer MAC Address Specify the peer MAC address.

Enable Auto-Reconnect Lets the client automatically reconnect with the last connected broker server when a session is lost.

Enable Peer Loss Overlay

When enabled, the “Network Connection Lost” overlay appears on the displays when a loss of network connectivity is detected. It also appears in the case of a virtual desktop such as VMware View. Normal hypervisor scheduling delays can falsely trigger this message. This option is disabled by default.

Note Desktop applications that require the peer loss notification should renewable the feature through the OSD, Administrative Web Interface, or Cisco VXC Manager.

Enable AES-128-GCM Configure the AES-128-GCM encryption for the client. AES-128-GCM is an encryption method implemented in the TERA1x100 processor that allows best performance between hardware endpoints.

Note The enabled encryption must match on the virtual machine and client for a session to be established. If both modes are enabled, the firmware selects:

– VM 4.5 and later to client: SALSA20-256-Round12 for the PCoIP session

Enable SALSA20-256-Round 12

Configure SALSA20-256-Round 12 encryption for the client. SALSA20-256-Round12 is a lighter encryption method implemented in firmware that may offer improved performance when connecting to VMware View 4 or later when there is more than about 7 Mbps available on the network.

Note The enabled encryption must match on the virtual machine and client for a session to be established. If both modes are enabled, the firmware selects:

– VM 4.5 and later to client: SALSA20-256-Round12 for the PCoIP session


OL-25151-01


Identify Peer By

The Identify Peer By selector allows you to choose whether the peer device is identified by IP and MAC address or by Fully Qualified Domain Name (FQDN). If Accept Any Peer is enabled, these fields are not required and are not editable.

Table 4-12 shows the peer identify parameters available when either method is chosen. If an invalid IP address or DNS name is entered, the web interface will prompt the administrator to correct it.

Controlling Bandwidth for PCoIP SessionsThe Bandwidth page lets you control the bandwidth used by the device during a PCoIP session. This applies to sessions between Cisco VXC clients and the remote virtual machine.

The parameters in this page are applied after you click Apply.

To configure the bandwidth used with a VMware View virtual desktop, adjust the PCoIP GPO session variables

Figure 4-16 Bandwidth Configuration Web Page

Table 4-12 Peer Identify Methods

Peer Identify Method Data Fields Comment

Peer IP/MAC Peer IP Address PCoIP client or RDP client

Peer MAC Address PCoIP client

Peer FQDN Peer DNS Name PCoIP client or RDP client

Peer MAC Address PCoIP client


OL-25151-01


Table 4-13 Bandwidth Parameters


Device Bandwidth Limit

Defines the maximum bandwidth peak for the PCoIP system.

The bandwidth setting defines the bandwidth based on which side is sending data:

• On the virtual machine side: from the virtual machine to the client (for example, graphics data)

• On the client side: from the client to the virtual machine (for example, USB data)

The usable range of the device bandwidth is 1000 to 220,000 kbps.

The PCoIP processor uses only the required bandwidth up to the Device Bandwidth Limit maximum. The PCoIP processor dynamically adjusts the bandwidth in response to network congestion.

Setting the 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 virtual machine.

Note The setting in this field is applied immediately after you click Apply.

See Bandwidth and Image Configuration Example, page A-1 for an example of setting the Device Bandwidth Limit.


OL-25151-01


Configuring Device Parameters for RDPThe RDP web page allows you to configure device parameters specific to the Remote Desktop Protocol (RDP).

Note Cisco VXC PCoIP firmware is bundled with, and provides configuration options for, the RDP 5.2 client. However, Cisco does not provide support for RDP network implementations with the Cisco VXC 2111/2211 and recommends that you do not use the bundled RDP client.

Device Bandwidth Target

Defines the temporary limit on the network bandwidth during periods of congestion (packet loss). When the network experiences congestion, the device bandwidth is reduced rapidly to the target value and more slowly below this value. This allows for a more even distribution of bandwidth between users sharing a congested network link.

After the congestion is alleviated, the bandwidth used increases depending on the available network resources up to the Device Bandwidth Limit.

You must have a good understanding of the network topology before setting this to a non-zero value.

Device Bandwidth Floor

Lets you configure the bandwidth floor used by the firmware when congestion is present and when bandwidth is required. This lets you optimize performance for a network with understood congestion or packet loss. If the bandwidth is not required, the bandwidth used drops below the floor.

A setting of 0 lets the firmware reduce bandwidth to 1000 kbps for these network impairments. You must have a good understanding of the network topology before setting this to a non-zero value.

Note The firmware implements a Slow Start Algorithm that:

– Increases the bandwidth used until the bandwidth required is reached, network congestion is detected, or the Device Bandwidth Limit is reached

– Begins at the lesser of the Device Bandwidth Limit and 8000 kbps

– Increases the bandwidth used within seconds

– Allows a graceful session startup for low bandwidth scenarios (for example, WAN)

After initiating a PCoIP session, users may temporarily notice low bandwidth video artifacts while the algorithm ramps up bandwidth use.

Table 4-13 Bandwidth Parameters (continued)



OL-25151-01


Figure 4-17 RDP Configuration Web Page

Figure 4-18 OSD: RDP Configuration


OL-25151-01


Setting the User Interface LanguageThe Language page allows the administrator to change the user interface language.

Note This setting affects the local OSD GUI.

Table 4-14 RDP Parameters


Resolution The RDP screen resolution. Options include:

• Native Resolution

• 800x600

• 1024x768

• 1280x768

• 1280x1024

• 1440x900

• 1600x1200

• 1680x1050

• 1920x1080

• 1920x1200

Bit Depth The RDP session color bit depth. Options include:

• 8 bpp (bits per pixel)

• 16 bpp

• 24 bpp

Terminal Server Port The port number to which the RDP client connects.

Audio Mode The location where the audio playback occurs for the RDP session.

Options include:

• Do not play

• Play on client

• Play on host (indicates play on the virtual machine)

Enable Wallpaper Enable the use of wallpaper with the RDP session.

Enable Themes Enable the use of desktop themes with the RDP session.


OL-25151-01


Figure 4-19 Language Configuration Web Page

Figure 4-20 OSD: Language Configuration

Configuring the OSD Screen-Save TimeoutThe OSD page allows you to modify the On Screen Display (OSD) parameters.

Table 4-15 Language Parameters


Language Configure the OSD language. This setting determines the language for the OSD only. It does not affect the language setting for the actual user session.

See Appendix B, “Client Language and Keyboard Support” for supported languages.

Keyboard Layout Change the layout of the keyboard. When the user starts a session, this setting is pushed to the virtual machine. If the Windows GPO is set to allow the keyboard layout setting, it is used during the user session. If the Windows GPO is not set to allow the setting, it is dropped.

See Table B-2 in Appendix B, “Client Language and Keyboard Support” for supported keyboard layouts.


OL-25151-01


Figure 4-21 OSD Configuration Web Page

Figure 4-22 OSD: OSD Configuration

Adjusting the Image QualityThe Image page lets you make changes to the image quality of the PCoIP session. This applies to sessions between Cisco VXC clients and the virtual machine.

To configure the image quality settings with a VMware View virtual desktop, adjust the PCoIP session variables.

Table 4-16 OSD Parameters


Screen-saver Timeout Configure the screen-saver timeout before the client puts the attached displays into low-power mode. You can configure the timeout mode in seconds, up to 9999 seconds. A setting of 0 seconds disables the screen-saver.

Note After the OSD screen Timeout period expires, the attached displays are dimmed. To bring the displays up again (within 5 seconds) move the attached mouse. (No password is required.)


OL-25151-01


Figure 4-23 Image Configuration Web Page

Figure 4-24 OSD: Image


OL-25151-01


Enabling Monitor Emulation

Note The Monitor Emulation page is not applicable to Cisco VXC clients.

Figure 4-25 Monitor Emulation Configuration Web Page

Table 4-17 Image Parameters


Minimum Image Quality

Lets you compromise between image quality and frame rate when network bandwidth is limited. Some use cases may require lower-quality images at a higher frame rate while others need higher-quality images at a lower frame rate.

In environments where the network bandwidth is constrained, 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.

See Bandwidth and Image Configuration Example, page A-1 for an example of setting the Minimum Image Quality.

Maximum Initial Image Quality

Use the slider to reduce the network bandwidth peaks caused by screen content changes. This parameter limits the initial quality on the first display frame of a screen change. Unchanged regions of the image are built to a loss-less state regardless of this parameter.

Note The Maximum Image Quality:

– Must be greater than or equal to the Minimum Image Qualified

– Does not have a corresponding parameter on the OSD because it is intended as an administrator-only parameter


OL-25151-01


Enabling the Host Driver Function

Note The Host Driver Function page is not applicable to Cisco VXC clients.

Figure 4-26 Host Driver Function Configuration Web Page

Configuring the NTP ParametersThe Time web page configures the Network Time Protocol (NTP) settings to allow the event logs (see Viewing and Clearing Event Log Messages, page 4-36) of the client to be time-stamped based on NTP time.

Note To simplify system troubleshooting, set the NTP parameters to allow correlation of user events to the relevant diagnostic event log entries.

Figure 4-27 Time Configuration Web Page

Table 4-18 Time Parameters


Current Time Displays the time based on the NTP.

Enable NTP Enable or disable the NTP feature.


OL-25151-01


Updating the Password for a DeviceThe Password page lets you update the local administrative password for the device. The password can be a maximum of 20 characters. Some PCoIP devices have password protection disabled by default. The Password page is not available on these devices. Password protection can be enabled through the Cisco VXC Manager for these devices.

Note This parameter affects the web interface and the local OSD GUI. Take care when updating the client password because the client may become unusable if the password is lost.

If a device is set up to have password protection disabled, the Password page on the OSD is not available. You can enable the password protection through the Cisco VXC Manager for these devices.

Identify NTP Host By Choose if the NTP Host (that is, the NTP server) is identified by IP address or by FQDN. If NTP is disabled, this field is not required and is not editable. If you enter an invalid IP address or DNS name, a message appears to prompt you to correct it. The parameter depends on which method you choose:

• IP Address: Shows the NTP server IP address

• FQDN: Shows the NTP server DNS name

NTP Host Port Lets you configure the NTP port number.

NTP Query Interval Lets you configure the query interval. The first field is for the interval period and the second field is for the time unit in Minute(s), Hour(s), Day(s), and Week(s).

Time Zone Lets you select the local time zone.

Enable Daylight Savings Time

Enable or disable the automatic adjustment for daylight savings time.

Table 4-18 Time Parameters (continued)



OL-25151-01


Figure 4-28 Password Configuration Web Page

Figure 4-29 OSD: Change Password

Password Reset Window

Figure 4-30 shows the Authorized Password Reset window.

Table 4-19 Password Parameters


Old Password This field must match the current administrative password before you can update the password.

New Password The new administrative password for both the web interface and the local OSD GUI.

Confirm New Password This field must match the New Password field for the change to take place.

Reset If the client password is lost, you can click the Reset button to request a response code from their client vendor. The challenge code can be sent to the vendor. The vendor qualifies the request and returns a response code if authorized.

When the response code is correctly entered, the client password is reset to an empty string. You must enter a new password.

Note Contact the client vendor for more information when an authorized password reset is required. This option is not available through the Administrative Web Interface. It is available only through the OSD.


OL-25151-01


Figure 4-30 OSD: Authorized Password Reset

Resetting the Parameters to Factory DefaultsThe Reset web page lets you reset configuration and permissions to factory default values stored in flash. When you click the Reset Parameters button, a prompt appears for confirmation. This is to prevent accidental resets.

Figure 4-31 Reset Parameters Web Page

Figure 4-32 OSD: Reset

Configuring the EDID Override ModeThe Display page lets you enable the Extended Display Identification Data (EDID) override mode.

Table 4-20 Reset Parameters


Reset Parameters The Reset Parameters button resets all configuration and permissions to factory default values. When this button is selected, the web interface will prompt the administrator for confirmation to prevent accidental resets.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationSetting up User Permissions

Note The EDID override mode can be enabled only from the OSD.

Under normal operation, the GPU in the virtual machine queries the monitor to determine the monitor's capabilities. These are reported in the EDID information. In some situations, a monitor may be connected to a client in a way that prevents the client from reading the EDID information such as connecting through some KVM devices. In this case, configure the client to report default EDID information to the virtual machine by enabling the display override mode.

When this feature is enabled, the client provides EDID information to the user’s virtual machine display properties that indicates the following resolutions are supported:

• 800x600 @60 Hz

• 1280x800 @60 Hz

• 1280x960 @60 Hz

• 1280x1024 @60 Hz (native resolution advertised)

• 1600x1200 @60 Hz

• 1680x1050 @60 Hz

• 1920x1080 @60 Hz

• 1920x1200 @60 Hz

Warning Enabling display override forces default-monitor display information that may not comply with the connected monitor and result in a blank monitor. Enable display override only when there is no valid EDID information and when monitor display characteristics are understood.

Figure 4-33 OSD: Display Configuration

Setting up User PermissionsThe Permissions option on the Administrative Web Interface lets you configure parameters for the USB, Audio, and Power for the device.


OL-25151-01


Note There are no corresponding Permissions options for the OSD.

Specifying USB Devices

Note Certain USB-powered devices require sufficient power to be available on the client to power them. If the client does not have sufficient power for a USB device, the USB device cannot function, regardless of the configurations on these screens.

The USB page lets you specify authorized and unauthorized USB devices. It is divided into two sections: Authorized Devices (“white list”) and Unauthorized Devices (“black list”). Devices are authorized or unauthorized based on ID or Class. You can use wildcards (or specify “any”) to reduce the number of entries needed to define all devices.

See USB Permissions Example, page A-7 in Appendix A, “Usage Examples” for more details on USB configuration.

USB plug events are blocked in the Cisco VXC client hardware for unauthorized USB devices. The virtual machine cannot see or access the device for an additional layer of security.

The factory defaults for the client USB permissions are any, any, any (that is, authorized USB devices).

Note The USB permissions are updated only at the start of a PCoIP session. They are authorized in the following order of priority (highest to lowest):

1. Unauthorized Vendor ID/Product ID

2. Authorized Vendor ID/Product ID

3. Unauthorized Device Class/Sub Class/Protocol

4. Authorized Device Class/Sub Class/Protocol


OL-25151-01


Figure 4-34 USB Permissions Web Page

Table 4-21 USB Parameters


Authorized Devices Specify the authorized USB devices for the 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 Class:

• ID: The USB device is authorized by Vendor ID and Product ID

• Class: The USB device is authorized by Device Class, Sub Class, and Protocol

Remove: Delete a rule for a device or device group from the list.

Unauthorized Devices Specify the unauthorized USB devices for the client.

Add New: Add a new device or device group to the list. This allows USB devices to be unauthorized by ID or Class:

• ID: The USB device is unauthorized by Vendor ID and Product ID

• Class: The USB device is unauthorized by Device Class, Sub Class, and Protocol


Bridged Devices Cisco VXC clients locally terminate HID devices when connecting to VMware View virtual desktops, however, some devices advertise as HID but use different drivers. These devices may need to be bridged to the virtual machine rather than locally terminated. This setting lets you force the client to bridge specific USB devices so that they use the drivers on the virtual desktop.

This rule only affects sessions between a client and a virtual machine running VMware View 4.6 or later.

Add New: Add a new device or device group to the list. This allows USB devices to be bridged by Vendor ID and Product ID.



OL-25151-01


Table 4-22 summarizes the USB authorization entry type and the associated data fields. Two buttons let you customize this “white list”:

Configuring the Audio ParametersYou can configure the audio parameters from the Initial Setup page when you start your first session. For subsequent sessions, use the Audio page to configure the audio permissions for the device. After you update the options on this page, click Apply to save your changes.

To display the Audio page from the Administrative Web Interface, select the Permissions menu, and then click Audio.

Figure 4-35 Audio Web Page

Table 4-22 USB Device Authorized/Unauthorized Entry Types

Entry Type Required Fields Hexadecimal Value Comments

ID VID 0-FFFF

PID 0-FFFF

Class Device Class 0-FF; asterisk (*) indicates any device class

Drop-down menu provides translations of the known device classes

Sub Class 0-FF; asterisk (*) indicates any device subclass

Drop-down menu provides translations of the known device subclasses

Protocol 0-FF; asterisk (*) indicates any protocol authorized

Drop-down menu provides translations of the known protocols

Table 4-23 Audio Parameters


Enable HD Audio Enables audio support on the client. If the Enable HD Audio option is disabled on the virtual machine, the audio hardware is not available for the OS to enumerate.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationUsing the Diagnostic Tools

Setting up the Client Power-off PermissionsThe Power page lets you configure the power-off permissions of the client.

Figure 4-36 Power Web Page

Using the Diagnostic ToolsThe Diagnostics menu contains links to pages with run-time information and functions that may be useful for troubleshooting.

Note The diagnostic options in the OSD are a subset of those available through the Administrative Web Interface.

Viewing and Clearing Event Log MessagesThe Event Log page lets you view and clear event log messages from the client. The web interface lets you change the log filter setting on the device, which controls which messages are put in the log. When you set the filter to “terse,” the device logs terse messages.

Table 4-24 Power Parameters


Client Power Button The pull-down menu lets you configure the client power button functionality. Options include:

• Power-off not permitted

• Soft power-off only soft limit

• Hard power-off only

• Soft and hard power-off


OL-25151-01


Figure 4-37 Event Log Web Page

Figure 4-38 OSD: Event Log

Session ControlThe Session Control web page allows control of the device session.

Table 4-25 Event Log Parameters


Event log Message View: Click View to open a browser page that displays all the event log messages (with time-stamp information) stored on the device. Press F5 to refresh the browser page log information.

Clear: Click Clear to delete all stored event log messages stored on the device.

Event log filter mode Click the drop-down menu to filter the event logs. Options are:

• Verbose

• Terse


OL-25151-01


Figure 4-39 Session Control Web Page

Viewing PCoIP Protocol StatisticsThe Session Statistics page on the Administrative Web Interface and OSD lets you view current statistics when a session is active. If a session is not active, you can view the statistics from the last session.

Table 4-26 Session Control Parameters


Connection State This field displays the current state for the session. Options include:

• Disconnected

• Connection Pending

• Connected

Two buttons appear below the Connection State field:

Connect: If the connection state is Disconnected, click this button to initiate a PCoIP session between the client and its peer device. If the connection state is Connection Pending or Connected, this button is disabled.

Disconnect: If the connection state is Connected or Connection Pending, click this button to end the PCoIP session for the device. If the connection state is Disconnected, this button is disabled.

Peer IP/MAC Address Peer IP Address: Displays the IP address for the peer device. When not in session, this field is blank.

Peer MAC Address: Displays the MAC address of the peer device. When not in session, this field is blank.


OL-25151-01


Figure 4-40 Session Statistics Web Page

Figure 4-41 OSD: Session Statistics


OL-25151-01


Working with the Host CPU web page

Note The Host CPU page is not applicable to Cisco VXC clients.

Table 4-27 Session Statistics Parameters


Connection State The current (or last) state of the PCoIP session. Values include:

• Asleep

• Canceling

• Connected

• Connection Pending

• Disconnected

• Waking

PCoIP Packets Statistics

PCoIP Packets Sent: The total number of PCoIP packets sent in the current/last session.

PCoIP Packets Received: The total number of PCoIP packets received in the current/last session.

PCoIP Packets Lost: The total number of PCoIP packets lost in the current/last session.

Bytes Statistics Bytes Sent: The total number of bytes sent in the current/last session.

Bytes Received: The total number of bytes received in the current/last session.

Round Trip Latency The minimum, average, and maximum round-trip PCoIP system (for example, virtual machine to client and then back to the virtual machine) and network latency in milliseconds (+/- 1 ms).

Bandwidth Statistics Active Bandwidth Limit: The maximum amount of network traffic the processor may currently generate. The value is derived from the configured bandwidth parameters and the current (or last) network congestion levels.

Transmit Bandwidth: The minimum, average, and maximum traffic transmitted by the processor.

Receive Bandwidth: The minimum, average, and maximum traffic received by the processor.

Display Frame Rate Display 1 Frame Rate: The frame rate for Display 1, reported in frames per second.

Display 2 Frame Rate: The frame rate for Display 2, reported in frames per second.

Reset Statistics Click this button to reset the statistic information on this page.

Note This button also resets the statistics reported in the home page.


OL-25151-01


Figure 4-42 Host CPU Web Page

Generating an Audio Test Tone from the ClientThe Audio web page allows you to generate an audio test tone from the client. To verify the audio test, you must first connect speakers or headphones to the client.

Caution Cisco recommends that you do not wear the headphones during the audio test. Instead, hold them approximately two feet away from your ears because the volume level is loud and cannot be adjusted.

To generate an audio test tone, click Start to start the test tone. Click Stop to stop the test.

Note The Audio web page functionality is available on a client only when not in a PCoIP session.

Figure 4-43 Audio Diagnostics Web Page

Viewing a Test Pattern on the Client DisplayThe Display web page lets you initiate and view a test pattern on the client display.

Note The test pattern only appears on the Display page when the client is not in a PCoIP session. If you click Start when the client is in session, an error message appears.


OL-25151-01


Figure 4-44 Display Web Page

Resetting the Device ProcessorThe PCoIP Processor page lets you reset the client and view the amount of time that has elapsed since the client PCoIP processor last booted.

Table 4-28 Display Parameters


Test mode Set the type of test pattern for the attached monitor(s) as:

• Video Test Pattern Generator

• Pseudo Random Bitstream

Test resolution Set the test pattern resolution as:

• 1024x768

• 1280x1024

• 1600x1200

• 1920x1200

Start/Stop Click Start to begin the test pattern. Click Stop to stop the test.


OL-25151-01


Figure 4-45 PCoIP Processor Web Page

Figure 4-46 OSD: PCoIP Processor

Determining if a Device is ReachableThe Ping page lets you ping a device to see if it is reachable across the IP network. This may help you determine if a broker server is reachable. Because the firmware forces the “do not fragment flag” in the ping command, you can also use this feature to determine the maximum MTU size.

Note The Ping tab has no matching menu in the Administrative Web Interface.

Table 4-29 PCoIP Process Parameters


Current Time The current time. This feature requires that the NTP be enabled and configured. For details about configuring the NTP settings, see Configuring the NTP Parameters, page 4-28.

Time Since Boot (Uptime)

View the time that has elapsed since the PCoIP processor last booted.

Reset PCoIP Processor Click this button to reset the client.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationViewing Device Information

Figure 4-47 OSD: Ping

Figure 4-48 Ping Parameters

Viewing Device InformationThe Information page lets you see details about the device. The Administrative Web Interface shows version, vital product data (VPD), and attached device information. The OSD lets you view the device version information.

Viewing the Version InformationThe Version page allows you to view hardware and firmware version details.


Destination IP Address or FQDN to ping

Interval Interval between ping packets

Packet Size Size of ping packet

Packets Sent Number of ping packets transmitted

Packets Received Number of ping packets received


OL-25151-01


Figure 4-49 Version Web Page

Figure 4-50 OSD: Version

Table 4-30 Version Parameters


VPD Information This is vital product information provisioned by the factory to uniquely identify each client.

MAC Address: Client unique MAC address

Unique Identifier: Client unique identifier

Serial Number: Client unique serial number

Firmware Part Number: Part number of the current firmware

Hardware Version: Client hardware version number

Firmware Information This information reflects the current firmware details.

Firmware Version: Version of the current firmware

Firmware Build ID: Revision code of the current firmware

Firmware Build Date: Build date for the current firmware


OL-25151-01


Viewing the Attached DevicesThe Attached Devices page lets you see the type and status of the monitor and USB hardware currently attached to the client.

Figure 4-51 Attached Devices Web Page

PCoIP Processor Revision

The silicon revision of the PCoIP processor. Revision B of the silicon is denoted by a 1.0.

Bootloader Information This information reflects the current firmware bootloader details:

Bootloader Version: Version of the current bootloader

Bootloader Build ID: Revision code of the current bootloader

Bootloader Build Date: Build date of the current bootloader

Table 4-30 Version Parameters (continued)


Table 4-31 Attached Devices Parameters


Monitors This section displays the name, serial number, vendor identification (VID), product identification (PID), date, and status of the monitor attached to each port. The first line is for monitor 1. The second line is for monitor 2.

USB Devices This section displays the name, serial number, vendor identification (VID), product identification (PID), device class, sub class, protocol, and status of the USB device attached to each port. The first line is for the first USB port. The second line is for the second port, and so on.

USB Device Status The possible status options include:

• Not Connected: No device is connected.

• Standalone: The device is detected outside of a PCoIP session.

• Not Initialized: The device is detected in a PCoIP session but the virtual machine has not initialized the device.

• Failed Authorized: The device is detected in a PCoIP session but is not authorized. (For more information, see USB Permissions Example, page A-7.)

• Locally Connected: The device is detected and authorized but locally terminated in a PCoIP session (for example, a local cursor).

• Connected: The device is detected and authorized in a PCoIP session.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationUploading to the device

Uploading to the deviceYou can use the options in this menu to upload new firmware to a device or to upload an OSD logo to a device. These options are not available through the OSD.

Uploading the Firmware to the DeviceThe Firmware web page allows you to upload a new firmware build to the client.

Figure 4-52 Firmware Upload Web Page

Firmware Upload Process Example

Procedure

Step 1 Ensure the client is disconnected from the virtual machine.

Step 2 Log in to the client Administrative Web Interface (using a password if enabled).

Step 3 From the Firmware Upload web page, browse to the firmware .all file (for example, tera1x00_rel1-9-v175.all).

Step 4 Click Open.

Step 5 Click Upload.

Step 6 Click OK to confirm that you want to proceed with the upload. When the firmware upload completes, the message “Success Flash successfully programmed! You must reset the device for the changes to take effect” appears.

Step 7 Click Reset. The message “The PCoIP processor will reset on the next host system restart; your changes will take effect then. Are you sure you want to proceed?” appears.

Step 8 Click OK.

Step 9 If the client does not automatically reset itself, reset the client manually.

Table 4-32 Firmware Upload Parameters


Firmware build filename

The filename of the firmware image to be uploaded. You can browse to the file using the Browse button. The file must be accessible to the web browser (that is, on a local or accessible network drive). The firmware image must be an .all file.

Upload Click the Upload button to transfer the specified file to the device. The web interface prompts you to confirm this action to avoid accidental uploads.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationUploading to the device

Step 10 Start the PCoIP session as usual.

Uploading a Logo to the DeviceThe OSD Logo page allows you to upload an image to the device. This image is displayed on the Connect window of the local GUI On Screen Display (OSD) logo.

The VMware View Advanced page includes an option “Use OSD Logo for View Banner,” which lets you configure if the OSD logo appears on the View login screen instead of the View banner. For more information, see Configuring the VMware View Advanced Parameters, page 4-11.

Figure 4-53 OSD Logo Upload Web Page

OSD Logo Upload Process Example

Procedure

Step 1 From the OSD Logo web page, click Browse to locate the target logo file.

Step 2 Click Open.

Step 3 Click Upload. The message “Are you sure? This will upload a new logo for the local GUI. This operation may take a few minutes” appears.

Step 4 Click OK.

Step 5 Wait for the OSD Logo upload to finish. A message appears to advise if the upload was successful.

Step 6 Reset the client.

Table 4-33 OSD Logo Parameters


OSD logo filename Specify the filename of the logo image you want to upload. You can browse to the target file using the Browse button. The file must be accessible to the web browser (that is, on a local or accessible network drive).

The 24-bits-per-pixel image must be in BMP format and its dimensions cannot exceed 256 pixels in width, 64 pixels in height. If the file extension is incorrect, an error message appears.

Upload Click Upload to transfer the specified image file to the client. A message to confirm the upload appears.


OL-25151-01

Chapter 4 Cisco VXC PCoIP ConfigurationConfiguring the User Settings

Configuring the User SettingsThe User Settings page lets you access tabs to define the mouse and keyboard settings, PCoIP protocol image quality, as well as the display topology.

Configuring the Mouse SettingsThe Mouse page lets you change the mouse cursor speed settings for the OSD and RDP sessions.

Figure 4-54 OSD: Mouse

Changing the Keyboard Repeat SettingsThe Keyboard page lets you change the keyboard repeat settings for the OSD and RDP sessions.

Note The Keyboard tab has no corresponding menu in the Administrative Web Interface.

Table 4-34 Mouse Parameters


Mouse Speed Configure the speed of the mouse cursor.

Note You can also configure the mouse speed through the virtual machine.


OL-25151-01


Figure 4-55 Keyboard

Image TabFor information about adjusting the image quality, see Adjusting the Image Quality, page 4-25.

Configuring the Display TopologyThe Display Topology page lets users change a display position, rotation, and resolution for a PCoIP session. To apply the display topology feature to a PCoIP session between a client and a Virtual Machine (VM), you must have VMware View 4.5 or later.

Note Be aware of the following:

• The Display Topology tab has no corresponding menu in the Administration Interface.

• Always change the display topology settings using the Display Topology tab on the client (OSD > Options > User Settings). Do not try to change these settings using the Windows Display Settings in a virtual machine when using VMware View.

To view the Display Topology page:

Procedure

Step 1 From the OSD, click Options, and then click User Settings.

Step 2 Click the Display Topology tab.

Table 4-35 Keyboard Parameters


Keyboard Repeat Delay Lets users configure the client keyboard repeat delay.

Keyboard Repeat Rate Lets users configure the client keyboard repeat rate.

Repeat Settings Test Box

Lets users test the chosen keyboard settings.


OL-25151-01


The Display Topology page appears.

Table 4-36 Keyboard Parameters


Enable Configuration When enabled, the device can be configured with display position, rotation and resolution settings. The settings are saved when you click Apply or OK and are applied when the device is reset.

Display Position Map The display position map consists of four possible display positions. A maximum of two displays can be enabled at the same time.

Display Position When two displays are connected to the client DVI-1 and DVI-2 connectors the user must configure how the monitors are arranged. The Display Position settings support this. Using these settings the user can arrange the displays horizontally or vertically. For example, to arrange the displays horizontally with the monitor connected to DVI-1 on the left, set Display 0 Position and Display 1 Position to Position 0 and 1, or Position 2 and 3, respectively. To arrange the displays horizontally with the monitor connected to DVI-2 on the left, set Display 0 Position and Display 1 Position to Position 1 and 0, or Position 3 and 2, respectively.

Origin Origin is a read-only parameter that indicates the (x,y) position of the upper left-hand corner of a display.

Rotation You can configure the orientation of a display to:

• No rotation

• 90° clockwise

• 180° rotation

• 90° counter-clockwise

Resolution The display resolution can be configured for a PCoIP session between a virtual machine and a client. The client detects the supported display resolutions of the monitor and populates them to the drop-down menu. By default, the native resolution of the display is used.


OL-25151-01


C H A P T E R


OL-25151-01

5About the Overlay Pages

Overlay pages are a way of displaying pertinent information to users during a PCoIP session. These pages occasionally overlay the user’s remote session.

Status overlay pages show network, USB device, and monitor statuses as icons and text. The overlays have simple animation and appear when the status changes (that is, the network connection is lost or an unauthorized USB device is plugged in).

Network Connection Lost OverlayLoss of network connectivity is indicated using an overlay with the message “Network connection lost” over the most recent screen data. This overlay appears when the client network cable is disconnected or when no PCoIP protocol traffic is received by the client for more than 2 seconds.

Figure 5-1 Network Connection Lost Overlay

The lost network connection message appears until the network is restored or the timeout expires (and the PCoIP session ends).

Note It is not recommended to use this notification message when using PCoIP devices with virtual desktops. Normal scheduling within the virtual desktop hypervisor can falsely trigger this message. For more information, see the Enable Peer Loss Overlay setting described in Configuring the Connections, page 4-17.

USB Device Not Authorized OverlayIf an unauthorized USB device is connected, an overlay appears with the message “USB device not authorized.” The overlay lasts for approximately 5 seconds.

Figure 5-2 USB Device Not Authorized Overlay

The overlay will be displayed for approximately 5 seconds.


OL-25151-01

Chapter 5 About the Overlay PagesUSB Over Current Notice Overlay

USB Over Current Notice OverlayIf the USB devices connected to the client cannot be handled by the USB ports, an overlay appears with the message “USB over current notice.” The overly appears until USB devices are removed to meet the current handling of the USB ports.

Figure 5-3 USB Over Current Notice Overlay

The overlay will be displayed until USB devices are removed to meet the current handling of the USB ports.

Half-Duplex OverlayPCoIP technology is not compatible with half-duplex network connections. When a half-duplex connection is detected, an overlay appears with the message “Half-duplex network connection.”

Figure 5-4 Half-Duplex Overlay

Video Source OverlaysImproper connection of the virtual machine video source is denoted by two possible overlays. These overlays appear for approximately five minutes. The monitor is put into sleep mode approximately 15 seconds later.

When no video source is connected to the virtual machine, an overlay appears with the message “No source signal.” This helps the user debug a situation where the virtual machine does not have video source connected or has stopped driving a video signal.

Figure 5-5 No Source Signal Overlay

Note This message can be triggered by the virtual machine going into display power save mode.

When a video source to on the virtual machine does not correspond to the video port used on the client, an overlay appears with the message “Source signal on other port.” This helps the user debug a problem where the video source is connected to the wrong port. You can correct this by swapping the video ports at the client.


OL-25151-01

Chapter 5 About the Overlay PagesVideo Source Overlays

Figure 5-6 Source Signal on Other Port Overlay


OL-25151-01

Chapter 5 About the Overlay PagesVideo Source Overlays

A-1Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

A P P E N D I X AUsage Examples

This section provides detailed examples to help you determine how best to configure your own devices.

Bandwidth and Image Configuration ExampleThis example outlines the steps for optimizing user experiences in an environment where bandwidth is constrained. It is assumed that there are four task-based workers (web browsing, simple word processing, simple spreadsheet manipulation, and small video pages) that are to share one 100-Mbps switch.

Due to the nature of these tasks, the users do not require heavy graphics changes and each user likely requires peak network bandwidth at different times.

Figure A-1 shows simplified bandwidth requirements for each user assuming they each had the full 100 Mbps available. The figure shows that network demand for each user peaks only for short periods (for example, when opening or closing pages, or scrolling a page).

Because the PCoIP system adapts quickly to available bandwidth, we recommend keeping the system defaults. However, the following examples show how to adapt the default settings if your configuration requires it.


OL-25151-01

Appendix A Usage ExamplesBandwidth and Image Configuration Example

Figure A-1 Simplified User Bandwidth Requirements (Assuming 100 Mbps)

Configuring the Client Bandwidth Limit to 25 MbpsIn this example, the network is configured to minimize packet loss. Networks respond to congestion by dropping packets. The PCoIP processor responds to dropped (lost) packets by reducing the amount of bandwidth it generates. In most cases, the PCoIP processor conceals the packet loss to be imperceptible to the user. However, in some situations where bandwidth is low or network latency is high, it might be preferable to eliminate congestion-based packet loss by limiting the available bandwidth to each user. In this example, we limit each user’s peak bandwidth to a hard limit of 25 Mbps (that is, the firmware does not use more than 25 Mbps).

We also set a target (soft limit) of 20 Mbps so that during periods of network congestion, the bandwidth is decreased rapidly to 20 Mbps and more slowly below 20 Mbps. This ensures that the available bandwidth is shared fairly if other network traffic further constrains the link.

To set the bandwidth limit to 25 Mbps:

Procedure

Step 1 Open an Internet browser, and then open the Administrative Web Interface for the first users client using the IP address for the client.

Step 2 Log in using a password (if enabled).

Step 3 From the Configuration menu, select the Bandwidth web page.


OL-25151-01


Figure A-2 Client Bandwidth Limit Configuration (25 Mbps)

Step 4 Enter 25 in the Device Bandwidth Limited field.

Step 5 Enter 20 in the Device Bandwidth Target field.

Step 6 Click Apply to accept the changes.

Step 7 Repeat for the other three users’ clients.

The bandwidth is now limited to 25 Mbps and targeted to 20 Mbps for each user.

Figure A-3 shows simplified bandwidth usage with the limit for each user now configured for 25 Mbps. This figure shows that all users are limited to 25 Mbps and do not have access to more bandwidth when required. It also shows that even when the usage is totaled, the total switch bandwidth (100 Mbps) is never fully used.

Also note that because there is no congestion, there is no requirement to reduce the bandwidth to the targeted 20 Mbps or lower.


OL-25151-01


Figure A-3 Simplified User Bandwidth Requirements (25 Mbps)

Configuring Image PropertiesIn the example where the client bandwidth was set to 25 Mbps, it is possible that users may occasionally require more than that bandwidth limit to fully render their display information at maximum quality and full frame rate. The PCoIP system gives two controls over imaging quality that can optimize the user experience in environments where bandwidth is constrained.

For users who prefer higher image quality than what the PCoIP protocol balanced-quality/frame-rate algorithm provides, increasing the client Minimum Image Quality setting may be beneficial.

The Maximum Initial Image Quality setting can change the peak bandwidth required by any user. Decreasing the Maximum Initial Image Quality from the default setting of 90 can reduce the amount of bandwidth required per user while maintaining a minimum limit on the user experience.

Note This example uses the Administration Interface for configuring the client for Minimum Image Quality and Maximum Initial Image Quality. Although you can also use the OSD to configure the client, the Maximum Initial Image Quality does not have a corresponding parameter in the OSD as it is meant as an administrator-only parameter due to the potential impact on network traffic.


OL-25151-01


To configure the image properties:

Procedure

Step 1 From an Internet browser, open the client Administrative Web Interface for the first user’s client by using the client's IP address.

Step 2 Log in using password (if enabled).

Step 3 From the Configuration menu, select the Image web page.

Figure A-4 Client Minimum Image Quality Configuration

Step 4 Slide the Minimum Image Quality slider to the right.

Step 5 Slide the Maximum Initial Image Quality slider to the left.


Step 7 Repeat for the other three user clients.

The Minimum Image Quality is now configured toward Perception-Free to increase the minimum image quality the system reduces to under any condition. This effect is only noticeable in limited bandwidth cases. If bandwidth is not constrained, the system always maintains perception-free quality. The Minimum Image Quality feature does not alter the overall bandwidth requirements of the user.

The Maximum Initial Image Quality is now configured toward Reduced to limit the quality on the changed image (that is, initial video frame). A lower Maximum Initial Image Quality setting requires less bandwidth as the lower-quality initial image requires less bandwidth to create. In this case, the administrator and the users determined that setting the Maximum Initial Image Quality to 60 was a preferable way of reducing bandwidth requirements than setting a hard limit on the Device Bandwidth Limit.

Regardless of the Maximum Initial Image Quality setting, the PCoIP system always builds unchanged regions of the display to a loss-less image

Note The Minimum Image Quality setting must always be less than or equal to the Maximum Initial Image Quality setting.


OL-25151-01


Configuring the Client Bandwidth Limit to 0 Mbps (No Limit)This example shows the PCoIP protocol default bandwidth and imaging settings being used to take advantage of the usage characteristics of the group. (The characteristics in this example are similar to many actual usage groups.) Here the device bandwidth limit and device bandwidth target are configured to 0 (no limit) to allow more effective bandwidth sharing. The firmware alleviates bandwidth congestion by implementing a bandwidth adaptation algorithm that strives for fairness on shared networks. The firmware uses the bandwidth as determined by the Ethernet physical-layer device.

To configure the client bandwidth to no limit:

Procedure

Step 1 From a web browser, enter the IP address of the first user’s client.

Step 2 Log in to the Administrative Web Interface for the client (using password if enabled).

Step 3 From the Configuration menu, select the Bandwidth web page.

Figure A-5 Client Bandwidth Limit Configuration (0 Mbps, no limit)

Step 4 Enter 0 in the Device Bandwidth Limited field to enable no limit.

Step 5 Enter 0 in the Device Bandwidth Target field to enable no limit.


Step 7 Repeat for the other three user clients.

The bandwidth limit and target are now set to 0 Mbps (no limit) for each user. Due to the nature of the users’ tasks—light graphics changes and peak network demand at different times—little conflict is expected for the full 100-Mbps bandwidth. The users share the bandwidth more effectively and have fewer situations where their images would have to be compromised to meet a bandwidth limit.

When there is congestion, the firmware automatically reduces the bandwidth limit using a bandwidth adaptation algorithm that strives for fairness on shared networks. When the congestion clears, the firmware again opens the bandwidth limit.

Figure A-6 shows the total simplified bandwidth usage with no limit for the four users in this example. This figure shows that the bandwidth is more efficiently shared, compared to the case of setting a low maximum bandwidth limit. In the unlimited case, each PCoIP session can use up to 100 Mbps. This provides the user with a more perception-free experience.


OL-25151-01

Appendix A Usage ExamplesUSB Permissions Example

Figure A-6 Simplified User Bandwidth Requirements (no limit)

USB Permissions ExampleThis example shows the use of the USB Permissions web page. It shows how you can use the drop-down menus to authorize a specific class of IEEE-compatible bidirectional USB printers and a specific vendor/product ID.

This example outlines the steps to authorize a USB device by Class or by Device ID. The example assumes that the systems already has Human Interface Devices (any Sub Class, Any Protocol) authorized.

Authorizing USB Device By ClassTo authorize a USB device by a class:

Procedure

Step 1 Open the USB Permissions web page.

Step 2 In the Authorization section, click Add new.

Step 3 When the entry fields expand, select Class from the Add New drop-down menu to authorize a class of devices.


OL-25151-01


Step 4 Select Printer from the Device Class drop-down menu to authorize a class of printers.

Step 5 Select Printer from the Sub Class drop-down menu to authorize a specific class of printers (otherwise, the sub class and protocol could be left as Any).

Step 6 Select the desired IEEE 1284.4-compatible bidirectional protocol from the Protocol drop-down menu.

Step 7 Select Apply to save the changes to flash and complete the configuration.

Authorizing USB Device By Vendor ID and Product IDTo authorize a USB device by a vendor ID and product ID:

Procedure

Step 1 In the Authorization section, click Add new.

Step 2 When the entry fields expand, select ID from the Add New drop-down menu to authorize a device by its vendor ID and product ID.

Step 3 Enter the USB device vendor ID and product ID into the corresponding fields.


OL-25151-01


Figure A-7 USB Permissions Example: Entering Vendor ID and Product ID

Step 4 Click Apply to save the changes to flash and complete the configuration.

Figure A-8 USB Permissions Example: Vendor ID and Product ID Authorization


OL-25151-01


B-1Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

A P P E N D I X BClient Language and Keyboard Support

The client firmware can support various languages and keyboard layouts.

Information concerning configuring the language and keyboard layout can be found in Setting the User Interface Language, page 4-23. Table B-1 and Table B-2 list the supported languages and supported keyboards layouts (defaults are noted).

Table B-1 Languages Supported by the Client

English [default] Portuguese

French Korean

German Japanese

Greek Traditional Chinese

Spanish Simplified Chinese

Italian

Table B-2 Keyboard Layouts Supported by the Client

Belgian ISO-8859-1 German ISO-8859-1 (accent keys)

Belgian ISO-8859-1 (accent keys) German Codepage 850

Danish Codepage 865 Greek ISO-8859-7 (104)

Danish ISO-8859-1 Italian ISO-8859-1

Danish ISO-8859-1 (accent keys) Japanese 106

Dutch ISO-8859-1 (accent keys) Japanese 106x

Finnish Codepage 850 Korean Dubeolsik ISO-8859-1

Finnish ISO-8859-1 Latin American

Finnish ISO-8859-1 (accent keys) Latin American (accent keys)

French Canadian ISO-8859-1 (accent keys) Norwegian Dvorak

French ISO-8859-1 Norwegian ISO-8859-1

French ISO-8859-1 (accent keys) Norwegian ISO-8859-1 (accent keys)

French Dvorak-like Polish ISO-8859-2 (Programmers)

French Dvorak-like (accent keys) Portuguese ISO-8859-1

German ISO-8859-1 Portuguese ISO-8859-1 (accent keys)

B-2Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

Appendix B Client Language and Keyboard Support

Spanish ISO-8859-1 United Kingdom ISO-8859-1

Spanish ISO-8859-1 (accent keys) United Kingdom ISO-8859-1 (ctrl and caps swapped)

Spanish ISO-8859-15 (accent keys) United Kingdom Codepage 850

Swedish Codepage 850 United Kingdom Codepage 850 (ctrl and caps swapped)

Swedish ISO-8859-1 United States of America Emacs optimized layout

Swedish ISO-8859-1 (accent keys) United States of America ISO-8859-1 [default]

Swiss-French ISO-8859-1 United States of America ISO-8859-1 (accent keys)

Swiss-French ISO-8859-1 (accent keys) United States of America ISO-8859-1 (ctrl and caps swapped)

Swiss-French Codepage 850 United States of America dvorak

Swiss-German ISO-8859-1 United States of America dvorakx

Swiss-German ISO-8859-1 (accent keys) United States of America left-hand dvorak

Swiss-German Codepage 850 United States of America right-hand dvorak United States of America dvorakx

Turkish Q ISO-8859-1 United States of America Emacs optimized layout

Turkish Q ISO-8859-1 (accent keys) United States of America Traditional Unix Workstation

Table B-2 Keyboard Layouts Supported by the Client (continued)

C-1Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

A P P E N D I X CCisco VXC 2111/2211 Power Considerations

You can power the Cisco VXC 2111/2211 using a Cisco PWR-CUBE-4 power adapter or using standard Power over Ethernet (PoE). This appendix describes the Cisco VXC configurations that are supported by the IEEE 802.3af and IEEE 802.3at PoE standards, by Cisco Universal Power Over Ethernet (UPOE), and by the Cisco PWR-CUBE-4 power adapter.

Cisco VXC 2111/2211 USB ports are compliant with USB 2.0 standard specifications to deliver a maximum power level of 2.5 watts.

Available Power on USB PortsThe USB ports on the Cisco VXC 2111/2211 operate at two power levels:

• Low: 0.5 watts

• High: 2.5 watts

USB ports that operate at the low-power level can only power USB devices that consume up to 0.5 watts of power, and USB ports that operate at the high-power level can power USB devices that consume up to 2.5 watts of power.

USB ports on the Cisco VXC 2111/2211 that operate at high power cannot individually power any noncompliant USB accessory that requires more than 2.5 watts of power. To power devices that require between 2.5 and 5 watts of power, you can use a USB Y cable to connect the accessory to USB port 3 and 4 of the client (when these are operating at high power).

In addition, if no device is connected to a port, the Cisco VXC 2111/2211 cannot reallocate the available power from this port to a device on another port. For example, if USB ports 1 and 2 are operating at low power, and no device is connected to port 2, the Cisco VXC 2111/2211 cannot redirect the power allocated to port 2 to power a high-power device on port 1. In this case, the maximum power limit on port 1 remains unchanged at 0.5 watts.

Low-power USB devices (0.5 watts or less) are typically keyboards, mice, and joysticks, while high-power USB devices (greater than 0.5 watts) are typically bus-powered cameras, hubs, and some USB Flash drives.

USB Hub SupportUSB ports on the Cisco VXC 2111/2211 can power a USB hub provided the hub does not draw more power than is available from the USB port to which it is connected (that is, 0.5 watts on low-power ports or 2.5 watts on high-power ports).


OL-25151-01

Appendix C Cisco VXC 2111/2211 Power ConsiderationsPoE Power Negotiation

PoE Power NegotiationWhen the Cisco VXC 2111/2211 is powered using PoE, the firmware performs a one-time negotiation of PoE power requirements at boot time and allocates the available power to the USB ports, power indicators, and monitors, as described in Cisco VXC 2111 Power Support, page C-2 and Cisco VXC 2211 Power Support, page C-3. During normal operation, this power allocation does not change.

Cisco VXC 2111 Power SupportTable C-1 describes the power configurations that are supported on the Cisco VXC 2111.

Note • IEEE 802.3af PoE does not support Cisco VXC 2111 configurations.

• IEEE 802.3at PoE does not support the Cisco VXC 2111 if a Key Expansion Module is attached to a Cisco Unified IP Phone 8961, 9951, or 9971.

As an alternative to PoE, the Cisco PWR-CUBE-4 power adapter can support a Cisco VXC 2111 attached to a Cisco Unified IP Phone 8961, 9951, or 9971 (with or without camera) with up to three Key Expansion Modules in a basic configuration (keyboard, mouse, and one monitor).

Table C-1 Cisco VXC 2111 Power Support

Cisco VXC 2111 with:

Power Source

USB Monitor

ConfigurationPort 1 keyboard

Port 2 mouse

Port 3 accessories

Port 4 accessories Port 0 Port 1

8961 802.3at Powered (low)

Powered (low)

Unavailable Unavailable Powered Powered Moderate

9951 without camera

802.3at Powered (low)

Powered (low)

Unavailable Unavailable Powered Powered 1

1. The values listed are applicable to Cisco VXC 2111 devices with a version ID (VID) of V02. The behavior may differ on Cisco VXC 2111 devices with a VID of V01. For example, while operating in certain moderate configurations, the Port 1 monitor may not be available on devices with a VID of V01. You can obtain the VID value from the compliance label on the underside of the device. The VID is listed at the end of the Product ID (PID). For example, CVXC-2111-W-K9 V01 indicates a V01 device and CVXC-2111-W-K9 V02 indicates a V02 device.

Moderate

9951 with camera


Powered (low)

Unavailable Unavailable Powered Powered 1 Moderate

9971 without camera


Powered (low)

Unavailable Unavailable Powered Powered 1 Moderate

9971 with camera


Powered (low)

Unavailable Unavailable Powered Unavailable Basic

8961/9951/9971 with or without camera

UPOE Powered (high)

Powered (high)

Powered (high)

Powered (high)

Powered Powered Full

PWR-CUBE-4

Powered (high)

Powered (high)

Powered (high)

Powered (high)



OL-25151-01

Appendix C Cisco VXC 2111/2211 Power ConsiderationsCisco VXC 2211 Power Support

If you add one or more Key Expansion Modules to the Cisco Unified IP Phone 8961, 9951, or 9971, these modules may reduce the amount of power available to the Cisco VXC client and may cause additional restrictions for powering Cisco VXC peripheral devices.

Cisco VXC 2211 Power SupportTable C-2 describes power configurations that are supported on the Cisco VXC 2211.

Note • The Unified IP Phone PC port can provide the network connectivity for the Cisco VXC 2211; however, it does not provide power for the device. A power adapter is required when you use the Unified IP Phone PC port for network connectivity for the Cisco VXC 2211.

• IEEE 802.3af PoE can support a Cisco VXC 2211 only in a basic configuration.

Cisco VXC 2211 Base LED BehaviorTable C-3 describes the behavior of the base LEDs when you connect power (PoE or Cisco Power Cube 4) to the Cisco VXC 2211.

Table C-2 Cisco VXC 2211 Power Support

Power Source

USB Monitor

ConfigurationPort 1 keyboard

Port 2 mouse

Port 3 accessories

Port 4 accessories Port 0 Port 1

Cisco VXC 2211

802.3af Powered (low)

Powered (low)

Unavailable Unavailable Powered Unavailable Basic

802.3at Powered (high)

Powered (high)

Powered (high)

Powered (high)


UPOE Powered (high)

Powered (high)

Powered (high)

Powered (high)


PWR-CUBE-4

Powered (high)

Powered (high)

Powered (high)

Powered (high)


Table C-3 Cisco VXC 2211 Base LED Behavior

Power source

Client connected to power source (PoE or Power cube)

Press power button for power-on (quick button press - no more than 1/2 second)

Press Power button again for power-off (hold minimum 3 seconds)

IEEE 802.3af PoE No light Dim white light Light turns off

IEEE 802.3at PoE No light Dim white light Light turns off


OL-25151-01

Appendix C Cisco VXC 2111/2211 Power ConsiderationsPower Consumption

Power ConsumptionTable C-4 describes the power consumption on the Cisco VXC 2111/2211.

Cisco UPOE No light Dim white light Light turns off

Cisco Power Cube 4 (plugged in AFTER network cable)

Initial white light flash, then light turns off

Dim white light, which becomes a bright white light after approximately 10 seconds

Light turns off

Cisco Power Cube 4 (plugged in BEFORE network cable)

No light Dim white light, which becomes a bright white light after approximately 10 seconds.

Light turns off

Table C-3 Cisco VXC 2211 Base LED Behavior (continued)

Power source

Client connected to power source (PoE or Power cube)

Press power button for power-on (quick button press - no more than 1/2 second)

Press Power button again for power-off (hold minimum 3 seconds)

Table C-4 Power Consumption

Thin Client Minimum Power Consumption Maximum Power Consumption

Cisco VXC 2111 12 watts1

1. The values listed indicate the power consumption for the thin client only. When the Cisco VXC 2111 is attached to a Cisco Unified IP Phone, you must add the phone power consumption to calculate the total power consumption of the system.

24 watts1

Cisco VXC 2211 12 watts 24 watts

GL-1Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

G L O S S A R Y

C

CA Certificate Authority

D

DHCP Dynamic Host Configuration Protocol

DNS Domain Name System

DNS SRV Domain Name System Service Record

E

EDID Extended Display Identification Data

F

FQDN Fully Qualified Domain Name

G

GPU Graphics Processing Unit

GUI Graphical User Interface

M

MIB Management Information Base

MTU Maximum Transmission Unit

Glossary

GL-2Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide

OL-25151-01

N

NTP Network Time Protocol

O

OS Operating System

OSD On Screen Display

P

PCoIP Personal Computer over Internet Protocol

PCoIP Zero Client Desktop client side of the PCoIP system (Cisco VXC client)

R

RDP Remote Desktop Protocol

S

SLP Service Location Protocol

SNMP Simple Network Management Protocol

SSL Secure Socket Layer (security protocol)

V

VPN Virtual Private Network

Z

Zero Client See PCoIP Zero Client

cisco virtualization experience client 2111/2211 pcoip ... · contents iv cisco virtualization...

Documents