Table Of Contents
Quality of Service (QoS) Messages
QALLOC Messages
QOS_CLASSIFY_NETIO Messages
QOS_FIFO Messages
QOS_RC_QOSMGR Messages
QOS_TXM Messages
QOS_WRED 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. The following facility codes are represented in this module:
•
QALLOC Messages
•
QOS_CLASSIFY_NETIO Messages
•
QOS_FIFO Messages
•
QOS_RC_QOSMGR Messages
•
QOS_TXM Messages
•
QOS_WRED Messages
•
QOS Messages
•
QOSEA Messages
•
QOSRM_DLL Messages
•
QOSRM Messages
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,
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
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_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-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-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-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-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-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-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-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-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-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-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-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_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-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-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-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-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-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_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-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-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.
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.
QOSEA Messages
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-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-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-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*