Configuring a Redundant Pair of VMA SAN Gateways - Process Guide

Save the ‘secondary’ gateway configuration by exiting the configuration wizard (configuration jump-

start).

Update the Secondary Gateway Software

Update the VMA SAN Gateway software OE to be the same version as running on the ‘primary’

gateway. For initial release of redundant gateway pairs this will be VMA SAN Gateway software

OE version G5.1.0. Please refer to the HP VMA SAN Gateway Software Update Guide (AM456-

9022A) document available at www.hp.com/go/vma-docs

for step-by-step details of the update

process for the VMA SAN Gateway, including how to obtain the VMA SAN Gateway software OE

update.

You can determine the VMA SAN Gateway Software OE version that is running on each gateway by

issuing the ‘show version’ command.

This step of individually updating the gateway software on the ‘secondary’ VMA SAN Gateway for

pairing of the gateways will only need to be done as part of this initial gateway pairing process.

After the gateways are paired, update of the VMA SAN Gateway software OE can be performed

from the web interface and take effect on both paired gateways as one step.

Configure Ethernet Port Bonding on Secondary Gateway

The network bonding and configuration of the secondary gateway must now be established. The

physical Ethernet link connections for the secondary gateway to the network switch were made in a

prior step.

Perform the same bonding of Ethernet ports eth1 and eth2 to create the bonded port eth0 on the

secondary gateway as was done previously on the primary gateway. To do this enter the following

command on the secondary gateway using the CLI:

# network bond eth0 mode <link-agg> interface eth1 interface eth2

# write memory

Use the same link aggregation bonding mode, <link-agg>, as used for the primary gateway. In this

pairing process example, the ‘balance-rr’ link aggregation mode is being used.

hp-gateway2 [memgate-cluster: master] > en

hp-gateway2 [memgate-cluster: master] # conf t

hp-gateway2 [memgate-cluster: master] (config) # network bond eth0 mode balance-

rr interface eth1 interface eth2

Are you sure you wish to change networking modes? All cached content will be

lost, the cache modules will leave the cluster to set up networking, and remote

cli connections may be terminated. Continue? [no] yes

*hp-gateway2 [memgate-cluster: unknown] (config) # write memory

hp-gateway2 [memgate-cluster: unknown] (config) #

Configure Inter-Gateway VLAN on Secondary Gateway

Next, create the VLAN on the secondary gateway which will be used for inter-gateway

communication and heartbeat.