Page 1 53-1002159-03 53-1002159-03 ® 28 July 2011 Fabric OS Encryption Administrator’s Guide Supporting HP Secure Key Manager (SKM) Environments and HP Enterprise Secure Key Manager (ESKM) Environments Supporting Fabric OS v7.0.0...
Page 2: Document History
Copyright © 2010-2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Page 3 Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 4 Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 5: Table Of Contents
Contents About This Document In this chapter ......... . . xiii How this document is organized .
Page 6 Chapter 2 Encryption configuration In this chapter ......... . . 13 Encryption Center features.
Page 7 Creating high availability (HA) clusters ..... . . 54 Removing engines from an HA cluster ....55 Swapping engines in an HA cluster .
Page 8 Viewing and editing group properties ......98 General tab......... . 99 Members tab .
Page 9 Re-exporting a master key ....... .140 Exporting an additional key ID ......141 Viewing the master key IDs .
Page 10 Chapter 4 Deployment Scenarios In this chapter ......... .175 Single encryption switch, two paths from host to target .
Page 11 Do not use DHCP for IP interfaces ......199 Ensure uniform licensing in HA clusters .....199 Tape library media changer considerations .
Page 12 Encryption group merge and split use cases ....213 A member node failed and is replaced ....213 A member node reboots and comes back up .
Page 13 Security processor KEK status ......250 Encrypted LUN states ........250 Index Fabric OS Encryption Administrator’s Guide xiii...
Page 14 Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 15: About This Document
About This Document In this chapter • How this document is organized ........xiii •...
Page 16: Supported Hardware And Software
• Chapter 6, “Maintenance and Troubleshooting,” provides information on troubleshooting and the most common commands and procedures to use to diagnose and recover from problems. • Appendix A, “State and Status Information,” lists the encryption engine security processor (SP) states, security processor key encryption key (KEK) status information, and encrypted LUN states.
Page 17: Command Syntax Conventions
Command syntax conventions Command syntax in this manual follows these conventions: command Commands are printed in bold. option, option Command options are printed in bold. argument, arg Arguments. Optional element. variable Variables are printed in italics. In the help pages, variables are underlined or enclosed in angled brackets <...
Page 18: Notice To The Reader
For definitions specific to this document, see “Terminology” on page 2. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia.org/education/dictionary Notice to the reader This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations.
Page 19: Getting Technical Help
Release notes are available on the MyBrocade website and are also bundled with the Fabric OS firmware. Other industry resources • White papers, online demos, and data sheets are available through the Brocade website at http://www.brocade.com/products-solutions/products/index.page. • Best practice guides, white papers, data sheets, and other documentation is available through the Brocade Partner website.
Page 20: Document Feedback
The serial number label is located as follows: • Brocade Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side of the switch on the left. • Brocade DCX—On the bottom right on the port side of the chassis •...
Page 21: In This Chapter
Chapter Encryption Overview In this chapter • Host and LUN considerations ........1 •...
Page 22: Terminology
Terminology Terminology The following are definitions of terms used extensively in this document. ciphertext Encrypted data. cleartext Unencrypted data. CryptoModule The secure part of an encryption engine that is protected to the FIPS 140-2 level 3 standard. The term CryptoModule is used primarily in the context of FIPS authentication.
Page 23 Terminology Opaque Key Vault A storage location that provides untrusted key management functionality. Its contents may be visible to a third party. DEKs in an opaque key vault are stored encrypted in a master key to protect them. Recovery cards A set of smart cards that contain a backup master key.
Page 24: The Brocade Encryption Switch
The Brocade Encryption Switch The Brocade Encryption Switch The Brocade Encryption Switch (BES) is a high performance 32 port auto-sensing 8 Gbps Fibre Channel switch with data cryptographic (encryption/decryption) and data compression capabilities. The switch is a network-based solution that secures data-at-rest for heterogeneous tape drives, disk array LUNs, and virtual tape libraries by encrypting the data using Advanced Encryption Standard (AES) 256-bit algorithms.
Page 25: The Fs8-18 Blade
The FS8-18 blade The FS8-18 blade The FS8-18 blade provides the same features and functionality as the encryption switch. The FS8-18 blade installs on the Brocade DCX and DCX-4S. Four FS8-18 blades may be installed in a single DCX or DCX-4S. FIPS mode Both the BES and the FS8-18 blade always boot up in FIPS mode, which cannot be disabled.
Page 26: Recommendation For Connectivity
Recommendation for connectivity Recommendation for connectivity In order to achieve high performance and throughput, the encryption engines perform what is referred to as “cut-through” encryption. In simple terms, this is achieved by encrypting the data in data frames on a per-frame basis. This enables the encryption engine to buffer only one frame, encrypt it, and send out the frame to the target on write I/Os.
Page 27: Brocade Encryption Solution Overview
Brocade encryption solution overview Brocade encryption solution overview The loss of stored private data, trade secrets, intellectual properties, and other sensitive information through theft or accidental loss of disk or tape media can have widespread negative consequences for governments, businesses, and individuals. This threat is countered by an increasing demand from governments and businesses for solutions that create and enforce policies and procedures that protect stored data.
Page 28: Data Flow From Server To Storage
Brocade encryption solution overview Data flow from server to storage The Brocade Encryption Switch can be introduced into a SAN with minimum disruption, with no need for SAN reconfiguration, and with no need to reconfigure host applications. Frames sent from a host and a target LUN are redirected to a virtual target associated with the encryption switch.
Page 29: Data Encryption Key Life Cycle Management
Data encryption key life cycle management Data encryption key life cycle management Data encryption keys (DEKs) are generated by the encryption engine. Data is encrypted and decrypted using the same DEK, so a DEK must be preserved at least long enough to decrypt the ciphertext that it created.
Page 30: Master Key Management
Master key management FIGURE 5 DEK life cycle Master key management Communications with opaque key vaults are encrypted using a master key that is created by the encryption engine on the encryption switch. Currently, this includes the key vaults of all supported key management systems except NetApp LKM.
Page 31: Support For Virtual Fabrics
Support for Virtual Fabrics • A set of recovery smart cards. This option is only available if the switch is managed by the Data Center Fabric Manager (DFCM), and if a card reader is available for attachment to the DCFM workstation.
Page 32 Cisco Fabric Connectivity support Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 33: In This Chapter
Chapter Encryption configuration In this chapter • Encryption Center features ........14 •...
Page 34: Encryption Center Features
Encryption Center features Encryption Center features The Encryption Center dialog box is the single launching point for all encryption-related configuration in the Management application. It also provides a table that shows the general status of all encryption-related hardware and functions at a glance. FIGURE 6 Encryption Center dialog box Beginning with Fabric OS 6.4, the Encryption Center is dynamically updated to reflect the latest...
Page 35: Encryption User Privileges
Encryption user privileges Encryption user privileges In the Management application, resource groups are assigned privileges, roles, and fabrics. Privileges are not directly assigned to users; users get privileges because they belong to a role in a resource group. A user can only belong to one resource group at a time. The Management application provides three pre-configured roles: •...
Page 36: Smart Card Usage
Smart card usage Smart card usage Smart cards are credit card-sized cards that contain a CPU and persistent memory. Smart cards can be used as security devices. You must have Storage Encryption Security user privileges to activate, register, and configure smart cards. Smart cards can be used to do the following: •...
Page 37 Smart card usage 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2. Select an encryption group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click an encryption group and select Security. The Encryption Group Properties dialog box displays, with the Security tab selected.
Page 38: Registering Authentication Cards From The Database
Smart card usage FIGURE 8 Add Authentication Card dialog box 5. Insert a smart card into the card reader. Wait for the card serial number to appear, then enter card assignment information as directed. 6. Click OK. Wait for the confirmation dialog box indicating initialization is done, then click OK. The card is added to the Registered Authentication Cards table in the Encryption Group Properties dialog box.
Page 39: Deregistering An Authentication Card
Smart card usage FIGURE 9 Authentication Cards dialog box - registering smart cards from archive 4. Select a card from the table, then click OK. 5. Wait for the confirmation dialog box indicating initialization is done, then click OK. The card is added to the Registered Authentication Cards table in the Encryption Group Properties dialog box.
Page 40: Using Authentication Cards
Smart card usage Using authentication cards When a quorum of authentication cards is registered for use, an Authenticate dialog box is displayed to grant access to the following: • The Encryption Group Properties dialog box Link Keys tab (for NetApp LKM only). •...
Page 41: Registering System Cards From A Card Reader
Smart card usage Registering system cards from a card reader System cards are smart cards that can be used to control activation of encryption engines. Encryption switches and blades have a card reader that enables the use of a system card. System cards discourage theft of encryption switches or blades by requiring the use of a system card at the switch or blade to enable the encryption engine.
Page 42: Tracking Smart Cards
Smart card usage 2. Select the switch from the Encryption Center Devices table, then select Switch > System Cards from the menu task bar, or right-click the switch and select System Cards. The System Cards dialog box displays. 3. Select the system card to deregister. 4.
Page 43: Editing Smart Cards
Smart card usage Editing smart cards Use the Edit Smart Card dialog box to edit smart card details. 1. From the Encryption Center dialog box, select Smart Card > Edit Smart Card from the menu task bar. The Edit Smart Card dialog box displays. FIGURE 12 Edit Smart Card dialog box 2.
Page 44: Network Connections
Network connections Network connections Before you use the encryption setup wizard for the first time, you must have the following required network connections: • The management ports on all devices that will perform encryption (Brocade Encryption Switches, or DCX and DCX-4S chassis with encryption blades installed) must have a LAN connection to the SAN management program, and must be available for discovery.
Page 45: Encryption Node Initialization And Certificate Generation
Encryption node initialization and certificate generation 3. Enter the link IP address and mask, and the gateway IP address. 4. Click OK. The Blade Processor Link dialog box can also be launched from the following locations: Select an encryption group from the Encryption Center Devices table, then select Group > HA Clusters from the menu task bar, or right-click a group and select HA Clusters.
Page 46: Steps For Connecting To An Skm Or Eskm Appliance
Steps for connecting to an SKM or ESKM appliance FIGURE 14 Warning message 2. Select Yes to initialize the node. Steps for connecting to an SKM or ESKM appliance The SKM and Enterprise SKM (ESKM) management web console can be accessed from any web browser with Internet access to the SKM/ESKM appliance.
Page 47: Configuring A Brocade Group On Skm Or Eskm
Steps for connecting to an SKM or ESKM appliance These steps are described in more detail in the following sections: • “Registering authentication cards from the database” on page 18 • “Registering the SKM or ESKM Brocade group user name and password” on page 28 •...
Page 48: And Password
Steps for connecting to an SKM or ESKM appliance Registering the SKM or ESKM Brocade group user name and password The Brocade group user name and password you created when configuring a Brocade group on SKM/ESKM must also be registered on each Brocade encryption node. NOTE This operation can be performed only after the switch is added to the encryption group.
Page 49 Steps for connecting to an SKM or ESKM appliance Setting up the local Certificate Authority (CA) on SKM or ESKM To create and install a local CA, complete the following steps: 1. Log in to the SKM/ESKM management web console using the admin password. 2.
Page 50: Downloading The Local Ca Certificate From Skm Or Eskm
Steps for connecting to an SKM or ESKM appliance 6. Under Certificates & CAs, select Trusted CA Lists to display the Trusted Certificate Authority List Profiles. Click on Default under Profile Name. 8. In the Trusted Certificate Authority List, click Edit. 9.
Page 51: Server
Steps for connecting to an SKM or ESKM appliance 10. Click Sign Request. 11. Enter the required data in the Sign Certificate Request section of the window. Select the CA name from the Sign with Certificate Authority drop-down list. 12. Paste the copied certificate request data into the Certificate Request box. 13.
Page 52: Creating An Skm Or Eskm High Availability Cluster
Steps for connecting to an SKM or ESKM appliance FIGURE 17 SKM Key Management Services Configuration window 3. In the KMS Server Settings section of the window, select the following check boxes: • Use SSL • Allow Key and Policy Configuration Operations •...
Page 53: Copying The Local Ca Certificate For A Clustered Skm Or Eskm Appliance
Steps for connecting to an SKM or ESKM appliance To create a cluster, perform the following steps on one of the HP SKM/ESKM appliances that is to be a member of the cluster. 1. From the SKM/ESKM management console, click the Device tab. 2.
Page 54: Signing The Brocade Encryption Node Kac Certificates
Steps for connecting to an SKM or ESKM appliance Enter information required in the Install CA Certificate section near the bottom of the page. Enter the Certificate Name of the certificate being transferred from the first cluster member. Paste the copied certificate data into the Certificate box. 4.
Page 55: Importing A Signed Kac Certificate Into A Switch
Steps for connecting to an SKM or ESKM appliance Alternatively, you may select a switch, then select Switch > Properties. Click the Export button beside the Public Key Certificate Request, or copy the CSR for pasting into the Certificate Request Copy area on the SKM/ESKM Sign Certificate Request page. 4.
Page 56: Skm Or Eskm Key Vault High Availability Deployment
Steps for Migrating from SKM to ESKM SKM or ESKM key vault high availability deployment The SKM/ESKM key vault has high availability clustering capability. SKM/ESKM appliances can be clustered together in a transparent manner to the end user. Encryption keys saved to one key vault are synchronously hardened to the cluster pairs.
Page 57: Steps Required Using Brocade Management Application
Steps for Migrating from SKM to ESKM NOTE If the earlier configuration was done for SKM using CLI and if the previously imported CA certificate was not deleted (using the command cryptocfg file -delete), the CA file that was previously imported can be reused, and importing the CA certificate is not required. 3.
Page 58: Encryption Preparation
Encryption preparation Click Download, and save the certificate file on your local system. d. Rename the downloaded file, changing the .cert extension to a .pem extension. 5. From the Encryption Group Properties dialog box, click Load from File to upload the new ESKM certificate to the switch, then click OK.
Page 59 Creating a new encryption group FIGURE 20 Encryption Center - No Group Defined dialog box 2. Select a switch from the <NO GROUP DEFINED> encryption group. (The switch must not be assigned to an encryption group.) 3. Select Encryption > Create/Add to Group, from the menu task bar, or right-click the switch and select Create/Add to Group.
Page 60 Creating a new encryption group FIGURE 22 Designate Switch Membership dialog box 5. Verify that Create a new encryption group containing just this switch is selected. 6. Click Next. The Create a New Encryption Group dialog box displays. FIGURE 23 Create a New Encryption Group dialog box Enter an Encryption Group Name for the encryption group and select Automatic failback mode.
Page 61 Creating a new encryption group If the name for the encryption group already exists, a pop-up warning message displays. Although unique group names avoid confusion while managing multiple groups, you are not prevented from using duplicate group names. Click Yes to use the same name for the new encryption group, or click No to enter another name.
Page 62 Creating a new encryption group FIGURE 25 Specify Public Key Certificate filename dialog box 11. Enter the location of the file where you want to store the certificate information, or browse to the desired location. 12. Click Next. The Specify Master Key File Name dialog box displays. FIGURE 26 Specify Master Key File Name dialog box Fabric OS Encryption Administrator’s Guide...
Page 63 Creating a new encryption group 13. Enter the passphrase, which is required for restoring the master key. The passphrase can be between eight and 40 characters, and any character is allowed. 14. Re-enter the passphrase for verification. 15. Click Next. The Select Security Settings dialog box displays.
Page 64 Creating a new encryption group FIGURE 28 Confirm Configuration dialog box 18. Verify the information, then click Next. The Configuration Status dialog box displays. Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 65 Creating a new encryption group FIGURE 29 Configuration Status dialog box All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified.
Page 66: Understanding Configuration Status Results
Creating a new encryption group FIGURE 30 Next Steps dialog box 20. Review post-configuration instructions, which you can copy to a clipboard or print for later. 21. Click Finish to exit the Configure Switch Encryption wizard. 22. Review “Understanding configuration status results”.
Page 67: Adding A Switch To An Encryption Group
Adding a switch to an encryption group • Back up the master key to a file. (Opaque key vaults only). The Management application saves the master key into the specified file. • Enable the encryption engines initializes an encryption switch using the cryptocfg initEE [<slotnumber>] and cryptocfg regEE [<slotnumber>] commands.
Page 68 Adding a switch to an encryption group FIGURE 31 Configure Switch Encryption wizard - welcome panel 3. Click Next. The Designate Switch Membership dialog box displays. FIGURE 32 Designate Switch Membership dialog box a. Select Add this switch to an existing encryption group. b.
Page 69 Adding a switch to an encryption group The Add Switch to Existing Encryption Group dialog box displays. FIGURE 33 Add Switch to Existing Encryption Group dialog box 4. Select the group in which to add the switch, then click Next. The Specify Public Key Certificate Filename dialog box displays.
Page 70 Adding a switch to an encryption group 5. Specify the name of the file in which to store the public key certificate that is used to authenticate connections to the key vault, then click Next. The Confirm Configuration panel displays. The dialog box shows the encryption group name and switch public key certificate file name you specified.
Page 71 Adding a switch to an encryption group FIGURE 36 Configuration Status dialog box All configuration items have green check marks if the configuration is successful. A red stop sign indicates a failed step. A message displays below the table, indicating the encryption switch was added to the group you named, and the public key certificate is stored in the location you specified.
Page 72 Adding a switch to an encryption group FIGURE 37 Error Instructions dialog box 8. Review the post-configuration instructions, which you can copy to a clipboard or print for later. 9. Click Finish to exit the Configure Switch Encryption wizard. 10. Review “Understanding configuration status results”...
Page 73: Replacing An Encryption Engine In An Encryption Group
Replacing an encryption engine in an encryption group Replacing an encryption engine in an encryption group To replace an encryption engine in an encryption group with another encryption engine within the same DEK Cluster, complete the following steps. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays.
Page 74: Creating High Availability (Ha) Clusters
Creating high availability (HA) clusters Creating high availability (HA) clusters A high availability (HA) cluster is a group of exactly two encryption engines. One encryption engine can take over encryption and decryption tasks for the other encryption engine, if that member fails or becomes unreachable.
Page 75: Removing Engines From An Ha Cluster
Creating high availability (HA) clusters NOTE If you are creating a new HA cluster, a dialog box displays requesting a name for the new HA cluster. HA Cluster names can have up to 31 characters. Letters, digits, and underscores are allowed. Removing engines from an HA cluster Removing the last engine from an HA cluster also removes the HA cluster.
Page 76: Failback Option
Creating high availability (HA) clusters 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2. Select an encryption group from the Encryption Center Devices table, then select Group > HA Cluster from the menu task bar, or right-click an encryption group and select HA Cluster. The Encryption Group Properties dialog box displays, with the HA Clusters tab selected.
Page 77: Invoking Failback
Adding encryption targets Invoking failback To invoke failback to the restarted encryption engine from the Management application, complete the following steps. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2. Select an encryption group from the Encryption Center Devices table to which the encryption engine belongs, then click Group >...
Page 78 Adding encryption targets FIGURE 42 Encryption Targets dialog box 3. Click Add. The Configure Storage Encryption wizard dialog box displays. The dialog box explains the wizard’s purpose, which is to configure encryption for a storage device (target). FIGURE 43 Configure Storage Encryption wizard dialog box 4.
Page 79 Adding encryption targets FIGURE 44 Select Encryption Engine dialog box The list of engines depends on the scope being viewed. • If the Targets dialog box is showing all targets in an encryption group, the list includes all engines in the group. •...
Page 80 Adding encryption targets FIGURE 45 Select Target dialog box a. Select a target from the list. (The Target Port WWN and Target Node WWN fields contain all target information that displays when using the nsshow command.) You can also enter WWNs manually, for example, to specify a target that is not on the list.
Page 81 Adding encryption targets Select hosts using either of the following methods: a. Select a maximum of 1024 hosts from the Hosts in Fabric table, then click the right arrow to move the hosts to the Selected Hosts table. (The Port WWN column contains all target information that displays when using the nsshow command.) b.
Page 82 Adding encryption targets FIGURE 48 Confirmation dialog box 10. Click Next after you have verified the contents. Clicking Next creates the configuration. The Configuration Status dialog box displays. The dialog box lists the target and host that are configured in the target container, as well as the virtual targets (VT) and virtual initiators (VI). NOTE If you can view the VI/VT Port WWNs and VI/VT Node WWNs, the container has been successfully added to the switch.
Page 83 Adding encryption targets 11. Review any post-configuration instructions or messages, which you can copy to a clipboard or print for later. 12. Click Next. The Next Steps dialog box displays. Instructions for installing public key certificates for the encryption switch are displayed. FIGURE 50 Next Steps dialog box 13.
Page 84: Configuring Hosts For Encryption Targets
Configuring hosts for encryption targets Configuring hosts for encryption targets Use the Encryption Target Hosts dialog box to edit (add or remove) hosts for an encrypted target. NOTE Hosts are normally selected as part of the Configure Storage Encryption wizard but you can also edit hosts later using the Encryption Target Hosts dialog box.
Page 85: Adding Target Disk Luns For Encryption
Adding target disk LUNs for encryption Adding target disk LUNs for encryption You can add a new path to an existing disk LUN or add a new LUN and path by launching the Add New Path wizard. Take the following steps to launch the Add New Path wizard. Before You Begin Before you can add a target disk LUN for encryption, you must first configure the Storage Arrays.
Page 86 Adding target disk LUNs for encryption 4. Select the target port from the Target Port table. 5. Click Next. The Select Initiator Port dialog box displays. FIGURE 54 Select Initiator Port dialog box 6. Select the initiator port from the Initiator Port table. Click Next.
Page 87 Adding target disk LUNs for encryption FIGURE 55 Correcting an Encryption Mode mismatch 9. Select the LUN from LUN list. 10. Set the LUN state to Encrypted or Clear Text as required. If the LUN already has an existing key ID, the State field is automatically set to Encrypted. You can accept this state or change it as desired.
Page 88: Configuring Storage Arrays
Adding target tape LUNs for encryption Configuring Storage Arrays The Storage Array contains a list of storage ports that will be used later in the LUN centric view. You must assign storage ports from the same storage array for multi-path I/O purposes. On the LUN centric view, storage ports in the same storage array are used to get the associated CryptoTarget containers and initiators from the database.
Page 89 Adding target tape LUNs for encryption FIGURE 56 Encryption Targets dialog box 3. Select a target storage device from the Encryption Targets table, then click LUNs. The Encryption Target LUNs dialog box displays. FIGURE 57 Encryption Target Tape LUNs dialog box 4.
Page 90 Adding target tape LUNs for encryption FIGURE 58 Add Encryption Target Tape LUNs dialog box 5. Select a host from the Host list. Before you encrypt a LUN, you must select a host, then either discover LUNs that are visible to the virtual initiator representing the selected host, or enter a range of LUN numbers to be configured for the selected host.
Page 91: Tape Lun Write Early And Read Ahead
Tape LUN write early and read ahead Tape LUN write early and read ahead Tape LUN write early and read ahead feature uses tape pipelining and prefetch to speed serial access to tape. These features are particularly useful for performing backup and restore operations, especially over long distances.
Page 92 Tape LUN write early and read ahead FIGURE 60 Encryption Target Tape LUNs dialog box - Setting tape LUN read ahead and write early 4. In the EnableWriteEarlyAck and EnableRead/Ahead columns, set these features as desired for each LUN: • To enable write early for a specific tape LUN, check Enable Write Early Ack for that LUN.
Page 93: Tape Lun Statistics
Tape LUN statistics Tape LUN statistics This feature enables you to view and clear statistics for tape LUNs. These statistics include the number of compressed blocks, uncompressed blocks, compressed bytes and uncompressed bytes written to a tape LUN. The tape LUN statistics are cumulative and change as the host writes more data on tape. You can clear the statistics to monitor compression ratio of ongoing host I/O.
Page 94: Viewing And Clearing Tape Lun Statistics For A Container
Tape LUN statistics FIGURE 62 Tape LUN Statistics dialog box 5. To clear the tape LUN statistics for all member LUNs for the container, click Clear. 6. When prompted with a confirmation dialog box, click Yes. To update the tape LUN statistics, click Refresh. Viewing and clearing tape LUN statistics for a container To view or clear statistics for tape LUNs in a container, follow these steps: 1.
Page 95: Viewing And Clearing Statistics For Specific Tape Luns
Tape LUN statistics 3. Select the container of type Tape for which to display or clear statistics. 4. Click Statistics. The Tape LUN Statistics dialog box displays. The dialog box lists the statistics for all LUNs that are members of the selected tape container. FIGURE 64 Tape LUN Statistics dialog box 5.
Page 96 Tape LUN statistics FIGURE 65 Target Tape LUNs dialog box 4. Select the LUN or LUNs for which to display or clear statistics. 5. Click Statistics. The Tape LUN Statistics dialog box displays. The dialog box displays the statistic results based on the LUN or LUNs you selected.
Page 97: Re-Balancing The Encryption Engine
Re-balancing the encryption engine Re-balancing the encryption engine If you are currently using encryption and running Fabric OS 6.3.x or earlier, you are hosting tape and disk target containers on different encryption switches or blades. Beginning with Fabric OS 6.4, disk and tape target containers can be hosted on the same switch or blade. Hosting both disk and tape target containers on the same switch or blade might result in a drop in throughput, but it can reduce cost by reducing the number of switches or blades needed to support encrypted I/O in environments that use both disk and tape.
Page 98: Master Keys
Master keys Master keys When an opaque key vault is used, a master key is used to encrypt the data encryption keys. The master key status indicates whether a master key is used and whether it has been backed up. Encryption is not allowed until the master key has been backed up.
Page 99: Master Key Actions
Master keys Master key actions Master key actions are as follows: • Backup master key, which is enabled any time a master key exists. You can back up the master key to a file, to a key vault, or to a smart card. You can back up the master key multiple times to any of these media in case you forget the passphrase you originally used to back up the master key, or if multiple administrators each needs a passphrase for recovery.
Page 100 Master keys 4. Select Backup Master Key as the Master Key Action. The Master Key Backup dialog box displays, but only if the master key has already been generated. FIGURE 67 Backup Destination (to file) dialog box 5. Select File as the Backup Destination. 6.
Page 101: Saving A Master Key To A Key Vault
Master keys Saving a master key to a key vault Use the following procedure to save the master key to a key vault. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2. Select a group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click a group and select Security.
Page 102: Saving A Master Key To A Smart Card Set
Master keys Saving a master key to a smart card set A card reader must be attached to the SAN Management application PC to complete this procedure. Recovery cards can only be written once to back up a single master key. Each master key backup operation requires a new set of previously unused smart cards.
Page 103 Master keys FIGURE 69 Backup Destination (to smart cards) dialog box 4. Select A Recovery Set of Smart Cards as the Backup Destination. 5. Enter the recovery card set size. 6. Insert the first blank card and wait for the card serial number to appear. Run the additional cards needed for the set through the reader.
Page 104: Restoring A Master Key From A File
Master keys Restoring a master key from a file Use the following procedure to restore the master key from a file. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2. Select a group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click a group and select Security.
Page 105: Restoring A Master Key From A Key Vault
Master keys Restoring a master key from a key vault Use the following procedure to restore the master key from a key vault: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. 2. Select a group from the Encryption Center Devices table, then select Group > Properties from the menu task bar, or right-click a group and select Properties.
Page 106: Restoring A Master Key From A Smart Card Set
Master keys Restoring a master key from a smart card set A card reader must be attached to the SAN Management application PC to complete this procedure. Use the following procedure to restore the master key from a set of smart cards. 1.
Page 107: Creating A New Master Key
Master keys 10. Click OK. For related information, see the following topics: • “Active master key” on page 78 • “Alternate master key” on page 78 Creating a new master key Although it is generally not necessary to create a new master key, you might be required to create one due to the following: •...
Page 108: Viewing Master Key Ids
Zeroizing an encryption engine Viewing master key IDs When the master key has been backed up multiple times, you can use this feature to view the associated key IDs. To view master key IDs, follow these steps: 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays.
Page 109 Zeroizing an encryption engine • If the encryption engine was part of an HA cluster, targets fail over to the peer which assumes the encryption of all storage targets. Data flow will continue to be encrypted. • If there is no HA backup, host traffic to the target will fail as if the target has gone offline. The host will not have unencrypted access to the target.
Page 110: Using The Encryption Targets Dialog Box
Using the Encryption Targets dialog box 4. Click Yes to zeroize the encryption engine. • For an encryption blade, after the zeroize operation is successful, a message displays noting that the encryption blade will be powered off and powered on to make it operational again.
Page 111: Redirection Zones
Re-keying all disk LUNs manually The Encryption Targets dialog box enables you to launch a variety of wizards and other related dialog boxes. Redirection zones It is recommended that you configure the host and target in the same zone before you configure them for encryption.
Page 112 Re-keying all disk LUNs manually FIGURE 76 Selecting the Re-Key All operation If REPL support is enabled on the encryption group, a confirmation dialog box appears asking you if you want mirror LUNs to be rekeyed also. 3. Click Yes to includes mirror LUNs. Click No to exclude mirror LUNs. A critical warning message appears, requesting confirmation to proceed with the re-key operation.
Page 113: Viewing The Progress Of Manual Re-Key Operations
Re-keying all disk LUNs manually FIGURE 77 Pending manual re-key operations For related information, refer to the following topics: • “Re-keying all disk LUNs manually” on page 91 • “Viewing the progress of manual re-key operations” on page 93 Viewing the progress of manual re-key operations To monitor the progress of manual re-key operations, complete these steps: 1.
Page 114: Viewing Time Left For Auto Re-Key
Viewing time left for auto re-key Viewing time left for auto re-key You can view the time remaining until auto re-key is no longer active for a disk LUN. The information is expressed as the difference between the next re-key date and the current date and time, and is measured in days, hours, and minutes.
Page 115: Viewing And Editing Switch Encryption Properties
Viewing and editing switch encryption properties Viewing and editing switch encryption properties To view switch encryption properties, complete the following steps. 1. Select Configure > Encryption from the menu task bar. The Encryption Center dialog box displays. The dialog box shows the status of all encryption-related hardware and functions at a glance.
Page 116 Viewing and editing switch encryption properties • Switch Status - the health status of the switch. Possible values are Healthy, Marginal, Down, Unknown, Unmonitored, and Unreachable. • Switch Membership Status - the alert or informational message description which details the health status of the switch.
Page 117: Exporting The Public Key Certificate Signing Request (Csr) From Properties
Viewing and editing switch encryption properties • Re-Balance Recommended - A value of Yes or No indicating whether or not LUN re-balancing is recommended for an encryption engine that is hosting both disk and tape LUNs. • System Card - the current status of system card information for the encryption engine. (registered or not registered).
Page 118: Viewing And Editing Group Properties
Viewing and editing group properties 2. Select an encryption engine from the Encryption Center Devices table, then select Engine > Properties from the menu task bar, or right-click an encryption engine and select Properties. The Encryption Properties dialog box displays. 3.
Page 119: General Tab
Viewing and editing group properties • “HA Clusters tab” on page 104 • “Tape Pools tab” on page 105 • “Engine Operations tab” on page 107 General tab The General tab is viewed from the Encryption Group Properties dialog box. To access the General tab, select a group from the Encryption Center Devices table, then select Group >...
Page 120: Members Tab
Viewing and editing group properties • Primary key vault certificate - the details of the primary vault certificate; for example, version and signature information. • Backup key vault certificate - the details of the backup vault certificate; for example, version and signature information.
Page 121: Consequences Of Removing An Encryption Switch
Viewing and editing group properties • OK - the member switch is responding to the group leader switch. • Not Available - the group leader is not a managed switch, so connection statuses are not being collected from the group leader. Members tab Remove button You can click the Remove button to remove a selected switch or an encryption group from the encryption group table.
Page 122 Viewing and editing group properties FIGURE 84 Removal of switch warning A warning message displays when you attempt to remove an encryption group. Click Yes to proceed. FIGURE 85 Removal of switch in encryption group warning Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 123: Security Tab
Viewing and editing group properties Security tab The Security tab is viewed from the Encryption Group Properties dialog box. To access the Security tab, select a group from the Encryption Center Devices table, then select Group > Security from the menu task bar, or right-click a group and select Security.
Page 124: Ha Clusters Tab
Viewing and editing group properties For related information, see the following topics: • “Master keys” on page 78 • “Smart card usage” on page 16 HA Clusters tab The HA Clusters tab allows you to create and delete HA clusters, add encryption engines to and remove encryption engines from HA clusters, and failback an engine.
Page 125: Tape Pools Tab
Viewing and editing group properties Tape Pools tab Tape pools are managed from the Tape Pools tab. From the Tape Pools tab, you can add, modify, and remove tape pools. • To add a tape pool, click Add, then complete the Add Tape Pool dialog box. •...
Page 126 Viewing and editing group properties Encryption switches and encryption blades support tape encryption at the tape pool level (for most backup applications) and at the LUN (tape drive) level. Since Tape Pool policies override the LUN (tape drive) policies, the LUN pool policies are used only if no tape pools exist, or if the tape media/volume does not belong to any configured tape pools.
Page 127: Engine Operations Tab
Viewing and editing group properties 3. Based on your selection, enter a name or number for the tape pool. If you selected Number as the Tape Pool Label Type, the name must match the tape pool label or tape ID/number that is configured on the tape backup/restore application.
Page 128 Viewing and editing group properties FIGURE 91 Encryption Group Properties Dialog Box - Engine Operations Tab NOTE You cannot replace an encryption engine if it is part of an HA Cluster. For information about HA Clusters, refer to “HA Clusters tab” on page 104.
Page 129: Encryption-Related Acronyms In Log Messages
Encryption-related acronyms in log messages Encryption-related acronyms in log messages Fabric OS log messages related to encryption components and features may have acronyms embedded that require interpretation. Table 3 lists some of those acronyms. TABLE 3 Encryption acronyms Acronym Name Encryption Engine Encryption Group High Availability Cluster...
Page 130 Encryption-related acronyms in log messages Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 131: Configuring Brocade Encryption Using The Cli
Chapter Configuring Brocade Encryption Using the CLI In this chapter • Overview ........... . . 112 •...
Page 132: Overview
Overview Overview This chapter explains how to use the command line interface (CLI) to configure a Brocade Encryption Switch, or an FS8-18 Encryption blade in a DCX or DCX-4S to perform data encryption. This chapter assumes that the basic setup and configuration of the Brocade Encryption Switch (BES), DCX, or DCX-4S has been done as part of the initial hardware installation, including setting the management port IP address.
Page 133: Command Rbac Permissions And Ad Types
Command RBAC permissions and AD types Command RBAC permissions and AD types Two RBAC roles are permitted to perform Encryption operations. • Admin and SecurityAdmin Users authenticated with the Admin and SecurityAdmin RBAC roles may perform cryptographic functions assigned to the FIPS Crypto Officer, including the following: •...
Page 134 Command RBAC permissions and AD types TABLE 4 Encryption command RBAC availability and admin domain type (Continued) Command name User Admin Operator Switch Zone Fabric Basic Security Admin Domain Admin Admin Admin Switch Admin Admin delete --container Disallowed delete --encgroup Disallowed delete --file Disallowed...
Page 135: Cryptocfg Help Command Output
Cryptocfg Help command output TABLE 4 Encryption command RBAC availability and admin domain type (Continued) Command name User Admin Operator Switch Zone Fabric Basic Security Admin Domain Admin Admin Admin Switch Admin Admin recovermasterkey Disallowed regEE Disallowed reggroupleader Disallowed regkeyvault regmembernode removehaclustermember removeinitiator...
Page 136: Management Lan Configuration
Management LAN configuration --initnode: Initialize the node for configuration of encryption options. --initEE [<slotnumber>]: Initialize the specified encryption engine. --regEE [<slotnumber>]: Register a previously initialized encryption blade. --reg -membernode <member node WWN> <member node certfile> <IP addr>: Register a member node with the system. (output truncated) Management LAN configuration Each encryption switch has one GbE management port.
Page 137: Special Consideration For Blades
Configuring cluster links Special consideration for blades HA clusters of FS8-18 blades should not include blades in the same DCX chassis. For FS8-18 blades, the slot number must also be included in the ipaddrset command, for example: switch:admin> ipaddrset -slot 7 -eth0 --add 10.32.33.34/23 switch:admin>...
Page 138 Configuring cluster links Node is a group leader node 1. Log in to the group leader as Admin or SecurityAdmin. 2. Reboot the encryption switch/DCX (both active and standby central processors) so the existing Group Leader fails over and one of the member nodes assumes the role of Group Leader. a.
Page 139: Steps For Connecting To An Skm Or Eskm Appliance
Steps for connecting to an SKM or ESKM appliance Steps for connecting to an SKM or ESKM appliance The following configuration steps are performed from the SKM/ESKM management web console, which can be accessed from any web browser with Internet access to the SKM/ESKM appliance. The same procedure is used for creating both SKM and ESKM encryption groups.
Page 140: Setting Up The Local Certificate Authority (Ca)
Steps for connecting to an SKM or ESKM appliance The Brocade user name and password are now configured on SKM/ESKM. NOTE Fabric OS v6.2.x uses brcduser1 as a standard user name when creating a Brocade group on SKM/ESKM. If you downgrade to version 6.2.x, the user name is overwritten to brcduser1, and the Brocade group user name must be changed to brcduser1.
Page 141: Downloading The Local Ca Certificate
Steps for connecting to an SKM or ESKM appliance The new local CA displays under Local Certificate Authority List (Figure 92). FIGURE 92 Creating an HP SKM/ESKM Local CA 5. Under Certificates & CAs, select Trusted CA Lists to display the Trusted Certificate Authority List Profiles.
Page 142: Creating And Installing The Skm Or Eskm Server Certificate
Steps for connecting to an SKM or ESKM appliance Creating and installing the SKM or ESKM server certificate To create the SKM/ESKM server certificate, complete the following steps: 1. Click the Security tab. 2. Under Certificates and CAs, select Certificates. 3.
Page 143: Server
Steps for connecting to an SKM or ESKM appliance 18. Click Install Certificate. The Certificate Installation window displays. 19. Paste the signed certificate data you copied under Certificate Response and click Save. The status of the server certificate should change from Request Pending to Active. Enabling SSL on the Key Management System (KMS) Server The KMS Server provides the interface to the client.
Page 144: Creating An Skm Or Eskm High Availability Cluster
Steps for connecting to an SKM or ESKM appliance 5. Configure the KMS Server Settings. Ensure that the port and connection timeout settings are 9000 and 3600, respectively. For Server Certificate, select the name of the certificate you created in “Creating and installing the SKM or ESKM server certificate”...
Page 145: Adding Skm Or Eskm Appliances To The Cluster
Steps for connecting to an SKM or ESKM appliance 4. Copy the certificate request, beginning with and ending ---BEGIN CERTIFICATE REQUEST--- with . Be careful not to include any extra characters. ---END CERTIFICATE REQUEST--- Adding SKM or ESKM appliances to the cluster If you are adding an appliance to an existing cluster, select Cluster Settings, click Download Cluster Key, and save the key to a convenient location, such as your computer's desktop.
Page 146: Initializing The Brocade Encryption Engines
Steps for connecting to an SKM or ESKM appliance NOTE An SKM/ESKM cluster may have many members, but the Brocade encryption products support only two as primary and secondary key vaults. Initializing the Brocade encryption engines You must perform a series of encryption engine initialization steps on every Brocade encryption node (switch or blade) that is expected to perform encryption within the fabric.
Page 147: Signing The Brocade Encryption Node Kac Certificates
Steps for connecting to an SKM or ESKM appliance 6. Initialize the encryption engine using the cryptocfg --initEE command. Provide a slot number if the encryption engine is a blade. This step generates critical security parameters (CSPs) and certificates in the CryptoModule’s security processor (SP). The CP and the SP perform a certificate exchange to register respective authorization data.
Page 148: Leader
Steps for connecting to an SKM or ESKM appliance Upon success, you are presented with the option of downloading the signed certificate. 13. Download the signed certificate to your local system as signed_kac_skm_cert.pem. 14. Import the signed certificate from its location, or from a USB storage device. SecurityAdmin:switch>cryptocfg --import -scp signed_kac_skm_cert.pem \ 192.168.38.245 mylogin /tmp/certs/kac_skm_cert.pem Password:...
Page 149 Steps for connecting to an SKM or ESKM appliance The switch on which you create the encryption group becomes the designated group leader. Once you have created an encryption group, all group-wide configurations, including key vault configuration, adding member nodes, configuring failover policy settings, and setting up storage devices, as well as all encryption management operations, are performed on the group leader.
Page 150: Registering The Skm Or Eskm Brocade Group User Name And Password
Steps for connecting to an SKM or ESKM appliance Client SDK Version: 4.8.2.000017 Client Username: brcduser1 Client Usergroup: brocade Connection Timeout: 10 seconds Response Timeout: 10 seconds Connection Idle Timeout: Key Vault configuration and connectivity checks successful, ready for key operations.
Page 151: Skm Or Eskm Key Vault High Availability Deployment
Steps for connecting to an SKM or ESKM appliance • Different user names and passwords can never be used within the same encryption group, but each encryption group may have its own user name and password. • If you change the user name and password using the -KAClogin option, the keys created by the previous user become inaccessible.
Page 152: Adding A Member Node To An Encryption Group
Steps for connecting to an SKM or ESKM appliance Tape LUN support • DEK Creation - The DEK is created and archived to the SKM/ESKM cluster using the cluster’s virtual IP address. The DEK is synchronized with other SKMs/ESKMs in the cluster. Upon successful archival of the DEK to the SKM/ESKM cluster, the DEK can be used for encryption of the tape LUN.
Page 153 Steps for connecting to an SKM or ESKM appliance CAUTION After adding the member node to the encryption group, you should not use the cryptocfg --zeroizeEE command on that node. Doing so removes critical information such as CP certificates from the node and makes it necessary to reinitialize the node and export the new CP certificates and KAC certificates to the group leader and the key vault.
Page 154 Steps for connecting to an SKM or ESKM appliance NOTE If the maximum number of certificates is exceeded, the following message is displayed. Maximum number of certificates exceeded. Delete an unused certificate with the ‘cryptocfg –delete –file’ command and then try again 6.
Page 155: Generating And Backing Up The Master Key
Generating and backing up the master key Role: MemberNode IP Address: 10.32.244.60 Certificate: enc1_cpcert.pem Current Master Key State: Not configured Current Master KeyID: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 Alternate Master Key State:Not configured Alternate Master KeyID: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 EE Slot: SP state: Unknown State Current Master KeyID: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 Alternate Master KeyID: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00...
Page 156 Generating and backing up the master key Total Number of defined nodes:2 Group Leader Node Name: 10:00:00:05:1e:41:9a:7e Encryption Group state: CLUSTER_STATE_CONVERGED Node Name: 10:00:00:05:1e:41:9a:7e (current node) State: DEF_NODE_STATE_DISCOVERED Role: GroupLeader IP Address: 10.32.244.71 Certificate: GL_cpcert.pem Current Master Key State: Configured Current Master KeyID: 8f:88:45:32:8e:bf:eb:44:c4:bc:aa:2a:c1:69:94:2 Alternate Master Key State: Not configured...
Page 157: High Availability Cluster Configuration
High availability cluster configuration No HA cluster membership Node Name: 10:00:00:05:1e:39:14:00 State: DEF_NODE_STATE_DISCOVERED Role: MemberNode IP Address: 10.32.244.60 Certificate: enc1_cpcert.pem Current Master Key State: Not configured Current Master KeyID: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 Alternate Master Key State:Not configured Alternate Master KeyID: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 EE Slot: SP state: Unknown State Current Master KeyID:...
Page 158: Creating An Ha Cluster
High availability cluster configuration • It is recommended that the HA cluster configuration be completed before you configure storage devices for encryption. • It is mandatory that the two encryption engines in the HA cluster belong to two different nodes for true redundancy.
Page 159: Adding An Encryption Engine To An Ha Cluster
High availability cluster configuration Adding an encryption engine to an HA cluster 1. Log in to the group leader as Admin or SecurityAdmin. 2. Enter the cryptocfg --add -haclustemember command. Specify the HA cluster name and the encryption engine node WWN. Provide a slot number if the encryption engine is a blade. The following example adds a Brocade FS8-18 in slot 5 to the HA cluster HAC2.
Page 160: Re-Exporting A Master Key
Re-exporting a master key Policy Configuration Examples The following examples illustrate the setting of group-wide policy parameters. To set the failback mode to manual failback: SecurityAdmin:switch>cryptocfg --set -failbackmode manual Set failback policy status: Operation Succeeded. To set the Heartbeat misses value to 3: SecurityAdmin:switch>cryptocfg --set -hbmisses 3 Set heartbeat miss status: Operation Succeeded.
Page 161: Exporting An Additional Key Id
Re-exporting a master key The following example lists the exported master key IDs for a given master key ID: cryptocfg --show –mkexported_keyids e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:92 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:92 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:93 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:94 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:95 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:96 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:97 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:98 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:99 e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:9a e3:ae:aa:89:ec:12:0c:04:29:61:9c:99:44:a3:9b:9b Operation succeeded. The exported key ID is displayed with the master key ID, as shown in the examples to follow: Example: Initial master key export cryptocfg --exportmasterkey Enter passphrase:...
Page 162: Viewing The Master Key Ids
Re-exporting a master key Viewing the master key IDs command shows the actual master key IDs, along with the new master key IDs. show localEE Also shown are all exported master key IDs associated with a given (actual) master key. NOTE You will need to remember the exported master key ID and passphrase you used while exporting the master key ID.
Page 163: Enabling The Encryption Engine
Enabling the encryption engine 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 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.
Page 164: Zoning Considerations
Zoning considerations 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 No HA cluster membership EE Attributes: Media Type DISK EE Slot: 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 No HA cluster membership EE Attributes: Media Type DISK EE Slot: SP state:...
Page 165: Frame Redirection Zoning
Zoning considerations 2. From any configured primary FCS switch, change the default zoning setting to No Access. switch:admin> defzone --noaccess switch:admin> cfgfsave The change will be applied within the entire fabric. Frame redirection zoning Name Server-based frame redirection enables the Brocade Encryption Switch or blade to be deployed transparently to hosts and targets in the fabric.
Page 166 Zoning considerations Permanent Port Name: 10:00:00:00:c9:2b:c9:3a Port Index: 6 Share Area: No Device Shared in Other AD: No Redirect: No The Local Name Server has 1 entry } The nsshow command shows all devices on the switch, and the output can be lengthy. To retrieve only the initiator PWWN, do a pattern search of the output based on the initiator Port ID (a hex number).
Page 167: Cryptotarget Container Configuration
CryptoTarget container configuration Create a zone that includes the initiator and a LUN target. Enter the zonecreate command followed by a zone name, the initiator PWWN and the target PWWN. FabricAdmin:switch>zonecreate itzone, "10:00:00:00:c9:2b:c9:3a; \ 20:0c:00:06:2b:0f:72:6d" 8. Create a zone configuration that includes the zone you created in step 4. Enter the cfgcreate command followed by a configuration name and the zone member name.
Page 168 CryptoTarget container configuration FIGURE 94 Relationship between initiator, virtual target, virtual initiator and target CAUTION When configuring a LUN with multiple paths, there is a considerable risk of ending up with potentially catastrophic scenarios where different policies exist for each path of the LUN, or a situation where one path ends up being exposed through the encryption switch and another path has direct access to the device from a host outside the secured realm of the encryption platform.
Page 169: Targets
CryptoTarget container configuration To determine if rebalancing is recommended for an encryption engine, check the encryption engine properties. Beginning with Fabric OS v6.4, a field is added that indicates whether or not re-balancing is recommended You may be prompted to rebalance during the following operations: •...
Page 170 CryptoTarget container configuration • The CryptoTarget container name can be up to 31 characters in length and may include any alphanumeric characters, hyphens, and underscore characters. • You may add initiators at this point or after you create the container. The following example creates a disk container named my_disk_tgt1.
Page 171: Removing An Initiator From A Cryptotarget Container
CryptoTarget container configuration cfg: itcfg itzone cfg: r_e_d_i_r_c__fg red_1109_brcd200c00062b0f726d200200051e414e1d; red_______base zone: itzone 10:00:00:00:c9:2b:c9:3a; 20:0c:00:06:2b:0f:72:6d zone: red_1109_brcd200c00062b0f726d200200051e414e1d 10:00:00:00:c9:2b:c9:3a; 20:0c:00:06:2b:0f:72:6d; 20:02:00:05:1e:41:4e:1d; 20:00:00:05:1e:41:4e:1d zone: red_______base 00:00:00:00:00:00:00:01; 00:00:00:00:00:00:00:02; 00:00:00:00:00:00:00:03; 00:00:00:00:00:00:00:04 Effective configuration: cfg: itcfg zone: itzone 10:00:00:00:c9:2b:c9:3a 20:0c:00:06:2b:0f:72:6d NOTE You may view the frame redirection zone with the cfgshow command, but you cannot use the zone for any other applications that use frame redirection.
Page 172: Deleting A Cryptotarget Container
CryptoTarget container configuration switch and another path has direct access to the device from a host outside the protected realm of the encryption platform. Refer to the section “Configuring a multi-path Crypto LUN” page 166 for more information. Deleting a CryptoTarget container You may delete a CryptoTarget container to remove the target port from a given encryption switch or blade.
Page 173: Moving A Cryptotarget Container
Crypto LUN configuration Moving a CryptoTarget container You can move a CryptoTarget container from one encryption engine to another. The encryption engines must be part of the same fabric and the same encryption group, and the encryption engines must be online for this operation to succeed. This operation permanently transfers the encryption engine association of a given CryptoTarget container from an existing encryption engine to an alternate encryption engine.
Page 174: Discovering A Lun
Crypto LUN configuration you are configuring multi-path LUNs as part of a HA cluster or DEK cluster or as a stand-alone LUN accessed by multiple hosts, follow the instructions described in the section “Configuring a multi-path Crypto LUN” on page 166. Discovering a LUN When adding a LUN to a CryptoTarget container, you must specify a LUN Number.
Page 175 Crypto LUN configuration NOTE LUN configurations and modifications must be committed to take effect. There is an upper limit of 25 on the number of LUNs you can add or modify in a single commit operation. Attempts to commit a configuration that exceeds this maximum will fail. Note that there is also a five second delay before the commit operation takes effect.
Page 176: Crypto Lun Parameters And Policies
Crypto LUN configuration Number of host(s): 1 Configuration status: committed Host: 10:00:00:00:c9:2b:c9:3a 20:00:00:00:c9:2b:c9:3a VI: 20:02:00:05:1e:41:4e:1d 20:03:00:05:1e:41:4e:1d LUN number: 0x0 LUN type: disk LUN status: 0 Encryption mode: encrypt Encryption format: native Encrypt existing data: enabled Rekey: disabled Key ID: not available Operation Succeeded Crypto LUN parameters and policies Table 6...
Page 177 Crypto LUN configuration TABLE 6 LUN parameters and policies (Continued) Policy name Command parameters Description Encryption -encryption_format native Sets the encryption format. Valid values are: • format Native - The LUN is encrypted or decrypted using the Brocade Disk LUN: yes encryption format (metadata format and algorithm).
Page 178: Configuring A Tape Lun
Crypto LUN configuration Configuring a tape LUN This example shows how to configure a tape storage device. The basic setup procedure is the same as for disk devices. Only a subset of configuration options and policy settings are available for tape LUNs.
Page 179: Removing A Lun From A Cryptotarget Container
Crypto LUN configuration Commit the configuration. FabricAdmin:switch>cryptocfg --commit Operation Succeeded d. Display the LUN configuration. FabricAdmin:switch>cryptocfg --show -LUN my_tape_tgt 0x0 \ 10:00:00:00:c9:2b:c9:3a -cfg EE node: 10:00:00:05:1e:41:9a:7e EE slot: Target: 20:0c:00:06:2b:0f:72:6d 20:00:00:06:2b:0f:72:6d 20:00:00:05:1e:41:4e:1d 20:01:00:05:1e:41:4e:1d Number of host(s): Configuration status: committed Host: 21:00:00:e0:8b:89:9c:d5 20:00:00:e0:8b:89:9c:d5 10:00:00:00:c9:2b:c9:3a 20:03:00:05:1e:41:4e:31 LUN number:...
Page 180: Modifying Crypto Lun Parameters
Crypto LUN configuration has direct access to the device from a host outside the protected realm of the encryption platform. Refer to the section “Configuring a multi-path Crypto LUN” on page 166 for more information. Modifying Crypto LUN parameters You can modify one or more policies of an existing Crypto LUN with the cryptocfg modify -LUN command.
Page 181: Lun Modification Considerations
Impact of tape LUN configuration changes LUN modification considerations Make sure you understand the ramifications of modifying LUN policy parameters (such as encrypt/cleartext) for LUNs that are online and already being utilized. The following restrictions apply when modifying LUN policy parameters for disk LUNs: •...
Page 182: Force-Enabling A Disabled Disk Lun For Encryption
Tape pool configuration Force-enabling a disabled disk LUN for encryption You can force a disk LUN to become enabled for encryption when encryption is disabled on the LUN. A LUN may become disabled for various reasons, such as a change in policy from encrypt to cleartext when encrypted data (and metadata) exist on the LUN, a conflict between LUN policy and LUN state, or a missing DEK in the key vault.
Page 183 Tape pool configuration The following rules apply when creating a tape pool label: • Tape pool names are limited in length to 63 characters. They may contain alphanumeric characters, and in some cases, underscores (_) and dashes (-). • Tape pool numbers are limited to eight hex digits. Valid characters for tape pool numbers are 0-9, A-F, and a-f.
Page 184: Creating A Tape Pool
Tape pool configuration NetBackup labeling NetBackup uses numbers to label tape pools. If you are using NetBackup as your application, follow these steps to obtain the tape pool number. 1. Log into the NetBackup application Windows host. 2. Select Start > run, and type cmd in the dialog box. 3.
Page 185: Deleting A Tape Pool
Tape pool configuration 4. Display the configuration. Enter the cryptocfg show -tapepool command followed by the tape pool number or label and the -cfg parameter. FabricAdmin:switch>cryptocfg --show -tapepool -label my_tapepool -stat Number of tapepool session(s): Tapepool 1: Tapepool label: my_tapepool Encryption mode: encrypted Encryption format:...
Page 186: Impact Of Tape Pool Configuration Changes
Configuring a multi-path Crypto LUN Impact of tape pool configuration changes Tape pool-level policies overrule policy configurations at the LUN level, when no policies are configured at the tape pool level. The following restrictions apply when modifying tape pool-level configuration parameters: •...
Page 187 Configuring a multi-path Crypto LUN FIGURE 95 A LUN accessible through multiple paths The following steps may be used to configure multiple path access to the LUN in Figure 1. Create zoning between host port 1 and target port 1. Refer to the section “Creating an initiator - target zone”...
Page 188 Configuring a multi-path Crypto LUN Add host port 1 to the container CTC1. FabricAdmin:switch>cryptocfg --add -initiator <CTC1> <Host Port1 WWN> \ <Host NWWN> d. Add host port 2 to the container CTC2. FabricAdmin:switch>cryptocfg --add -initiator <CTC2> <Host Port2 WWN> <Host NWWN> e.
Page 189: First-Time Encryption
First-time encryption NOTE The LUN policies must be exactly the same on both CTC1 and CTC2. Failure to do so results in undefined behavior and data corruption. 6. Validate the LUN policies for all containers. Display the LUN configuration for ALL CryptoTarget containers to confirm that the LUN policy settings are the same for all CryptoTarget containers.
Page 190: Resource Allocation
Data re-keying Resource allocation System resources for first time encryption sessions are shared with re-key sessions. There is an upper limit of 10 sessions with two concurrent sessions per target. Refer to the re-key “Resource allocation” on page 170 section for details. First time encryption modes First-time encryption can be performed under the following conditions: •...
Page 191: Resource Allocation
Data re-keying Re-keying is only applicable to disk array LUNs or fixed block devices. There is no re-keying support for tape media. If there is a need to re-encrypt encrypted tape contents with a new key, the process is equivalent to restoring the data from tape backup. You decrypt the data with the old DEK and subsequently back up the tape contents to tape storage, which will have the effect of encrypting the data with the new DEK.
Page 192: Initiating A Manual Re-Key Session
Data re-keying NOTE For a scheduled re-keying session to proceed, all encryption engines in a given HA cluster, DEK cluster, or encryption group must be online, and I/O sync links must be configured. Refer to the section “Management LAN configuration” on page 116 for more information.
Page 193: Suspension And Resumption Of Re-Keying Operations
Data re-keying 5. Check the status of the re-keying session. FabricAdmin:switch> cryptocfg --show -rekey -all Number of rekey session(s): Container name: cx320-157A EE node: 10:00:00:05:1e:40:4c:00 EE slot: Target: 50:06:01:60:30:20:db:34 50:06:01:60:b0:20:db:34 Target PID: 022900 20:00:00:05:1e:53:8d:cd 20:01:00:05:1e:53:8d:cd VT PID: 06c001 Host: 10:00:00:00:c9:56:e4:7b 20:00:00:00:c9:56:e4:7b Host PID: 066000 20:02:00:05:1e:53:8d:cd 20:03:00:05:1e:53:8d:cd...
Page 194 Data re-keying 1. Enter the cryptocfg --resume_rekey command, followed by the CryptoTarget container name, the LUN number and the initiator PWWN. FabricAdmin:switch>cryptocfg --resume_rekey my_disk_tgt 0x0 \ 10:00:00:05:1e:53:37:99 Operation Succeeded 2. Check the status of the resumed re-key session. FabricAdmin:switch> cryptocfg --show -rekey -all •...
Page 195: In This Chapter
Chapter Deployment Scenarios In this chapter • Single encryption switch, two paths from host to target....176 • Single fabric deployment - HA cluster ......177 •...
Page 196: Single Encryption Switch, Two Paths From Host To Target
Single encryption switch, two paths from host to target Single encryption switch, two paths from host to target Figure 96 shows a basic configuration with a single encryption switch providing encryption between one host and one storage device over two the following two paths: •...
Page 197: Single Fabric Deployment - Ha Cluster
Single fabric deployment - HA cluster Single fabric deployment - HA cluster Figure 97 shows an encryption deployment in a single fabric with dual core directors and several host and target edge switches in a highly redundant core-edge topology. Key Management Management Management Appliance...
Page 198: Single Fabric Deployment - Dek Cluster
Single fabric deployment - DEK cluster Figure 97, the two encryption switches provide a redundant encryption path to the target devices. The encryption switches are interconnected through a dedicated cluster LAN. The Ge1 and Ge0 gigabit Ethernet ports on each of these switches are attached to this LAN. This LAN connection provides the communication needed to distribute and synchronize configuration information, and enable the two switches to act as a high availability (HA) cluster, providing automatic failover if one of the switches fails, or is taken out of service.
Page 199: Dual Fabric Deployment - Ha And Dek Cluster
Dual fabric deployment - HA and DEK cluster Figure 98, two encryption switches are required, one for each target path. The path from host port 1 to target port 1 is defined in a CryptoTarget container on one encryption switch, and the path from host port 2 to target port 2 is defined in a CryptoTarget container on the other encryption switch.
Page 200: Multiple Paths, One Dek Cluster, And Two Ha Clusters
Multiple paths, one DEK cluster, and two HA clusters failover for the encryption path between the host and target in fabric 1. Encryption switches 2 and 4 act as a high availability cluster in fabric 2, providing automatic failover for the encryption path between the host and target in fabric 2.
Page 201 Multiple paths, one DEK cluster, and two HA clusters The configuration details shown in Figure 100 are as follows: • There are two fabrics. • There are four paths to the target device, two paths in each fabric. • There are two host ports, one in each fabric. •...
Page 202: Multiple Paths, Dek Cluster, No Ha Cluster
Multiple paths, DEK cluster, no HA cluster Multiple paths, DEK cluster, no HA cluster Figure 101 shows a configuration with a DEK cluster with multiple paths to the same target device. There is one encryption switch in each fabric. Management Network Management Link Management Link...
Page 203: Deployment In Fibre Channel Routed Fabrics
Deployment in Fibre Channel routed fabrics Deployment in Fibre Channel routed fabrics In this deployment, the encryption switch may be connected as part of the backbone fabric to another switch or blade that provides the EX_port connections (Figure 102), or it may form the backbone fabric and directly provide the EX_port connections (Figure 103).
Page 204 Deployment in Fibre Channel routed fabrics The following is a summary of steps for creating and enabling the frame redirection zoning features in the FCR configuration (backbone to edge). • The encryption device creates the frame redirection zone automatically consisting of host, target, virtual target, and virtual initiator in the backbone fabric when the target and host are configured on the encryption device.
Page 205: Deployment As Part Of An Edge Fabric
Deployment as part of an edge fabric Deployment as part of an edge fabric In this deployment, the encryption switch is connected to either the host or target edge fabric. The backbone fabric may contain a 7500 extension switch or FR4-18i blade in a 48000 director, DCX, or DCX-4S, or an FCR-capable switch or blade.
Page 206: Deployment With Fcip Extension Switches
Deployment with FCIP extension switches Deployment with FCIP extension switches Encryption switches may be deployed in configurations that use extension switches or extension blades within a DCX, DCX-4S or 48000 chassis to enable long distance connections. Figure 105 shows an encryption switch deployment in a Fibre Channel over IP (FCIP) configuration. Refer to the Fabric OS Administrator’s Guide for information about creating FCIP configurations.
Page 207: Vmware Esx Server Deployments
VMware ESX server deployments VMware ESX server deployments VMware ESX servers may host multiple guest operating systems. A guest operating system may have its own physical HBA port connection, or it may use a virtual port and share a physical HBA port with other guest operating systems.
Page 208 VMware ESX server deployments Figure 107 shows a VMware ESX server with two guest operating systems where two guests access a fabric over a shared port. To enable this, both guests are assigned a virtual port. There are two paths to a target storage device: •...
Page 209: Best Practices And Special Topics
Chapter Best Practices and Special Topics In this chapter • Firmware download considerations ....... 190 •...
Page 210: Firmware Download Considerations
Firmware download considerations Firmware download considerations The encryption engine and the control processor or blade processor are reset after a firmware upgrade. Disruption of encryption I/O can be avoided if an HA cluster is configured. If encryption engines are configured in an HA cluster, perform firmware upgrades one encryption engine at a time so that the partner switch in the HA cluster can take over I/O by failover during firmware upgrade.
Page 211: Data-At-Rest Encryption Support For Ibm Svc Luns Configuration
Firmware download considerations • In the case of active/active arrays, upgrade order of nodes does not matter, but you still must upgrade one node at a time. The Host MPIO ensures that I/O fails over and fails back from one active path to another active path during this firmware upgrade process.
Page 212: Configuration Upload And Download Considerations
Configuration upload and download considerations cryptocfg --disableEE 3. Make sure that these Crypto Target Containers and LUNs actually failover to node 2 (BES2) in the HA cluster. Check for all LUNs in encryption enabled state on node 2 (BES2). This ensures that I/O also fails over to node 2 (BES2) and continues during this process.
Page 213: Node
Configuration upload and download considerations Configuration upload at an encryption group member node A configuration upload at an individual encryption group member node contains the following: • The local switch configuration. • Encryption group-related configuration. • Encryption group-wide configuration of Crypto Targets, disk and tape LUNs, tape pools, HA clusters, security, and key vaults.
Page 214: Configuration Download At The Encryption Group Leader
Configuration upload and download considerations Configuration download at the encryption group leader The configuration download contains the encryption group-wide configuration information about Crypto Targets, disk and tape LUNs, tape pools, HA clusters, security, and key vaults. The encryption group leader first applies the encryption group-wide configuration information to the local configuration database and then distributes the configuration to all members in the encryption group.
Page 215: Hp-Ux Considerations
HP-UX considerations 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.
Page 216: Tape Metadata
Tape metadata Tape metadata One kilobyte of metadata is added per tape block for both the native Brocade format and DF-compatible formats. Tape block size (as configured by host) is modified by the encryption device to accommodate 1K metadata per block. A given tape can have a mix of compressed and uncompressed blocks.
Page 217: Tape Block Zero Handling
Tape block zero handling Tape pool configuration is used only when labeling of tape media is done on the first write for the tape media. After tape labeling is done and metadata written, the tape pool configuration is no longer used. Tape pool configuration is not required for restoring data from the encrypted tape belonging to the tape pool, because the key ID is present in the metadata.
Page 218: Redirection Zones
Redirection zones • Before committing CryptoTarget container or LUN configurations or modifications on an encryption switch or FS8-18 blade, make sure that there are no outstanding zoning transactions in the switch or fabric. If there is an outstanding zoning transaction, the commit operation will fail and result in disabling the LUN.
Page 219: Deployment With Admin Domains (Ad)
Deployment with Admin Domains (AD) Deployment with Admin Domains (AD) Virtual devices created by the encryption device do not support the AD feature in this release. All virtual devices are part of AD0 and AD255. Targets for which virtual targets are created and hosts for which virtual initiators are created must also be in AD0 and AD255.
Page 220: Pid Failover
PID failover PID failover Virtual device PIDs do not persist upon failover within a single fabric HA cluster. Upon failover, the virtual device is s assigned a different PID on the standby encryption switch or blade. Some operating systems view the PID change as an indication of path failure, and will switch over to redundant path in another fabric.
Page 221: Allow Re-Key To Complete Before Deleting A Container
KAC certificate registration expiry Allow re-key to complete before deleting a container Do not delete a crypto container while re-key is in session or if re-key is not completed. If you want to delete a container, use the command cryptocfg show -rekey –all to display the status of re-key sessions.
Page 222: Changing Ip Addresses In Encryption Groups
Changing IP addresses in encryption groups NOTE In the event that the signed KAC certificate must be re-registered, you will need to log in to the key vault web interface and upload the new signed KAC certificate for the corresponding Brocade Encryption Switch Identity.
Page 223 Recommendations for Initiator Fan-Ins An encryption engine has 6 distinct encryption blocks with 4 ports each port operating at 4Gbps. The architecture of the encryption blocks provides the potential for an aggregate 96 Gbps of full duplex encryption bandwidth, if the performance license is installed. Figure 108 shows the encryption blocks within an encryption engine, and the host initiator to target port fan-ins.
Page 224: Best Practices For Host Clusters In An Encryption Environment
Best practices for host clusters in an encryption environment Best practices for host clusters in an encryption environment When host clusters are deployed in a encryption environment, please follow these recommendations: • If two encryption engines are part of an HA cluster, configure the host/target pair so they have different paths from both encryption engines.
Page 225: Maintenance And Troubleshooting
Chapter Maintenance and Troubleshooting In this chapter • Encryption group and HA cluster maintenance ..... . 205 • Encryption group merge and split use cases......213 •...
Page 226: Removing A Member Node From An Encryption Group
Encryption group and HA cluster maintenance Removing a member node from an encryption group This procedure permanently removes a member node from an encryption group, as shown in Figure 109. Upon removal, the HA cluster failover capability and target associations pertaining to the node are no longer present.
Page 227 Encryption group and HA cluster maintenance 3. Determine the state of the node. Log in to the member node and enter the cryptocfg show -groupmember command followed by the node WWN. Provide a slot number if the encryption engine is a blade. SecurityAdmin:switch>cryptocfg --show -groupmember \ 10:00:00:05:1e:41:99:bc Node Name:...
Page 228: Deleting An Encryption Group
Encryption group and HA cluster maintenance Deleting an encryption group You can delete an encryption group after removing all member nodes following the procedures described in the previous section. The encryption group is deleted on the group leader after you have removed all member nodes.
Page 229: Replacing An Ha Cluster Member
Encryption group and HA cluster maintenance HA cluster name: HAC1 - 2 EE entries Status: Committed Slot Number Status 11:22:33:44:55:66:77:00 Online 10:00:00:05:1e:53:74:87 Online HA cluster name: HAC2 - 1 EE entry Status: Defined Slot Number Status 10:00:00:05:1e:53:4c:91 Online In the following example, the encryption group brocade has one HA cluster HAC3. The encryption engine with the WWN of 10:00:00:05:1e:53:89:dd has failed over containers from the encryption engine with the WWN of 10:00:00:05:1e:53:fc:8a it is offline.
Page 230 Encryption group and HA cluster maintenance 1. Invoke the cryptocfg replace -haclustermember command on the group leader to replace the failed encryption engine (EE2) with another encryption engine (EE3). This operation effectively removes the failed encryption engine (EE2) from the HA cluster and adds the replacement encryption engine (EE3) to the HA cluster.
Page 231: Deleting An Ha Cluster Member
Encryption group and HA cluster maintenance Case 2: Replacing a “live” encryption engine in an HA cluster 1. Invoke the cryptocfg replace -haclustermember command on the group leader to replace the live encryption engine EE2 with another encryption engine (EE3). This operation effectively removes EE2 from the HA cluster and adds the replacement encryption engine (EE3) to the HA cluster.
Page 232: Performing A Manual Failback Of An Encryption Engine
Encryption group and HA cluster maintenance Performing a manual failback of an encryption engine By default, failback occurs automatically if an encryption engine that failed was replaced or comes back online. When manual failback policy is set in the encryption group, you must invoke a manual failback of the encryption engine after the failing encryption engine was restored or replaced.
Page 233: Encryption Group Merge And Split Use Cases
Encryption group merge and split use cases SecurityAdmin:switch>cryptocfg --show -hacluster -all Encryption Group Name: brocade_1 Number of HA Clusters: 1 HA cluster name: HAC3 - 2 EE entries Status: Committed Slot Number Status EE1 => 10:00:00:05:1e:53:89:dd Online EE2 => 10:00:00:05:1e:53:fc:8a Online Encryption group merge and split use cases This section describes the following recovery scenarios and related operations:...
Page 234: A Member Node Reboots And Comes Back Up
Encryption group merge and split use cases 4. Set up the member node: Configure the IP address of the new node that is replacing the failed node, and the IP addresses of the I/O cluster sync ports (Ge0 and Ge1), and initialize the node with the cryptocfg initnode command.
Page 235: A Member Node Lost Connection To The Group Leader
Encryption group merge and split use cases A member node lost connection to the group leader AssumeN1, N2 and N3 form an encryption group, and N2 is the group leader node. N3 and N1 are part of an HA cluster. Assume that N3 lost connection to the group leader node N2 but still maintains communications with other nodes in the encryption group.
Page 236: Several Member Nodes Split Off From An Encryption Group
Encryption group merge and split use cases Recovery 1. Restore connectivity between the two separate encryption group islands. When the lost connection is restored, an automatic split recovery process begins. The current group leader and the former group leader (N3 and N2 in this example) arbitrate the recovery, and the group leader with the majority number of members (N2) becomes group leader.
Page 237: Adjusting Heartbeat Signaling Values
Encryption group merge and split use cases Adjusting heartbeat signaling values Encryption group nodes use heartbeat signaling to communicate to one another and to their associated key vaults. A configurable threshold of heartbeat misses determined how long an encryption group leader will wait before declaring a member node unreachable. The default heartbeat signaling values are three heartbeat misses, each followed by a two second heartbeat time-out.
Page 238 Encryption group merge and split use cases Given that you may have up to four nodes per encryption group, an EG split may leave you with any of the following possible EG split combinations: • Two node EG split - resulting in two single node encryption groups. Each node is a group leader node.
Page 239 Encryption group merge and split use cases Two node EG split manual recovery example The following example is a case where you have an EG split of a two node encryption group with nodes named Node181 and Node182. Node181 has WWN 10:00:00:00:05:1e:33:33 and Node182 has WWN 10:00:00:05:1e:55:55:55.
Page 240 Encryption group merge and split use cases …Output truncated… 4. Go to every other encryption group island to delete the encryption group. NOTE If you have four encryption nodes that have split into a pair of two node encryption groups, refer to “The 2:2 EG split exception”...
Page 241 Encryption group merge and split use cases Eject the node shown above which is in the DEF_NODE_STATE_DISCOVERED state using the following command: EGisland2GLNode:admin->cryptocfg --eject -membernode 10:00:00:05:1e:c1:9b:91 You can now delete the encryption group from the member node using the admin->cryptocfg delete -encgroup command, and perform a cryptocfg show -groupcfg command to verify that no encryption group is defined on the member node as was done for Node181 in the two...
Page 242: Isolation
Encryption group merge and split use cases Configuration impact of encryption group split or node isolation When a node is isolated from the encryption group or the encryption group is split to form separate encryption group islands, the defined or registered node list in the encryption group is not equal to the current active node list, and the encryption group is in a DEGRADED state rather than in a CONVERGED state.
Page 243: Encryption Group Database Manual Operations
Encryption group database manual operations Encryption group database manual operations Manual intervention may be necessary if the encryption group databases or security databases of encryption group members are not synchronized. The following sections describe manual operations that enable you to do the following: •...
Page 244 Key vault diagnostics If an encryption switch is part of an EG, the diagnostic testing is performed on that switch only and not the entire group. If multiple nodes in an encryption group have different Fabric OS versions, only those nodes running Fabric OS 7.0.0 and later can be configured for periodic key vault diagnostic testing.
Page 245 Key vault diagnostics This check indicates only the synchronization capability at a given point of time, and does not mean all keys on the vault are synchronized. The need for manual synchronization of keys depends on the point of key vault connectivity failure or user-initiated operations (for example, reboot) and is not identified by the KV diagnostics report.
Page 246: General Encryption Troubleshooting
General encryption troubleshooting General encryption troubleshooting Table 9 lists the commands you can use to check the health of your encryption setup. Table 10 provides additional information for failures you might encounter while configuring switches using the CLI. TABLE 9 General troubleshooting tips using the CLI Command Activity...
Page 247 General encryption troubleshooting TABLE 10 General errors and conditions Problem Resolution A backup fails because the LUN is always in the initialize Use one of two resolutions: state for the tape container. • Load the old master key on the switch at an alternate location. The key Tape media is encrypted and gets a key which is archived for the tape media can then be decrypted.
Page 248 General encryption troubleshooting TABLE 10 General errors and conditions Problem Resolution A performance drop occurs when using DPM on a Microsoft Change the DPM behavior to send one request at a time by adding DWORD Windows system to back up to a Scalar 500i tape library. “BufferQueueSize”...
Page 249: Troubleshooting Examples Using The Cli
Troubleshooting examples using the CLI Troubleshooting examples using the CLI Encryption Enabled Crypto Target LUN The LUN state should be Encryption enabled for the host to see the Crypto LUN. switch:FabricAdmin> cryptocfg --show -LUN disk_container1 0 21:01:00:e0:8b:a9:ac:d2 -stat Container name: disk_container1 Type: disk...
Page 250: Encryption Disabled Crypto Target Lun
Troubleshooting examples using the CLI Encryption Disabled Crypto Target LUN If the LUN state is Encryption Disabled the host will not be able to access the Crypto LUN. > switch:FabricAdmin> cryptocfg --show -LUN disk_container1 0 21:01:00:e0:8b:a9:ac:d2 -stat Container name: disk_container1 Type: disk EE node:...
Page 251: Management Application Encryption Wizard Troubleshooting
Management application encryption wizard troubleshooting Management application encryption wizard troubleshooting • Errors related to adding a switch to an existing group ....231 • Errors related to adding a switch to a new group ....232 •...
Page 252: Errors Related To Adding A Switch To A New Group
Management application encryption wizard troubleshooting Errors related to adding a switch to a new group Table 12 lists configuration task errors you might encounter while adding a switch to a new group, and describes how to troubleshoot them. TABLE 12 Error recovery instructions for adding a switch to a new group Configuration task Error description...
Page 253: Wizard
Management application encryption wizard troubleshooting TABLE 12 Error recovery instructions for adding a switch to a new group (Continued) Configuration task Error description Instructions Create a new master key (opaque key A failure occurred while attempting to Remove the switch from the group using the Group vaults only) create a new master key.
Page 254: Lun Policy Troubleshooting
LUN policy troubleshooting LUN policy troubleshooting Table 14 may be used as an aid in troubleshooting problems related to LUN policies. TABLE 14 LUN policy troubleshooting Case Reasons for the LUN getting disabled by Action taken If you do not need to save the data: If you need to save the data: the encryption switch The LUN was modified from encrypt...
Page 255: Loss Of Encryption Group Leader After Power Outage
Loss of encryption group leader after power outage Loss of encryption group leader after power outage When all nodes in an encryption group, HA Cluster, or DEK Cluster are powered down due to catastrophic disaster or power outage to whole data center, and the group leader node either fails to come back up when the other nodes are powered on, or the group leader is kept powered down, the member nodes lose information and knowledge about the encryption group.
Page 256: Mpio And Internal Lun States
MPIO and internal LUN states MPIO and internal LUN states The Internal LUN State field displayed within the cryptocfg show -LUN command output does not indicate the host-to-storage path status for the displayed LUN, but rather the internal LUN state as known by the given encryption engine.
Page 257: Fs8-18 Blade Removal And Replacement
FS8-18 blade removal and replacement 2. Check the status of the resumed re-key session. FabricAdmin:switch> cryptocfg --show -rekey -all • Read all data off the LUN and write it to another LUN. In this case, you can cancel the re-key session by removing the LUN from its container and force committing the transaction.
Page 258: Bes Removal And Replacement
BES removal and replacement Zeroize the new encryption engine. cryptocfg --zeroizeEE 4 The new encryption engine will power off and power on again automatically. 8. If a system card authentication is needed to enable the encryption engine, re-register the system card through the Management application client for the new encryption engine. 9.
Page 259 BES removal and replacement 2. Reclaim the WWN base of BES3. cryptocfg --reclaimWWN –membernode <switchWWN> [-list] 3. Synchronize the crypto configurations across all member nodes. cryptocfg –-commit NOTE When attempting to reclaim a failed Brocade Encryption Switch, do not execute .
Page 260 BES removal and replacement 9. Set the IP address for the new Brocade Encryption Switch using the ipaddrset command for the Mgmt Link and IO link. Check that the switch name and domain ID associated with the replacement switch matches that of the original. 10.
Page 261 BES removal and replacement 23. Register the new node KAC Certificate with the HP SKM/ESKM appliances and create a username and password for this node on the HP SKM Appliances under the group “Brocade.” 24. Create the username and password on the new node same as created on the HP SKM/ESKM appliances.
Page 262: Single Node Eg Replacement
BES removal and replacement b. Issue commit. cryptocfg --commit 30. Check the encryption group state to ensure that the entire encryption group is in the converged and In Sync state: cryptocfg --show -groupcfg Single Node EG Replacement 1. Upload the configuration stored on the Brocade Encryption Switch you are replacing using the FOS configupload command.
Page 263 BES removal and replacement 14. Check the encryption engine state using following command to ensure encryption engine is online: cryptocfg --show -localEE 15. Export the KAC CSR from the new node and sign the CSR from the HP SKM/ESKM Local CA. 16.
Page 264: Switch
Reclaiming the WWN base of a failed Brocade Encryption Switch Reclaiming the WWN base of a failed Brocade Encryption Switch When a Brocade Encryption Switch fails, to reclaim the WWN base, follow these steps: 1. Locate the Brocade Encryption Switch that has failed and deregister from the encryption group.
Page 265: Moving A Blade From One Eg To Another Eg In The Same Fabric
Moving a blade from one EG to another EG in the same fabric 4. Enter the following command on BES1 to deregister the ejected node from the encryption group: cryptocfg --dereg -membernode <BES3-WWN> 5. Enter the following command on BES3 to clean up the encryption configuration on the deregistered node: cryptocfg –-reclaimWWN –cleanup When prompted, enter yes to each prompt.
Page 266: Moving A Bes From One Eg To Another Eg In The Same Fabric
Moving a BES from one EG to another EG in the same fabric 2. Enter the following command to propagate the change throughout the EG: cryptocfg --commit 3. Remove the blade from DCX1, slot 4 and plug into DCX2, slot 3. 4.
Page 267: Removing Stale Rekey Information For A Lun
Removing stale rekey information for a LUN Removing stale rekey information for a LUN To clean up stale rekey information for a LUN, complete one of the following procedures: Procedure 1: 1. Modify the LUN policy from “encrypt” to “cleartext” and commit. The LUN will become disabled. 2.
Page 268 Removing stale rekey information for a LUN Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 269: State And Status Information
Appendix State and Status Information In this appendix • Encryption engine security processor (SP) states ....249 • Security processor KEK status ........250 •...
Page 270: Security Processor Kek Status
Security processor KEK status Security processor KEK status Table 19 lists security processor KEK status information. TABLE 19 Security processor KEK status KEK type KEK status Description Primary KEK (current MK or None Primary KEK is not configured. primary KV link key) Mismatch Primary KEK mismatch between the CP and the SP.
Page 271 Encrypted LUN states TABLE 20 Encrypted LUN states (Continued) LUN_1ST_TIME_REKEY_IN_PROG First time re-key is in progress. LUN_KEY_EXPR_REKEY_IN_PROG Key expired re-key is in progress. LUN_MANUAL_REKEY_IN_PROG Manual re-key is in progress. LUN_DECRYPT_IN_PROG Data decryption is in progress. LUN_WR_META_PENDING Write metadata is pending. LUN_1ST_TIME_REKEY_PENDING First time re-key is pending.
Page 272 Encrypted LUN states TABLE 20 Encrypted LUN states (Continued) LUN_DIS_WR_META_DONE_ERR Disabled (Write metadata done with failure). LUN_DIS_LUN_REMOVED Disabled (LUN re-discovery detects LUN is removed). LUN_DIS_LSN_MISMATCH Disabled (LUN re-discovery detects new device ID). LUN_DIS_DUP_LSN Disabled (Duplicate LUN SN found). LUN_DIS_DISCOVERY_FAIL Disabled (LUN discovery failure). LUN_DIS_NO_LICENSE Disabled (Third party license is required).
Page 273 Encrypted LUN states TABLE 21 Tape LUN states Internal Names Console String Explanation LUN_DIS_LUN_NOT_FOUND Disabled (LUN not found) No logical unit structure in tape module. This is an internal software error. If it occurs, contact Brocade support. LUN_TGT_OFFLINE Target Offline Target port is not currently in the fabric.
Page 274 Encrypted LUN states TABLE 21 Tape LUN states LUN_ENCRYPT Encryption enabled The tape medium is present, and is in ciphertext (encrypted). The encryption switch or blade has full read/write access, because its current tape policy for the medium is also encrypted.
Page 275 Index container adding a LUN to CryptoTarget using the CLI creating a CryptoTarget add commands deleting a CryptoTarget using the CLI --add -haclustermember discovering a Crypto LUN using the CLI --add -initiator moving a CryptoTarget using the CLI --add -LUN removing a LUN to CryptoTarget using the CLI removing an initiator using the CLI Control Processor...
Page 276 cryptocfg command CryptoTarget container --add -haclustermember adding a LUN --add -initiator configuring --add -LUN creating --commit deleting --create -container discovering a LUN --create -encgroup moving --create -hacluster removing a LUN --create -tapepool removing an initiator from --delete -container --delete -encgroup --delete -hacluster --delete -tapepool --dereg -membernode...
Page 277 encryption encryption group adding a license adding a switch using the management application best practices for licensing advanced configuration configuration planning for the management allowed configuration changes application basic configuration configure dialog box configuration impact of split or node isolation configuring confirming configuration status LUNs for first-time encryption...
Page 278 failback command, --failback -EE import commands, --import failover and failback, states of encryption engines during initialize commands --initEE initEE field replaceable unit --initnode See FRU initializing firmware download considerations encryption switch using the CLI frame redirection initiators, removing from CryptoTarget container creating and enabling in an FCR configuration (edge to initiator-target zone, creating edge)
Page 279 configuring for first-time encryption configuring for multi-path example NetBackup labeling configuring policies using the CLI NetWorker labeling force-enabling for encryption impact of policy changes modifying parameters using the CLI multi-path configuration requirements policy parameters PID failover removing Crypto LUN to CryptoTarget container policies setting policy for automatic re-keying configuration examples...
Page 280 cryptoCfg commands tape LUN, configuring tape metadata tape pool impact of policy changes tape pools adding security processor (SP) CommVault Galaxy labeling using the CLI KEK status configuring states for encryption engines creating using the CLI security tab on management application deleting using the CLI using to back up a master key description of...
Page 281 configuration virtual targets, description of in an encryption configuration zeroize command --zeroize zeroizing effects of using on encryption engine zone creating an initiator-target using the CLI Fabric OS Encryption Administrator’s Guide 53-1002159-03...
Page 282 Fabric OS Encryption Administrator’s Guide 53-1002159-03...

This manual is also suitable for:

Fabric os encryption

Brocade Communications Systems Brocade 8/12c Administrator's Manual

Chapter 1 Encryption Overview

Chapter 2 Encryption Configuration

Chapter 3 Configuring Brocade Encryption Using the CLI

Chapter 4 Deployment Scenarios

Chapter 5 Best Practices and Special Topics

Chapter 6 Maintenance and Troubleshooting

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for Brocade Communications Systems Brocade 8/12c

Summary of Contents for Brocade Communications Systems Brocade 8/12c