Our first publication of Framehawk was get on the forums a lot of positive feedback.
This month, the support has been extended to remote mobile users with the release of NetScaler Gateway 11.0.62, and the new version 6.0 of Citrix Receiver for iOS added Framehawk support.
Check out the latest Framehawk Administrator's Guide for updated instructions.
Framehawk UDP used for much performs his magic, which works a little differently from the TCP world we Citri-Xens (yes, I just made that word up) are used.
Thought I would some of the quick and dirty tips and tricks collecting in the area learned to help Framehawk accelerate proof-of-concept testing. I will update keep this site as we learn more, but feel free to add your own tips in the comments to add (that's what community is for!)
Standard Disclaimer before we continue: Citrix does not support or guarantee for the use of tools mentioned in this article. These steps need not be performed in the production environment, unless instructed by Citrix support to do this.
1. Check on the endpoint, the Framehawk used
Typically, the protocol for the end user is invisible because all they care about law user experience is. The DisplayStateGUI.exe can for administrators in early demonstrations to ensure that they have the correct settings to be useful. In its first release, kick Framehawk is only when certain conditions are met, as described in the Administrator's Guide. Citrix Engineering developed with this small program for their internal use, which exposes the log information at the end point. It runs a banner on Windows endpoint contains the state of the display channel, either Thin Wire or Framehawk (as "LFP" shown).
The more official way to do this to extract information using session details in Director, where a new metric ( "Graphics - Framehawk") has added the HDX Statistics:
So, here is where you download you can set the tool to use is available, without any guarantee or support, as it is, your non-production evaluation help: DisplayStateGUI.exe
2. Check Framehawk functionality on the VDA
another quick tip to execute a command to validate that were applied to enable the settings Framehawk on the virtual machine (where VDA is installed). Looking for these two pieces of information in the result:
- Component_Provider = VD3D
- IsActive = Active
Use the following command line entries (CLI) on the VDA to verify that the channel is active Framehawk
- a prompt start (as an administrator) on the VDA.
- Enter wmic to enter the command line, and press
- Enter / namespace: .. \ root Citrix HDX and press Enter
- Enter path obtained citrix_virtualchannel_framehawk_enum / VALUE and press Enter
- ensure that Framehawk specific data (see above) is returned.
3. IPerf With Framehawk ports available through firewalls
to check Another note: iPerf is an open-source tool, freely available on the Internet. For more information about IPerf (including binaries and documentation) can be found here. Citrix does not support or guarantee for the use of this tool in a production environment.
IPerf is often used by network administrators to check network connectivity and performance under load. In this case, it makes sense, available to the defined UDP ports to confirm the connectivity between Citrix clients and servers to, especially in the presence of firewalls. Framehawk uses ports 3224-3324 by default (this can be changed in the policy). For remote access with NetScaler to enable its port UDP 443 needs open to any external firewall secure transport of datagrams. IPerf is run on two machines, in each case at the two ends of a network. simulate For the purposes of Framehawk UDP traffic, we recommend that are IPerf server mode to VDA and UDP traffic on the remote client running (with Citrix Receiver) outside the firewall network IPerf in client mode set . If the connection fails, it's time to pursue with the network and security teams to open ports on the firewall help check
IPerf use to Framehawk port availability .:
1. Download and install IPerf on the two test machines
2. Run IPerf in server mode on the VDA (referred to as "listening" mode):
. C: > iperf -s - p (PORT)
3. Run IPerf in client mode on the computer running Citrix Receiver is installed (hereinafter referred to as "Owner" mode) , with -u switch for UDP
C: -b > iperf -c (IPAddress) -p (PORT) -u (SIZE) m -l (MTU) -t (SECONDS)
the following example shows the output in the UDP port available:
c: Temp iperf-2.0.5-3- win32> iperf -c 54,204,250,164 -p 3222 -u - b 6m -l 1440 -t 10
--------------------
client connect 54,204,250,164, UDP port 3222
send 1440 bytes datagrams
UDP buffer size: 63.0 Kbytes (default)
- ----------------- -
[ 3] local 53235 192.168.1.101 port connected to 54,204,250,164 Port 3222
[ ID] Interval transmission bandwidth
[ 3] 0.0-10.0 sec 7.15 MBytes 6.00 Mbits / sec
[ 3] Sent 5210 datagrams
[ 3] Server Report:
[ 3] 0.0-10.0 sec 7.15 MBytes 5.99 Mbits / sec 2,689 ms 0/5209 (0%)
[ 3] 0.0 -10.0 sec 1 datagrams out-of-order received
the following sample output shows where UDP port has been blocked by the firewall:
c: Temp iperf 2.0 .5-3-win32> iperf -c 54,204,250,164 -p 3222 -u -b 6m -l 1440 -t 10
----- ------------ ---
client 54,204,250,164 port UDP port 3222
send 1440 bytes datagrams
UDP buffer size: 63.0 Kbytes (default)
--------------------
[1945026connected] local with 54.204 58947 192.168.1.101 Port .250.164 Port 3222
[ ID] Interval transmission bandwidth
[ 3] 0.0-10.0 sec 7.15 MBytes 6.00 Mbits / sec
[ 3] Sent 5210 datagrams
[ 3]. ATTENTION: not after 10 attempts ack the last datagram received
Other considerations for a successful demos and evaluation
avoid these common missteps your Framehawk evaluation in a making laboratory environment successfully. In a true WAN environment, you would not run into these situations in most cases. They are relevant for simulated WAN (with some kind of WAN emulator to produce the loss and latency)
Consider the following best practices .:
- Set the bandwidth and latency on the network emulator before to connect.
- Disconnect and close the session every time change the bandwidth, packet loss or latency, to allow new calibration, by the Protocol during handshake.
- do not limit the bandwidth on the WAN Emulator. Emulators rarely replicate the opportunity for instantaneous peaks that are allowed in real WAN. Uncapped bandwidth is to demonstrate a more realistic user experience, and the average bandwidth will automatically limit.
- on iOS, switch automatically rotate and adjust automatically. Use in landscape mode for best experience
Note . The Framehawk virtual channel at the time will not be recalibrated in session if latency or bandwidth can be observed changes
Share your experiences
We would like you to listen to the innovative application- ~~ POS = TRUNC, which are now possible thanks Framehawk. This is a first version of the new protocol HDX and evolve is based significantly on community and customer feedback. Keep sharing your experiences, tip and tricks, and help questions on the newsgroup to others with the collective wisdom.
0 Komentar