How to deploy dedicated Ubuntu VDA through MCS

Step 1: Create Ubuntu 16.04 VM on Hypervisor such as VMware vSphere or Citrix XenServer

Step 2: Install Hypervisor tools

Step 3: Install Linux VDA

sudo dpkg -i <PATH>/<Linux VDA deb>

sudo apt-get install -f

Step 4: Set up the runtime environment to complete installation

sudo /opt/Citrix/VDA/sbin/ctxinstall.sh

Step 5: Configure mcs.conf

Change variables in /var/xdl/mcs/mcs.conf. The mcs.conf configuration file contains variables for setting MCS and the Linux VDA. The following are variables you can set as required:

dns: Sets the DNS IP address.

AD_INTEGRATION: Sets Winbind or SSSD (SSSD is not supported on SUSE).

WORKGROUP: Sets the workgroup name (case-sensitive) if it is configured in AD.

For dedicated single session VDA, set VDI_MODE=Y

Step 6: Shutdown VM and take snapshot.

Related:

  • No Related Posts

XenDesktop Active Directory Name Caching Explained

XenDesktop 5.x had provided a registry DesktopServerNameCacheNameRefreshPeriodMins to tune default Active Directory (AD) name cache refresh period.

CTX126704 – Registry Entries Used by XenDesktop 5.x Broker Service

The registry is still available for XenDesktop 7.x with minimum setting = 5 min

CTX138738 – Registry Key Entries Used by XenDesktop 7.x

To achieve a quick query of AD Machine & User name related to XenDesktop Site, Citrix Broker Service is designed to cache these name info in XenDesktop Database, specifically:

Tablechb_State.Controllers stores Delivery Controller SAM name and DNS Name

Tablechb_State.AccountNames stores AD User account SAM name, User Principal Name (UPN) and Common Name (CN)

Tablechb_State.WorkerNames stores AD Machine SAM name and DNS Name

By Default, Citrix Broker Service will synchronize Machine & User name changes with Active Directory every 24 hours and then refresh Name Cache in Database.

It can be monitored through CDF trace:

**********************

15:48:13:05827,1992,2300,0,***,***,***,***,***,CDF_NET_INFO,”ControllerNameCache: start refresh…”,””

15:48:13:09241,1992,2300,0,***,***,***,***,***,CDF_NET_INFO,”ControllerNameCache: refresh complete, 1 entries updated”,””

15:48:34:43042,6540,2300,0,***,***,***,***,***,CDF_NET_INFO,”WorkerNameCache: start refresh…”,””

15:48:34:50038,6540,2300,0,***,***,***,***,***,CDF_NET_INFO,”WorkerNameCache: refresh complete, 7 entries updated”,””

15:48:39:73442,4400,2300,0,***,***,***,***,***,CDF_NET_INFO,”AccountNameCache: start refresh…”,””

15:48:39:73565,4400,2300,0,***,***,***,***,***,CDF_NET_INFO,”AccountNameCache: refresh complete, 0 entries updated”,””

*************************

Under the hood, three Store Procedures chb_state.UpdateControllerNames(), chb_State.UpdateAccountNamesBySid() and chb_State.UpdateWorkerNames() will apply the new data to above 3 tables respectively.

XenDesktop PowerShell provides a way to refresh Name Cache immediately for AD Machine and User name changes:

> asnp citrix*

> Update-BrokerNameCache –Machines

> Update-BrokerNameCache -Users

Example

  1. Suppose we got a desktop assigned with an AD user named CtxNameCache.

    User-added image

  2. Change CtxNameCache login name to NameCache_new from AD.

    User-added image

  3. Refresh Delivery Group page, User name won’t change until next Name cache refresh period comes.

  4. Run Update-BrokerNameCache –users to manually refresh the name cache.

    User-added image

  5. Refresh Delivery Group page, new login username is refreshed immediately.

    User-added image

Related:

  • No Related Posts

Voice call over AVAYA Softphone may have a choppy voice or humming sound after multiple users login, while using Receiver for Windows 

1. Enable the Audio policies as documented in this article:

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-6/xad-hdx-landing/xad-hdx-audio.html

Ensure Audio quality is set to Medium in Citrix audio policy

2. Added following in default.ica at C:inetpubwwwrootCitrixStoreApp_Datadefault.ica

; This is to enable Real-Time Transport

EnableRtpAudio=true

; This is to Allow Real-Time Transport Through gateway

EnableUDPThroughGateway=true

; This is to set audio quality to Medium

AudioBandwidthLimit=1-

; UDP Port range

RtpAudioLowestPort=16500

RtpAudioHighestPort=16509

3. Did a iisreset using following command on Storefront server < elevated command prompt>

iireset


4. Set HDX Adaptive Transport to “Preferred” in Citrix Policies


5. Do a group policy update on VDA hosting Avaya softphone application

gpupdate /force


6. The ICA file should have following entries:

[Avaya one-X Communi]

Address=XXX.XXX.XXX.XXX:1494

AudioBandwidthLimit=1-

AutologonAllowed=ON

BrowserProtocol=HTTPonTCP

CGPAddress=*:2598

ClearPassword=XXXXXXXXXXX

ClientAudio=On

DesiredColor=X

DesiredHRES=0

DesiredVRES=0

Domain=<Hexa Decimal>

DoNotUseDefaultCSL=On

EnableRtpAudio=true

EnableUDPThroughGateway=true

FontSmoothingType=0

HDXoverUDP=Preferred

InitialProgram=#Avaya one-X Communi

Launcher=WI

LaunchReference=<Hexa Decimal GUID>

LocHttpBrowserAddress=!

LogonTicket=<Hexa Decimal GUID>

LogonTicketType=CTXS1

LongCommandLine=

LPWD=687

NRWD=656

ProxyTimeout=30000

ProxyType=Auto

RtpAudioHighestPort=16509

RtpAudioLowestPort=16500

SessionsharingKey=<Hexa Decimal GUID>

SFRAllowed=Off

SSLEnable=Off

startSCD=XXXXXXXXXX

Title=Avaya one-X Communicator

TransportDriver=TCP/IP

TRWD=0

TWIMode=On

UDPCGPPort=XXX.XXX.XXX.XXX:2598

UDPICAPort=XXX.XXX.XXX.XX:1494

WinStationDriver=ICA 3.0

7. Test Avaya softphone, by calling an extension or direct phone number

Related:

VM’s Power State Does Not Update And Shows As “Unknown” After vCenter Server Reboots

This is an issue with Citrix hypervisor communication library plugin since version Xenapp/XenDesktop version 7.16.

When vCenter server goes alive after reboot i.e “https://<vCenter FQDN>/sdk” becomes accessible, BrokerHostingPlugin still fails to login the vCenter server with exception “The session is not authenticated.”.

CDF Traces from Delivery Controller

109369,0,2018/09/05 11:35:54:09721,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Attempting connection”,””

109370,0,2018/09/05 11:35:54:09729,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”***** Get Hypervisor Certificate for Connection to ‘https://vcenter.***.***/sdk‘ *****”,””

109371,1,2018/09/05 11:35:54:17750,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Certificate is untrusted: False”,””

109372,1,2018/09/05 11:35:54:17761,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Time elapsed to get the hypervisor certificate: 80ms”,””

109373,1,2018/09/05 11:35:54:17770,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”***** Login Connection – 0 to ‘https://vcenter.***.***/sdk‘ as ‘administrator’ *****”,””

109374,0,2018/09/05 11:35:54:49296,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”VMware plugin initialisation times: create service 0ms, content time 315ms, total 315ms”,””

109375,0,2018/09/05 11:35:54:49301,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Connected to ‘VMware vCenter Server 6.0.0 build-3018524′”,””

109376,0,2018/09/05 11:35:54:51280,1972,8384,1,BrokerHostingPlugin,,0,,1,Error,”System.Web.Services.Protocols.SoapException: The session is not authenticated.

109377,0,2018/09/05 11:35:54:51541,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Connection attempt threw exception System.Web.Services.Protocols.SoapException: The session is not authenticated.

109378,0,2018/09/05 11:35:54:51548,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Connection is still down”,””

109379,0,2018/09/05 11:35:54:51554,1972,8384,1,BrokerHostingPlugin,,0,,1,Information,”Sleeping for 00:00:30 before trying to reconnect again”,””

Related:

  • No Related Posts

Driver Disk for LSI megaraid sas 07.701.18.00+rc1 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.1.0 who use LSI’s megaraid-sas driver and wish to use the latest version of the following:

Driver Module Version
megaraid-sas 07.701.18.00+rc1

Note: The download on this article was updated on 30 Oct 2017 to correct an issue with the installation of the driver at host-install time.

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod megaraid-sas

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-avago-megaraid-sas-07.701.18.00+rc1.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=82a37d30-48f0-417b-8d7e-9ca2372c2fe3

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-avago-megaraid-sas-07.701.18.00+rc1.iso
File sha256 23ad4355f7e2d66ad2655f11f89135b1d1e2564defe5c9f63a8b8be8d66e42d6
Source Filename driver-avago-megaraid-sas-07.701.18.00+rc1-sources.iso
Source File sha256 128e002f39be7b1d38a9b9bb137a420c5472c54f19fb4550e45db2124ba69186
Zip Filename driver-avago-megaraid-sas-07.701.18.00+rc1.zip
Zip File sha256 252bdb42504cb4406ab55e876ee772b0970de51f9770e612454b73f29500e4ea
Size of the Zip file 0.20 MB

RPMs Provided

RPM Name
avago-megaraid-sas-07.701.18.00+rc1-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.1 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Intel i40e-2.0.23 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.1.0 who use Intel’s i40e driver and wish to use the latest version of the following:

Driver Module Version
i40e 2.0.23

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod i40e

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-intel-i40e-2.0.23.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=1e92c0a5-51c1-409a-98b7-6d6660ad3466

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-intel-i40e-2.0.23.iso
File sha256 feb83c981a055fa7a94d0097aa111c99109d76026b3d7b20a8420af563caaf56
Source Filename driver-intel-i40e-2.0.23-sources.iso
Source File sha256 17bc2e51506877261fd01cf8a96fa84e7d9b75e218b5e08adfbeec85586b5b99
Zip Filename driver-intel-i40e-2.0.23.zip
Zip File sha256 caffaa88c27fb730f88436e1d7edf509873136183946e21e61a169c0d5da9dcd
Size of the Zip file 0.68 MB

RPMs Provided

RPM Name
intel-i40e-2.0.23-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.1 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for LSI mpt3sas 22.00.00.00 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.1.0 who use LSI’s mpt3sas driver and wish to use the latest version of the following:

Driver Module Version
mpt3sas 22.00.00.00

Note: The download on this article was updated on 07 Dec 2017 to correct an issue with the installation of the driver at host-install time.

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod mpt3sas

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-avago-mpt3sas-22.00.00.00.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=4091a425-3ddd-4a14-887f-e3c7a147a111

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-avago-mpt3sas-22.00.00.00.iso
File sha256 a368bc1acb70e44af9f32d295abf3a60323afd70720338228ea0ca4ac5321bd2
Source Filename driver-avago-mpt3sas-22.00.00.00-sources.iso
Source File sha256 fcdaa13cf1ac6693f47b278ca073154b71a5fa260e25a9d0298e219ef6e4d718
Zip Filename driver-avago-mpt3sas-22.00.00.00.zip
Zip File sha256 7d4666b17c0662c0b3977e506bafc4458862cca98d7974df80ac4a4664ee3d2c
Size of the Zip file 0.48 MB

RPMs Provided

RPM Name
avago-mpt3sas-22.00.00.00-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer � 7.1 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Cisco enic 2.3.0.40 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.1.0 who use Cisco’s enic driver and wish to use the latest version of the following:

Driver Module Version
enic 2.3.0.40

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod enic

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-cisco-enic-2.3.0.40.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=e727bf68-07ea-4429-89a2-020a33907d85

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-cisco-enic-2.3.0.40.iso
File sha256 34fba3fc082689e9136c97327403dadc6343d03e2b009282d42611488ad69de4
Source Filename driver-cisco-enic-2.3.0.40-sources.iso
Source File sha256 010b07df6855b46e9d63fe4f8fffe2c3915adb45e6ed234ea8d8e986145a6ed2
Zip Filename driver-cisco-enic-2.3.0.40.zip
Zip File sha256 48051e0f4deb7d8bf1d172a5b585251bcf5f2a6d327bbaccb05862888067cfa4
Size of the Zip file 0.19 MB

RPMs Provided

RPM Name
cisco-enic-2.3.0.40-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.1 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Cisco fnic 1.6.0.34 – For XenServer 7.1

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.1.0 who use Cisco’s fnic driver and wish to use the latest version of the following:

Driver Module Version
fnic 1.6.0.34

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod fnic

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-cisco-fnic-1.6.0.34.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=2f7ef049-548b-4601-85d1-b8b6f73b4465

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-cisco-fnic-1.6.0.34.iso
File sha256 d13751465a417c2220ddc463ca0d0045a7134f8ac9f91c1ee12775b13527e597
Source Filename driver-cisco-fnic-1.6.0.34-sources.iso
Source File sha256 fa72605f35d78809818ac6d7ce09b65e1ee000baf967b607e723657630883c32
Zip Filename driver-cisco-fnic-1.6.0.34.zip
Zip File sha256 b86c2cbb30c339691cf773e0d5fca9ceb2b5b2539d921f0bd2c133e31344f61d
Size of the Zip file 0.74 MB

RPMs Provided

RPM Name
cisco-fnic-1.6.0.34-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.1 Supplemental Packs and the DDK Guide.

Related: