Brocade Virtual Traffic Manager 17.1 released

PaulWallace · ‎01-23-2017

This latest version of Brocade Virtual Traffic Manager includes enhanced flexibility for management, control and more deployment options. Highlights in this release include:

DHCP on Admin Interface - When a virtual appliance needs to be deployed with a separate management network, the admin network interfaces can now be configured via DHCP, instead of static IP address assignment.
Delayed Fail-Back - It is now possible to delay the automatic fail-back of a cluster node when recovering from a failure. Previously, fail-back had to be either immediate or manual. Now, automatic fail-back can be set to a variable delay, to provide more flexibility in recovery in production.

PROXY Protocol Support - The PROXY protocol can be used to share information about the original client-side connection. When Brocade vTM is installed behind an intermediate proxy server, the PROXY protocol can be used by the intermediate proxy: Traffic Manager makes the client-side connection information available through new TrafficScript functions.
Hypervisor Support - This release now supports more hypervisor versions, including VMware vSphere 6.5, and Microsoft Hyper-V on Windows Server 2016.

Version Numbering:

Note that from January 2017, we are changing the version number scheme across all software products, to the format "YY.n" - where "YY" represents the year, and "n" represents the sequence number during the year. This release of Traffic Manager is designated "17.1" - following directly from the previous T raffic Man ager release, which was designated "11.1"

For more information:

For more information, please refer to the release notes, available on the download site. A complete set of user documentation is also available on brocade.com/vadc-docs, including getting started guides, installation, configuration and API reference documentation.