Cisco WS-C2916M-XL Software Guide - Page 302

FRANK Messages

Page 302 highlights

Error Message and Recovery Procedures Appendix A System Messages FRANK Messages This section contains the Gigabit Ethernet controller error messages. Error Message FRANK-1-BUFFER_STORE_FAIL: 64B frame storage failure on [chars] Explanation When storing 64-B frames, the controller has ignored the buffer congestion warnings and kept storing until a buffer reject. Hence, the port bandwidth allocation limit was increased to allow the last frame to be stored without rejection. In spite of this, the frame storage has failed. Recommended Action This error prevents a crucial workaround for the controller from executing. This brings down the switch and causes it to reload. Error Message FRANK-1-BUFFER_STORE_SET_FAIL: 64B frame storage cap_set failure on [chars]. Explanation When storing 64-B frames, the controller has ignored the buffer congestion warnings and kept storing until a buffer reject. Hence, the port bandwidth allocation limit needs to be increased to allow the last frame to be stored without rejection. However, the set for the extra allocation value has failed. Recommended Action This error prevents a crucial workaround for the controller from executing. This brings down the switch and causes it to reload. Error Message FRANK-1-DIST_FIFO_POLL_HANDLE: [chars]: Failed to allocate molecule handle Explanation A molecule chain is sent by the CPU to the controller driver to read the values of all the distribution FIFO registers for the controller. The memory allocation for this molecule has failed during initialization, and this command cannot be issued to the controller. Recommended Action This error prevents a crucial workaround for the controller from executing. This brings down the switch and causes it to reload. Error Message FRANK-1-INSTANCE_NOT_FOUND: Instance to be removed not found\n Explanation The controller instance to be removed was not found in the linked list of instances. Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the gathered information. A-10 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-08

  • 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
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368

A-10
Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-08
Appendix A
System Messages
Error Message and Recovery Procedures
FRANK Messages
This section contains the Gigabit Ethernet controller error messages.
Error Message
FRANK-1-BUFFER_STORE_FAIL: 64B frame storage failure on [chars]
Explanation
When storing 64-B frames, the controller has ignored the buffer congestion warnings and
kept storing until a buffer reject. Hence, the port bandwidth allocation limit was increased to allow
the last frame to be stored without rejection. In spite of this, the frame storage has failed.
Recommended Action
This error prevents a crucial workaround for the controller from executing. This
brings down the switch and causes it to reload.
Error Message
FRANK-1-BUFFER_STORE_SET_FAIL: 64B frame storage cap_set failure on
[chars].
Explanation
When storing 64-B frames, the controller has ignored the buffer congestion warnings and
kept storing until a buffer reject. Hence, the port bandwidth allocation limit needs to be increased to
allow the last frame to be stored without rejection. However, the set for the extra allocation value has
failed.
Recommended Action
This error prevents a crucial workaround for the controller from executing. This
brings down the switch and causes it to reload.
Error Message
FRANK-1-DIST_FIFO_POLL_HANDLE: [chars]: Failed to allocate molecule
handle
Explanation
A molecule chain is sent by the CPU to the controller driver to read the values of all the
distribution FIFO registers for the controller. The memory allocation for this molecule has failed
during initialization, and this command cannot be issued to the controller.
Recommended Action
This error prevents a crucial workaround for the controller from executing. This
brings down the switch and causes it to reload.
Error Message
FRANK-1-INSTANCE_NOT_FOUND: Instance to be removed not found\n
Explanation
The controller instance to be removed was not found in the linked list of instances.
Recommended Action
Copy the error message exactly as it appears on the console or in the system log.
Enter the
show tech-support
command to gather data that might provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text or
from the
show tech-support
output, contact your Cisco technical support representative, and provide
the representative with the gathered information.