HP StorageWorks 8/8 - SAN Switch Release Note page 32

Target Containers and corrupts any LUN engaged in a re-keying operation. There is no recovery
for this type of failure.
To remove access between a given initiator and target, the user must not only remove the active
zoning information between the initiator and target, but must also remove the associated Crypto
Target Containers (CTCs), which will in turn remove the associated frame redirection zone inform-
ation.
Before committing configurations or modifications to the CTC or LUNs on an HP Encryption Switch
or HP Encryption Blade, make sure that there are no outstanding zoning transactions in the switch
or fabric. Failure to do so results in the commit operation for the Crypto Target or LUNs failing
and may cause the LUNs to be disabled. The user can check for outstanding zoning transaction
by issuing the cfgtransshow CLI command:
DCX_two:root> cfgtransshow
There is no outstanding zoning transaction
Each LUN is uniquely identified by the HP Encryption Switch or HP Encryption Blade using the
LUN's serial number. The LUN serial numbers must be unique for LUNs exposed from the same
target port. The LUN serial numbers must also be unique for LUNs belonging to different target
ports in non-multipathing configurations. Failure to ensure unique LUN serial numbers results in
non-deterministic behavior and may result in faulting of the HP Encryption Switch or HP Encryption
Blade.
When creating an HA Cluster or Encryption Group with two or more HP Encryption Switch/En-
cryption Blades, the GE Ports (I/O sync links) must be configured with an IP address for the eth0
Ethernet interface using ipaddrset. In addition, both eth0 and eth1 Ethernet ports should be
connected to the network for redundancy. These I/O sync links connections must be established
before any Re-Key, First Time Encryption, or enabling EE for crypto operations. Failure to do so
results in HA Cluster creation failure. If the IP address for these ports is configured after the EE
was enabled for encryption, HP Encryption Switch needs to be rebooted and Encryption blades
should be slotpoweroff/slotpoweron to sync up the IP address information to the EEs. If
only one Ethernet port is configured and connected to a network, data loss or suspension of Re-
Key may occur when the network connection toggles or fails.
initEE will remove the existing master key or link key. Backup the master key by running
cryptocfg –exportmasterkey and cryptocfg –export –currentMK before running
initEE. After initEE, regEE and enableEE, run cryptocfg –recovermasterkey to re-
cover the master key previously backed up, or in the case of fresh install run cryptocfg –
genmasterkey to generate a new master key. If you are using SKM, establish a trusted link with
SKM again. Certificate exchange between key vaults and switches are not required in this case.
The disable EE interface CLI cryptocfg --disableEE [slot no] should be used only to
disable encryption and security capabilities of the EE from the Fabric OS Security Admin in the
event of a security compromise. When disabling the encryption capabilities of the EE using the
noted commands, the EE should not be hosting any CTCs. Ensure that all CTCs hosted on the HP
Encryption Switch or HP Encryption Blade are either removed or moved to a different EE in the
HA Cluster or EG before disabling the encryption and security capabilities.
Whenever initNode is performed, new certificates for CP and KAC (SKM) are generated. Hence,
each time InitNode is performed, the new KAC Certificate must be loaded onto key vaults for
Secure Key Manager (SKM). Without this step, errors will occur, such as key vault not responding
and ultimately key archival and retrieval problems.
The HTTP server should be listening to port 9443. Secure Key Manager is supported only when
configured to port 9443.
When all nodes in an Encryption Group (HA Cluster or DEK Cluster) are powered down (due to
catastrophic disaster or a power outage to the data center) and later nodes come back online (in
the event of the Group Leader (GL) node failing to come back up or the GL node being kept
powered down) the member nodes lose information and knowledge about the Encryption Group.
32