HP Cisco MDS 9020 Cisco MDS 9000 Family Storage Media Encryption Configuration - Page 187

show tech details, show tech sme, C:\Program Files\Cisco Systems\MDS 9000\logs

Page 187 highlights

Chapter 9 Cisco SME Troubleshooting Troubleshooting Scenarios Send documentation comments to [email protected] If you need to contact your customer support representative or Cisco TAC At some point, you may need to contact your customer support representative or Cisco TAC for some additional assistance. Before doing so, enter the show tech details and the show tech sme commands and collect all logs from the C:\Program Files\Cisco Systems\MDS 9000\logs directory before contacting your support organization. A syslog message is displayed when a Cisco MDS switch configured with Cisco SME in the startup configuration boots up When you reboot a Cisco MDS switch that has the cluster configuration stored in the startup-config file, the following syslog message may be displayed: %CLUSTER-2-CLUSTER_DB_SYNC_FAIL: Cluster application 3 dataset 1 database synchronization failed, reason="Invalid cluster API registration" This error message is expected and can be ignored. Importing a volume group file causes a 'wrap key object not found' error message A tape volume group was created and the volume group was exported to a file. The tape volume group was deleted and a new tape volume group was created. When the same volume group was imported, the import operation fails and the error message "wrap key object not found" is displayed. This error occurs because there is another volume group key active in the Key Management Center with the same index (but different versions) as the current volume group into which the import operation is performed. Accounting log file shows the replication of keys failed. The replication of a key for a cluster fails when the transaction context is invalid or is expired. The key entry will be moved to Sme_repl_error_key table. You should manually remove this record from the Sme_repl_error_key table to the Sme_repl_pending_key table and retry the replication process. OL-18091-01, Cisco MDS NX-OS Release 4.x Cisco MDS 9000 Family Storage Media Encryption Configuration Guide 9-9

  • 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
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280

Send documentation comments to [email protected]
9-9
Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
OL-18091-01, Cisco MDS NX-OS Release 4.x
Chapter 9
Cisco SME Troubleshooting
Troubleshooting Scenarios
If you need to contact your customer support representative or Cisco TAC
At some point, you may need to contact your customer support representative or Cisco TAC for some
additional assistance. Before doing so, enter the
show tech details
and the
show tech sme
commands
and collect all logs from the
C:\Program Files\Cisco Systems\MDS 9000\logs
directory before
contacting your support organization.
A syslog message is displayed when a Cisco MDS switch configured with Cisco SME in the startup configuration
boots up
When you reboot a Cisco MDS switch that has the cluster configuration stored in the startup-config file, the
following syslog message may be displayed:
<timestamp> <switch name> %CLUSTER-2-CLUSTER_DB_SYNC_FAIL: Cluster <cluster-id>
application 3 dataset 1 database synchronization failed, reason="Invalid cluster API
registration"
This error message is expected and can be ignored.
Importing a volume group file causes a 'wrap key object not found' error message
A tape volume group was created and the volume group was exported to a file. The tape volume group
was deleted and a new tape volume group was created. When the same volume group was imported, the
import operation fails and the error message “wrap key object not found” is displayed.
This error occurs because there is another volume group key active in the Key Management Center with
the same index (but different versions) as the current volume group into which the import operation is
performed.
Accounting log file shows the replication of keys failed.
The replication of a key for a cluster fails when the transaction context is invalid or is expired. The key
entry will be moved to Sme_repl_error_key table. You should manually remove this record from the
Sme_repl_error_key table to the Sme_repl_pending_key table and retry the replication process.