HP 4400 HP StorageWorks Fabric OS 6.4.1 Release Notes (5697-0760, November 201 - Page 43

In a DC SAN Director or DC04 SAN Director with Fabric OS 6.3.1x and DC Switch encryption

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

• Make one of the existing member nodes the Group Leader node and continue operations. 1. On one of the member nodes, create the EG with the same EG name. This makes that node the GL node and the rest of the CTC and Tape Pool related configurations remain intact in this EG. 2. For any containers hosted on the failed GL node, issue cryptocfg --replace to change the WWN association of containers from the failed GL node to the new GL node. • Replace the failed GL node with a new node. 1. On the new node, follow the switch/node initialization steps. 2. Create an EG on this fresh switch/node with the same EG name as before. 3. Perform a configdownload to the new GL node of a previously uploaded configuration file for the EG from an old GL node. 4. For any containers hosted on the failed GL node, issue cryptocfg --replace to change the WWN association of containers from failed GL node to the new GL node. • 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. HP StorageWorks Fabric OS 6.4.1 Release Notes 43

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
•
Make one of the existing member nodes the Group Leader node and continue operations.
1.
On one of the member nodes, create the EG with the same EG name. This makes that
node the GL node and the rest of the CTC and Tape Pool related configurations remain
intact in this EG.
2.
For any containers hosted on the failed GL node, issue
cryptocfg --replace
to
change the WWN association of containers from the failed GL node to the new GL node.
•
Replace the failed GL node with a new node.
1.
On the new node, follow the switch/node initialization steps.
2.
Create an EG on this fresh switch/node with the same EG name as before.
3.
Perform a
configdownload
to the new GL node of a previously uploaded configuration
file for the EG from an old GL node.
4.
For any containers hosted on the failed GL node, issue
cryptocfg --replace
to
change the WWN association of containers from failed GL node to the new GL node.
•
During an online upgrade from Fabric OS 6.2.0x to 6.3.1x, expect to see the I/O link status re-
ported 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.
HP StorageWorks Fabric OS 6.4.1 Release Notes
43