Running a QFARM command in XenApp 7.x


As most of you are aware by now, Qfarm command doesn’t run anymore in XenApp 7.x as it is a part of old IMA architecture.

With FMA, there are several ways to check the Server load, the easiest being using Citrix Studio and checking Load Index.

However, there is another method to check the load from using a PowerShell window and it is as below.

asnp citrix*
Get-BrokerMachine –Filter ‘SessionSupport –eq “MultiSession”’ –Property @(‘DNSName’,’LoadIndex’)

qfarm1

if you need more details, you could add more parameters in your command line as below

Get-BrokerMachine –Filter ‘SessionSupport –eq “MultiSession”’ –Property @(‘DNSName’,'WindowsConnectionSetting','SessionCount',’LoadIndex’)

The result from running the above command is as follows

qfarm2

Hope it’s useful for someone out there!!!

 

 

Advertisements

Qfarm/load does not Return any Server Load Information


Symptoms

When the command Qfarm/load is carried out, the server load information is not returned.

Cause

This issue is leaked because of the invalid zones that are associated with the servers in the farm. The issue is usually caused by zones being created and deleted, servers moving in and out of zones and not immediately being rebooted which can leave the servers with the old information.

Resolution

To resolve the issue, complete the following steps:

  • Run the following command from the command prompt of the Zone data Collector. This gathers the dynamic store information of Zone Data Collector:

Queryds /table:LMS_ServerLoadTable > c:\loadtable.txt
(The c:\ can be replaced by any local drive on the XenApp server)

  • Run a CDF trace for 30 seconds on all modules from the Zone Data Collector and simultaneously run the command Qfarm /load from the command prompt of the zone data collector.
  • Upload both the queryds output log and the cdftrace .etl file to the automatic support site for analysis.

To find the servers that have issues, open the queryds log in Notepad and look for any servers that are listed in a zone that does not exist.

In the cdf trace, look for the following errors:

  • “IMA_BUF_BinBuffer::ReadStringObject size<=0 00B895E4 0 00B88CBC 00B895E4 20
    and
  • Read fetch Errored Uid: 1796-000c-00006692 (the Uid will be different as it a unique identifier for the XenApp server)”

There must be a matching host ID in the queryds output log that shows the server that has the issue.

name : 1796-000c-00006692

host : XenAppServerName

zone : Zone 5

Once the server or servers have been identified, remove them from the server farm and run the command dscheck /full servers to ensure that the servers are no longer part of the farm.

Once that has been verified, the command qfarm /load must now run without issues, and then add the problem servers back to the farm, and the command qfarm /load must continue to work.

The issue can also occur if the server was removed from the farm but XenApp was not removed from the server. The XenApp might still contact the ZDC causing the issue. If yes, just turn off the machine to resolve the issue. The command queryds in the preceding section will not show the server.

Note: The local host cache must be recreated on all servers or on the zone data collector of the farm if the dscheck command shows the servers in the database after removal, and run the command dscheck with the clean switch to remove them.

More Information

Queryds utility is located on the XenApp install media under the support > debug folder.

CTX134966 – Citrix Diagnostics Toolkit – 32bit Edition

CTX135075 – Citrix Diagnostics Toolkit – 64bit Edition

CTX111961 – CDFControl

CTX130147 – Citrix Scout

CTX124406 – DSCHECK – XenApp Data Store Checker Tool Commands

CTX133983 – IMA Helper Tool