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

Initial setup of encrypted LUNs, Fabric OS 6.4.0 fixes, Solution, Closed defect summary

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 46 highlights

is down, the key creation will fail because of the hardening check failure. As a result, the new key creation operation will not function. For Key retrieval, this is not the requirement and any one Key Vault being online will get the Key as long as that Key Vault has the Key. • Auto rekeying of encrypted disk LUNs may be delayed when an encryption engine reboots or when HAC failover/failback occurs. Should either of these events delay auto rekeying, use the cryptocfg -manual_rekey command to manually start the rekeying of the affected LUNs. Initial setup of encrypted LUNs IMPORTANT: While performing first-time encryption to a LUN with more than one initiator active at the time, rekey operations slow to a standstill. Define LUNs for a single initiator at a time to avoid this occurrence. NOTE: When configuring multipath LUNs, care should be taken to add LUN 0 on all of the paths, subject to the following considerations: • If LUN 0 presented by the back-end target is a controller LUN (not a disk LUN; that is, not visible in the discoverLUN output), add LUN 0 to the container as a clear text LUN. Make sure all of the paths have this LUN 0 added for MPIO operation (EVA configuration, for example). • If LUN 0 presented by the back-end target is a disk LUN, LUN 0 can be added to the container either as clear text or encrypted (MSA configuration, for example). • For HP-UX, LUN 0 can appear as 0x0 or 0x400, but both of them are LUN 0 only and should be treated alike. Fabric OS 6.4.0 fixes Table 10 lists defects closed in the Fabric OS 6.4.0 firmware release. Table 9 Fabric OS 6.4.0 closed defects Closed defect summary Solution Switch panic occurred when management application performed repeat Fixed in Fabric OS 6.4.0 FCP LUN emulation queries through the SMI interface or application polling a switch that had password changed multiple times. HP StorageWorks DC SAN Backbone running Fabric OS 6.1 with 8Gb EX_Ports (Integrated routing, IR) as precondition, upgrade to Fabric OS 6.2-based code, if there is additional hafailover, then add new device, bounce device ports could trigger route problem, causing host to not see the device. Fixed in Fabric OS 6.4.0 Workaround prior to upgrade: Disable SMI agents. Multiple FCR masters in edge fabrics after ISL issues in the backbone. Fixed in Fabric OS 6.4.0 CP rolling reboot on 24000 after standby CP detects heartbeat miss threshold reached and takes over as active CP. Fixed in Fabric OS 6.4.0 Workaround prior to upgrade: Power On/Off. 46

  • 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
is down, the key creation will fail because of the hardening check failure. As a result, the new
key creation operation will not function. For Key retrieval, this is not the requirement and any one
Key Vault being online will get the Key as long as that Key Vault has the Key.
•
Auto rekeying of encrypted disk LUNs may be delayed when an encryption engine reboots or
when HAC failover/failback occurs. Should either of these events delay auto rekeying, use the
cryptocfg –manual_rekey
command to manually start the rekeying of the affected LUNs.
Initial setup of encrypted LUNs
IMPORTANT:
While performing first-time encryption to a LUN with more than one initiator active at the time, rekey
operations slow to a standstill. Define LUNs for a single initiator at a time to avoid this occurrence.
NOTE:
When configuring multipath LUNs, care should be taken to add LUN 0 on all of the paths, subject to
the following considerations:
•
If LUN 0 presented by the back-end target is a controller LUN (not a disk LUN; that is, not visible
in the
discoverLUN
output), add LUN 0 to the container as a clear text LUN. Make sure all of
the paths have this LUN 0 added for MPIO operation (EVA configuration, for example).
•
If LUN 0 presented by the back-end target is a disk LUN, LUN 0 can be added to the container
either as clear text or encrypted (MSA configuration, for example).
•
For HP-UX, LUN 0 can appear as 0x0 or 0x400, but both of them are LUN 0 only and should be
treated alike.
Fabric OS 6.4.0 fixes
Table 10
lists defects closed in the Fabric OS 6.4.0 firmware release.
Table 9 Fabric OS 6.4.0 closed defects
Solution
Closed defect summary
Fixed in Fabric OS 6.4.0
Switch panic occurred when management application performed repeat
FCP LUN emulation queries through the SMI interface or application
polling a switch that had password changed multiple times.
Fixed in Fabric OS 6.4.0
Workaround prior to upgrade:
Disable SMI agents.
HP StorageWorks DC SAN Backbone running Fabric OS 6.1 with 8Gb
EX_Ports (Integrated routing, IR) as precondition, upgrade to Fabric OS
6.2
–
based code, if there is additional
hafailover
, then add new
device, bounce device ports could trigger route problem, causing host
to not see the device.
Fixed in Fabric OS 6.4.0
Multiple FCR masters in edge fabrics after ISL issues in the backbone.
Fixed in Fabric OS 6.4.0
Workaround prior to upgrade:
Power On/Off.
CP rolling reboot on 24000 after standby CP detects heartbeat miss
threshold reached and takes over as active CP.
46