Hp-ux considerations, Aix considerations, Enabling a disabled lun – Brocade Fabric OS Encryption Administrator’s Guide Supporting RSA Data Protection Manager (DPM) Environments (Supporting Fabric OS v7.2.0) User Manual
Page 253
Fabric OS Encryption Administrator’s Guide (DPM)
233
53-1002922-01
HP-UX considerations
5
HP-UX considerations
The HP-UX OS requires LUN 0 to be present. LUNs are scanned differently based on the type value
returned for LUN 0 by the target device.
•
If the type is 0, then HP-UX only scans LUNs from 0 to 7. That is the maximum limit allowed by
HP-UX for device type for type 0.
•
If the type is 0xC, then HP-UX scans all LUNs.
For HP-UX multi-path configurations:
•
Add LUN 0 as a cleartext LUN.
•
Make sure to configure a dummy LUN 0 for each host accessing multi-path LUNs through CTCs
in the encryption switch.
cryptocfg -–add –LUN
<crypto target container name> 0 <initiator PWWN>
<initiator NWWN>
Best practices are as follows:
•
Create a cryptoTarget container for the target WWN.
•
Add the HP-UX initiator WWN to the container.
•
Issue the discover LUN CLI command on the container to discover the LUNs present in the
target.
•
Based on the LUN list returned as part of LUN discovery, add the LUN 0 if LUN 0 is present in
the target (which is usually the case).
NOTE
When an EMC-CX3 storage array is used with HP-UX the CX3 array exposes both 0x0 and 0x4000
LUNs to the HP-UX host. 0x0 and 0x4000 LUNs have the same LSN. Both must be added as
cleartext.
AIX considerations
For AIX-based PowerHA SystemMirror host clusters, the cluster repository disk should be defined
outside of the encryption environment.
Ensure that Dynamic Tracking is set to “Yes” for all Fibre Channel adapters on the AIX system.
Enabling a disabled LUN
When Metadata is found on the LUN, but current LUN state is indicated as cleartext or is being
converted from encrypt to cleartext, the LUN is disabled and the LUN status displayed by the LUN
Show CLI command is Internal EE LUN state: Encryption disabled <Reason Code>.
The disabled LUN can be enabled by invoking the enable LUN command.
switch:admin> cryptocfg --enable -LUN <crypto target container name> <LUN Num>
<InitiatorPWWN>