One of the interesting and I think that fundamental changes in WAN optimization, was the addition of a rich QoS Branch Repeater Version 6. several years ago, Citrix has purchased a company called deterministic Networks, which was a wedge that examined different applications and rank them according to the payload, not just TCP port / UDP, to a number of different VPN providers. Citrix has taken this technology and added to Branch Repeater to automatically classify and association to be smarter about how you managed that traffic on the basis of no traffic user.
This is what we called "user-centric, not focused on the network" which in itself is a big step in the evolution of the field of WAN optimization, but Citrix also changed their QoS to a Fair Queuing on personalized basis, allowing Citrix to associate a weight to an application, location or URL (via the application within classifier BR through inspection packets), this feature is a big step forward especially when taken into CIA multi-steam and experience of the end user.
now, most users Branch Repeater and new QoS features in version 6, would generally affect the quality of service on the repeater and align with existing QoS on their router and according to the amount of the CIA in this site they involve more emphasis on the repeater on the router.
it is interesting that I have a client (0% of all their traffic is ICA), which removes the QoS (Weighted Fair Queuing) on their routers, so all their routers! They are using the QoS parameters on the Branch Repeater
Their reasoning was based on a couple of " fundamental truths " of the suppliers
- Router
- . QoS was quick and intelligent, even with ICA and ICA Multi Stream (MSI)
- The configuration of QoS providers has been able to meet the different and changing traffic values
- the cost of the quality of service was a benefit to the business, mitigate delays and help with the user experience
Almost by mistake the customer had to replace a router and discovered that there was no QoS allocated to their router, ICA traffic was ONLY managed through the repeater and users saw a better experience then before when everything was status quo.
client did some research, they talked to me and I asked to see their repeater configuration, meanwhile, one of the engineers on the customer site decided to get their suppliers to remove QoS since another site and waited for a few days (this site was to have a large number of lost packets when supported and the provider wanted to increase the speed of connection). Remarkably overall use and user experience went!
Now, to be fair this client understands their WAN environment extremely well, they also monitor and do performance testing (test iperf via Repeater), on all of the links and I wouldn 't recommend short and do it without the preparation work.
However, the result of this is a better performance (Repeater understand ICA better than any router), under general operating expenses, (management of QoS settings on their routers by their supplier) and cost less per month on all their links, (built in cost QoS)
something to think about is not it?
Courtesy of Matt Moore, Senior Manager WAN Optimization, A / NZ
0 Komentar