Cisco IOS XR System Error Message Reference Guide, R3.8.4
Quality of Service Messages
Downloads: This chapterpdf (PDF - 420.0KB) The complete bookPDF (PDF - 16.68MB) | Feedback

Quality of Service (QoS) Messages

Table Of Contents

Quality of Service (QoS) Messages

EFCM Messages

QOS_EA_TEST Messages

QOS_EA_VERIFY Messages

QOS_FIFO Messages

QOS_MA Messages

QOS_TXM Messages

QOS Messages

QOSEA Messages

QOSRM_DLL Messages

QOSRM Messages


Quality of Service (QoS) Messages


This section contains all Quality of Service related System Error Messages.

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*

QOS_EA_TEST Messages

Error Message     
 
    
    
   

%QOS-QOS_EA_TEST-3-ERROR QoS EA test error ocured at function [chars]: [chars]

Explanation    The QoS EA test process encountered the specified error

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_EA_TEST-3-ERROR QoS EA error [chars]: [chars]

Explanation    The QoS EA process encountered the specified error

Recommended Action    None

QOS_EA_VERIFY Messages

Error Message     
 
    
    
   

%QOS-QOS_EA_VERIFY-6-ERROR QoS EA verify policy failed, error [chars]: [chars]

Explanation    The QoS EA policy verification encountered the specified error

Recommended Action    Correct the qos policy

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

QOS_MA Messages

Error Message     
 
    
    
   

%QOS-QOS_MA-3-CAPS_INFO_ADD QoS MA caps add failed: caps: [unsigned int], proto: [unsigned int], ifhandle: [hex], service_policy: [chars], error: [chars]

Explanation    The QoS MA process encountered the specified error while trying to add the caps.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_MA-3-CAPS_REMOVE QoS MA caps remove failed: caps: [unsigned int], proto: [unsigned int], ifhandle: [hex], error: [chars]

Explanation    The QoS MA process encountered the specified error while trying to remove the caps.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_MA-3-DPC_REM QoS MA DPC (delete) failed: ifhandle: [hex], caps: [unsigned int], error: [chars]

Explanation    The QoS MA process encountered the specified error while trying to send a critical operation to the EA.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_MA-3-OP_FAIL [chars] Error [hex]:[chars]

Explanation    A critial operation attempted by QoS MA has failed. It may affect the proper functioning of QoS features.

Recommended Action    None.

Error Message     
 
    
    
   

%QOS-QOS_MA-7-FABQOS_SEND_FAILED The switch-fabric service policy '[chars]' was not accepted correctly by the EA. Error: [chars]

Explanation    The QoS MA process encountered the specified error upon startup or restart. The EA did not process the FABQOS policy correctly.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_MA-7-INIT QoS MA initialisation failed in function [chars]: [chars]

Explanation    The QoS MA process encountered the specified error while initializing the specified facility. If this error occurs, the sysmgr process will restart the QoS MA process.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_MA-7-INVALID_CAPS_STATUS The service policy '[chars]' on '[chars]', '[chars]' is in inconsistent state. Please remove and reconfigure the service policy.

Explanation    The QoS MA process encountered the specified error in the 'apply' phase. The incorrect caps type is present in the QOS MA DB. This could be the result of an incorrect operation in the'verify' phase.

Recommended Action    None

Error Message     
 
    
    
   

%QOS-QOS_MA-7-INVALID_ERROR_ARRAY_STATUS The dpc error array '[hex]' and caps error array '[hex]' have invalid codes at the same index '[dec]'.

Explanation    An internal error was encountered while processing QoS configuration.

Recommended Action    None

QOS_TXM Messages

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 Messages

Error Message     
 
    
    
   

%QOS-QOS-2-MALLOC_FAIL Memory alloc error [chars] [chars]

Explanation    The router cannot allocate more memory.

Recommended Action    It may be necessary to free some memory by exiting a program.

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-CONNECT_FAIL Server connection failed - [chars]. Error code - [chars]

Explanation    Connection to some server failed.

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-DEBUG_FAIL Error occurred while registering for debugging services

Explanation    Error occurred while waiting for an event.

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-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-EA_IIR_ATTACH_FAILURE Error encountered during QoS programming for bundle member [chars] (ifh: [hex]) of bundle CH[hex], direction: [chars], error: [chars]

Explanation    A member was added to the bundle or it was added earlier and link came up now. This triggers update event and an error is encountered in QoS EA process while handling update event for the bundle member.

Recommended Action    If its scaled config exhausting h/w resources, try reducing number of targets for QoS policies.

Error Message     
 
    
    
   

%QOS-QOS-3-EA_IM_CAPS_RESYNC_FAILURE Error encountered during caps resync with IM for interface: [chars] (ifh: [hex]), direction: [chars], error: [chars]

Explanation    QoS EA encountered an error during resync of QoS capsulations with IM.

Recommended Action    Try removing the QoS policy on the interface for which this error message is printed from configuration, and then reattach the policy to the interface.

Error Message     
 
    
    
   

%QOS-QOS-3-EA_ROLLBACK_FAILURE_DURING_MODIFY Error encountered during rollback of policy modification on interface: [chars] (ifh: [hex]), direction: [chars], error: [chars]

Explanation    QoS EA encountered an error when modifying the policy on an interface, upon which a rollback was attempted on this interface to restore the old policy. There was an error encountered during this rollback too, due to which neither the old policy nor the new policy is applied in hardware for this interface.

Recommended Action    Try removing the QoS policy on the interface for which this error message is printed from configuration, and then reattach the policy to the interface.

Error Message     
 
    
    
   

%QOS-QOS-3-EVM_CREATE_FAIL Failed to create event manager

Explanation    Failed to create event manager.

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-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-WAIT_ERR Error occurred while waiting for an event

Explanation    Error occurred while waiting for an event.

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-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-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-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    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-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-EA_DEBUG_INIT_FAIL Failed to initialise debug infra within QoS EA. Error: [chars]

Explanation    Debug initialization failed within EA. Debugs may not be printed

Recommended Action    Try restarting QoS EA process

Error Message     
 
    
    
   

%QOS-QOS-6-EA_LTRACE_INIT_FAIL Failed to initialise ltrace infra within QoS EA. Error [chars]

Explanation    Ltrace initialization failed within EA. Ltraces may not be printed

Recommended Action    Try restarting QoS EA process

Error Message     
 
    
    
   

%QOS-QOS-6-EA_MIPC_NTFN_ACK_FAILURE Error encountered while trying to ACK to an MIPC event notification [unsigned int]. Error [chars]

Explanation    QoS EA encountered an error while ACKing to an MIPC event

Recommended Action    Try restarting QoS EA process

Error Message     
 
    
    
   

%QOS-QOS-6-EA_MIPC_NTFN_HNDLR_FAILURE Failed to process MIPC notification [unsigned int] within QoS EA. Error [chars]

Explanation    QoS EA encountered an error while processing an MIPC event notification

Recommended Action    Try restarting QoS EA and/or HFR Platform Manager process

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-NETIO_SET_PAK_SHAPEQ_FAIL Failed to set packet shape Q to [dec]. Dropping packet. Error: [chars]

Explanation    Could not set the outgoing queue associated with this packet. As a consequence the packet is being dropped. During normal operation of the system, an occasional (very in-frequent) packet drop in the slow-path is tolerable.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%QOS-QOS-6-QFIFO_DEBUG_NETIO_INIT_FAIL Failed to initialise debug infra within the qfifo node on the netio chain. Error: [chars]

Explanation    Debug initialization failed within the qfifo node on the NetIO chain. Debugs may not be printed.

Recommended Action    Try restarting netio process

Error Message     
 
    
    
   

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

Explanation    Connection to IMP server failed during process init. This could be because QoS EA is - Unable to bind to the IMP server, - Unable to map context to connection ID, - Unable to register callback handler, or - Unable to initialise event handler for connect/ disconnect events The above situations would lead to an inability of QoS EA to process CAPS from MA (via IM/IMP infrastructure), and to a potential disconnect between the hardware/software views of the configured qos policies on the system.

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-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 setup event manager

Explanation    Failed to setup 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-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.

QOSEA Messages

Error Message     
 
    
    
   

%QOS-QOSEA-3-BWCHG_ERROR QOSEAERR: update bandwidth for ifh [hex] with [dec] [chars] [chars] [chars]

Explanation    This is an error message from the QoS EA bandwidth changeProcess, it indicates that something has gone wrong internally in the QoS EA during bandwidth change.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSEA-3-ERROR QoSEA-Err: [chars]

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

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSEA-3-EXIT_ERROR QoSEA-Err: [chars] [chars]

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

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSEA-3-IMATTR_ERROR QOSEAERR: im_attr_get bandwidth [chars] [hex] Error: [chars]

Explanation    This is an error message from the QoS EA bandwidth changeProcess, it indicates that something has gone wrong internally in the QoS EA during bandwidth attribute get.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSEA-3-MSG_CHAN Could not create Msg chan: [chars] error: [chars]

Explanation    The QoS EA could not create the necessary message channel due to the given error

Recommended Action    *DDTS*

Error Message     
 
    
    
   

%QOS-QOSEA-3-MSG_HANDLER_ERR An error occurred in the [chars] message handler

Explanation    An error occurred during message handling in the indicated message handler

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSEA-3-POLICY_ERROR QoSEA-Err: class:[chars], [chars]

Explanation    This is an error message from the QoS EA Process, it indicates that something has gone wrong while trying to configure a service policy.

Recommended Action    *NONE*

Error Message     
 
    
    
   

%QOS-QOSEA-3-ROLLBACK_ERROR QoSEA-Rollback-Err: [chars]

Explanation    This is an error message from the QoS EA Process, it indicates that rollback failed in the QoS EA.

Recommended Action    Pls analyse the resource availability in the LC. Remove and add the qos policy-map for the interface.

Error Message     
 
    
    
   

%QOS-QOSEA-3-UNHANDLED_MSG The QoS EA received an unhandled message

Explanation    The QoS EA received a message that it was unable to handle'

Recommended Action    *DDTS*

Error Message     
 
    
    
   

%QOS-QOSEA-3-UNKNOWN_MSG An unknown message was dispatched to the [chars] message handler: Msg: [hex]

Explanation    An incoming message was demuxed to the incorrect message handler

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSEA-4-WARN QoSEA-Warn: [chars]

Explanation    This is a warning message from the QoS EA Process

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QOSEA-5-NOTICE QoSEA-Notice: [chars]

Explanation    This is a notice message from the QoS EA Process

Recommended Action    *NONE*

Error Message     
 
    
    
   

%QOS-QOSEA-6-BWCHG_LOG QOSEA: updated bandwidth for ifh [hex] with [dec] [chars] [chars]

Explanation    This is an informational message from the QoS EA Process, it indicates that bandwidth change happened for an interface.

Recommended Action    *NONE*

Error Message     
 
    
    
   

%QOS-QOSEA-6-INFO QoSEA-Info: [chars]

Explanation    This is an informational message from the QoS EA Process

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QOSEA-6-MSG_ASYNC An Asynchronous message was received

Explanation    The QoS EA received an asynchronous message.

Recommended Action    *NONE*

Error Message     
 
    
    
   

%QOS-QOSEA-6-POLICY_INFO QoSEA-Info: class:[chars], [chars]

Explanation    This is an informational message from the QoS EA Process. It indicates that something can not be configure in service policy.

Recommended Action    *NONE*

Error Message     
 
    
    
   

%QOS-QOSEA-7-DEBUG QoSEA-Debug: [chars]

Explanation    This is a debuging message from the QoS EA Process

Recommended Action    *NONE*

QOSRM_DLL Messages

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-3-ERROR QoSRM-DLL-Err: [chars]

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

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-3-MSG_CHAN Could not create Msg chan: [chars] error: [chars]

Explanation    The QoS RM dll could not create the necessary message channel due to the given error

Recommended Action    *DDTS*

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-3-MSG_HANDLER_ERR An error ([chars]) occurred in the [chars] message handler,Msg:[hex]

Explanation    An error occurred during message handling in the indicated message handler

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-3-UNHANDLED_MSG The QoS RM dll received an unhandled message

Explanation    The QoS RM dll received a message that it was unable to handle'

Recommended Action    *DDTS*

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-3-UNKNOWN_MSG An unknown message was dispatched to the [chars] message handler: Msg: [hex]

Explanation    An incoming message was demuxed to the incorrect message handler

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-3-UNKNOWN_QTYPE Unknown Q-Type in message: [hex]

Explanation    The QoS RM dll received a message, but was unable to determine which resource the message was intended for because the Q-Type field was incorrect.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-4-WARN QoSRM-DLL-Warn: [chars]

Explanation    This is a warning message from the QoS RM DLL

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-6-INFO QoSRM-DLL-Info: [chars]

Explanation    This is an informational message from the QoS RM DLL

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-6-MSG_ASYNC An Asynchronous message was received

Explanation    The QoS RM dll received an asynchronous message.

Recommended Action    *NONE*

Error Message     
 
    
    
   

%QOS-QOSRM_DLL-7-DEBUG QoSRM-DLL-Debug: [chars]

Explanation    This is a debuging message from the QoS RM DLL

Recommended Action    *NONE*

QOSRM Messages

Error Message     
 
    
    
   

%QOS-QOSRM-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-QOSRM-3-MSG_CHAN Could not create Msg chan: [chars] error: [chars]

Explanation    The QoS RM could not create the necessary message channel due to the given error

Recommended Action    *DDTS*

Error Message     
 
    
    
   

%QOS-QOSRM-3-MSG_HANDLER_ERR Event: [chars] occurred in the [chars] message handler, Msg:[hex]

Explanation    An error occurred during message handling in the indicated message handler

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSRM-3-UNHANDLED_MSG The QoS RM received an unhandled message

Explanation    The QoS RM received a message that it was unable to handle'

Recommended Action    *DDTS*

Error Message     
 
    
    
   

%QOS-QOSRM-3-UNKNOWN_MSG An unknown message was dispatched to the [chars] message handler: Msg: [hex]

Explanation    An incoming message was demuxed to the incorrect message handler

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%QOS-QOSRM-3-UNKNOWN_QTYPE Unknown Q-Type in message: [hex]

Explanation    The QoS RM received a message, but was unable to determine which resource the message was intended for because the Q-Type field was incorrect.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

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

Explanation    This is a warning message from the QoS RM Process

Recommended Action    *RECUR*

Error Message     
 
    
    
   

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

Explanation    This is an informational message from the QoS RM Process

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%QOS-QOSRM-6-MSG_ASYNC An Asynchronous message was received

Explanation    The QoS RM received an asynchronous message.

Recommended Action    *NONE*

Error Message     
 
    
    
   

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

Explanation    This is a debuging message from the QoS RM Process

Recommended Action    *NONE*