DHCP change causes loss of IPV4 address

If you are using DHCP reservations to assign your IP addressing for your appliance VMs, any prob;lems with DHCP can break your addressing. For ninstance, if the DHCP server on your local subnet becomes unresponsive when your address lease expires, you will lose your IP address without even needing to reboot. Or if your DHCP server changes the range it’s allowed to lease, or even if it gives your address to another machine, you may lose networking.

The solution is, if you can’t completely trust your DHCP reservations, to set a fixed address directly on the appliance VM. Login as the “administrator” account through the VM console or SSH and set the networking configuration there.

In addition to checking from the “administrator” configuration menu, you can see whether your appliance is using DHCP by checking /var/log/messages for events from dhclient:

Feb 19 07:28:19 localhost dhclient[999]: DHCPREQUEST on eth0 to 128.104.155.41 port 67 (xid=0x426f83d6)

Feb 19 07:28:19 localhost dhclient[999]: DHCPACK from 128.104.155.41 (xid=0x426f83d6)

Feb 19 07:28:21 localhost dhclient[999]: bound to 10.128.101.251 — renewal in 120621 seconds.

Errors would look more like this:

Feb 25 06:01:26 localhost dhclient[935]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x469ee39c)

Feb 25 06:01:41 localhost dhclient[935]: No DHCPOFFERS received.

Related:

Elevated CPU usage by vmsp.exe on XenDesktop Windows 10 VDA with TPM

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

How to verify if Auto-discovery is enabled for a domain in XenMobile ADS

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

Receiver for Windows 4.9LTSR/4.10 – Citix HDX Engine crash when connecting to Linux VDA

There are two possible workarounds for this issue:

1. If the Receiver is a clean install and you see the partial grey screen issue, reducing the number of virtual channels on the Receiver side ( so that they are less than or equal to 32 in number ) would resolve the problem. To reduce the virtual channels, perform the following steps:

1. Exit Receiver from System tray.

2. Open Registry on the client machine.

3. Browse to the following key:

HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixICA ClientEngineConfigurationAdvancedModulesICA 3.0

Modify the VirtualDriver key on the right hand pane and remove the entries that are not needed in your environment. Some candidates are:

vd3d (Desktop Composition Redirection – deprecated)

Framehawk (recommended only for extreme WAN scenarios and where server resource usage is not an issue)

ZL_FONT (Zero Latency, only supported up to XA 6.5)

ZLC (Zero Latency, only supported up to XA 6.5)

For example, removing vd3d and Framehawk, following would be the contents of VirtualDriver key:

Thinwire3.0, ClientDrive, ClientPrinterQueue, ClientPrinterPort, Clipboard, ClientComm, ClientAudio, LicenseHandler, TWI,ZL_FONT,ZLC,SmartCard,Multimedia,ICACTL,SSPI,TwainRdr,UserExperience,VDTUI,DVCAdapter,GenericUSB, Flash,FlashV2,MobileReceiver,Sensor,Multitouch,VDIME,WebPageRedirection,PortForward,NSAP

2. If the Receiver is an upgrade from 4.9 to 4.10, uninstalling the receiver and performing a clean install (instead of upgrade) will resolve the issue. This is because the clean install has a different ordering of Virtual Channels compared to an upgrade.

Citrix team is currently working on enhancing the Linux VDA to support 64 Virtual channels. This support is expected to be included in the future version of Linux VDA.

Related:

  • No Related Posts

AMD MxGPU Tech Preview

Note: This Tech Preview has now been superseded. In XenServer 7.4, AMD’s MxGPU is fully supported for production use. For more information, see the XenServer 7.4 documentation.

XenServer 7.2 contains a technical preview of AMD’s multi-user GPU technology, MxGPU. This technical preview is suitable for early adopters to evaluate the technology with Windows 7 SP1 (64-bit) and Windows 10 (64-bit) guests, but may not be suitable for production environments.

AMDs MxGPU enables multiple Virtual Machines (VM) to have direct access to a portion of a single physical GPU, by making use of Single Root I/O Virtualisation. The same AMD graphics driver deployed on non-virtualized Operating Systems can be used inside the guest.

Guest VMs use MxGPU GPUs in the same manner as a physical GPU that has been passed through by the hypervisor; an AMD graphics driver loaded in the guest VM provides direct access to the GPU for performance critical fast paths.

Note: This MxGPU technical preview does not currently have supported hardware configurations with XenServer 7.2. Details on supported configurations will be available on the XenServer Hardware Compatibility List

1. Licensing Note

MxGPU is available for XenServer Enterprise edition customers, or those who have access to XenServer through their XenApp/XenDesktop entitlement. To learn more about XenServer editions, and to find out how to upgrade, visit the Citrix website here. For detailed information on Licensing, refer to the XenServer Licensing FAQ on the Citrix Product Documentation website.

2. Available AMD MxGPU vGPU Types

AMD MxGPU cards can contain multiple Graphics Processing Units (gpu). For example, S7150 cards contain one physical GPUs, and S7150x2 cards contain two GPUs. Each physical GPU (pgpu) can host several different types of virtual GPU (vgpu). vgpu types split a pgpu into a pre-defined number of vgpus, each with an equal share of the framebuffer and graphics processing capabilities. The different vgpu types are targeted at different classes of workload with the vgpu types that split a pgpu into a fewer number of pieces being more suitable for intensive workloads.

Note: At any given time, vgpus hosted on a physical gpu must all be of the same type. However, there is no corresponding restriction between physical gpus on the same card. This restriction is automatic and may cause unexpected capacity planning issues.

3. AMD MxGPU System Requirements

  • AMD FirePro S7100-series GPUs
  • XenServer Enterprise edition (or access to XenServer through a XenDesktop/XenApp entitlement).
  • A server capable of hosting XenServer and AMD MxGPU cards. The list of servers validated by AMD can be found on AMDs website (http://www.amd.com/citrix).
  • AMD MxGPU host driver public key (Attached to this KB article)
  • AMD MxGPU host drivers for XenServer
  • AMD FirePro in-guest drivers, suitable for MxGPU on XenServer
  • To run XenDesktop with VMs running AMD MxGPU, you will also need: XenDesktop 7.13 or later, full installation.
  • System BIOS configured to support SR-IOV, with the MxGPU configured as the secondary adapter.

4. Preparation Overview

  • Install XenServer
  • Install the AMD MxGPU host driver public key
  • Install the AMD MxGPU host drivers for XenServer
  • Reboot the XenServer host

5. Installation on XenServer 7.2

XenServer 7.2 is available for download from the XenServer Downloads page.

Customers should install:

  • XenServer 7.2 Base Installation ISO
  • XenCenter 7.2 Windows Management Console

Refer to the XenServer Installation Guide on the Citrix Product Documentation website for comprehensive details on installation. Please see section 1 for details on licensing requirements.

6. Installing the AMD MxGPU host driver for XenServer

Before installing the MxGPU host driver, the GPG key must be installed in dom0. Once this feature is formally supported, and out of tech preview, this step will not be required. In order to run the following, make sure you download the RPM-GPG-KEY-AMD-MXGPU attachment on this article, copy it to the host and reference the correct location in the following commands.

Note: The names and versions below are examples and may be different in your environment.

  1. Before installing the MxGPU host driver, the GPG key must be installed in dom0. Once this feature is formally supported, and out of tech preview, this step will not be required. In order to run the following, make sure you copy RPM-GPG-KEY-AMD-MXGPU to the host and referencing the correct location

    [root@xenserver ~]# /opt/xensource/debug/import-update-key RPM-GPG-KEY-AMD-MXGPU

    gpg: key 09DD72A4: public key “RPM-GPG-KEY-AMD-MXGPU (GPG key for AMD MxGPU) <MxGPU@amd.com>” imported



    pub 2048R/09DD72A4 created: 2017-03-16 expires: never usage: SC

    trust: ultimate validity: unknown

    [ unknown] (1). RPM-GPG-KEY-AMD-MXGPU (GPG key for AMD MxGPU) MxGPU@amd.com

    [root@xenserver ~]#

  2. The Update can then be installed using XenCenter (Tools > Install Update > Select update or supplemental pack for disk) or using the xe CLI command xe-install-supplemental-pack. As with the GPG key, copy the Update to the host and reference the correct location.

    [root@xenserver ~]# xe-install-supplemental-pack mxgpu-0.9.amd.iso

    [root@xenserver ~]# xe update-list

    uuid ( RO) : b9c2969d-9ed3-4432-9b86-8e9399b0e8d7

    name-label ( RO): mxgpu

    name-description ( RO): MxGPU Host Driver

    version ( RO): 0.9

    installation-size ( RO): 595329

    hosts (SRO): 369a34f4-f273-4c0f-9c77-0c0f59220412

    after-apply-guidance (SRO):

    [root@xenserver ~]#

  3. Reboot the XenServer host:

    [root@xenserver ~]# shutdown -r now

    Broadcast message from root (pts/1) Mon May 09 13:05:31 2016):

    [root@xenserver ~]#

  4. After rebooting the XenServer host, verify that the MxGPU package has installed and loaded correctly by checking that the gim kernel driver can be loaded: [root@xenserver ~]# modinfo gim

    filename: /lib/modules/4.4.0+10/updates/gim.ko

    version: 0.9.0-k



    [root@xenserver ~]# modprobe gim

    [root@xenserver ~]#

  5. Verify that the gim kernel driver successfully created MxGPU Virtual Functions, which will then be provided to the guests. The Virtual Functions will have the “S7150V” identifier, as in the following output:

    [root@xenserver ~]# lspci | grep “FirePro S7150”

    05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XT GL [FirePro S7150]

    05:02.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XTV GL [FirePro S7150V]

    05:02.1 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XTV GL [FirePro S7150V]

    05:02.2 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XTV GL [FirePro S7150V]



    [root@xenserver ~]#

  6. Use the GPU tab in XenCenter to confirm that MxGPU Virtual GPU types are listed as available on the system:User-added image

7. Create a MxGPU Enabled VM

Before configuring a VM to use MxGPU, the guest VM must be installed. Note that this technical preview of MxGPU will only work with Windows 7 SP1 (64-bit) and Windows 10 (64-bit).

Once the VM is installed, follow the XenServer “Configuring Graphics” guide for XenServer 7.2 section “5. Create a Virtual GPU or GPU Pass-Through Enabled VM” to complete the configuration.

8. Known Restrictions

  • A host must either use MxGPU or Passthrough of a GPU; you cannot dynamically switch between these. The host must be rebooted before switching between these modes.
  • Various features, including VM Suspend/Resume, Live Migration and High Availability are not compatible with MxGPU.
  • Some systems may require a vendor-specific VBIOS. Ensure that the latest VBIOS available from the system vendor is applied.

9. Providing Feedback and Raising Issues

As this feature is a technical preview, feedback should be provided via https://tracker.citrix.com rather than with Citrix Support.

  1. Create an account: Visit https://tracker.citrix.com, click the “Sign up” link and follow the wizard for help in signing up
  2. Create an issue in the XenServer Feedback (XSB) project, selecting the appropriate issue type (Enquiry, Bug or Improvement)
  3. Select the “AMD MxGPU” component
  4. Fill in as many details about the environment and problem you are seeing
  5. Attach a Server Status Report or bugtool to the ticket (see https://support.citrix.com/article/CTX125372)

Related:

How to use AMD MxGPU with XenServer

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

NetScaler MAS Does Not Retrieve HDX Insight Report from NetScaler for More Than an Hour

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

How to Configure NetScaler MAS Simplified Audit Log Management

To configure NetScaler MAS simplified audit log management:

1. Navigate to System > Auditing > Syslog Messages.

User-added image

2. Under Syslog Messages you will see audit logs messages. You can choose to filter them based on Module, Event Type, or Severity.

User-added image

Additionally, you can click within the syslog message to gather information on what kind of module, event type any particular message was.

3. Module is selected and the module (GUI) gets highlighted:

User-added image

User-added image

5. You can use that to learn what modules, or events type, or severity you want to filter with and select them from the Filter By menu on the right hand side of the screen.

User-added image

4. Event Type gets selected (CMD_EXECUTED).

Related:

Service/Load Balancing State is Not Shown as DOWN on NetScaler MAS Even if the Resource is DOWN on NetScaler

NetScaler MAS will only know about the virtual server being down when it polls that instance. Every 30 minutes, entities are polled by NetScaler MAS by using NITRO calls. An entity is either a policy, virtual server, service, or action attached to a NetScaler instance. While this poling interval is configurable, you cannot set it to less than 10 minutes. To configure it, navigate to Networks > Network Functions > Settings > Configure Polling Interval for Entities. You can also poll the entities configuration when required by navigating to Networks > Network Functions > Load Balancing > Entities Configuration > Poll Now.

User-added image

But you will see the status change in the Application dashboard of NetScaler MAS because it monitors the applications in real time.

User-added image

You will also receive traps for this event and you can see that under Infrastructure > Events > Event Messages. You can see the output of the MAS poll in mps_config.log and mps_inventory.log files.

Related:

Unable to Add Instance to NetScaler MAS

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts