Configuring a Redundant Pair of VMA SAN Gateways - Process Guide

21
Next, set the gateway cluster interface to be the VLAN created above:
# cluster interface vlan14
# write memory
Refer to the ‘VLAN Commands’ section of the ‘HP VMA-series SAN Gateway Installation and User
Guide’ for additional details and examples.
*hp-gateway1 [hp-redundant1: master] (config) # cluster interface vlan14
*hp-gateway1 [hp-redundant1: *unknown*] (config) # show network
Networking configuration:
Bonded interface eth0:
Enabled: yes
Interfaces:
eth1
eth2
Jumbo frames:
Enabled: no
Interfaces:
eth0 (mtu: 1500)
eth1 (mtu: 1500)
eth2 (mtu: 1500)
eth3 (mtu: 1500)
eth4 (mtu: 1500)
eth5 (mtu: 1500)
eth6 (mtu: 1500)
eth7 (mtu: 1500)
eth8 (mtu: 1500)
Global default-gateway:
Enabled: yes
Address: 10.61.184.1
Global mtu:
Enabled: yes
Global VLANs:
Enabled: yes
Interfaces:
vlan14 (id: 14, if: eth0)
*hp-gateway1 [hp-redundant1: *unknown*] (config) # write memory
Configure Management VIP on Primary Gateway
Configure the Virtual IP (VIP) which will be used for all future gateway management operations of the
gateway pair. It is important that all gateway management operations be performed on the current
‘master’ gateway of the gateway pair. The management VIP is a virtual IP that will always be hosted
on the active ‘master’ gateway of the redundant pair so that any gateway operations and
management changes are saved in the active configuration database on the active ‘master gateway’.
# cluster master address vip <IP address> /<network prefix>
# write memory
hp-gateway1 [hp-redundant1: master] (config) # cluster master address vip
10.61.184.240 /24
From this point forward, use the Management VIP for any gateway operations and management
changes. You should only use the individual IP address assigned to each gateway for individual
gateway debugging or maintenance, such as shutting down a specific gateway.