xenclient enterprise 5.0

XenClient Enterprise 5.0Mobile Broadband Wireless Networking

Copyright 2013 Citrix


Table of Contents

Broadband Networking Options Page 3

Method 1: Assignment to Engine Page 4

Method 2: Assignment to a VM Page 5

Method 3: Mobile Hotspot Devices Page 6

General Issues with Broadband Modems in Engine Page 7

SIM PINs Page 8

Broadband Modem Device Assignment Page 9

Broadband Modem Control Panel Page 10

List of Tested Broadband Modems Page 11



Method Device Connection Method Current Status

1 3G/4G Modem Device assigned to Engine. Broadband network connection managed by Engine.

Suffers from limited modem device support in the Engine. No longer recommended.

2 3G/4G Modem Device assigned to a VM. Broadband network connection managed by the VM.

An area of proposed development, to improve reliability and performance of broadband modems passed through to specific VMs.

3 Hotspot/MiFi Engine connects to local WiFi network created by the device. Network connection managed in the Engine like any other wireless network.

Current recommended best practice. Aligns with products and services offered by the major broadband carriers.

There are three ways to connect XenClient Enterprise to a wireless broadband network, based on the broadband device being used, and how the device is connected or managed within XenClient Enterprise.

Broadband Networking Options



Advantages

•The broadband network connection can be shared between the Engine and all VMs.

•IP address and other network configuration in the VM doesn’t change when the Engine switches between:

• Wireless broadband• Wireless LAN/WiFi• Wired LAN (in NAT mode)

Disadvantages

•The set of compatible modem devices is very limited.

•SIM PINs not supported for most devices.

•Device-specific software can’t be used (for example, Verizon Access Manager).

• Some devices need software to work properly with all features enabled.

• Users may be accustomed to using this software.

•This approach is no longer recommended due to modem compatibility issues. Current recommended best practice is to use mobile hotspot devices.

Method 1: Assignment to Engine



Advantages

•In theory, there should be much broader device support in Windows.

•Device-specific software can be installed into the VM and used with the modem.

Disadvantages

•The Engine won’t have access to the broadband network.

•If multiple VMs are deployed to Engine, only one VM will have access to the broadband modem.

•In practice, some modems may not work when passed through to the VM, due to:

• Conflicts between the modem device, or management software, and how networking is configured within the VM.

• Device-specific USB issues between the device, the Engine, and the VM.

Method 2: Assignment to a VM



• Mobile hotspot devices are the current recommended method for using XenClient Enterprise with wireless broadband networks.

• The hotspot connects to the broadband network and creates a local WiFi network.

• The Engine connects to the local WiFi network. It is managed as a Wireless LAN connection, not a wireless broadband connection.

• This is the best of both worlds.

• Management of the broadband network connection is moved from the Engine to a device specifically designed for the purpose.

• But the broadband network connection can still be shared between the Engine and all VMs.

• Many smart phones (including iPhone) can be configured as mobile hotspots.

LocalWiFi

Network

MobileHotspot VM

VM

Method 3: Mobile Hotspot Devices



• There is limited support in Linux for broadband modem devices.• Especially devices that need management software to function properly.• Fundamental incompatibilities with GOBI-3000 and GOBI-4000 devices.

• Broadband modem devices evolve rapidly.• Every new USB product ID needs special handling in the Engine.• Can’t be done through policy, an actual Engine update is often needed.

• Most modems have a peculiar behavior when attached to a computer.• They initially appear as USB optical drives.• The OS is expected to install drivers from the optical drive.• Then the device is reset and appears as a broadband modem.• Recognition of the optical drive as a modem requires device-specific

handling in the Engine.

• Adding support for a new modem requires access to the device for testing.• Also the broadband network the device is configured to use.• This is problematic for foreign carriers.

General Issues with Broadband Modems in Engine



• Each broadband modem includes a SIM (Subscriber Identity Module), usually on a removable card.

• The SIM is used to store data about the carrier and subscriber account, such as the modem’s phone number.

• SIM PINs are not supported in the Engine. If a SIM PIN is set, the modem may not function properly, or it might not appear in the Engine broadband networking control panel.

• If a SIM PIN is set, it might be necessary to clear the PIN from the SIM before the Engine can use the modem. For instructions on clearing the SIM PIN, check with documentation provided by the carrier or modem vendor.

• SIM PINs may work if the modem is passed through to a VM instead of being managed by the Engine.

SIM PINs



Broadband modems will often be listed as type “USB Storage”. This provides an insight into how these devices work at the USB level, which can make them difficult to support.

If the modem is assigned to the Engine, then the Engine will manage the device and the broadband network connection. The network connection can be shared between the Engine and all VMs.

If the modem is assigned to a specific VM, then the VM will manage the device and the broadband network connection. The network connection cannot be shared with the Engine or other VMs.

Broadband Modem Device Assignment



• The Engine networking control panel includes a “Broadband Modem” section.• Only appears if a modem is connected and assigned to the Engine.• If it doesn’t appear:

• Make sure the device is assigned to the Engine.• If the modem has a SIM PIN set, try clearing the PIN from the SIM.• Otherwise, it may not be a compatible device.

Broadband Modem Control Panel



Device Vendor ID

Device ID Carrier Notes

Qualcomm GOBI-2000 (GSM) 05c6 9205 AT&T Internal USB.

Ericsson F3507g Mobile Broadband Module 0bdb 1900 AT&T USB Dongle.

Sierra Wireless Mini Card 1199 6813 AT&T Internal USB.

Sierra Wireless 598 1199 0025 Sprint USB Dongle.

Huawei UMG1831 (Webconnect Rocket) 12d1 1446 TMobile USB Dongle.

LG 1004 6141 USB Dongle.

Option GL1505 0af0 d057 AT&T USB Dongle.

• Broadband modems recently tested with XenClient Enterprise are shown below.

• This is for modems assigned to and managed by the Engine, not passed through to a VM.

• The list is short and includes devices that are old and possibly obsolete.

• Newer devices may or may not work.

• Each device must be tested individually.

• GOBI-3000 and GOBI-4000 devices generally don’t work.

List of Tested Broadband Modems

xenclient enterprise 5.0

Documents