HP 8/8 Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864-01, June - Page 141

Creating a CryptoTarget container, any alphanumeric characters, hyphens, and underscore characters.

Page 141 highlights

CryptoTarget container configuration 3 Creating a CryptoTarget container Before you begin, have the following information ready: • The switch WWNs of all nodes in the encryption group. Use the cryptocfg --show -groupmember -all command to gather this information. • The port WWNs of the targets whose LUNs are being enabled for data-at-rest encryption. • The port WWNs of the hosts (initiators) which should gain access to the LUNs hosted on the targets. Any given target may have multiple ports through which a given LUN is accessible and the ports are connected to different fabrics for redundancy purposes. Any given target port through which the LUNs are accessible must be hosted on only one Encryption switch (or pair in case of HA deployment). Another such target port should be hosted on a different encryption switch either in the same fabric or in a different fabric based on host MPIO configuration. A given host port through which the LUNs are accessible is hosted on the same encryption switch on which the target port (CryptoTarget container) of the LUNs is hosted. NOTE It is recommended you complete the encryption group and HA cluster configuration before configuring the CryptoTarget containers. 1. Log into the group leader as Admin or FabricAdmin. 2. Enter the cryptocfg --create -container command. Specify the type of the container, (disk or tape), followed by a name for the CryptoTarget container, the encryption engine's node WWN, and the target's Port WWN and node WWN. Provide a slot number if the encryption engine is a blade. • 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. The initiator is added in step 3. FabricAdmin:switch>cryptocfg --create -container disk my_disk_tgt \ 10:00:00:00:05:1e:41:9a:7e 20:0c:00:06:2b:0f:72:6d 20:00:00:06:2b:0f:72:6d Operation Succeeded 3. Add an initiator to the CryptoTarget container. Enter the cryptocfg --add -initiator command followed by the initiator port WWN and the node WWN. Note that the initiator port WWN must also be added to the LUN when the LUN is added to the CryptoTarget container. FabricAdmin:switch>cryptocfg --add -initiator my_disk_tgt \ 10:00:00:00:c9:2b:c9:3a 20:00:00:00:c9:2b:c9:3a Operation Succeeded 4. Commit the transaction. The commit operation creates the virtual devices and the redirection zone that routes traffic through these devices. FabricAdmin:switch>cryptocfg --commit Operation Succeeded Fabric OS Encryption Administrator's Guide 123 53-1001864-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248

Fabric OS Encryption Administrator’s Guide
123
53-1001864-01
CryptoTarget container configuration
3
Creating a CryptoTarget container
Before you begin, have the following information ready:
The switch WWNs of all nodes in the encryption group. Use the
cryptocfg
--
show
-groupmember -all
command to gather this information.
The port WWNs of the targets whose LUNs are being enabled for data-at-rest encryption.
The port WWNs of the hosts (initiators) which should gain access to the LUNs hosted on the
targets.
Any given target may have multiple ports through which a given LUN is accessible and the ports are
connected to different fabrics for redundancy purposes. Any given target port through which the
LUNs are accessible must be hosted on only one Encryption switch (or pair in case of HA
deployment). Another such target port should be hosted on a different encryption switch either in
the same fabric or in a different fabric based on host MPIO configuration.
A given host port through which the LUNs are accessible is hosted on the same encryption switch
on which the target port (CryptoTarget container) of the LUNs is hosted.
NOTE
It is recommended you complete the encryption group and HA cluster configuration before
configuring the CryptoTarget containers.
1.
Log into the group leader as Admin or FabricAdmin.
2.
Enter the
cryptocfg
--
create -container
command. Specify the type of the container, (disk or
tape), followed by a name for the CryptoTarget container, the encryption engine’s node WWN,
and the target’s Port WWN and node WWN. Provide a slot number if the encryption engine is a
blade.
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. The initiator is added in
step 3.
FabricAdmin:switch>
cryptocfg --create -container disk my_disk_tgt \
10:00:00:00:05:1e:41:9a:7e 20:0c:00:06:2b:0f:72:6d 20:00:00:06:2b:0f:72:6d
Operation Succeeded
3.
Add an initiator to the CryptoTarget container. Enter the
cryptocfg
--
add -initiator
command
followed by the initiator port WWN and the node WWN.
Note that the initiator port WWN must also be added to the LUN when the LUN is added to the
CryptoTarget container.
FabricAdmin:switch>
cryptocfg --add -initiator my_disk_tgt \
10:00:00:00:c9:2b:c9:3a 20:00:00:00:c9:2b:c9:3a
Operation Succeeded
4.
Commit the transaction. The commit operation creates the virtual devices and the redirection
zone that routes traffic through these devices.
FabricAdmin:switch>
cryptocfg --commit
Operation Succeeded