Posted at 05:16 PM | Permalink | Comments (0)
Riverbed Stingray Traffic Manager 9.1 released
Today we are releasing Stingray Traffic Manager 9.1, which is now available via customers’ download pages and for evaluation. Although this is a minor revision of the Stingray product family, it does contain a wide range of improvements and bug fixes. Customers are recommended to upgrade to this version to take advantage of the changes. Enhancements in this release include:
RESTful API
This release introduces a new RESTful API, to give developers and operations a web services based API for managing their application delivery infrastructure. The REST API complements the existing methods of configuration management, such as the Admin GUI, SOAP API and zconf. The REST API is available to all Stingray configurations (Stingray Traffic Manager 1000/2000/4000); users with legacy Zeus licenses may migrate to Stingray to obtain this new functionality.
Scalability
This release also includes scalability updates to improve failover and startup times when running in very large configurations, such as thousands of virtual servers and/or IP addresses.
Extended Platform Support:
This release has been validated and is fully supported on VMware vSphere 5.1. For the complete range of supported platforms, see the release notes.
Contacting support
Please contact support on support@riverbed.com.
Upgrading
Customers with valid maintenance and support contracts will be able to download this release from their customer page. See the relevant instructions for upgrading your Riverbed Stingray or Zeus installation.
The documentation and release notes for Stingray Traffic Manager 9.1 may be found here.
Regards,
The Stingray Product Team
Riverbed Technology
Posted at 08:00 PM | Permalink | Comments (0)
Today we are releasing Stingray Traffic Manager v9.0r3, which is now available via customers’ download pages and for evaluation. Although this is is a minor revision of the Stingray product family, it does contain a wide range of improvements and bug fixes. Customers are recommended to upgrade to this version to take advantage of the changes. Enhancements in this release include:
Stingray Aptimizer:
This release improves the display of information on Aptimizer status and configuration, particularly in clustered and MSM installations, and corrects a number of cases where resources were incorrectly handled or displayed during optimization of some sections of HTML, CSS, images and JavaScript.
Note that this release does NOT affect users of Stingray Aptimizer for SharePoint.
Global Load Balancing:
This release includes a number of improvements to the way in which Stingray Traffic Manager handles traffic during reconfiguration of GLB services and includes an updated GeoIP database.
TrafficScript:
This release improves support for IPv6 back-end addresses in TrafficScript, and improves the way in which Aptimizer profiles are managed through TrafficScript. There are also improvements in the way that pathnames with special characters are encoded.
Security and Error Handling:
This release improves performance and usability with long Certificate Revocation Lists, and has improved error handling, logging of alerts and warnings of a number of events.
Contacting support
Please contact support on support@riverbed.com.
Upgrading
Customers with valid maintenance and support contracts will be able to download this release from their customer page. See the relevant instructions for upgrading your Riverbed Stingray or Zeus installation.
The documentation and release notes for Stingray Traffic Manager 9.0 may be found here.
Regards,
The Stingray Product Team
Riverbed Technology
Posted at 06:48 AM | Permalink | Comments (0)
Stingray can load balance servers in a few different ways. Looking at a Pool's Load Balancing configuration page shows the different options:
They're all pretty straightforward except for Perceptive; how does that one work? Perceptive can be thought of as Least Connections skewed to favor the servers with the Fastest Response Time. Perceptive factors in both connection counts and response times into the load balancing decision to ensure that traffic is distributed evenly amongst the servers in a farm. It is best understood in the context of a few examples:
Heterogeneous Server Farm
A great scenario in which to use Perceptive is when your server farm is heterogeneous, where some servers are more powerful than others. The challenge is to ensure that the more powerful servers get a greater share of the traffic, but that the weaker servers are not starved.
Perceptive will begin by distributing traffic based on connection counts, like Least Connections. This ensures that the weaker servers are getting traffic and not sitting idle. As traffic increases the powerful servers will naturally be able to handle it better, leading to a disparity in response times. This will trigger Perceptive to begin favoring those more powerful servers, as they are responding quicker, by giving them a greater share of the traffic.
Heterogeneous workloads
Another great scenario in which to use Perceptive is when your workload is heteregeneous, where some requests generate a lot more load on your servers than others. As in the Heterogeneous Server Farm case, Perceptive will begin by distributing traffic like Least Connections. When the workload becomes more heterogeneous, some servers will get bogged down with the more CPU intensive requests and begin to respond slower. This will trigger Perceptive to send traffic away from those servers, to the other servers that are not bogged down and responding quicker.
Summary
The Perceptive load balancing algorithm factors in both connection counts along with response times into a two step load balancing decision. When there is little disparity in response times, traffic will be distributed like Least Connections. When there is a larger disparity in response times, Perceptive will factor this in and favor the servers that are responding quicker, like Fastest Response Time. Perceptive is great for handling heterogeneity in both the server farm and the workload, ensuring effecient load balancing across your server farm in either case.
Posted at 02:59 AM | Permalink | Comments (0)
This release has improved Aptimizer performance and stability; users of Stingray Aptimizer are strongly encouraged to upgrade.
Note that this release does NOT affect users of Stingray Aptimizer for SharePoint.
This release fixes two security vulnerabilities in the kernel (CVE-2012-2744, and CVE-2012-1601).
Please contact support on support@riverbed.com.
Customers with valid maintenance and support contracts will be able to download this release from their customer page. See the relevant instructions for upgrading your Riverbed Stingray or Zeus installation.
The documentation and release notes for Stingray Traffic Manager 9.0 may be found here.
Regards,
The Stingray Product Team
Riverbed Technology
This earlier article went into a lot of depth on how you can use TrafficScript to automatically insert Google Analytics code into your webpages. I've updated the code in that article and posted it along with instructions here.
Posted at 03:51 PM | Permalink | Comments (0)
A great usage of TrafficScipt is for managing and inserting widgets on to your site. With TrafficScript you can easily insert a Twitter Profile Widget to your site.
With a Twitter Profile Widget on your site you can easily communicate what's new, on sale, or anything else you like to your users. With TrafficScript you have ultimate control and can easily move, modify, or even disable the widget with the click of a button all within the Stingray web interface.
The TrafficScript code along with instructions is available here. Give it a try.
Posted at 01:43 PM | Permalink | Comments (0)
Using Stingray Traffic Manager to load balance a pool of LDAP servers is a fairly simple process. Here are the steps:
At this point a virtual server and pool will be created. Before it is usable a few additional changes need to be made:
The final step is to install the LDAP Health Monitor. The LDAP Health Monitor is an External Program Monitor that binds to the LDAP server, submits an LDAP query, and checks for a response. Instructions to install the monitor are in the linked page.
That completes the configuration of the Stingray Traffic Manager to work with LDAP.
Posted at 02:15 PM in Configuration | Permalink | Comments (0)
We are pleased to announce the release of Stingray Traffic Manager 9.0. This new release can be extended with add-ons for both web content optimisation and application firewall, to provide a comprehensive set of ADC capabilities.
Web Content Optimization (WCO):
Stingray Traffic Manager 9.0 can be extended with the WCO add-on, based on Riverbed's Stingray Aptimizer software. This can dramatically accelerate web-based applications and websites, by automatically grouping requests for fewer long distance round trips, compressing images to reduce bandwidth required, increasing caching for faster repeat visits, and prioritising layout to give the best possible response time on any browser.
Developer Edition
The new Stingray Developer Edition includes all the capabilities of the Stingray product family, including web content optimization and application firewall. The Stingray Developer Edition can be downloaded at no cost, and runs without the need for an additional development license.
Contacting support
Please contact support on support@riverbed.com.
Upgrading
Customers with valid maintenance and support contracts will be able to download this release from their customer page. See the relevant instructions for upgrading your Riverbed Stingray or Zeus installation.
The documentation and release notes for Stingray Traffic Manager 9.0 may be found here.
Kind regards,
The Stingray Product Team
Riverbed Technology
We are pleased to announce the release of Stingray Traffic Manager v8.1r1, which is now available via customers’ download pages and for evaluation. All customers are recommended to upgrade to this version to take advantage of the security and availability enhancements in this release. Enhancements in 8.1r1 include:
Security and Availability:
This 8.1r1 release is fully up-to-date with currently available security enhancements for Stingray, and upgrade is recommended
Improved cluster monitoring and fault recovery allows additional failure modes to be detected and managed automatically
Support for an additional switch to control endpoint persistence of UDP traffic, which gives better performance and availability for DNS
Virtual Appliance:
The Stingray Traffic Manager virtual appliance now has an upgraded 2.6.24-31.100 kernel, which includes recommended enhancements for security and availability
Usability:
This release includes improvements to the user interface to improve usability particularly for complex configurations, which resolves problems such as an unresponsive license management page
Developer License:
Developer licenses are available at no cost, and provide access to a full-featured Stingray Traffic Manager, with certain limitations on performance and use, by completing the online developer license form.
For a complete list of all changes, please read the release notes on the Stingray documentation pages.
Contacting support
Please contact support on support@riverbed.com.
Upgrading
Customers with valid maintenance and support contracts will be able to download this release from their customer page. See the relevant instructions for upgrading your Riverbed Stingray or Zeus installation.
The documentation for Stingray Traffic Manager 8.1r1 is unchanged from 8.1, and may be found here.
Kind regards,
Riverbed Technology
Posted at 05:29 PM in Installation | Permalink | Comments (0)
Technorati Tags: stingray traffic manager, zeus software, zeus traffic manager