Technical data

If you have an NSPOF configuration, use device names for at
least two host bus adapters.
For example, to ensure that you have a connected boot path
in case of a failed host bus adapter or controller failover,
choose device names for multiple host bus adapters and
each controller port. If you use the reachability display for
member system 1’s boot disk as shown in Example 4-17,
choose all of the following device names when setting the
bootdef_dev console environment variable for the first
cluster member system:
dga101.1001.0.7.0
dga101.1002.0.7.0
dgb101.1001.0.8.0
dgb101.1002.0.8.0
If the bootdef_dev console environment variable ends up
with all boot paths in an unconnected state, you can use the
ffauto or ffnext console environment variables to force a
boot device from a not connected to a connected state.
The ffauto console environment variable is effective only
during autoboots (boots other than manual boots). Use the
set ffauto on console command to enable ffauto. (The
default for ffauto is off.) It is stored in nonvolatile memory
so it persists across system resets and power cycles.
During an autoboot, the console attempts to boot from
each connected device listed in the bootdef_dev console
environment variable. If ffauto is on, and if the end
of devices listed in bootdef_dev is reached without
successfully booting, the console starts again at the
beginning of the devices listed in the bootdef_def console
environment variable. This time, devices that are not
connected are changed to connected and an attempt is
made to boot from that device.
The ffnext console environment variable is a one-time
variable. It does not persist across a system reset, power
cycle, or reboot. This variable may be used (set ffnext on)
to cause the next command to a not connected device to
change the state to connected. After the command has been
executed, the ffnext variable is automatically set to off,
so it has no further effect.
Preparing the MSA1000 for TruCluster Server Use 4-29