HP StorageWorks 8/8 - SAN Switch Nota de lançamento - Página 28
Procurar online ou descarregar pdf Nota de lançamento para Interruptor HP StorageWorks 8/8 - SAN Switch. HP StorageWorks 8/8 - SAN Switch 43 páginas. Hp storageworks fabric os 6.1.2b release notes (5697-0351, march 2010)
Também para HP StorageWorks 8/8 - SAN Switch: Nota de lançamento (30 páginas), Nota de lançamento (29 páginas), Nota de lançamento (32 páginas)
Imprimir página
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.
This leads to no crypto operations or commands (except node initialization) being available on
the member nodes after the power-cycle. This condition persists until the GL node is back online.
Workaround. In the case of a datacenter power down, bring the GL node online first, before
the other member nodes are brought back up.
In the event of the GL node failing to come back up, the GL node can be replaced with a new
node. The following are the procedures to allow an EG to function with existing member nodes
and to replace the failed GL node with a new node
Make one of the existing member nodes the Group Leader node and continue operations:
1.
On one of the member nodes, create the Encryption Group with the same Encryption
Group name. This will make that node the GL node and the rest of the Crypto Target
Container and Tape Pool related configurations will remain intact in this Encryption Group.
28