Showing posts with label technotes. Show all posts
Showing posts with label technotes. Show all posts

Friday, October 14, 2011

CTX128272 - Autosize Settings on FlexVols - created on NetApp Filers Might Require Modification - Citrix Knowledge Center

CTX128272 - Autosize Settings on FlexVols - created on NetApp Filers Might Require Modification - Citrix Knowledge Center:

Autosize Settings on FlexVols - created on NetApp Filers Might Require Modification

Document ID: CTX128272 / Created On: Oct 13, 2011 / Updated On: Oct 13, 2011
Average Rating: not yet rated

Symptoms

The following error might appear when you start a Virtual machine:

“Unable to grow volume '' to recover space: Volume cannot be grown beyond maximum growth limit”

This message implies that the autosize option is enabled on the NetApp Filer and the limit for volume growth is set to the default value or too low a value for the volume usage.

Background

The Best Practices guide for using Citrix XenServer 5.x with NetApp Filers recommends using the Autosize option to facilitate Thin Provisioning for the volumes on the storage array. This option might need configuring from the default of 58MB if it is in use.

Resolution

To resolve the preceding issue, Autosize Settings on FlexVols, which is created on NetApp Filers, might need some modification.

To check and resize the Autosize value, complete the following procedure:

  1. To check the current Autosize settings, run the following command on the NetApp Filer:
    vol autosize

    Following is the format of the output of the preceding command:
    “Volume autosize is currently ON for volume '<volume name>'.
    The volume is set to grow to a maximum of , in increments of .”
    Note
    : If the maximum value displayed is 58980 KB with increments set to 80 MB then obviously the volume will not be able to grow at all and the virtual machine will be unusable.
    Therefore, set a more reasonable limit on the volume growth and the increment size as well.
  2. To resize the autosize value, run the following command:
    vol autosize [-m [k|m|g|t]] [-i [k|m|g|t]] [ on | off | reset ]

This document applies to:

Thursday, October 13, 2011

CTX131150 - RadeFastLaunch improves the launch time - Citrix Knowledge Center

CTX131150 - RadeFastLaunch improves the launch time - Citrix Knowledge Center:

'via Blog this'

CTX126043 - How to Create a Staggered Scheduled Server Reboot Policy in XenApp 6.x - Citrix Knowledge Center

CTX126043 - How to Create a Staggered Scheduled Server Reboot Policy in XenApp 6.x - Citrix Knowledge Center:

'via Blog this'

CTX131156 - HP Proliant BL 460G7/465G7 Unable to Boot from Boot Device Manager Start Imaging Process - Citrix Knowledge Center

CTX131156 - HP Proliant BL 460G7/465G7 Unable to Boot from Boot Device Manager Start Imaging Process - Citrix Knowledge Center:

HP Proliant BL 460G7/465G7 Unable to Boot from Boot Device Manager Start Imaging Process

Document ID: CTX131156 / Created On: Oct 12, 2011 / Updated On: Oct 12, 2011
Average Rating: not yet rated

Symptoms

Boot Device Manager (BDM) Boot on HP Proliant BL 460G7 or BL465G7 server fails after installing Provisioning Services software.

The following screen shot is an example of the behavior:

Cause

While the exact root cause is being investigated by Citrix, the issue only occurs on the BL 460G7 and 465G7 servers, which use the HP branded Emulex NIC cards. NIC cards affected include, but are not limited to, the HP NC553i Dual Port 10gb Converged Network Adapter and HP NC522m Dual Port 10gb Multifunction Adapter.

Servers using the Broadcom cards do not experience the issue. Citrix and HP engineering teams are fully engaged and working jointly to find a resolution to this issue.

Workaround

Contact HP for a fix for this issue.

  • HP Support has a bundle containing a zipped ISO image for the NC55x firmware , BDM utility and Citrix instruction on how to apply the BDM hotfix.

Alternatively, replace the Emulex cards with Broadcom cards on the server affected.

Note: This hotfix is not applicable for Provisioning Services 6.0. Follow up with HP to get a timeframe for when the hotfix will be available for Provisioning Services 6.0 version and later.


Wednesday, October 12, 2011

CTX131001 - XenApp 6.5 - Implementing ICA MultiStream / MultiPort - Virtual Channel Groups and Priorities - Citrix Knowledge Center

CTX131001 - XenApp 6.5 - Implementing ICA MultiStream / MultiPort - Virtual Channel Groups and Priorities - Citrix Knowledge Center:

'via Blog this'

Summary

This article contains information about the Citrix ICA Channels and their priorities. These channels and priorities are used in XenApp 6.5 Multi-Stream Multi-Port ICA.

Background

In XenApp 6.5 and XenDesktop 5.5, with Receiver 3.0 (including Online Plugin 13.0), Citrix introduced support for true network based Quality of Service (QoS) to the ICA/HDX protocol.

QoS is a mechanism to prioritize network traffic to help ensure that the most important data gets through the network as quickly as possible.

Multi-Stream and Multi-Port ICA allow assigning a separate TCP Port for each of the four groups of ICA Channels. These TCP ports can then be assigned unique priorities on Network Devices.

To decide if it is required and to decide how to implement Multi-Stream and Multi-Port ICA in an environment, it is necessary to understand what the ICA Channels are, and how they are divided into the four priority groups. This article contains these details.

Default ICA Virtual Channel Groups and Priorities

The following table lists the default priorities for each ICA Virtual Channel in XenApp 6.5. This table includes both Single Stream ICA, and Multi-Stream ICA (with Multi-Stream Policy enabled).

Note: These priorities apply to XenApp 6.5.

The following are the numerical priorities in the XenApp 6.5 ICA/GPO:

  • Very High = 0
  • High = 1
  • Medium = 2
  • Low = 3

Assuming that Branch Repeater is not in use in the environment, to implement Multi-Stream and Multi-Port ICA, complete the following tasks:

  1. Enable Session Reliability, and therefore enable CGP.
    Note
    : With Branch Repeater, CGP is not required.
  2. Enable and configure the Multi-Stream and Multi-Port ICA/GPO Policies.
  3. Configure Network Devices to assign QoS as desired to each configured port.

Default ICA Virtual Channel Priorities

Channel Name

Description

Single Stream (XenApp 6.5)

Multi-stream

(XenApp 6.5)

CTXCAM

Client audio mapping

0

0

CTXTWI

Seamless Windows screen update data (ThinWire)

0

1

CTXCTL

Citrix Control Virtual Channel

0*

1

CTXEUEM

End User Experience Monitoring

0*

1

CTXFLASH

Citrix Flash Redirection

0*

2

CTXGUSB

USB Redirection

0*

2

CTXSBR

No longer used.
Previously: Citrix Browser Acceleration

0*

1

CTXSCRD

Smartcard

0*

1

CTXCLIP

Clipboard

1

2

CTXLIC

License management

1

1

CTXPN

Program Neighborhood

1

1

CTXTW

Remote Windows screen update data (ThinWire)

1

1

CTXVFM

Video server video (not ThinWire video)

1

1

CTXCCM

Client COM port mapping

2

3

CTXCDM

Client drive mapping

2

2

CTXMM

Citrix Windows Multimedia Redirection

2

2

CTXCM

Client management (Auto Client Update)

3

3

CTXCOM1

Printer mapping for non-spooling client (Thin client devices)

3

3

CTXCOM2

Printer mapping for non-spooling client (Thin client devices)

3

3

CTXCPM

Printer mapping for spooling clients

3

3

CTXLPT1

Printer mapping for non-spooling client (Thin client devices)

3

3

CTXLPT2

Printer mapping for non-spooling client (Thin client devices)

3

3

OEMOEM

Used by Original Equipment Manufacturers (OEMs)

3

3

OEMOEM2

Used by Original Equipment Manufacturers (OEMs)

3

3