Brocade Fabric OS Encryption Administrator's Guide v7.1.0 (53-1002721-01, March 2013)
Table Of Contents
- Contents
- About This Document
- Encryption Overview
- In this chapter
- Host and LUN considerations
- Terminology
- The Brocade Encryption Switch
- The FS8-18 blade
- FIPS mode
- Performance licensing
- Recommendation for connectivity
- Usage limitations
- Brocade encryption solution overview
- Data encryption key life cycle management
- Master key management
- Support for virtual fabrics
- Cisco Fabric Connectivity support
- Configuring Encryption Using the Management Application
- In this chapter
- Encryption Center features
- Encryption user privileges
- Smart card usage
- Using authentication cards with a card reader
- Registering authentication cards from a card reader
- Registering authentication cards from the database
- Deregistering an authentication card
- Setting a quorum for authentication cards
- Using system cards
- Enabling or disabling the system card requirement
- Registering systems card from a card reader
- Deregistering system cards
- Using smart cards
- Tracking smart cards
- Editing smart cards
- Network connections
- Blade processor links
- Encryption node initialization and certificate generation
- Steps for connecting to an ESKM/SKM appliance
- Configuring a Brocade group on ESKM/SKM
- Registering the ESKM/SKM Brocade group user name and password
- Setting up the local Certificate Authority (CA) on ESKM/SKM
- Downloading the local CA certificate from ESKM/SKM
- Creating and installing the ESKM/SKM server certificate
- Enabling SSL on the Key Management System (KMS) Server
- Creating an ESKM/SKM High Availability cluster
- Copying the local CA certificate for a clustered ESKM/SKM appliance
- Adding ESKM/SKM appliances to the cluster
- Signing the encryption node KAC certificates
- Importing a signed KAC certificate into a switch
- ESKM/SKM key vault high availability deployment
- Encryption preparation
- Creating a new encryption group
- Adding a switch to an encryption group
- Replacing an encryption engine in an encryption group
- High availability (HA) clusters
- Configuring encryption storage targets
- Configuring hosts for encryption targets
- Adding target disk LUNs for encryption
- Adding target tape LUNs for encryption
- Moving Targets
- Configuring encrypted tape storage in a multi-path environment
- Tape LUN write early and read ahead
- Tape LUN statistics
- Encryption engine rebalancing
- Master keys
- Active master key
- Alternate master key
- Master key actions
- Saving the master key to a file
- Saving a master key to a key vault
- Saving a master key to a smart card set
- Restoring a master key from a file
- Restoring a master key from a key vault
- Restoring a master key from a smart card set
- Creating a new master key
- Security Settings
- Zeroizing an encryption engine
- Using the Encryption Targets dialog box
- Redirection zones
- Disk device decommissioning
- Rekeying all disk LUNs manually
- Thin provisioned LUNs
- Viewing time left for auto rekey
- Viewing and editing switch encryption properties
- Viewing and editing encryption group properties
- Encryption-related acronyms in log messages
- Configuring Encryption Using the CLI
- In this chapter
- Overview
- Command validation checks
- Command RBAC permissions and AD types
- Cryptocfg Help command output
- Management LAN configuration
- Configuring cluster links
- Setting encryption node initialization
- Steps for connecting to an SKM or ESKM appliance
- Configuring a Brocade group
- Setting up the local Certificate Authority (CA)
- Downloading the local CA certificate
- Creating and installing the SKM or ESKM server certificate
- Enabling SSL on the Key Management System (KMS) Server
- Creating an SKM or ESKM high availability cluster
- Copying the local CA certificate
- Adding SKM or ESKM appliances to the cluster
- Initializing the Fabric OS encryption engines
- Signing the Brocade encryption node KAC certificates
- Registering SKM or ESKM on a Brocade encryption group leader
- Registering the SKM/ESKM Brocade group user name and password
- SKM or ESKM key vault high availability deployment
- Adding a member node to an encryption group
- Generating and backing up the master key
- High availability cluster configuration
- Re-exporting a master key
- Enabling the encryption engine
- Zoning considerations
- CryptoTarget container configuration
- Crypto LUN configuration
- Impact of tape LUN configuration changes
- Configuring a multi-path Crypto LUN
- Decommissioning LUNs
- Decommissioning replicated LUNs
- Force-enabling a decommissioned disk LUN for encryption
- Force-enabling a disabled disk LUN for encryption
- Tape pool configuration
- First-time encryption
- Thin provisioned LUNs
- Data rekeying
- Deployment Scenarios
- In this chapter
- Single encryption switch, two paths from host to target
- Single fabric deployment - HA cluster
- Single fabric deployment - DEK cluster
- Dual fabric deployment - HA and DEK cluster
- Multiple paths, one DEK cluster, and two HA clusters
- Multiple paths, DEK cluster, no HA cluster
- Deployment in Fibre Channel routed fabrics
- Deployment as part of an edge fabric
- Deployment with FCIP extension switches
- VMware ESX server deployments
- Best Practices and Special Topics
- In this chapter
- Firmware upgrade and downgrade considerations
- Configuration upload and download considerations
- Configuration upload at an encryption group leader node
- Configuration upload at an encryption group member node
- Information not included in an upload
- Steps before configuration download
- Configuration download at the encryption group leader
- Configuration download at an encryption group member
- Steps after configuration download
- HP-UX considerations
- AIX Considerations
- Enabling a disabled LUN
- Disk metadata
- Tape metadata
- Tape data compression
- Tape pools
- Tape block zero handling
- Tape key expiry
- Configuring CryptoTarget containers and LUNs
- Redirection zones
- Deployment with Admin Domains (AD)
- Do not use DHCP for IP interfaces
- Ensure uniform licensing in HA clusters
- Tape library media changer considerations
- Turn off host-based encryption
- Avoid double encryption
- PID failover
- Turn off compression on extension switches
- Rekeying best practices and policies
- KAC certificate registration expiry
- Changing IP addresses in encryption groups
- Disabling the encryption engine
- Recommendations for Initiator Fan-Ins
- Best practices for host clusters in an encryption environment
- HA Cluster deployment considerations and best practices
- Key Vault Best Practices
- Tape Device LUN Mapping
- Maintenance and Troubleshooting
- In this chapter
- Encryption group and HA cluster maintenance
- Displaying encryption group configuration or status information
- Removing a member node from an encryption group
- Deleting an encryption group
- Removing an HA cluster member
- Displaying the HA cluster configuration
- Replacing an HA cluster member
- Deleting an HA cluster member
- Performing a manual failback of an encryption engine
- Encryption group merge and split use cases
- A member node failed and is replaced
- A member node reboots and comes back up
- A member node lost connection to the group leader
- A member node lost connection to all other nodes in the encryption group
- Several member nodes split off from an encryption group
- Adjusting heartbeat signaling values
- EG split possibilities requiring manual recovery
- Configuration impact of encryption group split or node isolation
- Encryption group database manual operations
- Key vault diagnostics
- Measuring encryption performance
- General encryption troubleshooting
- Troubleshooting examples using the CLI
- Management application encryption wizard troubleshooting
- LUN policy troubleshooting
- Loss of encryption group leader after power outage
- MPIO and internal LUN states
- FS8-18 blade removal and replacement
- Brocade Encryption Switch removal and replacement
- Reclaiming the WWN base of a failed Brocade Encryption Switch
- Removing stale rekey information for a LUN
- Downgrading firmware from Fabric OS 7.1.0
- Fabric OS and ESKM compatibility matrix
- Splitting an encryption group into two encryption groups
- Moving an encryption blade from one EG to another in the same fabric
- Moving an encryption switch from one EG to another in the same fabric
- State and Status Information
160 Fabric OS Encryption Administrator’s Guide (SKM/ESKM)
53-1002721-01
Enabling the encryption engine
3
MasterKey ID: 1a:e6:e4:26:6b:f3:81:f7:d8:eb:cc:0f:09:7a:a4:7e
Exported Key ID: 1a:e6:e4:26:6b:f3:81:f7:d8:eb:cc:0f:09:7a:a4:80
Example: Recovering a master key using master key ID from the second master key export
SecurityAdmin:switch> cryptocfg --recovermasterkey -currentMK -keyID
15:30:f0:f3:5c:2b:28:ce:cc:a7:b4:cd:7d:2a:91:fc
Enter passphrase:
Recover master key status: Operation Succeeded.
Enabling the encryption engine
Enable the encryption engine by entering the cryptocfg --enableEE command. Provide a slot
number if the encryption engine is a blade.
NOTE
Every time a Brocade Encryption Switch or DCX Backbone chassis containing one or more FS8-18
blades goes through power cycle event, or after issuing slotpoweroff <slot number> followed by
slotpoweron <slot number> for an FS8-18 blade in a DCX Backbone chassis, the encryption engine
must be enabled manually by the Security Administrator. Hosts cannot access the storage LUNs
through the storage paths exposed on this Brocade Encryption Switch or FS8-18 blade until the
encryption engine is enabled. The encryption engine state can viewed using the cryptocfg
--show
-localEE command, or by displaying switch or blade properties from DFCM. An encryption engine
that is not enabled indicates Waiting for Enable EE.
SecurityAdmin:switch> cryptocfg --enableEE
Operation succeeded.
Checking encryption engine status
You can verify the encryption engine status at any point in the setup process and get information
about the next required configuration steps or to troubleshoot an encryption engine that behaves in
unexpected ways. Use the cryptocfg
--show -localEE command to check the encryption engine
status.
SecurityAdmin:switch> cryptocfg --show -localEE
EE Slot: 0
SP state: Waiting for initEE
EE key status not available: SP TLS connection is not up.
No HA cluster membership
EE Slot: 1
SP state: Online
Current Master KeyID:
a3:d7:57:c7:54:66:65:05:61:7a:35:2c:59:af:a5:dc
Alternate Master KeyID:
e9:e4:3a:f8:bc:4e:75:44:81:35:b8:90:d0:1f:6f:4d
HA Cluster Membership: hacDcx2
EE Attributes:
Media Type : DISK
EE Slot: 3
SP state: Online