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

VMA SAN Gateway G5.1.0 SNMP events are not integrated with HP

System Insight Manager (SIM)

Due to current compatibility issues with SNMP events from the VMA SAN Gateway G5.1.0, SNMP

integration and events are not supported with HP System Insight Manager (SIM) at this time.

VMA v-commands available with the Gateway CLI

A number of the VMA Array “v” commands are also available with the Gateway CLI:

• vspeedtest (performs a quick test of read speed with the array)

• vincident collects information on attached arrays

• vmesg lists the debug messages on the Gateway

• vvimms, varray, veeprom, vinfo provide configuration information on the array

• vstat displays array status

• vpartial shows partial/unaligned array I/O counters

• vcounts displays array I/O counts

• vzero resets the array I/O counters

Setting date and time

It is recommended to set the correct date and time on your VMA SAN Gateway and VMA-series

array when initially installed and configured. Setting the correct date and time will help with

correlation and analysis of host server, gateway and array events if a problem is reported.

CLI commands are case sensitive

All CLI commands are case sensitive and usually are all lower case. CLI commands are documented

in appendices of the user manuals.

Backing up VMA SAN Gateway configuration for recovery

For disaster recovery of the VMA SAN Gateway configuration file, you can create a copy of the

gateway configuration file and upload it to a production or maintenance server to be included in the

regular data backup of that server. When required to recover the gateway configuration file you can

restore it to the server and then from the gateway issue a ‘fetch’ to retrieve it back to the gateway.

First create a copy of the current active configuration on the VMA SAN Gateway to a configuration

file, using the configuration write command:

# configuration write to <file-name>

Next step is to copy the saved gateway configuration file to the production or maintenance server

using the configuration upload command so that it can be included in regularly scheduled

data backups:

# configuration upload <file-name> scp://<user-login>[:<password>]@<server IP>/<target-

directory>[/<file-name>]

When required to recover the gateway configuration file, you can retrieve the restored configuration

file from the production or maintenance server by issuing the configuration fetch command:

# configuration fetch scp://<user-login>[:<password>]@<server-IP>/<source-

directory>/<source-file-name> [<gateway-file-name>]