HP 4400 HP StorageWorks Fabric OS 6.4.0c Release Notes (5697-0703, September 2 - Page 43
Relative to the Encryption SAN Switch and a DC SAN Director with Encryption FC blade, all nodes
View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 43 highlights
• 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. • To clean up the stale rekey information for the LUN, use one of the following methods: • Method 1 1. Modify the LUN policy from encrypt to cleartext and commit. The LUN becomes disabled. 2. Enable the LUN using cryptocfg --enable -LUN. Modify the LUN policy from clear-text to encrypt with enable_encexistingdata to enable the first time encryption and commit. This clears the stale rekey metadata on the LUN and the LUN can be used again for encryption. • Method 2 1. Remove the LUN from Crypto Target Container and commit. 2. Add the LUN back to the Crypto Target Container with LUN State="clear-text", policy="encrypt" and enable_encexistingdata set for enabling the First Time Encryption and commit. This clears the stale rekey metadata on the LUN and the LUN can be used again for encryption. • In an environment with a mixed firmware version (Fabric OS 6.2.x + 6.3.x) Encryption Group, the I/O link state reported for Fabric OS 6.2.x nodes is unreachable. During a rolling upgrade from Fabric OS 6.2.0x to 6.3.1x, you should see the I/O link status reported as Unreachable when the cryptocfg -show -loc command is invoked. However, once all the nodes are upgraded to Fabric OS 6.3.1x, the show command accurately reflects the status of the I/O Link. The I/O link status while performing the rolling upgrade from Fabric OS 6.2.x to 6.3.1x can be ignored until all nodes have been upgraded to 6.3.1x. Mace39:root> cryptocfg --show -loc EE Slot: 0 SP state: Online Current Master KeyID: 43:f1:bd:dc:91:89:f2:f1:6a:a1:48:89:7b:d0:5f:59 Alternate Master KeyID: 3a:a4:5b:86:90:d5:69:26:29:78:f8:3b:f9:b2:9c:b9 HA Cluster Membership: hac39_115 EE Attributes: Link IP Addr : 10.32.50.36 Link GW IP Addr: 10.32.48.1 Link Net Mask : 255.255.240.0 Link MAC Addr : 00:05:1e:53:8a:86 Link MTU : 1500 Link State : UP Media Type : DISK System Card Label : System Card CID : HP StorageWorks Fabric OS 6.4.0c Release Notes 43