HP StorageWorks Fabric OS 6.3.3d Release Notes (5697-0493, May 2010 - includes all 6.3.0x versions)

CommentsDCFMWebTools 6.1.0Function
Configure > FCIP tunnelPort Admin Module >
GigE tab
GigE ports interface
Configure > FCIP tunnelPort Admin Module >
GigE tab
GigE ports route
In WebTools,
non-local switch
port id/WWN
can be added us-
ing text box.
Configure > ZoningZone Admin
Admin Domain
Switch Admin > DCC
policies
Performance Monitoring
Non-local switch ports
display in zoning tree
Configure > Zoning
Replace/Replace All zone
members by selecting the offline
devices from the zone tree.
Offline devices have an unknown
overlay badge with good
visibility.
Zone AdminRemove Offline or inac-
cessible Devices
Configure > Zoning
Zoning report for both online and
offline database
Zone AdminZone database summary
ping
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.
40