Cisco III System Message Guide - Page 266
For each queue, there is a limited number of unique WRED limits sets that can
UPC - 746320181691
View all Cisco III manuals
Add to My Manuals
Save this manual to your list of manuals |
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