We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer

Barracuda Load Balancer Release Notes 4.2.2.x

  • Last updated on

Before installing any firmware version, be sure to take a backup of your configuration and read all release notes that apply to versions more recent than the one currently running on your system.

Do not manually reboot your system at any time during an upgrade, unless otherwise instructed by Barracuda Networks Technical Support. The update process typically takes a few minutes to complete after the update is applied. If the process takes longer, please contact Technical Support for further assistance.

Reverting to an Earlier Firmware Version

When reverting to an earlier firmware version:

  • If you have enabled Network Port Configuration support on your Barracuda Load Balancer (versions 4.2 and later), before reverting to a version that does not support Network Port Configuration, you must:
    • Disable Network Port Configuration.
  • If you have enabled IPv6 support on your Barracuda Load Balancer (versions 4.1 and later), before reverting to a version that does not support IPv6 addresses, you must:
    • Delete all IPv6 Services, IPv6 virtual interfaces, IPv6 static routes, and all IPv6 addresses on the BASIC > IP Configuration page.
    • Turn off the Enable IPv6 option on the BASIC > IP Configuration page.

Firmware Version 4.2.2

New Features
  • Created or updated the following guides to assist in deployment with the Barracuda Load Balancer. These guides are found in the Barracuda Networks TechLibrary:
  • Service Monitor HTTP tests now include the ability to perform a POST request. [BNLB-4225]
  • Added option to select an interface when performing a Ping test. [BNLB-4098]
  • Generate SNMP trap if available memory is less than 25%. [BNLB-4070]
  • Replaced Protocol column in the Services table on the BASIC > Server Health page with Service Type. [BNLB-4009]
  • Added host header to Microsoft SharePoint authentication check. [BNLB-3960]
  • Can manually enable or disable standard ciphers. [BNLB-3920]
  • Added a “Weighted Least Connections” load-balancing policy to client impersonation-enabled services. [BNLB-3846]
  • Layer 7 FTP Proxy Services support using MLSD and MLST. [BNLB-3016] [BNLB-4248]
  • Increased flexibility of content rules with regards to adding and monitoring servers. [BNLB-2875] [BNLB-4125]
Version 4.2.2.009:
  • Fixed : OpenSSL vulnerability [ CVE-2014-0160 ] for TLS/DTLS Heartbleed attack has been addressed. [ BNLB-4774 ]
Version 4.2.2.008:
  • Fixed : High severity vulnerability: arbitrary command execution, remotely exploitable, unauthenticated. [BNSEC-2001 / BNLB-4489]
  • Fixed : Added ability to configure TLS version for SSL communication with real servers. [BNLB-4637]
  • Fixed : In rare cases, usually involving authentication with a 401 status code, requests were dropped if the server responded prematurely. These are now forwarded correctly. [BNLB-3959]
  • Fixed : Primary unit sends a higher priority VRRP advertisement when recovering from a failed state in manual failback mode. [BNLB-4493]
  • Fixed : URL encoding is performed for the ampersand (&) character in URL Translations > Redirect Rules. [BNLB-4522]
  • Fixed : When clustered, the two systems assume the correct active-passive state combination. [BNLB-4520]
  • Fixed : The "Critical Events" number is displayed correctly on the BASIC > Status page. [BNLB-4505]
  • Fixed : Alert messages are generated only for the Services which have "Enable Notification" set to Yes. [BNLB-4373]
  • Fixed : Restored ability to create a bond interface after updating to firmware version 4.2.2.007. [BNLB-4531]
  • Fixed : Fixed issue where web interface was listening on all available interface IP addresses, causing SSL enabled services to fail. [BNLB-4621]
Version 4.2.2.007:
  • Behavior change: If you are using an SNMP monitor, make sure that its IP address is in the Allowed SNMP IP/Range table on the ADVANCED > SNMP Configuration page. If no IP addresses are entered in that field, SNMP access is not allowed. [BNLB-4551]
  • Fixed : Issues with monitor groups for monitoring servers associated with content rules. [ BNLB-4476 ] [ BNLB-4478 ] [ BNLB-4480 ]
  • Fixed : Client session for RDP traffic are not persisted to the correct server. [ BNLB-4387 ]
Version 4.2.2.006:
  • Fixed : Fixed memory leak in Exchange 2010 deployments. [BNLB-4337]
  • Fixed : Core system modules have been upgraded to resolve out of memory errors. [ BNLB-4327 ]
  • Fixed : Improved GUI memory management and performance when system memory is low. [ BNLB-4123 ]
  • Fixed : Show LAN interface configuration as unavailable in a virtual machine if the second adapter is not found. [BNLB-4274 ]
  • Fixed : Cookie persistence is maintained during HA failover. [BNLB-4100]
  • Fixed : Added multiplier tag option for Adaptive Scheduling for SNMP CPU (to account for multiple cores and differing behavior between Linux and Windows). [BNLB-4120]
  • Fixed : Outlook client failover from one CAS to another occurs quickly. [BNLB-4133]
  • Fixed : Outlook client is able to download a large mailbox (>1.5GB) when using RPC over HTTP. [BNLB-4231]
  • Fixed : All configured SNAT rules are maintained even after failover and fallback. [BNLB-4232]
  • Fixed : Custom cipher is not used if default cipher is selected. [BNLB-4258]
  • Fixed : Load Balancing with weighted least connections and TCP Proxy works as expected. [BNLB-4310]
  • Fixed : Last Resort Server setting is maintained after failover and failback. [BNLB-4348]
  • Fixed : Data part of Active FTP connection uses VIP address rather than WAN IP address of the Load Balancer. The WAN IP address was used if IP Masquerading was turned on. [BNLB-2645]
  • Fixed : When using Internet Explorer 9, Server Health page shows column checkboxes correctly. [BNLB-3565]
  • Fixed : Disabled LAN management access option in UI while in High Availability mode. [BNLB-3634]
  • Fixed : Redirect Rule element type pathinfo works as expected. [BNLB-4010]
  • Fixed : Common name field in BASIC > Certificates page displays subject common name instead of issuer common name. [BNLB-4015]
  • Fixed : CPU temperature displays correctly on the BASIC > Status page. [BNLB-4097]
  • Fixed : BASIC > Server Health page shows correct value for traffic. [BNLB-4159]
  • Fixed : If server is down/disabled/in maintenance mode, then the Adaptive Scheduling SNMP CPU test for that server returns value of 0. [BNLB-4182]
  • Fixed : If Direct Server Return is enabled, SIP health check works correctly. [BNLB-4195]
  • Fixed : SSH to servers works with Layer 4 TCP ALL port service. [BNLB-4201]
  • Fixed : Added more log file maintenance routines to conserve disk space. [BNLB-4209], [BNLB-4221]
  • Fixed : For GSLB, test for the first site shows accurate results in user interface. [BNLB-4251]
  • Fixed : Only unique entries for HTTP content type in compression rules are allowed. [BNLB-4265]
  • Fixed : UDP Proxy Service for port 123 (NTP) works when first created. [BNLB-4277]
  • Fixed : When server is disabled and then re-enabled, the Traffic to Servers graph for that server shows accurate data instead of spikes. [BNLB-4333]
  • Fixed : Service/server health probe failure reason appears in BASIC > Event Log, even if name of Service/server includes a '-' or '_'. [BNLB-4334]
  • Fixed : Status and link speed display correctly for a bonded interface.[BNLB-3785]
  • Fixed : Automated SMB backups work. [BNLB-3893]
  • Fixed : Server restore alert email is sent when required by a group monitor test. [BNLB-4316]
Last updated on