Baker’s Half Dozen — Episode 12

If you’ve got questions about this episode, or a question you’d like Matt to answer in the next episode, comment below or tweet Matt using #BakersHalfDozen. If you have finished Netflix, not a problem. You now have a new Baker’s Half Dozen to watch! On today’s episode we discuss how you, the viewer, can help fight the coronavirus at home by using your PC. We also discuss the importance of keeping Atomic Time, and how your car is a snitch! And finally, we want you to share what piece of old technology you refuse to part … READ MORE

Related:

VMware vSphere 6.5 – Citrix Known Issues

Note: This is a live article, and is updated as and when the new information becomes available.

The following information outlines the issues and their solutions:

Issue 1

Some Virtual Machines may fail to register when trying to boot large number of VMs in a catalog on Dell PowerEdge servers using PERC 8/PERC 9 storage controller.

Problem Cause

Lsi_mr3 PERC drivers installed with VMware ESXi is sometimes found to be incompatible with PERC 8/PERC 9 installed on the newest 13 generation PowerEdge servers

Solution

To resolve this issue, the appropriate PERC driver ‘megaraid_perc9’ should be installed. The driver is available on Dell or VMware support sites.

Please refer to http://www.dell.com/Support/Article/in/en/indhs1/SLN297261 for more information.


Issue 2

Windows 10 v1607 VDA fails to launch when GPU pass-through is enabled on NVIDIA K-Series Graphic cards through DirectPath I/O for PCI Devices. This issue impacts HDX 3D Pro VDAs with vDedicated Graphics Acceleration (vDGA) enabled.

Solution

NVIDIA has released a new driver for K-Series Graphics cards. Please update the Graphics card driver on the system to v372.90 or later


Issue 3

An increased load on storage systems in terms of IOPS may be observed when using VMFS6 with non-persistent Windows10 VDA deployed through MCS.

Solution

There is no solution to this issue. Citrix is investigating this issue.

Workaround

Users are recommended to use VMFS5. Users considering VMFS6 should try it in a non-production environment to determine if the storage system used can support the higher load with VMFS6.

Issue 4

PVS target device booted from vdisk with USB Controller 2.0 attached may fail to boot OR freezes at Windows splash screen.

Solution

There is no solution to this issue. Citrix is investigating this issue.

Workaround

Users are advised to attach USB 3.0 controller to the target device on ESXi 6.5 platform.


Issue 5

On Virtual Machine’s (hosted on vSphere) with VMWare tools (10.3.2.x or above) installed, a failure may be seen with standalone installation of Storefront or while upgrading Storefront part of Virtual Apps and Desktops 7 1906 OR 1909. An error ‘An error occurred with the operation for Storefront’ may be seen.

[WSP-4895]

Solution

This issue is fixed with VMtool v11.0. Upgrade VMWare tools to v11 or newer before attempting to install/upgrade of Storefront.

Related:

question about http referer and server.response.code

I need a solution

We have employees who use an application which will display a map when the map button is clicked. This has stopped working. I ran a trace and what I see is a server.response.code of 400 and a client response.code of 400. Does that mean the proxy got a 400 from the server it was trying to go to (in this case arcgis.com)?

When I look at what is being sent there is a malformed url but it is in the http referer part of the header, would this still affect it?  I see other times when they go to the site and if there is no referer they get a 400/400. 

This is snippets of the trace… (note the “//” in the referer line which make it malformed)

Code 200/200 with no referer…

GET http://js.arcgis.com/3.15/esri/dijit/BasemapGallery.js
  DNS lookup was unrestricted
origin server next-hop IP address=13.32.80.95
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
user: unauthenticated
authentication status=’not_attempted’ authorization status=’not_attempted’
  url.category: COT_Services@Policy;COT_Whitelist@Policy;Technology/Internet@Blue Coat
    total categorization time: 1
    static categorization time: 1
server.response.code: 200
client.response.code: 200

Similar url but with referer and now code 400/400

GET http://js.arcgis.com/3.15/esri/nls/jsapi_en-us.js
  DNS lookup was unrestricted
origin server next-hop IP address=13.32.80.95
Referer: http://tpdrms80:1911/rms/web_components//arcGIS/arcGIS.html
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/538.1 (KHTML, like Gecko) Genero Desktop Client Safari/538.1
user: unauthenticated
authentication status=’not_attempted’ authorization status=’not_attempted’
  url.category: COT_Services@Policy;COT_Whitelist@Policy;Technology/Internet@Blue Coat
    total categorization time: 14
    static categorization time: 14
server.response.code: 400
client.response.code: 400

Also, this is the second time since the categorization was changed a week or so ago that we have had this issue, the other site was online811, which also had the double // in certain urls in their site. The proxy response was malformed request, and if I removed one of the “/” the url would work. We have been using both of the sites forever, and the vendors say they made no changes.

Any assistance is greatly appreciated. We have ProxySG 900-10B with 6.6.5.17

0

Related:

HPE Networking blog will retire

After a long stay, this HPE Networking blog is to be retired from the HPE Community. You will however be able to find data center networking content and more on Aruba Blog: blogs.arubanetworks.com.

Thank you to everyone who over the years followed this blog or subscribed to the feed and to those who contributed to the content.

MargaretN
HPE Community Manager
Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise
CM_Cert_Logo_BW.png

Related:

  • No Related Posts

VxRail: after upgrading to 4.5.210 , vCenter is complaining about LSI driver version warning

Article Number: 521197 Article Version: 3 Article Type: Break Fix



VxRail Appliance Family,VxRail Appliance Series,VxRail 460 and 470 Nodes,VxRail V Series Nodes,VxRail S Series Nodes,VxRail P Series Nodes

After upgrading VxRail to 4.5.210 in vCenter we can see the following warning for LSI drivers.

User-added image

vmhba0 Avago (LSI Logic) Dell HBA330 lsi_msgpt3 warning

The HCL could not be updated in time for the v4.5.210 release.

Upgrade to v 4.5.210

The vSAN HCL is in the process of being updated to reflect that the currently installed driver is on the HCL. This is a known issue that is actively being worked on. The currently installed driver is fully tested and supported.

Note that , there is no need to update the lsi driver at this time and the customers should never update individual components of a VxRail cluster.

Related:

Has anyone had any luck excluding Google Drive FS from scans?

I need a solution

We’re using the Google Drive FS client, which creates a G: drive on the host. At first the problem was with performance. Large directories were almost unusable because even though the FS client index was complete, the SEP client constantly scanned the G: drive. As we could see the volume attempting to mount at G: when the drive was accessed, we added a static mount point per Google.

That seems to have stopped the SEP client from continually scanning the drive when users are browsing, however we’re still having problems with exclusions.

We’ve explicitly excluded certain files, directories and the drive G: itself but the client seems to ignore that part of the policy and is still generating false positives.

I’ve found tech docs per McAfee and Kaspersky that say the problem with their product was McAfee was also seeing the Google Drive FS drive letter as a removable drive.

Sure enough if we disable scaning removable drives, then the G: drive is not scanned.

Obviously we don’t want to turn off scanning for all removable drives but we can’t find a way around this without doing just that. Does anyone else have any experience with this and know of a workaround?

I did log a support ticket but I didn’t get anywhere and finally just let it go out of frustration.

0

Related: