This task provides a list of the
support actions when configuring the FAStT disk controllers.
 | Attention: The SAN Volume Controller does not concurrently support I/O operations with the
download of ESM (Environmental Services Monitor) firmware. You must quiesce
all I/O operations from the hosts that are using storage provided by the FAStT
controllers you wish to update before installing new ESM firmware. |
The FAStT storage server has many options and actions. The
following list the supported actions and its impact on the SAN Volume Controller and its configuration.
-
host type:
- You must set either the default host type of your FAStT or the host type
of the chosen partition to:
IBM TS SAN VCE
You can set the host type
in 2 ways:
- Click Storage Subsystem -> Change -> Default
Host Type, or
- For each host port you can specify the host type of that port or modify
existing ports.
-
WWNN:
- Set the subsystem so that both controllers have the same WWNN. Scripts
are available from the FAStT support Web site to change the set up of the
FAStT if required.
www.storage.ibm.com
-
auto volume transfer (AVT):
- Make sure the auto volume transfer is enabled. The host type selection
should have enabled this function already.
- View the storage subsystem profile data to confirm that you have the AVT
function enabled. This storage profile is presented as a text view in a separate
window.
- Scripts are available from the FAStT Web site to enable AVT if required.
www.storage.ibm.com
- limitations:
- Only one FAStT storage partition can be created that contains any of the ports of any of the nodes
in a single SAN Volume Controller cluster.
- You must not map more than one partition to any of the ports on any of the nodes in the same SAN Volume Controller cluster.
Otherwise, unexpected behavior might result. For example, there will not be
any warning messages, however, there will be errors logged in the SAN Volume Controller error
log and access to storage may be lost.
-
access LUN:
- The access LUN, also known as the Universal Transport Mechanism (UTM)
LUN, might not be in a partition that contains the SAN Volume Controller ports. It is not
required by the SAN Volume Controller. The UTM LUN is a special LUN that allows the SAN Volume Controller to
be configured through suitable software over the Fibre channel connection.
However, the SAN Volume Controller does not require the UTM LUN, therefore does not generate
errors either way.
- The FAStT must not have the Access (UTM) LUN presented
as Logical Unit Number 0 (zero).
-
logical unit:
- The SAN Volume Controller attempts to follow the FAStT specified preferred ownership.
You can specify which controller (A or B) is used to do I/O operations to
a given Logical Unit. If the SAN Volume Controller can see the ports of the preferred controller
and no error conditions exist, then it will access that Logical Unit through
one of the ports on that controller.
- Under error conditions, the ownership is ignored. Meaning, the SAN Volume Controller has
found a given path through the fabric to be errant, or there is no connection
to a given port.
- Copy services (FlashCopy and Remote Copy):
- FAStT copy services must not be used when the SAN Volume Controller is
attached to the FAStT. Partitioning might allow copy services to be used on
other host platforms.
Related topics