Cisco III System Message Guide - Page 266

For each queue, there is a limited number of unique WRED limits sets that can

Page 266 highlights

SIP600_QOS Messages Chapter 2 Messages and Recovery Procedures Error Message %SIP600_QOS-3-NOTFOUND: SIP-600 Software Element Not Found - [chars]: [chars] [dec] Explanation The SIP 600 client could not locate a required software element. Recommended Action Reload the Cisco IOS image on the affected line card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Error Message %SIP600_QOS-3-NOTSUP: SIP-600 Feature Not Supported - [chars]: [chars] [chars] Explanation The SIP 600 does not support the specified feature. Recommended Action Change the SIP 600 configuration so that it does not include the specified feature. Error Message %SIP600_QOS-3-QEXCEEDWREDGRP: SIP-600 Exceeded WRED limit groups for queue [dec] Explanation The SIP 600 depleted available resources when configuring WRED on the specified hardware queue. This condition is the result of attempting to configure a QoS action. Recommended Action For each queue, there is a limited number of unique WRED limits sets that can be configured. The user-configuration action has caused the limits to go beyond the system limit. As a result, WRED is not configured on that queue. The following configuration illustrates three unique sets of WRED min/max limits: random-detect random-detect prec 0 1000 2000 1 random-detect prec 1 1000 2000 1 random-detect prec 2 2000 3000 1 random-detect prec 3 2000 3000 1 random-detect prec 4 1000 2000 1 random-detect prec 5 3000 4000 1 random-detect prec 6 2000 3000 1 random-detect prec 7 3000 4000 1 Update your configuration so that the WRED configuration is within the limits, and reapply the service policy. 2-236 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02

  • 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

2-236
Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY
OL-11469-02
Chapter 2
Messages and Recovery Procedures
SIP600_QOS Messages
Error Message
%SIP600_QOS-3-NOTFOUND: SIP-600 Software Element Not Found - [chars]:
[chars] [dec]
Explanation
The SIP 600 client could not locate a required software element.
Recommended Action
Reload the Cisco IOS image on the affected line card or platform. If the error
persists, copy the message exactly as it appears on the console or in the system log. Research and
attempt to resolve the issue using the tools and utilities provided at
. With
some messages, these tools and utilities will supply clarifying information. Search for resolved
software issues using the Bug Toolkit at
. If you still
require assistance, open a case with the Technical Assistance Center via the Internet at
, or contact your Cisco technical support
representative and provide the representative with the information you have gathered. Attach the
following information to your case in nonzipped, plain-text (.txt) format: the output of the
show
logging
and
show tech-support
commands and your pertinent troubleshooting logs.
Error Message
%SIP600_QOS-3-NOTSUP: SIP-600 Feature Not Supported - [chars]: [chars]
[chars]
Explanation
The SIP 600 does not support the specified feature.
Recommended Action
Change the SIP 600 configuration so that it does not include the specified
feature.
Error Message
%SIP600_QOS-3-QEXCEEDWREDGRP: SIP-600 Exceeded WRED limit groups for
queue [dec]
Explanation
The SIP 600 depleted available resources when configuring WRED on the specified
hardware queue. This condition is the result of attempting to configure a QoS action.
Recommended Action
For each queue, there is a limited number of unique WRED limits sets that can
be configured. The user-configuration action has caused the limits to go beyond the system limit. As
a result, WRED is not configured on that queue. The following configuration illustrates three unique
sets of WRED min/max limits:
random-detect
random-detect prec 0 1000 2000 1
random-detect prec 1 1000 2000 1
random-detect prec 2 2000 3000 1
random-detect prec 3 2000 3000 1
random-detect prec 4 1000 2000 1
random-detect prec 5 3000 4000 1
random-detect prec 6 2000 3000 1
random-detect prec 7 3000 4000 1
Update your configuration so that the WRED configuration is within the limits, and reapply the
service policy.