Cisco IOS XR System Error Message Reference Guide, Release 3.5
Quality of Service (QoS) Messages
Downloads: This chapterpdf (PDF - 440.0KB) The complete bookPDF (PDF - 18.83MB) | Feedback

Quality of Service (QoS) Messages

Table Of Contents

Quality of Service (QoS) Messages

CLASSIFY Messages

EFCM Messages

FQ_QOS Messages

MARK_QOS Messages

QALLOC Messages

QOS_CLASSIFY_NETIO Messages

QOS_FIFO Messages

QOS_RC_QOSMGR Messages

QOS_TXM Messages

QOS_WRED Messages

QOS Messages


Quality of Service (QoS) Messages


This section contains all Quality of Service related System Error Messages. The following facility codes are represented in this module:

CLASSIFY Messages

EFCM Messages

FQ_QOS Messages

MARK_QOS Messages

QALLOC Messages

QOS_CLASSIFY_NETIO Messages

QOS_FIFO Messages

QOS_RC_QOSMGR Messages

QOS_TXM Messages

QOS_WRED Messages

QOS Messages

CLASSIFY Messages

Error Message     
 
    
    
   

%QOS-CLASSIFY-4-MATCH_NOT_SUPPORTED Matching based on [chars] is not supported on [chars].

Explanation    Matching based on the configured criterion is not supported in the specified direction. Reconfigure the policy map so that the specified match feature clause is removed and then reapply the service policy.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-CLASSIFY-4-TOO_MANY_CLASSES Policymap '[chars]' contains [dec] classmaps, which exceeds the maximum supported

Explanation    The number of class-maps configured for the specified policy exceeds the currently supported maximum. Currently, the maximum number of supported classes is 32.

Recommended Action    Reconfigure the policy map so that it contains fewer than 32 classes, and reapply the service policy. The total number of class-maps for a policy-map includes both the number of specifically configured class-maps as well as the number of class-maps configured for all of its child policies, plus the default class, if not already configured.

Error Message     
 
    
    
   

%QOS-CLASSIFY-7-DEBUG_INIT_ERROR An error occurred during debug initialization, err: [chars]

Explanation    The QoS Classify DLL encountered an error during debug initialization. This is not a critical error. The QoS classification feature will function properly, but will not be able to use any of the debugging facilities.

Recommended Action    None

EFCM Messages

Error Message     
 
    
    
   

%QOS-EFCM-3-ERROR EFCM-Err: [chars]

Explanation    This is an error message from the EFCM, it indicates that something has gone wrong internally in the EFCM.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-EFCM-6-INFO EFCM-Info: [chars]

Explanation    This is an informational message from the EFCM

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-EFCM-7-DEBUG EFCM-Debug: [chars]

Explanation    This is a debuging message from the EFCM

Recommended Action    *NONE*

FQ_QOS Messages

Error Message     
 
    
    
   

%QOS-FQ_QOS-3-CAPS_ADD_FAIL Cannot add FQ capsulation to the data plane. Error code= [chars]

Explanation    QoS Manager failed to add capsulation for Fair Queueing to the the data plane.

Recommended Action    Turn on debugs with the following command debug qos control all dev and reapply the configuration command that caused the failure.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-BUNDLE_BW_NOPCT Absolute bw specified for bundle interfaces, use percentage values instead

Explanation    Bandwidth for a bundle interfaces must be specified in percentage values instead of absolute values.

Recommended Action    Modify the bandwidth parameter to specify percentage instead of absolute values and then reapply the configuration.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-BW_EXCEED Sum of allocated[chars] bandwidth exceeds the maximum

Explanation    The sum of the reserved bandwidth configured in the policy-map exceeds the maximum bandwidth for the interface.

Recommended Action    Correct the policymap so that the sum of reserved bandwidth is less than the maximum for the interface, and then reapply the service policy.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-BW_REMAINING_PRIORITY_ERROR Remaining Bandwidth and Priority can not be configured under the same class

Explanation    Remaining Bandwidth and priority can not be configured under the same policy.

Recommended Action    Reconfigure the policy-map so that one of the features is removed and then reapply the service policy.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-INVALID_UNIT An invalid or incompatible unit '[chars]' ([dec]) was specified for [chars].

Explanation    An invalid unit has been specified for the feature mentioned in the message.

Recommended Action    Modify the configuration parameter so that the specified unit is compatible with the feature and platform.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-MAX_CLASSES_EXCEEDED Number of classes exceeds the maximum number of classes allowed in a single policy map

Explanation    The number of class maps configured on the applied policy map exceeds the maximum allowed.

Recommended Action    Reconfigure the policy map so that the number of class-maps is reduced below the maximum allowed number and then reapply the policy.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-MIN_BW_ERROR Configured minimum bandwidth ([dec] kbps) is greater than the configured shape bandwidth ([dec] kbps) for class '[chars]'

Explanation    The specified minimum bandwidth is greater than the shape bandwidth.

Recommended Action    Correct the configuration so that minimum bandwidth is less than the shape(maximum) bandwidth, and reapply the service policy.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-NO_L1_BW_ERROR Level1 has no bandwidth guarantee. So cannot specify level2 bandwidth guarantee.

Explanation    A level 2 class has been configured with a bandwidth guarantee without the level 1 class having a bandwidth guarantee

Recommended Action    Reconfigure the policy-map so that the level 1 class includes a bandwidth guarantee and then reapply the service policy

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-SHAPE_BW_EXCEED Shape bandwidth exceeds 100 percent of the interface bandwidth

Explanation    The configured shaping bandwidth exceeds the maximum bandwidth for the interface.

Recommended Action    Correct the configuration so that shape bandwidth is less than or equal to the interface bandwidth.

Error Message     
 
    
    
   

%QOS-FQ_QOS-4-VALUE_TOO_LARGE The value specified for [chars] is too large and cannot be handled by the system

Explanation    The configured value for the feature mentioned in the message is too large.

Recommended Action    Use a value which is less than 4294967295 kbps or KBytes (depending on the type of parameter configured).

Error Message     
 
    
    
   

%QOS-FQ_QOS-5-PRIORITY_ERROR Shaping and Priority can not be configured under the same class

Explanation    Shape and priority can not be configured under the same class.

Recommended Action    Reconfigure the policy-map so that one of the features, either priority, or shaping is removed and then reapply the service policy.

Error Message     
 
    
    
   

%QOS-FQ_QOS-7-DEBUG_INIT_ERROR A error occurred during debug initialization, err: [chars]

Explanation    The QOS FQ dll encountered an error while initializing the debug facility. This is not a fatal error. QOS Fair Queueing will continue to execute properly, but will not be able to use the debugging facility.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-FQ_QOS-7-ERR_MEM_ALLOC Memory alloc error [chars]

Explanation    The router cannot allocate more memory while performing the specified task. This condition occurs only when the system is low on memory.

Recommended Action    None

MARK_QOS Messages

Error Message     
 
    
    
   

%QOS-MARK_QOS-5-NOT_SUPPORTED Marking of [chars] on [chars] interface in [chars] direction is not supported

Explanation    Marking of given attribute is not supported on a particular interface type in a particular direction.

Recommended Action    Please modify the policy-map so that the specified marking option is not included in the policy-map configuration.

Error Message     
 
    
    
   

%QOS-MARK_QOS-7-DEBUG_INIT_ERROR A error occurred during debug initialization, err: [chars]

Explanation    The QOS Mark component encounterd an error while initializing the debug facility. This is not a fatal error. QOS Marking will continue to execute properly, but will not be able to use the debuging facility.

Recommended Action    None

QALLOC Messages

Error Message     
 
    
    
   

%QOS-QALLOC-3-ALLOC_BLOCK_ERROR [chars]

Explanation    An error has occurred while dealing with blocks on the allocated list.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QALLOC-3-COALESCE_ERROR Error Coalescing free queues

Explanation    An error has occurred while coalescing free queues

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QALLOC-3-ERROR QoSRM-Err: [chars]

Explanation    This is an error message from the QoS RM Process, it indicates that something has gone wrong internally in the QoS RM.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QALLOC-3-FREE_BLOCK_ERROR [chars]

Explanation    An error has occurred while dealing with blocks on the free list.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QALLOC-3-QUEUE_SANITY Queue value out of bounds ([chars]) Queue: [unsigned int]

Explanation    Queue bounds checking has detected an error with a queue value

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QALLOC-4-WARN QoSRM-Warn: [chars]

Explanation    This is a warning message from the QoS RM Process

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QALLOC-6-INFO QoSRM-Info: [chars]

Explanation    This is an informational message from the QoS RM Process

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QALLOC-7-DEBUG QoSRM-Debug: [chars]

Explanation    This is a debuging message from the QoS RM Process

Recommended Action    *NONE*

QOS_CLASSIFY_NETIO Messages

Error Message     
 
    
    
   

%QOS-QOS_CLASSIFY_NETIO-7-DEBUG_INIT_ERROR A error occurred during debug initialization. Error: [chars]

Explanation    The QoS Classify DLL encountered an error while initializing the debug facility. This is not a fatal error. QoS Classify will continue to execute properly, but will not be able to use the debugging facility.

Recommended Action    None

QOS_FIFO Messages

Error Message     
 
    
    
   

%QOS-QOS_FIFO-7-DEBUG_INIT_ERROR An error occurred during debug initialization. Error: [chars]

Explanation    The QoS FIFO dll encountered a problem while initializingg the debug facility. This is not a fatal error. QoS FIFO will continue to execute properly, but will not be able to use the debugging facility.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_FIFO-7-DEBUG_INIT_ERROR An error occurred during debug initialization, err: [chars]

Explanation    The FIFO QoSMgr component encountered an error during debug initialization This is not a fatal condition. FIFO queueuing will work properly but will not be able to use any of the debugging facilities.

Recommended Action    None

QOS_RC_QOSMGR Messages

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-INVALID_CFG [chars]

Explanation    An invalid or unsupported policer has been configured.

Recommended Action    Please correct the configuration as indicated in the message.

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-INVALID_INTF_TYPE Policer Action [chars] has been configured on an un-supported interface type

Explanation    An invalid or unsupported policer has been configured.

Recommended Action    Please correct the configuration as indicated in the message.

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-INVALID_PEAK_RATE Configured peak-rate ([dec] [chars]) should be more than the configured conform rate ([dec] [chars])

Explanation    The peak-rate was configured less than the conform rate, which is not allowed.

Recommended Action    Increase the peak-rate or reduce the conform rate to satisfy the above requirement.

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-INVALID_UNIT An invalid or incompatible unit '[chars]' ([dec]) was specified for [chars]

Explanation    An invalid unit has been specified for the feature mentioned in the message.

Recommended Action    Correct the policy-map so that a correct unit value is specified for the feature being configured

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-NOT_SUPPORTED Action [chars] not supported on [chars]

Explanation    The policy has an action that is not supported .

Recommended Action    Correct the policy-map to correct the action to a supported action.

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-RC_BUNDLE_BW_NOPCT Absolute bw specified for bundle interfaces, use percentage values instead

Explanation    For bundle interfaces, the bandwidth must be specified in percentage values of absolute values.

Recommended Action    Correct the policy-map so that the bandwidth value is specified as a percentage of the total bandwidth and then reapply the policy-map

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-RC_BW_EXCEED Policer rate exceeds 100 percent of the interface bandwidth

Explanation    The Policer rate in the policy-map exceeds the maximum bandwidth that the interface can support.

Recommended Action    Correct the policy-map so that the policer rate is smaller than the maximum of the interface it has been applied to.

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-TOO_MANY_ACTIONS More than [dec] [chars] actions can not be configured.

Explanation    More than the maximum supported actions of the category mentioned in the message have been configured.

Recommended Action    Reduce the number of actions so they don't exceed the max allowed.

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-4-VALUE_TOO_LARGE The value specified for [chars] is too large and cannot be handled by the system

Explanation    The value configured for the feature mentioned in the message is too large.

Recommended Action    Use a value which is less than 4294967295 kbps or KBytes (depending on the type of parameter configured).

Error Message     
 
    
    
   

%QOS-QOS_RC_QOSMGR-7-DEBUG_INIT_ERROR A error occurred during debug initialization, err: [chars]

Explanation    The QoSMgr policer component encountered an error during debug initialization This is not a fatal condition. Policing will work properly but will not be able to use any of the debugging facilities.

Recommended Action    None

QOS_TXM Messages

Error Message     
 
    
    
   

%QOS-QOS_TXM-4-DEBUG_INIT_ERROR A error occurred during debug initialization, err: [chars]

Explanation    The QOS Mark process encounterd an error while initializing the debug facility. This is not a fatal error. QOS Marking will continue to execute properly, but will not be able to use the debuging facility.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_TXM-7-DEBUG_INIT_ERROR A error occurred during debug initialization, err: [chars]

Explanation    The QOS TXM process encountered an error while initializing the debug facility. This is not a fatal error. QOS TXM will continue to execute properly, but will not be able to use the debugging facility.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_TXM-7-UNINITIALISE_ERROR An error occurred in initialization sequence for iface: [chars]

Explanation    The QOS TXM process encountered an error in its initialsation sequence. This is a serious error. QOS TXM functioning correctly is not guranteed depending upon the exact problem in initialisation sequence

Recommended Action    None

QOS_WRED Messages

Error Message     
 
    
    
   

%QOS-QOS_WRED-7-DEBUG_INIT_ERROR An error occurred during debug initialization. Error: [chars]

Explanation    The QoS WRED dll encountered a problem while initializing the debug facility. This is not a fatal error. QoS WRED will continue to execute properly, but will not be able to use the debugging facility.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_WRED-7-INVALID_WRED_TYPE The type of random-detect configured under class '[chars]' is invalid or not supported on this platform. Please configure a supported random-detect type.

Explanation    An invalid type of random-detect was configured for the class specified in the message.

Recommended Action    Please reconfigure the policy-map with a supported type of random-detect. If the configured type of random-detect is supported on this platform and this message is seen, please contact the customer support with the following information.

QOS Messages

Error Message     
 
    
    
   

%QOS-QOS-3-CHKPT_GET_DATA_FAIL Failed to get QoS init data during restart. Remove policy [chars] from interface [chars], direction [chars] and re-add to recover.

Explanation    Getting init data from qos ma on RP could fail if there are any issues in restart code path in RP.

Recommended Action    Remove the policy and add it back

Error Message     
 
    
    
   

%QOS-QOS-3-DLL_INIT_FAIL Could not initialize [chars] dll. Error code - [chars]

Explanation    An error was encountered while trying to initialize a DLL that supports a given feature. Both the DLL name and the error code are displayed. This is a critical error in the QOS component. It indicates that the DLL that implements a feature does not provide an initializing function. This indicates that some QOS feature is not working properly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-FEATURE_ADD_FAIL Failed to add policy [chars], class = [chars], feature = [chars].

Explanation    Failed to add the specified feature while applying the specified service policy.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-FILE_ERROR File [chars] error: [chars]. Reason: [chars]

Explanation    An error was encountered while accessing a file. Both the file name and the error reason are displayed. This is a critical error in the QOS component. It indicates that the file that defines a feature is missing from the system and the related QOS feature will not work properly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-FILE_WRONG_INFO File [chars] [chars] [dec]

Explanation    An error was encountered while accessing a file. Both the file name and the error reason are displayed. This is a critical error in the QOS component. It indicates that the file that defines a feature is missing from the system and the related QOS feature will not working properly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-FT_CONFIGURE_FAIL Failed to configure feature [chars]. Error code - [chars]

Explanation    The specified feature could not be configured due to the specified reason.

Recommended Action    Please turn on debugs using the following command: debug qos control all dev

Error Message     
 
    
    
   

%QOS-QOS-3-FT_REMOVE_FAIL Failed to remove the feature [chars]. Error code - [chars]

Explanation    The QOS Manager process failed to remove the specified feature. The error code is also displayed.

Recommended Action    Please turn on debugs using the following command: debug qos control all dev and reenter the configuration command that caused the error. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-FT_SEND_FAIL Sending control to [chars] feature failed

Explanation    Failed to send a control feature information to the Execution Agent. The name of the feature is displayed.

Recommended Action    Please turn on debugs using the following command: debug qos control all dev and reenter the configuration command that caused the error. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-MGR_DLL_OPEN_FAIL Could not open [chars] DLL. Error code - [chars]

Explanation    An error was encountered while trying to open a DLL that supports a given feature. Both the DLL name and the error code are displayed. This is a critical error in the QOS component. It indicates that the DLL that implements the feature is not present in the system. This indicates that some QOS feature is not working properly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-MSG_SEND_FAIL Failed to send message to feature [chars] [chars]. Error code - [chars]

Explanation    Failed to send the a message to the specified feature due to the error message displayed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-PMAP_BW_REMAINING_PC_EXCEED_100 Sum of bandwidth remaining percent configured in policy [chars] is [dec]. Exceeding 100

Explanation    Configuration not allowed if the sum of bandwidth remaining percent in the policy exceeds 100.

Recommended Action    Ensure sum of bandwidth remaining percent is less than 100. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-3-POLICY_CHECK_FAIL Failed to configure policy - [chars]. Error code - [chars]

Explanation    The policy could not be configured on the interface as the policy itself or one of its child policies does not exist. The error code is also displayed.

Recommended Action    Please turn on debugs using the following command: debug qos control qosmgr dev and reenter the configuration command that caused the error. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message    
 
    
    
   

%QOS-QOS-3-BW_BUNDLE_ABSOLUTE Absolute values cannot be used for policies configured on Bundle interfaces. Use percentage values instead

Explanation    If the policy is applied on the bundle interface, the policer/shaper values must be configured in percentages.

Recommended Action    Reconfigure policy to use percentage values instead of absolute values.

Error Message     
 
    
    
   

%QOS-QOS-3-BW_SUM_EXCEEDS_100_PC Sum of bandwidth allocated to all classes exceeds 100 percent. Allocated BW : [dec] percent

Explanation    Allocated bandiwdth total including the default class can not exceed beyond 100%.

Recommended Action    Reconfigure policy to assign appropriate bandiwdth guarantees.

Error Message     
 
    
    
   

%QOS-QOS-3-DEF_CLASS_BW_EXCEED_99_PC Sum of bandwidth allocated to non-default classes exceeds 99 percent. Allocated BW : [dec] percent

Explanation    Allocated bandiwdth total can not exceed beyond 99% as 1% has to be reserved for the default class.

Recommended Action    Reconfigure policy to assign appropriate bandiwdth guarantees.

Error Message     
 
    
    
   

%QOS-QOS-3-FABQOS_BWR_UNSUPPORTED With [chars] classes, BWR percent [chars] is not supported in a [chars] class

Explanation    With HP and BE classes only, only BWR 100 is allowed. With HP, AF and BE classes, BWR 100 is not supported in any Low Priority class. BWR 0 is not supported in any Low Priority class.

Recommended Action    Reconfigure policy to configure BWR less than 100% and greater than 0%

Error Message     
 
    
    
   

%QOS-QOS-3-MAX_CLASS_EXCEEDED_FOR_FABQOS Policy exceeds number of classes allowed for FabQoS

Explanation    Fabric QoS policy can only have a maximum of 3 classes. If the number of classes is more than 3, policy map is rejected.

Recommended Action    Reconfigure policy map to adjust number of classes

Error Message     
 
    
    
   

%QOS-QOS-3-ONLY_PRI_OR_BW_REM_PERCENT_ALLOWED Can not configure anything other than priority or bandwidth remaining percent for a fabqos policy

Explanation    Only priority and bandwidth remaining percent commands are supported for FabQoS policy.

Recommended Action    Reconfigure policy to use these two commands.

Error Message     
 
    
    
   

%QOS-QOS-3-OVER_SUBSCRIPTION_OF_MIN_BW_GAURANTEES There is oversubscription of minimum bandwidth guarantees, taking HP bandwidth into account. Bandwidth guarantees may not be met for this policy. Allocated BW : [dec] percent

Explanation    With high priority class configured and the bandwidth guarantee for the HP taken into account, the interface may have been oversubscribed. This could cause some packets from the class that has bandwidth guarantee configured to be dropped.

Recommended Action    Reconfigure policy to achieve optimal bandwidth guarantee results.

Error Message     
 
    
    
   

%QOS-QOS-3-QFIFO_DEBUG_NETIO_INIT_FAIL Failed to Initialize debug netion - [chars] Error : [chars]

Explanation    Debug initialization failed for NetIO. Debugs may not be printed.

Recommended Action    Try restarting qos_ma_ea process.

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_CONFIG_ON_PARENT_CLASS Un-supported configuration on a parent class of a hierarchical policy

Explanation    WRED and Queue-Limit configuration in a parent class of a hierarchical policy is not supported if the parent class necessitates the creation of a new group or port

Recommended Action    Remove invalid 'random-detect' OR 'queue-limit' statements from the policymap

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_IP_OR_MPLS_MATCH_CONFIG match on ip or mpls packet fields is not supported on a policy attached to layer2 interface

Explanation    Matching on layer3 packet fields such as dscp, prec, exp on a service policy attached to an Access Circuit is not supported. Packets received and transmitted on an AC are considered layer2 packets, packet headers beyond L2 are not parsed in the hardware

Recommended Action    Remove match statements that match on layer3 fields of a packet in the classmaps used by the service policy

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_L2_MATCH_CONFIG match on mac address is not supported on a policy attached to layer3 interface

Explanation    Matching on source or destination mac address on a policy attached to layer-3 interfaces such as routed vlan or POS interfaces is not supported

Recommended Action    Remove invalid match statements in the classmaps used by the service policy

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_MAC_ADDR_MATCH_CONFIG match on src/dst mac is not supported on output/input l2 service policy

Explanation    Matching on mac address in an l2 service policy is supported with the following constraints: Match on source mac address is supported only on input l2 service policy Match on destination mac address is supported only on output l2 service policy

Recommended Action    Remove unsupported match statements in the classmaps used by the service policy

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_MARKING_CONFIG Invalid marking configuration in service policy attached to layer2 interface

Explanation    On service policy attached to an AC, marking of certain fields is not supported. The following marking configurations are invalid: Ingress/Egress: ip dscp, ip precedence, mpls exp topmost Egress: mpls exp imposition, qos-group, discard-class

Recommended Action    Remove invalid 'set' statements from the policymap

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_MATCH_COS_CONFIG match cos command is not supported on layer-3 interface egress policies. Invalid Configuration.

Explanation    'match cos' command is not supported on service policy applied to layer-3 interfaces since layer2 encapsulations are removed before packets are sent to egress.

Recommended Action    Remove invalid 'match cos' command from class-map

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_MIN_BW_CONFIG Bandwidth command is not supported on the ingress side. Invalid Configuration.

Explanation    Bandwidth command is not supported on ingress policies. Instead, configure 'bandwidth remaining' to assign weights for the different queues.

Recommended Action    Configure policy without 'bandwidth' on the ingress.

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_MULTIPLE_POLICER_ACTIONS multiple set commands in a policer action are not supported

Explanation    Only one set command is allowed on each of conform, exceed and violate actions of a policer.

Recommended Action    Remove multiple set commands on policer conform/exceed/violate action

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_POLICER_MARKING_CONFIG Invalid policer marking configuration in service policy attached to layer2 interface

Explanation    On service policy attached to an AC, policer marking of certain fields is not supported. The following policer marking configurations are invalid: Ingress/Egress: ip dscp, ip precedence, mpls exp topmost Egress: mpls exp imposition

Recommended Action    Remove invalid 'police' statements from the policymap

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_POLICER_MARKING_L2_COS_CONFIG Invalid policer marking configuration in service policy attached to layer3 interface

Explanation    On service policy attached to a layer-3 interface, policer marking of layer-2 CoS field is not supported.

Recommended Action    Remove 'set cos' action on 'police' command from the policymap

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_POLICER_RATE Unsupported policer value used in policymap : [dec] kbps. It must be less than 16 Gbps

Explanation    Configured policer value can not be more than 16Gbps. Policy map is rejected.

Recommended Action    Reconfigure policy map to configure appropriate policer value.

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_Q_LIMIT_CONFIG In order to configure queue-limit for a class, atleast one feature that allocates a separate queue for that class needs to be configured.

Explanation    If queue-limit command for a class is configured, then that class requires a separate queue (due to h/w implementation). Since the user has not configured any feature for this class that allocates a separate queue for that class, the user is not allowed to configure queue-limit for that class.

Recommended Action    Configure policy with a feature which allocates a separate queue.

Error Message     
 
    
    
   

%QOS-QOS-3-UNSUPPORTED_WRED_CONFIG Invalid wred profile type in service policy attached to layer2 interface

Explanation    On service policy attached to an AC, valid wred profile types are layer2_cos discard-class and default

Recommended Action    Remove invalid 'random-detect' statements from the policymap

Error Message     
 
    
    
   

%QOS-QOS-3-WRONG_QUANTAS_SPECIFIED Bandwidth remaining should only be specified in multiples of 5

Explanation    Bandwidth remaining commnad has a limitation where the percentages can only be specified in multiples of 5. If not, policy map is rejected.

Recommended Action    Reconfigure policy to configure quantas in multiples of 5

Error Message     
 
    
    
   

%QOS-QOS-4-NODE_INSTL_FAIL Could not install [chars] feature [chars]

Explanation    An error was encountered while trying to add the specified feature node to NetIO. Both the feature name and the error code are displayed. This is a critical error in the QOS component. It indicates that some QOS feature is not working properly.

Recommended Action    Please provide the output of the commands: Please provide the output of the commands: show running configuration show qos trace

Error Message    
 
    
    
   

%QOS-QOS-4-ERR_EVM_EVENT_BLOCK Unrecoverable error in event loop. Error: [chars]

Explanation    An error (other than EINTR) occured in the event loop. The process has exited and restarted.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-4-PARENT_HAS_NO_QUEUEING_CONFIG Queueing configuration for all child classes ignored since parent class [chars] has no queueing configuration

Explanation    Since parent class has no queueing configuration, the queueing configuration in all its child classes will be ignored and the classes will be assigned to default queue.

Recommended Action    Configure some queueing command like 'shape average percent 100' in parent class.

Error Message     
 
    
    
   

%QOS-QOS-4-Q_LIMIT_BELOW_MIN Configured value of queue-limit [dec] has been increased to the minimum permissible value of [dec] bytes

Explanation    Queue limit must be set to atleast max MTU size of 9216 bytes. Therefore, if configured queue limit is below max MTU size, it will be automatically increased to the minimum permissible value.

Recommended Action    Configure queue limit to be atleast the minimum permissible value displayed in the syslog message.

Error Message     
 
    
    
   

%QOS-QOS-4-Q_THRESHOLD_EXCEEDS_MAX [chars]

Explanation    Ingress and egress queuing asics support a maximum packet buffering capacity of 1 Gbytes. Therefore queue-limit or RED thresholds of greater than 1 Gbytes (1073741824 bytes) cannot be configured and will be automatically set to the maximum permissible value.

Recommended Action    Please re-evaluate the value of queue-limit and/or RED thresholds since it is unlikely that such a high value is necessary.

Error Message     
 
    
    
   

%QOS-QOS-4-WRED_THRESH_MORE_THAN_QUEUE_LIMIT Min or max threshold for one or more RED profiles of class [chars] is greater than queue limit ([dec] bytes)

Explanation    Since min or max threshold is greater than queue limit, RED will not take effect or partially take effect for one or more RED profiles of this class.

Recommended Action    Set RED min and max threshold to be below queue limit.

Error Message     
 
    
    
   

%QOS-QOS-5-PARENT_HAS_NO_BW_MIN_CONFIGURED Child class bandwidth minimum is reduced to zero due no minimum bandwidth guarantee in parent

Explanation    Bandwidth command in a child class requires similar command in the parent class. Otherwise minimum bandwidth guaranteed for child class would be zero

Recommended Action    Reconfigure policy to assign bandwidth guarantee in the parent class before the gaurantee is given to the child class.

Error Message     
 
    
    
   

%QOS-QOS-6-MIN_BW_IGNORED_ON_SUBIF Minimum bandwidth configuration ignored in a non-hierarchical policy applied on a sub-interface

Explanation    Since non-hierarchical policy has been applied on a sub-interface, minimum bandwidth configuration will be ignored for all classes in this policy.

Recommended Action    Reconfigure policy such that it is a hierarchical policy with class-default as the only parent class and the original non-hierarchical policy as the child policy. Then configure minimum bandwidth in parent class-default.

Error Message     
 
    
    
   

%QOS-QOS-6-HPOLICY_ATTACH_FAIL Too many levels of hierarchy in policy [chars].

Explanation    The Policy could not be installed because it has more than 2 levels of hierarchy.

Recommended Action    Simplify the policy-map to include no more than 2 levels of hierarchy. and reapply it.

Error Message     
 
    
    
   

%QOS-QOS-6-POLICY_ATTACH_FAIL Service policy [chars] could not be attached to [chars]. Error code - [chars]

Explanation    Policy could not be installed. The reason is displayed.

Recommended Action    Please verify that the specified policy has been configured with the following command: show running configuration

Error Message     
 
    
    
   

%QOS-QOS-7-CLASSMAP_NOT_FOUND Class map [chars] not found

Explanation    The specified class map was not found. Make sure that it is properly configured. If not, please confifure it.

Recommended Action    Verify that the specified class-map name is properly configured by issuing the following command show running class-map

Error Message     
 
    
    
   

%QOS-QOS-7-DLL_REGISTER_CERR_FAIL Could not register error codes for [chars] dll. Error code - [chars]

Explanation    Could not get register DLL error codes. This is not a critical error. The QOS Manager will function properly, but will not be able to use any of the debug facilities.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-ENS_ERROR ENS Debug:[chars] rc=[chars]

Explanation    The ENS/NRS infrastructure is not available.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-7-ERR_BAG_REGISTER Failed to register bag structures with bag server (Reason: [chars])

Explanation    The process could not register the data structures used by QoS statistics and management agents. This is not a critical error Qos will work properly. However show commands may not work.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-ERR_EVM_ASYNC_ATTACH Failed to attach handler for async events: [chars]

Explanation    Failed to attach handler for async events.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-7-ERR_EVM_CREATE Failed to create event manager

Explanation    Failed to create event manager.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-ERR_MEM_ALLOC [chars]

Explanation    The QOS manager process could not get memory for the specified memory usage. This condition will occur if the system is low on memory.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-ERR_SYSDB SysDB error [chars]. Error code - [chars]

Explanation    There were problems communicating with the SysDB. The reason and error message are displayed. If this message is displayed, the qosmgr process will restart itself.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-EVENT_CONN_ERR Error in [chars]: [chars]

Explanation    Error encountered in opening connection to a required server. If this error occurs, the QoS Manager will restart itself.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-IM_CONNECT_FAIL Interface control server connection failed - [chars]. Error code - [chars]

Explanation    Connection to interface manager failed. If this contition occurs, the QOS Manager will restart itself.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-OVL_RGST_FAIL Could not register ovl notification handler. Error code - [chars]

Explanation    An error was encountered while trying to register the OVL notification handler.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS-7-POLICY_INSTALL_FAIL Policy could not be installed [chars] [chars] Error code - [chars]

Explanation    The specified policy could not be attached to an interface due to the specified reason.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%QOS-QOS-7-POLICY_NOT_FOUND Policy [chars] not found

Explanation    The specified policy name was not found. Make sure that it is properly configured. If not please configure it.

Recommended Action    Verify that the specified policy map is properly configured by issuing the following command show running policy-map .

Error Message     
 
    
    
   

%QOS-QOS-7-POLICY_REMOVE_FAIL Failed to remove policy [chars]. Error= [chars]

Explanation    The specified policy could not be removed from an interface due to the specified reason.

Recommended Action    Please follow the instructions from the error message.

 
    
    
   

QOS-QOS-7-CONNECT_FAIL Server connection failed - [chars]. Error code - [chars]

Explanation    Connection to IMP server failed during process init.

Recommended Action    No action is required. Process will be automatically restarted. If not recovered, it is a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%QOS-QOS-7-ERR_EVM_CREATE Failed to create event manager

Explanation    Failed to create event manager.

Recommended Action    No action is required. Process will be automatically restarted. If not recovered, it is a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%QOS-QOS-7-NETIO_SET_PAK_SHAPEQ_FAIL Failed to set packet shape Q - [chars] Error : [chars]

Explanation    Could not set the queue where this packet is supposed to be queued. As a consequence the packet is being dropped.

Recommended Action    Try removing the policy and reapplying it.