HP VMA SAN Gateway Installation and Configuration Guide For release G5.5.1

AM456-9025A HP VMA SAN Gateway Installation and Configuration Guide 39
Management VLAN Configuration
The VMA-series SAN Gateway can use a separate network for low-latency, low-bandwidth
communication between HP VMA SAN Gateways in a cluster.
To separate redundant gateway network traffic from management traffic, you can configure a virtual
local area network (VLAN). Network switches must also be configured to provide a private VLAN
if it will be used for the cluster network traffic.
For best performance and minimal impact on the customer network, HP recommends configuring
a private network for use by the cluster through VLAN tagging.
When VLANs span multiple switches, VLAN Tagging is highly recommended. A VLAN creates
an independent logical network within a physical network. VLAN Tagging is the process of
inserting a VLAN ID into a packet header in order to identify which VLAN the packet belongs to.
Each network switch port connected to a HP VMA SAN Gateway should be configured to allow
VLAN-tagged traffic for the given management VLAN ID. This is a configurable option that you
can change to suit your network setup. For more information on VLAN commands, see the HP
VMA SAN Gateway User’s Guide.
Some switch vendors, including Cisco, do not allow untagged traffic over an LACP link. If you are
using this type of switch, you must provide the HP VMA SAN Gateway with the public-facing
VLAN (in addition to the cluster VLAN) and tag the ports appropriately.
Note: Multicast DNS (mDNS) is used for cluster communication, and so must be allowed on all
switches. Use the IP multicast group address (224.0.0.251).
Managing a Redundant Gateway Pair
Management of a redundant gateway pair includes monitoring the HP VMA SAN Gateway nodes,
stopping or rebooting nodes, and upgrading the software running on the nodes. For information on
how to manage gateway nodes, see the
HP VMA SAN Gateway User’s Guide.
For information on upgrading SAN Gateway nodes, see CHAPTER 5, “
Memory Gateway Software
Upgrades”
on page 75.
Caution: Be sure to check the current Release Notes for the latest recommendations before beginning a
gateway software upgrade.