HP B-series Fabric OS 6.3.2e Release Notes (5697-1816, March 2012) - includes all 6.3.2x versions

issued. Fabric OS 6.3.1b and later now reclassifies these messages as warnings, rather than
critical errors.
A new command has been introduced in Fabric OS 6.3.2a that allows configuration of the
fault delay on individual ports. The command portCfgFaultDelay allows a port to be
configured to a 1.2 second fault delay versus the default setting of R_A_TOV.
NAME: portCfgFaultDelay - Configures the fault delay for a single FC port.
SYNOPSIS: portcfgfaultdelay [slot/]port, mode
DESCRIPTION: Use this command to configure the fault delay of an FC port. In the event
that the link is noisy after a host power cycle, the switch may go into a soft fault state,
which means a delay of R_A_TOV. Setting the mode value to 1 reduces the fault delay
value to 1.2 seconds. The configuration is stored in nonvolatile memory and is persistent
across switch reboots and power cycles. Use the portCfgShow command to display
user-configured fault delay settings.
Encryption behavior
HP recommends that the encrypted LUN containers be created when all of the nodes/encryption
engines (EEs) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and
enabled.
If two Encryption Engines are part of a High Availability Cluster, configure the host/target
pair such that they form a multipath from both EEs. Avoid connecting both the host/target
pairs to the same EE. This connectivity does not give full redundancy in case of EE failure
resulting in HAC failover.
Since the quorum disk plays a vital role in keeping the cluster in sync, configure the
quorum disk to be outside of the encryption environment.
LUN configuration
To configure a LUN for encryption:
Add the LUN as clear-text to the Crypto Target Container (CTC).
When the LUN comes online and the clear-text host I/O starts, modify the LUN from
clear-text to encrypted, including the enable_encexistingdata option to convert
the LUN from clear-text to encrypted.
An exception to this LUN configuration process: If the LUN was previously encrypted by
the HP Encryption Switch or HP Encryption Blade, the LUN can be added to the CTC with
the encrypt and lunstate =encrypted options.
LUN configurations must be committed to take effect. No more than 25 LUNs can be
added or modified in a single commit operation. Attempts to commit configurations that
exceed 25 LUNs will fail with a warning. There is also a five-second delay before the
commit operation takes effect.
Always ensure that any previously committed LUN configurations or LUN modifications
have taken effect before committing additional LUN configurations or additions. All LUNs
should be in an Encryption Enabled state before committing additional LUN modifications.
The cryptocfg -manual_rekey -all command should not be used in environments
with multiple encryption engines (encryption blades) installed in a director-class chassis when
more than one encryption engine has access to the same LUN. In such situations, use the
cryptocfg -manual_rekey <CTC> <LUN Num> <Initiator PWWN> command to
manually rekey these LUNs.
If an HA Cluster is configured within an Encryption Group with containers configured for auto
Failback Mode, the following procedure must be followed when upgrading from Fabric OS
34