The VASA credentials comprise a username and a password that is set separately from the
Spectrum Connect user accounts, and separately from the
storage system credentials.
From the Spectrum Connect UI you can set, change, or display these
VASA credentials at any time.
Note:
Only one set of a username and a password can be used for the VASA credentials, which applies to
all vCenter servers that require VASA functions and connect to Spectrum Connect.
Click VASA Provider settings on the Settings menu. The VASA Provider settings dialog box is displayed.Figure 1. VASA Provider settings dialog box
Enter the username and password that you want to set, confirm
the password and then click Apply.
Note: The VASA username must be different from any username stored in the Spectrum Connect user database. See Managing Spectrum Connect users.
In the Priority drop-down box, select a priority (0–255) of Spectrum
Connect as a storage provider in vCenter. In its turn, it defines priority of all storage systems
added to the current Spectrum Connect instance on the vCenter server.
Note: You can use the Priority setting for resolving an issue, when a Spectrum Connect instance defined for the same storage
system is active on one vCenter server and passive on another vCenter. This might occur, when two SC
instances with the same priority, managing the same storage system are registered as storage
providers on two different vCenters. A loss of connectivity between any of the Spectrum Connect instances and vCenter servers might result
in the following configuration:
Spectrum Connect A is an active storage provider on
vCenter 1.
Spectrum Connect B is an active storage provider on
vCenter 2.
This renders Spectrum Connect A to be the active
storage provider on vCenter 1 and passive on vCenter 2. In its turn, Spectrum Connect B is active provider on vCenter 2 and
passive on vCenter 1. To avoid this situation, use the Priority parameter to define the required Spectrum Connect instance to have a higher priority than
another one. This ensures that it remains active after a failover.