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

40 HP VMA SAN Gateway Installation and Configuration Guide AM456-9025A
Configuration File Management
Changes made to the configuration of a HP VMA SAN Gateway redundant pair take effect
immediately. Those changes can be lost if they are not saved to a configuration file, however. The
HP VMA SAN Gateway redundant pair stores one or more configuration files on persistent storage,
one of which is designated as the active configuration file.
The active configuration file is where configuration changes are stored when you save a
configuration. Whenever the gateway reboots, it loads the configuration settings from the file
designated as active. The gateway backs up the active configuration file automatically.
For more information on managing configuration files, see the
HP VMA SAN Gateway User’s Guide.
User Roles
User management privileges are set by assigning one of the following roles to a user account:
• admin: The administrator role has full privileges to view anything, take any action, or change
any configuration. This role can access every page in the VMA Gateway Web interface.
• monitor: The monitor role can read all data and perform some actions, such as rebooting the
system and configuring various system parameters, but cannot change the configuration of the
VMA-series SAN Gateway. This role can view some of the pages in the Web interface.
Caution: Initially these accounts have no password. Setting a password for the admin role is highly
recommended.
The CLI command modes
configure, enable, and standard correspond to the admin and
monitor roles. For more information on managing users using the CLI and VMA Gateway Web
interfaces, see the HP VMA SAN Gateway User’s Guide.
Upgrading the Gateway Software
Part of managing a gateway is keeping the software version up to date. Upgrading the HP VMA
SAN Gateway software requires that you obtain the latest software release, run a command to
distribute and install the software on each HP VMA SAN Gateway, and then reboot the cluster.