HP VMA SAN Gateway for VMA-series Memory Arrays Release Notes - May 2012 - Software OE version G5.1.0

4
Figure 1: VMA SAN Gateway – front view
VMA features not initially supported by HP
HP OEMs the VMA-series memory arrays (VMA) and vSHARE OE from Violin Memory. Not all
features and configurations possible with the VMA-series arrays and VMA SAN gateway have been
fully tested to the expected level from HP and are considered unsupported until a later time. While
the following features and configurations may be described in the manuals, they are not initially
supported by HP:
• iSCSI connectivity with the SAN Gateway is not supported at this time.
• HP is not supporting connectivity to all the host platforms and operating systems (OSes) that
may be mentioned in the manuals; only those listed in Table 2 below have been fully tested to
the level of HP quality and are considered supported.
• Only the VMA3205 (5TB) and VMA3210 (10TB) models are supported; other models with
other capacity and memory module capacities are not supported by HP at this time.
Web Release of VMA SAN Gateway software OE version
G5.1.0 and VMA Array firmware version A5.1.3
HP is releasing the VMA SAN Gateway software OE version G5.1.0 and VMA Array firmware
version A5.1.3 as a web release. This means that VMA SAN Gateways and VMA Arrays will not be
shipped with gateway software and array firmware versions needed to support the configurations and
features possible with this release. VMA SAN Gateway software OE version G5.1.0 is supported
only with VMA Array firmware version A5.1.3. Thus when intending to deploy VMA SAN Gateways
with G5.1.0 version of software OE, either as redundant pairs or standalone, you will need to
manually update the software OE on the VMA SAN Gateway to version G5.1.0 and update firmware
on the VMA Array to version A5.1.3.
Detailed documentation on how to:
• update the firmware on a VMA Array
• update the software OE on a VMA SAN Gateway
• configure a redundant VMA SAN Gateway pair
is available from our VMA documentation collection location as noted in the ‘Documentation location’
section below.