HP 1606 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 40

• During an online upgrade from Fabric OS 6.2.0x to 6.3.1x, expect to see the I/O link status reported as Unreachable when the cryptocfg command is invoked. However, once all the nodes are upgraded to Fabric OS 6.3.1x, the command accurately reflects the status of the I/O Link. The I/O link status should be disregarded during the code upgrade process. • The -key_lifespan option has no effect for cryptocfg -add -LUN, and only has an effect for cryptocfg --create -tapepool for tape pools declared -encryption_format native. For all other encryption cases, a new key is generated each time a medium is rewound and block zero is written or overwritten. For the same reason, the Key Life field in the output of cryptocfg --show -container -all -stat should always be ignored, and the Key Life field in cryptocfg --show -tapepool -cfg is significant only for native-encrypted pools. • The Quorum Authentication feature requires DCFM 10.3.0 or later. Note that all nodes in the EG must be running Fabric OS 6.3.0 or later for quorum authentication to be properly supported. • In a DC SAN Director or DC04 SAN Director with Fabric OS 6.3.1x and DC Switch encryption FC blades installed, you must set the quorum size to zero and disable the system card on the blade prior to downgrading to a Fabric OS version earlier than 6.3.0. • The System Card feature requires DCFM 10.3.0 or later. Note that all nodes in the EG must be running Fabric OS 6.3.0 or later for system verification to be properly supported. • The Encryption SAN Switch and Encryption FC blade do not support QoS. When using encryption or Frame Redirection, participating flows should not be included in QoS Zones. • HP encryption devices can be configured for either disk or tape operation. However, encryption FC blades can be configured to support different media types within a common DC SAN Director/ DC04 SAN Director chassis. The ability to configure multiple Crypto-Target Containers defining different media types on a single encryption engine (Encryption SAN Switch or Encryption FC blade) is supported beginning with Fabric OS 6.4.0. • SKM is supported with Multiple Nodes and Dual SKM Key Vaults. Two-way certificate exchange is supported. See the Encryption Admin Guide for configuration information. If you are using dual SKMs on Encryption SAN Switch/Encryption FC blade Encryption Group, these SKM Appliances must be clustered. Failure to cluster results in key creation failure. Otherwise, register only one SKM on the Encryption SAN Switch/Encryption FC blade Encryption Group. • When the tape key expires in the middle of write operation on the tape, the key is used to append the data on the tape media. When the backup application rewinds the media and starts writing to Block-0 again (and if the key is expired), a new key is created and used henceforth. The expired key is then marked as read only and used only for restoring data from previously encrypted tapes. • With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes less than 400 MB are presented to the Encryption SAN Switch for encryption, a host panic may occur; this configuration is not supported for Fabric OS 6.3.x. • HCL from Fabric OS 6.2.x to 6.3.1x is supported. Cryptographic operations and I/O are disrupted but other layer 2 traffic is not. • Relative to the Encryption SAN Switch and a DC SAN Director with Encryption FC blade, all nodes in the Encryption Group must be at the same firmware level of Fabric OS 6.2 or 6.3 before starting a rekey or First Time Encryption operation. Make sure that existing rekey or First Time Encryption operations complete before upgrading any of the encryption products in the Encryption Group. Also, make sure that the upgrade of all nodes in the Encryption Group to Fabric OS 6.3.1x completes before starting a rekey or First Time Encryption operation. 40