KEMP LoadMaster v7.0-4 firmware is now available with Edge Security Pack

Kemp announced  Firmware release LoadMaster 7.0-4. Here are the details below. Watch out for more announcements on some of the features in the coming weeks.

New Features and Feature Enhancements:
  • Edge Security Pack – A range of new security features has been added to the LoadMaster.
  • Sub-VS Support – The LoadMaster now supports the creation and management of sub-VSs.
  • Graphical Metrics – There is a new dashboard home screen with the capability to display graphical performance information.
  • New License format – A new license format has been introduced
  • Oracle VirtualBox VLM – A new VLM package, to support VLM installation within an Oracle VirtualBox environment is available
  • MIBS files have been updated
  • SID and revision information included in IPS logging
  • VLAN Separation per Interface
  • Support for larger TCP window sizes
  • ‘Kill switch’ is now supported on all LoadMaster versions
  • LM-R320 has its serial number visible on the WUI
  • The Netconsole Host interface is configurable via the WUI
Issues Resolved:
    • Issue with SMTP STARTTLS when a client sends an EHLO is resolved
    • Issue with ACL whitelist allowing other IPs is resolved
    • Issue with switching VS types under load is resolved
    • Some reboot issues have been resolved
    • An issue with caching on Firefox has been resolved
    • The “-“ character is now allowed in the DNS Search Domain field
    • Issues with the MIBS have been resolved
    • A circular routing problem has been resolved
    • SNMP trap Source IP has been changed to pre 5.1-48 behaviour
    • SSL renegotiation can be toggled on/off
    • SSLv2 is no longer used for LoadMaster initiated SSL connections
    • An issue with Not Available Redirection XSS has been resolved
    • The Default IP is now displayed on the WUI when DHCP fails
    • An issue with VS Specific insert X-Clientside header being overwritten by system default has been resolved
    • The “-“ character is now allowed in the User Login field
    • An issue with the Fail on Match functionality has been resolved
    • An issue with Maximum Cache Size has been resolved
    Known Issues:
      • Quick setup Help appears automatically if no IP address is configured on the LM if a VLAN is configured on eth0 and no IP address is assigned to the underlying interface (eth0)
      LoadMaster version v7.0-4 supports the following hardware:
      • LM-2000
      • LM-2200
      • LM-2500
      • LM-2600
      • LM-3500
      • LM-3600
      • LM-5300
      • LM-5500
      • LM-Exchange
      • LM-R320
      • VLM-100
      • VLM-1000
      • VLM-Exchange
      NOTE – ESP is supported on select LoadMaster models and new VLM installations.

      Learn more about LoadMaster 7.0:


      Full Release Notes

      Full Documentation

      Convert VHD to VHDX

      VHDX is the new and default format of virtual hard disk (VDH) that is provided by Windows 8 Client Hyper-V and Windows Server 2012 Hyper-V. There are many reasons to favor VHDX files over VHD files, including:

      • scalability to 64 TB instead of 2040GB
      • better performance by offering 4 K sector matching
      • protection against data corruption during power outages
      Using PowerShell to Convert to VHDX

      You can dispense with the time-consuming wizard by using PowerShell. This will be extremely useful if you need to use a script to automate lots of VHD conversions across many virtual machines. The following snippet will convert a VHD to a VHDX:

      Convert-VHD –Path d:\VM01\Disk0.vhd –DestinationPath d:\VM01\Disk0.vhdx

      When you create a new VHDX file (not converted) it has a physical sector size of 4 K. A converted VHDX file has a physical sector size of 512 Bytes. You can change the physical sector size of a converted VHDX by running this piece of PowerShell before you power up the virtual machine:

      set-vhd d:\VM01\Disk0.vhdx -PhysicalSectorSizeBytes 4096

      Now you have a virtual machine that is using the best kind of virtual machine storage, the VHDX format virtual hard disk

      The above instructions do not finish the job. The next essential set of steps are:

      1. Open the settings of the virtual machine.
      2. Replace the VHD with the VHDX.
      3. Start and test the virtual machine.
      4. Delete the VHD file.